YA 2026 corporate tax filing-version control

Corporate tax filing-version control should identify the one approved YA 2026 computation, the portal draft created from it and the exact submission acknowledged by IRAS. Email labels such as final and final revised do not provide enough control.

The company remains responsible for timely and accurate filing even when a tax agent prepares or submits the return. A short version register lets a director see what changed and what was actually filed.

Fix the filing population and form

Record the legal name, UEN, basis period, Year of Assessment and filing form. Confirm whether the company will file Form C-S, Form C-S (Lite), Form C or another applicable return.

The IRAS Corporate Income Tax Filing Season 2026 page states that companies must file by 30 November 2026 unless a waiver applies. It also says directors remain responsible when a tax agent is engaged.

Keep separate records for different entities and Years of Assessment. A group folder with similarly named workbooks can create a cross-company error even when each calculation is correct.

Name the documents that form one version

A version can include the tax computation, financial statements, detailed profit and loss statement, capital-allowance schedules, donation data, loss schedules and other supporting records. List each component and its file date.

IRAS’s tax-computation guidance explains that the computation reconciles accounting profit to chargeable income through tax adjustments. The return should be completed only after the computation and supporting schedules are prepared.

Form C requires specified attachments. Form C-S and Form C-S (Lite) may not require the same uploads, but the company still needs working papers to support the figures.

Give each controlled version a unique identity

Use a version number, date, preparer and status such as working, reviewed, approved or superseded. Lock or checksum the approved file where practical. Keep formulas visible in the working copy and preserve the approved output.

Do not overwrite a reviewed workbook with later edits. Save a new version and state why it changed. A file timestamp alone does not explain the decision.

Maintain a change log for material figures, elections, claims, disclosures and attachments. Typographical changes can be grouped if they do not affect the return.

Reconcile the portal draft to the approved computation

Map each material return field to the source schedule. Use control totals for revenue, profit before tax, total adjustments, capital allowances, losses, donations, foreign tax credits and chargeable income as relevant.

The IRAS filing guidance requires the financial statements, tax computation and supporting documents to be ready before filing. It also allows a portal draft to be saved until the filing due date.

Give the draft a recorded date and preparer. If the portal pre-fills a figure, compare it with the approved source and document any difference.

Control work shared with a tax agent

Agree how files will be transferred, named and approved. The company should retain its own copy of the final computation and schedules rather than depend on a tax agent’s portal or document system.

Require the tax agent to identify every post-approval change. A correction made during portal entry still needs review if it affects a figure or declaration.

Limit approval to the named version. A director’s email saying please file does not authorise later substantive changes unless the agreed process says so.

Set one controlled cut-off for management information. Late invoices, revised accounts or a new claim should enter through the change log, not through a quiet replacement of the approved workbook. The preparer should assess the tax effect, update the connected schedules and return the revised package to the named reviewer.

Where a question remains open near the deadline, record the owner, amount, tax treatment under consideration and filing decision. Do not remove the item from the review list merely because the portal can accept a number.

Preserve attachments as submitted

For Form C, retain the PDFs uploaded, their filenames and the portal response. Check that scans are readable and that conversion has not cut off a schedule or hidden a page.

Do not keep an editable source file as the only evidence when the submitted attachment was a PDF. Preserve both where each has a purpose.

Record documents retained for possible IRAS request even if they were not uploaded with the return. The filing pack should distinguish submitted, retained and not applicable.

Use a filing-version register

Freeze the filed package and monitor follow-up

After submission, save the acknowledgement and view the filing status through the official service. Compare the filed result with the approved package one last time.

If an error is found, preserve the original filing and create a separate correction record. Do not alter the archived version to make it match a later revision.

Set reminders for the Notice of Assessment and any information request. Link later correspondence to the filed version so management can see which position IRAS is reviewing.

The YA 2026 tax-agent filing authority guide covers the approval boundary. The Singapore transfer-pricing workflow is the tax pillar cornerstone.

Clear corporate tax filing-version control turns a series of spreadsheets and portal screens into one defensible company record. The Tax Consulting hub connects the wider filing library.