Back to blog

Blog

How To Get Client Approval Before Sending An Invoice

A practical workflow for getting client approval before invoicing, so the invoice can stay simple and payment feels less awkward.

May 2, 2026

Cover image for How To Get Client Approval Before Sending An Invoice

Sending an invoice should feel simple.

You did the work.
The client agrees.
You send the invoice.
They pay it.

Nice and clean.

But in reality, it often goes differently.

You send the invoice, and then the client starts reviewing what was done.

They ask about the hours.
They want to check the details.
They forward it internally.
They say they will “get back to you.”

And suddenly the invoice is stuck.

Not because the client refuses to pay, but because the approval happened too late.

Start here

Make client approvals easier before you bill.

Otterflow keeps work logs, reviews, approvals, and invoices in one simple flow.

Send a review first

Before you invoice, send the client a simple summary of what you are about to bill.

It should show:

  • what work was done
  • which period it covers
  • how many hours were included
  • any fixed-fee items or expenses
  • the total amount

The goal is not to add more admin.

The goal is to give the client one clear moment to say:

“Yes, this looks good.”

Before the invoice exists.

Make it easy to understand

Clients should not need to decode your invoice.

Instead of writing:

Design work — 12 hours

Give a bit more context:

Homepage layout updates, mobile adjustments, and final export preparation — 12 hours

That small detail helps the client understand what they are approving.

You do not need to write a novel.
Just enough to make the work clear.

Ask for approval directly

Do not just send a summary and hope the client knows what to do.

Say it clearly:

Here is the work summary for this month. Can you please review and approve it before I send the invoice?

That makes the next step obvious.

The client knows what they are looking at.
They know what you need.
And you avoid the vague “let me know what you think” situation.

Keep questions before the invoice

Questions are not the problem.

Clients are allowed to ask questions. That is normal.

The problem is when those questions happen after the invoice is sent.

Because then the invoice becomes a discussion document.

If something needs to be clarified, it is better to fix it before billing.
If everything looks good, the invoice can go out cleanly.

The invoice should be boring

That is the goal.

The invoice should not create surprise.
It should not trigger a long email thread.
It should not be the first time the client sees what they are paying for.

By the time the invoice arrives, the client should already know what it is for.

They approved the work.
They agreed with the amount.
Now the invoice is just the final payment step.

A simple workflow

A better freelance billing flow looks like this:

Do the work → send a review → get approval → send the invoice

It is a small change, but it makes the process feel much cleaner.

The client gets more clarity.
You get fewer awkward follow-ups.
And the invoice is less likely to get stuck.

That is the kind of workflow I’m building Otterflow around.

A simple way to share the work first, get approval, and only then send the invoice.

Because getting paid should not start with confusion.

Related posts

Cover image for Why Freelancers Should Separate Client Review From Invoicing

May 2, 2026

Why Freelancers Should Separate Client Review From Invoicing

A practical case for reviewing client work before sending the invoice, so payment feels clearer and less awkward.

Read post
Cover image for What Makes Otterflow Different

June 8, 2026

What Makes Otterflow Different

Why Otterflow is built around one focused workflow: giving independent professionals a clean way to get client approval before invoicing.

Read post
Cover image for How Otterflow Was Created

May 9, 2026

How Otterflow Was Created

A look at how Otterflow was shaped around client reviews, approvals, and the step before invoicing.

Read post