Redistributing Subledger Accounting into posting profiles

Translate the R12 SLA and Accounting Methods Builder rule stack into D365 vendor, customer, inventory, asset and project posting profiles plus dimension defaulting, and prove the result with a replay rather than a configuration comparison.

What you will be able to do

Introduction

This is the largest single design workstream on the path, and the source package treats it as such: the playbook gives it its own section as the dominant pre-wave workstream, ahead of the eight-wave load plan.

Required outputs before anything loads

The playbook specifies four outputs from this workstream, and they are worth quoting as a checklist because they define what "the crosswalk" actually is:

The thirteen canonical posting rules

The source package identifies thirteen posting rules that any EBS programme must resolve. Nine are mapped; four are partial, meaning the pattern is understood but the estate-specific answer depends on discovery.

Payables: one liability, four offset classes

The AP invoice rule looks like the simplest in the set and is not. The liability side is straightforward — a vendor posting profile supplies the summary account, scoped by whatever grouping the target design chose. The offset side is where the work lives.

Receivables: do not collapse AutoInvoice

The AR invoice rule carries the sharpest instruction in the whole rule set: do not collapse AutoInvoice line-type differences into one rule.

Procurement and inventory

The PO receipt accrual rule carries one instruction — model perpetual versus period-end accrual explicitly — and it is the instruction that most often gets skipped, because the source behaviour feels like an implementation detail.

Assets and projects

Fixed asset posting is the closest family in the set. Additions map onto acquisition posting through the asset group and book; depreciation maps onto depreciation posting the same way. Two caveats attach.

The dimension-sourcing policy

This is the output that teams most often skip, and it is the one that determines whether the target's reporting matches the source's.

Proving it: replay, not comparison

The final output is evidence, and there is only one form of evidence that counts.

Knowledge check

Summary

R12 Subledger Accounting concentrates account derivation in one configurable layer. D365 distributes the same intent across vendor, customer, inventory, asset and project posting configuration, plus tax, plus dimension defaulting.