When the Customer Disputes the Invoice

All three arrive as an email saying the amount is wrong. The three resolutions have nothing in common.

Start by assuming the customer has done arithmetic correctly on a document that was unclear. In our experience of the shape of this problem, that is what an amount dispute almost always is, and the reason it is an argument rather than a payment is that the customer cannot reconcile the lines to the total. A line with a description they read differently, a discount applied without a visible reason, a tax row they expected to be handled elsewhere. The customer is not refusing the number. They cannot explain the number to their own finance team, and that is a legitimate objection.

The response is to make the arithmetic visible rather than to assert the total. A constructed example. Invoice I-402: three lines. Line one, 40,000. Line two, 25,000. Line three, 8,000. Taxable value: 40,000 plus 25,000 is 65,000, plus 8,000 is 73,000. GST at 18 percent, used only so the total is checkable: 73,000 multiplied by 0.18 is 13,140. Total: 73,000 plus 13,140 is 86,140. A credit note was already issued against this invoice for a short delivery on line two, 8,000 taxable, which is 9,440 including the tax at 18 percent. So the amount the customer is being asked for is 86,140 minus 9,440, which is 76,700.

The customer has written to say the invoice is for 86,140 and is wrong. They are not wrong. The document they are looking at is the original invoice, which is correct as issued, and the credit note is a separate document they have not seen. Nothing is in dispute about the arithmetic at all. The dispute is about which document governs, and it is settled by showing both, in order, with the reason for the credit note attached to the line it belongs to.

This is where the four-record separation earns its keep. The invoice is the claim as issued, immutable. The credit note is a new document against it that reduces what is claimable. Neither has been edited, so both are true, and the settlement is a matter of presenting them together rather than of arguing. If the credit note had been applied as an edit to reduce the invoice total to 76,700, the record would now show a single document and the customer would still be confused, because they would have an invoice they believe is for 86,140 and a record saying 76,700, and the reason would be gone. The edit destroys the ability to explain. The new document is what makes the explanation possible.

This is the expensive one, because it looks identical to an amount dispute in the email and it is a completely different problem. The customer is saying a line on the invoice was never agreed. Sometimes they are right that it was never agreed. Sometimes they are misremembering a conversation. Either way, the resolution is not an arithmetic conversation at all, it is a comparison between the invoice and the quote, and the entire difficulty is that many businesses cannot produce that comparison because the quote they hold is not the quote they sent.

We should be precise about what this system does and does not have, because it is exactly the point where people expect a change-order module and there is not one. There is no change-request record, no milestone record, and no deliverable record. There is no contract editor and there is no e-signature. A quote is a structured document with line items, tax rows, totals, a validity period, and terms, and what establishes it is the customer's acceptance of it. When the scope changes, the mechanism is a NEW QUOTE raised against the same project. It is not an edit to the old quote and it is not a line typed into the invoice.

That design has an obvious benefit in a dispute. The old quote is untouched, so the comparison between what was agreed and what was invoiced is a fact rather than a reconstruction. The cost is the thing that generates the disputes: if a new quote is not raised, the extra work has no home. It ends up on an invoice as a line that cannot be traced to anything the customer agreed to, and now the customer is disputing a figure that we know is arithmetically correct and know is commercially indefensible.

So the honest sequence when a scope dispute arrives is in this order, and the order matters. First, produce the accepted quote for that project and compare it, line by line, against the invoice. Second, for any line on the invoice that is not on the quote, establish internally whether it was agreed and merely not quoted, agreed and quoted but on a quote the customer never accepted, or not agreed at all. Third, for anything genuinely not agreed, raise a new quote against the same project for that work, with its own line items, tax, and terms, and let the customer accept it. Fourth, if the customer is right that they should not be charged for it, issue a credit note for that line. The new quote is how the work becomes agreed; the credit note is how the invoice becomes correct. They are different records doing different jobs, and the temptation to do neither and simply reduce the total is what leaves the customer believing they were overcharged on purpose.

One constructed case, and the arithmetic is the point. Quote Q-88, accepted: two lines, 30,000 and 20,000, so a taxable value of 50,000, with GST at 18 percent used only to keep the totals checkable, which is 9,000, for a total of 59,000. Work was then done that nobody quoted: a further 12,000, with tax of 2,160 at the same illustrative rate, so 14,160. The invoice raised I-410 was 59,000 plus 14,160, which is 73,160. The customer has disputed the 14,160. The arithmetic is correct and the scope was not agreed. There is no record of the 12,000 anywhere, because the only mechanism is a new quote and no new quote was raised.

What the business can do now is limited and should be acknowledged as limited. It can issue a credit note for 14,160 and collect 59,000. It can raise a new quote for the 12,000 of work, on the same project, and if the customer accepts it, invoice it properly and keep the rest. What it cannot do is go back and add the line to Q-88 and pretend the scope was always agreed, because that would make the document say something that never happened, and the next dispute on that project would then be about the document rather than about the work.

Somebody writes to say the tax on the invoice is wrong, or was charged on the wrong basis, or should have been handled by them rather than by you. This is the one category where the correct response is to decline to have the conversation, and the reason is not caution for its own sake. Tax treatment is not a matter of what the document says, it is a matter of what the law requires for your business, your customer, your place of supply, and your product. You are not the right party to settle it, we are certainly not, and a settlement reached on a phone call with a customer is a settlement you may have to unwind.

So: record precisely what the customer has asserted, in their words, on the record. Do not interpret it. Do not offer to split the difference, and do not issue a credit note for the tax element as a way of making the email stop, because a credit note against a tax line is a document with its own consequences and it is not a collections tool. Do not reissue the invoice with a different treatment to see whether the customer stops complaining.

Take the invoice, the accepted quote, the customer's message, and the correspondence to your own chartered accountant, and let them tell you what the treatment should be and what, if anything, needs to change. This is genuinely the correct answer rather than a deflection, and it is worth saying why. Your accountant can see your registration, your customer, your place of supply, and the specific product. You can see one document and one email. If the customer's treatment is right, your accountant will tell you and the correction is straightforward. If it is wrong, you now have a defensible position rather than a concession, which is a materially better place to be in six months.

We do not file GST returns and we do not pursue statutory recovery, and nothing on this page is tax advice. But there is a collections consequence worth stating plainly: a tax dispute is the dispute most likely to stall indefinitely, because the person who can resolve it is not in the conversation. The correct collections response is to keep the relationship warm on everything else, get the accountant's answer, and separate the disputed amount from the undisputed amount so that the undisputed amount is not held hostage. In the I-402 case above, the undisputed 76,700 does not have to wait for the treatment question. Splitting them is not a tactic, it is what the records make possible.

A dispute is settleable when you can produce the documents that make the answer obvious, and it is unsettleable when the answer depends on what somebody remembers. The requirement is therefore not more data. It is a specific set of documents, each one readable on its own, each one attached to the right things, and none of them edited after the fact.

There are five, and the fifth is the one most systems are missing. The issued invoice with its line items, its tax rows, and its total, unedited. The accepted quote for the work, with the date it was accepted, so a scope question has something to compare against. Every credit note and every new quote raised against the invoice, linked to it rather than filed separately, so the current claimable amount is derivable by reading the attachments in order. The allocation history, so that what the customer has already paid is a list of receipts rather than a claim. And the correspondence, on the record, with dates, in what was actually said rather than in what you understood it to mean.

The fifth item is what turns a dispute from a standoff into a conversation. Without the correspondence you are arguing about the document while the customer is arguing about a conversation that is not in evidence, and neither of you will move. With it, you can usually find the point where the two versions diverged, and that point is nearly always a sentence somebody said in a call or a message that neither of you thought was a commitment. Finding it ends the dispute, because both parties can see the same moment.

There is one more requirement that is about the record and not about the document. The dispute has to be attached to the invoice rather than living in somebody's inbox, and it needs a status that is not simply open or closed. A disputed amount that is still collectable, a disputed amount that is under review, and a disputed amount that has been referred are three different states with three different consequences for the outstanding figure, and collapsing them into one is how a small dispute quietly stops being chased. What the outstanding figure should do with a disputed invoice is a policy decision you make deliberately — most businesses keep the disputed amount outstanding until it is resolved, on the basis that resolving it is the point — and it should be written down rather than discovered.

One last thing, because the discomfort is the point. The most common way disputes are lost is not that the customer is unreasonable. It is that the business cannot produce the quote, cannot show the credit note in context, and cannot find the call note, so the conversation becomes about trust rather than about facts, and trust does not move in a favourable direction. Every item on the list above is cheap to keep at the time and impossible to reconstruct afterwards, and that asymmetry is the whole argument for writing the record down when nothing is wrong.