Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

Fees, Scorecards & Recurrence

Why Did I Get a Debit Memo? A Plain Guide for Suppliers

A debit memo after a quality issue can feel like it came from nowhere. This guide helps an operations manager trace it to a request, check it and decide on next steps.

Rovaryn Digital · · 8 min read

A debit memo shows up and nobody remembers the request

The remittance advice arrives on a Tuesday, and the payment is a little short. A line in the AP detail says "quality debit memo" with a number you don't recognize. Your receiving contact says it relates to a rejection. Someone in quality remembers a call about a burr a few weeks ago, but not a formal request. Nobody on the floor is sure which part, which lot or which customer team issued it.

This is a common spot for an operations manager in a smaller shop, especially when customer complaints land on your desk as well as the quality group's. A debit memo is a customer's financial record. It does not always travel with the quality paperwork that explains it.

This guide walks through how to trace a debit memo to its source, check it against your customer's current manual and your own records, and decide whether to pay it, question it or dispute it. It is general information, not legal or financial advice.

What a quality debit memo usually is

A debit memo is a document from your customer that reduces what they pay you, or bills you for a cost. When it follows a quality problem, it generally falls into one of a few buckets. Which ones apply depends on the customer.

  • Cost recovery: sorting, rework, scrap, freight or line-down time the customer says your part caused.
  • Administrative charge: a fixed fee for opening or processing a corrective action request or a rejection report.
  • Late-response charge: a fee tied to a response that the customer considers late or missing.
  • Other adjustments: return freight, replacement parts or warranty-related recovery.

Customers use different words for the same thing: chargeback, debit memo, supplier charge, deduction. Your customer's supplier manual or customer-specific requirements (CSRs) define their term and how it works. Read the current revision rather than relying on what a previous customer, or an earlier version, did.

Step 1: Trace the debit memo to a request

Start with the paperwork, not the dispute. A memo normally points back to something: a rejection report, a corrective action request (CAR), a supplier corrective action request (SCAR) or an 8D request. If you need a refresher on how those requests work, see what a corrective action request is.

Capture these fields from the memo before you call anyone:

  1. Memo number and date
  2. Amount and currency
  3. Customer plant or buyer group that issued it
  4. Part number and, if shown, lot, PO or shipment reference
  5. Any request, rejection or problem report number
  6. The stated reason or charge category
  7. Any payment or dispute deadline printed on it

Then search your own records for the matching request. Check email threads, the customer portal, your shared drives and any spreadsheet where you log requests. If the memo cites a report number, search for that number first. If it doesn't, search by part number and date range.

Two outcomes are common. You find the request and the memo makes sense. Or you find nothing, which usually means a notice went to a mailbox no one monitors, a portal notification went unread, or the customer charged before issuing a formal request. All of those are worth knowing.

Step 2: Check the charge against your customer's manual

Once you have the request, look up what the customer's current manual or CSRs say about charges. You are looking for a few things.

What triggered the charge

Does the manual say a charge applies to every request, or only to certain severity levels or rejection types? Is it tied to the issue itself, to a late response, or both?

How the amount is determined

Is the charge fixed, a schedule, or actual cost with supporting documentation? A cost-recovery memo should generally be supportable with the customer's own records, such as sorting hours or scrap counts. Ask for the support if it wasn't attached.

What the response window was

Windows and fee terms differ from one customer to the next, and manuals change between revisions. A containment or response window in one customer's manual says nothing about another's. Check the revision in effect on the date your request was issued, not just the latest one, and keep a copy of that version.

If you want a closer look at how these terms are usually laid out, see our guide to fees in supplier quality manuals.

What the dispute process is

Some manuals describe how to question a charge, who to contact and by when. Others say little. If the manual is silent, ask your supplier quality engineer (SQE) or buyer what the process is, and ask in writing.

Step 3: Check your own records for the timeline

The next question is whether your records agree with the customer's. Build a plain timeline:

Event Customer says Your records say
Problem identified or shipment rejected
Request issued
Request received by your team
Containment confirmed
Initial response submitted
Final response submitted
Customer accepted or closed

Fill in both columns with dates and times, and note the source for each. Then look for gaps.

A few things are worth checking carefully:

  • Receipt date versus issue date. A request issued on Friday may not have reached the right person until Monday. Whether that matters depends on how the customer's manual counts the window.
  • Calendar versus working days. If the manual says "days," see whether it specifies calendar or working days. The count can differ by several days across a weekend or holiday.
  • Time zone and cutoff. A response sent late in the day may be logged the next day by the customer's system.
  • Proof of submission. A portal timestamp, sent email or confirmation screen is the evidence you want. A verbal "we sent it" is not.
  • Extension requests. If someone agreed to a later date by phone or email, find that message.

If your timeline shows the response was on time and the customer's record shows otherwise, you have a factual question to raise. If your timeline confirms the delay, you have a process question instead.

Step 4: Decide what to do

After the first three steps, a debit memo usually lands in one of four places.

  1. The charge is consistent with the manual and your records. There is little to question. Record it and move to the fix. Treat it as information about where the process broke.
  2. The charge looks valid in principle but the amount is unclear. Ask the customer for the supporting detail, such as the cost breakdown or the manual section they applied.
  3. Your records and theirs disagree. Send a written, factual note with your timeline and proof of submission. Keep the tone neutral. Ask what they need to review it.
  4. The memo cites a request you never received, or a rule you can't find. Ask which document and which revision the charge is based on, and where the request was sent.

A short, specific message to the SQE or buyer tends to work better than a long argument. Reference the memo number, the request number, the dates and what you are asking for. Check the memo for a dispute deadline and watch it, because some customers set a window for questions. If the amount is significant or a contract question is involved, talk to your own finance or legal advisers before responding. This guide can't tell you whether a particular charge is enforceable.

Also remember the person on the other end is usually your day-to-day contact, and the relationship matters beyond one memo. Whether you pay, question or dispute, keep it factual.

Step 5: Work out why it happened

Whatever you decide on the memo, look at the cause. Common patterns include:

  • The request went to a general mailbox or a former employee.
  • A portal notification was never forwarded to the quality team.
  • Nobody owned the clock, so the due date lived in someone's head.
  • The response was ready but waited on a signature or a review.
  • The customer's windows were different from what the team assumed.

The corrective action here is about your own process: who receives requests, who logs them, who tracks due dates and who confirms submission. A simple fix is a shared intake mailbox plus a log with one row per request: customer, part, received date, due dates taken from that customer's current manual, owner and status.

It also helps to count what these events cost you over time, including sorting, rework and response effort, not just the memo amount. The article on calculating the cost of poor quality describes how to structure that, and our overview of supplier chargebacks covers the broader picture.

A note on keeping your own record

Customer portals show you that customer's requests. They don't show you the pattern across all your customers, and a request can fall out of view when the portal is the only record. A supplier-side record, whether a well-kept spreadsheet or a purpose-built tool, lets you see every open request, due date and charge in one place.

Supplier CAR Response Desk is designed to be that kind of record, with editable per-customer response rules and a view built from the fee terms you enter yourself. It records and calculates; it is not advice or certification. It is pre-launch; you can join the waitlist to hear when it opens.

Treat a debit memo as a pointer back to a request. Find the request, read the customer's current manual, compare timelines, and then decide.

Where to go next

If you want to put your own numbers around what quality problems cost your shop, start with the ROI calculator.

Put it to work

Compare plans on the pricing page.

Get the next guide

Practical guides for supplier quality teams, delivered straight to your inbox.