6.3 Ledger Settlements Configuration & Processing

6.3 Ledger Settlements Configuration & Processing

Quick Summary: While Accounts Payable and Accounts Receivable provide robust subledger invoice-to-payment settlement engines, organizations also require internal reconciliation within General Ledger balance sheet clearing accounts. Ledger Settlements (General ledger > Periodic tasks > Ledger settlements) provides a specialized mechanism to match, clear, and reconcile debit and credit entries within designated main accounts—such as Goods Received / Invoice Received (GR/IR) clearing, payroll clearing, intercompany in-transit clearing, and tax clearing. Through automated Process Automation rules, Financial Tags, and Year-End Close Awareness, Dynamics 365 Finance streamlines balance sheet clearing reconciliations.

---

1. Purpose & Fundamentals of Ledger Settlements

In standard enterprise accounting, various operational workflows generate temporary timing differences that reside in balance sheet clearing or suspense accounts before final resolution.

+---------------------------------------------------------------------------------------------------+
|                         Subledger Settlements vs. General Ledger Settlements                      |
+---------------------------------------------------------------------------------------------------+
|  Attribute             | Subledger Settlements (AP / AR)   | General Ledger Settlements           |
|  --------------------- | --------------------------------- | ------------------------------------ |
|  **Module Domain**     | Accounts Payable / Receivable     | General Ledger                       |
|  **Record Types**      | CustTrans / VendTrans             | GeneralJournalAccountEntry           |
|  **Core Purpose**      | Settle customer/vendor invoices   | Clear internal offsetting debit/     |
|                        | against payments/credit notes.    | credit lines within a Main Account.  |
|  **Subledger Impact**  | Updates open balances, aging.     | Zero subledger impact (GL only).     |
|  **Gain/Loss Realize** | Realizes FX gain/loss & discounts | Does not calculate realized FX.      |
|  **Reconciliation**    | AP/AR Subledger to GL Control.    | Internal Main Account Clearing.      |
+---------------------------------------------------------------------------------------------------+

Primary Business Use Cases for Ledger Settlements

1. Goods Received Not Invoiced (GR/IR) / Purchase Order Accrual (Account 200140):

   • Physical PO product receipt posts: Debit Inventory (130100) / Credit PO Accrual (200140).
   • Financial PO vendor invoice posts: Debit PO Accrual (200140) / Credit Accounts Payable (210100).
   • Ledger settlement pairs the credit from the product receipt with the debit from the vendor invoice, clearing both lines and leaving only un-invoiced receipts visible.

2. Payroll Clearing (Account 210300):

   • Payroll run accrual posts gross salaries: Debit Salary Expense (610100) / Credit Payroll Clearing (210300).
   • Bank payroll disbursement posts: Debit Payroll Clearing (210300) / Credit Operating Bank (110110).
   • Ledger settlement clears the net pay disbursement against the payroll accrual batch.

3. Sales Tax Clearing / VAT Bridge Accounts (Account 220200):

   • Periodic tax settlements move calculated tax balances into a tax bridge account pending government remittance.
   • When the wire payment to the tax authority clears the bank, the bridge account is settled.

4. Intercompany In-Transit Suspense Accounts:

   • Clearing intercompany inventory shipments in transit between dispatch and receipt confirmations.

---

2. Configuring Ledger Settlements & Main Account Selection

To enable main accounts for ledger settlement, navigate to General ledger > Ledger setup > Ledger settlements.

+---------------------------------------------------------------------------------------------------+
|                             Ledger Settlement Configuration Form                                  |
+---------------------------------------------------------------------------------------------------+
|  Main Account | Account Name                      | Financial Tags Enabled                        |
|  ------------ | --------------------------------- | --------------------------------------------- |
|  `200140`     | Purchase Accrual (GR/IR)          | `PurchaseOrderNumber`, `ItemNumber`           |
|  `210300`     | Payroll Clearing                  | `EmployeeID`, `PayPeriod`                     |
|  `220200`     | Sales Tax Settlement Clearing     | `TaxAuthority`, `TaxPeriod`                   |
|  `130900`     | Inventory In-Transit Suspense     | `TransferOrderNumber`                         |
+---------------------------------------------------------------------------------------------------+

Main Account Selection Governance

[!CAUTION] Consultant Best Practice: Only assign balance sheet clearing, transit, and suspense accounts to the Ledger Settlements setup. Never enable Ledger Settlement on:

• AP / AR Trade Summary Control Accounts (210100, 120100): These must be settled exclusively through AP/AR subledger settlement. Attempting to settle subledger control accounts via GL ledger settlement causes discrepancies and breaks reconciliation.
• High-Volume P&L Accounts: Revenue and expense accounts are closed to Retained Earnings during year-end close and do not maintain ongoing balance clearing logic.

Leveraging Financial Tags (FinTags) for Precision Matching

Financial Tags provide a lightweight, high-performance mechanism to track operational transaction identifiers (such as Purchase Order numbers, Sales Order numbers, or Employee IDs) directly on General Ledger journal entries without creating heavy Financial Dimension records. When configuring Ledger Settlements, consultants can activate specific Financial Tags to be displayed on the settlement workspace and used as matching criteria in automated settlement rules.

---

3. Manual Ledger Settlement Execution

When processing manual settlements (General ledger > Periodic tasks > Ledger settlements):

+---------------------------------------------------------------------------------------------------+
|                                 Manual Ledger Settlement Workspace                                |
+---------------------------------------------------------------------------------------------------+
|  Filter: Main Account = 200140 (Purchase Accrual) | Date: 01/01/2026..08/31/2026                  |
|                                                                                                   |
|  Mark | Date       | Voucher      | Text / Reference      | FinTag: PO# | Debit       | Credit        |
|  ---- | ---------- | ------------ | --------------------- | ----------- | ----------- | ------------- |
|  [X]  | 08/12/2026 | `PO-REC-101` | PO 9042 Product Rcpt  | `PO-9042`   |             | $14,500.00    |
|  [X]  | 08/18/2026 | `AP-INV-882` | PO 9042 Vend Invoice  | `PO-9042`   | $14,500.00  |               |
|  [ ]  | 08/24/2026 | `PO-REC-105` | PO 9048 Product Rcpt  | `PO-9048`   |             |  $8,200.00    |
|                                                                                                   |
|  Selected Total: Debit = $14,500.00 | Credit = $14,500.00 | Difference = $0.00                     |
|  Action: [ Settle Marked Transactions ]                                                           |
+---------------------------------------------------------------------------------------------------+

Processing Steps

1. Select the Main account to settle from the dropdown.
2. Filter by Posting date, Transaction currency, or Financial Tag.
3. Check the Mark box next to corresponding debit and credit transaction lines.
4. Verify that the Difference indicator at the bottom of the form equals 0.00.
5. Click Settle marked transactions.
6. The settled transactions immediately move from the Unsettled transactions grid to the Settled transactions history tab.

Reversing / Canceling Settlements

If an accountant accidentally settles mismatched records (e.g., matching PO 9042 invoice to PO 9048 receipt):

1. Navigate to the Settled transactions tab.
2. Select the settled transaction group.
3. Click Reverse marked transactions / Cancel settlement.
4. Both lines immediately return to the active Unsettled transactions list for re-matching.

---

4. Advanced Automated Ledger Settlement Rules

To eliminate manual clearing overhead in high-volume environments, Dynamics 365 Finance integrates Ledger Settlements with the Process Automation framework (General ledger > Ledger setup > Ledger settlements > Automation rules).

+---------------------------------------------------------------------------------------------------------+
|                                Automated Ledger Settlement Rule Architecture                            |
+---------------------------------------------------------------------------------------------------------+
|  RULE CONFIGURATION: GR/IR Matching Rule                                                                |
|  - Target Main Account: `200140` (Purchase Accrual)                                                     |
|  - Execution Schedule: Nightly Batch (02:00 AM)                                                         |
|                                                                                                         |
|  MATCHING CRITERIA MATRIX (All Selected Criteria Must Match Simultaneously):                            |
|  +---------------------------------------------------------------------------------------------------+  |
|  | 1. Transaction Amount:     Debit Amount == Credit Amount (in Transaction or Accounting Currency)   |  |
|  | 2. Financial Tag:          Financial Tag `PurchaseOrderNum` matches exactly on Debit and Credit   |  |
|  | 3. Posting Date Tolerance: Invoice date within +/- 30 days of Product Receipt date                |  |
|  | 4. Currency:               Transaction Currency matches exactly (e.g., USD == USD)                |  |
|  +---------------------------------------------------------------------------------------------------+  |
|                                                                                                         |
|  Automated Batch Run -> Evaluates Open GL Lines -> Pairs Exact Matches -> Posts Settlement Timestamp    |
+---------------------------------------------------------------------------------------------------------+

Configuring Automated Process Rules

1. In the Ledger settlements setup form, click Automation rules.
2. Click New and define the rule parameters:
   • Rule name: e.g., AutoSettle_GRIR.
   • Main accounts: Select 200140.
   • Match criteria toggles:
     • Amount: Mandatory.
     • Financial tags: Select active tags (e.g., PONumber).
     • Posting date: Set allowable date difference threshold (e.g., within 30 days).
3. Navigate to System administration > Setup > Process automations and initialize the Ledger settlement process automation background batch series.

---

5. Critical Interaction: Ledger Settlements and Year-End Close

A historically complex area of General Ledger architecture is the interaction between Ledger Settlements and the periodic Year-End Close.

+---------------------------------------------------------------------------------------------------------+
|                         Year-End Close: Traditional vs. Settlement-Aware Model                          |
+---------------------------------------------------------------------------------------------------------+
|  TRADITIONAL YEAR-END CLOSE (Legacy Flaw):                                                              |
|  - All transactions in Balance Sheet accounts were compressed into a single Opening Balance row.       |
|  - Original voucher IDs, transaction dates, and line references were lost in Year 2.                    |
|  - Consequence: Unsettled 2025 receipts could NOT be matched against 2026 invoices in detail!          |
|                                                                                                         |
|  MODERN "AWARENESS BETWEEN LEDGER SETTLEMENT AND YEAR-END CLOSE" (Active Standard):                     |
|  - SETTLED TRANSACTIONS: Summarized into net opening balance (saving DB space and query performance).    |
|  - UNSETTLED TRANSACTIONS: Brought forward IN DETAIL to Period 0 of the new fiscal year.               |
|  - Consequence: Original Voucher `PO-REC-101` from Dec 2025 remains individually open in Jan 2026,      |
|    enabling seamless cross-year settlement against Jan 2026 invoice `AP-INV-882`!                       |
+---------------------------------------------------------------------------------------------------------+

Key Prerequisites for Year-End Close Awareness

• The feature "Awareness between ledger settlement and year-end close" must be enabled in Feature Management.
• Before executing the final Year-End Close run (General ledger > Period close > Year end close), all known matching pairs in the closing year should be settled.
• If a settlement performed in Year 1 needs to be reversed after Year-End Close has already completed, the user must un-close / re-run the Year-End Close for that fiscal year to recalculate opening detailed balances properly.

---

6. Comprehensive Implementation Best Practices

1. Always Use Financial Tags for Non-Subledger Tracking: When tracking PO numbers or project references in general journals for clearing purposes, use Financial Tags rather than creating custom financial dimensions to prevent dimension combination table explosion.
2. Run Automated Rules Prior to Period-End Close: Schedule automated settlement batch jobs to run daily or weekly so that accounting teams only need to manually investigate true exception outliers during month-end close.
3. Isolate Currency Differences: If settling cross-currency transactions within GL clearing accounts, ensure that any rounding or timing variance is journalized before marking transactions, as GL ledger settlements do not auto-post FX gain/loss adjustments.