Form 8966 Reporting: FATCA Filers, IDES and the 31 March Deadline

Form 8966 reporting is the annual FATCA return that institutions dealing directly with the Internal Revenue Service file on their U.S. accounts, on the U.S. owners of passive foreign entities and on pools of recalcitrant account holders. The current IRS edition is the 2025 Form 8966, FATCA Report, with its 2025 instructions, and the form is due by 31 March of the year after the calendar year it covers.

Who files turns on the chapter 4 status an entity holds. A Reporting Model 1 FFI reports to its own tax authority and does not file Form 8966 with the IRS. The direct filers include participating FFIs (a group that, for filing purposes, includes Reporting Model 2 FFIs), direct reporting NFFEs and their sponsors, and withholding agents that pay passive NFFEs or owner-documented FFIs. Any filer that is a financial institution has to file electronically, as FATCA XML sent through the International Data Exchange Service (IDES).

The IRS states the stakes in its own notification text. When a filed record fails validation, the valid file notification warns that failure to correct errors by the date required may result in a determination that the institution has defaulted under its FFI agreement or is in significant non-compliance with the terms of the IGA. A filer that is required to file electronically and does not, with no approved waiver on record, faces possible penalties under sections 6721 to 6724.

Related reading: FATCA Reporting in Luxembourg: Practical Guide for Financial Institutions

The fixed calendar, as the instructions, the regulations and the IRS notification guides set it:

Legal basis of Form 8966: section 1471(c), Regulations section 1.1471-4(d) and the FFI agreement

Chapter 4 of the Internal Revenue Code, sections 1471 to 1474 and the Treasury Regulations under them, is the regime commonly called FATCA. Its enforcement mechanism is a 30% withholding tax. A withholding agent generally has to withhold 30% of a withholdable payment made to an FFI unless the FFI has an FFI agreement with the IRS and is treated as a participating FFI (PFFI), and 30% of a withholdable payment to a passive NFFE unless that entity certifies it has no substantial U.S. owners or identifies them. Form 8966 is the information return that sits on the other side of those agreements and certifications.

The statutory hook is section 1471. Subsection (b)(1)(C) makes annual reporting a term of the FFI agreement, and subsection (c)(1) lists what has to be reported for each United States account the institution maintains: the name, address and TIN of each account holder that is a specified United States person, or of each substantial United States owner where the holder is a U.S.-owned foreign entity; the account number; the account balance or value; and, except as the Secretary provides otherwise, gross receipts and gross withdrawals or payments.

Treasury Regulations section 1.1471-4(d) converts that into filing mechanics for participating FFIs. Paragraph (d)(3)(vi), headed “Time and manner of filing”, provides that Form 8966 is to be filed electronically with the IRS on or before 31 March of the year following the calendar year. Paragraph (d)(3)(vii), “Extensions in filing”, grants the automatic 90-day extension on Form 8809-I and allows a further 90 days under hardship conditions. Other filer types draw their duty from neighbouring provisions that the instructions cite: Regulations section 1.1472-1(c)(3) for direct reporting NFFEs, sections 1.1471-4(d)(2)(ii)(C) and 1.1472-1(c)(5) for sponsoring entities, and section 1.1471-5(f)(1)(i) or the applicable Model 2 IGA for registered deemed-compliant FFIs (RDCFFIs).

The FFI agreement itself is published as a revenue procedure. Rev. Proc. 2017-16 sets out the agreement for FFIs with an agreement effective on or after 1 January 2017, and section 6 of that agreement requires a participating FFI to report its U.S. accounts and its recalcitrant account pools on Form 8966 “on magnetic media”, which the agreement glosses as the FATCA Report XML, by 31 March. The agreement’s stated term ran to 31 December 2018, and the IRS FATCA compliance legal FAQs, in an answer updated 17 January 2024, treat a participating FFI’s continued registration as its agreement to these terms until the earlier of 31 December 2024 or a revenue procedure superseding Rev. Proc. 2017-16, without giving a later date. A Reporting Model 2 FFI follows the same agreement as modified by its Model 2 IGA. Consistent with that, the instructions tell Model 2 filers to complete Form 8966 in line with the PFFI instructions unless a specific line says otherwise.

The form and its instructions are IRS products: Form 8966 carries OMB No. 1545-2246 and Cat. No. 55748F, and the IRS estimates the average time to complete one form at 25 minutes. That estimate is per form, and the per-owner and per-pool filing rule described below is what multiplies it.

Who must report on Form 8966: eleven filer categories and the Model 1 exit

The instructions list the filers by chapter 4 status, and Part I line 1b records that status as a two-digit code. The FATCA XML schema carries the same eleven categories in its FilerCategory element, coded FATCA601 to FATCA611 in the same order.

Three roles change what a filer reports. Account reporters (PFFIs, Reporting Model 2 FFIs, RDCFFIs reporting as a condition of their status, trustees of trustee-documented trusts, and sponsors of sponsored FFIs) report the following accounts they maintain at any time during the year: U.S. accounts held by specified U.S. persons, accounts of passive NFFEs with substantial U.S. owners (controlling persons that are specified U.S. persons, for a Model 2 filer) and accounts of owner-documented FFIs (ODFFIs). The pooled reports cover the accounts treated as held by recalcitrant account holders at the end of the year or, for a Model 2 filer, its non-consenting U.S. accounts. Payment reporters are withholding agents outside the FFI categories, and they report the substantial U.S. owners of passive NFFEs, and the specified U.S. persons holding interests in ODFFIs, to which they make withholdable payments. Owner reporters are direct reporting NFFEs, which report their own substantial U.S. owners, or that they have none.

Branch treatment follows the same logic. A U.S. branch of an FFI that is not treated as a U.S. person reports like a PFFI under code 01; a U.S. branch that is treated as a U.S. person files in the same manner as a withholding agent under code 10. The instructions treat all units and offices of a PFFI in one country, including disregarded entities there, as a single branch, and the FFI receives a separate GIIN for each jurisdiction where it keeps a branch that is not a limited branch. When an FFI reports accounts it maintains, line 4 takes the GIIN of the branch that maintains the account. The instructions contain no group-level consolidated filing; reporting runs entity by entity and, inside an FFI, branch GIIN by branch GIIN.

Third-country treatment depends on IGA coverage. An FFI in a jurisdiction not treated as having an IGA in effect has to register for participating FFI or registered deemed-compliant status to avoid chapter 4 withholding, unless it qualifies as a certified deemed-compliant FFI or an exempt beneficial owner; as a PFFI it then files under code 01. Treasury’s IGA table lists Model 2 arrangements for jurisdictions including Japan, Hong Kong, Austria, Bermuda and Switzerland, whose FFIs report to the IRS as Reporting Model 2 FFIs.

The instructions provide no size threshold for filers. The exceptions work at account level or through someone else filing: depository accounts held solely by individuals are excepted where the aggregate balance or value of all depository accounts held by each such individual does not exceed $50,000 at the end of the calendar year or on closure (Regulations section 1.1471-5(a)(4), which the instructions cite), unless the FFI elects to forgo the exception, certain retirement and other accounts are excluded, and sponsored FFIs and sponsored direct reporting NFFEs do not file if their sponsoring entity reports for them.

The Model 1 exit is narrower than it sounds. “Reporting Model 1 FFIs do not file Form 8966 directly to the IRS” describes the Model 1 FFI’s own account reporting, and other entities in a Model 1 group can still be in scope. Code 10 expressly covers a U.S. branch of a Reporting Model 1 FFI that is treated as a U.S. person and a U.S. branch of a Reporting Model 1 FFI that is not treated as a U.S. person, so the U.S. branch of a Model 1 bank can still be a Form 8966 filer in its withholding agent capacity.

What the report contains: Parts I to V, one form per owner and per pool

Form 8966 has five parts, and a filer completes only those that apply. The unit of reporting is narrow: a separate form is filed for each reportable account, for each substantial U.S. owner of a passive NFFE, for each specified U.S. person with an interest in an ODFFI, and for each pooled reporting type. The instructions’ completion chart sets the parts by filer and record type.

Parts I to III: who is filing, about whom

Part I identifies the filer. Every filer completes lines 1a to 3c (name, category code and mailing address). Line 4 takes the GIIN; line 5 takes a U.S. TIN only where no GIIN was entered on line 4, with one exception: a qualified intermediary, withholding foreign partnership or withholding foreign trust enters both its GIIN and the EIN issued for that capacity. A foreign TIN never goes on line 5, and a filer without a U.S. TIN leaves it blank. Lines 6 to 10 are used only by sponsoring entities, by trustees of trustee-documented trusts, and by filers making payments to a territory financial institution not treated as a U.S. person that acts as an intermediary or flow-through entity, or to a certified deemed-compliant FFI acting as an intermediary that supplies information on a passive NFFE’s substantial U.S. owner.

Part II identifies the account holder or payee, with the residence address and, for a U.S. address, the 9-digit ZIP+4 code only. Line 5 classifies an entity holder as an ODFFI with specified U.S. owners, a passive NFFE with substantial U.S. owners, a nonparticipating FFI or a specified U.S. person. A jointly held account produces one Form 8966 for each holder who is a specified U.S. person. Part III carries the U.S. owner’s name, residence address and SSN, ITIN or EIN, again one form per owner. Direct reporting NFFEs skip Part II entirely and identify themselves in Part I.

Part IV: the financial data

Line 1 is the account number the PFFI uses for its own purposes, an ISIN or similar code for a debt or equity interest held outside a custody account, or “NANUM” where no numbering system exists. Line 2 is a three-character ISO 4217 currency code, or “USD”. Line 3a is the average calendar year balance if that figure is reported to the account holder, and otherwise the balance or value at the end of the calendar year. Each holder of a joint account is attributed the entire balance.

Lines 4a to 4d split the year’s payments into interest, dividends, gross proceeds or redemptions, and other income. Two account types break that pattern: for certain debt or equity interests (other than partnership interests) and certain cash value insurance and annuity contracts, everything paid or credited, including redemptions, goes on line 4d with nothing on lines 4a to 4c. For a partner’s interest in a partnership, line 4d carries the distributive share of income or loss, whether or not distributed, plus guaranteed payments for the use of capital. A closed account reports the amount withdrawn or transferred on closure on line 3a with the box on line 3b checked; a rollover into another account at the same FFI is reported once and is not treated as a closure.

Part V: pooled reporting

Part V reports recalcitrant account holders (or, for a Model 2 FFI, non-consenting U.S. accounts) in aggregate: the pooled type on line 1, the number of accounts on line 2, the aggregate year-end balance on line 4 and the currency on line 5. Line 3 stays empty. Each pooled type needs its own form, and the XML equivalents run from FATCA201 (recalcitrant with U.S. indicia) to FATCA206 (recalcitrant passive NFFEs).

The “nonparticipating FFI” options are the non-example on this form. They still appear in Part II line 5 and in Part V line 1, yet the instructions’ reminders tell PFFIs, including Reporting Model 2 FFIs, not to check the nonparticipating FFI box in either place and not to complete Part V line 3, because they are not required to report accounts held by nonparticipating FFIs. The FFI agreement in Rev. Proc. 2017-16 confined the specific reporting of payments to nonparticipating FFIs to calendar years 2015 and 2016.

Units, currency and rounding

The amount and character of payments may follow the principles the filer already uses to report resident account holders to its domestic tax authority; U.S. federal tax principles are optional, and changing method needs IRS consent unless the change is to U.S. federal tax principles. Balances and payments may be reported in U.S. dollars or in the currency of denomination, and an account denominated in several currencies may be reported in one of them, with the currency code identified. Rounding to whole currency units is optional, but a filer that rounds one amount has to round them all, and the IDES technical FAQs say the same rounding guidelines apply to the XML. The XML monetary type allows up to two decimal places and requires a currCode attribute; Publication 5124 shows fifty thousand dollars as 50000.00 or 50000 with “USD”.

Form 8966 reporting deadlines: 31 March, Form 8809-I and the Model 2 carve-out

Form 8966 reporting runs on one annual clock. The calendar year now running is reported by 31 March of the following year, and the instructions move the due date to the next business day when 31 March falls on a weekend or a U.S. legal holiday. A Reporting Model 2 FFI files on the same dates as a PFFI unless its Model 2 IGA specifies a different reporting date.

The reference point inside the year depends on the field. The XML ReportingPeriod element identifies the reporting year in YYYY-MM-DD format, Publication 5124’s example uses 31 December of the year, and future years are barred. Account balances are year-end values unless the filer reports an average balance to the holder, pooled balances are year-end aggregates, and payment fields cover the whole calendar year or the period up to closure.

The automatic 90-day extension is requested on Form 8809-I, and the instructions place the request as soon as the need is known and no later than the due date. Each branch requesting an automatic or additional extension files its own Form 8809-I. Under hardship conditions the IRS may grant a further 90 days, requested on a second Form 8809-I before the end of the initial extended due date, with a statement of reasons. The current Form 8809-I is the November 2015 revision.

The carve-out is specific: no extension is permitted for Forms 8966 filed by a Reporting Model 2 FFI to report non-consenting U.S. accounts. The applicable Model 2 IGA sets those due dates. A Model 2 institution that extends its main filing still has to meet the IGA date for the non-consenting pool.

Two more dates attach to the filing cycle. A request to waive electronic filing goes on Form 8508-I at least 45 days before the due date. After filing, the correction windows differ by error type: the file-level notifications NMR, NDM and NTP set the organisation’s Form 8966 due date as the action date, while record-level errors carry the 120-day window shown in the calendar above.

On the first applicable reference date, the 2025 instructions are silent: they describe the current annual cycle and do not say when Form 8966 reporting began. The next reference period is always the calendar year in progress.

Submission of Form 8966: FATCA XML v2.0.1, the IDES data packet and the paper route

The instructions require an entity that is a financial institution to file Form 8966 electronically, however few forms it files, and strongly encourage every other filer to do the same. Electronic filers populate the FATCA XML following Publication 5124, the FATCA XML Schema v2.0 User Guide (Rev. 04-2017), and transmit through IDES following Publication 5190, the IDES User Guide, and Publication 5188, the metadata schema guide.

Schema version

The IRS schema page states that FATCA XML v2.0 replaced v1.1 in January 2017 and that v1.1 is not supported. The package posted there is labelled FATCA XML v2.0.1, updated 6 October 2025. The main schema file in that package declares version 2.0.1 and keeps the urn:oecd:ties:fatca:v2 namespace. Publication 5124 has not been reissued for v2.0.1 and remains the v2.0 guide; the schema page does not describe what changed between v2.0 and v2.0.1.

Building and sending the data packet

Publication 5188 summarises the transmission sequence:

1. Obtain a digital certificate from an IRS-approved certificate authority, in DER or PEM format; wildcard certificates are rejected.
2. Enroll in IDES with a registered GIIN in the 19-character format XXXXXX.XXXXX.XX.XXX, or with a FATCA Identification Number (FIN) for a filer not required to obtain a GIIN.
3. Prepare the FATCA XML, validate it against the schema and digitally sign it.
4. Compress the signed file, encrypt it with an AES-256 key, and encrypt that key with the IRS public key.
5. Create the sender metadata file, which is never encrypted.
6. Upload the data packet through the IDES Gateway in a web browser or by SFTP.

The packet is a .zip archive holding three files (the payload, the encrypted key and the metadata XML), or four in a Model 1 Option 2 jurisdiction, where a key file encrypted for the host country tax authority is added, and it is named with a UTC timestamp and the sender’s GIIN in the pattern UTC_FATCAEntitySenderId.zip. Publication 5190 states that file names are case sensitive and that any variation in name or format fails the transmission. Before transmission, verify the current IDES file-size limits and packaging requirements against the IRS IDES Technical FAQs and Publication 5190. The applicable limit should be tested against the relevant file size measure rather than inferred from differently worded guidance. There is no method to merge files split across transmissions, and the FAQs say none is needed.

XML identifiers and test codes

MessageRefId must be unique across every file the sender ever submits, and the IRS strongly recommends a GUID. DocRefId must be unique across all reports for all time. Publication 5124 recommends one DocTypeIndic per message, with new, corrected, void and amended records sent in separate files. The test codes FATCA11 to FATCA14 belong only in the IDES test environment during an IRS testing window; a production file carrying them draws an NTP notification and is not accepted as a FATCA report.

Account maintenance that sits outside the file

IDES access has its own failure points. Publication 5190 describes a multi-factor authentication code at Gateway login, locks an account after three unsuccessful login attempts, and expires a password that is not changed within 90 days. Before each annual filing cycle, confirm that IDES credentials remain valid, that the authorised user can complete multi-factor authentication and that the digital certificate remains usable. An IRS notification stays available for download for 7 days for FFIs, and a download, once started, has to finish within 24 hours.

The paper route

Paper is available only to a filer with an IRS waiver of the electronic filing requirement or one not otherwise required to file electronically. Paper forms go with Form 8966-C, Cover Sheet for Form 8966 Paper Submissions, to Internal Revenue Service, FATCA, Stop 6052 AUSC, 3651 South IH 35, Austin, Texas 78741. Each paper form carries a unique three-digit numeric identifier, which an amended, corrected or voided form has to repeat and which can be reused on a new original form in a later year.

Validation of Form 8966 files: IDES alerts, ICMM notifications and the 120-day clock

A Form 8966 file passes three gates, and each gate answers with a different kind of message. IDES checks the packet and sends alerts. The IRS International Compliance Management Model (ICMM) system then downloads the file and runs file-level checks. Records that survive those are evaluated individually, and the result comes back as a valid file notification listing any record-level errors.

Gate one: IDES alerts

A clean upload shows RC001 (file uploaded), RC021 (available for download by the receiver) and RC024 (downloaded by the IRS) as its last status. Packet failures carry their own codes, for example RC018 when the packet name lacks the underscore separator and RC020 when the digital certificate is expired, revoked or invalid. RC007 means the packet passed IDES validation but expired before the IRS downloaded it, and Publication 5190’s alert table refers that case to the IDES help desk.

Gate two: ICMM file-level notifications

Publication 5189 (Rev. 8-2020) lists the file-level notifications, among them NDC (failed decryption), NKS (incorrect AES key size), NSC (failed signature check), NTD (failed threat detection), NSV (failed schema validation), NMR (invalid MessageRefId), NDM (duplicate MessageRefId), NTP (test data sent to production) and NCF (certificate failure). A file rejected at this stage never reaches record processing. It is replaced by a new transmission, and Publication 5189 asks filers not to correct, amend or void any of its records until a valid file notification arrives.

Character handling causes avoidable rejections. Publication 5188 requires the ampersand and the less-than sign in text content to be replaced with entity references; left raw, they make the XML not well-formed. Certain character combinations, including a double dash, slash-asterisk and ampersand-hash, are rejected outright as failed threat detection. The checks apply to text content, so free-text name and address fields need screening before the file is signed and encrypted.

Gate three: record-level errors

The valid file notification (NVF) reports four-digit record-level codes. 8001, 8007 and 8013 flag field-level errors in pooled, account and nil reports. 8008 marks a duplicate account report, which the IRS disregards.

8010, 8011 and 8012 mean a corrected, void or amended account report did not match an original. 8019 marks a file that contained neither an account nor a pooled report and was not flagged as nil. 8020 and 8021 mark duplicate or badly formatted DocRefIds, and those records were not processed at all. Since the v2.5 notification schema (August 2020), the RecordLevelErrorCd element is a five-character string where it used to be an enumerated four-digit list, which matters to any parser written against the older schema.

Correct, amend or void

Publication 5124 gives each update type a narrow job. FATCA2 (corrected) answers a record-level error notification. FATCA4 (amended) updates an accepted record when the filer finds the problem itself and has received no record-level notification. FATCA3 (void) withdraws a record that should not have been filed, with every field matching the original. The guide is explicit that a record should not be amended in response to a record-level error notification.

Publication 5124 section 7.2.4 lists fields that cannot be corrected or amended: a missing or incorrect account holder or substantial U.S. owner TIN, an incorrect name, and an incorrect name and address. An error in one of them requires the original record to be voided and a new FATCA1 record filed. The IRS notification FAQs add that where the filer has confirmed that an account holder is not required to have a U.S. TIN in the agreed format, no re-filing is needed to clear the TIN format error itself, although any other errors in the notice still have to be corrected. Publication 5189 applies the same void-and-replace rule to an error in the reporting FI’s GIIN.

Paper corrections follow the medium of the original. A form first filed electronically is corrected electronically, a paper original is corrected on paper, and the instructions warn that a correction filed in the wrong medium will not be processed. On paper, a corrected report answers an IRS notification and needs no voided copy, while an amended report goes with a copy of the original marked “Voided report”.

Caveats and interactions: chapter 61 elections, Form 1042-S, Model 1 Option 2 and sponsored filers

The chapter 61 election removes less than its name suggests. A PFFI, including a Reporting Model 2 FFI, or an RDCFFI may elect to satisfy its chapter 4 reporting for accounts of specified U.S. persons on Form 1099 under Regulations section 1.1471-4(d)(5). That election does not reach accounts of passive NFFEs with substantial U.S. owners or of ODFFIs: the electing institution still files Form 8966 for those. The same carve-back applies to a U.S. payor PFFI or RDCFFI (other than a U.S. branch) that reports an account holder’s payments on Form 1099 under Regulations section 1.1471-4(d)(2)(iii)(A).

Tax withheld under chapter 4 is reported on Form 1042 and Form 1042-S, which a withholding agent may have to file alongside Form 8966, and a U.S. payor reporting payments to U.S. non-exempt recipients on Form 1099 does not repeat those payments on Form 8966.

Model 1 jurisdictions add two routing traps. In a Model 1 Option 2 jurisdiction, the IDES technical FAQs say every file an FI uploads is routed to the host country tax authority. A direct reporting NFFE resident in a Model 1 jurisdiction, which reports to the IRS itself, can find its IDES enrollment rejected as coming from a Model 1 jurisdiction; the FAQs describe obtaining a second GIIN registered with “Other” as the jurisdiction, using it only to enroll in IDES, and entering the GIIN for the actual residence jurisdiction as the ReportingFI TIN in the XML. Institutions on the Model 1 side report to their own tax authority as the applicable IGA and local rules require; our FATCA reporting guide for Luxembourg covers one such route.

Several adjacent regimes share the same customer data without sharing the return. A group that reports Form 8966 for a Model 2 or non-IGA entity and runs OECD reporting elsewhere, as described in our CRS reporting guide for Luxembourg and our CARF crypto tax reporting guide, still needs the FATCA-specific fields that Form 8966 carries, such as the filer category code, the U.S. TIN of each owner and the pooled reporting type.

Sponsorship moves the filing obligation with it. A sponsoring entity files on behalf of its sponsored FFIs under the PFFI requirements and on behalf of sponsored direct reporting NFFEs under the direct reporting NFFE requirements, identifies itself in Part I and names the sponsored entity on lines 6 to 10. Line 9 takes the sponsored entity’s GIIN, except for a sponsored closely held investment vehicle, where it stays blank, and the instructions bar entering the sponsor’s own GIIN there.

Mergers are the other interaction with a timing edge. A successor PFFI that acquires another PFFI’s accounts in a merger or bulk acquisition may assume the predecessor’s Form 8966 reporting for the calendar year of the transaction if the regulatory conditions are met. The instructions contain no proportionality regime or transitional relief beyond the account-level exceptions, the chapter 61 election, the electronic filing waiver and the IGA-specific dates.

Changes to Form 8966: the 2025 edition, schema v2.0.1, IDES updates and Switzerland’s move to Model 1

The form itself has been stable. The 2025 instructions carry no “What’s New” section, and the IRS About Form 8966 page lists “None at this time” under recent developments. The form and instructions are issued as calendar-year editions, the current pair labelled 2025, and the About page links to all prior revisions.

The technical layer has moved more. The IRS updated the FATCA XML v2.0.1 package on 6 October 2025 while leaving Publication 5124 at its April 2017 revision. The schema page lists the supporting files as ISOFATCATypes v1.1 and OECDTypes v4.1, while the files inside the package are named isofatcatypes_v1.2 and oecdtypes_v4.2, so validation tooling has to reference the files as packaged. The CRS side has its own schema cycle, as our note on the BZSt CRS schema v3.0 switch describes; FATCA XML stays on its v2 namespace.

IDES itself went through a system upgrade scheduled for 14 to 20 June 2024; the IRS technical FAQs said users should not see substantive changes, registration information should transfer automatically and the Gateway URL would stay the same. The current edition of Publication 5190 revises the April 2025 edition and adds Foreign Filers as authorized IDES users, with existing FATCA processes applying wherever the guide does not refer to Foreign Filers. The IDES testing schedule page publishes each open test window with its enrollment cut-off and states that test files must conform to FATCA XML schema version 2.0, with files on any version other than 2.0 (or 2.0.1) generating error notifications.

Switzerland and the United States signed a new Model 1 FATCA agreement on 27 June 2024. The Swiss Federal Administration states that implementation is under way and that the earliest planned entry into force is 1 January 2029. Until the new agreement becomes applicable, Swiss financial institutions must continue to assess their obligations under the existing Model 2 arrangements. The new agreement provides for automatic and reciprocal exchange of information between the competent authorities, with transitional provisions intended to maintain continuity. The first reporting period under the new arrangements remains subject to the implementation timetable.

Frequently Asked Questions

We are a sponsoring entity that also registered as a PFFI. Which GIIN goes on line 4?

It turns on the capacity in which each form is filed. On a form filed on behalf of a sponsored FFI or sponsored direct reporting NFFE, line 4 takes the sponsoring entity GIIN, and the instructions tell a sponsoring entity to enter that GIIN and not a separate GIIN it received when registering as a PFFI or RDCFFI. A trustee filing for a trustee-documented trust likewise uses the GIIN issued for its trustee role. A form on which the entity reports its own accounts as a PFFI follows the general line 4 rule: the GIIN assigned to the filer, using the GIIN of the branch that maintains the account where applicable.

An account holder has no U.S. TIN. Can the field stay empty?

On the paper form, line 4 of Part II is left blank when the holder has no TIN. The XML is stricter: the IRS notification FAQs say the account holder TIN element has to be included and cannot consist of blank characters, and omitting the TIN element or inserting blank spaces draws a “TIN Not Populated” error. Missing or invalid U.S. TINs require assessment under the applicable IRS reporting and correction rules. The appropriate treatment depends on the record status, error notification and reporting circumstances. Filers should follow Publication 5124 and the relevant IRS FATCA compliance guidance rather than assuming every TIN issue requires the same correction procedure.

A payment line came out negative after a reversal. Will the record fail?

The IDES technical FAQs record that since April 2016 the IRS treats zero or negative amounts as valid payment amounts and balances. If a Payment element carries a zero or negative PaymentAmnt, the Type element has to be completed too; omitting the Payment element altogether is also accepted.

A direct reporting NFFE had no substantial U.S. owners this year. Does it still file?

Yes. A direct reporting NFFE, or a sponsoring entity reporting for one, checks the “no accounts to report” box and completes Part I only. The IDES technical FAQs say that, generally, only these filers are required to submit a nil report; for every other filer a nil report is optional.

IDES confirmed the upload but no ICMM notification arrived. What does that mean?

Check the IDES dashboard sequence first. A file the IRS has collected ends on RC024; an RC007 means the file expired before the IRS downloaded it, and Publication 5190 refers that case to the IDES help desk. Notifications themselves sit in the IDES inbox for 7 days for FFIs, so an unwatched inbox can lose one.

Can we test a file before the March filing?

Only during an IRS open testing window, using the test codes FATCA11 to FATCA14 and no production data or personal information. The IDES testing schedule page carries the window dates and enrollment cut-off once the IRS sets them, and outside a window there is no test environment to send to.

Related Articles

• FATCA Reporting in Luxembourg: Practical Guide for Financial Institutions: the Model 1 route, where Luxembourg reporting financial institutions report U.S. accounts locally instead of filing Form 8966.
• BZSt CRS Reporting: The Schema v3.0 Switch and Saint-Martin Refile: the CRS XML schema v3.0 switch for German financial institutions.
• CARF Reporting in Luxembourg: DAC8 Crypto Filing by 30 June: which crypto-asset service providers file, what the report contains and the 30 June deadline.
• Form PF Reporting: Thresholds, Deadlines and the July 2027 Form Switch: another U.S. register explainer, covering the SEC and CFTC private fund return.

Key Takeaways

• Assign one line 1b code to every filing entity and branch before the file is built; the FATCA601 to FATCA611 value follows from it.
• File a separate Form 8809-I for each branch that may need more time, by the due date; a late request forfeits the automatic extension.
• Model 2 institutions: hold the non-consenting U.S. account pool to the IGA date even when the main filing is extended.
• Confirm the IDES credentials, multi-factor access and certificate validity before each filing season; any of them can stop a file at the IDES gate.
• Point schema validation at the files inside the v2.0.1 package, whose names differ from the labels on the IRS schema page.
• Log the date on every NVF that lists record-level errors; the 120-day window runs from it.
• Swiss Model 2 filers: monitor implementation of the signed Model 1 agreement, whose earliest planned entry into force is 1 January 2029, and maintain existing reporting arrangements until the transition becomes applicable.

Sources and References

• IRS, 2025 Instructions for Form 8966, FATCA Report: i8966.pdf and HTML edition
• IRS, 2025 Form 8966, FATCA Report (OMB No. 1545-2246): f8966.pdf
• IRS, About Form 8966: irs.gov/forms-pubs/about-form-8966
• 26 U.S.C. 1471, Withholdable payments to foreign financial institutions: law.cornell.edu/uscode/text/26/1471
• 26 CFR 1.1471-4, FFI agreement (including paragraphs (d)(3)(vi) and (d)(3)(vii)): law.cornell.edu/cfr/text/26/1.1471-4
• 26 CFR 1.1471-5, Definitions applicable to section 1471 (including paragraph (a)(4), the $50,000 depository account exception): law.cornell.edu/cfr/text/26/1.1471-5
• Rev. Proc. 2017-16, Updated FFI Agreement: rp-17-16.pdf
• IRS, Frequently asked questions (FAQs) FATCA compliance: Legal (FFI agreement renewals, Q1, updated 17 January 2024): irs.gov FATCA legal FAQs
• IRS, FATCA XML schemas and business rules for Form 8966: schema page and FATCA XML v2.0.1 package
• IRS Publication 5124, FATCA XML Schema v2.0 User Guide (Rev. 04-2017): p5124.pdf
• IRS Publication 5190, IDES User Guide: p5190.pdf
• IRS Publication 5188, FATCA Metadata XML Schema v1.2 User Guide (Rev. 07-2020): p5188.pdf
• IRS Publication 5189, ICMM Notifications User Guide (Rev. 8-2020): p5189.pdf
• IRS Publication 5216, ICMM Notification XML Schema User Guide (Rev. 8-2020): p5216.pdf
• IRS, FATCA report notifications frequently asked questions: irs.gov FATCA notifications FAQs
• IRS, FATCA IDES technical FAQs: irs.gov FATCA IDES technical FAQs
• IRS, International Data Exchange Service: irs.gov IDES page
• IRS, IDES testing schedule: irs.gov IDES testing schedule
• IRS, FATCA IDES resources and support information: irs.gov IDES resources
• IRS, About Form 8809-I, Application for Extension of Time to File FATCA Form 8966: irs.gov/forms-pubs/about-form-8809-i
• IRS, FATCA governments (Model 1 and Model 2 IGAs): irs.gov FATCA governments
• U.S. Department of the Treasury, Foreign Account Tax Compliance Act resource center and IGA table: home.treasury.gov FATCA
• Swiss State Secretariat for International Finance (SIF), FATCA agreement page (earliest entry into force of the Model 1 agreement, 1 January 2029): sif.admin.ch/en/fatca-agreement
• Swiss Federal Administration (admin.ch), Switzerland and United States agree on mutual exchange of financial account data (27 June 2024): admin.ch media release

The next Form 8966 cycle: classification first, then the 31 March file

Several of the failure points above sit upstream of the upload: the status registered for each entity and branch, the GIIN data behind Part I and the IDES credentials that carry the file. For the calendar year now running, the operative date is 31 March of the following year, with a Form 8809-I filed no later than that date for any branch that needs the 90 days.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.