Drag and Drop Question You are implementing Business Central for a company. The finance manager of the company must configure the system to post payments and expenses. The configuration must include…

Question

Exhibit

Answer Area

Explanation

Explanation: Business Central Posting Groups for Payment Configuration

Context

This question is about posting group configuration in Microsoft Dynamics 365 Business Central - not payment processing pages. Posting groups define which G/L accounts transactions post to for each entity type.

Correct Mapping

Why Each Placement is Correct

1. Customer Posting Groups → Apply customer payments to multiple invoices

Customer Posting Groups link customers to the Accounts Receivable G/L account. When applying a customer payment across multiple invoices, BC must know where to post the receivable reduction. Without a customer posting group assigned, payment application cannot reconcile correctly against open entries.

2. Bank Account Posting Groups → Submit electronic payments to the bank

Each bank account in BC must have a Bank Account Posting Group that maps it to a specific G/L bank account. Electronic payment files (e.g., EFT, SEPA) are generated from bank account records - if the posting group is missing or misconfigured, the bank account cannot be used for electronic payment export.

3. Vendor Posting Groups → Get suggested payment to external parties based on due dates

The Suggest Vendor Payments function in the Payment Journal filters open vendor ledger entries. Vendors must have a Vendor Posting Group assigned so BC knows the Accounts Payable G/L account to credit when payments are posted. Without this, vendors won't appear in payment suggestions.

Why "General Posting Groups" is Not Used

General Posting Groups control revenue/expense accounts (combinations of General Business and General Product posting groups). They govern income statement accounts, not the liability/asset accounts involved in payment flows. This is a common misconception - general posting groups handle what was sold/bought, not who owes/is owed.

Common Mistakes

• Confusing Vendor and Customer posting groups for bank submissions - the bank account itself needs its own posting group; vendor/customer groups don't control the bank-side posting.
• Thinking General Posting Groups handle payments - they handle revenue/expense recognition, not AR/AP or bank account mapping.
• Employee reimbursement - employees reimbursed through BC are typically set up as vendors, so Vendor Posting Groups apply there too (the 4th requirement likely reuses Vendor Posting Groups).

No community discussion yet for this question.