Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

Fees, Scorecards & Recurrence

Supplier Quality Chargebacks: Where They Come From and How to See Them Coming

A chargeback usually arrives as a debit memo long after the request. This guide shows how to read the terms in your own customers' manuals and keep a running figure instead.

Rovaryn Digital · · 11 min read

The debit memo that arrives after the request is closed

A debit memo reaches accounts receivable on a Tuesday. It cites a part number, a rejection date from several weeks earlier, and a one-line defect description that nobody in quality recognizes at first glance. The engineer who handled the request has moved to another program, and the email thread sits in a mailbox nobody else can open.

Finance asks whether the charge is valid. Quality is not sure which customer's terms apply, which revision of the manual was in force, or whether the response went out inside the window.

This is a familiar shape for a supplier chargeback. The money moves through purchasing and accounts payable, while the corrective action moves through quality, and the two often meet only when the deduction appears. By then, the details are reconstructed from memory.

This article is written from the supplier's side of that gap. It covers where quality-related charges come from, where each customer writes its terms down, how to record those terms per request, and how to keep a running exposure figure while a response is still open, so the memo is something you expected.

Where supplier quality chargebacks come from

A chargeback is a charge a customer applies after a quality problem, usually as a debit memo, a payment deduction or a separate invoice. The names change from customer to customer. The underlying charges tend to fall into a few groups.

  • Administrative charges. A fee a customer's manual attaches to a formal quality notice, such as a rejection report, a problem report or a corrective action request. Depending on the customer, the notice may be called a CAR, a SCAR (supplier corrective action request) or an 8D request.
  • Late-response fees. A charge tied to missing the response window. A manual may describe a single fee, a fee that repeats for each overdue period, or something else. A late 8D penalty is only as clear as the wording that defines "late."
  • Cost recovery. The customer's own costs of handling your parts, such as sorting, rework, line stoppage, expedited freight or replacement material, billed back with whatever supporting detail the customer provides.
  • Field-related recovery. Warranty or recall costs that flow back to a supplier through the purchase agreement.

Some consequences carry no invoice but still cost something: a scorecard drop, escalation to a higher level of customer attention, controlled shipping (added inspection before your shipments are released) or a hold on new business. Each customer's manual names and defines these in its own way, so treat them as items to look up rather than assume.

Not every customer applies every term it writes. A manual states what a customer may do. What it does on a given request is a separate matter, which you learn by asking and by recording the outcome. Both facts are worth keeping.

Two things follow. First, the memo is rarely the whole cost. The cost of supplier nonconformance also includes your containment labor, sorting and engineering hours, which our guide to calculating cost of poor quality walks through. Second, the memo trails the event. A fee tied to a response deadline depends on dates you could have watched while the request was open.

Supplier chargeback quality terms: where each customer writes them down

Supplier chargeback quality terms may sit in several documents rather than one. Check each of these for every customer you answer:

  • The supplier quality manual. Often where response expectations and any administrative or late-response charges are described.
  • Customer-specific requirements (CSRs). For IATF 16949 suppliers, these are a customer's additions to the standard.
  • Purchase terms, supply agreements and quality agreements. Cost recovery frequently rests on these rather than on the manual.
  • The request and any portal notice. Some state a response expectation or point to a governing document.
  • Scorecard documents. They may describe what a late or repeated response does to your rating.

The reason each customer needs its own record is partly built into the standard. IATF 16949:2016, clause 10.2.3, as published with the IATF's Sanctioned Interpretations (November 2025), says that where a customer has prescribed processes, tools or systems for problem solving, the organization uses them unless the customer approves otherwise. Timing, format and consequences tend to follow the same pattern, one customer at a time.

Manuals are also revised. Fee language and windows can change between revisions, so a memo may refer to a request received under an older one. Record the revision you worked from, and confirm which one applies with the customer's supplier quality engineer (SQE) or buyer.

A checklist for reading the fee and response sections

  1. Note the manual name, revision, date and where you obtained it.
  2. Find what triggers a charge: a formal notice, a rejection, a late response, a repeat or an incurred cost.
  3. Identify the amount basis: fixed, capped, or actual cost.
  4. Find when the response window starts (sent, received or logged) and whether it counts hours, calendar days or working days.
  5. For late fees, note whether they are one-time or repeating, how a period is counted, and whether there is a ceiling.
  6. Note how a charge is delivered and how long you have to contest it.
  7. Look for extension rules: who may grant one and how it should be recorded.
  8. Record other consequences, such as scorecard impact, escalation levels and controlled shipping criteria.

If the manual is silent on fees, write that down with the revision number. Costs may be set in purchase terms or recovered case by case. For a closer look at this part of the manual, see supplier quality manual fees.

A fee-terms record you can keep without software

Two layers keep supplier chargeback quality terms manageable. Terms change rarely and belong to the customer. Request details change daily and belong to each request. A spreadsheet with two tabs can hold both, provided someone maintains it.

Terms tab field What to capture
Customer and ship-to Which customer, and which plant or program the terms cover
Source and revision Document name, revision, date, file location
Charge trigger The event the document says can lead to a charge
Amount basis Fixed, capped, actual cost, or not stated
Window and start event Length, unit, and what starts the count
Day-count method Calendar or working days, and whose holidays
Repeat rule One-time or repeating, how periods are counted, any ceiling
Dispute route Who receives a query, and the time limit
Confirmed with Who at the customer confirmed your reading, and when

The request tab holds the request ID, customer reference, part, received date and time, window end, extension granted (who, when, new date), response sent date, cost items the customer reported, and the memo reference when one arrives.

When a customer issues a new revision, add a new terms row with an effective date rather than overwriting the old one. A memo may refer to a request received under the earlier text, and you will want both.

Give the terms tab one owner, usually the Quality Manager or, in a smaller shop, the Operations Manager. Have that person update it whenever a new revision arrives. A record nobody owns drifts out of date, and an out-of-date terms row is worse than a blank one because it looks reliable.

Seeing exposure while a request is still open

Exposure here means what a customer's written terms could charge for a request, given where it stands today. It is not a forecast of what the customer will apply, and the correct reading of a term is sometimes a question for the customer's SQE. The figure is useful because it exists while there is time to act, and it changes only when a date or a term changes.

Count the window the way the manual counts it

Many disputes about lateness come from day counting rather than from the work. Check whether the count starts when the notice is sent, received or logged, whether it uses calendar or working days, and whether it runs in hours from a timestamp. Record the time received, not only the date.

An invented example shows how far the counts can drift. A notice arrives on a Thursday with a four-day window. This is not any customer's rule.

Counting rule Window ends
Calendar days Monday
Working days, weekends excluded Wednesday
Working days, with a Monday holiday Thursday

The same request is on time or late depending on the rule. Customers in other regions may also observe different holidays, so confirm the calendar with the SQE.

Add the fee arithmetic once the rule is clear

Suppose, again hypothetically, that a manual lists an administrative charge A for each formal notice and a late-response fee W that repeats for each week the response stays overdue. On the day the request arrives, exposure is A. Once the window passes, it is A plus W for each week counted overdue.

Whether a response ten days late counts as one week or two depends on whether the manual counts completed weeks or started weeks. The wording decides the result, so copy it into your terms record. Costs the customer reports, such as sorting or freight, go on the request as separate lines with the stated amount and the supporting detail.

A short weekly review

Once a week, list open requests by window end and mark what is overdue. For each, note the extension status, the exposure to date, any reported cost items and who owns the next action. Share the same list with finance, so quality and accounts payable are looking at one set of numbers.

If an extension was agreed, save the written confirmation and the new date on the request. The person who agreed to it may not be around when the memo arrives.

For the response work itself, see our guide to responding to a supplier corrective action request.

Checking a memo against your record

When a memo arrives, a good record answers these questions in order:

  1. Which request does it refer to? Match on part, date and customer reference.
  2. Which document and revision applied when the request was received?
  3. Do the trigger and amount basis match the terms: fixed, capped or actual cost?
  4. Do the dates agree on receipt, response and any extension?
  5. For cost recovery, is supporting detail attached, and does it match what the customer told you at the time?
  6. Is a dispute window running, and who receives a query?

From there, the choice is to accept the charge, query it, or contest it through the customer's own route, usually with your SQE or buyer involved. Whether a charge is valid depends on your agreement with the customer. Take contract questions to your own contracts or legal contact; this article describes the record, not legal advice. For a step-by-step on reading a memo, see why you got a debit memo.

Scorecards and escalation levels deserve the same treatment. A late or repeated response may move your rating or your escalation status even when no money changes hands, and those effects can matter more to the relationship than the fee. Log them on the request when you learn of them, with the date, so the pattern is visible later.

A charge is also information. A debit memo for a supplier quality defect on one customer's parts may describe the same cause already open on another customer's request. Records kept customer by customer hide that pattern; the issue is covered in our piece on repeat nonconformance.

A chargeback is easier to question, and easier to learn from, when the terms, the dates and the response were written down at the time instead of rebuilt from an inbox.

Where a supplier-side record fits

A spreadsheet can hold everything above if someone builds and maintains it by hand. It starts a clock, flags an overdue response or connects history across customers only if someone builds that in.

Supplier CAR Response Desk is designed to be the supplier chargeback quality record on your side of the desk. Each request is its own record with customer, part, severity and received date. Per-customer response rules, which you set from each customer's own manual, are built to start a containment clock and a plan clock, with reminders and an overdue state.

On the Professional tier and above, the fee-exposure view is designed to calculate exposure from the fee terms you enter from your own customer's manual. The Response Desk does not know any customer's fees. Cross-customer search and repeat-failure flags are also Professional and above, and are built to help you see the same cause across customers. All records are designed to export to CSV.

The Response Desk records and calculates; it is not advice or certification. It is built to work alongside the customer portals your customers require. You keep your own record and re-key from a copy-friendly field view. Pricing is planned as one flat price per plant rather than per seat.

If you want to test these ideas against your own situation, the ROI calculator is a place to estimate your own figures.

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.