Handling an Invoice Change Request Without the Chaos

You sent invoice INV-2031 on Tuesday for 8,400 dollars. On Thursday the client replies: "Can you split the discovery and design phases into separate line items, drop the rush fee, and change the currency to EUR? Also our PO is 44781." Now you have four changes, two of which affect the total, and no clear record of who agreed to what. The wrong move here is to open your invoice file, retype everything, and email a new PDF. That's how you end up paid the wrong amount against the wrong version.

Here is the workflow that keeps both sides aligned, in the order it actually happens.

Step 1: Separate the edits from the requests before you touch anything

Not every change a client asks for is the same kind of change. Some are administrative details the client owns. Others affect what you're being paid. Split the message in two columns in your head.

Administrative edits the recipient can make themselves: PO number, billing entity, billing address, AP contact. In the example above, PO 44781 falls here. The client doesn't need your permission to set their own PO. With recipient editing on the live invoice, they type it in, you get notified, and it's stamped onto the current version as an amendment. No new version, no back and forth.

Requests that need your approval: line items, pricing, discounts, currency, payment terms, due date. Splitting the discovery and design phases, dropping the rush fee, and switching to EUR all sit here. These change the commercial deal, so they go through a request-and-approve flow rather than a direct edit.

Step 2: Have the client submit the changes on the invoice itself

Send the client back to the invoice link, not to your inbox. On the invoice they click into the line items or terms and submit a change request with what they want. You see the proposed change next to the current value: "Rush fee, 1,200 USD" struck through, "Remove" requested. "Currency: USD" with "EUR" proposed. The invoice status flips to Change Requested.

Two things this buys you. First, the request is attached to the exact invoice, not floating in an email thread that your bookkeeper will never find in March. Second, the client has stated the change in writing, in the system, with a timestamp. If they later say "we never asked to remove the rush fee," the request is right there.

Step 3: Review, approve, or decline each request

Open the invoice. You'll see each requested change as a discrete item. Approve the ones you agree with. Decline the ones you don't, with a short reason the client will see. You don't have to take all or nothing. In our example you might approve the line item split and the currency switch but decline removing the rush fee, with a note: "Rush fee applies because delivery was inside 5 business days per quoted terms."

When you approve changes that alter content, the invoice rolls to a new version. V1 becomes V2. The old version doesn't disappear. It sits in the history, frozen, so anyone can see what changed and when. That trail is the whole point of tracking every edit as its own version, and it's also what lets you revert a bad change in one click if you approved something by accident.

Step 4: Send the new version for the recipient to approve

The client now sees V2 with the agreed changes applied and the declined items unchanged. They review it. If it matches what they wanted, they approve. The status moves to Approved and that version locks permanently. The PO number they added in step 1 carries forward as an amendment on V2, so AP gets everything they need in one document.

If they're still not happy, they can submit another request. You repeat step 3. V3, V4, however many it takes. Each one is a clean snapshot, not a marked-up file with red strikethrough that nobody can read.

Step 5: Forward to AP and let it pay

Once V2 is approved and locked, the client (or you) forwards the invoice to their AP contact. AP sees a single live link with the right PO, the right billing entity, the right currency, the right total. They don't have to ask which PDF in the thread is the real one. If you want to understand what AP is actually checking when they receive it, the breakdown of what AP teams want field by field is worth reading once and bookmarking.

What to do when the client wants to go back to V1

It happens. The client approved V2, then their finance director said the original rush fee should have stayed. Open the version history, find V1, and revert. A new version is created from V1's content (so V3 in this case). Send it for approval. The locked V2 is still in the record, so you can show that the change was a deliberate revert, not a quiet rewrite.

Where this workflow saves you the most time

Agencies and consultants with multi-phase projects, where scope shifts mid-engagement, get the biggest payoff. So do freelancers invoicing larger companies with formal AP processes. If most of your work is one-off and paid on receipt, you'll feel it less. The patterns at agencies juggling several active clients and consultants billing against retainers and milestones are where this falls apart fastest without structure.

Next time you have a client asking for changes, send them the invoice link and let them mark up the document. Start a new one from the create-invoice screen if you don't have one open yet. The conversation moves from your inbox to the invoice, which is where it should have been from the start.