Invosmith

Invoice Due Dates: How to Set and Explain Payment Dates

An invoice due date tells the customer when payment is expected under the agreement. The issue date says when the invoice was created; the due date may be a calendar date, a Net term counted from issue, or a milestone date. The contract and applicable local rules control the wording.

01

Issue date and due date are different

The issue date identifies when the invoice was made. The due date identifies when payment is expected. Put both on the document when the agreement uses both concepts.

02

Choose the date from the agreement

Check whether the job uses a deposit, progress stage, delivery, acceptance, or final-payment trigger. If it says Net 15, write the resulting date and keep the term visible. Do not silently replace a negotiated date with a generic default.

03

Explain grace periods carefully

A grace period may be a contract or policy choice, not an automatic right. State what happens after the date and link to the agreed payment terms. Avoid promising that a late fee is enforceable everywhere.

04

An illustrative calendar example

If an illustrative invoice is issued on 1 September with Net 15 terms, the example due date is 16 September. Confirm local counting rules and the actual agreement before sending.

Frequently asked questions

Is the issue date the due date?

Not necessarily. They are separate fields unless the agreement makes them the same.

What is Net 30?

It describes a payment period counted from an agreed starting event; verify the contract and local practice.

Is a grace period automatic?

No universal grace period applies. Follow the agreement and applicable rules.

Where can I find follow-up steps?

See the past-due invoice guide for a factual follow-up workflow.

Related

Write invoice payment termsFollow up on a past-due invoiceCreate an invoiceDownload a template

Use the date your agreement supports; do not present this guide as jurisdiction-specific legal advice.

Create an invoice