14.1 Methods of Payment & the Vendor Payment Proposal Engine
Key Takeaways
- A method of payment carries the payment type, the account the payment posts to, and the Electronic Reporting export format.
- Payment specifications on the method of payment vary the file layout per bank without duplicating the method.
- The payment proposal selects open invoices by due date, cash discount date, vendor, or method of payment.
- Choosing the cash discount date as the proposal basis pulls invoices forward so the discount is not lost.
14.1 Methods of Payment & the Vendor Payment Proposal Engine
Quick Summary: In enterprise financial management, executing accurate, timely, and compliant vendor disbursements is essential for maintaining liquidity, capturing cash discounts, and enforcing segregation of duties. In Microsoft Dynamics 365 Finance, the Accounts Payable (AP) payment processing architecture enables automated payment proposal generation, bank integration via Electronic Reporting (ER) formats (such as ISO 20022 SEPA Credit Transfer and NACHA ACH), centralized cross-company disbursements across multiple legal entities, and rigorous check lifecycle management.
1. Methods of Payment & Payment Specifications
Methods of payment (Accounts payable > Payment setup > Methods of payment) establish the operational and accounting rules for how disbursements are generated, settled, and posted.
+---------------------------------------------------------------------------------------------------------+
| Method of Payment Configuration Matrix |
+---------------------------------------------------------------------------------------------------------+
| Field / Setting | Functional Purpose / Options | Business & Audit Impact|
| :---------------------------------- | :-------------------------------------- | :--------------------- |
| **Payment type** | Check, Electronic payment, Total, Bill | Determines processing |
| | of exchange, Promised payment | engine and validation |
| ----------------------------------- | --------------------------------------- | ---------------------- |
| **Period** | **Invoice:** 1 payment line per invoice | Governs aggregation |
| | **Date:** 1 payment line per due date | of multiple open |
| | **Total:** 1 payment line per vendor | vendor invoices |
| ----------------------------------- | --------------------------------------- | ---------------------- |
| **Account type & Payment account** | Bank or Ledger (Disbursement Bank Acct) | Default credit account |
| ----------------------------------- | --------------------------------------- | ---------------------- |
| **Payment status required** | **None:** Can post without generation | Enforces generation of |
| | **Sent:** Must generate payment file | payment media before |
| | **Approved:** Requires sign-off | journal posting |
| ----------------------------------- | --------------------------------------- | ---------------------- |
| **Export format / ER configuration**| Electronic Reporting format mapping | Generates bank-ready |
| | (e.g., ISO 20022 Credit transfer) | XML or text data file |
| ----------------------------------- | --------------------------------------- | ---------------------- |
| **Bridging posting** | Intermediary transit account flag | Delays bank credit |
| | (Bridging account GL) | until bank reconciliation|
+---------------------------------------------------------------------------------------------------------+
Payment Specifications
Under a single method of payment (such as EFT or ACH), organizations frequently require different clearing parameters depending on transaction type or bank specifications. Payment specifications (Accounts payable > Payment setup > Methods of payment > Payment specification button) define sub-formats:
- NACHA CCD (Corporate Credit or Deposit): Standard corporate-to-corporate vendor ACH transfers.
- NACHA PPD (Prearranged Payment and Deposit): Direct deposit disbursements to individual independent contractors or employees.
- NACHA CTX (Corporate Trade Exchange): B2B payments containing ANSI ASC X12 EDI remittance detail addenda records.
- SEPA Core vs. SEPA B2B: Specific ISO 20022 clearing schemes for European bank compliance.
Electronic Reporting (GER) vs. Legacy Export Formats
Modern Dynamics 365 Finance deployments utilize Electronic Reporting (ER) configurations rather than legacy X++ file formats for bank integration:
- ISO 20022 Credit Transfer (
pain.001.001.03/pain.001.001.09): Global XML standard adopted by European, North American, and Asian clearing networks. - NACHA Format (US): Fixed-length 94-character record structure for US Automated Clearing House network.
- BACS / Faster Payments (UK): Specialized UK electronic payment clearing formats.
[!NOTE] To configure Electronic Reporting formats for a method of payment, navigate to
Accounts payable > Payment setup > Methods of payment, enable the Generic electronic reporting toggle in the File formats fast tab, and select the appropriate Export format configuration imported from the Global Repository in the Electronic Reporting workspace.
2. Vendor Payment Proposal Engine & Execution
The Vendor payment proposal (Accounts payable > Payments > Vendor payment journal > Lines > Payment proposal > Create payment proposal) is the primary automation engine used by accounts payable specialists to select open vendor invoices for settlement based on cash flow strategy and payment terms.
+---------------------------------------------------------------------------------------------------------+
| Payment Proposal Parameter Configuration |
+---------------------------------------------------------------------------------------------------------+
| Parameter | Selection / Options | Analytical Behavior |
| :-------------------------- | :-------------------------------------- | :------------------------------------- |
| **Proposal type** | **Due date:** Invoices due by cutoff | Filters open invoices where Due Date |
| | **Cash discount date:** Discount cutoff | <= To Date or Cash Discount Date <= To |
| | **Due date and cash discount date** | Date (optimizes working capital) |
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **From date / To date** | Date range filter | Evaluates open AP document dates |
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Minimum payment amount** | Numerical currency threshold (e.g., $10)| Excludes micro-balances from payment |
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Maximum payment amount** | Numerical cash cap | Limits total disbursement run to budget|
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Include vendor prepayments**| Toggle (Yes / No) | Pulls open prepayment journal vouchers |
| | | to offset against pending invoices |
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Check vendor balance** | Toggle (Yes / No) | Verifies vendor does not have an |
| | | overall net debit balance |
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Delete negative payments**| Toggle (Yes / No) | If credit memos exceed invoices, either|
| | | removes negative lines or keeps debits |
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Payment currency** | Transaction currency vs. Accounting cur | Controls FX conversion and bank currency|
| --------------------------- | --------------------------------------- | -------------------------------------- |
| **Payment method default** | Method of Payment override code | Forces selected payment method onto lines|
+---------------------------------------------------------------------------------------------------------+
Cash Discount Date Grace Days
When selecting invoices by Due date and cash discount date, the system evaluates whether taking early settlement discounts (e.g., 2/10 Net 30) generates a positive rate of return compared to holding working capital until invoice maturity. Organizations can configure Cash discount grace days in Accounts payable > Setup > Accounts payable parameters > Settlement to allow taking discounts even if payment is executed 1-2 days after the formal discount date due to bank processing latencies.
Proposal Grid Editing & Settlement Adjustments
Once the payment proposal runs, D365 Finance presents the Vendor payment proposal grid:
- Remove Lines: Users can highlight and remove specific vendor invoice lines without altering the underlying open invoice status.
- Change Payment Amount: Users can edit the Payment amount to execute partial payments.
- Vendor Netting / Credit Memo Application: The system automatically aggregates open credit memos and debit memos against positive invoices when the Method of Payment period is set to Total.
- Move to Journal: Clicking Create payments transfers the validated proposal lines into the active Vendor payment journal.
An Accounts Payable specialist in Dynamics 365 Finance runs a vendor payment proposal on August 15, 2026. An invoice for $20,000 is due on August 31, 2026, with payment terms of '2/10 Net 30' and a cash discount date of August 16, 2026. The proposal parameter is configured with Proposal Type set to 'Due date and cash discount date' with a To Date of August 15, 2026, and the Cash Discount Grace Days parameter is set to 2 days. How will the payment proposal treat this invoice?
An Accounts payable specialist runs a payment proposal on 15 August. An invoice of $20,000 is due 31 August but offers a 2% cash discount if paid by 20 August. The proposal is built using the due date as the selection basis and the invoice is not included. What should the specialist change to capture the discount?