Raffles Consulting Services
GST technical request evidence retention should preserve the facts, contracts, analysis, authority and submission history for each numbered issue.
GST technical request evidence retention should begin before a request is sent to IRAS. Keep the facts, contracts, numbered issues, taxpayer analysis, alternative views, authority, submission copy and later correspondence in one controlled file. That record helps the taxpayer explain what IRAS was asked and whether the eventual answer applies to the transaction reported.
The file is not a source dump. Each item should be linked to a fact or issue, dated and assigned to an owner. Sensitive commercial documents should be shared through the official secure channel and retained according to the taxpayer’s legal and records policy.
Set up one file for one request
The current IRAS GST technical clarification guidance applies from 1 September 2026. It asks requesters to list and number each issue and says additional issues not covered in the original request should be submitted separately.
Give the file a request reference, taxpayer name, tax reference number, affected accounting periods and submission date. Record the tax agent and authorised taxpayer contact. Do not merge several taxpayers into one authority letter or assume one party can instruct for all parties.
If a customer asks about the GST treatment of a supplier’s supply, keep the supplier’s written consent where IRAS requires it. Reverse charge cases follow a different responsibility because the recipient determines its own GST treatment.
Preserve the authority to act
Keep a signed letter of authority for each taxpayer represented. The file should show the authorised agent, scope, date and taxpayer signatory. Check that the authority covers the request and the secure submission channel used.
Do not copy an old authority letter from another engagement without review. A corporate reorganisation, change of tax agent or new taxpayer can make the document inaccurate even if the transaction looks similar.
Restrict access to tax reference numbers, contracts and personal information. Use named folders or case permissions rather than an open team drive. Record material downloads or transfers where the organisation’s policy requires it.
Freeze the factual record at submission
IRAS asks for a comprehensive description of the arrangement and business reasons, including parties, roles, GST profiles, fees, mark-ups, affected periods and transaction dates. Save the final fact statement as submitted.
Add a source beside every material fact. A party and role can point to the agreement. A fee can point to an invoice or pricing schedule. A transaction date can point to delivery, acceptance or payment evidence. If a diagram is used, label the contracts, goods, services and cash flows it represents.
State assumptions clearly and explain why they were necessary. If a fact changes after submission, do not overwrite the original statement. Create a dated change note and consider whether IRAS must be informed.
Index the supporting documents
IRAS asks for agreements, service contracts and other relevant documents with the relevant clauses or passages identified and highlighted. It may also require documents specified in an applicable e-Tax Guide.
Prepare an index showing document name, date, parties, version, issue supported and relevant clause. Keep the signed agreement as well as any schedule or amendment that changes the GST analysis. A draft without the final amendment can produce a false fact pattern.
If a document cannot be provided, record the reason and the substitute evidence offered. IRAS says it may be unable to give a clarification where information is incomplete. The omission should be visible to the taxpayer and adviser before submission.
Retain the technical analysis
For each numbered issue, keep the proposed GST treatment, relevant provisions of the Goods and Services Tax Act 1993, subsidiary legislation, e-Tax Guides and relevant case law. Explain how the authority applies to the facts.
Record possible arguments for a different interpretation. This is not unnecessary pessimism. It helps the taxpayer understand why the issue is uncertain and prevents the file from presenting one conclusion without addressing a material alternative.
Where the request asks to depart from published conditions or guidance, preserve the reason compliance is not possible, why the problem cannot be resolved and how the proposed treatment remains within GST rules. Keep the commercial evidence supporting those statements.
Keep the submission and correspondence trail
Use myTax Mail where the agent has the relevant CorpPass authority, as IRAS recommends it for added security. Otherwise use the official online form identified by IRAS. Save the final submitted package, acknowledgement and reference number.
Log every IRAS request for information, the deadline, person responsible, documents supplied and date sent. Keep the full response rather than only an email saying that the matter was answered.
If the taxpayer changes its reported GST treatment while the request is open, record the affected return, adjustment and advice. A pending clarification does not automatically suspend filing or payment obligations.
Use an evidence retention matrix
| Record | Index field | Control |
|---|---|---|
| Authority | Taxpayer, agent, scope and date | Separate authority for each taxpayer |
| Facts | Statement, source and affected period | Freeze the submitted version |
| Contracts | Version, clause and issue | Retain signed amendments |
| Analysis | Issue, position and alternative view | Link authority to the facts |
| Submission | Channel, date and reference | Keep exact package and acknowledgement |
| Correspondence | Request, response and owner | Track every deadline |
Connect voluntary compliance work carefully
IRAS says the clarification guidance also applies to requests submitted under voluntary compliance initiatives. Its Assisted Self-help Kit page directs tax agents with technical questions to provide the information specified on the clarification page.
Keep the ASK or other compliance review file connected but distinct. A technical question, error disclosure and advance ruling serve different purposes. The records should show which route was used and why.
If the review discovers an error, obtain advice on correction and voluntary disclosure without assuming that a technical request will resolve penalty or filing obligations. Record the action taken and its date.
Close the file against the reported transaction
When IRAS replies, map the answer to each numbered issue and the facts stated. Identify conditions, limitations and any question IRAS did not answer. Have the taxpayer confirm whether the transaction remains factually the same.
Update the tax position paper, return instructions, accounting treatment and future transaction checklist. Preserve the original request and answer together. Do not replace the submitted analysis with the final answer and lose the history.
The Singapore tax compliance workflow is the pillar cornerstone. The GST clarification workflow explains the submission requirements, while the additional issues guide covers separate follow-up requests. The Corporate and International Tax Consulting hub connects the library.
A well-kept evidence file lets a later reviewer see the exact question, facts and answer. That matters when staff change, an audit begins or the same commercial arrangement is repeated years later.