“Net 30” looks like a complete instruction. It gives accounts payable a payment interval, but it may leave one operational question unanswered: 30 days from which date? Depending on the agreement and the system rule, the candidate could be the invoice date, the date the invoice was received, a configured terms date, or a specific month-end date.

That distinction is easy to miss when a document workflow extracts only the phrase Net 30. A useful invoice payment terms extraction process also captures the dates that could anchor the calculation and keeps their source visible. If the agreement does not settle the question, the workflow should send it for review instead of choosing whichever date is easiest to read.

One invoice can carry several different dates

Invoices and payables systems commonly distinguish the date printed on the invoice from the date it arrives, the date it is posted, and the due date calculated from a payment term. They are related, but they are not interchangeable.

Microsoft's documentation for vendor invoices describes separate invoice received, invoice, posting and due dates. In that workflow, the due date is initially based on posting date and payment terms; entering an invoice date can recalculate it. That is an example of a configurable system rule, not a universal definition of Net 30. Microsoft Learn: Vendor invoice dates.

For extraction, keep each value in its own field and retain where it came from. A date printed beside “Invoice date” is evidence for that field. It does not, by itself, prove that the contract uses it as the payment-term start date.

The same term can lead to different dates

Suppose an invoice is dated March 28, 2026, arrives on April 2, and the governing terms say Net 30. The arithmetic below shows why the start date matters. It assumes calendar-day counting and no separate holiday or business-day adjustment; the agreement and configured rules control in practice.

Possible anchorDate plus 30 daysWhen it applies
Invoice dateApril 27, 2026When the agreed terms use the invoice date.
Receipt dateMay 2, 2026When the agreement or configured rule starts at receipt.
Month-end dateApril 30, 2026Only when the terms explicitly define month-end as the anchor.

These are candidate calculations, not three valid due dates for the same invoice. The workflow should identify the controlling clause or approved policy before turning a candidate into a payable date. If the purchase order says one thing and the invoice another, preserve both values and route the mismatch through the established approval path.

Keep the discount window attached

Terms such as “2/10, Net 30” combine an early-payment discount period with the final payment interval. Oracle's payment-term guidance describes the common meaning as a 2% discount when payment is received within 10 days, with the remaining balance due within 30 days. It also describes systems that calculate due and discount dates from a configured terms date. Oracle Financials: Guidelines for defining payment terms.

If March 28 is the approved anchor in an example, the 10-day discount date would be April 7 and the 30-day due date April 27 under that rule. If another date is the anchor, both dates move. Extract the discount percentage, discount period and net period as separate values, and keep the source phrase so a reviewer can see whether the normalized fields reflect the document.

What to capture before calculating

A reliable workflow separates what the document says from the rule used to interpret it:

  • Preserve the wording — keep the original payment-terms text, including discount notation, “due upon receipt,” or an end-of-month clause.
  • Capture candidate dates — record invoice date, received date and any explicit terms date separately, with page or field references.
  • Check the governing records — compare the invoice with the purchase order, supplier agreement and approved AP policy that apply to that vendor.
  • Apply only an approved basis — calculate a due date from the configured rule, and retain the selected anchor and rule version with the result.
  • Route ambiguity — send missing, conflicting or unreadable terms to an AP reviewer; do not silently substitute posting date or receipt date.

This gives downstream systems a traceable result: the extracted phrase, its source, the selected date basis, the calculation rule, and the reviewer or workflow decision when an exception was needed. It also makes a later correction explainable instead of leaving only a changed due date.

Where document AI stops

Document AI can extract an invoice's payment-term text and related dates with their source references. Cogneris shows fields such as payment_terms in its supplier invoice workflow example. The buyer's contract, purchase order and AP policy determine which date is authoritative, while the accounting system applies the configured calculation and any business-day adjustments.

Do not treat a confident reading of “Net 30” as proof of the correct due date. When the start event is absent or the records disagree, preserve the evidence and ask the person who owns the terms to resolve it. This article is an operational example, not legal or accounting advice.