Deferrals in Business Central

Deferrals in Business Central spread revenue or expense across multiple accounting periods, automating what would otherwise be manual journal entries every month. The typical use case: a customer pays for a twelve-month subscription up front, but the revenue should be recognised one month at a time over the year. Or a company prepays a twelve-month insurance premium, and the expense should be recognised one month at a time.

Deferral templates. A deferral template defines:

• The deferral account — the balance-sheet account where the deferred amount lives temporarily (deferred revenue liability for income, prepaid expense asset for outflow).
• The calculation method — Straight-Line, Equal per Period, Days per Period, User-Defined.
• The number of periods to spread across.
• The start date — beginning of period, end of period, or based on the document date.
• The default GL accounts for revenue or expense recognition.

Templates are reused across many transactions, so you set them up once.

Applying a deferral. On a sales invoice, sales credit memo, purchase invoice, purchase credit memo, or G/L journal line, the user attaches a deferral template (or the template defaults from the item or GL account). At posting, Business Central:

1. Posts the full transaction amount to the deferral account (not the regular revenue/expense account).
2. Generates the deferral schedule — one ledger entry per period with the calculated amount.
3. Books the period entries automatically: the deferral account is reduced and the recognition account (revenue or expense) is increased, period by period.

The deferral schedule view. Each posted document with a deferral has a viewable schedule showing every recognition entry and its status (posted, pending, reversed). Useful for audit and for explaining numbers to controllers who are new to the mechanism.

Reversals and adjustments. A deferral can be reversed by posting a credit memo or G/L correction that triggers the reverse schedule. Partial cancellations and mid-stream changes are supported but require care — adjusting the underlying template doesn't retroactively change already-posted documents.

Job and project use. Project-related deferrals work alongside the WIP module, which has its own revenue and cost recognition mechanism for percentage-of-completion projects. Use deferrals for time-bound straight-line recognition; use WIP journals for milestone-driven recognition.

Reporting. Standard reports show:

• Deferral movement per period (recognised, remaining, total).
• Deferral schedules per document for audit.
• Deferral balance by account at any date.

These reconcile to the balance-sheet deferral accounts and validate the period-end financial statements.

Limits.

• Deferrals are time-based, not event-based — straight-line, not "recognise when the customer uses 50% of their entitlement". For event-based recognition, customers either post manual journals or use Subscription Billing (in BC's newer feature set).
• Deferrals don't model complex ASC 606 / IFRS 15 contracts with multiple performance obligations. For those, customers move to Dynamics 365 Finance Subscription Billing or a specialist tool.

Common use cases. Annual subscriptions, prepaid insurance, annual licence fees, prepaid rent, deferred set-up fees, multi-period support contracts.