WhenMathNet Terms Invoice Planner
Turn a payment term such as Net 30 into an actual due date, plus a set of reminder dates counted back from it. Choose whether the term counts calendar days or business days. This does not determine whether any specific invoice is legally payable.
Worked example
An invoice dated January 1 under Net 30 counted in calendar days is due January 31, since 30 calendar days simply advances the date by 30 regardless of weekends. The same Net 30 counted in business days instead skips every Saturday and Sunday along the way, landing on a later calendar date because roughly nine of those 30 days fall on a non-business weekend. Choosing the wrong convention for a specific vendor relationship can shift the real due date by more than a week, which is exactly why the counting convention needs to be confirmed rather than assumed from the number alone.
Common mistakes
- Assuming Net 30 always means calendar days. Business-day terms are common in some industries and produce a meaningfully later due date.
- Setting a reminder offset larger than the terms count itself, which lands the reminder before the invoice date. This tool still computes it, but the result likely does not reflect what was actually intended.
Limitations
This applies the exact terms and convention you enter. It makes no determination about whether an invoice is legally enforceable, whether a specific payment is actually owed, or how any dispute over payment terms should be resolved.
Frequently asked questions
- Can I set more than two reminder dates?
- Yes, enter as many comma separated day offsets as needed and each one generates its own reminder date counted back from the due date.
- Does this roll the due date forward if it lands on a weekend?
- No, the due date itself is shown exactly as computed, and the receipt states plainly whether it falls on a business day or not, leaving any rollover decision to you.