Direct answer: A supplier quality-claim/chargeback page cannot just say "nonconforming incoming material is deducted per contract." It should state when a claim can be made, how responsibility is allocated, how the amount is calculated (sorting/rework/scrap/line stop/customer claim/freight), what evidence is needed, how notification and confirmation work, how debit notes/reconciliation/set-off are handled, how a supplier can dispute, whether insurance responds, and how to prevent recurrence. Otherwise, when a supplier asks "on what basis, how much, can you set it off against payables, what if I disagree," the answer becomes an argument.
This guide is for procurement, quality, finance, legal and website teams at manufacturers in Changzhou and nearby industrial areas. It explains how to build and accept a supplier quality-claim/chargeback page. Information is current to 2026-11-02. It is a review of public regulations and project practice, not contract, claim, tax or legal advice; the specific claim scope, amount, set-off, deadlines and dispute handling depend on the contract/quality agreement, evidence, applicable law and finance/tax rules.
A claim is not "deduct whatever you like": it needs a contract/quality-agreement basis, verifiable evidence, a reasonable amount, and a notification/confirmation process. Damages are limited to the loss caused by the breach and to what was foreseeable at contract conclusion; set-off requires mutual due debts of the same kind and notice. Passing a customer penalty 100% to the supplier, or deducting from payables first and explaining later, is the fastest route to a dispute.
How does the claims/chargeback page relate to IQC, SCAR, quality agreement and payment pages?
The IQC page answers "how incoming material is inspected, judged and segregated"; the supplier audit page answers "how on-site capability is audited"; SCAR/8D answers "how the problem is corrected"; the contract/quality agreement page answers "liability, acceptance and breach"; the payment page answers "when and how to pay"; the claims/chargeback page answers "how the loss is calculated, evidenced, notified, set off and disputed." IQC is detection, SCAR is improvement, a claim is the financial consequence—they are not the same.
The common break is: nonconforming material is returned but sorting/line-stop/customer claims are never costed; the amount is decided by procurement without labour/scrap/freight records; a debit note is issued but the supplier disputes it, and the amount is simply deducted from payables; a customer claim is passed 100% to the supplier, who says "this was your design/storage issue"; set-off is done without notice/reconciliation and finance and procurement tell different stories; the same problem recurs and claims become "revenue" rather than improvement. A page that states triggers, responsibility, amount, evidence, notification, set-off, dispute and prevention gives procurement, quality, finance and legal one playbook.
| Page/entry | Answers | Audience | Cannot replace |
|---|---|---|---|
| IQC | Incoming inspection, judgment, segregation | Quality, warehouse | Loss calculation and set-off |
| Supplier audit | System/process capability, CAPA | SQE, procurement | Lot-specific claim |
| Quality agreement | Liability, acceptance, breach, claim clauses | Procurement, legal | Specific amount/evidence |
| Payment page | Milestones, credit, invoice, overdue | Finance, customer | Quality-claim basis |
| Claims/chargeback | Triggers, amount, evidence, notice, set-off, dispute | Procurement, quality, finance | Court/arbitration award |
This page map is editorial; breach liability and damages are in Articles 577, 582 and 584 of the Civil Code.
When can a claim/chargeback be made?
Common triggers: nonconforming incoming material causing return/replacement, 100% sorting, rework/repair or scrap; mixed/wrong material causing line stop/changeover; supplier-caused customer return/claim/recall; transport/packaging failure causing damage; unapproved supplier change causing quality/certification issues; repeat problems causing tightened inspection/audit/third-party testing costs. Not every nonconformity supports a claim: you need supplier breach, real loss, reasonable amount and causation, plus a contract/quality-agreement basis or legal support.
"Pass the customer claim 100% to the supplier" needs care: first establish the cause and responsibility chain—supplier material, or our design/process/storage/transport/installation; whether the customer claim includes indirect loss/goodwill/penalties that were foreseeable; whether the contract has a liability cap/exclusion. What can be passed on is the direct, reasonable, provable loss caused by the supplier's breach; unrelated loss, double counting and loss increased by failure to mitigate should not be pushed over.
| Trigger | Common loss | Key evidence | Common gap |
|---|---|---|---|
| Nonconforming incoming | Return/replace/sort/rework | IQC/NC record | No labour record |
| Mixed/wrong material | Line stop/changeover/scrap | Batch/traceability | Responsibility unclear |
| Customer return/claim | Return/claim/recall | Customer letter/8D | 100% passed on |
| Packaging/transport | Damage/rework/freight | Photos/carrier record | Responsibility not split |
| Unapproved change | Certification/testing/rejection | Change record | No notice |
| Repeat problem | Tightening/audit/third-party test | SCAR/audit report | Cost not captured |
This trigger list is editorial; specific claims follow the contract/quality agreement and evidence, and unrelated or unmitigated loss should not be passed on.
How should responsibility be allocated?
Build the responsibility chain first: supplier material/process/packaging/marking/change; our design/process/storage/transport/installation/use; customer-designated material/supplier/design; transport/warehouse/third party. If responsibility is unclear, do not deduct first and investigate later; segregate/inspect/trace/jointly confirm, and use third-party testing where needed. A customer-designated supplier does not automatically exempt the supplier, nor does it make us fully liable; allocate per contract/quality agreement and actual fault.
Common disputes: the supplier says "you gave the drawing", we say "you should have flagged it as unmanufacturable"; the supplier says "transport damage", we say "packaging was insufficient"; customer-designated material fails and the supplier says "we followed the customer". The page can say "allocate per responsibility chain/contract, resolve disputes by negotiation/testing", but not "supplier bears everything/customer-designated means none of our business".
| Stage | What to check | Evidence | Common gap |
|---|---|---|---|
| Supplier | Material/process/packaging/marking/change | IQC/SCAR/audit | All liability |
| Our side | Design/process/storage/transport/installation | Drawings/records | Pushed to supplier |
| Customer-designated | Material/supplier/design | Contract/designation | Assumed exempt |
| Transport/warehouse | Carrier/custody/handling | B/L/photos | Carrier not pursued |
| Third party | Testing/certification/outsourcing | Report/contract | Unclear |
| Mixed | Multiple causes | Joint analysis | One party blamed |
This allocation is editorial; specifics follow the contract/quality agreement, fault and causation, with testing/appraisal/legal process where needed.
How should the amount be calculated?
The amount must be "calculable, provable and reasonable": return/replacement at purchase price/freight; sorting/rework at labour hours × rate + consumables + equipment; line stop at actual stop hours/capacity loss (with production records, not a guess); scrap at material/processing cost; customer claim at the customer's actual debit/return/freight/testing, net of our share; third-party testing/audit at invoice. Whether indirect loss/goodwill/lost profit is recoverable and how much depends on the contract/law and foreseeability—not automatically all.
The Civil Code provides that damages equal the loss caused by the breach, including the benefit of performance, but not exceeding the loss the breaching party foresaw or should have foreseen at contract conclusion. So "the customer fined us RMB 1 million, deduct RMB 1 million from the supplier" may not hold; consider whether the supplier could foresee it, whether there is a liability cap and whether mitigation was taken. The page can say "calculated on actual loss/contract, with a breakdown", but not "whatever the customer fines, deduct from the supplier".
| Item | How to calculate | Evidence | Common gap |
|---|---|---|---|
| Return/replace | Purchase price + freight/duty | Invoice/waybill | Goods value only |
| Sort/rework | Hours × rate + consumables | Time/material records | No records |
| Line stop | Actual stop loss/capacity | Production/schedule | Guessed |
| Scrap | Material + processing cost | BOM/work order | Sales price used |
| Customer claim | Actual debit/return/testing | Customer letter/invoice | 100%/double count |
| Testing/audit | Third-party invoice | Invoice/report | No basis |
This calculation is editorial; loss scope and caps are in Articles 584 and 585 of the Civil Code and the contract, and this is not legal/tax advice.
What evidence chain is needed?
At minimum: contract/quality agreement/purchase order (basis); IQC/nonconformance/inspection records (fact); batch/traceability (scope); photos/video/samples (condition); SCAR/8D/supplier confirmation (responsibility); sorting/rework/line-stop/scrap records (hours/quantity/cost); customer claim letter/debit/return (downstream loss); freight/testing/third-party invoices (cost); notice/reply/reconciliation (procedure). Evidence must answer "which batch, how much, who caused it, how much loss"—a debit note alone is not enough.
Evidence should be captured at the time, not recreated later: photograph/retain samples at incoming inspection, record hours/quantity during sorting, record start/end/impact during line stop, keep customer letters/debit evidence. Electronic records should be traceable/tamper-resistant; chat records can support but not replace formal records. The page can say "claim per evidence chain", but must not publish supplier/customer/prices/defect data.
| Evidence | Proves | Form | Common gap |
|---|---|---|---|
| Contract/quality agreement | Basis/liability/cap | Signed copy | No clause |
| IQC/NC record | Nonconformity/batch | Record/photos | Only "failed" |
| Traceability | Scope/customers | Batch report | Broken chain |
| SCAR/8D | Responsibility/root cause | Report | Supplier disagrees |
| Hours/stop/scrap | Loss amount | Work order/schedule | No source record |
| Customer claim/invoice | Downstream loss | Letter/invoice | Missing proof |
This evidence list is editorial; specific requirements and probative value are determined by the contract, finance rules and dispute-resolution body.
How should notification, confirmation and reconciliation work?
Suggested flow: detect → segregate/inspect → initial notice (problem/batch/interim action) → responsibility confirmation/SCAR → loss calculation → debit note/claim letter (amount/breakdown/evidence/deadline) → supplier confirmation/objection → reconciliation → set-off/payment/invoice. Notice should be written (email/system) with batch, quantity, amount, basis, deadline and objection channel; a WeChat message saying "we will deduct this order" is not enough.
Confirmation does not mean "the supplier must sign in agreement": if the supplier does not reply/confirm, follow the contract's objection period/deemed-confirmation clause (if any), but a standard clause cannot deprive a reasonable right to object. Reconciliation should show claims and payables/invoices separately, so a "quiet deduction from the payment" does not break the reconciliation. The page can say "written notice/breakdown/objection period/reconciliation", but not "deemed agreed/final interpretation is ours".
| Step | What to do | Evidence | Common gap |
|---|---|---|---|
| Initial notice | Problem/batch/containment | Email/system | Verbal |
| Responsibility | SCAR/joint analysis | Report | Deduct first |
| Loss calculation | Breakdown/unit price/quantity | Calculation sheet | Guessed |
| Debit note | Amount/basis/deadline | Document | No breakdown |
| Objection | Period/channel/review | Record | No channel |
| Reconciliation/set-off | Separate from payables/confirm | Statement | Hidden deduction |
This flow is editorial; specific deadlines, confirmation and objection rules follow the contract/quality agreement and finance policy.
How should debit notes, set-off and invoices be handled?
A debit note is a commercial claim/chargeback notice, not a tax invoice and not a court judgment; it must attach the breakdown/evidence/basis. Set-off requires Article 568 of the Civil Code: mutual debts, same kind/quality, the other party's debt due, and not a case where set-off is prohibited; the party claiming set-off must notify the other, effective on arrival, and may not attach conditions/terms. If the contract prohibits set-off, follow the contract; for SME payments, also check the Regulations on Ensuring Payments to Small and Medium-sized Enterprises.
Invoices/tax need separate handling: a quality deduction may be a price reduction, compensation or liquidated damages; the tax treatment (red-letter invoice/input transfer-out or no invoice) differs. Do not simply reduce an invoice through a "deduction" without the tax process. Follow current tax rules and the competent tax authority's position, confirmed by finance/tax. The page can say "debit note/reconciliation/per tax rules", but not "deduct freely/no invoice needed".
| Item | Key point | Evidence | Common gap |
|---|---|---|---|
| Debit note | Amount/breakdown/basis/deadline | Document | Total only |
| Set-off conditions | Mutual/same kind/due | Contract/statement | Forced deduction |
| Set-off notice | Effective on arrival/no conditions | Email/receipt | No notice |
| Contract restriction | No set-off/procedure | Contract | Ignored |
| Invoice/tax | Reduction/compensation/penalty differ | Invoice/tax advice | Direct write-off |
| SME payment | Payment deadlines/no forced bills | Regulation/contract | Deduction instead of payment |
Set-off rules are in Article 568 of the Civil Code; invoice/tax follows current rules and the competent tax authority, and this is not tax advice.
What if the supplier disputes?
Provide an objection channel and deadline: the supplier may submit an objection/evidence within a set period after the debit note; procurement/quality/finance review jointly; use third-party testing/appraisal, joint stocktaking or recalculation where needed. Reply in writing; if negotiation fails, follow the contract's dispute-resolution clause (negotiation/mediation/arbitration/litigation). Do not ignore objections, blacklist immediately or delay indefinitely, and do not pressure a small supplier by refusing to process.
During a dispute, decide whether to continue supply/payment per the contract and business continuity; you may "pay the undisputed part first and hold the disputed part", but explain in writing—do not stop all payment or deduct everything. If the supplier becomes insolvent/unreachable, file the claim/preserve assets promptly and watch the limitation period. The page can say "objection/review/dispute resolution", but not "final interpretation/no objection allowed".
| Step | What to do | Evidence | Common gap |
|---|---|---|---|
| Objection period | Days/channel after receipt | Debit note | Not stated |
| Review | Procurement/quality/finance joint | Review record | One side decides |
| Testing/appraisal | Third party/joint | Report | Refused |
| Negotiation/mediation | Meeting/options | Minutes | Delayed |
| Arbitration/litigation | Per contract clause | Filing materials | Time-barred |
| Insolvency/unreachable | File claim/preserve assets | Filing record | No pursuit |
Dispute handling is editorial; specifics follow the contract's dispute-resolution clause and applicable law, and this is not legal advice.
What about insurance, recovery and prevention?
Distinguish the insurance: product liability insurance covers third-party bodily/property loss, not supplier incoming claims; cargo insurance covers transport loss; credit insurance covers receivables, not quality claims. The "insurance" for a supplier claim is usually the supplier's product liability/quality warranty, or our retained quality risk; whether it responds and how to recover depends on the policy/contract. If the supplier is insolvent/unreachable, recovery is difficult—prevention through admission, security, second source matters.
Prevention matters more than claims: admission audit, sample/PPAP, IQC, SCAR, performance grading, contract clauses (liability/cap/notice/set-off), second source, tightened inspection for key materials. A claim is not a "revenue tool": treating claims as profit pushes suppliers to cut corners/exit, hurting delivery/quality. The page can say "claims compensate loss/drive improvement", not "claims are revenue/heavy penalties for all".
| Item | Coverage/role | Evidence | Common gap |
|---|---|---|---|
| Product liability | Third-party bodily/property | Policy | Assumed all-risk |
| Cargo insurance | Transport loss | Policy/B/L | Mixed with quality |
| Credit insurance | Receivables | Policy | Treated as quality cover |
| Supplier warranty | Warranty/indemnity | Contract/guarantee | No security |
| Recovery | Negotiation/litigation/insolvency filing | Records | Time-barred |
| Prevention | Admission/IQC/SCAR/second source | Records | Claims only |
Insurance/recovery is editorial; coverage follows the policy/contract, and this is not insurance or legal advice.
| Prevention | Role | Evidence | Common gap |
|---|---|---|---|
| Admission/sample/PPAP | Verify capability first | Audit/approval | Admit then audit |
| IQC | Lot gatekeeping | Inspection record | Exemption abuse |
| SCAR/8D | Root cause/prevention | Report/verification | Close on receipt |
| Performance grading | Tighten/downgrade/exit | Scorecard | No review |
| Contract clauses | Liability/cap/notice/set-off | Contract | Missing clauses |
| Second source | Supply/quality backup | List | Single source |
Prevention measures are editorial; specifics follow the supplier management procedure, contract and quality agreement.
What should the page say, and what must not be published?
A public page should include: claim triggers, responsibility principles, amount calculation, evidence requirements, notification/confirmation/reconciliation, debit note/set-off, objection/dispute, insurance/recovery, prevention and a contact route. Do not publish: supplier names/prices/deduction amounts, customer lists/claim details, specific defect data, open disputes, or the full contract. Wording must be precise: "claim per contract/evidence/actual loss, notify/reconcile before set-off", not "deduct at will/pass on whatever the customer fines/final interpretation is ours".
The page should distinguish "towards customers" and "towards suppliers": customers see quality responsibility/after-sales; suppliers see the claim rules; do not put customer claim letters/supplier debit notes online. Keep versions/dates when updating; review when contract/tax rules change.
| Page wording | Problem | Suggested wording | Basis |
|---|---|---|---|
| "Any nonconformity is deducted" | Ignores responsibility/evidence | State trigger/responsibility/evidence | Contract/Civil Code |
| "Pass on whatever the customer fines" | Foreseeability/cap/causation | State actual loss/reasonable scope | Civil Code 584 |
| "Deduct directly from payment" | Set-off conditions/notice | State reconciliation/notice/conditions | Civil Code 568 |
| "Final interpretation is ours" | Deprives objection | State objection/review/dispute | Contract/law |
| Publishing supplier deductions | Confidentiality/reputation | Internal/redacted only | Confidentiality |
| "Claims are revenue" | Damages cooperation | State compensation/improvement | Supplier management |
These red lines are editorial; whether a claim/set-off stands is determined by the contract, evidence and dispute-resolution body, and this is not legal advice.
Go-live acceptance checklist
Ten checks: triggers/basis, responsibility, amount calculation, evidence chain, notification/confirmation, debit note/set-off, objection/dispute, insurance/recovery, public boundaries, and updates/evidence. Each needs an owner, evidence and review date. The pass condition is not "the page says we can deduct", but that supplier/customer can understand the rules, the company can execute the same process, and disputes have a channel.
Before go-live, run one real claim through: nonconformity → responsibility → loss → notice → confirmation → debit note → set-off/payment → dispute. Any step that fails is a gap in the page or the process.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Trigger/basis | Contract/quality agreement/case | Clause/list | Add basis |
| Responsibility | Chain/fault/causation | Analysis record | Add analysis |
| Amount | Breakdown/unit price/quantity | Calculation sheet | Add calculation |
| Evidence | Batch/fact/loss/downstream | Evidence pack | Add evidence |
| Notice/confirmation | Written/deadline/channel | Email/receipt | Add notice |
| Debit/set-off | Conditions/notice/reconciliation | Documents | Add process |
| Objection/dispute | Review/testing/arbitration | Records | Add channel |
| Insurance/recovery | Policy/security/filing | Policy/records | Add cover |
| Boundaries | No supplier/customer/amount disclosure | Page test | Remove |
| Update | Date/version/reviewer | Version record | Add update |
This checklist is editorial; specific claim/chargeback requirements follow the contract/quality agreement, finance/tax rules and applicable law.
Who should read this, who should not, and what decisions does it support?
It suits manufacturers in Changzhou and nearby areas with purchasing/outsourcing, frequent incoming nonconformity, customer claims/line stops/sorting, or many supplier deduction disputes—especially equipment, auto parts, electronics, metal processing, injection moulding and assembly; it also suits suppliers assessing a buyer's claim rules. It does not suit no-purchasing/customer-supplied-only operations, or teams wanting one page to replace contract/evidence/legal process.
Read it if you are in procurement, quality, finance, legal or a website vendor; you are building a claim/chargeback page, handling incoming nonconformity loss, issuing debit notes, or doing supplier set-off/disputes; or you need to answer "can we deduct, how much, how to prove, can we set off, what if they disagree." Skip it if you treat deduction as revenue, deduct before proving, or want a page saying "final interpretation is ours". It supports self-review of triggers, responsibility, amount, evidence, notice, set-off, dispute, insurance and prevention.
Lingyi Information is a website development and enterprise AI project provider, not a contract, claim, tax or legal body. This article is not a substitute for contract/quality agreement, finance/tax advice or legal advice. Changzhou projects are delivered remotely or on site as confirmed per project; Lingyi is one candidate, does not claim a local office or team, and does not promise claim success, recovery, conversion or inquiries.
FAQ
Can we deduct for any nonconforming incoming material?
Not necessarily. You need a contract/quality-agreement basis, supplier breach, real loss, causation and a reasonable amount; segregate/inspect/trace/confirm responsibility first, then notify/calculate/set off. A nonconformance report alone is not enough, and unrelated or unmitigated loss should not be passed to the supplier.
How is the amount calculated, and can we pass the whole customer claim to the supplier?
Calculate actual, reasonable, provable loss: return/replacement, sorting/rework hours, line stop, scrap, customer actual debit/return/testing, freight. Do not pass a customer claim 100% without checking the responsibility chain, whether the supplier could foresee it at contract conclusion, the contractual liability cap and mitigation; under the Civil Code, damages are limited to the loss caused and the foreseeable loss.
What if the supplier disagrees?
Provide a written objection channel/deadline, joint review by procurement/quality/finance, and third-party testing/appraisal where needed; if negotiation fails, follow the contract's dispute-resolution clause (arbitration/litigation). During the dispute you may "pay the undisputed part and hold the disputed part", but explain in writing; do not stop all payment or deduct secretly.
Can we set off directly against payables?
Article 568 of the Civil Code requires mutual debts, same kind/quality, the other party's debt due, and no prohibition on set-off; the party claiming set-off must notify the other, effective on arrival, without conditions/terms. If the contract prohibits set-off, follow it; for SME payments, also check the relevant regulations.
Does a deduction require an invoice/red-letter invoice?
It depends on the nature: price reduction, compensation and liquidated damages are treated differently for tax; a red-letter invoice/input transfer-out may or may not be required. Do not simply reduce an invoice through a "deduction" without the tax process; follow current tax rules and the competent tax authority, confirmed by finance/tax.
How do we recover if the supplier is insolvent/unreachable?
Fix evidence/reconciliation promptly, file the claim/preserve assets under the contract/law, and watch the limitation period; claim under guarantees/letters of guarantee/insurance where available. Prevention matters more: admission audit, security/retention, second source and tightened inspection for key materials.
One-sentence takeaway
A Changzhou manufacturer's supplier quality-claim/chargeback page should not be "deduct for any nonconformity". It should turn triggers and basis, responsibility, amount calculation, evidence chain, notification/confirmation, debit note/set-off, objection/dispute, insurance/recovery and prevention into a verifiable checklist—so suppliers understand the rules and the company executes one process.
Method and limitations
This is a review of public regulations and project practice, not contract, claim, tax or legal advice on any company's contracts, claims, deductions or disputes. No undisclosed supplier lists, prices, deduction amounts, customer claims or dispute details were used. Triggers, checklists, calculations and the acceptance checklist are editorial suggestions, not legal/tax conclusions. Specific claim scope, amount, set-off, deadlines and dispute handling depend on the contract/quality agreement, evidence, applicable law and finance/tax rules.
Sources and scope
Information is current to 2026-11-02. The following are public official pages; their scope, version and wording control.
- Civil Code of the PRC, Articles 509, 568, 577, 582, 584 and 585: Supreme People's Court. Full performance/good faith, set-off conditions and notice, breach liability, remedies for nonconforming performance, damages and foreseeability, adjustment of liquidated damages.
- Product Quality Law of the PRC (2018 amendment), Articles 26 and 40: Hami Municipal People's Government (NPC text reprint). Producer responsibility for product quality; seller repair/replacement/return/compensation rules.
- Regulations on Ensuring Payments to Small and Medium-sized Enterprises (State Council Order No. 802, in force 1 June 2025): The State Council of China. Payment deadlines, prohibition on forcing SMEs to accept commercial bills or other non-cash payment, overdue interest; applies to procurement by public bodies/large enterprises from SMEs.