Translating Automatic Journals and Accounting Codes into posting profiles

How Sage X3's Automatic Journal engine — SIHI, PIHI, STK, STKREVAL, MFG/WIP and supporting families, resolved through Accounting Codes, Dimension Types and Allocation Keys — is decomposed into D365 posting profiles surface by surface, with two fully traced worked examples and the reconciliation invariant that proves the translation is complete.

What you will be able to do

• Explain what an Automatic Journal is, how it resolves accounts at posting time, and what role Accounting Codes, Dimension Types and Allocation Keys play in the resolution
• Inventory the full Automatic Journal estate and classify every rule by its D365 posting-profile target surface
• Map each of the 29 posting-rule entries to its correct D365 configuration surface
• Trace a stock receipt and a customer invoice end to end through both systems
• Identify rules that have no posting-profile home and design the correct D365 mechanism for each
• Apply the reconciliation invariant — subledger balances must explain the control-account balance — and describe the proof method

Introduction

The Automatic Journal engine is the centre of Sage X3's accounting architecture. When an operational document is posted — a customer invoice, a stock receipt, a production completion, a payment — the system does not ask the user which accounts to debit and credit.

Anatomy of an Automatic Journal

An Automatic Journal in X3 is a named posting template — identified by a journal code (such as SIHI for customer invoices, PIHI for supplier invoices, STK for stock movements) — that defines the accounting entries to be created when a specific operational event occurs.

Inventorying the Automatic Journal estate

The Automatic Journal estate is the source-of-truth for how X3 generates accounting entries. Missing a rule means missing the logic that generated a category of postings — those postings will either fail in D365 or post to the wrong account.

The D365 posting-profile framework surface by surface

The customer posting profile determines the AR control account (summary account) and related accounts for customer transactions. In X3, this is the SIHI Automatic Journal's AR control line, resolved through customer Accounting Codes.

Worked example: stock receipt end to end

This example traces a purchase order receipt for 200 units of a raw material at standard cost 25.00 per unit through both systems.

Worked example: customer invoice end to end

This example traces a sales invoice for 50 units of a finished product at 80.00 per unit with a 5% line discount through both systems.

Rules without a posting-profile home

Not every Automatic Journal rule maps to a D365 posting profile. The following categories require alternative mechanisms:

The reconciliation invariant

The posting-profile translation is complete if and only if: the sum of each subledger's open balance equals its corresponding control-account balance in the general ledger. Total open AR must equal the AR summary account balance; total open AP must equal the AP summary account; total inventory value must equal inventory control accounts;

Knowledge check

Summary

The Automatic Journal estate is the heart of Sage X3's accounting system. Translating it into D365 posting profiles is a functional redesign exercise — not a data migration — that requires understanding the resolution logic, decomposing it across multiple D365 surfaces, and proving the result through the reconciliation invariant.