Understand how Workday resolves an operational event to a ledger account through Account Posting Rule Sets and Journal Sources, and translate that logic into D365's distributed posting-profile framework — including a fully worked supplier invoice example.
Workday's Account Posting Rule Set is the mechanism that decides, at the moment a business process reaches its Final Action step, which Ledger Account each transactional line posts to. It is the bridge between the operational world — a supplier invoice, an expense report, a cash receipt — and the accounting ledger.
A Workday Account Posting Rule Set is a named collection of rules, each of which maps an (event-type, Worktag-bundle) combination to a Ledger Account within a specified Account Set.
The canonical model names the source fact OperationalEvent: a Customer Invoice, Supplier Invoice, Expense Report, Procurement Requisition, Manual Journal, Cash Receipt, Payment, Inventory Adjustment or Project Transaction.
Worked example: a Workday Settlement Run closes three customer invoices and one payment in a batch. D365 will post or import the payment journal, then settlement links the payment to each CustTrans record.
A Workday Customer Invoice line has Company UK01, Book Corporate, Customer C-4480, Ledger Account 4000, Revenue Category Consulting, Region EMEA and Tax Code UK-STD. The Account Posting Rule Set resolves the event into three intents: recognise consulting revenue, debit AR control and post VAT output.
Workday's Account Posting Rule Sets consolidate operational-to-accounting account resolution in a small number of named, Worktag-aware rule surfaces. D365 distributes the same logic across CustPostingProfile, VendPostingProfile, InventPosting, ProjPosting, AssetPosting, Sales Tax setup, and Expense Management category posting.