What source evidence supports the additional amount?
Does the change affect tax, revenue, cost, or inventory?
How will both parties reconcile the document?
Meaning in day-to-day work
What does it mean in practice?
A debit note records an increase or correction connected to an earlier invoice or supplier transaction. Depending on the business and jurisdiction, the buyer or seller may issue it. The document must state who is increasing which balance and why.
Practical example
An approved delivery charge was omitted from the original customer invoice. A debit note references that invoice, adds the agreed charge and applicable tax, and increases the customer balance without rewriting the original document.
From start to close
How does the workflow operate?
1
Identify the original transaction, issuing party, and contractual reason.
2
Calculate the additional amount, quantity, price, or tax correction.
3
Validate the direction of the balance and local document rules.
4
Approve and issue the note with a unique linked reference.
5
Update receivables or payables and reconcile tax, ledger, and customer/supplier statements.
Recommended controls
What protects workflow quality?
Original-document reference and clear issuing-party role
Contract, receipt, or calculation evidence for the increase
Duplicate and overstatement checks
Approval, tax-period treatment, and complete audit history
Common mistakes
What should teams avoid?
Using “debit” without stating whose account is affected
Issuing a note with no link to the original transaction
Adding unapproved fees or duplicating an amount already invoiced