會計數智化的驗收單,第一次不由廠商來寫

Today is Thursday, November 19, 2026. On November 11, the Ministry of Finance issued the 'Accounting Reform and Development 15th Five-Year Plan' (Caihui [2026] No. 13). The document was signed on October 23, and the full text was made public on the Ministry of Finance website on November 16. People working in ERP should read Part VII word for word.

The reason is simple: over the past two decades, the acceptance standards for accounting informatization have basically been defined by vendors—feature lists, number of modules, whether reports can be produced, and whether the interface looks good. This plan, for the first time, has written “the specifications of accounting data itself” into a policy task, and explicitly calls for “studying and formulating evaluation methods for accounting digital-intelligence, and organizing pilot evaluation work.”

Translate into one sentence: someone else needs to write the acceptance form.

1. It didn't provide a single number

Let me start with a counterintuitive observation. This plan lists seven main objectives, all stated qualitatively: the foundation of accounting rule of law is continuously consolidated, accounting talent support is more robust, the accounting services industry develops with high quality and efficiency, accounting supervision plays a better role, the level of accounting digitalization and intelligence continues to rise, the contribution to international accounting governance is significantly enhanced, and innovative achievements are made in accounting theory development. There is not a single percentage, no coverage rate, and no annual deadlines.

0 items

The number of quantitative indicators among the seven main objectives in the plan, all are qualitative statements such as 'basically completed' and 'continuously enhanced' (Caikuai [2026] No. 13)

For people accustomed to targets like 'cover 20,000 businesses by 2028,' this is actually harder to deal with. With numbers, you can report '80% completed' to get by; without numbers, it means you cannot prove yourself and can only wait for the evaluation criteria to come out and then use materials to check against them. And the evaluation criteria are set by regulators, not by vendors, nor by enterprises themselves.

The only one that gave an explicit status phrase was the digital-intelligence item: by the end of the "15th Five-Year Plan" period, "an accounting digital-intelligence system with unified standards, controllable security, and intelligent efficiency will be basically established."

The three adjectives are actually three questions. Standardized and unified refers to the criteria; safe and controllable refers to the boundaries; intelligent and efficient refers to efficiency. Their order cannot be changed—only after unification can controllability be discussed; only after controllability can one dare to discuss intelligence.

II. Three-stage standard: input, processing, output

The plan, under “Establishing and Improving Accounting and Auditing Data Standards,” wrote a very critical sentence: coordinate the planning, formulation, and implementation of accounting data standards covering stages such as input, processing, and output of accounting information systems.

This sentence breaks the accounting system down into a three-stage pipeline. The input is vouchers, the processing is accounting, and the output is reports. The policy requirement is not "the system should be easy to use" but "the data in all three stages must meet specifications." These are two completely different languages of acceptance.

segmentTask Description in PlanningWhat does it mean to land in ERP?
InputContinue to promote the application of accounting data standards for electronic vouchers, and steadily advance paperless and automated processing across the entire process of receiving, reimbursing, recording, and archiving electronic accounting vouchers.Whether invoice types can be automatically received and verified, whether reimbursement and accounting entry use the same data, and whether original files are retained in archiving
ProcessRevise the General Taxonomy of Accounting Standards for Business Enterprises, and explore ways to promote the development of a single-source system for corporate financial reporting.Accounts, auxiliary accounting, and consolidation basis must have machine-readable mappings; they cannot rely on manual table matching by hand.
OutputResearch and formulate corporate sustainability information classification standards; improve the data standards system for certified public accountants' audits, and promote its application in accounting software, audit work software, and other areasFinancial reports and sustainability reports can be delivered digitally; audit data is extracted directly from the system, not from Excel.

There are two more that are easily overlooked. One is the accounting data standard for credit enhancement of micro and small enterprises—“using standardized accounting data to help solve the financing problems of micro and small enterprises.” What this means is that accounting data is beginning to serve as financing evidence; if the format is wrong, it will not get through at the bank. The other is more concrete: the audit data standard should cover “applications in accounting software, audit operation software, and other areas.”

The phrase “apply in accounting software” shifts the responsibility to the product side.

In the past, when auditors began fieldwork, they first spent three months cleaning data—exporting tables from systems, matching fields, and filling in ledgers; now the policy wording is that the accounting software itself must be capable of outputting data according to standards. Enterprises can use this to ask when purchasing: Can your system directly export according to audit data standards? If it cannot export, then it is not the auditor's problem.

The backdrop is not sudden. In May 2025, nine departments—the Ministry of Finance, the State Taxation Administration, the People's Bank of China, the State-owned Assets Supervision and Administration Commission, the National Archives Administration, the Standardization Administration, the Office of the Inter-Ministerial Joint Conference on National Electronic Document Management (Cryptography Administration), the Civil Aviation Administration of China, and China State Railway Group—jointly issued the Notice on Promoting the Application of Electronic Voucher Accounting Data Standards (Caihui [2025] No. 9) for nationwide promotion. What this effort does is upgrade 'promotion' into a 'system'—from the paperlessization of a single voucher to the standardization of the three stages of input, processing, and output.

In the past, it was 'invoices need to be digitized'; now, it is 'accounts need to be standardized'.

The former solves the problem of paper; the latter solves whether machines can read and understand it. There is no format dispute on paper, but there is with data.

III. Can ERP's books be delivered as standard factory output

From the enterprise's perspective, what this document truly changes is the integration boundary.

The plan is written very straightforwardly: strengthen the integration of the unit's accounting information system with business systems and archive systems, strengthen the interconnection and interoperability between the unit's accounting information system and external information systems such as finance, taxation, banks, suppliers, and customers, and build and optimize working models such as financial shared services and cloud services.

Note its direction: it is not about making the accounting system bigger, but about making its boundaries more numerous. Business systems, archive systems, tax, banks, suppliers, and customers—all six directions need to be connected. This puts pressure on ERP—the more integration points there are, the greater the gap between 'being able to run through' and 'being able to reconcile'.

Let’s give a concrete example. A purchase invoice—from the supplier issuing it, the enterprise receiving it, reimbursement and booking, to archiving—may pass through five places: email, OA, ERP, an imaging system, and an archival system. If the format is nonstandard at any one point, the chain breaks there, and everything afterward relies entirely on manual remediation. What the plan requires is end-to-end paperless automation, not paperless operation in just one segment.

The pitfall of electronic vouchers is not whether they can be received, but whether they reconcile after receipt.

With the same invoice, if the reimbursement system shows it as reimbursed, the ERP shows it as not yet posted, and the archive system shows it as archived, these three statuses coexist; usually no one notices, but as soon as an audit asks, it is exposed. The prerequisite for a fully paperless process is that the same piece of data has only one status across the three systems, rather than each of the three systems recording it separately.

The other line is supervision. The plan frames the goal as 'accelerating the clearing of existing stock and effectively curbing new additions,' and explicitly states that the principal person in charge of a unit bears primary responsibility for the unit's financial and accounting work and for the authenticity and completeness of accounting records. Anyone who works in financial systems understands the weight of this statement: when the system makes an error, the person who ultimately signs is a human. Therefore, 'automatically generated by the system' has never been a reason for exemption from liability.

In the first half of accounting digitalization, the competition is over who can turn paper into electronic form; in the second half, it is over who can turn electronic data into a format that others can understand. The former is the scanner business; the latter is the data standards business.

There is also something new worth preparing for in advance: sustainability information. The plan places the "Corporate Sustainability Information Classification Standards" alongside accounting data standards as one of the two pillars of the digital and intelligent system, and calls for promoting the pilot implementation of published standards and advancing enterprise disclosure capacity building in a categorized and phased manner. This means that in the next two to three years, the output side of financial systems will have an additional set of delivery requirements for non-financial data.

IV. The CIO's Three Acceptance Checklists

First sheet: write the three sections of standards into the acceptance clauses. Do not write phrases such as “complies with national accounting data standards”—that is as good as not writing anything. Be specific: which invoice types are supported, what the receiving method is, whether both the original documents and structured data are retained after booking, whether the archive format can be read over the long term, whether audit data extraction can be exported according to the standard, and whether sustainability information can be mapped according to the classification standard. During acceptance, tick each item one by one rather than listening to reports.

On the second page, conduct an end-to-end stress test, and deliberately create failures. What to do if voucher receipt times out, how to deduplicate repeated pushes of the same document, where the original voucher is held after posting fails, how to retain an audit trail for cross-month red reversals, how to access records after archiving, and during system switchover, which of the old and new data sets prevails. These problems can never be detected in a smooth process; they will only erupt in concentration during audits and inspections.

Acceptance FormKey fieldsWhat is being guarded against?
Standards complianceInvoice type list, receiving method, posting fields, archiving format, audit export format, sustainability information mappingIt went live, but the data was out of spec; it was only discovered when switching systems.
Exception pathTimeout, duplicate, failed and suspended, red reversal, cross-period, post-archive retrieval, dual copies of data during switchover periodThe normal flow is all green, and exception paths rely entirely on manual fallbacks.
Pre-embedded evaluationStandards compliance rate, paperless rate, number of interfaces and success rate, traceability, permissions and audit trailsThey only started supplementing materials after the evaluation pilot notice was issued.

Third, pre-embed indicators for the "evaluation pilot." The evaluation measures have not yet been issued, but the foreseeable dimensions will not go beyond the categories above. Start collecting these data in the system now; when the notice comes down, what you do is "retrieve data," not "backfill materials." The workload for these two things differs by an order of magnitude.

Past acceptanceSubsequent acceptance
Are all the modules in place, can reports be generated, and will users know how to use it? Standards are proposed by vendors, and sign-off is given by enterprises.Whether vouchers can come in automatically, whether accounts can be understood by machines, and whether data can go out according to standards. Standards are set by policy; enterprises can only comply.

By the way, a word to vendors: the policy dividend in this round does not belong to the products with the most features; it belongs to the products whose data best matches up. Sooner or later, clients will come back to you with audit and tax questions—at that point, what matters is fields and definitions, not the interface.

Return to the opening line, “someone else writes the acceptance form.” Its real meaning is not that regulation has become stricter, but that the coordinate system for evaluation has changed: in the past, the comparison was who had more features; from now on, it will be whose books can be read by machines, reconciled by audits, and matched by tax authorities.

There is no launch event for this, and no demo. It will only show up during an audit entry, a tax inspection, or a financing due diligence. And what can be brought out at that time is whether a data standard has been seriously done once in these five years.

Source: Ministry of Finance, "Accounting Reform and Development '15th Five-Year Plan'" (Cai Kuai [2026] No. 13, signed 2026-10-23, news released 2026-11-11, full text published on the Ministry of Finance website on 2026-11-16). The phrases cited in this article—"accounting data standards covering the input, processing, output, and other stages of accounting information systems," "continuously promote the application of electronic voucher accounting data standards, and steadily advance paperless and automated processing across the entire process of receiving, reimbursing, booking, and archiving electronic accounting vouchers," "revise the general taxonomy of accounting standards for business enterprises and explore promoting the establishment of a single-source system for corporate financial reporting," "promote the application of accounting data standards for enhancing credit for micro and small enterprises," "research and formulate corporate sustainability information taxonomy standards," "improve the auditing data standards system for certified public accountants and actively promote the application of auditing data standards in accounting software, audit operation software, and other areas," "strengthen the integration of entity accounting information systems with business systems and archive systems," "research and formulate evaluation measures for accounting digital and intelligent development and organize pilot evaluation work," and "accelerate the clearing of existing stock and effectively curb increments"—all come from this plan; the seven main objectives and "basically complete the building of an accounting digital and intelligent system featuring unified standards, controllable security, and intelligent efficiency" are original wording from the plan. Background document: Ministry of Finance and eight other departments, "Notice on Promoting the Application of Electronic Voucher Accounting Data Standards" (Cai Kuai [2025] No. 9, 2025-05-19).

Definition note: The plan does not set quantitative indicators throughout, nor does it provide annual deadlines. The statement “0 quantitative indicators” in this article is a summary of how the seven main objectives are phrased and does not mean that there are no work requirements; the “Accounting Digital Intelligence Evaluation Measures” are still at the “research and formulation” stage, and the specific dimensions and scoring methods have not been published. The indicators listed in this article are projections based on implementation experience, not the original policy text; the word “ERP” does not appear directly in the full text of the plan, and the ERP mapping in this article (invoice type, account mapping, audit data extraction, etc.) is a summary of implementation experience and does not represent the specific product functions required by policy.

关于我们

​我们致力于帮助中小企业实现数字化转型,我们的团队由一群充满激情和创新思维的专业人士组成,他们具备丰富的行业经验和技术专长。

扫一扫获取顾问以及手册

登入 發表評論
Copilot 當上工位,ERP 變成插座