What an "audit-ready" package actually means
Most Australian parent teams describe the China subsidiary submission as a "reporting package", but in practice they receive a folder of disconnected files: a trial balance export, some manual reconciliations, a few PDFs of bank statements, and an email with VAT screenshots.
That isn't a package. It is a starting point for the parent to rebuild the close.
An audit-ready package is the artefact a parent's external auditor can open, follow, and tie back to source without contacting the local team. It has three properties:
- Self-contained. A reviewer can move from group line to entity ledger to underlying evidence without leaving the package.
- Reconciled. Each schedule ties to the trial balance, and the trial balance ties to the previous period's signed numbers.
- Owned. Every adjustment, reclassification, and judgement has an attributable owner with a date.
If any of those three are missing, the parent absorbs the cost — usually as audit hours, restated half-years, or extra management representations.
If you are unsure how this subsidiary package handoff design is currently impacting your group close, you can run a 2-minute diagnostic via our Close Clash Calculator to see where the evidence path is breaking down.
The standard package structure that holds up
The structure below is what we use as a baseline. It is deliberately boring, because audit reliance is built on consistency rather than novelty.
Section A — Period control
- Period definition (statutory PRC view, group cut date, FX rates used)
- Roll-forward from prior signed group balance to current period opening
- Sign-offs: preparer, local reviewer, group reviewer
Section B — Trial balance and chart mapping
- Frozen PRC ASBE trial balance at the cut date
- Chart of accounts mapping table to the group chart, with version reference
- Accounts requiring split mapping flagged with rationale
Section C — Reconciliations
- Bank reconciliations to all in-scope accounts
- AR / AP aged listings reconciled to the trial balance
- VAT receivable / payable position reconciled to the most recent filing
- CIT current and deferred position with workings
Section D — Intercompany
- Counterparty-level schedule (entity, currency, balance, source)
- Matching status against parent and sister-entity records
- Open differences with owner and target resolution date
Section E — Translation and adjustments
- FX translation pack (closing rate, average rate, historical rate)
- Group adjustment journals with policy reference
- PRC-to-group equity bridge
Section F — Evidence
- Source documents indexed and linked into each schedule
- Local statutory filings (most recent)
- Tax positions, exposures, and rulings
Section G — Sign-off
- Local management representation
- Group reviewer note
- Open items log carried forward
Why this structure creates a clearer evidence path
Three quiet design choices do most of the work.
The trial balance is frozen. Once the package is issued, the underlying ledger can move on, but the package's TB cannot. Every later adjustment is journalised separately and visible. This is what allows an auditor to sample without chasing a moving target.
Adjustments live in journals, not in narrative. A journal with a date, an owner, a policy reference, and a counter-signature is a control. A narrative paragraph is not. Auditors will rely on the first; they will sample around the second.
Open items are carried forward, not deleted. When something is closed, it stays in the log with a resolution note. That history is what lets the parent argue, in next year's audit, that the control environment is operating.
What we see when packages are not designed this way
The typical pattern in groups that send "whatever the local accountant produced":
- Quarter-end close stretches by one to two weeks
- Auditors raise the same five queries every cycle
- Restatements and disclosure additions cluster in the final week of half-year sign-off
- Management representations grow longer each year as a substitute for evidence
- Group finance staff burn out on rebuilding submissions
None of those are accounting problems. They are package design problems.
The minimum upgrade path
Groups that aren't ready to rebuild the package end-to-end can still recover most of the value with three changes in one cycle:
- Freeze the trial balance at the group cut date and stop accepting later edits to that file.
- Move every group-level adjustment out of narrative and into a numbered journal.
- Carry an open-items log forward instead of clearing it each period.
Those three changes alone usually reduce avoidable back-and-forth more than any system project.