10.1 Purchases & Payables Setup & Vendor Master

10.1 Purchases & Payables Setup & Vendor Master

Quick Summary: In Microsoft Dynamics 365 Business Central, procurement and accounts payable operations are governed at the company level through Purchases & Payables Setup (Page 460) and at the entity level through the Vendor Card (Page 26). Purchases & Payables Setup controls critical accounting policies such as Discount Posting (No Discounts, Invoice Discounts, Line Discounts, All Discounts), Exact Cost Reversing Mandatory for returns, and master Number Series for orders and posted documents. Vendor cards structure purchasing terms, currency codes, posting groups, and the Application Method (Manual vs. Apply to Oldest). Vendor disbursements rely on Vendor Bank Accounts for automated electronic payment exports. The underlying subledger architecture separates transaction totals in Vendor Ledger Entries (Table 25) from granular monetary events in Detailed Vendor Ledger Entries (Table 380), rolling up to the General Ledger via Vendor Posting Groups.

---

Purchases & Payables Setup: Global Governance & Controls

The Purchases & Payables Setup card (Page 460 / Table 312 Purchases & Payables Setup) defines the global accounting rules, posting behaviors, default calculation parameters, and document numbering series for all procurement workflows across the company.

UI Navigation Path:
Tell Me (Alt+Q) -> Purchases & Payables Setup (opens Page 460)

1. Discount Posting Policies

A primary functional decision tested on the MB-800 exam is how purchase discounts are recognized in the General Ledger. The Discount Posting drop-down field on the General FastTab provides four distinct configuration options:

[!NOTE] Regardless of the Discount Posting selection, the Vendor Ledger Entry always reflects the net payable balance owed to the vendor. The setting exclusively controls whether discounts are split into separate General Ledger debits and credits or absorbed into the primary purchase account.

2. Exact Cost Reversing Mandatory

When processing vendor returns or issuing purchase credit memos, maintaining inventory valuation integrity is paramount. Business Central provides the Exact Cost Reversing Mandatory boolean setting:

• When Enabled (Yes - Recommended Best Practice): Users cannot post a Purchase Return Order or Purchase Credit Memo unless an exact original posted inbound entry is linked using the Applies-to Item Entry field on the line or the Get Posted Document Lines to Reverse action. Business Central retrieves the exact original unit cost from the posted purchase receipt, preventing inventory cost distortion.
• When Disabled (No): Users can enter arbitrary unit costs on purchase return orders or credit memos, or allow the system to apply current average/standard costs. This frequently creates cost variances between original receipt valuation and return settlement.

3. Background Document Posting & Archival Controls

• Receipt on Invoice: When enabled, posting a purchase invoice directly (without creating a prior purchase receipt) causes Business Central to automatically generate a Posted Purchase Receipt in the background, ensuring physical inventory tracking matches the financial invoice.
• Return Shipment on Credit Memo: When enabled, posting a purchase credit memo directly automatically posts a Posted Return Shipment in the background.
• Allow Document Deletion Before: Establishes a date threshold preventing users from deleting processed blanket orders, purchase orders, or quotes prior to the specified date, preserving operational audit trails.
• Archive Quotes / Orders: Specifies whether quotes and orders are automatically archived upon deletion, posting, or manual request (Never, Question, Always).

4. Number Series Configuration

The Number Series FastTab establishes the automated, sequential alphanumeric identifiers used throughout the purchasing module:

• Vendor Nos.: Number series assigned when creating a new Vendor Card.
• Quote Nos. / Order Nos. / Invoice Nos. / Credit Memo Nos.: Preliminary numbering for unposted purchasing documents.
• Posted Receipt Nos.: Mandatory series assigned to warehouse receipts upon posting.
• Posted Invoice Nos. / Posted Credit Memo Nos.: Continuous legal number series stamped on posted commercial documents.
• Posted Return Shipment Nos.: Number series stamped on outbound return shipments.

---

The Vendor Master Card (Page 26 / Table 23)

Vendor records are created and maintained on the Vendor Card (Page 26). When creating a vendor, functional consultants typically utilize Vendor Templates to pre-populate standardized posting groups, payment terms, and currency settings based on vendor classification (e.g., Domestic, EU, Foreign, Services).

UI Navigation Path:
Tell Me (Alt+Q) -> Vendors -> Action: New (select template) or Edit (opens Page 26)

Vendor Card FastTab Structure:

Vendor Card (Page 26)
 ├── General FastTab       ──► No., Name, Search Name, Blocked (Blank / Payment / All)
 ├── Address & Contact     ──► Physical Street, City, Country, Primary Contact
 ├── Invoicing FastTab     ──► Gen. Bus. Posting Group, Vendor Posting Group, Currency Code
 ├── Payments FastTab      ──► Payment Terms, Payment Method, Priority, Application Method
 └── Receiving FastTab     ──► Location Code, Lead Time Calculation, Base Calendar

1. General FastTab: Identification & Posting Restrictions

• No.: Primary unique identifier assigned from the configured Number Series.
• Name & Search Name: Official trading entity name and indexed search string.
• Blocked: Enforces operational controls across purchasing workflows:
  • [Blank]: Open for all operational activities (quotes, orders, receipts, invoices, payments).
  • Payment: Purchasing documents (orders, receipts, invoices) can be processed, but outgoing payment disbursements and check printing are strictly blocked.
  • All: Completely blocks all transactions for this vendor, preventing document entry, receipt, invoice posting, and payment issuance.

2. Invoicing FastTab: Financial Mapping & Taxation

• Gen. Bus. Posting Group: Connects the vendor to the General Posting Setup matrix, determining which G/L purchase expense accounts, inventory adjustment accounts, and discount accounts are utilized on transaction lines.
• Vendor Posting Group: The critical control link connecting the vendor subledger to the G/L Payables Account (balance sheet liability account). It also defines payment discount debit/credit accounts, payment tolerance accounts, and rounding accounts.
• VAT Bus. Posting Group / Tax Area Code: Establishes the regional tax framework (e.g., domestic standard VAT, zero-rated exports, reverse-charge import rules, or US sales tax jurisdictions).
• Currency Code: When left blank, the vendor operates in the company's base Local Currency (LCY). When populated (e.g., EUR, USD, GBP), all purchase documents and payments for this vendor default to that foreign currency.
• Invoice Disc. Code: Specifies the vendor code used to look up invoice discount percentages. By default, this matches the vendor's own number, but multiple vendor accounts can share a single parent vendor discount code.
• Prices Including VAT: Specifies whether unit costs entered on purchase lines include or exclude Value Added Tax.

3. Payments FastTab: Settlement Terms & Cash Flow Controls

• Payment Terms Code: References Table 3 Payment Terms, defining the net due date calculation formula (e.g., 1M, 30D, CM), early settlement discount date formula (e.g., 10D, 8D), and discount percentage (e.g., 2%).
• Payment Method Code: References Table 289 Payment Method, defining the default payment channel (e.g., CHECK, EFT, BANK, CASH).
• Priority: An integer value (1, 2, 3...) utilized by the Suggest Vendor Payments batch job. When available cash is limited, Business Central prioritizes payments to vendors with lower numerical values (Priority 1 is processed before Priority 2).
• Application Method: A fundamental posting configuration tested on the certification exam:
  • Manual (Default): Payments, credit memos, and refunds are not applied automatically upon posting. The user must manually link payments to specific invoices using Applies-to Doc. No. or the Apply Entries window. If posted without application, the payment remains an open credit entry.
  • Apply to Oldest: When a payment or credit memo is posted without selecting a specific invoice, Business Central automatically applies the entry against the vendor's oldest open credit entry (earliest posting date).
• Preferred Bank Account Code: Links to a specific record in the Vendor Bank Accounts table, identifying the default destination for electronic bank transfers (EFT/SEPA).

---

Vendor Bank Accounts (Page 425 / Table 288)

To facilitate automated electronic funds transfers (EFT), Automated Clearinghouse (ACH) transactions, and Single Euro Payments Area (SEPA) Credit Transfers, organizations configure Vendor Bank Accounts.

UI Navigation Path:
Vendor Card -> Related -> Vendor -> Bank Accounts (opens Page 425)

Each vendor bank account record stores the supplier's external financial institution coordinates:

• Code & Name: Unique identifier (e.g., MAIN, OPERATING, WIRE) and bank institution name.
• Bank Branch No. / Transit No.: Domestic transit routing number (e.g., 9-digit ABA routing transit number in the United States, sort code in the UK, transit/institution number in Canada).
• Bank Account No.: The supplier's account number at their financial institution.
• SWIFT Code (BIC): The 8- or 11-character Business Identifier Code required for international wire transfers.
• IBAN: International Bank Account Number (up to 34 alphanumeric characters) mandatory for European cross-border settlement.

Once configured, the primary banking record code is populated in the Preferred Bank Account Code field on the Vendor Card's Payments FastTab. When the payment export routine executes in the Payment Journal, Business Central retrieves these coordinates automatically to construct the outgoing payment file.

---

Payables Subledger Architecture & Financial Ledger Integration

Understanding the relational data model between vendor master records, subledger entries, and the General Ledger is essential for functional consultants:

Payables Data Architecture:

[Vendor Card: Table 23 (Master Data)]
         │
         ├──► [Vendor Ledger Entry: Table 25 (High-Level Operational Record)]
         │         - Document Type (Invoice, Payment, Credit Memo)
         │         - Document No., Posting Date, Due Date, Pmt. Discount Date
         │         - Amount, Remaining Amount, Open (Yes/No), Closed by Entry No.
         │         │
         │         └──► [Detailed Vendor Ledger Entry: Table 380 (Granular Monetary Events)]
         │                   - Entry Type (Initial Entry, Application, Realized/Unrealized Gain/Loss)
         │                   - Amount, Amount (LCY), Debit/Credit Amount
         │
         └──► [General Ledger Entry: Table 17 (Financial Balance Sheet Impact)]
                   - Linked via Vendor Posting Group (Payables Control Account: e.g., 20100)

1. Vendor Ledger Entry (Table 25)

Represents commercial transactions at the document level. Key fields include:

• Document Type: Invoice, Payment, Credit Memo, Finance Charge Memo, Reminder, Refund.
• Amount & Remaining Amount: Amount records the original posted gross value (credits are negative). Remaining Amount tracks the unapplied, open balance remaining on the document.
• Open: A boolean flag. Set to Yes when Remaining Amount is non-zero. When payments or credit memos fully settle the document, Remaining Amount becomes 0.00 and Open switches to No.
• Due Date & Pmt. Discount Date: Calculated at posting from the Payment Terms Code.

2. Detailed Vendor Ledger Entry (Table 380)

Business Central never mutates or overwrites posted financial records. When applications, currency revaluations, or discounts occur, Business Central writes immutable records to the Detailed Vendor Ledger Entries table. Each detailed entry references a parent Vendor Ledger Entry:

3. Complete Lifecycle Accounting Example

1. Post Purchase Invoice for $1,000 (Vendor V100, Net 30):
   • Vendor Ledger Entry: Doc Type = Invoice, Amount = -$1,000, Remaining Amount = -$1,000, Open = Yes.
   • Detailed Vendor Ledger Entry: Entry Type = Initial Entry, Amount = -$1,000.
   • G/L Entry: Credit G/L 20100 (Accounts Payable) $1,000; Debit G/L 50100 (Inventory/Expense) $1,000.
2. Post Payment of $1,000 applied to Invoice:
   • Vendor Ledger Entry (Payment): Doc Type = Payment, Amount = +$1,000, Remaining Amount = $0.00, Open = No.
   • Vendor Ledger Entry (Invoice): Remaining Amount updates to $0.00, Open = No, Closed by Entry No. populated.
   • Detailed Vendor Ledger Entries:
     • Line 1: Entry Type = Initial Entry (Payment VLE), Amount = +$1,000.
     • Line 2: Entry Type = Application (Invoice VLE), Amount = +$1,000 (offsets -$1,000 remaining balance).
     • Line 3: Entry Type = Application (Payment VLE), Amount = -$1,000 (offsets +$1,000 remaining balance).
   • G/L Entry: Debit G/L 20100 (Accounts Payable) $1,000; Credit G/L 10100 (Bank Cash Account) $1,000.

---

Common Implementation Pitfalls & Exam Traps