Upfront cash can finance operations, but part of it may represent an obligation to serve or refund the customer.
Revenue accountant
Monthly
Maintain a customer-level schedule.
Customer contract and invoice.
Deferred or unearned revenue arises when billing or collection precedes satisfaction of the related performance obligation under the applicable accounting framework.
The balance should be supported contract by contract or through a reliable subledger. Opening liability plus new deferrals minus revenue recognised and refunds should reconcile to closing liability.
Cash planning must recognise the service cost that remains. Spending all annual subscription cash immediately can create a future liquidity problem even when the current bank balance appears strong.
| Control | What it covers | Operating rule |
|---|---|---|
| Opening balance | Prior-period obligation not yet earned. | Reconcile to customer schedule. |
| New billing | Invoices or receipts for future service. | Separate earned and deferred portions. |
| Revenue release | Obligation satisfied during the period. | Use service and contract data. |
| Closing balance | Remaining obligation and refund exposure. | Tie to general ledger. |
Show both operating cash and remaining contractual obligation to the board. High upfront collections improve liquidity but do not erase the cost of future delivery.
Investigate negative or old deferred balances. They may indicate invoice errors, cancellations, integration gaps or an incorrect revenue policy.
Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.
Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.
Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?
The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.
The operating record should connect the control stages—opening balance, new billing, revenue release, closing balance—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.
Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.
Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.
Finance should reconcile the operational schedule to the general ledger and explain every reconciling item by amount, age and owner. Manual journals, overrides and post-close changes deserve heightened review because they can bypass the normal transaction flow.
The board view should separate reported results from estimates and management metrics. When a KPI does not follow the statutory accounting framework, provide a stable definition and a bridge to the closest financial statement line so the measure cannot be changed silently.