Posting profiles, posting definitions and the subledger journal — how the same architecture produces vouchers through a new validation layer
How AX 2012 posting profiles, posting definitions, inventory posting setup and the operational-event-to-voucher pipeline map onto D365 — identity-mapped in structure, but with a subledger journal-entry reconciliation layer that changes timing and traceability, and a fully worked purchase-receipt and sales-invoice example traced end to end.
What you will be able to do
Distinguish identity-mapped posting-profile configuration from configuration that demands reconciliation after upgrade
Explain how the operational event becomes an accounting intent becomes a voucher in both AX 2012 and D365, and identify where the subledger journal-entry layer adds a validation and timing difference
Trace a purchase receipt and a sales invoice end to end from operational document to GeneralJournalAccountEntry, with resolved accounts shown
Describe posting definitions and when they apply versus standard posting profiles
State and prove the reconciliation invariant: subledger balances must explain the control-account balance
Introduction
AX 2012's posting profiles are the bridge between operational events and the general ledger. When a purchase order is product-receipted, when a sales invoice is posted, when a production order reports as finished — the posting-profile configuration determines which main accounts receive the debit and credit, and which financial…
Posting profiles per subledger: the identity-mapped estate
Each subledger module has its own posting-profile surface. The following table summarises the full estate and its upgrade treatment.
Posting definitions: the rule-based supplement
Posting definitions (PostingDefinition) are a specialised feature that generates additional ledger entries when a source posting meets defined match criteria. They are not a replacement for posting profiles — they are a supplement used for specific scenarios:
The operational-event-to-voucher pipeline
The journey from an operational event (a goods receipt, a sales invoice, a journal entry) to a GL voucher follows the same logical sequence in both systems. The difference is that D365 inserts an explicit, enforceable validation layer in the middle.
Worked example: purchase receipt end to end
This example traces a goods receipt for 200 units of a stocked item at standard cost EUR 10.00 per unit through both systems.
Worked example: sales invoice end to end
```text Source data Customer: CUST-500 Customer group: DOMESTIC Item: FG-100 Item group: FNGDS (Finished Goods) Quantity: 50 Unit price: EUR 40.00 Line amount: EUR 2,000.00 Line discount: EUR 100.00
Where AX 2012 posting configuration is identity-mapped and where it must be reconciled
[!IMPORTANT] "Identity-mapped" means the configuration object carries forward unchanged in the data upgrade. It does not mean "no work." Every posting family requires sandbox validation: post representative transactions, compare the resulting voucher to the equivalent AX 2012 posting, and confirm that accounts, amounts, dimensions and…
The reconciliation invariant
The invariant is simple: subledger balances must explain the GL control-account balance. Specifically:
Knowledge check
Summary
AX 2012 posting profiles are genuinely identity-mapped in the upgrade. Customer, vendor, inventory, fixed-asset, bank, tax, project and production posting configurations all carry forward under the same names, with the same resolution logic, to the same main accounts.