Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
IMG Activity
| ID | VORAUSZAHLUNG | Accounting Treatment of Advance Payments |
| Transaction Code | S_ALR_87100544 | (empty) |
| Created on | 19990915 | |
| Customizing Attributes | SIMG_CFMENUOFDIVORAU | Accounting Treatment of Advance Payments |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOFDIVORAU |
In this section, the special treatment of advance payments in rental agreements and sales-based settlements from an accounting point of view is described:
You post service charge advance payments and sales-based rents to the customer account with the help of two special G/L transactions.
The special G/L transactions have to be of the type
"Customer down payments received"
In standard Customizing, sample settings have been made for special G/L transactions J for posting advance payment requests and K for offsetting entries for operating and heating expenses or U for offsetting entries for sales-based rents.
In this case, the posting record reads:
- Service charges
09 J Customer with special G/L account update to J
- to -
19 K Customer with special G/L account update to K - Sales-based rent:
09 J Customer with special G/L account update J
- to -
19 K Customer with special G/L account update to U
On receipt of payment, the advance payment request posting (special G/L transaction J) is cleared. Postings with special G/L indicators K and U remain as open items on the customer account (down payments received) until the service charge settlement or sales-based settlement runs. They are then cleared during the settlement. See also: Service Charge Settlement
You have to make the following settings in Customizing for Financial Accounting:
- Create special G/L transactions as customer down payments received. Note that the transactions MUST be identified as "down payments".
Financial Accounting ->
Accounts Receivable and Accounts Payable ->
Business Transactions ->
Down Payment Received ->
Carry Out or Check Document Settings ->
Define Posting Keys
Here you enter the special G/L transactions required. - Assign special G/L accounts to the special G/L transactions for each customer reconciliation account.
Financial Accounting ->
Accounts Receivable and Accounts Payable ->
Business Transactions ->
Down Payment Received ->
Define Reconciliation Accounts for Customer Down Payments
Here you enter alternative reconciliation accounts (special G/L accounts). - For tax treatment, you have to define value-added tax clearing accounts.
See below for tax treatment.
Financial Accounting ->
Accounts Receivable and Accounts Payable ->
Business Transactions ->
Down Payment Received ->
Define Account for Tax Clearing
Here you define the value-added tax clearing accounts. - The special G/L transactions for receivables postings (09 J) have to be identified as payable transactions to allow for automatic incoming payment and correct tenant account display.
Financial Accounting ->
Accounts Receivable and Accounts Payable ->
Business Transactions ->
Incoming Payments ->
Automatic Incoming Payments ->
Payment Method/Bank Selection ->
Configure Payment Program ->
All company codes ->
Select company code ->
Use: Customer -> Special G/L transactions to be paid
Only define the special G/L transaction for receivable posting (J) here. The K and U postings should not be settled; these are transferred during the settlements. - You have to indentify the special G/L transactions for advance payment requests as being dunnable.
Financial Accounting ->
Accounts Receivable and Accounts Payable ->
Business Transactions ->
Dunning ->
Define Dunning Procedures
For the dunning procedures used, the "Dunning of special G/L transactions" indicator has to be set. Choose Goto -> Special G/L indicator to identify the relevant G/L indicators (J in standard Customizing).
Value-added postings for advance payments
For commercial rental agreements, advance payment postings are handled in the same way as basic rent postings with tax. Depending on the settings made in the reconciliation accounts for G/L transactions, tax can either be posted together with the receivables postings (planned principle) or with the incoming payment (actual principle).
The basic rent (transaction without special G/L transaction) is always posted on the basis of the actual principle.
The following example shows which settings have to be made to post the tax on the basis of the actual principle or the planned principle. The standard Customizing settings are used in the example.
Example:
Condition type "Operating costs advance payments" refers to a flow type that is assigned to posting record
09 J Customer to 19 K Customer
The following reconciliation accounts have been set up in Customizing for Financial Accounting for the special G/L transactions:
J 196900 Real Estate advance payment requests
K 196910 Operating costs advance payments
The tax treatment is controlled by the tax category defined in the master record of the G/L accounts (field SKB1-MWSKZ).
PLANNED PRINCIPLE
Objective: The sales tax appears in the advance tax return after the debit position.
The following postings are made (US 100 net advance payment, US 15 tax):
Debit position
09 J Customer US 115 debit
- 196900 Payment request US 115 debit (reconc.acct)-
19 K Customer US 115 credit
- 196910 Advanced payments received US 115 credit (reconc.acct)-
50 175000 Output tax (from K) US 15 credit
40 170011 Output tax clearing K US 15 debit
After the debit position, the tax appears in the advance tax return.
Incoming payment:
The J item posted to the customer is cleared; the K item remains open (advance payment made). Der auf den Debitoren gebucht J-Posten wird
40 Bank account US 115 debit
19 J Customer US 115 credit
- 196000 Payment request US 115 credit (reconc.acct)-
Settings:
Account and corresponding tax category
196900 not tax-relevant 170010 + 175000 >
196910 +B 170011 +
ACTUAL PRINCIPLE
Objective: The sales tax appears in the advance tax return after receipt of payment.
The following postings are made (US 100 net advance payment, US 15 tax):
Debit position
09 J Customer USD 115 debit
- 196900 Payment request USD 115 debit (reconc.acct)-
40 175000 Output tax (from J) USD 15 debit
50 170010 Output tax clearing J USD 15 credit
19 K Customer USD 115 credit
- 196910 Payments received USD 115 credit (reconc.acct)-
50 175000 Output tax (from K) USD 15 credit
40 170011 Output tax clearing K USD 15 debit
After the debit position, the tax does not appear in the advance tax return.
Incoming payment:
Th J item posted to the customer is cleared: the K item remains open (advance payment made)
40 Bank account US 115 debit
19 J Creditor US 115 credit
- 196900 Payment requeest US 115 credit (reconc.acct)-
40 175000 Output tax (from J) US 15 credit
50 170010 Output tax clearing J
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOFDIVORAU | 0 | I090004614 | Rental Accounting |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19991025 |
| SAP Release Created in |
