Turn Acumatica's account determination — customer and vendor classes, inventory posting classes, tax zones and account and subaccount masks — into D365 posting profiles, inventory posting setup and dimension defaulting, and prove the result by replay rather than by comparison.
The Finance module decided what accounts and dimensions exist. This module decides how transactions find them.
Six layers can influence the account and the segment values on a posted entry. Understanding the layering is what makes the decomposition tractable.
The source package identifies ten posting rules that an Acumatica programme must resolve. Seven are rated high confidence and three are rated medium — and the three medium ones are precisely the areas the adapter flags as tenant-specific.
Rules 1 and 2 look like the easiest in the set and they contain a trap worth naming.
Rules 3 and 4 cover stock, cost of goods sold and revenue, and the posting-rules note for rule 3 is unusually blunt: posting class plus mask design is a major target-configuration workstream.
Rules 6, 7 and 9 are the high-confidence, lower-drama part of the set, which does not make them small.
Rule 8 has no independent answer. It is the accounting consequence of the classification made in the Organisational Modelling module, and there are exactly two outcomes.
The method that produces a defensible crosswalk has five steps and only the last one is convincing.
Acumatica decides accounts through classes and masks; D365 decides them through posting profiles, inventory posting setup, tax configuration and dimension defaulting. One source rule routinely becomes several target objects, and the mask layer in particular splits into a defaulting half and a validation half that are configured in…