Direct answer: A procurement performance-bond and quality-retention page is not just "write 5% retention in the contract". The page should state: types (bid/performance/advance payment/quality retention/warranty bond), amount/percentage/cap, term (performance/defect liability/warranty), form (cash/bank guarantee/insurance bond/parent guarantee), release conditions/application/approval/deadline, set-off/claims/liquidated damages/quality chargeback, guarantee verification/expiry/extension/call, register/finance/archive, dispute handling, public boundary. On the rules: MOF Internal Control Application Guideline No. 16 (Contract Management) requires performance/change/dispute/archive; No. 7 (Procurement) requires contracts/acceptance/payment/records; No. 15 (Comprehensive Budgeting) requires budget/execution/assessment. This article is current to 2026-11-10 and is a summary of public rules and page method, not legal/finance/procurement advice; the contract, tender documents, company policy and applicable law control.
This article is for procurement, legal, finance, quality, engineering and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a procurement performance-bond and quality-retention page. The usual gap is "percentage only, no release, cash/guarantee mixed, expired guarantee, quality chargeback without basis, release without approval, missing register, no dispute path", ending with a page that only says "collect a bond to secure performance", while release/claims/audit still disagree.
A bond is not "money deducted": state type/percentage/term/form/release conditions. Cash, bank guarantees and insurance bonds differ in verification/expiry/claims. Quality chargeback/liquidated damages/set-off need basis/notice/approval. Release needs application/acceptance/approval/deadline, with register/finance/archive following up.
How does this page relate to payment terms, guarantee verification, liquidated damages/deposit, quality claims and contract-change pages?
The performance/quality bond page answers "how much to collect, when to return, how to deduct, how to manage guarantees"; the payment terms/settlement page answers "terms/milestones/invoices"; the insurance/guarantee verification page answers "authenticity/validity"; the liquidated damages/deposit page answers "breach/deposit penalty"; the quality claim/chargeback page answers "responsibility/amount/set-off"; the contract change page answers "how terms change". The bond page is the main page for "security/retention" and cannot be replaced by payment or liquidated-damages pages.
Common breaks: percentage only; no release; cash/guarantee mixed; expired guarantee; quality chargeback without basis; release without approval; no register; no dispute path. The page separates "types—amount—form—release—set-off—register—boundary" so procurement/legal/finance/quality/engineering share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Performance/quality bond | How much/when to return/how to deduct | Types, percentage, form, release, set-off | Payment terms |
| Payment terms/settlement | Terms/milestones/invoices | Prepayment, terms, documents | Security/retention |
| Guarantee/insurance verification | Authenticity/validity | Verification, expiry, claim | Bond governance |
| Liquidated damages/deposit | Breach/deposit penalty | Liquidated damages, deposit, loss | Performance security |
| Quality claim/chargeback | Responsibility/amount/set-off | Claim, chargeback, set-off | Bond release |
| Contract change | How terms change | Change, supplement | Security management |
Page relationships are editorial; the contract, tender documents, company policy and applicable law control.
What types of bonds exist, and how should each be accepted?
At minimum: bid bond (tendered projects, per tender documents/rules), performance bond (contract performance), advance-payment guarantee/bond (recovery of prepayment), quality retention/retention money (warranty/defect liability period), warranty bond/maintenance bond (replacing cash), parent/third-party guarantee (group/affiliate). For each, state purpose, applicable contract, amount/percentage/cap, term, form, release/claim conditions and owner. Do not mix bid bond with performance bond; do not mix quality retention with retention money/final payment; do not treat a guarantee as "cash received". Guideline No. 16 requires performance/change, No. 7 requires contracts/payment/records.
Acceptance checks: types; applicability; amount/percentage; term; form; release/claim; owner; distinction. Common gaps: mixed types; unsupported percentage; unclear term; mixed forms; no owner.
| Type | What to write | Evidence | Common gap |
|---|---|---|---|
| Bid bond | Tender documents/rules/return | Tender file | Mixed with performance |
| Performance bond | Contract performance, percentage/term | Contract | Unsupported percentage |
| Advance-payment guarantee | Prepayment recovery, reduction | Guarantee | No reduction |
| Quality retention | Warranty/defect liability, release | Contract | Mixed with final payment |
| Warranty bond | Replacing cash, claim | Guarantee | Treated as cash |
| Parent guarantee | Group/affiliate, scope | Guarantee | Unclear scope |
| Term | Performance/defect/warranty | Contract | Mixed term |
| Owner | Procurement/finance/legal/quality | Policy | No owner |
Types/percentages are editorial; the contract, tender documents, company policy and applicable law control.
How should amount, percentage and term be set and accepted?
At minimum: contract-value basis (tax-inclusive/exclusive), percentage/cap, currency, term (performance/defect liability/warranty), reduction/staging, interest, release conditions and overdue liability. Percentages are not a single statutory standard; agree per contract/tender documents/risk/industry practice. Quality retention should match the warranty/defect liability period—not "2-year warranty, 1-year retention". Advance-payment guarantees should reduce as the prepayment is recovered. Cash bonds tie up cash/credit; guarantees consume credit lines/fees. Amount/term changes follow contract change/supplement. Guideline No. 15 requires budget/cash flow, No. 16 requires contract/change.
Acceptance checks: basis; percentage/cap; currency; term; reduction/staging; interest; release; overdue; change. Common gaps: mixed basis; arbitrary percentage; mismatched term; no reduction; no interest; unsigned change.
| Element | What to write | Evidence | Common gap |
|---|---|---|---|
| Basis | Tax-inclusive/exclusive, contract value | Contract | Mixed basis |
| Percentage/cap | Percentage, cap, rationale | Contract | Arbitrary |
| Currency | RMB/foreign currency/FX | Contract | Mixed currency |
| Term | Performance/defect/warranty | Contract | Mismatched |
| Reduction/staging | Prepayment recovery/staged release | Contract | No reduction |
| Interest | Interest/no interest/rate | Contract | No interest |
| Release conditions | Acceptance/defect/final payment | Contract | Unclear |
| Overdue/change | Overdue liability/change agreement | Contract | No change |
Amount/term are editorial; the contract, tender documents, finance and applicable law control.
How should cash, guarantees and insurance be selected and accepted?
At minimum: cash bond (receipt/escrow/interest/return), bank guarantee (on-demand/conditional, verification, expiry, extension, call), insurance bond/surety (insurer/terms/claims), parent/third-party guarantee (scope/term/enforcement). Selection depends on cash tied up, credit lines, fees, risk, enforceability and supplier acceptance; cash is direct but ties up cash; guarantees need verification/expiry/terms; insurance has exclusions. Guarantees should state beneficiary/amount/validity/claim conditions/reduction/governing law; remind/extend/call before expiry. Link to guarantee/insurance verification pages.
Acceptance checks: form; receipt/escrow; verification; validity; claim conditions; reduction; extension; fees; exclusions; enforcement. Common gaps: no verification; expired; unclear terms; insurance exclusions; unclear guarantee scope.
| Form | What to write | Evidence | Common gap |
|---|---|---|---|
| Cash | Receipt/escrow/interest/return | Bank | Not received |
| Bank guarantee | On-demand/conditional, verification | Guarantee | No verification |
| Insurance bond | Insurer/terms/claims | Policy | Exclusions |
| Parent guarantee | Scope/term/enforcement | Guarantee | Unclear scope |
| Validity | Expiry/extension/call | Register | Expired |
| Reduction | Prepayment/staged | Guarantee | No reduction |
| Fees/credit | Guarantee fee/credit line | Finance | Cost ignored |
| Enforcement | Claim/litigation/jurisdiction | Legal | Unenforceable |
Forms/selection are editorial; the contract, guarantee terms, finance and legal advice control.
How should release, return and set-off be accepted?
Release at minimum: conditions (acceptance/delivery/defect liability expiry/warranty expiry/no outstanding claim), application (supplier/project), evidence (acceptance/defect closure/final payment/invoice), approval (procurement/quality/finance/legal), deadline (contract days), method (cash return/guarantee return/release), interest, overdue. Set-off at minimum: quality claims/liquidated damages/repairs/freight/other payables, basis (contract/claim/reconciliation), notice, approval, order of set-off, remaining release. Release is not "automatic at expiry"; it needs conditions and approval; set-off is not "deduct at will"; it needs basis/notice. Guideline No. 16 requires performance/disputes, No. 7 requires payment/records.
Acceptance checks: conditions; application; evidence; approval; deadline; method; interest; overdue; set-off basis; notice; order. Common gaps: automatic release; no acceptance; no approval; delay; no basis; unclear order.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Release conditions | Acceptance/defect/warranty/no claim | Contract | Automatic release |
| Application | Supplier/project application | Form | No application |
| Evidence | Acceptance/defect closure/final payment | Record | No acceptance |
| Approval | Procurement/quality/finance/legal | Approval | No approval |
| Deadline | Contract days/overdue | Contract | Delay |
| Method/interest | Cash/guarantee/release, interest | Finance | No interest |
| Set-off basis | Claim/liquidated damages/freight | Document | No basis |
| Notice/order | Notice, set-off order, remainder | Letter | Unclear order |
Release/set-off are editorial; the contract, claim documents, finance and legal advice control.
How should the register, finance and archive be accepted?
Register at minimum: contract/supplier, type, amount/currency, form, effective/expiry, release conditions, released/remaining, set-off, guarantee number/issuer, owner, status. Finance at minimum: cash bond receipt/escrow/interest, guarantee fee/credit line, release/set-off entries, overdue/dispute; follow accounting standards/policy (this is not accounting advice). Archive at minimum: contract/tender documents, guarantee/policy, acceptance/defect, release application/approval, set-off/claim, letters. Remind/extend/call before expiry; link to contract register/payment plan/budget. Guideline No. 16 requires register/archive, No. 7 records, No. 15 budget/cash flow.
Acceptance checks: register fields; finance treatment; guarantee fee; expiry reminder; release/set-off; archive; linkage; access. Common gaps: incomplete register; cash/guarantee mixed; no reminder; scattered archive; no linkage.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Register fields | Contract/type/amount/form/expiry/status | Register | Incomplete |
| Finance treatment | Receipt/escrow/interest/fee | Finance | Cash/guarantee mixed |
| Expiry reminder | Guarantee/bond expiry | System | No reminder |
| Release/set-off | Application/approval/entries | Record | No record |
| Archive | Contract/guarantee/acceptance/letters | Archive | Scattered |
| Linkage | Contract register/payment/budget | System | Disconnected |
| Access | View/edit/approve | System | No access control |
| Disputes | Release/set-off/claim disputes | Legal | No path |
Register/finance are editorial; the company's finance policy, contracts and systems control.
How should the website page be written, and what must not be published?
Suggested sections: (1) types/applicability; (2) amount/percentage/term; (3) form/verification/expiry; (4) release/set-off; (5) register/finance/archive; (6) disputes/contact window/update date. The public page explains "types, principles, release/set-off process, boundary" and does not publish specific contracts/suppliers/amounts/percentages, guarantees/accounts, quality chargebacks/disputes or finance/system screenshots. The English page should use consistent terms (performance bond, retention money, quality guarantee, advance payment guarantee, bank guarantee, defect liability period, release, set-off, claim) and state the cut-off date.
Do not turn the bond page into "collect a bond to secure performance", and do not claim "zero risk/full refund" if it cannot be proven. The page should let procurement/legal/finance/quality/engineering judge "how much to collect, how to manage, when to release, how to deduct", without exposing contracts and amounts.
Go-live acceptance checklist
Ten checks: types/applicability; amount/percentage/term; form/verification; release conditions; approval/deadline; set-off/notice; register/finance; expiry/extension; archive/linkage; public boundary. Each needs evidence and a review date. The pass standard is not "the contract has a bond clause", but that procurement/legal/finance/quality/engineering can judge amount, form, release, set-off and dispute path.
Before go-live, run a tabletop exercise on a real (redacted) contract: type → amount/term → guarantee verification → performance/acceptance → defect/claim → release/set-off → archive, simulating "expired guarantee", "quality chargeback" and "supplier lost contact", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Types/applicability | Bid/performance/advance/quality/bond | Contract | Add types |
| Amount/term | Basis/percentage/term/reduction | Contract | Add clauses |
| Form/verification | Cash/guarantee/insurance, verification | Guarantee | Add verification |
| Release conditions | Acceptance/defect/warranty/no claim | Contract | Add conditions |
| Approval/deadline | Approval/deadline/overdue | Record | Add approval |
| Set-off/notice | Basis/notice/order | Document | Add basis |
| Register/finance | Fields/entries/fees/reminder | Register | Add register |
| Expiry/extension | Reminder/extension/call | System | Add reminder |
| Archive/linkage | Archive/contract/payment/budget | Archive | Add archive |
| Public boundary | No amounts/suppliers/accounts | Page/permissions | Take down |
The acceptance list is editorial; the contract, company policy and applicable law control.
Who should read it, who should not, and what decisions does it support?
For procurement, legal, finance, quality, engineering and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "percentage only, unclear release, expired guarantee, quality chargeback without basis, missing register". Not for teams without bond/security management, or that want one page to replace legal/finance/procurement advice.
Read it if: building a bond page; only "collect a bond"; percentage only; no release; no guarantee verification; quality chargeback without basis; missing register. Not suitable if: treating "bond" as "deduction"; "guarantee" as "cash"; "expiry" as "automatic release"; "page" as "legal/finance conclusion". Supports: types/amount, form/verification, release/set-off, register/finance and public-boundary self-checks.
FAQ
What is the difference between the bond page, payment-terms page and liquidated-damages/deposit page?
The bond page answers "how much to collect, when to release, how to deduct, how guarantees are managed"; the payment-terms page answers "terms/milestones/invoices"; the liquidated-damages/deposit page answers "breach/deposit penalty". A bond is security/retention, not a payment milestone or liquidated damages; they complement but cannot replace each other.
How should performance/quality bond percentage and term be set?
There is no single statutory percentage; agree per contract/tender documents/risk/industry practice; state tax-inclusive/exclusive basis, currency and cap; the term should match performance/defect liability/warranty—not "2-year warranty, 1-year retention"; advance-payment guarantees reduce with recovery; changes follow contract change/supplement.
Cash, bank guarantee or insurance bond?
Consider cash tied up, credit lines, fees, risk, enforceability and supplier acceptance: cash is direct but ties up cash; bank guarantees need verification/expiry/terms; insurance bonds need insurer/exclusions/claims; parent guarantees need scope/term/enforcement. No absolute best; choose per contract/risk/finance, and ensure enforceability.
When and how should it be released?
Conditions: acceptance/delivery/defect liability expiry/warranty expiry/no outstanding claim; process: application → evidence (acceptance/defect closure/final payment) → approval (procurement/quality/finance/legal) → deadline → method (cash return/guarantee return/release) → interest/overdue; not "automatic at expiry".
Can quality claims/liquidated damages be set off?
Yes per contract/claim documents, but state basis, amount, notice, approval, set-off order and remaining release; no "deduct at will". Quality claims/liquidated damages/repairs/freight need evidence; supplier objections follow the dispute path.
What if a guarantee expires/becomes invalid?
Remind before expiry, require extension/renewal/replacement; if expired, assess claim/litigation/alternative security; guarantee terms (on-demand/conditional/reduction/governing law) determine enforceability; verification/expiry/claim link to the insurance verification page. Do not discover expiry after the fact.
Should the website publish bonds/amounts/suppliers?
Usually not specific contracts/suppliers/amounts/percentages, guarantees/accounts, quality chargebacks/disputes or finance/system screenshots; it can publish bond types, principles, release/set-off process, dispute path, public boundary and update date. The goal is to let customers/suppliers understand security management, not to disclose contracts and amounts.
One-sentence takeaway
The procurement performance-bond and quality-retention page on a Changzhou manufacturer's website is not "5% deducted in the contract"; it is about turning types/applicability, amount/percentage/term, form/verification, release conditions/approval/deadline, set-off/notice, register/finance/archive, expiry/extension and public boundaries into a checkable list, so procurement/legal/finance/quality/engineering can judge how much to collect, how to manage, when to release and how to deduct.
Research method and limitations
This article is a summary of public rules and page method, not legal/finance/procurement advice. It uses no unpublished company contracts/suppliers/amounts/percentages, guarantees/accounts, quality chargebacks/disputes, finance/system screenshots or undisclosed disputes; the tables and acceptance items are editorial and not legal/finance/procurement conclusions. MOF Internal Control Application Guideline No. 16 (Contract Management), No. 7 (Procurement) and No. 15 (Comprehensive Budgeting) are public sources; the contract, tender documents, company policy and applicable law control. This article does not decide whether any specific percentage/release is reasonable, and does not promise "zero risk/full refund"; companies should set them item by item based on contract, supplier, project and finance basis.
Sources and basis
Current to 2026-11-10; the official pages below control.
- MOF Internal Control Application Guideline No. 16 — Contract Management (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Contract performance, change, disputes and archive; used for bond clauses/release/disputes.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Procurement contracts, acceptance, payment and records; used for bond/payment/records.
- MOF Internal Control Application Guideline No. 15 — Comprehensive Budgeting (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Budget preparation, execution, adjustment and assessment; used for cash tied up/cash flow/budget.