Editorial Standards
How we research, review, and update this guide
Every Accountably guide is researched against primary IRS sources, reviewed by a U.S. CPA, and refreshed as guidance evolves. Read our Editorial Guidelines to see how we source, fact-check, and update our content.
The common mistake with Form 8966 is reaching for paper. You do not mail this one; it goes electronically through the International Data Exchange Service after you secure a GIIN or other IRS FATCA Entity ID, enroll, then upload an encrypted package. A team that prints a stack of FATCA reports learns this the hard way during pre-flight review.
Calendar-year 2025 data is due March 31, 2026, the same March 31 pattern that put 2024 data on March 31, 2025. The report pulls account holder details, each substantial U.S. owner, account numbers, year-end balance, and aggregate payments. If you need more runway, Form 8809-I grants an automatic 90-day extension.
Key Takeaways
- You file Form 8966 electronically in IDES, not on paper. Get a GIIN or other IRS FATCA Entity ID, enroll, then upload your encrypted package.
- Due date is March 31 for the prior calendar year. For example, 2024 data was due March 31, 2025, and 2025 data is due March 31, 2026. You can request an automatic 90-day extension via Form 8809-I, mailed to the Austin FATCA address.
- Reporting covers account holder details, each substantial U.S. owner, account numbers, year-end balance (or balance immediately before closure if the account was closed during the year), and aggregate payments like interest, dividends, and gross proceeds.
- Who actually files, PFFIs, Reporting Model 2 FFIs, QI/WP/WT, Direct Reporting NFFEs, certain withholding agents, sponsoring entities, trustee documented trusts, and U.S. branches treated as U.S. persons in limited cases. Reporting Model 1 FFIs normally report to their local tax authority, not on Form 8966 to the IRS.
- IDES requires FATCA XML Schema v2.0; verify the currently effective schema version with the IRS IDES User Guide before filing so your software is current.
What Is IRS Form 8966?
Form 8966, the FATCA Report, is the information return used to report U.S. accounts, substantial U.S. owners of passive NFFEs, and certain other relationships depending on your chapter 4 status. It is generally an electronic filing through IDES, the IRS’s secure gateway for FATCA data, with paper filing limited to narrow filer categories specifically permitted in the IRS Instructions for Form 8966. You report identifiers for the filer, account holders, and owners, plus the balance and payment aggregates. You are not filing detailed income statements here, you are reporting required FATCA data elements.
A quick but crucial point on who files, Reporting Model 1 FFIs usually report to their local authority under the IGA and do not submit Form 8966 directly to the IRS. Reporting Model 2 FFIs report to the IRS on Form 8966. If you are uncertain which model applies, confirm your jurisdiction and your registration status before building files.
What You Will Report, In Plain Language
- Filer identity, your name and address, your category code, and your GIIN. If you have a U.S. TIN in this capacity, follow the IRS line instructions.
- Account holders, one per line, with name, address, classification, and TIN if available.
- Owners, every substantial U.S. owner of a passive NFFE (generally more than 10% ownership by vote or value, though a 0% threshold applies for foreign investment vehicles under Treasury regulations), with name, address, and TIN.
- Account data, account number, currency code (three-letter ISO 4217 alphabetic code such as USD, EUR, or GBP, not currency symbols or numeric codes), year-end balance (or balance immediately before closure if the account was closed during the year), and aggregate amounts for interest, dividends, gross proceeds, and other income.
In practice, I keep a short internal checklist, “IDs, owners, balances, aggregates.” It prevents the most common late stage scramble, missing owner TINs or a wrong currency code.
A Quick Note On Extensions And Timing
The annual deadline is March 31. If you need time, file Form 8809-I for a 90-day extension, which is paper mailed to the Austin FATCA address. The IRS can grant a second 90-day extension for hardship, but you must apply by the first extended due date and explain the extenuating circumstances. Plan ahead, because digital certificates can take weeks, and GIIN or FATCA Entity IDs also take time.
If you like to test in advance, the IRS opens IDES test windows, for example a June 2025 window, so your team can validate packaging and file names without risking production rejects.
Who Must File, And What They Report
Here is a simple view you can share with your team.
| Filer type | Do you file Form 8966 to IRS? | What you report |
| Participating FFI, includes Reporting Model 2 FFI | Yes | U.S. accounts, substantial U.S. owners of passive NFFEs, permitted pooled data for recalcitrant or non consenting accounts |
| Reporting Model 1 FFI | Generally No, report to local authority under IGA | Report under local rules to HCTA, not directly to IRS on Form 8966 |
| QI, WP, WT | Yes, when required under your agreement | Accounts, partners, beneficiaries, or owners as applicable |
| Direct Reporting NFFE | Yes | Each substantial U.S. owner, or report none |
| Sponsoring Entity | Yes, when filing for a Sponsored FFI or Sponsored Direct Reporting NFFE | Same data the sponsored entity would report |
| Withholding agent that is not an FFI, includes certain U.S. branches | Yes, in limited cases | Substantial U.S. owners or specified U.S. persons tied to withholdable payments, per rules |
| Trustee Documented Trust, trustee acts | Yes | Report required info as if a Reporting Model 2 FFI |
These categories come straight from the IRS instructions. If you are a Model 1 FFI, do not send Form 8966 to the IRS unless a special rule applies, you report to your tax authority instead.
The Data You Need On Your Desk
Collect these items before you open your software, it will save hours later.
- Filer identifiers, GIIN, and, if applicable, the correct U.S. TIN for the capacity in which you file.
- Account holder details, legal name, address, classification, account number, ISO 4217 currency.
- Owner details, each substantial U.S. owner of a passive NFFE, full name, address, and TIN.
- Financial amounts, year end or average balance, total interest, total dividends, gross proceeds, and other income.
- Status flags, closed or transferred accounts, pooled report types.
Per Account, Per Owner, Or Pooled
- Per account, report each U.S. account with required data.
- Per owner, file a separate form for each substantial U.S. owner of a passive NFFE.
- Pooled reporting, allowed for recalcitrant holders or non consenting U.S. accounts, use Part V, one pool per form. Keep backup schedules ready for auditors.
Pro tip, if your team is new to pooled reporting, draft a one page SOP that lists your pool codes, how you aggregate amounts, and where you store the support. It speeds reviews and avoids second guesses during an exam.
Common Misunderstandings To Avoid
- “All FFIs file 8966 to the IRS.” Not true, Model 1 FFIs report to their HCTA.
- “Any XML version will do.” IDES requires FATCA XML Schema v2.0; verify the currently effective schema version with the IRS IDES User Guide before generating files and update your tools accordingly.
- “We can request the extension online.” Not for Form 8966, use Form 8809-I by mail and do it before March 31.
Deadlines, Extensions, And A Simple Calendar
- Standard due date, March 31 for the prior calendar year. If you are planning your 2025 filing season, that means 2025 data is due March 31, 2026.
- Automatic extension, file Form 8809-I for a 90-day extension (the general Form 8809 used for other information returns does not cover Form 8966, so use the -I variant). Mail it as soon as you know you need time, but not before January 1 of the filing year, and not after the original due date.
- Hardship extension, if needed, you can request one additional 90-day extension due to extenuating circumstances, and you must submit the second request by the first extended due date.
Where to mail the extension, Internal Revenue Service, FATCA, Stop 6052 AUSC, 3651 South IH 35, Austin, TX 78741. Keep proof of mailing.
Penalties And Practical Risk
The instructions reference general information return penalties for late or incomplete filings under IRC §6721 and §6722 (not the §6651 failure-to-pay regime, which applies to income tax returns rather than information returns like Form 8966). In practice, the bigger operational risk is a rejected transmission on the deadline week. Protect yourself with lead time, a clean SOP, and a test run. The IRS periodically opens IDES testing windows, for example June 2025, which are ideal for dry runs.
Nil, Corrected, And Void Reports
- Nil reports, many filers send a nil report when no reportable accounts exist, often to satisfy internal policy or regulator expectations (whether nil reporting is actually required is not universal, it depends on your FFI agreement and applicable IGA, so confirm before defaulting in either direction). IDES accepts nil submissions that meet schema rules. Use the current schema and the correct DocType codes.
- Corrections, if you discover an error after acceptance, file a corrected or void report per the schema rules, keep a simple register that ties original and corrected transmissions by MessageRefId.
Model 1 Special Note
If you are a Reporting Model 1 FFI, your reporting cadence and method come from your local tax authority, not from Form 8966. Still, your data set will look similar, so the preparation steps here will help your accuracy.
Small habit that pays off, add calendar holds for March 1, March 15, and March 25. Those three checkpoints catch missing TINs and wrong currency flags long before March 31.
Quick Compliance Note
This guide is general information, not legal or tax advice. Always confirm the latest instructions and your local IGA rules before filing. For the 2025 season, check the 2024 Form 8966 instructions page and the FATCA XML schema v2.0.1 update.
IDES Packaging, The Step By Step Version
You can follow this in your SOP exactly as written.
- Create the FATCA XML and validate against FATCA XML Schema v2.0 (verify the currently effective schema version with the IRS IDES User Guide before each filing run).
- Digitally sign the XML using an enveloping XML signature, SHA 256 hash, RSA 2048 bit key. Do not use detached or enveloped types.
- Compress the signed XML into the sender payload zip, file name format matters, for example 000000.00000.TA.840_Payload.zip.
- Encrypt the payload with AES 256 in CBC mode, IV of 16 bytes, PKCS 5 or 7 padding.
- Encrypt the AES key and IV with the IRS public key, RSA 2048, PKCS#1 v1.5 padding. If applicable, also encrypt for an approving HCTA.
- Create the metadata XML using the published metadata schema, do not encrypt the metadata.
- Build the final transmission archive with the UTC timestamp in the file name, then upload in IDES or via SFTP. Keep the confirmation message for your records.
The IRS runs IDES across modern browsers and SFTP. If you are new to the portal, enroll early, upload your certificate, and confirm your GIIN or Entity ID authorization before filing week.
Certificates, Lead Times, And Team Roles
- Digital certificate, obtain one from an IRS approved certificate authority. Budget two to four weeks for procurement and internal security approvals.
- GIIN or FATCA Entity ID, registration lead times vary, start early. The IRS also references a FIN and HCTA Entity ID for certain test or authority flows.
- Roles, maker checks data, checker validates against schema, submitter packages and uploads, reviewer monitors the IDES receipt and error notifications. Put names next to each role.
The Most Common Rejects I See
- Wrong signature type, anything other than enveloping gets rejected.
- File name format errors, IDES is picky about case, underscores, and timestamps.
- Old schema, sending v1.1 or a mismatched element, update to the currently effective FATCA XML Schema v2.0 per the IRS IDES User Guide.
- Certificate problems, expired or mismatched certificate in the IDES profile.
Build Your One Page SOP
Keep it simple and visible, one page that covers, document naming convention, DocType codes for new, corrected, and void reports, who signs, who uploads, where confirmations are stored, and your escalation path if IDES is unavailable in the final 48 hours.
If your internal team is stretched during peak season, a disciplined external team can help with packaging and validation without taking over client relationships. On Accountably.com, we keep the mention light, our U.S. led offshore teams can prepare schema compliant XML, validate, and package inside your systems and SOPs, then your firm submits, so you stay in control of risk and review time.
A Practical Checklist You Can Reuse
- Confirm filer type and obligation, Model 2 FFI, PFFI, QI/WP/WT, Direct Reporting NFFE, sponsor, trustee, or withholding agent.
- Gather data, filer GIIN, holder and owner details, balances, and aggregates.
- Validate classifications, entity status, substantial U.S. owners, and pooled categories.
- Prepare XML using FATCA XML Schema v2.0 (confirm the currently effective version with the IRS IDES User Guide).
- Package for IDES, enveloping signature, AES encryption, correct file names, metadata.
- File early, monitor confirmations, and store receipts with your workpapers.
- If needed, mail Form 8809-I for a 90-day extension, and calendar the new due date.
FAQs
Do Model 1 FFIs file Form 8966 with the IRS?
Generally no. Reporting Model 1 FFIs report to their local tax authority under the IGA, not directly to the IRS on Form 8966. Model 2 FFIs file Form 8966 with the IRS.
What exactly is due on March 31?
Form 8966 for the prior calendar year. For example, 2025 data is due March 31, 2026. If you need time, mail Form 8809-I for a 90-day extension before the due date.
Can I send a nil report?
Yes, many filers submit nil reports when no reportable accounts exist. Your package must still meet schema and IDES rules.
What is pooled reporting?
It is aggregate reporting for recalcitrant holders or non consenting U.S. accounts. Use Part V, one pool per form, and maintain support schedules.
What schema version should my software use?
Use FATCA XML Schema v2.0. Verify the currently effective schema version with the IRS IDES User Guide before each filing run, since files using older versions will be rejected.
How do I fix an accepted file with an error?
Submit a corrected or void report under the schema and IDES packaging rules, and keep a register that ties corrections to the original MessageRefId.
How Accountably Can Help, Briefly
If you need extra capacity for FATCA season, our team can work inside your systems to build clean workpapers, prepare the XML, and assemble IDES packages that follow your SOPs, so partners stay focused on reviews, not rework. If that would help, reach out and ask for our Form 8966 checklist and sample SOP.
Conclusion
Form 8966 gets easier once you lock your data set, your roles, and your IDES steps. Confirm your filer status, collect IDs and owner details, validate balances and aggregates, and package with the right schema and signature type. File early, mail extensions when needed, and keep clean audit trails. Do that, and your FATCA reporting will stand up to scrutiny year after year.
Common Mistakes We See Every Season
Across our FATCA engagements, the same recurring filing errors show up year after year. The IRC §6721 penalty stack moves fast on Form 8966, so catching these in pre-flight saves real money and senior-reviewer time.
Reusable Checklists
Copy the lists below into your engagement SOP, workpaper template, or tracker. Each item is a pre-flight step we run before any Form 8966 IDES upload leaves the building.
Pre-IDES filing packet
- Confirm filer status (Participating FFI, Reporting Model 2 FFI, registered deemed-compliant FFI, withholding agent, or sponsoring entity) and document the source.
- Verify the 19-character GIIN format (XXXXXX.XXXXX.XX.XXX) on Part I Line 4 against the monthly IRS FFI List and capture the snapshot date.
- Pull the two-digit filer category code for Part I Line 1b and reconcile it against the filer's FATCA status code in the registration record.
- Capture the three-digit identifier number when a paper-eligible filing path applies; otherwise mark the engagement electronic-only.
- Confirm IDES enrollment, AES-256 encryption keys, and IRS PKI signing credentials are current.
- Validate the FATCA XML schema version effective for the 2025 filing year before generating the package.
Account data validation
- For each reportable U.S. account, capture Part II account-holder name, address, and TIN, and check exactly one of Individual or Entity on Part II Line 1b.
- For entity holders, check exactly one of the four Part II Line 5 categories: Owner-Documented FFI with specified U.S. Owner(s), Non-Participating FFI, Passive NFFE with substantial U.S. Owner(s), or Specified U.S. Person.
- For passive NFFEs and owner-documented FFIs, file a separate Form 8966 per U.S. owner with Part III Lines 1-4 completed.
- Report Part IV Line 3a as the year-end account balance, or the balance immediately before closure with Part IV Line 3b checked.
- Aggregate Part IV Line 4a interest, 4b dividends, 4c gross proceeds, and 4d other payments for the calendar year, using three-letter ISO 4217 currency codes on Part IV Line 2.
- When Part V Pooled Reporting applies, file a separate Form 8966 per pooled category and reconcile Lines 3 and 4 aggregates against the underlying roster.
Post-submission audit trail
- Save the IDES notification IDs, MessageRefId, and acceptance receipt against the filer's engagement file.
- Maintain a corrections register that links any Corrected, Amended, or Voided report to the original MessageRefId and the trigger event.
- Document nil-filing decisions against the FFI agreement or applicable IGA so the no-accounts-to-report checkbox is supported by written evidence.
- Calendar the next-year refresh of GIIN status, sponsoring-entity relationships, and pooled-category counts in November so January and February prep runs clean.
- Log any §6721 exposure scenarios encountered (late files, schema rejections) and bring them into the post-season debrief.
Keep 8966 Season From Stalling
FATCA season is a narrow window. The March 31 IDES deadline arrives with calendar-year 2025 account data, schema validation, AES-256 encryption, IRS PKI signing, and pooled-category reconciliation all converging at once. The IRS publishes the FFI List monthly (per the IRS FATCA Online Registration System), which means filer status, GIIN currency, and sponsoring-entity relationships can shift between November planning and March execution if the workflow does not track them.
The fix is treating Form 8966 as a packaging discipline, not a return. Once the workpaper template, schema dry-run, and IDES upload SOP are in place, the team stops rebuilding the workflow every March and the reviewer load drops to exception handling. The IRC §6721 information-return penalty regime and the 30% FATCA withholding exposure under IRC §1471(a) make documented turnaround a real margin lever, not a nice-to-have.
- Lock a workpaper template that ties Part I Lines 1-10 to the registration record, Part II Lines 1-5 to the account-holder file, and Part III Lines 1-4 to the U.S. owner roster for passive NFFEs and owner-documented FFIs.
- Run a schema dry-run against the current FATCA XML schema version before every IDES upload so encryption, signature, and structural issues fail in staging, not production.
- Maintain a corrections register that links Corrected, Amended, Voided, and no-accounts reports back to the original MessageRefId so the audit trail stays clean across multi-year reporting.
- Separate pooled reporting categories per form on Part V Line 1, reconciling Lines 2-4 against the underlying roster before submission so a single rejected file does not stall the whole batch.
- Calendar Form 8809-I evaluation by the first week of March so the automatic 90-day extension is requested on time, not after the original deadline slips.
Our team handles the FATCA workpaper build, IDES packaging, and post-submission reconciliation inside your existing review workflow. See tax outsourcing services for how we plug a documented Form 8966 process into your filing calendar.