Invoice Due Date Calculator

Date review needed {{ termBadge }}

Invoice date:

Select the issue or receipt date shown on the invoice or payment request.

Payment term:

Choose the term wording from the invoice, contract, PO, or vendor setup.

{{ termDaysLabel }}:

Enter whole days from 0-3650; use 30 for Net 30 or 10 for 10 business days.

days

Day of next month:

Enter a day from 1-31; short months automatically use their final calendar day.

Weekend days:

Select the non-payable weekly pattern used by your business calendar.

Custom weekend weekdays:

Select one or more weekdays to exclude from business-day counting and adjustment.

Due date adjustment:

Choose whether a weekend or holiday deadline rolls forward, backward, or stays as calculated.

{{ warning }}

Common term:

Use a preset to fill common term fields, then adjust weekend and holiday rules if needed.

Holiday dates:

Examples: 2026-05-25 Memorial Day or 07/03/2026 Company holiday.

Status date:

Pick the date used for due today, overdue, or days-remaining status badges.

EOM cutoff day:

Use 31 for normal EOM terms, or a lower cutoff day when late-month invoices roll forward.

day

Count invoice date:

Date display:

Select ISO, long, or US-style labels for visible due dates and exports.

Step	Result	Copy
{{ row.step }}	{{ row.result }}

Date	Day	Reason	Copy
{{ row.date }}	{{ row.day }}	{{ row.reason }}

Metric	Value	Copy
{{ row.label }}	{{ row.value }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

An invoice due date is more than a date printed near the total. It is the point where payment expectations, approval timing, cash planning, discount windows, and overdue follow-up all meet. When the date is wrong, a payer may release cash early, miss a discount, trigger unnecessary collection messages, or apply late-payment rules before the underlying invoice is actually due.

The first date to settle is the anchor date. Many ordinary invoices count from the issue date, but some agreements count from receipt, delivery, inspection, acceptance, approval of a proper invoice, or another event named in a purchase order. A correct term calculation from the wrong anchor still produces the wrong payable deadline, so the anchor should be kept with the final date whenever the result supports a payment run or audit note.

Common invoice payment term wording and due date meaning
Term wording	How the due date is usually built	Common mistake
Due on receipt	The anchor date is also the base due date.	Forgetting that a weekend or holiday rule may still affect when payment is practical.
Net days	A fixed number of calendar days is added to the anchor date.	Treating Net 30 as 30 business days when the term only says Net 30.
End of month	The due date is tied to the month end that belongs to the anchor date.	Missing a cutoff rule that moves late-month invoices to the next month end.
Specific day next month	The deadline is a numbered day in the following month.	Assuming every month has day 29, 30, or 31.
Business days	Only payable weekdays are counted, with holidays removed when supplied.	Using the vendor calendar when the payer's calendar controls the payment obligation.

Calendar-day and business-day terms answer different questions. Calendar-day terms measure elapsed time, so weekends remain part of the count unless a final adjustment rule moves the deadline. Business-day terms count only dates that are open for payment under the chosen weekly pattern and holiday list. End-of-month terms are different again because the month boundary, not elapsed time, is the main reference point.

Short months and local closures are common sources of date drift. A term aiming at the 31st of next month must land on the last day of February when February is next. A due date that lands on a Saturday might remain Saturday, move to Monday, or move back to Friday depending on the clause, procurement policy, bank calendar, or local rule. The arithmetic is simple only after those rules are explicit.

A defensible due-date review keeps the anchor date, base date, final adjusted date, and status review date separate.

A due date does not prove that an invoice is approved, undisputed, or collectible. It only says when the entered payment term reaches a deadline under the calendar rules being used. For statutory prompt-payment programs, public-sector invoices, regulated accounts, or disputed work, the controlling rule may define the start event, due date, grace period, and interest trigger differently from the wording on a commercial invoice.

How to Use This Tool:

Match the fields to the exact payment wording first, then use the result tabs to check the date path before relying on the final deadline.

Set Invoice date to the anchor date you want to count from. If the agreement starts from receipt, delivery, acceptance, or approval, enter that date instead of the printed issue date.
Choose Payment term. Net days, End of month, End of month plus days, Specific day of next month, and Business days use different base-date rules.
Enter Term days or Day of next month when the selected term needs a number. Term days are whole numbers from 0 to 3650, and a numbered day beyond a short month is capped at that month's final date.
Select Weekend days and Due date adjustment. Use a custom weekend only when the payer's working calendar is not one of the standard patterns.
Open Advanced for common term presets, holiday dates, Status date, EOM cutoff day, the business-day start option, and date display format.
Check any warning before using the result. Unreadable holiday lines are ignored, duplicate holiday dates are ignored after the first entry, and an invalid status date makes the due-soon or overdue badge unreliable.
Use Term Walkthrough to audit the calculation, Calendar Exclusions to see skipped or adjusted dates, Payment Timeline for the chart, and Payment Snapshot or JSON when you need a portable record.

Interpreting Results:

Due date is the final adjusted payable deadline. Base calculated date is the date produced by the payment term before weekend or holiday movement, which makes it the best row to inspect when the final date seems later or earlier than expected.

Days until due is measured from the selected Status date. It can say not due yet, due today, or overdue without changing the actual due date. Change the status date when you are preparing a future reminder or checking a past payment date.

If the base and final dates differ, read the Adjustment note before approving a payment batch, sending a reminder, or applying a late-payment clause.
If Calendar Exclusions is empty, no configured weekend day or entered holiday changed the result. It does not confirm that every bank, buyer, or jurisdiction was open.
If a business-day term looks too long, check the weekend pattern, holiday list, and Count invoice date setting. All three can change the count.
If the status says overdue, confirm the anchor date and contract wording before moving from reminder planning to penalties, holds, or collections.

Technical Details:

Invoice due-date arithmetic has three distinct dates. The anchor date starts the payment term. The base date is the direct result of the term rule. The final due date applies the selected weekend and holiday adjustment to the base date. Keeping those dates separate prevents a business-day rollover from being mistaken for the original term result.

Calendar terms use elapsed UTC day counts so daylight saving changes do not alter the number of days. Business-day terms scan forward through calendar dates and count only dates that are not in the configured weekend set and not in the holiday list. End-of-month terms first find a month-end anchor, and a cutoff day below 31 can move late-month invoices to the following month end before any extra days are added.

Formula Core:

\begin{array}{lcl} D_{base} & = & payment term rule (D_{anchor}, N, C) \\ D_{final} & = & calendar adjustment (D_{base}, W, H, R) \\ days_until_due & = & D_{final} - D_{status} \end{array}

D_anchor is the entered invoice or receipt date. N is the term-day count when the term uses one. C is the end-of-month cutoff day. W is the weekend set, H is the holiday list, and R is the final adjustment rule. The status comparison is a signed day difference, so negative values indicate an overdue invoice.

Invoice due date term rules
Term	Base due-date rule	Boundary behavior
Due on receipt	Base date equals the anchor date.	A final adjustment can still move the date when the anchor is excluded.
Net days	Adds the entered term days as calendar days.	Net 30 adds 30 calendar days, not 30 payable weekdays.
End of month	Uses the last day of the anchor month unless the cutoff rolls forward.	If the invoice day is greater than the cutoff day, the anchor moves to the following month end.
End of month plus days	Finds the EOM anchor, then adds calendar days.	The cutoff decision happens before the extra day count.
Specific day of next month	Uses the selected day in the month after the anchor month.	The day is capped at the next month's final calendar day.
Business days	Counts payable dates under the weekend and holiday calendar.	The anchor date counts as day one only when the business-day switch is on and that date is payable.

Invoice due date calendar adjustment behavior
Condition	Behavior	Interpretation effect
Holiday date text	Recognizes ISO dates, YYYY/MM/DD dates, and MM/DD/YYYY dates with optional labels.	Unreadable lines are warned and left out of the calendar.
Duplicate holiday date	Keeps the first matching date and ignores later duplicates.	A closure date is never counted twice.
Move to next business day	Scans forward until a payable date is found.	The final date can be later than the base date.
Move to previous business day	Scans backward until a payable date is found.	The final date can be earlier than the base date.
No adjustment	Leaves the base date unchanged.	A weekend or holiday deadline remains the final due date.
Status date	Compares only with the final due date.	It changes status labels, not the calculated deadline.

As a substitution check, an invoice dated 2026-05-01 with a Net 30 term reaches a base date of 2026-05-31. If Saturday and Sunday are excluded and the adjustment rule moves to the next business day, 2026-05-31 is skipped and the final due date becomes 2026-06-01. A status date of 2026-06-03 would then read as two days overdue.

Accuracy and Privacy Notes:

The calculator applies the dates and rules you enter. It does not decide which contract clause, procurement policy, statutory rule, receipt event, or acceptance event controls a real invoice.

Confirm whether the clock starts at invoice issue, invoice receipt, delivery, acceptance, approval, or another named event.
Use the payer's working calendar when the payer's weekends or holidays differ from the vendor's location.
Keep the source term with the exported summary when the due date affects discounts, late fees, collections, or payment authorization.
The date arithmetic runs in your browser from the entered fields and does not require a server lookup.

Worked Examples:

Net 30 with weekend rollover. An invoice dated 2026-05-01 with Payment term set to Net days and Term days set to 30 reaches a base date of 2026-05-31. With Saturday/Sunday weekends and Move to next business day, the final due date moves to 2026-06-01.

Five business days across a holiday. An invoice dated 2026-05-20 with a 5 business day term, Saturday/Sunday weekends, and 2026-05-25 entered as a holiday skips the weekend and the holiday. The final due date lands later than a simple five-calendar-day count, and the skipped dates appear in Calendar Exclusions.

EOM cutoff after the cutoff day. If an invoice dated 2026-05-20 uses an end-of-month term with an EOM cutoff day of 15, the base date moves to 2026-06-30 because the invoice day is after the cutoff. Any weekend or holiday adjustment is applied after that base date is chosen.

Fixing a holiday warning. A line that contains only "Company retreat" has no readable date token, so it is ignored. Change it to a dated entry such as "2026-07-03 Company retreat" before relying on the exclusion table.

FAQ:

Does Net 30 count calendar days or business days?

In this calculator, Net days counts calendar days. Choose Business days only when the payment term specifically says business days or payable working days.

Can I use receipt date instead of invoice date?

Yes. Enter the receipt, delivery, acceptance, or approval date in Invoice date when that is the anchor your agreement uses, then keep that choice with the payment review.

Why did my final due date move backward?

Due date adjustment is set to Move to previous business day, and the base date landed on a configured weekend or holiday. Change the rule if the agreement rolls forward or leaves excluded dates unchanged.

Why is the status badge different from the due date?

The badge compares Status date with the final due date. It can say not due yet, due today, or overdue without changing the calculated deadline.

Does the calculator know official holidays automatically?

No. Enter the holiday dates that matter for the payer or contract. The calculator only excludes the recurring weekend pattern and the holiday dates you provide.

Glossary:

Anchor date: The date the payment term starts from, such as invoice date, receipt date, delivery date, acceptance date, or approval date.
Base due date: The date produced directly by the payment term before weekend or holiday adjustment.
Final due date: The payable deadline after the selected adjustment rule is applied.
Business day: A date that is not in the configured weekend set and not listed as a holiday.
EOM cutoff: A day-of-month rule that can move end-of-month terms into the following month.
Status date: The review date used to classify the invoice as not due yet, due today, or overdue.

References:

Prompt Payment, Bureau of the Fiscal Service.
Guidelines for Calculating Prompt Payment Interest for Weekends and Federal Holidays, U.S. Department of the Treasury.
Invoicing and taking payment from customers: Payment obligations, GOV.UK.
Late commercial payments: charging interest and debt recovery, GOV.UK.