Confirm what was promised
Check service dates, billing period, deliverables, renewal terms and whether performance occurs over time or at a point in time.
Invoicing a customer is not always the same as earning the revenue. For annual subscriptions, prepaid support and services delivered over time, the accounting needs to follow the service period—not just the invoice date.
Illustrative straight-line service schedule. Actual treatment depends on contract terms and accounting policy.
When a customer pays ahead of the service or performance period, the unearned portion generally remains a liability until the related obligation is satisfied. The schedule should explain how that balance turns into revenue over time.
The invoice records the amount due from the customer. For advance billing, that alone does not prove the full amount has been earned.
The appropriate portion is tracked as deferred revenue or another suitable liability based on the contract and accounting policy.
Periodic entries move the appropriate amount from the liability to revenue based on the service pattern or other applicable recognition approach.
Treat each stage as a control point. A correct invoice does not guarantee that subsequent deferral and recognition entries are correct.
Check service dates, billing period, deliverables, renewal terms and whether performance occurs over time or at a point in time.
Verify that invoice lines use the intended revenue or deferred-revenue account treatment for the configured process.
Confirm the schedule begins and ends in the right periods, total scheduled amounts agree to the relevant balance, and periods are allocated correctly.
Tie deferred revenue to unrecognized contract amounts and explain the current-period revenue released from the liability.
Model a simple arrangement where revenue is earned evenly over the service term. Adjust the contract amount, number of months and how much of the term has elapsed.
This is an educational estimate, not an automatic determination of the correct accounting treatment. Contract terms and the applicable accounting framework govern recognition.
Use these scenarios to identify where the schedule and service agreement may not agree.
A customer pays for 12 months upfront. If the service is provided over the year, recognizing the full amount in the first month may overstate that month's revenue.
A business bills a maintenance package before all support periods have occurred. The outstanding obligation should be visible and reconciled, subject to the contract terms.
A customer's payment or advance invoice can be mistaken for earned revenue even when work remains. The correct treatment depends on what has been delivered and the contract terms.
Check these before making a manual adjustment to the liability or income statement.
The setup may recognize the full billed amount before the related service period has elapsed.
A start/end date mismatch may push revenue into periods outside the contract.
Discounts, credits, partial periods or manual edits may leave part of the amount unallocated.
The schedule may exist, but the related period entries may be missing or unposted.
A contract change can affect unearned revenue; confirm the schedule reflects the approved change.
The ledger may include manual entries or contracts not included in the supporting schedule.
At month-end, link the contract-level schedule to the liability and the revenue released for the period.
| Control | Question to answer | Evidence |
|---|---|---|
| Contract schedule | Does it match the arrangement and remaining service? | Contract, dates, schedule |
| Deferred revenue liability | Does the GL balance match the amount not yet recognized? | Liability ledger, detail report |
| Revenue recognized | Does current-period revenue match the service delivered? | Posted entries, service evidence |
| Adjustments | Are credits, cancellations and manual journals explained? | Credit notes, journals, approvals |
Use the checklist each close, then investigate exceptions instead of rebuilding the reconciliation from scratch.
Deferred revenue generally represents an amount billed or received before the related goods or services have been provided. The unearned portion is typically tracked as a liability and recognized as the relevant obligation is satisfied.
Check the accounts mapped to invoice lines, deferral setup and whether the appropriate schedule or recurring entries are configured and posted. Exact labels and steps can differ by Odoo version and configuration.
Compare the contract-level unrecognized balance with the deferred revenue liability in the general ledger. Tie current-period releases to recognized revenue and investigate credits, schedule differences and manual entries.
Not automatically. Treatment depends on the contract, what the payment relates to, whether a performance obligation has been satisfied and the applicable accounting policy. Review the facts before deciding how an advance should be classified.
No. Straight-line recognition is appropriate only when it reasonably reflects the pattern in which the related goods or services are transferred. Some contracts require another pattern or separate treatment for distinct obligations.
Accountrise helps US businesses and accounting firms clean up Odoo accounting, review revenue schedules, reconcile balance sheet accounts and build repeatable month-end processes.
Accounting support starting at $10/hour. Final pricing depends on scope, transaction volume, complexity and engagement requirements.