Prepare a financial statement for a subsidy audit successfully

The Shinagawa City programme helps eligible small and medium-sized businesses in the Ward adopt automation, robotics and digital solutions. Subsidy support connects firms with vetted technology providers, while a funded project may trigger an audit requiring proof that public money was spent on the approved purpose.

The hardest task is rarely choosing a template. It is proving that every figure agrees with the grant agreement, bank activity and operational evidence. A defensible set of accounts combines sound accounting with a traceable account of what was purchased, when it happened and how it advanced the project.

The Shinagawa scheme itself is limited to eligible Ward businesses, but its evidence standard travels well to Australian operators comparing state, federal or local technology grants. Melbourne manufacturers, Brisbane wholesalers and Sydney service firms commonly manage records through Xero or MYOB, and many government-backed grants require a co-contribution rather than covering every invoice. In Australian business conversations, a sound reconciliation is often described as getting the numbers “square”.

This guide explains how to prepare a financial statement for a subsidy audit successfully, from setting the evidence scope to presenting measurable transformation results. It also explains where Australian GST, BAS and financial-year conventions can affect the pack. Programme seminars on factory digital transformation, IT investment and online sales efficiency can clarify technical requirements before a claim.

Start with the grant rules

Identify the exact document required: a profit and loss statement, balance sheet, cash-flow statement, project account or set of management accounts. Read the signed grant agreement and expenditure manual for eligible costs, funding caps, co-contribution, reporting periods, required templates and retention periods.

Treat the programme subsidy guidance as part of the evidence map rather than background reading. Compare it with the signed agreement and obtain written clarification where eligibility, timing, currency or presentation is unclear.

Create a one-page scope sheet showing the applicant, grant reference, project, approved budget, audit period, required statements and responsible finance lead. Do not reshape source records to fit the template; identify conflicts before drafting.

Create a traceable document trail

Every funded cost should resolve to an invoice or receipt, purchase order, written approval, proof of payment and the relevant project deliverable. Payroll costs need time records, while equipment should appear in the fixed-asset register. Store supporting records against the same cost reference used in the ledger.

Use a consistent folder structure and file names, such as project code, cost category, supplier and date. Keep an approved PDF or read-only export alongside editable working files, and retain source receipts rather than reconstructed copies. A simple index of links is useful, but the files themselves must remain accessible.

Record who approved each purchase, which quote was accepted and how conflicts of interest were managed. Never backdate approval or overwrite an invoice after payment. Small control failures, such as a purchase split to avoid a quote threshold, can create a larger audit issue than the original amount.

Reconcile the financial statements

Start with a trial balance that agrees to the general ledger, then reconcile cash to bank statements, payroll to payroll reports, receivables to customer balances and fixed assets to the asset register. The profit and loss statement, balance sheet and cash-flow statement should use the same reporting period and agree with each other.

Follow the applicable accounting policy and grant agreement when presenting assistance. Depending on the terms, the subsidy may reduce project cost, appear as income or be recognised over time; do not deduct it in one period and report it differently in the notes. Accruals, prepayments and capital expenditure also need consistent treatment.

If statutory accounts are required, use the framework applicable to the entity, such as Japanese GAAP for a Shinagawa business or Australian Accounting Standards for an Australian entity. If management accounts are accepted, state the basis of preparation clearly. Have a qualified accountant review arithmetic, classifications, comparatives and unusual balances before submission.

Prove eligibility of funded costs

Prepare a cost-by-cost register showing description, supplier, invoice date, payment date, ledger code, gross amount, GST or tax, proposed funding amount, recipient share and approval evidence. Reconcile this register to the general ledger and the subsidy claim so every amount has both accounting and eligibility support.

Separate capital expenditure from operating expenditure and check whether the programme reimburses the asset's purchase price or a depreciated amount. Record disposal, partial funding and grant caps accurately. Do not claim the same item twice, treat a supplier's quote as an invoice, or include expenses incurred before the approved start date without written approval.

Test procurement evidence against the grant's rules. Depending on the threshold, retain one or several comparable quotes, tender records, sole-source justification and supplier due-diligence checks. Explain related-party purchases and any variation between a purchase order, invoice and payment receipt, because reviewers often focus on these differences.

Evidence the digital transformation

Show a before-and-after result using a small set of agreed indicators. Examples include units produced per hour, machine downtime, order-pick time, defect rate, labour hours per sale and online conversion rate. State the baseline, target, actual result, measurement period and source system for every metric.

Implementation records should demonstrate that the funded solution was delivered and used. Useful evidence includes signed acceptance documents, milestone reports, training attendance, configuration records, licences, photographs and dated system logs. Protect customer and employee information through redaction, and preserve records of approvals and change requests.

Before committing funds, use the vetted technology providers directory to compare scope, qualifications and commercial terms. Ask each shortlisted provider for a detailed quotation, implementation plan and acceptance criteria. The provider's assurances can support eligibility, while invoices and completed milestones provide the stronger evidence of delivery.

Apply Australian tax and market practices

Australian reporting periods do not always match a grant period. Many sole traders use a financial year from 1 July to 30 June, while companies may choose a different tax year; a subsidy claim can still run from project approval to a different end date. Build a period bridge and label income and expenditure clearly.

For an Australian GST-registered business, GST normally passes through the Business Activity Statement and must be supported by retained records. A BAS lodgement is not proof that a cost is grant-eligible. Confirm whether the subsidy ceiling is GST-inclusive or GST-exclusive, and reconcile the accounting treatment to the grant agreement and ATO records.

The Australian grant market often uses matched funding, milestone payments or staged claims, and local councils or state agencies may impose quote thresholds. Keep quotations, grant agreements and bank receipts for the whole funding chain. For a Japanese supplier, retain the original currency invoice, translation where needed, bank conversion evidence and an explanation of fees or withholding tax.

Assemble the final audit pack

Create an index covering the scope sheet, financial statements, trial balance, general ledger, reconciliations, bank evidence, cost register, invoices, contracts, quote comparisons, approvals, milestone records, outcome measures and correspondence. Match each index entry to the grant reference and use page numbers for a printed pack or stable bookmarks for a digital one.

Run a final red-flag review for arithmetic errors, duplicate claims, unsupported balances, wrong dates, inconsistent supplier names and GST treatment differences. Check that narrative claims are supported by evidence, then ask an independent reviewer to trace several transactions from the statement to source records and back again.

Obtain authorised management sign-off on the statements and supporting explanation, but do not sign facts that have not been verified. State known limitations, unresolved queries and accounting judgements rather than hiding them. Keep the submitted pack, delivery evidence and final reviewer correspondence together for the retention period, with access limited to authorised personnel.

For eligible Ward businesses, the next practical step is to contact the Shinagawa City programme, confirm eligibility and book the relevant seminar or workshop. Teams can use sessions on factory automation, IT investment and e-commerce efficiency to identify realistic productivity gains, required evidence and likely eligible expenditure before committing capital.

Start with a subsidy-scope check, obtain firm quotations, define measurable milestones and assemble source records as the project progresses. The programme's provider network and subsidy support can then be matched to a documented, review-ready investment that strengthens competitiveness rather than relying on retrospective paperwork.