Invoice due dates: controlling the baseline date and payment terms
The same invoice can produce a different due date depending on the baseline date, contract terms and system configuration. AP should be able to reproduce the calculation before the document enters a payment proposal.
A due date is not a field to copy mechanically. A system may calculate it from the invoice date, receipt date, posting date or another agreed baseline. Net terms, end-of-month rules, day-of-month rules, discounts and payment calendars then affect the result. This model supports data control in the client process; it does not replace the contract, payment policy or authorised decision.
1. Separate the four dates at intake
Microsoft distinguishes invoice received date, invoice date, posting date and due date. In the documented flow, the due date can initially be calculated from posting date and payment terms, then recalculated when invoice date is entered. The value in the due-date field alone is therefore not enough.
Record the source and role of each date. Receipt date comes from the intake channel, invoice date from the document, posting date from the financial period, and due date from a rule. Mixing these roles can shorten or extend the payment window incorrectly.
2. Establish the payment-terms hierarchy
Terms can come from a purchase order, supplier master, contract or defaults. Oracle describes PO terms taking priority when an identifying PO is entered, otherwise supplier-site or invoice-option defaults. SAP also describes proposals from a PO or vendor data.
Compare the terms code with the source document and explain every override. A supplier master match is insufficient if the contract provides different terms. For invoices spanning several orders, check which PO supplied the default.
3. Reproduce the calculation step by step
A net rule adds a number of days to the baseline. Other rules calculate from month end, use a specified day of month or move the result after a cutoff. Oracle also documents fixed-date, calendar and day-of-month terms with cutoff day and months ahead.
Keep the baseline date, terms code, rule parameters, pre-calendar result and final due date in the control record. A reviewer can then reproduce the result and later configuration changes will not erase the basis of the decision.
4. Separate net due date from discount date
The net due date and early-payment discount date are different outcomes. SAP documents terms with successive discount levels and a net date, while Oracle distinguishes due dates from discount dates. The discount date does not make the invoice overdue.
Show discount amount and date separately and validate them against the agreement. An economically attractive early payment still requires duplicate control, approval and available funds. AP should not alter terms merely to obtain a discount.
5. Control exceptions and manual overrides
An override may be justified by a corrected source date, amendment, dispute or process-owner decision. Capture old and new values, reason, evidence, author and timestamp. A person changing a date should not approve an exception beyond their authority.
Pay special attention to late-received invoices, closed periods, multiple-PO documents and due dates falling on non-working days. Urgency can trigger escalation but must not remove the audit trail.
6. Checklist before the payment proposal
Verify the source of invoice and receipt dates, baseline, terms hierarchy and code, due-date calculation, holiday calendar, discount, holds and change history. Compare the outcome with the contract or PO and confirm the exception owner.
A sound process does not manually set a “reasonable” date; it proves why the date is correct. That reduces premature payments, late payments, lost discounts and supplier disputes.
Sources and scope
Microsoft, SAP and Oracle documentation was checked on 28 October 2026. Features depend on product and configuration. The proposed hierarchy, change log and checklist are an editorial model to agree with the process owner. This guide is not a posting instruction or payment authorisation.
FAQ
Is the date printed on the invoice always binding?
Not necessarily. Compare it with the contract, PO and client policy, then resolve any difference.
What is a baseline date?
It is the date from which the system counts days or the period defined by the payment terms.
Is the discount date the net due date?
No. It is a separate date for earning a discount; the net date defines payment without discount.
What should an override record contain?
Old and new values, reason, evidence, author, timestamp and approval within authority.
