Direct answer: A procurement contract register and expiry/renewal page is not "copy contract numbers into Excel". The page should state: what the register records (number/counterparty/category/amount/tax/term/renewal/termination notice/guarantee/insurance/obligations/owner/status); how the obligation calendar is built (delivery/acceptance/payment/warranty/guarantee/insurance/price-adjustment window/reporting/audit); how far ahead to alert, who acts and how it escalates; how renewal/re-tender/termination is decided, notified and handed over; how systems/permissions/versions/attachments are managed; reporting/KPIs/audit; public boundary. On the rules: MOF Internal Control Application Guideline No. 16 (Contract Management) Article 15 requires contract registration covering conclusion, performance and change, with closed-loop management; Article 16 requires performance review/post-evaluation; Guideline No. 7 (Procurement) requires contract, acceptance, payment and records control; No. 15 (Comprehensive Budgeting) requires budget preparation, execution, adjustment and assessment. This article is current to 2026-11-10 and is a summary of public rules and page method, not legal/procurement/audit advice; the company's contract policy, authority and systems control.
This article is for procurement, legal, finance, quality, demand-owning 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 contract register and expiry/renewal page. The usual gap is "amount only, no obligation, expiry unmanaged, missed auto-renewal notice, expired guarantee/insurance, renewal without evaluation, termination without handover, systems and contract out of sync", ending with a page that only says "full contract lifecycle management", while renewal/payment/audit/disputes still disagree.
A register is not a contract index: record obligations, deadlines, amounts and owners. Expiry is not just a reminder: evaluate renewal/re-tender/termination ahead of time and keep notice evidence. Renewal is not automatic continuation: price, terms, performance and compliance must be re-confirmed.
How does this page relate to contract signing/change, stamp-duty ledger, archive, payment/budget and supplier performance pages?
The contract register and expiry/renewal page answers "what state the contract is in, when it expires, what obligations remain, who owns it, whether to renew"; the contract change/supplement page answers "how terms are changed"; the stamp-duty/contract ledger page answers "which documents are taxable and how to reconcile with tax"; the procurement archive/records page answers "how long to keep, how to archive/borrow/destroy"; the payment terms/settlement page answers "how and when to pay"; the supplier performance page answers "how to evaluate before renewal". The register is the main page for "contract status and obligations" and cannot be replaced by a stamp-duty ledger or archive page.
Common breaks: only number/amount recorded; no obligations/deadlines; no expiry alert; missed auto-renewal notice; expired guarantee/insurance; renewal without evaluation; termination without handover; systems/attachments/versions in chaos; unclear owner. The page separates "fields—calendar—expiry—alerts—renewal/termination—systems—reporting—boundary" so procurement/legal/finance/quality/demand teams share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Register/expiry renewal | Status/term/obligations/renew? | Fields, calendar, alerts, renewal/termination | Contract text |
| Contract signing/change | How terms are set/changed | Terms, approval, supplement | Register management |
| Stamp-duty ledger | Tax calculation/filing/reconciliation | Tax item, basis, filing | Performance obligations |
| Archive/records | How long/how to archive | Retention, archive, borrow, destroy | Expiry/renewal |
| Payment/settlement | How/when to pay | Terms, documents, reconciliation | Full obligation view |
| Supplier performance | QCDS/rating | Score, rating, allocation | Renewal decision |
Page relationships are editorial; the company's contract policy, authority and systems control.
What fields should the contract register have at minimum?
At minimum: contract number/version, counterparty (name/unified social credit code/account), category/project, scope/subject, amount/tax rate/currency, payment terms, delivery/acceptance, warranty, effective/expiry dates, auto-renewal/notice period, guarantee/insurance, audit right/IP/confidentiality, obligations, linked PR/PO/budget, amendment count, owner/backup, status (draft/active/expiring/terminated), attachment location. The fields must answer "where is the contract, who owns it, when does it expire, what obligations remain, how much has been paid, can it be renewed". The register should not duplicate the contract text but must locate the text and attachments.
Acceptance checks: number/version; counterparty; amount/tax; term; obligations; guarantee/insurance; owner; status; linked documents; attachments; access. Common gaps: number/amount only; incomplete counterparty/account; missing term; no obligations; no owner; scattered attachments.
| Field group | What to write | Evidence | Common gap |
|---|---|---|---|
| Number/version | Contract number, supplement, version | Register | No version |
| Counterparty | Name, credit code, account, contact | Business licence | Incomplete |
| Category/scope | Category, project, subject, boundary | Contract | Vague scope |
| Amount/tax/currency | Tax-inclusive/exclusive, tax, currency, FX | Contract | Mixed basis |
| Term | Effective, expiry, auto-renewal, notice | Contract | Missing expiry |
| Obligations | Delivery/acceptance/payment/warranty/reporting | Calendar | Not recorded |
| Guarantee/insurance | Guarantee, deposit, insurance, validity | Policy/guarantee | Expired |
| Owner/status | Owner/backup, status, linked PR/PO | Register | No owner |
The field list is editorial; the company's contract policy, systems and authority control.
How should the obligation calendar be built and accepted?
The obligation calendar should cover at least: delivery/partial shipments, acceptance/signing, payment/terms/prepayment, warranty start/end, guarantee/letter of guarantee/deposit, insurance expiry, price-adjustment window, minimum purchase/exclusivity, reporting/audit right, IP/confidentiality, renewal/termination notice. Each entry states the obligation, trigger, date/cycle, responsible department, evidence, completion status and overdue escalation. The calendar is not a "due-date reminder table"; it must drive action: reconcile before payment, inspect before acceptance, evaluate before renewal, renew the guarantee before expiry. Link to PR/PO, acceptance, invoice, payment and budget.
Acceptance checks: obligation types; trigger/date; responsible department; evidence; status; overdue escalation; document linkage; review. Common gaps: payment only; warranty/guarantee missing; no evidence; no escalation; disconnected from systems.
| Obligation | What to write | Evidence | Common gap |
|---|---|---|---|
| Delivery/partial | Date, quantity, place, partial | Order/receipt | Partial missing |
| Acceptance/signing | Standard, deadline, signer | Acceptance | No acceptance |
| Payment/terms | Terms, prepayment, documents, reconciliation | Invoice/payment | Payment only |
| Warranty | Start/end, scope, response | Quality agreement | Missing |
| Guarantee/insurance | Guarantee/deposit/insurance, expiry | Policy/guarantee | Expired |
| Price/volume | Adjustment window, minimum volume, exclusivity | Contract | Window missed |
| Reporting/audit | Reports, audit right, notice | Records | Not executed |
| Renewal/termination | Notice period, method, evidence | Letter | Notice missed |
The obligation calendar is editorial; the contract terms, company policy and system capability control.
How should expiry, renewal and termination be accepted?
Expiry management should include at least: lead times (e.g. 90/60/30 days), alert recipients, evaluation (demand/price/performance/risk/compliance/budget), options (renew/re-tender/tender/terminate/transition), approval, notice and handover. Auto-renewal must be flagged with "notice deadline/method/evidence" to avoid "forgot the notice = another year"; renewal is not copying the old terms—price/payment/warranty/guarantee/compliance must be re-confirmed; whether a renewal/re-signing of a project subject to mandatory tendering needs re-tendering is subject to applicable project rules and legal judgment. Termination should state notice, settlement, inventory/WIP, tooling/documents/access, transition/alternate and surviving confidentiality/audit.
Acceptance checks: lead time; alerts; evaluation; options; approval; notice/evidence; auto-renewal; re-tender judgment; termination handover; records. Common gaps: no lead time; missed auto-renewal notice; no evaluation; no handover; no evidence.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Lead time | 90/60/30 days, owner, escalation | Calendar | No lead time |
| Evaluation | Demand/price/performance/risk/budget | Assessment | No evaluation |
| Options | Renew/re-tender/tender/terminate/transition | Decision | Default renew |
| Approval | Amount/terms/risk approval | Approval | Beyond authority |
| Notice/evidence | Notice period, method, delivery proof | Letter | Notice missed |
| Auto-renewal | Flag, deadline, reminder, review | Register | Another year |
| Re-tender | Applicable rules, legal judgment | Opinion | Circumvention |
| Termination handover | Settlement, inventory, tooling, documents, transition | Checklist | No handover |
Expiry/renewal/termination are editorial; the contract terms, company authority and applicable rules control, and it is not legal advice.
How should alerts, roles and escalation be accepted?
Alerts should include at least: tiered lead times (e.g. 180/90/60/30/7 days), recipients (contract owner/backup/procurement lead/legal/finance/business), channels (system/email/meeting), escalation conditions (overdue/value/risk/auto-renewal), acknowledgement/closure, holidays/time zones. Roles should include at least: contract owner (business), register administrator (data), legal (terms/notice), finance (payment/budget/tax), demand department (whether to renew), management (threshold). RACI should state responsible/accountable/consulted/informed; "register in procurement, expiry unmanaged" is the failure mode.
Acceptance checks: tiered lead times; recipients; channels; escalation; acknowledgement/closure; holidays; RACI; backup; assessment. Common gaps: one reminder; no backup; unclear escalation; no acknowledgement; holiday trap; unclear responsibility.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Tiered lead times | 180/90/60/30/7 days | Rule | One reminder |
| Recipients | Owner/backup/procurement/legal/finance/business | List | Missing people |
| Channels | System/email/meeting | Record | Memory only |
| Escalation | Overdue/value/risk/auto-renewal | Rule | No escalation |
| Acknowledgement/closure | Who confirms, how to close, trace | System | Not closed |
| Holidays/time zones | Rolling rule, cross-border time zones | Rule | Missed |
| RACI | Responsible/accountable/consulted/informed | Policy | Unclear |
| Backup | Leave/exit handover | Register | No backup |
Alerts/roles are editorial; the company's policy, authority and system capability control.
How should systems, reporting and KPIs be accepted?
Systems should include at least: a single register/CLM/ERP module, required fields/validation, attachments/versions, permissions/audit trail, expiry reminders, links to PR/PO/acceptance/invoice/payment/budget/supplier master, import/export and backup. Reports should include at least: active/expiring/expired/terminated lists, overdue obligations, guarantee/insurance expiry, auto-renewal list, amendment count, renewal timeliness, data completeness, contract coverage and distribution by category/supplier/value. KPIs should drive action, not "number of register rows". Guideline No. 16 Article 15 requires registration/closed-loop management and Article 16 requires performance review; No. 7 requires traceable records; No. 15 requires budget execution/analysis.
Acceptance checks: single source; required/validation; attachments/versions; permissions/trail; reminders; system links; reports; KPIs; data quality; backup. Common gaps: multiple registers; empty fields; scattered attachments; no permissions; inaccurate reports; KPIs count rows only.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Single source | One register/system, unique number | System | Multiple registers |
| Required/validation | Key fields, logic check, duplicate check | Config | Empty fields |
| Attachments/versions | Contract/supplement/attachment/version | System | Scattered |
| Permissions/trail | Role access, change trail | Log | No access control |
| Reminders | Expiry/obligation/guarantee/insurance | System | No reminder |
| System links | PR/PO/acceptance/invoice/payment/budget | Interface | Disconnected |
| Reports | Expiry/overdue/renewal/amendment/coverage | Report | Inaccurate |
| KPIs/data quality | Timeliness/completeness/coverage | Report | Rows only |
Systems/reporting are editorial; the company's system capability, contract policy and finance basis control.
How should the website page be written, and what must not be published?
Suggested sections: (1) register positioning/relationship with contract, stamp duty, archive and payment pages; (2) fields; (3) obligation calendar; (4) expiry/renewal/termination; (5) alerts/roles/escalation; (6) systems/reporting/KPIs; (7) contact window/update date. The public page explains "fields, process, roles, alerts, renewal/termination principles, records" and does not publish specific contracts/prices/suppliers/customers, register details, expiry lists, guarantee/insurance amounts, approval opinions or system screenshots. The English page should use consistent terms (contract register, obligation calendar, expiry/renewal, auto-renewal, notice period, termination/handover, RACI, data completeness) and state the cut-off date.
Do not turn the register page into a "full contract lifecycle management" slogan, and do not claim "zero omission/100% timeliness" if it cannot be proven. The page should let procurement/legal/finance/demand teams judge "where the contract is, when it expires, what obligations remain, whether to renew, who owns it", without exposing contract and supplier information.
Go-live acceptance checklist
Ten checks: register fields; obligation calendar; expiry/renewal/termination; auto-renewal/notice evidence; alerts/roles/escalation; systems/attachments/permissions; reporting/KPIs; data quality; audit/archive linkage; public boundary. Each needs evidence and a review date. The pass standard is not "there is a register", but that procurement/legal/finance/demand teams can judge contract status, obligations, expiry, renewal options and owner, with systems and contract consistent.
Before go-live, run a tabletop exercise on a real (redacted) contract: register → obligation calendar → expiry alert → renewal evaluation → approval → notice → system update → archive, simulating "auto-renewal", "owner on leave", "guarantee expiry" and "supplier will not renew", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Register fields | Number/counterparty/amount/term/obligations/owner | Register | Add fields |
| Obligation calendar | Delivery/acceptance/payment/warranty/guarantee/insurance | Calendar | Add obligations |
| Expiry/renewal | Lead time, evaluation, options, approval | Record | Add process |
| Auto-renewal | Flag, notice deadline, evidence, review | Letter | Add reminder |
| Alerts/roles | Tiered alerts, RACI, backup, escalation | Rule | Add responsibility |
| Systems/access | Single source, attachments, trail, links | System | Add system |
| Reporting/KPIs | Expiry/overdue/renewal/completeness | Report | Add report |
| Data quality | Required/validation/de-dup/review | Sample | Add validation |
| Audit/archive | Link with archive/tax/payment | Record | Add linkage |
| Public boundary | No contracts/prices/suppliers/register | Page/permissions | Take down |
The acceptance list is editorial; the company's contract policy, authority and system capability control.
Who should read it, who should not, and what decisions does it support?
For procurement, legal, finance, quality, demand-owning and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "amount only, expiry unmanaged, missed auto-renewal notice, expired guarantee, renewal without evaluation, termination without handover". Not for teams without contract register management, or that want one page to replace legal/procurement/audit advice.
Read it if: building a register/expiry-renewal page; only "full lifecycle"; amount only; no obligation calendar; missed auto-renewal notice; renewal without evaluation; termination without handover. Not suitable if: treating "register" as "contract index"; "expiry" as "a reminder"; "renewal" as "automatic continuation"; "page" as "legal opinion/audit conclusion". Supports: fields, obligation calendar, expiry/renewal/termination, alerts/RACI, systems/reporting and public-boundary self-checks.
FAQ
What is the difference between the contract register, the stamp-duty ledger and the archive page?
The contract register manages "contract status, term, obligations, owner, renewal/termination" and is the business master register; the stamp-duty ledger manages "which documents are taxable, the tax basis, filing and reconciliation"; the archive page manages "how long to keep, how to archive/borrow/destroy". They can share a contract number but cannot replace each other: the tax ledger does not track performance obligations, and the archive page does not manage expiry/renewal.
What fields should the register have at minimum?
At least: contract number/version, counterparty/credit code/account, category/project/scope, amount/tax rate/currency, payment terms, delivery/acceptance, warranty, effective/expiry, auto-renewal/notice period, guarantee/insurance, audit right/IP/confidentiality, obligations, linked PR/PO/budget, amendment count, owner/backup, status and attachment location. The key is to answer "where, who, when, what remains, can it be renewed".
How far ahead should expiry alerts be set?
By value/risk/renewal complexity, commonly 180/90/60/30/7 days; auto-renewal contracts should separately flag the "notice deadline" and consider holidays/time zones. Recipients include owner/backup/procurement lead/legal/finance/demand department; overdue/value/risk triggers escalation. Longer is not always better; it must leave time for evaluation, approval, tender/comparison and handover.
How can auto-renewal be prevented from being missed?
Flag auto-renewal/notice period/notice method separately, set multiple advance alerts and owner/backup, keep delivery evidence of the notice, and review "renew/not renew/change terms" before expiry; system reminder plus human confirmation. Do not assume "the supplier will remind you"; a missed notice may auto-renew for another year while price/terms have not been reassessed.
Does renewal require re-tendering or price comparison?
It depends on the contract, procurement policy, value/category/risk and whether the project is subject to mandatory tendering; renewal is not copying the old terms—price/payment/warranty/guarantee/compliance/performance must be re-confirmed. Where comparison/tendering is required, follow policy; whether renewal/re-signing of a mandatory-tender project needs re-tendering is subject to applicable rules and legal judgment, and renewal must not circumvent tendering.
How should termination/non-renewal notice and handover be handled?
Send written notice per the contract notice period/method and keep delivery evidence; handle settlement, invoices, prepayment/deposit, inventory/WIP, tooling/fixtures, documents/access, surviving confidentiality/audit and alternate supplier/transition; update register status and system access. Termination is not "send an email"; it needs a handover checklist and owner.
Should the website publish contract register/expiry information?
Usually not specific contracts/prices/suppliers/customers, register details, expiry lists, guarantee/insurance amounts, approval opinions or system screenshots; it can publish register fields, obligation calendar, expiry/renewal process, alert/RACI, system/reporting requirements and update date. The goal is to let customers/suppliers understand the contract-management method, not to disclose contract positions.
One-sentence takeaway
The procurement contract register and expiry/renewal page on a Changzhou manufacturer's website is not a "contract index"; it is about turning register fields, obligation calendar, expiry/renewal/termination, auto-renewal/notice evidence, alerts/RACI, systems/attachments/permissions, reporting/KPIs, data quality, audit/archive linkage and public boundaries into a checkable list, so procurement/legal/finance/demand teams can judge where the contract is, when it expires, what obligations remain, whether to renew and who owns it.
Research method and limitations
This article is a summary of public rules and page method, not legal/procurement/audit advice. It uses no unpublished company contracts/prices/suppliers/customers, register details, expiry lists, guarantee/insurance amounts, approval opinions or system screenshots; the tables and acceptance items are editorial and not legal/procurement/audit conclusions. MOF Internal Control Application Guideline No. 16 (Contract Management), No. 7 (Procurement) and No. 15 (Comprehensive Budgeting) are public sources; the company's contract policy, authority, system capability and contracts control. This article does not decide whether any specific renewal/termination is reasonable, and does not promise "zero omission/100% timeliness"; companies should set them item by item based on contract, category, supplier and system capability.
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. Article 15: registration covers conclusion, performance and change with closed-loop management; Article 16: performance review/post-evaluation; used for the register, obligations and renewal review.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Contract, acceptance, payment and records control; used for linkage with PR/PO/acceptance/payment.
- 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 contract value/budget commitment and renewal budget review.