calculate-loan

01 Loan payments

D365FO Payment Schedule: Setup and Calculation

Guide 01-14576 · Updated · Step by step

In Dynamics 365 Finance and Operations (D365FO), a payment schedule splits a customer or vendor invoice into installments with specified due dates and amounts. The schedule is generally set up through payment-schedule terms, then applied to a transaction; it determines how the amount is divided, while payment processing and settlement happen separately.

What a payment schedule means in D365FO

A payment schedule is a rule for dividing an invoice balance into multiple payments. It is not the same as a payment method, which describes how money is transferred, nor is it a bank payment journal that initiates a payment. A schedule can be useful when an agreement calls for a deposit followed by later installments, or for equal payments over several due dates.

D365FO applies schedules in Accounts receivable and Accounts payable. The exact labels and available options can vary with the application version, configuration, and enabled features. In practice, an organization defines schedule terms, assigns them to a customer or vendor where appropriate, and selects or confirms the terms on the transaction. The resulting invoice accounting remains subject to the usual posting and settlement processes.

How payment schedules are set up and applied

Payment schedule terms define how D365FO divides the transaction amount and calculates installment due dates. Depending on the schedule type and configuration, terms can specify a number of installments, a percentage or amount for each, and timing rules. Administrators typically configure the terms in the Accounts receivable or Accounts payable setup area; names and navigation can differ by release.

  1. Create or review the payment schedule terms, including the installment pattern and due-date basis.
  2. Assign the terms to the relevant customer or vendor account if they should be a default, or select them directly on a transaction when allowed.
  3. Enter the invoice or order details and check the schedule before posting. Confirm that the installment amounts add up to the transaction total and the due dates match the agreement.
  4. Post the invoice. D365FO creates the related open amounts for collection or payment; later, users process and settle those amounts through the applicable receivables or payables workflow.

For example, a 1,200-unit invoice split into three equal installments would allocate 400 units to each installment. The currency is whatever the invoice uses. This illustration is arithmetic, not a claim about a particular configuration: rounding, tax treatment, discounts, or other transaction details can affect the posted amounts.

Due dates, amounts, and transaction details

A schedule’s due dates are based on its configured rules and the transaction’s date information. Payment terms and schedule terms are related but not interchangeable: payment terms commonly calculate a due date or discount conditions, while a payment schedule establishes multiple installments. If an installment schedule is involved, review how its due-date calculation interacts with the transaction’s payment terms in the configured environment.

Schedule percentages should total 100% when the pattern is percentage-based. Fixed-amount schedules must account for the entire invoice balance. If installments are calculated in a currency with minor units, division may create a rounding remainder. Check the final installment and the posted invoice rather than assuming every installment will be identical to the displayed rounded example.

Also distinguish the invoice’s schedule from the cash-flow timing after posting. A due date is not proof that a payment has been sent or received. Customers may pay late or partially, and vendor payments may be held or grouped according to separate payment processing rules.

Choosing and checking schedule terms

Choose schedule terms that reflect the documented commercial arrangement and can be administered consistently. Before using a term broadly, test it with representative transactions, including a transaction amount that does not divide evenly into the desired number of installments.

  • Installment pattern: Decide whether amounts are equal, percentage-based, or based on specific amounts.
  • Timing: Verify the starting date and the interval or date rule for each installment.
  • Rounding: Check how fractional minor units are handled, especially in the final installment.
  • Defaults: Confirm whether account-level terms are appropriate and whether users can override them on a transaction.
  • Currency and tax: Test relevant currency and tax scenarios using the organization’s actual configuration.

A customer or vendor default can reduce data entry, but defaults should be reviewed when agreements differ. Do not assume changing the terms on an account will revise already-posted invoices; verify the transaction and document status before making changes.

Common problems and troubleshooting

If an expected schedule is missing, check that the terms exist and are available for the relevant module and transaction. Then review the account defaults, the transaction’s selected terms, and whether the current document state permits editing. Security roles, customizations, and version differences may also affect what a user can see or change.

If installment amounts or dates look wrong, inspect the schedule definition and the dates used by the transaction. Verify percentages, intervals, and rounding with a small test invoice. If the schedule looks correct before posting but the open transactions do not match expectations, review the posted voucher and related customer or vendor transactions; the schedule itself does not replace reconciliation of the accounting entries.

Another frequent misconception is that setting a schedule automatically collects or pays installments. It does not, by itself, move money. Each installment remains subject to the organization’s collection, payment, approval, and settlement processes.

Frequently Asked Questions

What does a payment schedule do in D365FO?
It divides a customer or vendor transaction into installments with amounts and due dates defined by schedule terms.

Where do I create payment schedule terms?
They are configured in Accounts receivable or Accounts payable setup. The precise menu path and options depend on the D365FO version and configuration.

Is a payment schedule the same as payment terms?
No. Payment terms generally determine a due date or discount conditions; payment schedule terms define multiple installment amounts and dates.

Does a payment schedule automatically pay an invoice?
No. It structures the amounts due. Sending or receiving money and settling transactions require separate processes.

Can I change a schedule after posting?
Whether a posted transaction can be changed depends on its status and the system’s configuration. Check the posted transaction and follow your organization’s correction procedures rather than assuming account defaults will update it.

Practical takeaway

For reliable results, define schedule terms around the agreed installment pattern, test dates and rounding, and review the transaction’s schedule before posting. Keep schedule setup, invoice posting, payment execution, and settlement distinct when troubleshooting. Because labels and behavior can depend on version and configuration, consult your organization’s D365FO documentation or administrator for the exact setup available in your environment.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this section

The whole Loan payments section →