Information date: 6 November 2026 — Under CAS 16 and the CIT rules, a government grant is recognised when there is reasonable assurance the conditions will be met and the grant will be received. Grants tied to assets go to deferred income and are released over the asset’s useful life; grants tied to expenses may offset them in the same period. Corporate income tax law conditions non-taxable treatment on three tests: a designated purpose with a supporting funding document, a separate accounting of the funds and expenditure, and the expenditure actually being incurred. If the grant has a named purpose and you can trace the money and the spend through a dedicated code, treat it as non-taxable and prepare the add-back schedule. If the purpose is generic or the funds were commingled, recognise it as taxable income and defer only for accounting. If the grant funds an asset, build the release schedule to the depreciation profile from day one. Where the amounts are material, disclose the policy and the movement even if the note is not strictly required.
Verified facts and scope
Under CAS 16 and the CIT rules, a government grant is recognised when there is reasonable assurance the conditions will be met and the grant will be received. Grants tied to assets go to deferred income and are released over the asset’s useful life; grants tied to expenses may offset them in the same period. Corporate income tax law conditions non-taxable treatment on three tests: a designated purpose with a supporting funding document, a separate accounting of the funds and expenditure, and the expenditure actually being incurred.
Scope has to be fixed before the numbers mean anything: Designed for WFOEs receiving local subsidies, relocation compensation, R&D incentives, employment-stabilisation grants or equipment-reimbursement funds. Before opening the workpaper, confirm: whether the funding document names a specific purpose, whether a separate bank account or project code exists, whether the asset has entered service, and whether the grant was recorded as income in the period of receipt rather than deferred. Anything outside that set is a separate question with its own evidence requirement, and mixing the two is the most common way a workable plan turns into an unusable one.
For a decision on “Tool: A Government-Grant Workpaper for a China WFOE — Splitting the Deferred-Income Portion, Testing the Three Conditions for Non-Taxable Treatment and the Disclosure Note the Statutory Auditor Will Request”, keep three layers apart: the published rule or statistic, the company’s own orders and process records, and the assumptions nobody has tested yet. The first layer defines the external conditions, the second proves what is true for this business, and the third is where the risk actually sits. Public material cannot substitute for a contract, a system log, a sample or a live test.
A practical way to test the scope is to ask which parts of “Tool: A Government-Grant Workpaper for a China WFOE — Splitting the Deferred-Income Portion, Testing the Three Conditions for Non-Taxable Treatment and the Disclosure Note the Statutory Auditor Will Request” would still be true if the company changed supplier, entity or product line tomorrow. Items that survive that change belong to the rule layer and can be taken from official publications; items that do not survive belong to the operating layer and have to be rebuilt from invoices, warehouse records, customs entries or platform statements. Where Designed for WFOEs receiving local subsidies, relocation compensation, R&D incentives, employment-stabilisation grants or equipment-reimbursement funds. Before opening the workpaper, confirm: whether the funding document names a specific purpose, whether a separate bank account or project code exists, whether the asset has entered service, and whether the grant was recorded as income in the period of receipt rather than deferred, the two layers are frequently mistaken for each other, and an action plan built on the wrong one either over-complies or misses a deadline it never saw coming.
How the effect reaches operations
Accounting treatment and tax treatment run on separate tracks and only align by coincidence. A grant can be deferred for accounting purposes while being fully taxable on receipt, or taxable on receipt but excluded from taxable income if the three conditions hold — and the exclusion then requires the related expenditure to be non-deductible. The deferred-income release schedule therefore has to be reconciled against the tax adjustment each year, or the auditor will find a mismatch between the release and the declared adjustment.
Typical failures: spreading a revenue-based grant over five years when the matching expenditure was incurred in year one; claiming non-taxable treatment without a funding document that states a purpose; failing to add back the corresponding expenses, which turns an exclusion into an understatement; and omitting the deferred-income movement from the disclosure note. Auditors also query grants received by an offshore parent and on-charged to the WFOE, where the funding document names the wrong entity.
Translated into an operating sequence, Accounting treatment and tax treatment run on separate tracks and only align by coincidence. A grant can be deferred for accounting purposes while being fully taxable on receipt, or taxable on receipt but excluded from taxable income if the three conditions hold — and the exclusion then requires the related expenditure to be non-deductible. The deferred-income release schedule therefore has to be reconciled against the tax adjustment each year, or the auditor will find a mismatch between the release and the declared adjustment. That ordering matters: check applicability first, then the transmission step, and only then the size of the gap in cost or timing. When an intermediate step cannot be confirmed, the honest response is to narrow the scope of the conclusion rather than to substitute an industry average for the company’s own figures.
The cost of getting the order wrong is asymmetric. A team that checks applicability too late usually discovers it at the point where the shipment, the filing or the invoice can no longer be changed without penalty, and by then the only remaining lever is price. A team that checks early spends a few hours on questions that turn out to be irrelevant, which is cheap by comparison. On “Tool: A Government-Grant Workpaper for a China WFOE — Splitting the Deferred-Income Portion, Testing the Three Conditions for Non-Taxable Treatment and the Disclosure Note the Statutory Auditor Will Request” the practical rule is therefore to spend the first hour on scope and the second on the numbers, never the other way round.
Decision
If the grant has a named purpose and you can trace the money and the spend through a dedicated code, treat it as non-taxable and prepare the add-back schedule. If the purpose is generic or the funds were commingled, recognise it as taxable income and defer only for accounting. If the grant funds an asset, build the release schedule to the depreciation profile from day one. Where the amounts are material, disclose the policy and the movement even if the note is not strictly required.
The conditions should be written down so the decision can be re-run by someone else: Designed for WFOEs receiving local subsidies, relocation compensation, R&D incentives, employment-stabilisation grants or equipment-reimbursement funds. Before opening the workpaper, confirm: whether the funding document names a specific purpose, whether a separate bank account or project code exists, whether the asset has entered service, and whether the grant was recorded as income in the period of receipt rather than deferred. When those hold, proceed as described; when one is missing, close the gap first and decide afterwards. General accounting and tax framework information, not an audit opinion or tax advice. Treatment depends on the specific funding document and local practice; confirm with your statutory auditor and tax adviser.
Two workstreams usually have to move in parallel. The compliance workstream closes the document side of “Tool: A Government-Grant Workpaper for a China WFOE — Splitting the Deferred-Income Portion, Testing the Three Conditions for Non-Taxable Treatment and the Disclosure Note the Statutory Auditor Will Request” — registrations, confirmations, filings — while the commercial workstream protects the delivery date, the pricing already quoted and the customer commitments that were made on the earlier reading of the rules. Running them as one queue is how small documentation gaps become missed shipment dates: the commercial side waits for a certificate that could have been requested a week earlier. If the grant has a named purpose and you can trace the money and the spend through a dedicated code, treat it as non-taxable and prepare the add-back schedule. If the purpose is generic or the funds were commingled, recognise it as taxable income and defer only for accounting. If the grant funds an asset, build the release schedule to the depreciation profile from day one. Where the amounts are material, disclose the policy and the movement even if the note is not strictly required. Set one owner per workstream and one shared status sheet, and treat a red item on either side as a reason to freeze only the affected order.
Implementation checklist
- Tie every release amount to the tax adjustment line in the same workpaper.
- Keep a dedicated project code so the separate-accounting test is evidenced.
- Draft the disclosure note before fieldwork starts, not after.
- Name one decision owner, one execution owner and one review date.
- Keep the source page, access date, entity and internal evidence.
- On any change, reopen only the affected judgement.
Evidence and review
Start with the smallest test that can change the answer: Tie every release amount to the tax adjustment line in the same workpaper. Pick one real entity or one representative case, write down the continue, watch and stop conditions in advance, and record the input version, the owner, the start time and the actual result. The first pass should only look at facts that move the decision; formatting preferences are not risk.
The second pass is completed by “Keep a dedicated project code so the separate-accounting test is evidenced”, and someone who did not prepare the file should spot-check one piece of critical evidence. Typical failures: spreading a revenue-based grant over five years when the matching expenditure was incurred in year one; claiming non-taxable treatment without a funding document that states a purpose; failing to add back the corresponding expenses, which turns an exclusion into an understatement; and omitting the deferred-income movement from the disclosure note. Auditors also query grants received by an offshore parent and on-charged to the WFOE, where the funding document names the wrong entity. A single small deviation can be corrected in place; a repeated deviation, or one that touches a statutory duty or changes the economics, is what justifies pausing the affected part.
After “Draft the disclosure note before fieldwork starts, not after”, compare the actual result with the baseline rather than with the impression of the team. If the grant has a named purpose and you can trace the money and the spend through a dedicated code, treat it as non-taxable and prepare the add-back schedule. If the purpose is generic or the funds were commingled, recognise it as taxable income and defer only for accounting. If the grant funds an asset, build the release schedule to the depreciation profile from day one. Where the amounts are material, disclose the policy and the movement even if the note is not strictly required. When the arrangement is extended to more products, customers or processes, keep the same success test and one complete record per batch. If later information changes, update only the affected fields.
One last discipline keeps the file usable next quarter: write the closing note as if a colleague who has never spoken to the supplier has to act on it. That note states what was verified, on which date, against which source, and what remains open — on “Tool: A Government-Grant Workpaper for a China WFOE — Splitting the Deferred-Income Portion, Testing the Three Conditions for Non-Taxable Treatment and the Disclosure Note the Statutory Auditor Will Request” it also states which of the three actions was actually finished and which was only scheduled. Teams that skip the closing note re-litigate the same question every month, and each round costs more than the documentation would have. General accounting and tax framework information, not an audit opinion or tax advice. Treatment depends on the specific funding document and local practice; confirm with your statutory auditor and tax adviser.
Limits of the conclusion
General accounting and tax framework information, not an audit opinion or tax advice. Treatment depends on the specific funding document and local practice; confirm with your statutory auditor and tax adviser.
The limits are structural rather than cautious wording. Public sources describe rules and market conditions; they do not observe “Tool: A Government-Grant Workpaper for a China WFOE — Splitting the Deferred-Income Portion, Testing the Three Conditions for Non-Taxable Treatment and the Disclosure Note the Statutory Auditor Will Request” inside a specific company. Where the analysis quotes a second-hand interpretation, the original release has to remain reachable, and a figure that cannot be traced back does not enter the decision table. Where the point depends on Designed for WFOEs receiving local subsidies, relocation compensation, R&D incentives, employment-stabilisation grants or equipment-reimbursement funds. Before opening the workpaper, confirm: whether the funding document names a specific purpose, whether a separate bank account or project code exists, whether the asset has entered service, and whether the grant was recorded as income in the period of receipt rather than deferred, the conclusion is only as current as the last check of those conditions.
