Net 30 Or Net 60 Due Dates
Net 30 and Net 60 are payment terms that state the invoice amount is due 30 or 60 days after a defined starting point. The starting point is the part that often gets glossed over in purchase orders and invoices, and it drives the real due date. For example, a seller may write “Net 30 from invoice date,” while a buyer’s contract may say “Net 30 from receipt of goods.” Those two phrases can shift the due date by weeks.
In practice, many disputes come down to which document controls the start date and which event counts as the trigger. A purchase order may reference one term, the invoice may display another, and the contract may define a third. When the documents disagree, the “payment really due” question becomes a contract interpretation problem, not an accounting problem.
One small detail matters: some invoices show “Invoice Date” and “Due Date” fields, but the due date may be calculated using the seller’s internal rule set. If your ERP exports invoices with a due date based on “invoice date + 30,” the buyer’s accounts payable team may still treat the contract as “receipt + 30,” which is where the mismatch begins. I’ve seen this happen with systems that stamp due dates automatically (for instance, QuickBooks Online invoice due dates) even when the underlying agreement says otherwise.
Common Payment Term Pitfalls
People often assume Net 30 means “30 days after you receive the invoice,” but the term does not specify the trigger by itself. Net 30 is a label; the contract language defines the clock. If the agreement says “Net 30 from invoice date,” then the due date can arrive before the buyer even receives the invoice, depending on mail time or electronic delivery timing.
Another frequent mistake is treating the invoice date as the same thing as the service delivery date. For goods, delivery and acceptance can be separate events. A contract may require inspection and acceptance before payment starts, while an invoice may be issued earlier. If the buyer pays based on invoice date, the buyer may pay before acceptance, and later deductions for defects can become harder to justify.
Supporting dependencies also matter. Accounts payable workflows often depend on document matching rules such as 3-way match (purchase order, receiving report, and invoice). If the receiving report posts later than the invoice, the AP system may hold the invoice, but the due date field might still show the earlier calculated date. That creates a situation where the invoice is “on hold” yet technically past due on paper, which can trigger late-fee language if the contract ties fees to the due date rather than actual payment timing.
Even the definition of “day” can cause friction. Some contracts count calendar days, others count business days, and some exclude weekends and holidays. If your agreement is silent, the default interpretation can vary by jurisdiction and contract drafting style. A clause that says “Net 30” without clarifying calendar vs business days is a common source of avoidable arguments.
How To Interpret The Start Date
Check The Controlling Document
Start by identifying which document governs: the master agreement, the purchase order terms, or the invoice terms. If the master agreement defines “Net 30 from receipt of goods,” but the invoice says “Net 30 from invoice date,” you need to resolve the conflict using the contract’s order-of-precedence clause. Many agreements include language like “in case of conflict, the purchase order prevails” or “the master agreement controls.” If you cannot find that clause, ask for written clarification before paying.
For a practical audit trail, save the exact PDF or email thread showing the term language. I’ve seen teams rely on a screenshot of the invoice terms, then lose the original email that carried the purchase order acceptance. In one case, the invoice terms were updated in a later version (version 2.1 of a vendor template) without notice, and the buyer’s AP team had no way to prove what was agreed.
Map The Trigger To A Date
Once you know the trigger, map it to a specific date in your records. Common triggers include “invoice date,” “invoice receipt date,” “shipment date,” “delivery date,” “receipt of goods,” “acceptance,” or “end of month.” “End of month” terms behave differently: “Net 30 EOM” often means 30 days after the end of the month in which the invoice was issued, not 30 days after the invoice date.
Use your system’s timestamps carefully. If you receive invoices through a portal, the “received” date may be the portal submission date, not the day someone in your organization opened the invoice. If you receive invoices by email, the “receipt” date may be the email arrival time in your mail server logs. When you dispute a due date, you’ll want the same definition on both sides.
Confirm Due Date Calculations
Ask the vendor how they calculate the due date when they print it on the invoice. Some vendors calculate due date as “invoice date + 30 calendar days,” while others calculate “invoice date + 30 business days,” and some use “terms from receipt” but still print a due date based on invoice date. If the invoice includes a due date field, compare it to your contract’s trigger and count method.
In many accounting systems, due dates are calculated automatically. For example, if your AP tool uses a rule like “Net terms days added to invoice date,” it may ignore a contract clause that says “receipt + 30.” That mismatch can be fixed by changing the AP rule mapping or by adding a manual override date when the receiving report posts. The fix is process, not just paperwork.
Document Disputes Early
If the due date seems wrong, raise the issue before the invoice becomes past due. A common approach is to send a written notice that identifies the contract clause, states the correct trigger, and requests an updated due date or payment schedule. If you plan to withhold payment for quality or quantity issues, tie the withholding to the contract’s dispute or deduction process rather than to a general “we don’t agree” statement.
Keep the communication factual: invoice number, invoice date, delivery/receipt date, and the exact clause language. Mild frustration is normal, but avoid emotional wording; it rarely helps when the dispute moves to collections or legal review. If the contract includes late fees, ask whether late fees will be paused during the dispute period.
Educational Case Examples
Scenario 1 (Goods, conflicting triggers): A buyer receives a shipment on March 10 and signs the receiving report on March 12. The master agreement states “Net 30 from receipt of goods.” The vendor issues the invoice on March 1 and prints “Due Date: March 31.” The buyer’s AP team notices the due date is earlier than March 12 + 30 days. The buyer sends a notice citing the master agreement and requests an updated due date based on receipt of goods. The vendor updates the invoice terms in a revised invoice and the buyer pays on the corrected schedule.
Scenario 2 (Services, end-of-month term): A contractor provides monthly services. The contract says “Net 60 EOM.” The vendor invoices for April services on April 5. The buyer’s AP system initially calculates due date as “invoice date + 60,” which lands in early June. The contract’s EOM rule means the clock starts at April 30, so the due date should be around June 29 or June 30 depending on the contract’s day-count method. The buyer corrects the due date rule for this vendor and documents the calculation method for future invoices.
Net 30 Vs Net 60 Checklist
| Decision Point | What To Look For | Why It Changes The Due Date | What To Do Next |
|---|---|---|---|
| Trigger | Invoice date vs receipt vs acceptance | Different start events shift the clock | Quote the clause and map to your records |
| Day Count | Calendar days vs business days | Weekends/holidays change the due date | Confirm the contract’s counting method |
| Order Of Precedence | Master vs PO vs invoice terms | Conflicts can flip the controlling language | Follow the precedence clause in writing |
| System Calculation | How AP software sets due dates | Auto rules may ignore contract triggers | Test one invoice and document the rule |
| Dispute Timing | When to notify about errors | Late fees may start at due date | Send a written correction request early |
Step-by-step checklist:
- Find the clause that defines the start event for Net 30 or Net 60.
- Identify the controlling document using the contract’s order-of-precedence language.
- Pull the relevant dates from your records (invoice date, receipt date, acceptance date).
- Count days using the contract’s calendar vs business-day rule.
- Compare your calculated due date to the vendor’s printed due date.
- If they differ, request a corrected invoice or a written confirmation of the calculation.
- Document the resolution so future invoices follow the same interpretation.
Common Mistakes That Create Fees
One mistake is paying based on the invoice due date field without checking the contract trigger. If the due date was calculated from invoice date but the agreement starts from receipt, the buyer may pay early or miss a deduction window tied to acceptance. Another mistake is assuming that “Net 60” automatically means “60 days after receipt,” which fails when the contract uses invoice date or shipment date.
Teams also miss the effect of partial deliveries. A contract may allow invoicing per shipment, while the buyer’s receiving report posts in batches. If the due date is tied to each delivery, the buyer needs a process that links each invoice line to the correct receiving event. Otherwise, the buyer may treat one invoice as due later while the vendor treats it as due earlier.
Late fees and interest clauses can be drafted tightly. Some agreements charge interest on the unpaid balance starting the day after the due date, even if the invoice is under dispute. If you expect to dispute, you need to follow the contract’s dispute notice procedure and timing. A vague email like “we will review this” rarely stops fees if the clause requires a formal notice.
Finally, people sometimes ignore document versioning. Vendor portals can update invoice terms, and purchase order attachments can be replaced. If you rely on a single PDF downloaded months later, you may not have the exact wording that governed the original transaction.
FAQ
Does Net 30 Mean 30 Days From Invoice Date?
Net 30 states a 30-day payment period, but the due date depends on the contract’s defined trigger. Many agreements specify “from invoice date,” while others specify “from receipt of goods” or “from acceptance.”
What If The Invoice Due Date Conflicts With The Contract?
Use the contract’s order-of-precedence clause to determine which terms control. Then request written confirmation or a corrected invoice that matches the contract’s trigger and day-count method.
Are Net Terms Counted In Calendar Days Or Business Days?
Net terms can be drafted as calendar days or business days. If the agreement does not specify, you may need to rely on jurisdictional contract interpretation and the surrounding drafting context, which is why written clarification helps.
How Do Net 60 EOM Terms Work?
“EOM” typically means the clock starts at the end of the month of the invoice or service period. The exact due date depends on the contract’s day-count method and whether it counts calendar days after month-end.
Can Late Fees Start During A Payment Dispute?
They can, depending on the contract language and whether you follow the dispute notice procedure. Some contracts pause fees during a properly noticed dispute; others do not.
Author's Insight
Net 30 and Net 60 look simple, but the due date is a product of contract wording plus how your systems record dates. The most reliable approach is to treat the trigger (invoice date, receipt, acceptance, or EOM) as the primary variable, then verify the day-count method. When disputes arise, the strongest evidence usually comes from the exact clause text and the date stamps from receiving and invoice delivery records. If your AP software auto-calculates due dates, test one invoice end-to-end and document the rule so the team does not repeat the same mismatch.
Key Takeaways
- Net 30 and Net 60 define a time window, but the contract defines the start event that sets the due date.
- Invoice due dates can be calculated from different triggers than the agreement uses.
- Confirm calendar vs business-day counting and any EOM rules before paying.
- Document the controlling clause and the relevant dates, then request a corrected due date early if there’s a mismatch.
