Direct answer

Approval is the client's decision about the work. The invoice is a fact about it.

Waiting for approval before invoicing feels polite and costs you weeks: the client's slow decision becomes your late payment. Here is how to invoice on delivery, honestly, with the pending acceptance state shown on the record instead of hidden, plus the follow-up that turns silence into a decision.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 20, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.

Two clocks, and they are not the same clock

Approval and payment feel linked because they usually happen in the same week. Underneath, they are different events. Delivery is your act: the final draft exists, it was sent, and it can be shown. Approval is the client's act: they checked the work and decided. Payment terms in most agreements run from delivery or from the invoice date, not from whenever the client gets around to deciding. When approval stalls, freelancers stall the invoice with it, out of politeness, and convert a client's slow decision into their own late payment. The invoice was never the thing that needed permission.

First, make sure the draft is provably delivered

Before invoicing, answer one question with evidence instead of memory: can you show when the final draft reached the client, and in what state? A sent email shows a send. A delivery record shows more: each step of the work, saved as it happened, with the client's decision state written on the same record. That state is the honest center of this whole situation. It does not hide the missing approval; it displays it, dated, next to the finished work. The two public records below show both ends of the story:

Still open: delivered, checked, and waiting on the client

Accepted: this stage is a settled fact, not a claim

The first record is your situation, photographed: the work is complete, every step checked, and the decision is still the client's to make, marked hold until they make it. The second is the same record after the client decided: accepted, by the client, on a stated date, with the release marked ok_to_release. Your invoice belongs next to the first kind of record, pointing at it, so the client sees the finished work and their own open decision in the same place.

Send the invoice now, and say the quiet part on it

The invoice itself needs three references most final invoices lack: the delivery date, the record link, and the acceptance state in plain words (approval pending, review window closes on this date). That last line is what makes early invoicing fair rather than pushy. You are not pretending the client approved something they have not. You are billing for delivered work while their decision stays visibly open, with the flag route right there if something is wrong. Clients pay invoices like this because there is nothing in them to argue with.

The nudge that actually gets a decision

Most unapproved drafts are not disputed; they are buried. The follow-up that works makes deciding cheaper than ignoring: one message, the record link, and two doors. Door one, accept, which takes a click on the record. Door two, flag the specific step that is wrong, which turns a vague unease into a fixable item. Name the date the review window closes. A client who flags a step has given you a small, finishable job; a client who accepts has closed the loop; and a client who does neither has let the window you both agreed on run out, which is itself an answer.

When the answer lands

If approval arrives after the invoice, nothing needs reissuing: the acceptance lands on the same record the invoice already points at, and the file is complete. If a flag arrives, fix that step, deliver the correction as its own recorded step, and let the client accept the corrected record; the invoice stands, because the work it bills for was delivered on the date it says. The one outcome to refuse is the renegotiation of the whole job from a single flagged step. A flag is about a step. Keep it about the step.

What this page does not settle

If your written agreement makes approval a condition that comes before invoicing or payment, that agreement governs, and no general page overrides it. Approval windows, review duties, and late-payment routes vary by contract and by place. This page is general information, not legal advice. A verifiable receipt proves the saved result was not changed since it was saved. It does not prove the work was good, and an acceptance recorded by the client is a decision state, not praise. Zambo never holds your money or the client's.

Frequently asked questions

My client has not approved the final draft. Can I still send the final invoice?

Yes, in the normal case. An invoice is a statement of what was delivered and what it costs; approval is the client's decision about the work, and the two run on different clocks. Send the final invoice when the final draft is delivered, reference the delivery date and the delivery record on it, and note the acceptance state honestly: approval still pending. One exception governs everything: if your written agreement makes client approval a condition that comes before payment, that clause is the deal you made, and the fix is to chase the decision, not to bill around it. Read the agreement once, then send the invoice.

Does invoicing before approval damage the relationship?

Done plainly, it does the opposite. An invoice that arrives with the delivery record attached, and that says approval is still open and here is the link to accept or flag the work, reads as an organized business closing its own loop. What damages relationships is the other pattern: waiting silently for weeks, then invoicing with accumulated frustration, so the client receives a bill and a grievance on the same day. Invoice on delivery day, while the work is fresh in front of both of you.

What if the client never approves and never says why?

Treat silence as a missing decision, not as a rejection, and make the decision smaller. Send one short message with the record link and exactly two doors: accept the work, or flag the specific step that is wrong, by a named date. A named step gets fixed and re-accepted. A general silence after that date is answered by your agreement: if it carries a clause that unflagged work counts as accepted after a set number of days, the clause now runs. If it does not, the pending state itself is your documented position, and the invoice stands on the delivery record while you escalate through the unpaid-invoice sequence.

How long should I wait for approval before following up?

Follow up on the rhythm you set at delivery, not on a rhythm invented by anxiety. A workable pattern: the delivery message names the review window, a short nudge goes out halfway through it with the record link, and the two-doors message goes out on the final day. Busy clients are usually grateful for the nudge, because approving your draft is one of forty things on their list and the link makes it a two-minute job. What never works is daily chasing, which trains the client to treat your messages as noise.

How do I stop approval delays from stalling payment on the next job?

Put the acceptance test in the agreement and deliver on a record that carries its own decision state. The clause is one line: work is accepted when the client accepts it on the delivery record, or flags a specific step within an agreed number of days, after which it counts as accepted. When the job runs through Zambo, the client gets one handover link, accepts or flags step by step, and the acceptance state sits on the record the invoice points at. For $0.99, deliver the next final draft that way and let the record carry the decision: https://zambo.dev/day-pass/ A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related