Two words on an invoice, “NET 30”, can mean anything from 30 to more than 42 days depending on one unspoken assumption: whether the count is in calendar days or business days. The same ambiguity sits inside shipping promises, notice periods, cure windows, and payroll cut-offs. Most of the time nobody notices, because the two readings happen to produce a similar date. Then one deadline lands during a run of weekends and a public holiday, the two sides disagree by a week, and a clause that felt precise turns out to have meant two different things all along. This is what the distinction actually is, why it widens far more than people expect, and how to write a date obligation that resolves to exactly one answer.
The plain definition, and why it is not as simple as it sounds
A calendar day is any day at all. You count Monday through Sunday, holidays included, and 30 calendar days after the 1st of a month is simply the 31st of that month or a day or two into the next one. There is nothing to interpret. A business day, sometimes called a working day, is a day on which normal commercial operations run. In the standard model that means Monday to Friday, excluding Saturday and Sunday, and excluding public holidays observed at the relevant location.
The catch is hidden in that last phrase, “at the relevant location”. Calendar days are universal. Business days are local. The set of dates you remove depends on which country's weekend and which country's holiday list you apply, and those vary a great deal. So a business-day count is only well defined once you have named the calendar it runs against. A calendar-day count needs no such qualifier. That single asymmetry is the root of nearly every dispute in this area.
How NET 30 quietly becomes 42 days or more
Take the common case that trips people up. A vendor issues an invoice and the terms say payment is due in 30 working days. Thirty working days is six five-day weeks with nothing removed. Six weeks is 42 calendar days on its own, because each working week you count off drags a weekend along behind it. Add even one public holiday inside that stretch and a second working day slides forward, pushing the real due date to 43 calendar days or beyond.
So a supplier who reads NET 30 as 30 business days genuinely believes the payment is on time when it arrives six weeks and a couple of days after the invoice. A buyer who reads the same NET 30 as 30 calendar days considers that payment nearly two weeks late and may apply a penalty. Neither party is acting in bad faith. They are counting in different units, and the contract never said which one to use. The commercial convention is that NET terms are calendar days, but convention is not enforceable and does not survive a determined disagreement. If you want to see the exact calendar-day gap between an invoice date and any due date, the invoice due date calculator settles it in one step, and the days between dates calculator gives you the raw calendar span between any two dates.
The rule of thumb worth memorising
You do not need a table for the everyday estimate. A five-day working week removes two days from every seven, so across a full 30 or 31 day month you land on about 21 to 23 weekdays before holidays. The exact figure swings by one or two depending on which weekday the month starts on, because a month either contains four weekends or five. A 30-day span is always four weeks plus two days: if those two spare days include a Saturday and Sunday you lose ten weekend days and keep 20 weekdays, and if they do not you lose eight and keep 22.
From there the mental model is easy. Roughly speaking, a working month is about three weeks of working days plus change, and every calendar week you count in business days costs you an extra weekend in real time. Multiply working days by seven-fifths to get a first estimate of the calendar span, then subtract for holidays. For anything that carries money or a legal consequence, do not rely on the estimate: the working days calculator counts the exact business days between two dates for a chosen country, holidays included, so the answer is defensible rather than approximate.
Why a global contract must name the calendar
Public holidays are the part people forget, and they are precisely the part that makes business days a moving target across borders. Holidays are declared by each country, and frequently by each region within a country, so no two national working calendars line up. A stretch of dates that contains no holidays in one country might contain two in another. The result is that “10 business days” is not one duration; it is a different duration in every jurisdiction, and it resolves to a different final date for each side of a cross-border deal.
Consider a contract between a company in one country and a supplier in another, with a clause promising delivery within 15 working days. If the two countries observe different public holidays during that window, the buyer counts to one date and the supplier counts to another, and both are correctly applying their own local calendar. Neither is wrong. The contract is wrong, because it delegated the count to a calendar it never specified. The fix is a single sentence naming the governing calendar, for example “working days as observed in Germany” or “excluding public holidays in the state of New York”. Once the calendar is named, the count has exactly one answer for everyone.
The weekend itself is not universal either. The Monday-to-Friday working week is common but not global; in several countries the customary rest days fall on different days of the week. A business-day obligation anchored to one of those countries skips a different pair of days, so a global agreement cannot assume the weekend it grew up with. This is one more argument for naming the calendar rather than leaving the reader to supply their own.
The ambiguity trap: “within 10 days”
The most expensive version of this problem is the shortest. A clause that says only “within 10 days” has not chosen a unit, and the two readings diverge by the full weight of the intervening weekends. Ten calendar days from a Friday is the following week's Monday. Ten business days from the same Friday runs to roughly two weeks out, once both weekends drop away and any holiday is removed. That is a gap of several days on an obligation that was meant to be exact.
When the deadline governs something with teeth, the gap stops being a curiosity. A notice period, a right to cancel, a cure window for a breach, a deadline to reject faulty goods: each of these hangs on a date, and an unqualified “days” means the two parties may compute different dates for the same event. In a dispute, the ambiguity tends to be read against the party who drafted it, which is a poor outcome to inherit from a missing word. The remedy costs nothing at drafting time: write “calendar days” or “business days” every single time, and never let a bare “days” carry a deadline.
Where each unit is the right choice
The two units are not competing; each fits a different kind of obligation, and the skill is matching them.
Reach for calendar days when the clock should run regardless of whether anyone is working. Long payment terms, subscription renewals, statutory limitation periods, and warranty durations are naturally calendar-based, because the underlying entitlement does not pause for a weekend. Calendar days also carry the practical virtue of being unambiguous across borders: 30 calendar days is 30 calendar days in every country, with no holiday calendar to reconcile.
Reach for business days when the obligation depends on someone actually doing work: processing a return, reviewing a document, releasing funds, or responding to a notice. It would be unfair to count a bank holiday against a party who could not act on it, so response and processing windows are usually written in working days. The price you pay is that you must now name the governing calendar, because a business-day count without a stated location is not fully defined.
Business days on both sides of the payroll and SLA line
Two everyday systems show the units colliding in practice. Payroll runs on business days at its edges: pay is often dated to the last working day of a period, and when a scheduled pay date lands on a weekend or holiday it is typically moved to the nearest working day. Yet the pay period those wages cover is measured in calendar days. The same payslip therefore mixes a calendar-day span with a business-day payment date, and a team that forgets the distinction mis-forecasts its own cash-out date.
Service-level agreements have the same seam. A support promise of “resolution within two business days” deliberately excludes weekends, so a ticket raised late on a Friday is not breached until well into the following week. Read that as calendar days and you will report a breach that never happened; read it as business days and you have to know the provider's holiday calendar to compute the real deadline. Any obligation that touches people's time and pay should be priced against working days, which is why a rate that has to convert an annual or monthly figure into a defensible day rate should use a working-day basis. The hourly rate calculator works from actual working days rather than raw calendar days, so the resulting rate reflects the days genuinely worked.
A short drafting checklist
Before any date obligation goes out, run it past these questions:
- Does every deadline state its unit explicitly, “calendar days” or “business days”, with no bare “days” left carrying a consequence?
- For every business-day count, is the governing calendar named, so both sides remove the same holidays and the same weekend?
- Where the parties sit in different countries, does the contract pick one calendar rather than letting each side apply its own?
- Is the unit the right fit for the obligation: calendar days for entitlements that never pause, business days for anything that needs someone to be at work?
- Have you sanity-checked the longest deadline against a real count, so a 30-working-day term is not quietly a six-week term nobody budgeted for?
None of this requires legal expertise, only the discipline to name the unit and the calendar every time. A date obligation that spells out both leaves nothing for the other side to reinterpret later, and that clarity is worth far more than the handful of words it costs.
Frequently asked questions
How many business days are in 30 calendar days?
Roughly 21 to 22, before you subtract public holidays. A 30-day span always contains four full weeks plus two extra days, so it covers either four or five weekends depending on which weekday it starts on. Four weekends removes eight Saturdays and Sundays and leaves 22 weekdays; five weekends removes ten and leaves 20. Take out one or two public holidays that fall inside the window and you are usually looking at 20 to 22 working days inside a calendar month.
Does NET 30 mean business days or calendar days?
By long-standing commercial convention, NET 30 means 30 calendar days from the invoice date, so weekends and holidays are counted. But convention is not a contract. If a supplier or a jurisdiction interprets NET 30 as 30 working days, the money is not late until far more calendar time has passed. The only safe practice is to write the unit into the terms explicitly, for example "payment due within 30 calendar days of the invoice date", so nobody has to guess.
Which public holidays count when I calculate business days?
Only the ones observed at the location the contract points to. Public holidays are set nationally, and often regionally, so the United States, the United Kingdom, Germany, India, and Japan each remove a different set of dates from the working calendar. A contract between parties in two countries has to name whose holiday calendar applies, or a deadline expressed in business days resolves to two different dates for the two sides.
Is Saturday a business day?
In most of the world, no. The standard five-day working week runs Monday to Friday, and business-day counts exclude Saturday and Sunday. The exception matters for global contracts: in several countries the weekend is not Saturday and Sunday. Where the local rest days differ, a business-day count anchored to that country skips different dates, which is one more reason a cross-border agreement should state which calendar governs it.
What does "within 10 days" mean if the contract does not say?
It is ambiguous, and that ambiguity is exactly the problem. Read as calendar days, 10 days from a Friday lands on the second Monday. Read as business days, the same 10 days runs to roughly two weeks later once the two weekends drop out. When a notice period, a cure period, or a right to cancel hinges on that difference, the gap is not academic. Always qualify the unit, and if you are on the receiving end of an unqualified deadline, confirm the intended reading in writing before you rely on it.