CRS, FATCA and US banking privacy for an LLC
CRS does not work the same way in Europe and the US. We explain what is reported, where privacy exists and how to document an LLC properly.
More than 120 jurisdictions exchange financial-account information under CRS. The United States is not a participating CRS jurisdiction: it uses FATCA, Bank Secrecy Act compliance, KYC, AML controls and legal-access procedures instead of a European-style automatic CRS export of balances.
If you run a US LLC with Mercury, Relay, Slash, Wise Business or another US banking layer, the serious question is not "can anyone see me?". The serious question is: what is reported, through which legal channel, by which entity, and what file must you keep to defend the structure.
Short answer: a US bank account held by a US LLC does not, by itself, create a yearly CRS package to your home tax authority with balances, holders and movements. That is real financial privacy. It is not anonymity. The bank knows the client, keeps records and can report when US law requires it, but the information does not travel like a standard European CRS account.
CRS 2.0, CARF and DAC8 for CRS, FATCA and US banking privacy for
The CRS picture for your LLC's bank accounts is updated by the OECD package: EMIs and electronic-money products are squarely inside the perimeter and due diligence on controlling persons becomes tighter. What Wise Europe SA or Revolut Bank UAB already reported keeps flowing, only with stricter criteria and more granular self-certifications at onboarding.
The OECD adopted an integrated package combining CRS 2.0 (the revised Common Reporting Standard, which brings EMIs and specified electronic-money products into the perimeter and tightens due diligence on controlling persons) and CARF (the Crypto-Asset Reporting Framework, which extends automatic exchange to crypto exchanges, custodians and crypto-derivative platforms). The European Union transposed it through Directive (EU) 2023/2226 (DAC8), adopted on 17 October 2023, which amends Directive 2011/16/EU to incorporate both components. The substantive application date is 1 January 2026 and the first effective exchange lands in January 2027 over the prior reporting period.
Official sources: <a href="https://www.oecd.org/tax/automatic-exchange/common-reporting-standard/" target="_blank" rel="noopener nofollow">OECD — CRS</a>, <a href="https://www.oecd.org/tax/exchange-of-tax-information/crypto-asset-reporting-framework-and-amendments-to-the-common-reporting-standard.htm" target="_blank" rel="noopener nofollow">OECD — CARF</a>, <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023L2226" target="_blank" rel="noopener nofollow">EUR-Lex — Directive (EU) 2023/2226 (DAC8)</a>.
This article is about the mechanics of CRS: who reports, which financial institution is involved, what information moves and why US banking is analysed through FATCA, bank records and legal-access procedures rather than the European CRS rail. A US LLC may still create reporting duties in the owner's country of residence, but the data route is not the same as a yearly CRS dump of balances and movements. We unpack the broader privacy layer in <a href="/en/blog/crs-carf-and-us-banking-privacy-for-llc-owners">CRS, CARF and US banking privacy for your LLC</a>.
The three mechanisms of international financial information exchange
1. CRS (Common Reporting Standard): The <a href="https://www.oecd.org" target="_blank" rel="noopener">OECD</a> standard used by 100+ countries for automatic exchange of financial account information. Financial institutions in participating countries automatically report non-resident account holders to their country of tax residence.
2. FATCA (Foreign Account Tax Compliance Act): The US law requiring foreign financial institutions to report accounts of US citizens/residents to the <a href="https://www.irs.gov" target="_blank" rel="noopener">IRS</a>. This is the US's own reporting mechanism (the US doesn't participate in CRS but uses FATCA instead).
3. Bilateral agreements: Specific treaties between two countries for information sharing upon specific request (not automatic).
Can your home country see your Mercury account?
The direct answer: Not automatically through CRS. The US doesn't participate in CRS.
Mercury's specific situation:
Mercury (through Column NA) operates exclusively within the US financial system. As a US-only institution, it doesn't have CRS reporting obligations. Column NA reports to the IRS (as required by US law), but doesn't automatically share information with foreign tax authorities.
However, this doesn't mean your account is invisible:
- FATCA Intergovernmental Agreements (IGAs): The US has signed IGAs with many countries. These allow reciprocal information sharing, but the scope and effectiveness vary significantly
- Specific requests under mutual assistance treaties: Your country's tax authority can request information from the US through tax treaty mechanisms. This requires a specific reason and formal request
- You are personally obligated to declare foreign assets in most countries (Modelo 720 in Spain, similar declarations in other countries)
Four reporting models you should not mix
Most confusion starts when CRS, FATCA, the IRS, FinCEN and US banks are treated as one single system. They are not. Each channel has its own trigger, destination and legal logic.
| Model | What may be reported | When it is triggered | Correct reading |
|---|---|---|---|
| CRS | Balance, ownership, tax residence and financial-account data for reportable accounts | Financial institution in a participating jurisdiction with a non-resident customer | Automatic exchange. US bank accounts do not run on this European-style CRS architecture |
| FATCA | Information tied to US persons and specific US tax forms | Banks and institutions inside the US tax-information framework | Not CRS in reverse. Its main focus is US tax exposure |
| BSA/AML and FinCEN | Cash activity, suspicious patterns, compliance records and risk signals | CTR, SAR, AML alerts, bank review or investigation | Financial-crime compliance, not mass tax reporting |
| Formal request or international cooperation | Specific account, holder or transaction information | Procedure, indicators, legal basis and cooperation between authorities | A legal channel. Not a yearly automatic dump |
That distinction matters for digital founders. A US bank account should not be sold as anonymity, but it should not be explained as if it were a European CRS account either. The reality is stronger: procedural financial privacy, serious KYC, bank records, regulated reporting and local filing duties that must be handled with discipline.
Are balances, interest or transactions reported?
For a US bank account, separate three layers:
- Balances and bank movements. They are not automatically sent every year to your tax-residence country as a CRS package just because an LLC holds a US account. The bank keeps records and can answer lawful requests, but that is a different mechanism.
- Reportable income. If the account generates interest or other payments subject to information forms, US tax reporting can exist. That is not the same as a full transaction ledger being exported abroad.
- Suspicious activity or cash. Under the Bank Secrecy Act, FinCEN and AML controls, certain operations can trigger CTR, SAR or internal reviews. This is US financial compliance, not “your home tax office receives everything”.
The professional conclusion is not “nothing happens”. It is this: if your LLC receives clients, pays providers, retains profits or distributes funds, activity, banking, invoices, contracts and tax residence must stay aligned. That is where privacy becomes defensible.
Real privacy does not mean improvising
US financial privacy has value because access to bank information runs through procedures, not through a general CRS export of balances. But that privacy loses strength quickly when the file is incoherent.
Clear examples:
- invoices issued by an LLC while the website does not explain the business;
- commercial income landing in personal European accounts;
- frequent withdrawals to personal accounts with no tax logic;
- personal expenses paid by the LLC as if they were operating costs;
- local clients deducting LLC invoices that cannot be explained;
- a bank account opened before contracts, activity, UBO, source of funds and KYC narrative are ready.
A well-designed LLC does not depend on silence. It depends on order. If someone asks, the answer should not be “nobody sees it”; it should be “this is the structure, this is the activity, this is the documentation and this is the tax treatment behind each movement”.
Wise, Revolut and the mistake of reading a brand instead of the legal perimeter
Wise and Revolut are not single, simple buckets. The brand is not the tax analysis. The analysis starts with legal holder, contractual entity, product, self-certification and actual use.
- Wise Personal is not Wise Business. A personal Wise account held by a CRS-resident individual is a personal product and should not be used to collect LLC business revenue. If that account sits with a European Wise entity, it can fall inside CRS reporting for that individual.
- Wise Business for a US LLC is different. The account should be opened in the company name, with EIN, UBO, business activity and self-certification aligned. The USD side may sit in the Wise US Inc. perimeter under US KYC/AML/FATCA rules, while European IBAN or e-money features can involve Wise Europe SA and CRS due diligence.
- Revolut Business for a US LLC is not Revolut Bank UAB in Europe. The US product can operate through Revolut Technologies Inc. and a US banking partner. European IBANs belong to a different perimeter. If an IBAN appears in the stack, confirm exactly which entity issues it and which regime applies.
The practical implication is not "avoid Wise" or "Wise reports everything". It is more useful: do not collect business money through personal European accounts, do not let the visible IBAN drive the conclusion, and document which legal entity holds each account before you move serious volume.
What information is exchanged under CRS, where CRS applies
Where CRS applies, the exchange generally revolves around account holder identity, tax residence, tax identification number, year-end balance and certain income. It is not usually a full export of every invoice or card transaction, but it is enough to create a fiscal signal. That is why the banking perimeter must match the tax file before the first review, not after.
Your declaration obligations
Regardless of what exchanges happen automatically, you have personal obligations:
Spain: Modelo 720 for foreign assets exceeding €50,000 (bank accounts, investments, real estate abroad). Penalty for non-declaration can be significant. Exentax documents that point before it becomes an operational emergency.
Mexico: Informational declaration of foreign investments (required by SAT).
Colombia: Declaration of foreign assets (required by DIAN).
Argentina: Personal assets declaration including foreign assets (Bienes Personales).
Chile: Declaration of foreign income and assets.
Why documentation gives you leverage
A correctly operated US LLC is not defended with slogans. It is defended with a file:
- invoices issued by the right entity;
- business expenses separated from personal spending;
- distributions and retained profits tracked in the bank statements;
- Form 5472 plus pro-forma 1120 calendar under control;
- BOI scope reviewed under the current FinCEN rule instead of treated as a routine filing;
- contracts, website, activity description and source of funds aligned under one documentary standard.
That is the commercial strength of the structure. You are not relying on a blind spot. You are using a legal US company, a different financial reporting architecture and a documented operating file.
The trend: more reporting, but not one single reporting system
The world is moving toward more financial reporting, but not every channel reports the same thing. CRS, FATCA, DAC8, CARF, 1099 forms, AML reviews, processor reporting and domestic declarations are different systems with different triggers.
Exentax's position is simple: use the privacy US banking gives you, but do not build a structure that collapses if a bank, processor or tax authority asks a serious question. The privacy is strongest when the file is clean.
What Mercury, Relay, and Wise report (and to whom)
| Platform | Banking partner | CRS participant? | Reports to IRS? | Reports to foreign tax auth? |
|---|---|---|---|---|
| Mercury | Column NA | No (US-based) | Yes | Not automatically |
| Relay | Thread Bank | No (US-based) | Yes | Not automatically |
| Wise | Multi-jurisdiction EMI | Partially (non-US entities) | US entity: Yes | May report via CRS jurisdictions |
| Slash | Treasury platform | Depends on structure | Yes | Not automatically |
| Revolut | Multi-jurisdiction | Yes (EU entities) | Some | Yes (via EU CRS) |
Practical implications for your LLC operations
- US operating layer by profile: Relay, Slash or Mercury sit in the US/FATCA banking perimeter when the account is held by the US LLC, but the decision must follow the entity, KYC story, corridors and closure mechanics. Your treasury should be well-organized and documented before the first review.
- Wise as treasury, conversion or payment layer only when the perimeter is clear: Wise can be useful, but the product must be in the LLC name, with business use, entity and self-certification aligned. A personal Wise account in Europe is not a business bank stack for a US LLC.
- Revolut with entity-level awareness: Revolut Business for a US LLC and a European Revolut Bank UAB account are not the same perimeter. Before using it for EUR/GBP operations, confirm holder, legal entity, reporting regime and what the tax file will say.
The strategy that works long-term
Build your LLC structure assuming full transparency. Because:
- Everything is documented (invoices, contracts, Mercury statements)
- All filings are current (Form 5472, BOI scope review when applicable, FBAR if applicable)
- All distributions are tracked (Owner's Draws documented)
- All deductions are legitimate (receipts and business purpose documented)
- You declare in your country of residence as required
When you operate this way, CRS, FATCA, DAC8, CARF or a formal request stop being existential threats and become reviewable facts. The advantage is not pretending that information exchange cannot exist. The advantage is knowing exactly which channel applies, what it can show and why your structure still makes sense.
Frequently asked questions about CRS and information exchange
Does CRS mean my country knows exactly how much I earn?
No. CRS reports account balances and interest income, not individual transactions, invoices, or income details. Your tax authority sees a year-end snapshot, not your full transaction history.
If the US doesn't participate in CRS, am I "safe"?
"Safe" is the wrong framing. You should operate with full transparency and declare everything as required. The US not participating in CRS means automatic reporting from Mercury to your tax authority doesn't happen, but it could change in the future, and you have personal declaration obligations regardless.
Should I worry about FATCA?
FATCA primarily targets US persons with foreign accounts. As a non-US person with US accounts, FATCA's impact on you is limited. However, FATCA IGAs may enable some reciprocal information sharing between the US and your country.
What about Stripe and PayPal, do they report?
Stripe and PayPal are payment processors, not banks. They report to the IRS when thresholds are met (Form 1099-K for US-based activity). They generally don't participate in CRS automatic exchange for non-US accounts.
Can my tax authority request my Mercury statements directly?
Through formal tax treaty mechanisms (mutual legal assistance), yes, but this requires a specific investigation, formal request, and legal process. This is not automatic bulk reporting.
For CRS and US banking, the practical next step is to map every account by legal entity, provider perimeter, tax self-certification and expected use. Privacy is strongest when the file explains the structure before a bank or authority asks for it.
> <a href="/en/book">Review my structure</a>
- Mercury: as a US banking layer, it requires coherence between ownership, activity, residence country, source of funds and KYC/KYB documentation. It does not provide opacity; it provides USD operations when the file explains why the LLC receives, holds or moves funds in the US.
- Payoneer operates through European entities (Payoneer Europe Ltd, Ireland) that are also in scope for CRS for clients resident in participating jurisdictions.
That note should sit next to the Operating Agreement, EIN letter, Form 5472 file, invoices, bank statements and distribution register. It is not bureaucracy. It is the difference between a structure that sounds clever and a structure that can be explained under pressure.
FinCEN and IRS reporting requirements moved recently; the current state is:
- EIN and notice. Without an EIN you cannot file Form 5472. The IRS does not warn before imposing penalties; you find out when an EIN is flagged or a later filing is rejected. The Exentax approach is practical: confirm the data, prepare the evidence and close the next step.