Revenue Management and Accounting
This domain tests how revenue is scheduled and recognized separately from billing, and how Receivables accounting reaches the general ledger through Subledger Accounting.
Revenue versus billing
Billing creates a receivable. Revenue recognition follows a revenue policy and satisfaction method, such as period-based recognition over a service period or milestone-based recognition. Accounting rules create revenue schedules for transactions, while revenue adjustments and changes in transaction price revise those schedules. When billing precedes revenue, the difference sits in unearned revenue; when revenue precedes billing, it sits in an unbilled receivable.
Subledger accounting
Receivables generates accounting entries through Subledger Accounting. You run Create Accounting to produce journal entries, review exceptions, then run Transfer to General Ledger and post in GL. The accounting date on the transaction and the GL period must be open in both applications.
Worked example
A 120,000 annual support contract is billed in full at the start of the year, and the revenue policy recognizes revenue evenly over 12 months. At billing, the entry debits Receivable and credits Unearned Revenue for 120,000. Each month, 10,000 is recognized by debiting Unearned Revenue and crediting Revenue. After six months, the unearned balance is 60,000. If the contract were billed in arrears, the same monthly recognition would create an unbilled receivable instead.
Traps
- Treating an accounting rule as the revenue policy, or vice versa; they serve different purposes.
- Running Create Accounting in draft mode and assuming the entries reached GL.
- Ignoring accounting date versus GL date, which can send entries to the wrong period.
- Missing revenue adjustments that should revise an existing schedule rather than create a new transaction.