Invoice dispute software that starts by asking which of the three disputes this actually is
A customer who disputes an invoice is not making an accounting argument. They are telling you something about what they thought you agreed, what they think you billed, or what they think the number means — and only the first of those is arithmetic. Disputing an amount is a calculation. Disputing the scope is a question about what was agreed, which only works if the agreed scope can be reconstructed. Disputing the tax treatment is not a software problem at all and goes to your chartered accountant. Sorting those three apart before anyone concedes anything is the entire skill.
Three disputes, one sentence
The customer’s email says the same thing in all three cases. What differs is what evidence settles it, who is allowed to settle it, and which document — if any — can carry the outcome.
Disputing the amount: the only one that is arithmetic
The customer believes a figure is wrong. It is settled by addition and subtraction on documents that already exist — the invoice, the payment, the allocation — and usually in a few minutes. The instrument is a credit note against the invoice that carries the wrong figure, and the direction matters: a credit reduces what is owed, it does not receive money, and cash received does not change. This is the only dispute on the page where the answer is a calculation.
Disputing the scope: the agreed work is the question, not the total
The total can be perfectly correct and the invoice still be wrong, because what was invoiced was not what was agreed. Settling this needs the agreed scope to be reconstructable — and that is a property of your records, not of the customer’s arithmetic. In NoxOrigin the reconstructable record is the quote, because there is no change-request record, no milestone record, no deliverable record, no contract editor and no e-signature, so a change in scope is a new quote on the same project and the original quote is never quietly rewritten.
Disputing the tax treatment: not a software problem
The figures are right as issued and the argument is about how a line should be treated. NoxOrigin stores the tax fields exactly as they were entered and does not evaluate them, does not file GST returns or any other statutory return, and does not determine how a credit note or a reduced quote should be treated. Until your chartered accountant answers, the honest position is that the number stands as issued — the system will not quietly net it out to make the conversation easier.
Disputing something that is not on the invoice at all
Sometimes the argument is about an arrangement, a delay, a person, or a line that was never billed. None of those produce a document, and a clarification that ends in understanding produces no money movement whatsoever. That is not a failure to resolve — it is the correct outcome when the numbers never actually moved, and it is worth saying so rather than issuing a credit to end an uncomfortable email.
A routine that ends in a document, or in a letter from your accountant
Six steps, in the order they should happen. Steps three and five are the fork, and step six is the one people try to avoid.
Ask what is being disputed, and refuse to answer it in one move
"The amount is wrong" is three different disputes wearing one sentence, and only one of them is arithmetic. Amount, scope, and tax treatment have different owners, different evidence, and different documents that can settle them. Classifying it first is the cheapest step in the whole process and the one most often skipped.
Rule out the boring answer first: has the money simply not been applied?
A payment is a different record from an invoice, and paid is a projection of allocations. An unallocated receipt leaves a customer looking underpaid while the ledger has not reduced anything, which produces a dispute that dissolves in five minutes. Check the allocations before you argue about scope.
If it is the amount: do the arithmetic on documents that exist
The invoice against the payment against the allocation, in that order, with the figures written down. A conceded amount is a credit note against the invoice that carries it — and note the direction: a credit reduces a claim, it does not receive money, and cash received does not change by a rupee.
If it is the scope: establish what was actually agreed, and where it is written
The agreed scope has to be reconstructable, and in NoxOrigin the record that reconstructs it is the quote — there is no change-request record, no milestone record, no deliverable record, no contract editor and no e-signature. A document explaining the change with the approval on it is still worth writing; it is simply not something the system will hold for you.
Then find out whether the disputed work is already on an invoice
Invoiced work can be credited against a document you can point at. Un-invoiced work cannot, and pretending otherwise produces a credit note against nothing. One question decides which document the rest of the process is, and it is worth ten minutes to answer properly.
If it is the tax treatment: stop, and send it to the accountant
This is not a software problem and NoxOrigin will not pretend to solve it. The figures can be arithmetically perfect and still be wrong in a way that needs a professional judgement, and the invoice stays exactly as issued until that judgement arrives. No statutory return is filed here and no tax treatment is determined here.
The same ₹80,000, three different disputes
Every figure below is constructed for this page and the arithmetic is shown so you can check it by hand. It is not a NoxOrigin result and not a customer’s account. One project is quoted at ₹4,40,000. INV-07 is raised for ₹2,00,000 and INV-08 for ₹1,20,000, so ₹2,00,000 + ₹1,20,000 = ₹3,20,000 has been billed, leaving ₹4,40,000 − ₹3,20,000 = ₹1,20,000 of the quote not yet invoiced. Payments received total ₹2,80,000, of which ₹1,60,000 is allocated, so outstanding is ₹3,20,000 − ₹1,60,000 = ₹1,60,000 and ₹2,80,000 − ₹1,60,000 = ₹1,20,000 sits unapplied. The customer now writes: we dispute ₹80,000.
Read one — it is the amount, and the customer is right about the money
The ₹80,000 they are describing is a payment that arrived and was never allocated. Allocating it drops total outstanding from ₹1,60,000 to ₹1,60,000 − ₹80,000 = ₹80,000, and the dispute ends with an allocation rather than a credit note. Nothing was conceded, no document was issued, and unapplied cash falls from ₹1,20,000 to ₹1,20,000 − ₹80,000 = ₹40,000. This is the version where the customer is disputing a number, the number is derived rather than stored, and the fix is bookkeeping.
Read two — it is the scope, and the invoice total is arithmetically correct
The same ₹80,000 is a bill for work the customer says was never agreed. The total is right; what is contested is the scope, so arithmetic cannot settle it and the agreed scope has to be reconstructed from the quote. Which document comes out of the conversation now depends on one fact nobody has checked yet — whether that ₹80,000 of work is already inside the ₹3,20,000 billed or still sitting inside the ₹1,20,000 not yet invoiced.
Read two, invoiced half — the work is already billed, so it is a credit note
If the disputed ₹80,000 is part of the ₹3,20,000 already raised, there is an invoice to attach a credit to. Credit note ₹80,000 reduces billed to ₹3,20,000 − ₹80,000 = ₹2,40,000, allocations stay ₹1,60,000, and outstanding becomes ₹2,40,000 − ₹1,60,000 = ₹80,000. The customer’s ₹80,000 dispute is answered by a credit note and nothing else. Note that the credit does not touch the unapplied cash at all — a credit reduces a claim, it does not absorb money you already hold, and the two are separate records pointing in opposite directions.
Read two, unbilled half — there is no invoice, so it is a new quote
If instead the disputed ₹80,000 is inside the ₹1,20,000 not yet invoiced, there is no invoice to credit. That work simply drops out of what you bill, and a new quote goes out on the same project for the reduced remainder: ₹1,20,000 − ₹80,000 = ₹40,000. Accepted, the project total billed becomes ₹3,20,000 + ₹40,000 = ₹3,60,000 against an original quote of ₹4,40,000, a reduction of ₹4,40,000 − ₹3,60,000 = ₹80,000 — the same ₹80,000, settled by a completely different document. The original quote is left untouched at ₹4,40,000, because it is the evidence of what was agreed.
Read three — it is the tax treatment, and the arithmetic never changes
The figures are exactly as they should be, and the argument is about how a line on the invoice should be treated. Outstanding is ₹1,60,000 before the question is asked and ₹1,60,000 after, because no document changed and none should. NoxOrigin does not evaluate tax fields, does not file GST returns or any other statutory return, and does not decide how a credit note or a reduced quote should be treated — so this one leaves the building and goes to your chartered accountant. Issuing a credit to end the email would be settling a tax question without authority, and the figure would be wrong on the invoice in a way that is harder to undo than a delay.
The same argument, three different outcomes
One sentence, three answers: an allocation, a credit note, or a letter to your accountant. In the first, outstanding falls to ₹80,000 and no document is issued. In the second, a credit note for ₹80,000 leaves outstanding at ₹80,000. In the third, nothing moves and the invoice stands. Two of the three end with a figure of ₹80,000 outstanding for completely different reasons, which is precisely why conceding before classifying is how a good customer ends up with two credits and still owes the original amount.
Where a receipt is allocated changes which dispute the customer is having
The ₹80,000 unapplied receipt can land on either invoice, and the customer sees a different statement either way. Allocate it to INV-07 and that invoice’s outstanding is ₹2,00,000 − ₹80,000 = ₹1,20,000 while INV-08 stands at ₹1,20,000. Allocate it to INV-08 instead and INV-07 is untouched at ₹2,00,000 while INV-08 is ₹1,20,000 − ₹80,000 = ₹40,000. Total outstanding is ₹80,000 either way, but the disputed line is now fully paid on one and untouched on the other. Nothing is spread by date automatically, so where it lands is a decision a person makes — and it should be made deliberately, not inherited from whoever opened the banking portal.
The clarification that is not a dispute at all
A customer asks what a particular line refers to, you explain it, and nothing changes: billed is still ₹3,20,000, allocated is still ₹1,60,000, outstanding is still ₹1,60,000. No credit note, no new quote, no adjustment. There is no dispute record, no dispute status, no ageing clock on an unresolved dispute and no threaded conversation in NoxOrigin — the answer is a note you write, and the only thing this platform will do about a dispute is hold the documents that whatever you decide has to attach to.
Where this is the wrong tool
A disputes tool is judged by what it refuses to decide. Conceding early is cheap to automate and expensive later — a credit issued to end an email is a document the customer will cite for the next two years.
There is no change-request, milestone, or deliverable record
A scope change is a new quote on the same project. There is no change-request record, no milestone record, no deliverable list, no contract editor and no e-signature, so a scope dispute is settled by reading the original quote and issuing a new one rather than by pulling up an approved amendment. A change-request document with the approval on it is still worth having — it is just not something the system will hold for you, and a quote nobody can reconstruct is a quote you will lose that argument on.
It is not a tax tool and it files nothing
NoxOrigin does not file GST returns or any other statutory return, does not determine the correct tax treatment of a line, and does not decide how a credit note or a reduced quote should be treated. Those go to your chartered accountant, and the invoice stays as issued until they answer. It is also not a statutory recovery or legal tool: no demand notice, no legal notice, no third-party collection agency.
It is not a collections product, and it will not chase
There is no dunning sequence, no automated escalation, no retry ladder, no card on file, no auto-debit, no credit bureau, no write-off automation, and no promise-to-pay or payment-plan record. Chasing an undisputed balance is a different subject, and the wrong instinct while a dispute is open is to escalate — most of what looks like a slow-paying customer is a customer who is waiting for you to answer a question.
There is no timesheet, no payroll, and no expense line
No timesheet record, no payroll module, and no expense tracking in NoxOrigin — expense tracking lives in Nox-Billings, a scoped custom deployment quoted separately from the platform — and purchasing sits in Commerce. So a disputed travel cost or pass-through purchase is an invoice line you can defend or credit, and the detail behind it has to come from another system or from a document you keep.
Nothing merges automatically
Merge is a setup decision: detection flags candidate pairs and a person reviews. Until that review happens, one customer on two records will generate two invoices, two disputed amounts and two statements — and a credit against the wrong one of them is a real loss rather than a bookkeeping error.
Paid is a projection, and day-end close is not a switch
An invoice and a payment are different records; paid is derived from allocations rather than stored, which is why an unallocated receipt can make a customer look underpaid. Shift close and day-end reconciliation are assisted-setup maturity rather than self-serve switches, so what gets set up with you, and how quickly, is agreed during implementation.
Where the answer has to live
The quote that was agreed, the invoice that was raised, the payment that arrived, and the allocation a person made are the whole of a dispute’s evidence. The next one about the same line is only cheap if all four of those are on the record.
Run it on the plan that matches your customer count
Growth is ₹1,600/month or ₹15,000/year, includes a 30-day trial, 10 users, 50 active projects, and 10,000 contacts. The quote, the invoice, the payment and the allocation are part of the workspace rather than an add-on. These are NoxOrigin platform plans — NoxCRM, Nox-Billings and Nox-Tickets remain scoped custom deployments, quoted and priced separately, and Nox-Billings in particular is where expense tracking lives rather than something a platform plan unlocks.
Invoice dispute and clarification questions
What is the difference between disputing an amount, a scope, and a tax treatment?
Only one of the three is a calculation. An amount dispute is settled by adding and subtracting on documents that already exist. A scope dispute cannot be settled that way at all, because the thing being contested is what was agreed — which means the agreed scope has to be reconstructable, and in NoxOrigin the reconstructable record is the quote, so a change in scope is a new quote on the same project rather than an edit to the old one. A tax-treatment dispute is not a software problem: the figures may be arithmetically perfect and still be wrong in a way only your chartered accountant can rule on, and nothing in NoxOrigin decides it.
Is the dispute a money record?
No. A dispute is a note with a name and a date against it, not an adjustment. Until a person decides what it should change, the customer owes what they owed, and the ledger is untouched. Only two documents can convert a dispute into money: a credit note against an invoice that already exists, or a new quote on the same project for work that has not been invoiced yet. If neither was raised, nothing moved, and that is the correct behaviour rather than a bug.
Why is a scope change a new quote instead of an edit to the existing one?
Because an edited quote is a quote nobody agreed to. There is no change-request record, no milestone record, no deliverable record, no contract editor and no e-signature here, so a reduction or addition in scope is priced and accepted as a new quote on the same project while the original stays intact as the thing that was originally agreed. The old quote is the evidence, and it is only evidence if it was never rewritten. This is also why an un-invoiced scope change is a smaller job than an invoiced one — one needs a document, the other needs a new one.
Can it tell me whether the tax treatment on an invoice is correct?
No. NoxOrigin stores the tax fields as they were entered and does not evaluate them. It does not file GST returns or any other statutory return, does not determine how a credit note or a reduced quote should be treated, and will not alter a figure because a dispute mentioned a number. Send a tax-treatment question to your chartered accountant, and until they answer, leave the number as issued rather than quietly netting it out.
Is a payment part of the dispute?
Sometimes, and it is worth separating before arguing about anything else. A payment is a different record from an invoice and paid is a projection of allocations, so a payment that was received but never allocated has not reduced anything — the customer can be right that money is missing from their statement while the ledger has not applied it yet. Allocating a receipt is not a financial concession and is not a credit, but it does change what is outstanding, and where a single receipt lands is a decision rather than something the system spreads for you.
Does NoxOrigin track disputes as a queue?
No. There is no dispute record, no dispute status, no ageing clock on an unresolved dispute, and no threaded conversation with the customer. The answer to a clarification is something you write, and the only state change is a document — a credit note or a new quote. A disputes process is a queue, a policy and a person, and those are yours; what NoxOrigin holds is the invoice, the quote, the payment and the allocation that whatever you decide has to attach to.
The disputed line is a travel cost or a pass-through purchase. Can it break that down?
Not beyond what the invoice line says. There is no timesheet record, no payroll module, and no expense tracking in NoxOrigin — expense tracking lives in Nox-Billings, which is a scoped custom deployment priced separately from the platform — and purchasing sits in Commerce. So a disputed cost is a line on an invoice you can defend or credit, and the detail behind it is in another system or in a document you attach.
Can it chase the customer while the dispute is open?
No, and you should be careful about wanting it to. There is no dunning sequence, no automated escalation, no retry ladder, no card on file, no auto-debit, no credit bureau, and no payment-plan or promise-to-pay record — the promised date is a date somebody typed. Reminders while a dispute is open tend to turn a disagreement into a relationship problem, and nothing in NoxOrigin will send a reminder on your behalf. Chasing an undisputed balance afterwards is a separate subject, and it is a prioritised outstanding list rather than a dispute.
Does paid get stored, and does anything merge automatically?
Two honest answers, both of which save arguments later. Paid is not a field: an invoice and a payment are different records and paid is derived from the allocations, so it cannot drift out of step with them. And merging is a setup decision — detection flags candidate pairs and a person reviews, so the same customer on two records will keep producing two invoices, two disputes and two ageing rows until somebody decides they are one person.
Send us a dispute that is not about arithmetic.
One disputed amount, one scope argument, and the tax question you were hoping somebody would answer. We will show you which of the three it is, which document could settle it, and which of them is not ours to decide.