Revenue Posting
The Revenue Accounting system manages revenue recognition by using objects like revenue accounting contracts and performance obligations. The system receives events that relate to revenue recognition and tracks the fulfillment of performance obligations. However, revenue postings do not occur at the times of those events. The accountant performs revenue posting jobs regularly to post FI documents to the general ledger. For example, the accountant may run a revenue posting job at the end of each accounting period to transfer revenue recognition transactions to the general ledger.
To enable revenue postings, you need to perform the following Customizing activities:
You have defined accounting principles and enabled company codes for Revenue Accounting.
Choose .
You have defined tax codes for non-taxable transactions.
Choose .
You have configured parallel processing for the posting of revenue.
Choose .
You have defined the transfer account, posting keys, document type, and account assignments.
Choose .
Note
Unless otherwise specified in this Customizing activity, the system uses by default SA as the document type, 40 as the debit posting key, and 50 as the credit posting key.
You have configured account determination.
Choose .
You can post revenue for one accounting period at a time. Before you can post revenue for a period, you must make sure that you have already successfully posted revenue for all of the previous periods.
The system allows you to simulate a posting job in test mode. You can use the simulated results to verify the account determination, account assignments, debit/credit side, and posting amounts. Additionally, the test mode allows you to select specific contracts and performance obligations to simulate postings. The test mode is activated by default when you enter the revenue posting user interface.
In test mode, the system performs basic checks on your posting options to prevent you from running a job that will eventually fail. For example, the test mode checks whether the selected company codes exist. However, it does not check against issues that can only be detected while the job is running.
In test mode, line items for contract liabilities and assets are aggregated at contract level. Other line items are aggregated at performance obligation level.
The posting of revenue is run as a background job. The accountant schedules a job and checks the job upon completion. The job monitor displays the results of posting jobs to indicate whether the jobs are successful.
You can monitor the status of the posting job, such as planned start time, start time, and end time. You can view the processing details of the posting job. Additionally, you can open the posted documents relating to the posting job.
You can schedule a posting job to run once or to recur at regular intervals. To run the posting job once, you can schedule it to run either immediately or at a specified time. You can also schedule the posting job to recur daily, weekly, or monthly.
For a scheduled posting job, the system performs basic checks on your posting options to prevent you from running a job that will eventually fail. However, it does not check against issues that can only be detected while the job is running.
The system determines the posting date, which is required in the posted FI documents, as follows:
Job Run Time | Posting Date |
|---|---|
Run once (either immediately or later) | You are prompted to specify a posting date for the posting job. The specified date must fall in the accounting period. |
Recur daily | The date for which the posting job is scheduled |
Recur weekly | The date for which the posting job is scheduled |
Recur monthly | The last day of the period |
You can choose whether to include transactions that relate to contract liabilities and contract assets in the posting job. However, when you retry a failed posting job for which this option was enabled, the system assumes that this option is enabled the second time round, regardless of whether it is actually enabled or not.
For more information, see Support of Multiple Accounting Principles.
If you have activated General Ledger Accounting (new), all postings are made to the relevant ledger group, depending on the accounting principle.
To reduce the total number of line items in the posted documents, the system aggregates line items by a combination of several fields, such as G/L account, account assignment attributes, and condition type. Therefore, line items that have identical values for all these fields are merged into one line item.
In some rare scenarios, the amount of a single line item exceeds 99,999,999,999. In this case, the system splits the line item into several line items.
Typically, the system creates one FI document for each posting job. However, the system splits the document into several documents in the following scenarios:
More than 900 line items are to be included.
The transactions to be posted involve different document currencies.
Revenue-related postings are not relevant to input and output taxes. If the posting involves an account that is defined as tax-related, the system uses a tax code that applies a zero tax rate. You can define the tax code in the following Customizing activity:
Choose .
You can include account assignment data (segment, profit center, business area, and function area) in FI documents posted to the general ledger. This can be customized at company code level in the following Customizing activity:
Choose .
You can reverse the postings made by a previous revenue posting job.
You can perform the following accounting tasks:
Schedule a revenue posting job to run immediately
Schedule a revenue posting job to run later
Schedule a revenue posting job to recur at regular intervals
Simulate a revenue posting job
Monitor the statuses of revenue posting jobs
Review the results of revenue posting jobs
View the posted documents of a revenue posting job
Reverse the postings made by a previous revenue posting job