The short answer
Every credit note is a record of something that went wrong: a wrong item, a fault, a missed delivery date, a dispute over what was agreed. Sorted by cause and costed over a year, your credit notes show where margin leaks and which two or three problems to fix first, without any new system.
By Euan Pallister, Operations & Quality Improvement Consultant. Published on .
Why credit notes are worth reading
Quality records tend to depend on someone remembering to fill in a form. Credit notes don’t. Every time the business gives money back to a customer, finance records the date, the customer, the job and the amount. That makes the credit note ledger one of the most complete records of failure most businesses have, even though it is rarely read that way.
It also speaks the board’s language. “We credited £48,000 last year, and over half of it was for one cause” lands in a way that “we have 40 open non-conformances” never does.
How to read a year of them
You need an export of last year’s credit notes and a spreadsheet.
- Add a reason code to each one. Read the narrative and pick from a short list: wrong item, missing item, damaged, fault, late, pricing or admin error, dispute over scope. If the narrative doesn’t say, ask the person who raised it while they still remember.
- Add a second column: where it started. Quote, order set-up, survey and design, purchasing, supplier, warehouse, dispatch, delivery or install. This is the column that tells you what to fix.
- Total by cause and by stage. Use a simple pivot table. Sort by value, not by count: ten small admin credits matter less than two large remakes.
- Look for repeats. The same customer, the same product family, the same supplier, the same fitting team. Repeats are where a single fix removes many credits.
- Pick the top two or three. For each, ask why it happened and why no check caught it before the customer did.
What you’ll usually find
Patterns vary by business, but a few are common in companies that quote, make, deliver and install:
- Pricing and admin credits that trace back to information retyped between systems, so the invoice doesn’t match the order.
- Wrong or missing items that started at order set-up, not at dispatch.
- Supplier faults credited to your customer but never charged back to the supplier.
- Scope disputes where a change was agreed on site but never written down or priced.
What credit notes don’t show
A credit note shows what you gave back, not what it cost you to put the problem right. A remake, a return visit or a day of office time often costs more than the credit itself. Once you’ve found the top causes in the credit notes, add the remakes and return visits for the same jobs. Our guide to what rework really costs shows how.
Keep it going
Make the reason and stage codes mandatory when a credit note is raised, and review the totals monthly with the person responsible for each stage. Within a quarter you’ll know whether your fixes are working, in pounds.
The free Margin Leak Review works from exactly this kind of record: bring a sample of your credit notes or remedial records, and we’ll show you where the money is going in about an hour.
Quick answers
Why are credit notes useful for quality?
Because they are already recorded, already costed and hard to ignore. Each one is money given back to a customer, so finance has kept a record even when nobody logged the problem behind it.
What reason codes should we use?
Start with a short list your team can apply consistently, such as wrong item, missing item, damaged, fault, late, pricing or admin error, and dispute over scope. Add more only when one code grows too big to act on.
Do credit notes show the full cost of a problem?
No. They show what you gave back, not what it cost to put right. Add remakes and return visits for the same jobs to see the full picture.
What is a good credit note rate?
Track credits as a share of invoiced sales over time and compare like with like. A falling rate is the measure that matters, not someone else's benchmark.