Invoice Due Date Calculator

Invoice due date

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 }}

Export to PDF Fullscreen

Include query parameters

Embed:

Customize embed code

Include query parameters

Wrap embed in collapsible toggle

Collapse panel by default

Hide card frame (bare iframe)

Loading behavior

Width

Height

Aspect ratio (width : height)

Max height (optional)

Collapsible heading

Collapsible description (optional)

Allow fullscreen

Referrer policy

Sandbox tokens

Invoice due dates translate payment terms into a calendar deadline. A small wording difference can move that deadline by days or weeks. Net 30 usually counts calendar days from the invoice date, end-of-month terms anchor payment to a month close, and business-day wording skips dates that are not payable workdays.

That date matters for both sides of a transaction. Accounts receivable teams use it to decide when a reminder is still early, when a balance is overdue, and how to explain the term to a customer. Accounts payable teams use it to schedule cash, avoid late-payment friction, and check whether a weekend or holiday should move the final payment date.

Flow from invoice date to base payment term and final due date after optional weekend or holiday rollover

Invoice date calculators are useful because payment terms often mix two ideas: how to find the base date and what to do when that date lands on a non-working day. A due-on-receipt term may stay on the invoice date. A net term may count calendar days. A business-day term may count only payable dates. A weekend adjustment then answers a separate question about moving the final date.

The result is still only as authoritative as the term being modeled. Contracts, purchase orders, government payment rules, and internal finance policies can define the starting date, holiday calendar, and rollover direction differently. Use the calculated date as a clear planning answer, then compare it with the governing agreement when money, penalties, or compliance deadlines are involved.

Technical Details:

A payment term first creates a base due date. Calendar-day terms count every date on the calendar. Business-day terms count only dates that are not in the selected weekend set and are not listed as holidays. Month-based terms use the invoice month as the anchor, then choose the month end or a stated day in the next month.

After the base due date is found, a separate adjustment rule may leave the date alone, move it to the next business day, or move it to the previous business day. This separation is important. Some agreements say "Net 30" and expect the date to stay on the 30th calendar day. Other policies count calendar days first but roll a weekend or holiday deadline to a business day.

Rule Core:

The main rules can be read as a small date pipeline. The term chooses the base due date, then the calendar-adjustment rule decides whether the final date changes.

\begin{array}{lcl} Due on receipt & = & invoice date \\ Net N & = & invoice date + N calendar days \\ EOM & = & last calendar day of the invoice month, unless the cutoff rolls to next month \\ EOM + N & = & EOM anchor + N calendar days \\ Business N & = & N payable dates reached after the invoice date, or from the invoice date when that option is on \end{array}

Invoice due date term behavior
Term path	Base date behavior	Boundary detail
`Due on receipt`	Keeps the invoice date as the base due date.	A final adjustment can still move the date if the invoice date is not payable.
`Net days`	Adds the entered number of calendar days to the invoice date.	The day count is clamped to a whole number from `0` to `3650`.
`End of month`	Uses the last day of the invoice month.	If the invoice day is after the EOM cutoff day, the anchor rolls to the following month end.
`End of month plus days`	Finds the EOM anchor, then adds the entered number of calendar days.	The cutoff rule is applied before the extra days are added.
`Specific day of next month`	Uses the selected calendar day in the month after the invoice month.	Days above the length of that month are capped at month end.
`Business days`	Counts payable dates while skipping configured weekends and entered holidays.	The invoice date counts only when the count-invoice-date switch is on and that date is payable.

The payable-date test is shared by business-day counting and final due-date adjustment. A date passes when its weekday is not part of the active weekend pattern and the date does not appear in the holiday list.

\begin{array}{lcl} payable (d) & = & weekday(d) not in weekend set and d not in holiday set \\ final date & = & base date, next payable date, or previous payable date according to the adjustment rule \end{array}

Calendar and validation behavior
Input or result	Accepted behavior	What it affects
`Weekend days`	Saturday/Sunday, Friday/Saturday, Sunday only, no weekend days, or a custom weekday set.	Business-day counts and next or previous business-day adjustment.
`Holiday dates`	Reads date tokens such as `YYYY-MM-DD`, `YYYY/M/D`, and `MM/DD/YYYY`, with optional labels.	Listed dates are excluded from business-day terms and adjustment scans.
`Status date`	Uses a valid calendar date to compare against the final due date.	Drives the due today, days remaining, and overdue badges.
Unread holiday line	The line is reported in the warning area and ignored for date exclusion.	Fix the date token before trusting a holiday-sensitive result.
Duplicate holiday date	The duplicate is reported and ignored after the first entry.	The same holiday date is counted once.
Long business-day scan	The browser stops after a 25,000-calendar-day safety limit.	Very unusual schedules should be split before use.

The visible date format changes only presentation. The date math uses date-only calendar values, and the structured result keeps the invoice date, base date, final due date, status date comparison, adjustment note, calendar-day span, skipped dates, and warnings together for later checking.

Everyday Use & Decision Guide:

Start with the contract wording or invoice terms exactly as written. If the term says Net 30, choose Net days and enter 30. If it says EOM or EOM plus 30, use the end-of-month options. If it says business days, use Business days and set the weekend and holiday rules before reading the final date.

The weekend adjustment deserves a separate check. Leave the due date unchanged when the invoice term does not mention rollover. Choose next business day when the policy allows a weekend or holiday deadline to move forward. Use previous business day only when the agreement requires payment before a non-working date.

Use Common term for a quick first pass with due on receipt, Net 7, Net 15, Net 30, Net 45, Net 60, EOM, EOM plus 30, the 15th of next month, or 10 business days.
Use Holiday dates when a company holiday, public holiday, or office closure should block payment processing.
Use EOM cutoff day when invoices issued late in a month should be pushed to the next month-end cycle.
Use Status date to answer whether the invoice is due today, still has days remaining, or is already overdue.
Open Term Walkthrough when you need to explain the base date, final date, adjustment note, and calendar span to someone else.
Open Calendar Exclusions whenever a business-day result lands later than expected.

A common mistake is treating every "30" as the same 30 days. Net 30 adds 30 calendar days to the invoice date in this calculator. EOM plus 30 starts from a month-end anchor first. A 30-business-day term skips configured weekends and holidays, so it can land much later than either calendar-day version.

Before copying the invoice term summary, compare Payment Snapshot with the warnings. If the status date is invalid, a holiday line was not read, or the weekend pattern does not match the payer's calendar, fix that input before sending the due date onward.

Step-by-Step Guide:

Use the payment term to find the base date first, then decide whether business-day adjustment applies.

Enter Invoice date. Use the issue date, receipt date, or accepted invoice date required by the agreement you are checking.
Choose Payment term. Enter Term days for net, EOM-plus, or business-day terms, or enter Day of next month for a fixed next-month due day.
Set Weekend days. Pick a preset or choose custom weekdays if the payer's workweek is not Saturday/Sunday.
Choose Due date adjustment. Leave unchanged, move to the next business day, or move to the previous business day based on the governing payment rule.
Open Advanced if you need a common-term shortcut, manual holiday dates, a status date, an EOM cutoff day, or the business-day option that counts the invoice date as day one.
Clear warnings before using the result. Unread holiday lines, duplicate holiday dates, or an invalid status date can make the status badge or exclusion list incomplete.
Read the headline due date, then check Term Walkthrough to confirm the invoice date, base calculated date, final due date, payment status, and calendar span.
Use Payment Snapshot or JSON only after the visible date, adjustment note, and excluded-date list match the payment term you intended to model.

Interpreting Results:

The headline due date is the final date after the selected term and adjustment rule. For audit work, also read Base calculated date and Adjustment note. Those two fields show whether the payment term itself produced the final date or whether weekend or holiday rollover moved it.

Do not treat Calendar days from invoice as a business-day count. It is the total calendar distance from invoice date to final due date. For business-day terms, the skipped weekends and holidays appear in Calendar Exclusions so you can see why the final date moved through the calendar.

How to interpret invoice due date outputs
Output	Meaning	Check before using it
`Due date`	The final payment deadline after the term and adjustment settings.	Compare it with `Base calculated date` when rollover is enabled.
`Payment status`	Due today, not due yet, or overdue as of the selected status date.	Confirm the status date before using an overdue or days-remaining badge.
`Adjustment note`	Explains whether the base date stayed unchanged or moved to a business day.	Verify that next-day or previous-day movement matches the agreement.
`Calendar Exclusions`	Dates skipped because they were configured weekends, holiday dates, or both.	Scan this table when a business-day due date seems late.
`Copyable invoice term summary`	A short sentence combining invoice date, due date, term badge, payment status, and adjustment note.	Use it after warnings are clear and the term wording has been checked.

A clean result proves the calculation matched the inputs. It does not prove the selected calendar is the official calendar for a contract, public-sector payment rule, or customer portal. When the date affects late fees, discount windows, supplier performance, or compliance reporting, verify the starting date, holiday list, and rollover direction against the source document.

Worked Examples:

Net 30 with weekend rollover

An invoice dated May 1, 2026 with Net days set to 30 has a base calculated date of May 31, 2026. Because that date is a Sunday on a Saturday/Sunday weekend calendar, choosing next business day moves the final Due date to June 1, 2026. The Adjustment note is the field to copy when the recipient needs to know why the date moved.

Late-month EOM cutoff

A supplier issues an invoice on February 25, 2026 and uses EOM terms with an EOM cutoff day of 20. The base month-end anchor rolls to March 31 because the invoice date is after the cutoff. With End of month plus days and 30 term days, the base calculated date becomes April 30, 2026 before any weekend or holiday adjustment is considered.

Business days with a manual holiday

An invoice dated Friday, May 1, 2026 uses a 10-business-day term on a Saturday/Sunday weekend calendar. If May 4 is entered as a holiday and the invoice date is not counted as day one, the final Due date becomes May 18, 2026. Calendar Exclusions should show the weekend dates and the May 4 holiday that pushed the count forward.

Troubleshooting an unexpected status badge

If Days until due says the status date is needed, the due date calculation may still be valid but the status comparison is not. Enter a valid Status date, then recheck Payment Snapshot. If the badge changes from unavailable to overdue, due today, or days remaining, the status issue was separate from the due-date math.

FAQ:

Does Net 30 mean 30 business days?

Not in this calculator. Net days adds calendar days to the invoice date. Use Business days only when the payment term explicitly counts payable business dates.

Why did the final due date move from the base calculated date?

The Due date adjustment setting moved the base date because it landed on a configured weekend or holiday. Choose Leave unchanged if the agreement does not allow rollover.

Can I add holidays for my country or company?

Yes. Paste one holiday per line in Holiday dates. The parser accepts ISO dates, slash-separated year-first dates, and U.S.-style month/day/year dates with optional labels.

Why is one holiday line ignored?

The warning area reports unread holiday lines and duplicate dates. Fix the date token or remove the duplicate, then check Calendar Exclusions again.

Does the status date change the due date?

No. Status date only compares the final due date with another date so the result can say due today, overdue, or how many days remain.

Is this a legal or accounting decision tool?

No. It applies the term, weekend, holiday, and adjustment rules you enter. Review the contract, purchase order, customer portal, or applicable payment law before treating the result as an official deadline.

Glossary:

Base calculated date: The date produced by the selected payment term before final weekend or holiday adjustment.
Business day: A date that is not in the selected weekend set and is not entered as a holiday.
EOM: End of month. In this calculator, it means the last calendar day of the invoice month unless the cutoff rule rolls the anchor forward.
Final due date: The date to use after the base payment term and selected adjustment rule have both run.
Payment status: The comparison between the final due date and the selected status date.

References:

Intuit QuickBooks Support, "Set up payment terms," accessed April 29, 2026. https://quickbooks.intuit.com/learn-support/en-us/help-article/pay-bills/set-payment-terms/L8BhXHl35_US_en_US
Xero Canada, "Invoice payment terms: what to include and common terms," accessed April 29, 2026. https://www.xero.com/ca/guides/invoice-payment-terms/
U.S. Bureau of the Fiscal Service, "Prompt Payment: FAQs," accessed April 29, 2026. https://www.fiscal.treasury.gov/prompt-payment/faqs.html