Raffles Consulting Services
Connect ACAP findings to a GST technical clarification request by separating control remediation, factual uncertainty and legal analysis.
ACAP findings and a GST technical clarification request should be connected only when the review has identified a genuine technical issue that cannot be resolved from the facts, legislation and published guidance. A control weakness, missing invoice or calculation error normally needs remediation or disclosure, not a request asking IRAS to decide an incomplete case.
The company should classify the finding, stabilise the facts and prepare one numbered issue with its own analysis and evidence. That sequence protects the ACAP review from becoming a collection of open-ended questions.
Understand the September 2026 connection
IRAS’s GST technical clarification guidelines apply from 1 September 2026. They are primarily intended for authorised tax agents, and taxpayers may also refer to them. IRAS states that the guidelines also apply to requests submitted under voluntary compliance initiatives such as ACAP.
The IRAS latest updates page records related amendments to the ACAP guidance and its review appendices. A review team should therefore use the current request requirements when an ACAP issue is escalated for clarification.
This does not mean every ACAP observation needs a separate request. The review must first determine what kind of problem was found.
Classify the finding before writing
Use four practical categories. A control finding concerns how the business prevents or detects errors. A factual finding concerns what actually happened in the transaction. A reporting error concerns the GST return or supporting schedule. A technical uncertainty concerns how the law or published guidance applies to a sufficiently settled fact pattern.
More than one category may apply. For example, a weak tax-code control may have caused incorrect returns and may also reveal a difficult agency question. Record each part separately so the remediation, disclosure and clarification actions are not confused.
The IRAS ACAP page provides the programme context. Follow the applicable review or renewal guidance and keep the technical request within the ACAP team’s agreed responsibilities.
Resolve missing facts first
Gather the contracts, invoices, purchase orders, payment records, delivery evidence, accounting entries and system reports for the affected transactions. Identify the parties, supply flow, consideration, dates and GST treatment in each accounting period.
Interview the commercial and finance owners where the documents do not explain the arrangement. Record what is confirmed, what remains disputed and what assumption would be needed. A technical request should not hide a gap that the taxpayer can reasonably resolve.
If several transaction variants exist, separate them. IRAS needs to know whether the requested answer concerns one standard arrangement or several materially different cases.
Decide whether another route is required
A known reporting error may require a voluntary disclosure or return correction. A proposed transaction requiring certainty may fall within the advance ruling system. A request for remission or refund under specific GST provisions needs the required amount and legal basis.
Do not use technical clarification to seek approval for a weak control, an incomplete record or a preferred commercial result. State why published guidance does not answer the issue and why the clarification route fits.
If the finding concerns more than one taxpayer, identify each person responsible for the GST treatment. Where a customer asks about a supplier’s treatment, IRAS may require the supplier’s written consent, subject to the stated exceptions.
Translate the ACAP finding into one issue
Write a short issue statement that identifies the taxpayer, transaction and exact point of uncertainty. Then describe the business reasons, contractual relationships, fees, mark-ups, movement of goods or services, and the treatment adopted in past and current reporting.
List the affected accounting periods and transaction dates. Quantify the GST involved where possible. If a diagram makes the supply chain or payment flow easier to understand, include one that matches the contracts and invoices.
Do not send a general question such as whether the arrangement is subject to GST. Ask the defined question that the completed fact record creates.
Present the taxpayer’s analysis
The IRAS guidelines ask for the proposed GST treatment, relevant statutory provisions, case law and legal reasons where applicable. Explain how each authority applies to the facts. Identify earlier IRAS correspondence, guidance, compliance initiative or issue-specific mailer that affects the analysis.
Address credible alternative interpretations. If the company seeks to depart from published conditions or use an administrative concession differently, explain the practical difficulty, why it cannot be resolved and how the alternative remains consistent with GST rules.
Where formal legal interpretation is required, Raffles Consulting Services coordinates with Singapore law firms with the relevant tax speciality. The final submission should distinguish legal advice from operational facts and accounting calculations.
Connect remediation without prejudging the answer
Fix the control weakness that is clear regardless of the technical outcome. For example, improve contract review, tax-code approval or evidence retention. Do not wait for IRAS to answer before correcting an unrelated process failure.
At the same time, avoid changing the disputed GST treatment without assessing the reporting consequences. Record interim controls, affected transactions and the decision authority while the request is pending.
If an error is already established, quantify it and follow the appropriate correction or disclosure route. A clarification request should not be treated as an automatic suspension of filing duties.
Use an issue handover table
| ACAP record | Technical request input | Owner |
|---|---|---|
| Finding and risk | Numbered issue | ACAP reviewer |
| Transaction sample | Complete fact pattern | Business and finance owners |
| Returns affected | Periods, dates and amounts | GST reporting owner |
| Authorities reviewed | Taxpayer analysis and alternatives | Tax adviser |
| Control weakness | Remediation outside the request | Process owner |
| Submission record | Documents and correspondence | Authorised sender |
Submit and retain a complete record
IRAS says an authorised Corppass user may submit through myTax Mail for added security, with other online routes available where applicable. Keep the final request, every attachment, authority to act, submission acknowledgement and subsequent correspondence.
If a new issue appears later, submit a separate request rather than adding it informally to the original. Maintain a decision log showing how the answer affected returns, controls, transaction documents and future treatment.
The Singapore tax compliance workflow is the pillar cornerstone. The GST technical clarification workflow covers the general request, while the ACAP renewal review file addresses a separate review use case. The Corporate and International Tax Consulting hub connects related guidance.
A disciplined handover keeps the ACAP finding useful. It fixes what is already known, isolates the unresolved technical point and gives IRAS a complete record on which to respond.