Business Central Setup for IFRS 16 - Part 3: Chart of Accounts, Posting Groups & Leasing Parameters

Part 1 introduced IFRS 16 and the core concepts: ROU Asset, Lease Liability, discount rate, and lease term.

Part 2 walked through the accounting Mechanics: Initial recognition, subsequent measurement, and the journal entries behind them.

Posts 1 and 2 covered the accounting, what IFRS 16 requires and how the numbers work. This post is how to configure Dynamics 365 Business Central so that the Asset Leasing module is ready to receive leases and produce correct journals.

A note on architecture before we begin. In our recommended setup, every ROU lease creates a Fixed Asset record in Business Central.

The FA Card is the master record for the asset side, and the Lease Card sits as an extension that adds the lease-specific economics (IBR, payment schedule, modification fields). This approach leverages BC’s native Fixed Asset engine for depreciation, keeps ROU assets visible in standard FA reports alongside owned assets, and creates a cleaner audit trail. The setup steps below reflect that architecture.

Setups & Configurations:

1. Asset Leasing Setup:

Configure the number series, journal templates and batches, rounding precision, and whether to allow multiple lease books.

2. Lease Book Setup:

The Lease Book setup supports multiple accounting frameworks simultaneously (e.g. IFRS and local GAAP). The Lease Book is linked to its corresponding FA Depreciation Book, keeping the asset and lease records aligned. Most organisations configure a single Lease Book and a matching FA Depreciation Book for IFRS reporting.

3. Lease posting groups:

Lease Posting Groups map transaction types to GL accounts. The key fields to configure are Lease Liability, Interest Expense and Gain or Loss on Modification.

4. Fixed Asset Setups:

Because each ROU lease is created as a Fixed Asset, the FA module must be configured first. Set up dedicated FA Classes, Subclasses, and FA Posting Groups for each type of ROU lease and map them to the corresponding acquisition and depreciation accounts.

5. Journal templates and batches:

Journal templates and batches let you set up dedicated journals for lease commencement, interest accrual, amortisation, modifications, and repayments. Separating journals this way keeps review, approval, and the audit trail much cleaner. ROU depreciation posts through the Fixed Asset G/L Journal, the same routine used for owned assets, so there is no parallel depreciation engine to maintain.

6. Chart of Accounts:

You need to configure lease-specific GL accounts and map them to the Lease Posting Groups and FA Posting Groups. Consider the numbering structure of your CoA and whether to use separate Lease Posting Groups for different asset classes (Property, Vehicles, Equipment).

Let’s walk through each configuration with an example.

1. Asset Leasing Setup:

The Asset Leasing Setup page controls organisation wide behaviour. These settings apply across all leases and all books.  Rounding precision addresses cumulative penny differences in NPV calculation within Lease schedules.

• Default Lease Book: Required for UK and international reporters. The Default Lease Book is applied to new Lease Cards unless overridden. If you need to maintain parallel books (e.g. IFRS + US GAAP for a subsidiary), enable Allow Multiple Lease Book and configure a separate book for ASC 842.

• Lease No. Series: Set up a dedicated number series for leases. A separate series keeps leases clearly identifiable in the GL and audit trail, distinct from the FA No. series.

• Rounding Precision: Mismatched rounding precision causes cumulative penny differences in amortisation schedules that are tedious to explain to auditors. Set this correctly before any leases are created.

• Journal Templates and Batches: Each row maps a lease event (Inception, Interest, Amortisation, Modification, Repayment) to a journal template and batch where BC will post entries. This gives auditors a clean, filterable audit trail. The templates and batches themselves must exist before they can be selected here (Refer Section 5).

• Automatic Posting: Automatic posting is faster but bypasses the review step. Turn this on only if warranted by your control environment.

2. Lease Book Setup:

A Lease Book in Business Central is an accounting policy container. It is selected on the Lease Schedule for each Lease Card and determines whether that schedule is recognised for accounting purposes. Most organisations configure a single IFRS 16 Lease Book and set it as the default on each Lease Card.

3. Lease Posting Group:

Lease Posting Groups bridge transaction types and GL accounts. Each posting group is assigned to a Lease Card, and BC uses it to determine which accounts to debit and credit for every journal it generates on the liability side. Asset side for ROU and amortization is driven by the FA Posting Group on the linked Fixed Asset.

4. Fixed Asset Setups:

In our recommended architecture, every ROU lease is created as a Fixed Asset in Business Central. The FA Card holds the asset identity, class, and depreciation book; the Lease Card is the extension that adds the lease-specific economics. This means the FA module must be configured for ROU assets before the Lease module is.

Standard BC requires the following configurations:

1. FA Depreciation Book aligned to the Lease Book

2. FA Classes for ROU

3. FA Subclasses for ROU

4. FA Posting Groups to map ROU and depreciation accounts

4A. FA Depreciation Book

Create at least one FA Depreciation Book that will be linked to the Lease Book. For most organisations, the default FA Depreciation Book (COMPANY) serves the purpose. Organisations with parallel GAAP requirements may need a second book (e.g. LOCAL-GAAP).

4B. FA Class for ROU

Create dedicated FA Classes for ROU assets, separate from owned-asset classes. This keeps the asset register clean and lets you filter reports for owned-vs-leased presentations.

4C. FA Sub class for ROU

Create FA Subclass for each FA Class.

4D. FA Posting Group for ROU

Each FA Class needs an FA Posting Group that tells BC which GL accounts to use for asset acquisition, depreciation, and disposal. Below is the recommended structure for a property-class ROU posting group.

5. Journal templates and batches:

Business Central uses journal templates and batches to organise the posting of lease journals. Setting these up deliberately, rather than using generic general ledger journals provides audit trails, better access controls and a clear month-end checklist.

Configure separate journal templates. One for the general lease-accounting entries (commencement, interest, amortisation, modification) and a separate one for processing recurring repayment entries.

6. Chart of Accounts:

IFRS 16 configuration requires new balance sheet and income statement lines that almost certainly do not exist in your current chart of accounts. The table below shows the minimum set of GL accounts required. Organisations with multiple lease classes (property, vehicles, IT equipment) should consider separate accounts per class to support disclosure.

The critical design decision is whether to use separate accounts per asset class. This is strongly recommended. It directly drives IFRS 16 disclosure note schedules without needing manual analysis at year-end.

→ Up next: Part 4 — configuring the Lease Card and payment schedule, and processing the journals in Business Central that account for IFRS 16 transactions through the full lease lifecycle.

📝 This post reflects the author's professional views, and is for informational purposes only. It does not constitute legal, financial, or accounting advice.