Direct answer
No. Date the invoice the day you issue it, and show the delivery date separately on the record.
The work was delivered, the invoice is ready, and the client asks for a small favour: can you date it last month instead? The request usually sounds harmless, and it often comes from an ordinary need, a budget period, a closing set of books, a manager who wants the cost in the month the work arrived. But an invoice date is not a label you move for convenience. It is a statement by you, on a business record, about when a document was issued, and other people, the client's finance team, their accountant, yours, rely on that statement matching reality. Backdating makes your records say something you know is not true, and it does it in writing, permanently, for a benefit that is almost always the client's rather than yours. The good news is that the honest version gives the client nearly everything they actually need: an invoice dated today, the day it is issued, with the work's delivery dates stated plainly and separately, backed by a delivery record whose dates neither side can quietly move. This page gives you the reply, the honest version line by line, and the fix if a wrong date has already gone out.
Updated November 21, 2026. First published November 21, 2026. The records quoted below are real and public, read back from the live service on November 21, 2026.
Step 1. See what is actually being asked: a false date on your own record
Strip the favour framing away and the request is precise: issue a document today that states it was issued last month. That statement then travels. It lands in the client's accounts for a period that has closed or is closing, it supports a cost being placed in that period, and it sits in your own sales records as the issue date of that invoice, where your totals for last month and this month are built from it. If the two sides' records are ever compared, with the email asking for the change sitting in the same file, the gap is not a grey area, it is a document whose date its issuer knew was wrong. The size of the job does not change this. Small backdates are how the habit forms, and the person carrying the lasting risk is the one whose name is on the invoice, which is you. None of this requires the client to be acting badly: many ask because a previous supplier shrugged and did it, and nobody explained the honest version that solves their actual problem. Explaining it is your job in the reply, once, clearly, without accusing them of anything.
Step 2. Find the real need underneath: period, budget, or paperwork
Ask, or infer from the conversation, which of three needs is driving the request, because each has an honest answer. Period need: the client wants the cost recognised in last month, when the work was delivered, rather than this month, when the invoice arrived. That is a question about the delivery date and their own accounting treatment, and your honest contribution to it is accurate delivery dates, stated on the invoice and proven by the record, not a moved issue date. Budget need: a pot of money existed last month and may not exist now. That is the client's internal problem to solve with their finance team, often solvable with the delivery evidence in hand, and never solvable honestly by your date. Paperwork need: a system, a portal, or a purchase order wants a date that matches its own record. Systems can almost always take the true issue date with the service dates shown alongside, and where a portal genuinely cannot, the escalation belongs inside the client's finance team, not on your invoice. Naming the need in your reply, kindly, is what turns a refusal into help: you are not blocking their month end, you are handing them the dates that actually support it.
Step 3. Issue the honest version: issue date today, delivery dates stated separately
The honest invoice carries both dates, each in its own place, each true. The invoice date, the issue date, is the day you issue it, today. The service or delivery line states when the work was done and delivered: delivered on [date], or the delivery period [start date] to [end date], exactly as your records show. Add the reference that lets anyone check: the job record or delivery reference for the work, so the delivery date on the invoice is not just your assertion but a link to the record made when the work was delivered. This version serves the client's period need better than a backdate does, because an accountant placing a cost in the delivery month needs evidence of delivery in that month, which is the delivery date and its record, and a moved issue date is weaker evidence that creates questions of its own. It also keeps your own books clean in the only way that stays clean under scrutiny: every document dated when it was made, every date on it true, and the sequence of invoice numbers and dates running in order, as auditors and accountants expect to find them.
Step 4. Let the delivery record carry the date that matters
The delivery date does the real work in this conversation, so it should rest on something stronger than either side's say so. A delivery record made as the work happened carries its own dates, saved step by step at the time, and a decision recorded on it by the client. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show what those dates look like in practice:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the accepted record for its dates: the steps checked, the decision recorded as decided_by client at 2026-10-16T14:31:51.146Z, release state ok_to_release. A client whose finance team needs to place work in a period can be handed this: the delivery and acceptance happened on stated dates, on a record neither side edits after the fact. The pending record, 5 steps checked and on hold, shows the same dating before any decision, the work's timeline visible while it is still waiting. This is the answer to give a finance team: not a moved invoice date, but a delivery date with a record behind it, which is the evidence their own rules actually ask for.
Step 5. Send the reply in this shape: no to the date, yes to the need
The reply, word for word in shape: I cannot date the invoice last month, because the date on an invoice states when it was issued, and I keep that true on every document, the same protection your finance team relies on when they read my paperwork. Here is what I can do today: the invoice is issued today, dated today, and it states the delivery date separately, delivered on [date], with the delivery record at [link] showing the work and its acceptance on that date. If your team needs the cost in last month's period, that delivery evidence is what supports it, and I am happy to confirm the dates to them directly in writing. Send the corrected, honest invoice with the same message, so the client is never left holding only a refusal. Most clients accept this in one exchange, because their need was the period, not the falsehood, and you have just handed them better paperwork for it than the favour would have produced.
Honest limits
This page is general information about invoice dating, not tax or legal advice: how issue dates, service dates, and accounting periods interact with tax filings and bookkeeping rules differs by place and by business type, and anything material, a large sum, a closed tax period, a regulated client, deserves your accountant's advice for your situation. The honest version stated here, invoice dated the day it is issued with delivery dates shown separately, is standard honest practice, not a device for moving income between periods, and it should never be used as one in the other direction either. A verifiable receipt proves the saved result was not changed since it was saved; it does not decide which accounting period a cost belongs to, which is a judgement for the client's and your own accountants working from true dates.
Step 6. If a wrong date already went out, fix it on the record, and tighten the habit
If you already issued an invoice with a moved date, perhaps before thinking it through, the fix is documentary, not quiet: cancel or credit the wrong document through your normal invoicing route so the correction itself is recorded, issue the replacement dated the day it is actually issued with the delivery dates stated, and keep the short paper trail that shows what changed and why. A visible correction made promptly reads as exactly what it is, an error fixed, while a wrong date left in place reads, to anyone who finds the asking email later, as a practice. Then tighten the habit that prevents the whole conversation: invoice on delivery, or on acceptance, as a standing rhythm, so your invoices naturally land in the same period as the work and clients rarely need to ask. Put one line in your terms if the requests recur: invoices are dated the day they are issued, with delivery dates stated on the invoice. The line is unremarkable, every honest firm could write it, and having written it in advance turns the next request into a pointer to your terms instead of a fresh negotiation about your records.
Frequently asked questions
My client asked me to backdate my invoice to last month. Should I do it?
No. The date on an invoice states when it was issued, and backdating makes your own business record say something you know is not true, in writing, for a benefit that is usually the client's. Issue the honest version instead: the invoice dated today, the day you issue it, with the delivery date or delivery period stated separately and plainly on the invoice, backed by the delivery record for the work. That version serves the need underneath most requests, placing the cost with the month the work was delivered, better than a moved date does, because the evidence for the period is the delivery date and its record. If the amounts or periods are material, take your accountant's advice for your situation.
Why does the client want a backdated invoice, and what do they actually need?
Usually one of three ordinary needs. A period need: they want the cost recognised in the month the work arrived. A budget need: money existed last month that may not exist now. Or a paperwork need: a portal or purchase order wants a matching date. None of the three needs a false issue date. The period need is met by true delivery dates with a record behind them, which is what their accountant actually relies on. The budget need is theirs to solve internally, often with that same delivery evidence in hand. The paperwork need is normally met by the true issue date with service dates shown alongside. Naming the need kindly in your reply turns a refusal into the help they were actually asking for.
What is the difference between the invoice date and the delivery date?
They state two different facts, and an honest invoice shows both. The invoice date, or issue date, is the day the document is issued, the day you create and send it. The delivery date, or service period, is when the work was done and handed over, which can be days or weeks earlier, especially when invoicing slipped. Confusion between the two is what makes backdating look harmless: it borrows the delivery month's date to do the issue date's job. Keep them separate and labelled, issue date at the top as today, delivery date or period stated in the service line, and every reader, the client, both accountants, any later reviewer, gets both facts true at once.
I already sent an invoice with the wrong date. What should I do now?
Fix it visibly and promptly. Cancel or credit the wrongly dated document through your normal invoicing route, so the correction is itself on the record, then issue the replacement dated the day it is actually issued, with the delivery dates stated separately, and keep the short trail showing what changed. Do not quietly edit the file and resend it as if the first version never existed, because copies travel and the two versions together look far worse than one honest correction. If the sums are large or a tax period has closed in between, ask your accountant how they want the correction documented before you send it. A prompt, recorded fix reads as an error corrected, which is the best available reading and, handled this way, the true one.
How does a delivery record help when a client asks me to move an invoice date?
It gives the delivery date, the date that actually matters for the client's period question, a home neither side can quietly move. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the delivery and acceptance dates sit on the record as they happened, ready to hand to a finance team. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run the job on one record, so its delivery date is already proven on the day the invoice question arrives: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- I forgot to send an invoice for work I finished months ago. Can I still bill the client?
- My client says they never received my invoice. How do I prove I sent it?
- What payment terms should I put on my invoices so clients pay on time?
- A new client wants me to do a free test project before they hire me. Should I do it?
- My client wants me to sign their contract instead of using mine. What should I check?
- Start with your problem: every problem in this directory, routed to its page