Invoice date vs due date

Two dates sit near the top of almost every invoice. One says when you issued the document. The other says when the client should pay. Mix them up, leave one blank, or invent a due date that does not match the Net term you agreed, and payment gets delayed for a reason that looks trivial until you are the one chasing it.

Invoice date (issue date)

The invoice date is the day you create and send the bill, or the day you treat as the official issue date if you batch invoices. It is the starting point for Net terms. Net 30 from 13 September is due 13 October, not 30 days from when the work finished, and not 30 days from when the client opens the email.

• Use a real calendar date, not “September” or “week 37”.
• Keep the invoice date and the email send date close. A PDF dated three weeks before you actually sent it looks like you sat on the bill.
• If you bill after delivery, the invoice date can still be the day you issue the PDF. The delivery date belongs in the line description or notes if the client needs it.

Due date

The due date is the last day payment is on time. Put it in the due date field as a date, and restate the term in the notes so a reader who only skims still sees both. “Net 30” alone forces someone in accounts payable to do arithmetic. Most of them will not do it in your favour.

Common pairings:

• Due on receipt. Due date equals invoice date, or the next business day. Honest for small clients; large ones often treat it as Net 30 anyway.
• Net 7 / Net 14 / Net 30 / Net 60. Count that many days from the invoice date. Confirm whether your client counts calendar days or business days. Calendar days are the default in most B2B settings.
• End of month terms. Net 30 EOM stretches the wait. Read payment terms explained before you agree to it.

How Net terms turn one date into the other

Worked example. Invoice date 13 September 2026, term Net 30:

Note wording you can paste: “Payment due within 30 days of the invoice date, by 13 October 2026. Please quote INV-2140 as the payment reference.”

If the due date lands on a weekend or public holiday, say whether you expect payment on the last working day before or the first working day after. Silence here creates “we thought Monday was fine” arguments.

More Net examples (calendar days)

Count from the invoice date, not from “when they said they would approve it.” If approval is slow, you still issued on a real day; the due date follows that day unless you both agree in writing to reset it.

Service period is not the invoice date

Clients often need a service or delivery window on the PDF (“Design work, 1-31 August 2026”). That window belongs in the line items or notes. It is not a substitute for the invoice date field. Mixing them up makes Net arithmetic look wrong and can confuse tax period reporting on their side.

Write lines so the period is obvious; writing invoice line item descriptions has patterns that survive a PO match.

Mistakes that look like late payment

• Due date blank. The client has no hard date to put in their payment run.
• Due date before the invoice date. Looks like a typo. Fix it before you send.
• Net 30 in the notes, due date set to Net 14. Your spreadsheet and their AP system will disagree. Pick one story.
• Backdating the invoice date to start the Net clock earlier. Tempting after a delay on your side. Risky if the client notices, and messy for your own records. Better to send promptly next time.
• Using the project start date as the invoice date. The clock for payment should start when you bill, unless you both agreed otherwise in writing.

Deposits and staged work

A deposit invoice still needs both dates. The due date is often sooner (due on receipt or Net 7) because you are waiting on that payment before you start. The balance invoice gets its own invoice date and its own due date. Do not reuse the deposit’s due date on the final bill. More on that pattern in how to invoice a deposit.

When you revise or reissue

If you void a bad invoice and send a corrected one, give the new PDF a fresh invoice date (usually today) and recalculate the due date from that new issue date unless the client agreed to keep the original due date. Say which choice you made in the cover email. Number history and credit notes are covered in revising or voiding an invoice.

What to put in your own records

Keep the invoice date, due date, send date, and paid date as four separate facts. When something is late, you want to know whether the client missed the due date or whether you sent the PDF late. That split also helps when you write a polite follow-up; see overdue invoice email wording.

Checklist before you export the PDF

• Invoice date is filled and matches when you are sending.
• Due date is filled and matches the agreed term.
• Notes restate the term in plain words, with the same due date.
• Service period (if needed) sits in lines or notes, not in the issue date field.
• Currency and payment details are present so they can pay on time.

Build the file in the browser invoice generator or start from the freelance invoice template. The Today chip sets the issue date, and the Due on receipt and Net chips fill in the due date from it. There is no paywall; labelled ads keep FreeInvoicePDF running. Pair the dates with clear payment methods on the invoice so the due date is actually usable.