Invoice Date vs. Service Date vs. Due Date: Three Dates, Three Jobs
An invoice carries three dates that readers constantly merge: the service date (when the work was done), the invoice date (when the document was issued), and the due date (when payment is expected). They are often three different days, and putting the right one in the right place is what makes terms like “Net 15” mean anything at all.
One scenario, three dates
Where each date lives on the document
- Service date — inside the line item description: “Deep clean, Nov 4”. This is the customer's memory anchor; it is how they verify the charge is real.
- Invoice date — in the document header, labeled as the issue date. Payment terms are counted from this date unless your agreement says otherwise — which is why issuing promptly is worth money (see the scenario: three days of due-date drift from one paperwork habit).
- Due date — printed as an actual date, not only as “Net 15”. Terms codes are fine for regulars; a calendar date is what a customer puts in their diary. The maker prints the due date when you set one and a dash when you do not — it never invents terms you did not agree.
The discipline that ties them together: the service date is history, the invoice date is the starting gun, the due date is the promise. If a line's service period spans weeks — consulting, a retainer — name the range in the description (“Nov 3–28”) the way hourly consulting invoices do it. And keep all three dates in your payment log; they are what turn “I think that one's late” into a factual, polite follow-up.
Set the dates deliberately on your next one: open the maker — issue date defaults to today, due date is yours to choose, and the service date goes in the line where the customer will look for it.
A worked timeline, start to finish
Notice what the example does not do: the invoice is not backdated to Nov 3 to make the paperwork look tidier. Backdating an issue date is the one date sin worth naming — it falsifies the record of when a document was created, and it unravels the moment a message thread or a file timestamp disagrees with it. An honest two-day gap between delivery and paperwork is a non-event; a discovered backdate is a credibility event. Create documents on the day you create them, let the description carry the service date, and the timeline always defends itself.