What the consolidated FAQs cover
The 35-page IRAS consolidated FATCA FAQs bring together the general rules, due diligence, registration, return preparation, XML validation, submission and questions for account holders. The amendment record runs through 19 December 2024. Some answers preserve earlier reporting-year arrangements, while later answers describe the replacements. The reporting year, account classification and applicable notice must therefore be identified before selecting a missing-TIN treatment.
FATCA is a US reporting regime intended to identify financial accounts held by specified US persons or certain foreign entities with US controlling persons. Non-compliant foreign financial institutions can face 30% withholding on relevant US-source payments. That is not a general 30% tax on a Singapore customer’s balance or every transfer. Singapore’s Model 1 agreement routes reporting through IRAS for exchange with the US; the Model 2 framework described for comparison instead generally involves direct reporting and supplementary exchange requests.
Institutions and US persons within scope
The financial-institution categories include depository and custodial institutions, investment entities and specified insurance companies. US-person analysis includes citizenship and permanent-resident status, as well as relevant US corporations, estates and trusts; the US tax definitions govern, rather than a Singapore nationality label alone. A trust can depend on the US court and control tests.
Singapore financial institutions generally include institutions resident or organised in Singapore, excluding their overseas branches, and Singapore branches of foreign institutions. Reporting institutions normally register with the IRS for a GIIN. Annex II exempt beneficial owners and deemed-compliant categories require separate analysis: the former may have no reporting obligation, while the latter can have reduced obligations. An entity should not assume that every non-reporting category has identical registration or due-diligence treatment.
Account reviews and changes in circumstances
The historical example concerns an account existing on 31 July 2014 whose mailing address changes to a US address on 15 December 2014. The new indication can make the account reportable for 2015 unless the institution obtains the appropriate evidence under the agreement’s curing procedures. Evidence requirements should be read with the agreement: a general reference to documentary evidence does not dispense with any required self-certification.
A sole-proprietorship account owned by an individual is treated as an individual account; an account owned by a company is not transformed into an individual account because a single person owns the company. An account closed after only fourteen days is not automatically outside FATCA. Institutions must apply the account rules and relevant reporting requirements rather than invent a minimum account lifespan.
Historical TIN relief for 2014–2019
The early reporting arrangements allowed an institution to omit a US TIN for certain existing accounts for 2014–2016 when the number was not in its records. The general requirement changed from 2017. Notice 2017-46 then provided conditional relief for the 2017–2019 reporting years: report dates of birth for relevant individuals and controlling persons, request missing TINs annually and perform the required search of electronically searchable information before reporting the 2017 year.
The nine-letter code AAAAAAAAA belongs to the relevant historical missing-TIN arrangements. It is not a permanent universal replacement for a US TIN. The later codes and notices must be used according to their effective reporting years.
The older codes used from reporting year 2020
The FAQs distinguish preexisting individual accounts and passive-NFFE controlling persons with only a US birthplace indication, for which 222222222 was specified, from preexisting accounts with other US indications and an unremedied change or threshold crossing, for which 444444444 applied. Code 777777777 addressed qualifying dormant accounts. Other relevant historical circumstances could use AAAAAAAAA.
The further categories included 333333333 for new individual accounts or passive-NFFE controlling persons with a US birthplace and the specified unreliable-certification or threshold circumstances; 555555555 covered comparable new-account circumstances involving other US indications. The older description of 666666666 referred to a preexisting passive-NFFE entity account above US$1 million with no self-certification and no identified US indications for controlling persons. The updated code description later in the document changes that wording, so the old threshold must not be carried into the newer table.
Foreign entity TINs and US controlling-person TINs
For reporting categories FATCA101 and FATCA102, a non-US entity’s own organisation TIN and its US owners’ or controlling persons’ TINs have distinct functions. An available foreign entity TIN can be reported using the issuing country, with permitted alphanumeric content. The entity’s foreign number does not replace the US TIN required for a specified US controlling person.
Omitting or leaving the entity TIN field blank can cause a record error. The FAQ prefers a valid foreign entity TIN; where that is unavailable, it describes reporting NA with SG as the issuing country for the relevant non-US entity field. This treatment should not be copied into an individual US person’s TIN field.
Notice 2023-11: relief for reporting years 2022–2024
Conditional relief for relevant preexisting accounts requires reporting the date of birth of individuals and controlling persons whose US TIN is missing, requesting missing TINs annually from calendar year 2023, annually searching electronically searchable data and using an accurate account-specific TIN code. Records demonstrating the required policies and procedures originally had to be retained through the end of 2028.
The annual communication should use the method reasonably most likely to reach the account holder. It must include the State Department’s Joint FATCA FAQs web address, or a copy of those FAQs together with a copy of, or link to, the IRS relief procedures for certain former citizens. The communication is intended to encourage provision of TINs. The 2022 return, due 31 May 2023, could use the older or updated codes as a transitional measure. The 2023 and 2024 returns, due 31 May 2024 and 2025 respectively, use the updated codes. Later relief extends relevant record retention, as explained below.
Updated birthplace codes and their priority
Code 000222111 is specific to a preexisting individual depository account with only a US birthplace indication where the institution also establishes residence in the account jurisdiction for both tax and AML purposes. It takes precedence over other potentially applicable codes. Code 222222222 covers the broader preexisting individual-account and passive-NFFE controlling-person category with only a US birthplace indication, excluding accounts that belong under 000222111; it takes precedence over the remaining codes.
Code 333333333 concerns a new individual account, including the relevant controlling-person circumstances, with a US birthplace indication where the original self-certification becomes unreliable after a change and a new one is missing, or where an account initially below the documentation and reporting threshold subsequently exceeds it without the required self-certification. A code does not itself cure due diligence or create relief for a new account.
Updated other-indicia, passive-entity and dormant codes
Code 444444444 covers preexisting individual and entity accounts with US indications other than birthplace, where a change introduces US indications or invalidates existing certification or documentation without valid replacement. It also addresses a preexisting account below the threshold at the agreement’s determination date that later crosses it without the necessary documents. That reference date is not automatically the account-opening date. Code 555555555 covers the corresponding new-account other-indicia circumstances, including unreliable documentation or subsequent threshold crossing.
Updated code 666666666 is for a preexisting passive-NFFE entity account with one or more controlling persons for whom self-certifications have not been obtained and no US indications have been identified. The updated description does not repeat the older US$1 million condition. Code 777777777 concerns dormant preexisting accounts above the reporting threshold, but another applicable code takes precedence. Code 999999999 is the residual category only where good-faith efforts and due diligence have been completed and none of the other codes applies; it is not an unrestricted substitute for an unknown TIN.
Notice 2024-78: additional requirements for 2025–2027
The December 2024 update extends conditional relief for relevant preexisting accounts through reporting years 2025, 2026 and 2027. Institutions continue the birth-date, annual request, annual electronic search and accurate-code procedures. From calendar year 2025, where electronically searchable account data contains a residence-country foreign TIN or functional equivalent, it must be reported for each specified US person missing a required US TIN.
The city and country of residence for each such person must be reported in AddressFix. AddressFix should generally be used for address reporting where possible; AddressFree can supplement it but does not replace those required structured fields. Policies, procedures and evidence of compliance must be retained through the end of 2031, including applicable records from earlier Notice 2023-11 relief. These conditions concern missing-TIN relief for preexisting accounts, not a general waiver for new accounts or other FATCA obligations.
IRS error notices do not automatically close an account
The IRS can still issue a record-error notification when a required US TIN is missing, even where the institution uses a specified code. The FAQs describe a 120-day correction period after the error notification is received through the IRAS process. An unresolved missing TIN does not, by itself, immediately establish significant non-compliance or require automatic account closure or withholding.
The facts matter: why the TIN is absent, whether the institution has made adequate requests and searches, whether due diligence is complete and whether all relevant relief conditions have been followed. Institutions should preserve their outreach and investigation records and respond through the prescribed correction process. A placeholder code alone is insufficient evidence of compliance.
Checking and submitting FATCA registration information
The FAQ directs reporting Singapore financial institutions to myTax Portal, under More > AEOI > View/Update FI AEOI Profile. The screenshot distinguishes CRS registration from the separate indication that FATCA registration information has been provided. It also shows institution types, first reporting year, effective date, the institution’s GIIN and relevant sponsor or trustee GIIN fields. A CRS entry alone does not establish that FATCA information is complete.
New submissions can use the Apply for CRS Registration service to provide the FATCA information described by IRAS. An institution already registered for CRS provides its FATCA information through the relevant AEOI service. The FAQ gives approximately three weeks for processing, with the outcome sent to the point of contact or individual trustee; the profile can also be checked. There is one point of contact for both regimes, and adding FATCA after CRS can require the letter of authorisation to be provided again.
Umbrella funds, sponsors and trustee-documented trusts
An umbrella fund registers with IRAS at umbrella level and reports its sub-fund accounts under that umbrella. A sub-fund GIIN cannot simply substitute for the umbrella GIIN: obtain the appropriate umbrella GIIN and cancel unnecessary sub-fund registrations after it is issued. A sponsor that is not itself a reporting Singapore financial institution does not provide its own FATCA registration information merely because it sponsors another entity. Sponsored entities supply the sponsor’s GIIN, with the SP.702 suffix where applicable; a sponsored closely held investment vehicle uses the sponsor GIIN for the specified registration and ReportingFI TIN fields.
A trustee-documented trust does not use Apply for CRS Registration for the arrangement described. The trustee first supplies the trust name and other details through View/Edit Trustee-Documented Trusts, then files the return. These routes depend on the entity classification and cannot be replaced by registering every underlying fund or trust in the same way.
Preparing XML, fillable PDF and nil returns
Institutions can prepare their own XML files. The portal does not provide direct manual entry of each account report, but a fillable PDF is available for reporting year 2019 onwards. Each XML or PDF file is limited to 5 MB. The PDF accommodates up to forty account reports; if it exceeds the size limit, it must be recreated. Every save can increase file size even without a change, so the FAQ recommends gathering the data and saving the completed file rather than repeatedly saving it.
Multiple files may be submitted, but all returns are due by 31 May following the reporting year. An institution with no US reportable accounts must still submit a nil return to IRAS. From reporting year 2019, it can select Return with Nil Data without preparing XML. The fact that the IRS does not require every Model 1 nil report does not remove Singapore’s local nil-return obligation. On liquidation or cessation, the institution can submit its final current-year return, including a nil return where appropriate, before the following year and then complete IRAS deregistration.
Validation, vendors and file-format controls
The FAQ refers users to IRS sample XML, schema version 2.0 and its user guide, together with the IRAS supplementary business rules and best-practice documents. Institutions can use software vendors and XML validators, but should assess the provider and involve their internal ICT team. IRS examples are not endorsements of a commercial vendor. An unvalidated file may be rejected and require recreation.
Use the required namespace prefixes rather than assuming an unprefixed default namespace will be accepted. Missing mandatory elements, incorrect special-character handling and restricted character sequences can cause validation failures. XML-sensitive characters require proper handling; the warning is not a claim that correctly escaped text can never contain an ampersand. File names should contain no spaces. Validation of XML syntax alone does not replace the IRAS business-rule checks.
Corrected, amended and voided account records
FATCA2 is the corrected-data type for an IRS-requested correction identified by the relevant record-error notification. FATCA4 is amended data where the institution identifies the change itself, or for the specified IRAS accepted-with-errors situation. FATCA3 voids a previously submitted record; a replacement can then be sent as new FATCA1 data where required. These are different operations and should not be selected interchangeably.
Use the appropriate DocTypeIndic and link CorrMessageRefID and CorrDocRefID to the original message and document identifiers. A corrected or amended record includes all required content, including unchanged fields, rather than just the changed item. A void record repeats the original values as required. Every file must meet schema requirements, and only one data type may be included in an XML file; do not mix corrected and amended data. The FAQ links IRS examples to illustrate each operation.
Who can file through myTax Portal
The institution first provides its IRAS registration information and then arranges the appropriate Corppass authorisation for its contact, staff or third-party filer. All returns, including nil returns, are submitted through myTax Portal rather than on paper. The FAQ describes selecting the financial institution reference, including UEN, ASGD or ITR references where applicable, and uploading files within the 5 MB limit.
A non-Singapore sponsor cannot use the Singapore portal to file on behalf of an institution merely by being its sponsor; it may prepare the data for the Singapore institution to submit. A sponsor located or resident in Singapore with the relevant SP.702 GIIN can use the described route and obtain client Corppass authorisation. For the IRS sponsor registration illustrated, select sponsoring entity, country Singapore and the specified None of the Above classification, complete registration and wait for the GIIN to be published.
What individuals should expect from self-certification
A Singapore citizen, permanent resident or business is generally not reportable merely because it has a Singapore account, but Singapore status is not a blanket exemption from US tax status. A dual US citizen or relevant US resident may still fall within FATCA. Institutions request self-certification to establish the actual status, including for customers who consider themselves non-US. Customers should return the information to the institution that issued the form; IRAS does not complete that institution’s form for them.
Failure to supply information can cause reporting, refusal to open an account or closure under the institution’s policy. The FAQ distinguishes such policies from the specific historical alternative procedures for certain new individual accounts opened between 1 July 2014 and 16 March 2015, where failure to obtain the required certification could trigger mandatory closure. It does not say every missing TIN now requires closure. A person who has been issued a US TIN should provide it.
Entity certifications, active NFFEs and the update record
An entity may be reportable because it is itself a specified US person, or because it is a passive non-financial foreign entity with specified US controlling persons. Institutions can therefore request both entity tax-residence and active/passive classification information, and controlling-person certifications. For the ordinary income-and-assets active-NFFE test, both passive income and assets producing or held to produce passive income must be below 50% for the relevant preceding calendar year. A typical operating food-and-beverage business illustrates the principle but is not automatically exempt without the facts.
Other active-NFFE categories exist under the guide’s section 6.3; the ordinary two-part test is not an additional condition imposed on every alternative category. The document’s appendix records the evolution from the 2015 account-holder questions, through registration and filing updates, the 2021 consolidation, the 2022 foreign-entity TIN answer and the 2023–2024 missing-TIN notices. Read that chronology with the substantive answers, and retain the original PDF and linked notices as references for the applicable year.
Official source
This article independently explains the substantive contents of the official PDF, including the relevant conditions, procedures and annexes. The linked document remains the authoritative source for its original wording, and later changes should be checked separately.
Read the official PDF ↗