Posting profiles in Dynamics 365 Finance

A posting profile in Dynamics 365 Finance is a configuration object that tells the system which GL accounts to use when a sub-ledger transaction posts. Sub-ledgers (customers, vendors, fixed assets, inventory, sales tax, banks, projects) all have posting profiles. They're how F&O bridges the operational world of invoices, receipts, and shipments to the accounting world of double-entry GL.

The pattern

Each sub-ledger has a default posting profile, plus the ability to attach more specific profiles to groups or individual records. For customers, for example, you might have a default profile pointing AR control to GL 1500-Receivables, an export-customer profile pointing AR control to 1510-Export Receivables, and an inter-company profile pointing AR control to 1520-IC Receivables. F&O picks the most specific match at posting time.

What's in a profile

A vendor posting profile names the GL accounts for:

• Summary account (AP control)
• Settlement account (where settlements net)
• Liability for discount
• Arrival account (goods received not invoiced)
• Charges accounts
• And more, depending on the modules in use.

Why it matters

Posting profiles are the single biggest source of GL posting errors after dimensions. A miscoded posting profile sends thousands of transactions to the wrong account, often only discovered at period-end when the trial balance won't reconcile. Mass-correcting requires either reversing and reposting transactions or running a reclassification journal — both are heavy operations.

Group versus specific

Posting profiles default at the group level (Customer Group, Vendor Group, Item Group, Bank Group). Resist the urge to override at the individual record level — it scatters configuration and makes auditing nearly impossible. Define groups for every meaningful classification, attach profiles at the group, and override at the record only when there's an explicit, defensible reason.

Currency and dimensions

Profiles can vary by currency (e.g. AR for EUR customers vs SEK customers) and can carry default dimension values that propagate to posted entries.

Audit

Every GL transaction stores a reference back to the source document, so auditors can trace from a GL line to the originating sub-ledger transaction and to the profile that mapped them. Reverse drill is one of the most-used troubleshooting tools.

Design discipline

Map out the posting profile design as part of CoA design, not as an afterthought. Two days early saves two weeks late.