Study guide
10.2 Customer Posting Profiles & Account Code Precedence
Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MB-310 Exam Overview & Financial Architecture
1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework
2 Chapter 2: Chart of Accounts & Main Accounts
2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions
3 Chapter 3: Financial Dimensions & Account Structures
3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates
4 Chapter 4: Ledgers, Calendars & Currencies
4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles
5 Chapter 5: General Ledger Journals & Allocations
5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals
6 Chapter 6: Intercompany Accounting & Settlements
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing
7 Chapter 7: Cash and Bank Management
7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting
8 Chapter 8: Periodic Closing & Financial Consolidations
8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules
9 Chapter 9: Sales Tax & Withholding Tax
9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting
10 Chapter 10: Accounts Receivable Setup & Invoicing
10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts
11 Chapter 11: Credit Management & Collections
11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals
12 Chapter 12: Subscription Billing & Revenue Deferrals
12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)
13 Chapter 13: Accounts Payable & Invoice Processing
13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation
14 Chapter 14: Vendor Payments & Expense Management
14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses
15 Chapter 15: Budgeting & Budget Control
15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries
16 Chapter 16: Fixed Assets Configuration & Transactions
16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)
10.2 Customer Posting Profiles & Account Code Precedence
Key Takeaways Explain This Topic AI
A customer posting profile maps summary (control), settlement discount, interest, and write-off accounts for a set of customers.
Account code determines scope: Table applies to one customer, Group to a customer group, and All to every customer.
Dynamics 365 Finance resolves the posting profile in the order Table, then Group, then All — the most specific match wins.
A posting failure citing a missing summary account almost always means no posting profile rule covers that customer's group and no All rule exists.
Last updated: August 2026
10.2 Customer Posting Profiles & Account Code Precedence
Quick Summary: Customer posting profiles are the bridge from the Accounts receivable subledger to general ledger control accounts. This section covers the account types on a profile and the Table/Group/All precedence hierarchy that determines which rule applies.
1. Customer Posting Profiles & Control Account Framework
Customer Posting Profiles represent the primary financial configuration link between Accounts Receivable subledger operations and the General Ledger Chart of Accounts.
Navigation
Path: Accounts receivable > Setup > Customer posting profiles +---------------------------------------------------------------------------------------------+
- | Customer Posting Profile Anatomy: [ GEN - General ] |
- +---------------------------------------------------------------------------------------------+
- | Posting Profile Header: [ GEN ] Description: [ Standard General Receivables ] |
- +---------------------------------------------------------------------------------------------+
- | Setup FastTab (Control Accounts Grid): |
- | Account Code | Account / Group | Summary Account | Settle Account | Sales Tax Prepayments |
- | ------------ | --------------- | --------------- | -------------- | ---------------------- |
- | `Table` | `US-001` | `130105` | `130190` | `220150` |
- | `Group` | `10` | `130110` | `130190` | `220150` |
- | `Group` | `30` (Gov) | `130130` | `130190` | `220150` |
- | `All` | `*` | `130100` | `130190` | `220150` |
- +---------------------------------------------------------------------------------------------+
- | Additional Control Accounts (Side Columns): |
- | - Arrival: `130180` (Interim Receipts) - Write-off: `610500` (Bad Debt Expense) |
- | - Interest: `420100` (Finance Charges) - Collection Letter: `420200` (Admin Fees) |
- +---------------------------------------------------------------------------------------------+
- | Table Restrictions FastTab: |
- | - Settle: [ Auto ] - Cancel: [ Yes ] |
- +---------------------------------------------------------------------------------------------+
- Core Control Account Fields and Functional Accounting Impact
Control Account Field Normal Balance Accounting Trigger & Subledger Event General Ledger Posting Entry
Summary account Asset (Debit) Posted when an invoice (Sales Order or Free Text Invoice) is committed to the subledger. Debit: Accounts Receivable Summary ( 130100 ); Credit: Sales Revenue / Tax Payable
Settle account Balance Sheet Used as an interim clearing account during automatic settlement or cross-currency payment matching. Clears variance differences between open invoice vouchers and payment vouchers.
Sales tax prepayments Liability (Credit) Used when a prepayment invoice is posted prior to the final shipment of goods to record statutory sales tax liability on advance deposits. Credit: Sales Tax Prepayment Liability ( 220150 ); Debit: AR Prepayment Summary
Arrival account Asset (Debit) Used in advanced payment arrival workflows where cash is received at a lockbox prior to invoice matching. Debit: AR Arrival Clearing ( 130180 ); Credit: Cash / Bank
Write-off account Expense (Debit) Populates automatically during the Write-off routine in the Collections Workspace when bad debt is recognized. Debit: Bad Debt Expense ( 610500 ); Credit: AR Summary Control ( 130100 )
2. The Table / Group / All Account Code Precedence Hierarchy
In Dynamics 365 Finance posting setups, the posting engine evaluates rules according to the universal Account Code Precedence Hierarchy : Table > Group > All . +---------------------------------------------------------------------------------------------------------+
- | Account Code Hierarchy: Resolution Order |
- +---------------------------------------------------------------------------------------------------------+
- | |
- | 1. TABLE LEVEL (Highest Priority) |
- | Evaluates whether a specific rule exists for the exact Customer Account Number (e.g., US-001). |
- | -> MATCH FOUND? Use configured Summary Account (e.g., 130105). STOPS SEARCH. |
- | |
- | 2. GROUP LEVEL (Medium Priority) |
- | If no Table match, evaluates whether a rule exists for the Customer's Group (e.g., Group 10). |
- | -> MATCH FOUND? Use configured Summary Account (e.g., 130110). STOPS SEARCH. |
- | |
- | 3. ALL LEVEL (Lowest Priority / Universal Fallback) |
- | If neither Table nor Group matches, evaluates the universal 'All' rule (*). |
- | -> MATCH FOUND? Use configured Summary Account (e.g., 130100). |
- | -> NO MATCH FOUND? System halts with hard posting exception: "Posting profile does not exist". |
- +---------------------------------------------------------------------------------------------------------+
- Practical Example of Account Code Resolution
Assume the following Customer Posting Profile setup for profile GEN :
- Line 1: Table = US-001 -> Summary Account 130105 (Key Account AR)
- Line 2: Group = 10 -> Summary Account 130110 (Wholesale AR)
- Line 3: Group = 20 -> Summary Account 130120 (Retail AR)
- Line 4: All = * -> Summary Account 130100 (General AR)
- Scenario Resolution Matrix
Transaction Customer Customer Group Resolved Rule Level Resolved Summary GL Account Rationale
US-001 10 Table 130105 Table rule explicitly matches US-001 ; overrides Group 10 and All .
US-002 10 Group 130110 No Table rule for US-002 ; matches Group 10 .
US-003 20 Group 130120 No Table rule for US-003 ; matches Group 20 .
US-004 30 All 130100 No Table rule for US-004 ; no Group 30 rule; falls back to All .
3. Accounts Receivable Parameters & Default Posting Profile Assignment
For the system to process sales invoices and customer payments without requiring manual profile selection on every document, a default posting profile must be assigned globally in AR parameters.
Navigation
Path: Accounts receivable > Setup > Accounts receivable parameters > Ledger and sales tax FastTab +---------------------------------------------------------------------------------------------+
- | Accounts Receivable Parameters: Ledger & Sales Tax |
- +---------------------------------------------------------------------------------------------+
- | Posting: |
- | - Posting profile: [ GEN ] <- Primary default for standard invoicing |
- | - Prepayment posting profile: [ PREPAY ] <- Dedicated profile for customer prepayments |
- | - Sales tax on prepayment: [ Yes ] <- Triggers tax accounting on deposit invoices |
- | - Cash discount posting: [ To accounts for cash discounts ] |
- +---------------------------------------------------------------------------------------------+
- Alternative Posting Profiles on Transactions
While GEN serves as the parameter-driven default, alternative posting profiles can be assigned or selected in specific operational scenarios:
Prepayments: When a prepayment sales order invoice is created, D365 Finance uses the Prepayment posting profile (e.g., PREPAY ) configured in AR Parameters to credit the Prepayment Liability account instead of the standard AR summary account.
Bad Debt Transfers: A customer balance can be reclassified by changing the posting profile on a general journal line from GEN to BAD_DEBT (moving the receivable from 130100 - Active AR to 130199 - Doubtful Accounts AR ).
Intercompany Billing: Direct intercompany sales can route to INTERCO (posting to 130300 - Intercompany Receivables ).
4. Exam Traps & Real-World Best Practices
Warning
Exam Trap: Changing Posting Profiles on Open Transactions Once an invoice has been posted to the customer subledger, you cannot retroactively edit the posting profile on the open transaction record ( CustTrans ). To move a posted balance from one posting profile to another (e.g., from GEN to DOUBTFUL ), you must post a customer settlement or a reclassification journal using a General Journal with an offsetting posting profile.
Important
Consultant Pro-Tip: The "Posting Profile Does Not Exist" Error If an invoice fails to post with the error "Customer posting profile does not exist for customer account X" , check two things immediately:
Is there an All record configured on the posting profile? If only Group and Table records exist, any customer belonging to a newly created customer group will cause posting failures.
Is the posting profile populated in Accounts receivable parameters > Ledger and sales tax > Posting profile ?