Setup, Accounting Flow & Best Practices (2026 Edition)

Version tested: 10.0.44 (March 2026)
Navigation path: Accounts payable ▸ Setup ▸ Vendor posting profiles
(Menu names may vary slightly depending on localization or system configuration.)

Vendor posting profiles determine how Accounts Payable transactions are summarized in the General Ledger.

They define which GL accounts are used when invoices, payments, prepayments, and discounts are posted.

Correct configuration during implementation prevents many common causes of:

• AP-to-GL reconciliation issues
• audit findings
• period-end surprises

This article illustrates a baseline configuration for one vendor group — DOM ▪ Domestic Suppliers — and explains the accounting entries generated throughout the procure-to-pay cycle.

→ For a deeper explanation of how subledgers flow into the general ledger, see:
Ledger vs Subledger in D365 Finance
https://www.fitgapfinance.com/ledger-vs-subledger-d365-finance/

→ If the chart of accounts is poorly structured, posting profiles become harder to maintain:
10 Best Practices for Designing a Chart of Accounts in an ERP
https://www.fitgapfinance.com/10-chart-of-accounts-best-practices-for-erp-success/

1. Why Vendor Groups Matter

Vendor posting profiles are evaluated in priority order.

D365 Finance searches for a match using the following sequence:

Best practice is to configure one posting profile per vendor group.

The All grouping should exist only as a safety net — not as the primary configuration.

For this walkthrough we assume the vendor group DOM already exists.

In practice, posting profile design should follow the same principle as chart of accounts design: structure for clarity, but avoid unnecessary fragmentation.

→ Vendor grouping also connects to reporting structure and financial dimensions. See:
The Strategic Role of Financial Dimensions
https://www.fitgapfinance.com/the-strategic-role-of-financial-dimensions-better-insight-without-a-bloated-chart-of-accounts/

2. Account Mapping Baseline

The following GL accounts represent a typical baseline configuration for a domestic vendor group.

Important

The AP control account (20100) is a summary account.

It should never be posted to directly through a general journal. Doing so bypasses the subledger and is one of the most common causes of audit exceptions and reconciliation issues in Accounts Payable.

All postings should originate from the AP subledger so the ledger balance remains reconcilable to vendor balances.

3. Invoice Posting

To understand the role of vendor posting profiles, it helps to examine the accounting entries generated during the procure-to-pay cycle.

3a Standard Invoice (No Purchase Order)

When a vendor invoice is posted without a purchase order reference, D365 Finance records the following entry.

Example:

Dr 60100 Purchases
Cr 20100 Accounts Payable

The AP account used in the credit entry comes directly from the vendor posting profile.

3b PO-Based Invoice — Three-Way Match

For purchases that are subject to a three-way-match policy, accounting flows through an interim GR/IR accrual account.

This account represents goods received but not yet invoiced (GRNI / GRIR) and is one of the key reconciliation points in the procure-to-pay cycle.

Typical flow:

Example:

Product receipt
Dr Inventory / Purchase expenditure
Cr GR/IR Accrual (20200)

Vendor invoice
Dr GR/IR Accrual (20200)
Cr Accounts Payable (20100)

Important

The debit side of the product receipt entry depends on the inventory posting profile and item configuration.

For stocked items, the entry typically appears as:

Dr Inventory (inventory posting profile)
Cr Accrued Purchases / GRNI

For non-stocked items or procurement categories, the debit may instead post directly to an expense or purchase expenditure account.

In other words:

• Vendor posting profiles control the liability side of the transaction.
• Inventory posting profiles determine the asset or expense account used on receipt.

In many implementations, the GR/IR account becomes one of the most actively monitored reconciliation accounts during the period-end close.

Unmatched balances typically represent goods received but not yet invoiced.

4. Payment Journal & Vendor Settlement

When a payment journal is posted and settled against an open invoice, the system clears the AP liability and records the cash movement.

4a Standard Payment

Example:

Dr 20100 Accounts Payable
Cr 11000 Main Bank Account

4b Payment with Cash Discount

If the payment is made within the discount window (for example 2/10 Net 30), D365 Finance automatically records the discount.

Example:

Dr Accounts Payable 1,000
Cr Bank Account 980
Cr Purchase Discounts 20

Setup dependency:

Cash discount terms must be configured under:

Accounts payable ▸ Payment setup ▸ Cash discounts

The discount account defined in the posting profile is used only when an active discount term applies at settlement.

5. Prepayments

D365 Finance supports two approaches for vendor prepayments.

Prepayment Accounting Flow

Critical configuration rule

The prepayment account must be separate from the AP control account.

Mixing these accounts is one of the most common configuration mistakes and makes it impossible to reconcile vendor prepayments independently.

6. Payment Differences & Tolerance

D365 Finance allows small settlement differences between invoices and payments to be absorbed automatically.

Configuration path:

Accounts payable ▸ Setup ▸ Payment ▸ Payment tolerance

Typical uses include:

• rounding adjustments
• small payment differences
• minor currency settlement discrepancies

The posting account used depends on the payment difference account configured in the vendor posting profile.

7. Vendor Posting Profile Setup Checklist

A reliable configuration typically includes:

✔ Vendor groups aligned with reporting structure
✔ AP control account defined
✔ Vendor prepayment account configured
✔ GR/IR accrual account configured
✔ Cash discount account defined
✔ Payment difference account configured
✔ Testing of invoice, PO, payment, and prepayment scenarios

In many implementations, reconciliation issues traced back to Accounts Payable almost always originate in posting profile configuration or manual postings bypassing the subledger.

Testing these scenarios during implementation prevents most downstream problems.

8. Troubleshooting Tip: When AP Doesn't Reconcile

If the AP subledger does not reconcile to the General Ledger, review the following areas:

• Vendor posting profiles assigned to vendors
• Manual journals posted directly to the AP control account
• Payment settlement errors
• GR/IR accounts with unresolved balances

In practice, many reconciliation issues originate from either incorrect posting profile setup or journal entries that bypass the subledger.

What's Next?

This guide focuses on baseline Procure-to-Pay posting profile configuration.

Additional topics typically required for a complete implementation include:

• foreign currency vendor configuration
• realized and unrealized exchange rate accounts
• intercompany vendor posting profiles
• withholding tax setup
• expense management configuration

→ For implementation governance guidance see:
Roles & Responsibilities in an ERP Implementation Project
https://www.fitgapfinance.com/roles-responsibilities-in-an-erp-implementation-project/

→ For asset accounting configuration see:
Fixed-Asset Posting Profiles in Dynamics 365 Finance
https://www.fitgapfinance.com/en-fixed-assets-posting-profiles-d365/

🇫🇷 Version française :
Profils de validation Procure-to-Pay dans D365 Finance
https://www.fitgapfinance.com/profils-validation-fournisseurs-d365-finance/

© 2026 FitGap Finance™
Practical ERP thinking for Finance leaders.