YA 2026 Form C: reconcile related-party disclosures

YA 2026 Form C related-party transaction reporting should be rebuilt from the company’s financial statements and ledgers, not copied from a prior return. IRAS states that a company whose disclosed related-party transactions exceed S$15 million should answer yes at Item 31 and complete the related-party transaction tab. The categories and balances must reconcile.

Build the related-party population

List the immediate and ultimate holding companies, subsidiaries, fellow subsidiaries, associates, joint ventures and other persons treated as related parties in the financial statements. Reconcile names, jurisdictions and relationship types with the consolidation and statutory records. Record additions, disposals and periods of relationship during the financial year.

The current IRAS transfer-pricing page states the S$15 million reporting threshold and Form C requirement. The YA 2026 Form C explanatory notes describes the reporting categories, relationship types and total value. The accounting records and current IRAS instructions should lead the filing analysis.

Map transactions and closing balances

Classify sales, purchases, services, loans, interest, royalties, licence fees and other receipts or payments under the Form C categories. Add the required closing balances and reconcile totals to the financial-statement note, general ledger and supporting schedules. Investigate netting, eliminations, foreign-currency differences and manual journals.

Keep transaction reporting separate from the conclusion on arm’s-length pricing or documentation exemptions. A reported amount can still require transfer-pricing analysis, and a documentation exemption does not remove every reporting or pricing duty. Link the broader annual process to the transfer-pricing cornerstone.

Approve and read back the filed return

Have finance, tax and the responsible director review the population, categories, threshold and major variances. Preserve the submitted tab, Form C acknowledgement and the schedules used. If the company later revises the related-party form, retain the original filing and the reason for correction.

Compare the filed values with the final financial statements and transfer-pricing file. Record any post-filing adjustment or assessment change. Carry the reconciled closing balances into the next year’s opening control without treating the prior amount as automatically correct for a changed group or transaction profile.

Turn the decision into a controlled file

Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.

Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.

Review before commitment and again before closeout

Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.

Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.

Handle exceptions without rewriting history

Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.

If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.

Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.

Verify the final outcome independently

Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.

Use the Singapore transfer-pricing cornerstone for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.

Practical review checklist

• Related parties listed
• Transactions classified
• Closing balances reconciled
• Threshold independently checked
• Filed return read back

YA 2026 related-party disclosure is ready when the party population, transaction categories, closing balances and S$15 million threshold reconcile to the accounts and the filed Form C readback.