Raffles Consulting Services

Perpetual securities tax terms and facts file

Build a perpetual securities tax terms facts file without treating IRAS Advance Ruling 20/2026 as a general classification rule.

A perpetual securities tax terms and facts file should analyse the actual instrument rather than assume that an accounting label decides Singapore tax treatment. IRAS Advance Ruling Summary 20/2026 addresses one tranche issued by a listed REIT trustee and specific debt-security, qualifying-debt-security and deduction questions. Its conclusion depends on the stated arrangement.

Build the perpetual securities tax terms facts file

Collect the trust deed or instrument, offering document, subscription records, board approvals, payment history, accounting analysis and use of proceeds. Extract the issuer, holders, ranking, maturity, redemption rights, distribution formula, deferral, accumulation, enforcement, events of default and conversion or write-down features.

The IRAS Advance Ruling Summary No. 20/2026 considers whether particular subordinated perpetual securities were debt securities, whether distributions were interest eligible for qualifying debt securities treatment if other conditions were met, and whether the issuer could deduct them as interest. It does not turn every perpetual instrument into debt for tax.

Compare facts without copying the ruling conclusion

Create a feature-by-feature comparison with the published arrangement and identify every difference. Pay attention to whether returns depend on profit, issuer discretion, cumulative treatment, subordination, redemption and legal obligations. Separate the debt-security classification question from QDS conditions and the issuer’s deduction analysis.

IRAS’s income tax advance ruling guidance states that a ruling applies only to the applicant and particular arrangement, years or periods and provisions stated. Use the summary to identify questions and evidence. Obtain a fact-specific tax view or ruling where material uncertainty remains.

Reconcile issuance, payments and filing positions

Map the legal conclusion to accounting entries, withholding or exemption analysis, distributions, investor records and corporate tax computation. Preserve evidence for any QDS condition relied upon. Do not combine issuer deductibility, holder exemption and instrument classification into one unsupported conclusion.

Review the file after amendments, exchanges, waivers, deferrals, redemptions or changes to holder and issuer facts. Record whether the earlier analysis still applies. Keep advice and privileged material under suitable access controls while retaining a clear filing support schedule for authorised reviewers.

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 tax compliance 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

  • Instrument documents collected
  • Material terms extracted
  • Ruling facts compared
  • QDS conditions separated
  • Tax filings reconciled

The file is supportable when the instrument’s legal and economic terms can be traced to the tax questions actually decided, with differences, QDS conditions and filing effects analysed separately.