Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Accruals and Deferrals in Your ERP: Automating Year-End Closing Entries

Automate accrued expenses, prepaid expenses and deferred revenue in your ERP: GR/IR, contracts, reversals, SAP, Odoo, Sage X3 and Business Central setup.

Accruals and Deferrals in Your ERP: Automating Year-End Closing Entries

Three days after the year-end close begins, a spreadsheet is going around between accounts payable, procurement and financial controlling. It lists goods received but not yet invoiced, subscriptions paid in advance, and contracts billed over several years. Every line is keyed in by hand, every amount is debated, and the final journal entry is posted in one go, then reversed by hand in January, when someone remembers.

That file is the weakest link of the close. Accrual and deferral entries (accrued expenses, prepaid expenses, deferred revenue) often involve large amounts, they are among the first items an auditor tests, and yet they can be calculated from data your ERP already holds: receipts, purchase orders, contracts and amortization schedules.

This article shows how to move from the spreadsheet to entries that the ERP generates and reverses itself. It complements our guides on continuous close and on year-end configuration, which do not cover accrual accounting itself.

The four year-end adjustments and what auditors expect

The underlying principle is the accruals (matching) concept: an expense or a revenue belongs to the period in which the triggering event takes place (delivery, service rendered), not to the period in which the invoice arrives or the payment leaves. Four entries put this principle into practice. The account numbers below follow the French chart of accounts (PCG); your local chart will use different codes, but the logic is the same under IFRS and most local GAAP, as the closing reference sheets show:

AdjustmentMeaningPCG accountEffect
Accrued expenses (FNP in French: invoices not yet received)Expense of the period, invoice received later408 (suppliers, invoices not yet received)Expense added, liability on the balance sheet
Accrued income (FAE: invoices to be issued)Revenue of the period, invoice issued later418 (customers, revenue not yet invoiced)Revenue added, receivable on the asset side
Prepaid expenses (CCA)Expense paid or invoiced, relating to the next period486Expense removed, prepayment asset
Deferred revenue (PCA)Revenue invoiced, relating to the next period487Revenue removed, deferred income liability

What an auditor expects boils down to three points:

  • Completeness: every receipt and every service rendered before the closing date is in the books, whether invoiced or not.
  • Support: every adjustment line ties back to a source document (goods receipt, contract, amortization schedule), not to an amount typed in without a trace.
  • Consistency from year to year: same valuation methods, systematic reversal at opening, no adjustment dragging on from one year to the next.

A properly configured ERP delivers all three: the source document is linked to the entry, the method is coded once, and the reversal is automatic.

Feeding accruals from the ERP: goods received not invoiced

The GR/IR clearing account

In a standard procure-to-pay flow, a goods receipt generates an entry: debit inventory or expense, credit a clearing account (called GR/IR at SAP). When the invoice arrives, the clearing account is cleared against the supplier payable. At closing, the balance left on that account represents exactly the receipts not yet invoiced: it is the basis for your accrued expenses. The mechanism is detailed in our article on three-way match and GR/IR discrepancies.

The same account also holds items that are not accruals: invoices received without a receipt (which are posted the other way round), and receipts that will never be invoiced because the order is de facto closed. Before taking the clearing account balance as your accrual, you have to clean it up. Without that step you count twice: once as an accrual, once in an invoice that has already been entered.

SAP provides program F.19 for this: it analyzes the GR/IR accounts at a key date and generates adjustment entries, automatically reversed on the first working day of the following period. Other ERPs offer equivalent reports (goods received not invoiced) from which the entry can be generated.

Services without a receipt

Services (consulting, maintenance, temp labor, fees) do not go through a physical goods receipt. If nobody enters a service receipt, the ERP sees nothing and the expense vanishes from the P&L. Three approaches work together:

  • Mandatory service entry on service orders above a threshold, entered by the requester rather than by procurement.
  • Commitments derived from contracts: a recurring service (monthly maintenance) generates an automatic accrual from the schedule, with no manual input.
  • Confirmation campaign: at year-end, the ERP lists open service orders (ordered, not invoiced) and sends requesters a progress confirmation request. Their reply creates the accrual.

The last approach remains manual in substance, but the ERP carries the list, the reminders and the trail. That is already a clear gain over the spreadsheet.

Valuing at the right price

An accrual must be valued at what the invoice will be, not at what you hope it will be. Two price sources are possible:

  • The purchase order price, used by default: it is how the receipt is valued in the ERP, so it is the most traceable.
  • The last known price, if the order price is out of date (contractual indexation, revised material price). This rule needs a control, because it creates a gap with inventory valuation.

In both cases, document the rule and keep it from one year to the next. The gap between the accrued amount and the final invoice should stay small and be analyzed in January: a recurring gap in the same direction signals a valuation bias.

Automatic reversal on day one

An accrual is a provisional entry: on the first day of the following fiscal year it is cancelled, then the actual invoice is posted normally in the new year. This is the reversal method. It spares you from tracking line by line which accruals have been invoiced.

Reversal is a native function to verify in your ERP: in Business Central, for example, recurring journals using the “reversing” method post the opposite entry the day after the posting date. In Odoo, deferral entries are reversed on the first day of the following month.

The control rule: no adjustment entry without a reversal date, except prepaid and deferred items tracked by schedule. A forgotten reversal doubles the expense in the following year, and the defect only shows up in analytical review.

Deferred revenue: subscriptions, maintenance, multi-year contracts

An annual subscription invoiced in November for twelve months is not revenue of the invoicing year alone: the part relating to the following year is deferred revenue (account 487), a liability, because the company still owes the service to the customer, as the reference sheets on account 487 remind us.

Typical cases are software subscriptions, maintenance contracts invoiced in advance, multi-year licenses and service packages. The calculation is a pro rata temporis: amount invoiced × (days remaining after the closing date ÷ days in the invoiced period).

Modern ERPs no longer require you to compute this by hand. Odoo’s deferred revenue schedule spreads the invoice amount over several periods, and Business Central offers deferral templates that place the amount on a deferral account when the invoice is posted, then release it to revenue month by month.

Deferred revenue is an accounting adjustment, not a revenue recognition analysis. As soon as a contract contains several performance obligations (license, implementation, support), the question goes beyond pro rata: you must determine when each component becomes revenue. For groups reporting under IFRS, that analysis falls under IFRS 15 (see our article on rebate management and IFRS 15 for an ERP-side example). For an SME under local GAAP, pro rata temporis is enough for most simple subscriptions, but mixed contracts demand the same discipline: one contract, one schedule, one documented rule.

Prepaid expenses: insurance, rent, SaaS licenses

The mirror logic applies to purchases. An annual insurance premium paid in October, December’s rent paid for January, a SaaS subscription paid for twelve months starting 1 November: the part belonging to the following year is a prepaid expense (account 486), an asset.

In the ERP there are two ways to handle it:

  • At invoice entry: a deferral code is attached to the line (Business Central, Odoo). The ERP then spreads the expense over the contract term, with no closing intervention. This is the most robust method.
  • At closing, through a report listing invoices whose service period runs past the closing date. More fragile: it depends on every line carrying a service start and end date.

In both cases, data quality comes first. An invoice entered without a service period cannot be adjusted automatically. The design of the invoice line (mandatory start and end dates for the relevant expense accounts) is set during configuration, together with the chart of accounts: a “subscription” type expense account should trigger the period field.

Configuration by ERP: native functions or add-ons

The points below should be validated with your integrator, as coverage depends on the version, the French localization and the modules activated.

NeedSAP (S/4HANA)OdooSage X3Dynamics 365 BC
Accruals on goods received not invoicedNative: GR/IR account, program F.19 with automatic reversalNative through inventory accounting; reports to be completed depending on configurationTo check with the integrator: uninvoiced receipt reports and adjustment entries depending on setupPartly native: uninvoiced receipts, adjustment entry via reversing recurring journal
Accruals on services without a receiptService entry sheet, module to activateManual entry or automation ruleTo be scoped in the projectGeneral journal with reversal, or add-on
Prepaid expenses on supplier invoicesNative (deferral entry) or add-on depending on versionNative: deferred expenses with reversalTo check with the integratorNative: deferral templates on purchase invoices
Deferred revenue on subscriptions and maintenanceNative or billing module (RAR / contracts) depending on versionNative: deferred revenuesTo check with the integratorNative: deferral templates on sales invoices; contract deferrals in the service module
Automatic reversalNative on F.19 adjustment entriesNative on deferral entriesDepends on the journal function; to validateRecurring journals with reversing method

The Sage X3 column is deliberately cautious: coverage of accrual entries varies by version, French localization and the add-ons of the publisher or integrator. Ask the question at scoping stage: who generates the entry, who reverses it, from which source document?

Controls: reconciliation, variance review, audit trail

Automation moves the controls, it does not remove them. Four checks close the loop.

  1. Subledger to general ledger reconciliation. The balance of account 408 must equal the sum of the accruals listed in the source report. The same logic applies to 486 and 487 with their schedules. A gap points to a manual entry that bypassed the process.
  2. Valuation variance review. In January, compare reversed accruals with the invoices actually received. A significant price gap or an accrual that was never invoiced gets analyzed.
  3. Analytical review. The year’s adjustments are compared with the prior year’s, line by line, with variances explained.
  4. Audit trail. Every entry carries its source document (receipt, contract, schedule), its author (user or automated job) and its reversal date. That is what the auditor will ask for, and what a consistent audit file (the FEC in France, see the annual close checklist) requires.

Common mistakes

  • Double-counting accruals: the invoice is entered before closing, but the accrual coming from the receipt is not cleared. The clearing account then holds a balance that is not one.
  • Forgotten reversal: the expense is counted twice, in year N (accrual) and in N+1 (invoice).
  • Deferred revenue not calculated pro rata temporis: taking one twelfth per whole month when the service starts mid-month, or ignoring the actual start date.
  • Prepaid expense without a service period: the invoice is booked entirely as expense because the period field was not filled in.
  • Manual end-of-period adjustment with no link to the source document, impossible to reconcile afterwards.

A worked example (fictional, for illustration)

The figures below are invented to show the mechanism. They do not reflect any real company.

A company with a calendar fiscal year closes on 31 December. Three situations:

  • Accrual: a €12,000 delivery of components is received on 28 December, and the invoice arrives on 9 January. On 31 December the ERP generates: expense €12,000, credit 408. On 1 January, automatic reversal. On 9 January, the invoice is posted normally.
  • Prepaid expense: a €24,000 SaaS license is invoiced on 1 November for twelve months. At 31 December, two months are consumed: €4,000 remains as an expense of the year, €20,000 is booked as a prepaid expense (account 486) and released in N+1.
  • Deferred revenue: an €18,000 maintenance contract is invoiced on 1 October for twelve months. At 31 December, three months are consumed: €4,500 is revenue of the year, €13,500 is deferred revenue (account 487).

With the schedule from a deferral template, the last two entries are created when the invoice is posted. The close then only has to check that the balance of 486 and 487 equals the sum of the schedules still running.

Typical annual close calendar (D+1 to D+15) and responsibilities

This calendar is a starting point to adapt to your statutory deadlines and your organization.

DayActionOwner
D+1Receipts freeze and procurement period block; run the goods-received-not-invoiced reportProcurement, accounts payable
D+1 to D+3Clearing account cleanup, accrual generation with reversal, service confirmation campaignAccounts payable, requesters
D+3 to D+5Generate prepaid and deferred entries from schedules; check contracts without a periodGeneral accounting, billing
D+5 to D+8Reconcile 408, 486 and 487 with source reports; variance reviewChief accountant
D+8 to D+10Analytical review of adjustments year over year, ruling on special casesFinancial controller
D+10 to D+12Validation, entry lock, audit trail file assemblyCFO, chief accountant
D+12 to D+15FEC export, hand-over to the auditor, check that reversal is scheduled for D+1 of the next fiscal yearChief accountant

Going further

To fit these adjustments into a broader close, read our continuous close guide and the year-end configuration checklist. To receive our next guides on closing and accounting compliance, subscribe to the newsletter.