Separate billing from recognition
Suppose a service provider invoices USD 1,200 in January for a full year of service. If the contract and accounting policy support twelve equal monthly periods, recognition would be USD 100 per month. The example assumes straight-line recognition, no partial periods and no further adjustments.
The initial invoice can post to a deferred account, with recognition entries moving the appropriate amount into revenue over time. Expense and cost deferrals require their own configuration. The correct treatment depends on the contract and the organisation’s accounting policy.
Configure templates and defaults
- Deferral templates describe the straight-line periods.
- Event-based templates support an agreed milestone or event pattern.
- Deferral defaults connect accounts and templates to the relevant transactions.
- Deferrable items and charges determine which transactions are marked for deferral.

Review equal-per-period settings, posting method and the recognition journal name. Automatic journal posting is a configuration choice, not an assumption. Where manual posting is used, include it explicitly in the operating process.
Apply deferrals to a billing schedule
- Create or select the billing schedule and relevant service lines.
- Check whether the line is marked for deferral.
- Review the deferral accounts, template, start date and period pattern.
- Generate the invoice and inspect the resulting deferral schedule.

A schedule is created from its originating document or billing schedule. Do not treat the deferral schedule as a separate manual allocation with no source transaction. Check revenue and cost postings independently rather than assuming they always follow identical patterns.
Process and reconcile recognition
Open the deferral schedules and review the active periods. Use recognition processing for the intended cut-off date, inspect the proposed entries, and confirm whether the resulting journals require manual posting.


After processing, compare the recognised amount, remaining deferred balance and posted vouchers. Test reversals, credit notes, changes and partial periods as part of acceptance testing. A successful invoice is only one part of the complete recognition process.
Further reading
For current feature availability, prerequisites and detailed configuration, refer to Microsoft Learn.
Screenshots and scenarios are illustrative. Interface labels and available features can vary by application version and environment.


sales@agilitz.com