China Statutory Reporting: ERP Requirements Explained

Statutory reporting is a calendar, not a single report

Teams new to China often think of statutory reporting as 'filing the tax return'. It is broader: a set of recurring obligations across the tax authority, the market regulator, and other bodies, each with its own deadline and format, all drawing on the same underlying books. The ERP's job is to make those filings a by-product of a normal close rather than a manual project. When it does, finance spends its time on judgment; when it does not, finance spends its time re-keying numbers into government portals. This guide sets out what the obligations typically include and what to require from a system, without pretending the details are identical for every entity — they are not, and your local advisor's view prevails.

The recurring obligations your ERP should support

The exact set depends on the entity's status, but these are the common items a China ERP should be able to produce data for. Treat each as a requirement, because each has a deadline and a format a spreadsheet has to be rebuilt for.

• Periodic tax filings: VAT and surcharges on the statutory cycle, plus corporate income tax prepayment.
• Annual corporate income tax settlement (汇算清缴): reconciling accounting profit to taxable profit, with adjusting items identified and documented.
• Statutory financial statements in the required format, produced from the books rather than assembled separately.
• Annual report to the market regulator (工商年报), drawing on company and financial data.
• Statistical and other bureau filings where applicable, consistent with the same ledger.

Why the annual tax settlement is the real test

The annual corporate income tax settlement is the moment all year's differences surface at once. Accounting profit under Chinese standards must be reconciled to taxable profit, and the reconciling items — non-deductible expenses, timing differences, incentive adjustments — have to be identified, justified, and documented. An ERP that can produce the accounting figures and, ideally, flag likely reconciling items turns a frantic exercise into a structured one. An ERP that cannot means the finance team exports balances and rebuilds the reconciliation in a spreadsheet that nobody can audit next year. For a group with a China entity, this is one of the clearest measures of whether the system is genuinely localized.

The consistency requirement nobody warns you about

Because Chinese authorities increasingly cross-check data, the numbers you report should be consistent across filings. Revenue declared for VAT should align with revenue in the statutory statements and with invoiced revenue; wages in payroll filings should align with the expense recognized. When each filing is produced independently by hand, small inconsistencies accumulate and become questions. When they all derive from one ledger, consistency is automatic. This is the strongest practical argument for statutory reporting being a system capability rather than a spreadsheet discipline, and it is also why the same data foundation supports the statutory-to-group bridge described in our HQ consolidation guide.

What to require from an ERP

Keep the requirement list concrete. A system that satisfies these earns its description as China-ready; one that does not will move the work into spreadsheets, where it will stay.

• Produce statutory financial statements in the required format directly from the books.
• Support the annual corporate income tax settlement with reconciliations that are stored and auditable.
• Keep tax, statutory, and invoiced figures consistent from one source of truth.
• Handle the local chart of accounts and reporting formats as standard, not as customizations.
• Allow the data to be exported in the formats government portals require, without manual reformatting.

None of these is exotic, and all are visible in a demonstration if you ask for them directly rather than accepting a slide. For the full set of China requirements — tax, data, payroll, and reporting — see the ERP checklist for foreign companies in China.

A stylised filing calendar

Statutory reporting is easier to plan once it is drawn as a calendar rather than treated as a set of unrelated tasks. The shape is broadly the same for most entities, and it is worth mapping your own obligations onto it, confirming the specific dates and formats with a local advisor.

• Monthly or quarterly: VAT and surcharge filings, with the figures reconciled to invoiced revenue before submission.
• Quarterly: corporate income tax prepayment, drawing on the accounting profit for the period.
• Annually, early in the year: the prior year's corporate income tax settlement, reconciling accounting profit to taxable profit.
• Annually: statutory financial statements and the report to the market regulator, consistent with the filed tax figures.
• Annually: other bureau filings where applicable, drawing on the same ledger and calendar year.

Mapping the calendar matters because the obligations are interdependent. The annual settlement depends on a clean year of monthly filings; the annual report depends on the audited statements; and all of them depend on the ledger being closed and reconciled. When the calendar is visible, the work can be sequenced, and the periodic filings stop being a series of unrelated deadlines and become one continuous process.

How the ERP supports the audit trail

The difference between a filing produced from the system and one assembled by hand is not speed — it is evidence. When a figure in a return comes from the ledger, the path back to the underlying transactions is a report away. When it comes from a spreadsheet, the path back depends on a person's memory and a file that may have been overwritten. For most filings this distinction is invisible; it becomes decisive the first time an authority asks how a number was derived. The value of statutory reporting in the ERP, then, is not that it fills in the forms faster, but that every figure it produces can be traced to its source without an archaeology project.

Common pitfalls

Three pitfalls recur across entities. The first is producing filings independently, so that revenue in the VAT return does not quite match revenue in the statements and the difference has to be explained later. The second is treating the annual settlement as a year-end event rather than something prepared for through the year, which turns a manageable reconciliation into a compressed scramble. The third is assuming a global template's reporting is sufficient without checking the specific format the Chinese authorities require, which leads to exports being reformatted by hand — reintroducing exactly the manual risk that the ledger was meant to remove. Each is avoidable, and each is visible in advance if the reporting requirements are written into the system's acceptance criteria rather than discovered at the first filing deadline.