Direct answer: A procurement records retention page is not "keep the documents in the archive room". The website page should state which records are kept (contracts/supplements, orders/change orders, delivery notes, goods receipts/inspection, invoices, payment vouchers, statements, approvals and emails), for how long, from which date, what conditions electronic records must meet, who files and transfers them, how access works, and how appraisal and destruction are handled. On the rules: accounting archives are kept permanently or for a fixed period, generally 10 or 30 years, counted from the first day after the end of the accounting year, and those are minimum periods, with the schedule in the Measures controlling (Accounting Archives Measures Articles 14 and 15); enterprise archives are kept permanently or for a fixed period (generally 30 or 10 years), with important contracts, agreements and supplements kept permanently, general contracts and agreements kept for a fixed period, and those periods also being minimums (Enterprise Records Retention Provisions Articles 7, 8, 9 and 11); the stub of an issued invoice must be kept for 5 years, and invoices must be stored and protected from unauthorised destruction (Invoice Administration Measures Article 28); the limitation period for civil claims in court is 3 years from knowledge of the harm and the obligor, with a 20-year long stop (Civil Code Article 188). Information is current to 2026-11-07. This is a review of public rules and page practice, not legal, accounting, tax or archive advice; the schedule, the company's archive retention table and the competent authority's requirements control.
This guide is for procurement, finance, tax, legal, archive, IT and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. This page most often misses what to keep, for how long, from when, whether electronic copies count and how destruction works, ending up as "complete records, properly kept".
First separate the archive type: contracts follow enterprise archives, while vouchers/ledgers/reports follow accounting archives; then set the minimum period and the starting point; finally set electronic-archive conditions, access and destruction. The website should state records, periods, starting point, electronic copies, transfer, access, destruction and retrieval—not "keep long-term".
How does this page relate to three-way match, payment terms and contract management pages?
The retention page answers "which documents to keep, for how long, how, and what to do at expiry"; the procurement three-way match/reconciliation page answers how order, receipt and invoice align; the payment terms and settlement page answers prepayment, credit terms, acceptance bills and overdue handling; the contract/technical and quality agreement signing page answers document precedence, deviations, seals and versions. Retention is the last stage of the document lifecycle; a reconciliation or signing page cannot replace it.
Common breakpoints: only finance keeps invoices, while procurement does not keep orders/receipts/change orders; the 5-year invoice stub rule is applied to all invoices; electronic copies are stored as PDFs without metadata; transfers have no register; access has no approval; records are shredded at expiry; customer/audit retrieval cannot find them. Separate "records—periods—starting point—electronic copies—transfer—access—destruction"; then procurement, finance, archive and IT share one playbook.
| Page | Answers | Key content | Cannot replace |
|---|---|---|---|
| Records retention | What/how long/how to keep | Records, periods, start, e-records, destruction | Reconciliation/payment |
| Three-way match | Order/receipt/invoice align | PO/GR/invoice, deviations, red-letter | Retention periods |
| Payment terms | How/when to pay | Prepayment, credit, bills, overdue | Voucher archiving |
| Contract/quality agreement | Precedence/seals | Deviations, versions, signing | Archive retention |
| Tax/audit | Inspection/retrieval | Lists, sampling, deadlines | Daily filing |
| Information security | Access/backup/redaction | Roles, logs, encryption | Retention periods |
This page map is editorial; the Accounting Archives Measures, enterprise archive policy and authority requirements control.
Which records should be listed?
List the full procurement chain: contracts/supplements/framework agreements, orders/change orders, RFQs/quotes/comparisons, delivery notes, goods receipts/acceptance, inspection/nonconformity/claims, invoices (including red-letter), payment requests/vouchers/bank receipts, statements/reconciliations, approval flows/emails/chat records, and supplier qualifications/authorisations. Mark "original/electronic/system record" so the company does not keep only invoices and lose orders and receipts. The page may give the list and owners, without publishing sensitive contract terms.
Acceptance checks: record list; original/electronic; system source; owner; gap remediation. Common gaps: invoices only; orders in a salesperson's mailbox; receipts on paper in the warehouse; change orders unfiled; chat records treated as evidence; expired supplier qualifications.
| Record | Includes | Form | Common gap |
|---|---|---|---|
| Contract/agreement | Body, supplements, technical/quality agreements | Original/e-signature | Scans only |
| Order/change | PO, change, cancellation, expedite | System/written | Email only |
| RFQ/quote | RFQ, quotes, comparison | System/email | No trace |
| Delivery/receipt | Delivery note, GR, acceptance | Paper/system | Warehouse copy |
| Inspection/claim | Inspection, nonconformity, 8D, claim | System/paper | Unfiled |
| Invoice | Invoice, red-letter, list | Electronic/paper | PDF only |
| Payment | Request, voucher, bank receipt | System/bank | Finance only |
| Statement | Statement, reconciliation | System/paper | Monthly loss |
This record list is editorial; the enterprise archive scope and finance policy control.
How long is each type kept?
Three groups: (1) Accounting archives—permanent, 10 years or 30 years, per the Measures schedule, and minimum periods (Articles 14 and 15); commonly vouchers and ledgers are managed at 30 years, annual financial reports permanently, and monthly/quarterly reports and bank statements generally 10 years. (2) Enterprise archives—permanent, 30 or 10 years; important contracts, agreements and supplements are permanent, general contracts and agreements are fixed-period, and these are minimums (Provisions Articles 7, 8, 9 and 11). (3) Invoices—the issuer keeps the stub of an issued invoice for 5 years and may not destroy invoices without authorisation (Article 28); where the buyer uses an invoice as an accounting source document, the accounting-archive rules apply. The limitation period is 3 years with a 20-year long stop (Civil Code Article 188), so "minimum period" is not the end of dispute risk.
Acceptance checks: category; period; basis; minimum/extendable; take the longer where rules overlap. Common gaps: everything at 10 years; applying the 5-year stub rule to the buyer; contracts at 3 years; different electronic and paper periods; destroy at expiry.
| Type | Period | Key point | Common gap |
|---|---|---|---|
| Accounting vouchers | Generally 30 years | Per schedule; minimum | Use 10 years |
| Ledgers | Generally 30 years | Per schedule | Early destruction |
| Monthly/quarterly reports | Generally 10 years | Per schedule | Mixed with annual |
| Annual financial report | Permanent | Per schedule | Treated as 30 years |
| Bank statements | Generally 10 years | Per schedule | Unfiled |
| Contracts/agreements | Permanent or fixed | Important permanent; general fixed | All 3 years |
| Invoice stubs | 5 years | Issuer; no unauthorised destruction | Applied to buyer |
| Limitation period | 3/20 years | Not a retention period | Confused |
Periods follow the Accounting Archives Measures, Provisions No. 10, Invoice Administration Measures and Civil Code; the schedule and enterprise retention table control.
From which date does the period run?
Accounting archives run from the first day after the end of the accounting year (Article 14); enterprise archives follow the company's archive policy (formation year/project end); contracts are most safely counted from completion, termination or rescission; invoice stubs run from the year of issue; the limitation period runs from knowledge of the harm and obligor. The page should state "rule + example" rather than let staff guess. Cross-year contracts, instalments and unsettled balances need separate notes so "the clock starts at signing" does not happen.
Acceptance checks: rule; examples; cross-year; instalments; unsettled; system dates. Common gaps: from signature; from payment; instalments from the first period; destroy while unsettled; system date differs from archive year.
| Record | Start | Evidence | Common gap |
|---|---|---|---|
| Accounting archives | First day after year end | Year/register | From signature |
| Contract | Completion/termination | Contract/settlement | From signing |
| Instalment contract | Last instalment/overall end | Performance record | From first |
| Invoice stub | Year of issue | Invoice number | From receipt |
| Unsettled | Until closed | Ledger | Destroy at expiry |
| Limitation | Knowledge | Record | Confused |
Starting rules follow Articles 14 of the Accounting Archives Measures and 188 of the Civil Code; enterprise archive rules follow company policy.
What conditions must electronic accounting archives meet?
The Measures allow electronic-only retention only if all conditions are met: the source is authentic and created/transmitted by computer; the accounting system can accurately and completely receive and read the data and output standard archive formats, with handler/reviewer/approver procedures; the archive system can receive, manage and use the records and meet long-term retention requirements, with links to related paper archives; measures prevent tampering; a backup system is in place; and the records are not of permanent or other important value (Article 8). Electronic accounting materials received externally with a reliable electronic signature under the Electronic Signature Law may be archived electronically only (Article 9). Permanent/important archives and external material without a reliable signature usually still need paper or another compliant form.
Acceptance checks: source; system; format; approvals; anti-tampering; backup; retrieval; e-signature; permanent/important exception. Common gaps: PDF only; no metadata; no backup; no approval log; external invoices without signatures kept electronically only; permanent archives electronic only.
| Condition | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Authentic source | System-created/transmitted | Logs | Assembled scans |
| Readable system | Receive/read/output | System spec | Proprietary format |
| Approval flow | Handler/reviewer/approver | Workflow log | No approval |
| Archive system | Long-term/retrieval | System | Cloud drive |
| Anti-tampering | Hash/roles/audit | Configuration | Editable |
| Backup | Offsite/multiple | Backup record | Single machine |
| E-signature | Reliable external signature | Verification | Image signature |
| Permanent/important | Electronic only? | Register | All electronic |
Electronic archive conditions follow Articles 8 and 9 of the Accounting Archives Measures; archive/IT policy controls.
How should paper, electronic and originals be handled?
The page should state where the original is, how copies are marked and how electronic and paper records map to each other. Paper archives keep the original binding on transfer; electronic archives transfer with metadata; special formats transfer with the reading platform; the recipient checks the medium and technical environment (Articles 12 and 24). One transaction may have a contract original, an order system record, a paper receipt, an electronic invoice and a payment receipt, so build a retrieval chain (contract—PO—GR—invoice—payment) instead of filing only by supplier name. Scans do not automatically replace originals; state which records may be electronic-only and which need originals.
Acceptance checks: original location; copy marking; electronic copy; metadata; retrieval keys; transfer testing. Common gaps: scans as originals; chaotic naming; no index; lost metadata; unreadable special formats; inconsistent duplicate sets.
| Item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Original | Location/custodian | Register | Cannot find |
| Copy | Marking/use | Watermark/log | Treated as original |
| Electronic copy | Format/readable | System | Proprietary |
| Metadata | Archived together | Package | File only |
| Retrieval keys | Contract/PO/GR/invoice | Index | Name only |
| Transfer testing | Medium/environment | Test record | Copy only |
| Duplicate consistency | Paper = electronic | Check record | Different versions |
Original/electronic requirements follow Articles 12 and 24 of the Accounting Archives Measures; company archive policy controls.
How should filing, transfer and responsibilities be accepted?
Accounting archives formed in a year may be kept temporarily by the accounting body for one year after year-end and then transferred; a delay needs the archive body's consent, and temporary custody may not exceed three years; the cashier may not concurrently manage accounting archives (Article 11). Transfers need a register listing name, volume number, number of volumes, start/end year, archive number, required and elapsed retention, with item-by-item handover and signatures (Articles 12 and 24). Enterprise archives must be centrally managed; no individual may keep them privately or refuse to file them (Provisions Article 6). The page may describe roles and deadlines without publishing custodian names.
Acceptance checks: temporary custody; transfer deadline; register; signatures; central management; cashier separation; electronic + metadata. Common gaps: kept in finance indefinitely; no register; personal custody; cashier also archivist; electronic records not transferred; no transfer testing.
| Step | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Temporary custody | 1 year/max 3 | Policy | Indefinite |
| Transfer deadline | Consent to delay | Approval | None |
| Transfer register | Complete fields | Register | No register |
| Signatures | Handler/supervisor | Signatures | One side |
| Central management | No private custody | Policy | Department keeps |
| Cashier separation | Not concurrent | Roles | One person |
| Electronic transfer | With metadata | Package | Files only |
Filing/transfer requirements follow Articles 11, 12 and 24 of the Accounting Archives Measures and Article 6 of Provisions No. 10; company policy controls.
How should access, retrieval and copying be accepted?
The page should state who may borrow, what, with what approval, for how long, whether copying is allowed, how copies are marked and whether records may be taken abroad. Taking or transmitting accounting archives or copies abroad follows national rules (Article 25). Enterprise archive access should be registered; customer audits, tax inspections, audits and litigation retrieval need a list and deadline; personal information/trade secrets should follow minimal necessity and redaction. Keep approver, time, purpose and return status so records do not disappear unnoticed.
Acceptance checks: permissions; approval; registration; copy marking; return; cross-border; redaction; deadline. Common gaps: verbal borrowing; no register; unmarked copies; long overdue; no cross-border approval; full set given to a customer audit.
| Item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Permission | By role/scope | Configuration | Everyone |
| Approval | Purpose/term | Approval form | Verbal |
| Registration | Who/time/volume | Register | No record |
| Copying | Marking/copies | Watermark/log | Free copying |
| Return | Deadline/check | Record | Never returns |
| Cross-border | Per rules | Approval | Direct transfer |
| Redaction | Minimum necessary | Redacted copy | Full set |
Access/retrieval is editorial; cross-border follows Article 25 of the Accounting Archives Measures and national rules.
How should appraisal and destruction be accepted?
Records cannot be destroyed simply because the period has expired. The unit should appraise periodically and issue an appraisal opinion; records still needed are re-periodised; only those with no retention value may be destroyed (Article 16). Appraisal is led by the archive body with accounting, audit and disciplinary inspection participating (Article 17). Destruction requires a destruction register (name, volume number, number of volumes, start/end year, archive number, required and elapsed retention, destruction time), sign-off by the unit head, archive and accounting heads and handlers, joint supervision by archive and accounting staff, and counting/signing before and after (Article 18); electronic destruction must also meet electronic-archive rules and be supervised jointly by archive, accounting and information-system staff. Accounting vouchers for unsettled claims/debts or unfinished matters may not be destroyed even at expiry; paper is pulled into a separate volume and electronic records are separately transferred until the matter is closed (Article 19).
Acceptance checks: appraisal; opinion; destruction register; sign-off; supervision; unsettled/unfinished; electronic supervision; records. Common gaps: shred at expiry; no appraisal; no register; one-person destruction; destroy unsettled records; delete electronic records directly; no destruction record.
| Step | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Appraisal | Expiry/value | Opinion | None |
| Re-periodise | Still needed | Record | Destroy all |
| Destruction register | Complete fields | Register | No register |
| Sign-off | Heads/handlers | Signatures | One person |
| Supervision | Archive + accounting | Record | Unsupervised |
| Unsettled claims | No destruction | Ledger | Destroyed |
| Electronic destruction | Three-party supervision | Record | Delete |
| Record keeping | Register/opinion | Archive | Lost |
Appraisal/destruction follows Articles 16–19 of the Accounting Archives Measures; company archive policy controls.
How should systems, permissions and retrieval be accepted?
The archive system should retrieve by contract number, PO number, supplier, invoice number, payment number and year; permissions by role; operation logs; anti-tampering; restorable backups; electronic records and metadata as a set; interfaces or import rules with ERP/imaging/e-signature/online banking. The page may state "findable, provable, recoverable" without exposing system architecture. At acceptance, run one real (anonymised) transaction from contract to payment and see whether all documents can be found under one key.
Acceptance checks: retrieval keys; permissions; logs; anti-tampering; backup; recovery drill; interfaces; completeness. Common gaps: search by supplier only; over-broad access; no logs; untested backups; interfaces drop attachments; missing metadata.
| Item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Retrieval keys | Contract/PO/invoice/payment | Demo | Name only |
| Permissions | By role | Configuration | Everyone |
| Logs | View/download/edit | Logs | None |
| Anti-tampering | Hash/read-only | Configuration | Editable |
| Backup | Multiple/offsite | Record | Single machine |
| Recovery drill | Restorable | Drill record | Never |
| Interface | Attachments/metadata | Reconciliation | Drops files |
| Completeness | Full set | Sample | Missing |
System controls are editorial; IT/archive policy controls.
How should audit, tax and customer-questionnaire retrieval be handled?
The page may state a "retrieval list + deadline + contact" for audits, tax inspections and customer audits. Common requests: a contract, orders, receipts, invoices and payments for a supplier in a year; evidence for a claim; batch traceability. Preparation: export a list by retrieval key → check completeness → redact → approve → provide → register. Personal information/trade secrets follow minimal necessity; tax inspections must be answered as required, without refusal or concealment (Invoice Administration Measures Article 30). Do not promise "all records at any time"; state scope and deadlines.
Acceptance checks: list template; deadline; contact; redaction; approval; registration; tax cooperation. Common gaps: last-minute search; full set; no register; late; over-redaction makes records unusable; refusal.
| Scenario | What to prepare | Evidence | Common gap |
|---|---|---|---|
| Audit sampling | Contract-order-receipt-invoice-payment | List | Broken chain |
| Tax inspection | Invoices/vouchers/returns | Records | Refuse/conceal |
| Customer audit | Quality/batch/claims | Records | Full set |
| Litigation | Contract/performance/dealings | Evidence pack | Destroyed |
| Redaction | Minimum necessary | Redacted copy | Over/under |
| Registration | Who/what purpose | Register | No record |
| Deadline | Agreed/statutory | Record | Delay |
Retrieval suggestions are editorial; tax inspection cooperation follows Article 30 of the Invoice Administration Measures and other rules.
How should the procurement records retention page be written?
Suggested content: (1) scope (entities/records); (2) record list; (3) period table and basis; (4) starting rules; (5) electronic-archive conditions; (6) paper/electronic/original; (7) filing and transfer; (8) access/retrieval; (9) appraisal and destruction; (10) systems/retrieval/backup; (11) audit/tax/customer retrieval; (12) contact, version and update date. The public page explains rules and entry points; it should not publish specific contracts, supplier lists, system accounts or custodian names; after login, parties can see their own archive status. State "the schedule, enterprise retention table and authority requirements control"; do not write "keep everything 10 years/permanently".
Use consistent English terms (records retention, accounting archives, limitation period, archive transfer, appraisal and destruction, electronic accounting records, retrieval) and state the review date. Link to three-way match, payment terms and contract signing pages, but do not turn retention into a reconciliation page.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Scope | Entities/records | Policy | Vague |
| Record list | Contract to payment | List | Invoices only |
| Periods/basis | 10/30/permanent/5 | Measures/schedule | One-size-fits-all |
| Start | Year/performance/matter | Rules | Signature date |
| Electronic archive | Conditions/signature/backup | System | PDF only |
| Filing/transfer | Deadline/register | Register | Private custody |
| Access/destruction | Approval/appraisal/supervision | Records | Shred at expiry |
| Contact/version | Channel/date | Page | No version |
This structure is editorial; external statements must be truthful and verifiable, per the law, enterprise archive policy and authority requirements.
What must not be written?
High-risk claims: "keep everything 10 years" (vouchers/ledgers generally 30, contracts may be permanent); "invoice stubs are 5 years, so all invoices are 5 years" (the buyer follows accounting archives); "a PDF is enough" (system, approvals, anti-tampering, backup and metadata are needed); "destroy automatically at expiry" (appraisal, approval and supervision are required; unsettled claims cannot be destroyed); "keep archives in the finance cabinet" (central management; cashier may not manage archives); "give a customer audit everything" (minimum necessity/redaction); "publish custodians and system accounts" (internal information); "limitation is 3 years, so destroy after 3" (limitation ≠ retention; long stop 20 years). These are inaccurate or misstate periods, electronic records or destruction.
Safer wording: "This page applies to [entities/records]; records [list]; periods [permanent/30/10/5] and basis [Measures/schedule/company table]; start [rule]; electronic archives [conditions]; transfer [register]; access [approval]; destruction [appraisal/supervision]; retrieval [channel/deadline]. The law, enterprise retention table and authority requirements control." External promotion must comply with advertising and fair-competition rules; customer and supplier information needs authorisation or redaction.
Go-live acceptance checklist
Ten checks: record list, periods and basis, starting rules, electronic-archive conditions, paper/electronic/original, filing and transfer, access/retrieval, appraisal/destruction, system retrieval/backup, page wording and version. Each needs an owner, evidence and review date. The pass condition is not "the page says keep properly", but that procurement, finance, archive and IT can find records, calculate periods, complete transfers, answer retrieval and destroy safely from the page.
Before go-live, run one real (anonymised) transaction through: contract → order → receipt → invoice → payment → filing → retrieval → access. Any step that fails is a gap in the page or the process.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Record list | Contract to payment complete | List | Add list |
| Periods/basis | Categories/minimums | Measures/schedule | Re-periodise |
| Start | Rule + examples | Policy | Add rule |
| Electronic archive | Conditions/signature/backup | System | Add |
| Original/electronic | Location/index | Register | Add index |
| Filing/transfer | Deadline/register/signatures | Register | Transfer |
| Access/retrieval | Approval/register/redaction | Register | Add register |
| Appraisal/destruction | Opinion/supervision | Record | Stop |
| System/retrieval | One-key full set | Demo | Add retrieval |
| Wording/version | No "one-size-fits-all" | Page | Rewrite |
This checklist is editorial; the law, enterprise retention table and authority requirements control.
Who should read this, who should not, and what decisions does it support?
It suits procurement, finance, tax, legal, archive, IT and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies building a retention page for the first time, or facing "audit retrieval cannot find records / destruction cannot be explained". It does not suit teams with only occasional procurement, no accounting archives, or those wanting one page to replace legal/accounting/tax advice.
Read it if you are building a retention page; periods are one-size-fits-all; invoice stubs and accounting vouchers are confused; electronic copies are PDF only; transfers have no register; access has no approval; records are destroyed at expiry. Skip it if you treat "long-term" as an answer, the 3-year limitation as a retention period, a customer audit as a full-set request, or want to publish custodians/system accounts. It supports self-review of records, periods, start, electronic archives, originals, transfer, access, destruction, retrieval and page wording.
FAQ
How long should a procurement contract be kept?
Under the enterprise records provisions, important contracts, agreements and supplements are kept permanently; general contracts and agreements are kept for a fixed period (generally 30 or 10 years), and these are minimums, so a company may choose longer in its retention table (Provisions Articles 7, 8, 9 and 11). Records for unsettled matters, litigation or customer requirements should be kept until the matter is closed.
How long are invoices and goods receipts kept?
The issuer keeps the stub of an issued invoice for 5 years and may not destroy invoices without authorisation (Invoice Administration Measures Article 28); where the buyer uses an invoice as an accounting source document, accounting-archive rules apply, with vouchers generally kept 30 years (per the schedule, as a minimum). Goods receipts as source/business records follow the same accounting or enterprise-archive periods; 5 years is not enough for the buyer.
Do electronic invoices/electronic accounting records still need printing?
Where the conditions in Article 8 of the Accounting Archives Measures are met (authentic source, readable system, archive system, anti-tampering, backup, not permanent/important), electronic-only retention is allowed; electronic accounting materials received externally with a reliable electronic signature under the Electronic Signature Law may be archived electronically only (Article 9). Permanent/important archives or records that cannot meet the conditions usually still need paper or another compliant form; follow archive policy.
When does the retention period start?
Accounting archives start from the first day after the end of the accounting year (Article 14); contracts are most safely counted from completion, termination or rescission; invoice stubs from the year of issue; the limitation period runs from knowledge of the harm and obligor (Civil Code Article 188). Cross-year, instalment and unsettled items need separate notes.
Can records be destroyed at expiry?
No. Appraise first and issue an appraisal opinion; re-periodise records still needed; only those with no retention value may be destroyed. Destruction needs a register, sign-off by responsible heads, and joint supervision by archive and accounting staff; vouchers for unsettled claims/debts or unfinished matters may not be destroyed—paper is pulled into a separate volume and electronic records are separately transferred until the matter closes (Articles 16–19).
How should records be provided for a customer or audit?
Follow "list—check—redact—approve—provide—register": confirm scope and purpose, export by retrieval key, check completeness, redact personal information/trade secrets to the minimum necessary, provide and register. Tax inspections must be answered as required, without refusal or concealment (Invoice Administration Measures Article 30); the page may state deadlines and contacts but should not promise "everything at any time".
One-sentence takeaway
A Changzhou manufacturer's procurement records retention page is not about "keep properly". It should turn the record list, periods and basis, starting rules, electronic-archive conditions, originals and indexing, filing and transfer, access and retrieval, appraisal and destruction, and system retrieval into a reviewable checklist—so procurement, finance, archive and IT can keep it complete, calculate correctly, retrieve it and destroy it compliantly.
Method and limitations
This is a review of public rules and page practice, not legal, accounting, tax or archive advice. No undisclosed customer, contract, price or supplier data were used; processes, lists, tables and acceptance items are editorial, not legal/accounting conclusions. Periods and procedures follow the Accounting Archives Measures (Ministry of Finance and National Archives Administration Order No. 79), the Enterprise Records Retention Provisions (National Archives Administration Order No. 10), the Invoice Administration Measures (2023 revision) and Civil Code Article 188; the schedule, enterprise retention table, authority requirements and actual business control. This article does not reproduce every item of the accounting archive schedule; companies should map their own record names to the nearest category.
Sources and scope
Information is current to 2026-11-07. The following are official pages; their text controls.
- Accounting Archives Measures (Ministry of Finance and National Archives Administration Order No. 79): State Council Gazette. Scope (Article 3), electronic archives (Articles 8, 9), temporary custody and transfer (Articles 11, 12, 24), periods and start (Articles 14, 15), appraisal and destruction (Articles 16–19).
- Enterprise Records Retention Provisions (National Archives Administration Order No. 10): State Council Gazette. Filing scope (Article 4), central management (Article 6), periods (Article 7), important contracts permanent (Article 8), general contracts fixed-period (Article 9), minimum periods (Article 11).
- Invoice Administration Measures (2023 revision): State Taxation Administration policy database. Storage and 5-year stubs (Article 28), cooperation with tax inspections (Article 30).
- Civil Code of the People's Republic of China: Supreme People's Court. Three-year limitation and 20-year long stop (Article 188).