FATCA and CRS for Business Accounts: Tax Declarations at Onboarding

FATCA and CRS for business accounts — the tax-residency declarations banks must collect at onboarding, entity classifications, and how to capture them cleanly.

Tax-information reporting has become a standing obligation for every bank that opens an account, and for business accounts it is rarely a single tick-box. FATCA and CRS require a bank to establish where an entity is tax-resident, how that entity is classified, and — for many entities — who the controlling persons behind it are. Get the declaration right at onboarding and the reporting that follows is mechanical; get it wrong and the bank spends months chasing customers for self-certifications it should have collected on day one.

Why tax declarations belong at account opening

The Foreign Account Tax Compliance Act (FATCA) is United States legislation that requires financial institutions outside the US to identify accounts held by US persons and report them. The Common Reporting Standard (CRS), developed by the OECD and adopted by most jurisdictions including Kenya, generalises the same idea to automatic exchange of financial-account information between tax authorities. Both regimes share a common mechanic: the account-opening institution is the data-collection point. The bank cannot report what it never captured.

For business accounts this matters more than for individuals, because an entity can be tax-resident in more than one country, can change classification over time, and can sit on top of a chain of owners who are themselves reportable. The cleanest moment to ask these questions is during onboarding, while the applicant is already assembling documents and is motivated to complete the application. Asking later — by email, after the account is live — produces low response rates, partial answers and a backlog of incomplete records that an examiner can see at a glance. This is why tax self-certification sits alongside the rest of the customer due diligence you perform when onboarding a business.

What an entity self-certification actually establishes

A self-certification is the entity's own declaration, on which the bank is entitled to rely unless it has reason to doubt it. For a business account it generally needs to establish three things.

The first is tax residency: the country or countries in which the entity is treated as resident for tax purposes, together with the relevant taxpayer identification number in each — in Kenya, the KRA PIN. An entity may declare a single residency or several.

The second is FATCA status: in plain terms, whether the entity is a US person, a foreign financial institution, or a non-financial foreign entity, and which sub-category applies.

The third is CRS entity classification, which is where most of the practical judgement lies. Under CRS an entity is broadly either a Financial Institution or a Non-Financial Entity (NFE), and an NFE is in turn either active or passive. The distinction is not cosmetic. A passive NFE — loosely, an entity that mainly holds assets and earns passive income rather than running an active trade — triggers a look-through requirement: the bank must identify the entity's controlling persons and determine their tax residency as well.

Looking through passive entities to controlling persons

The look-through obligation is the part of CRS that most often surprises onboarding teams. When a business is classified as a passive NFE, the controlling persons — the natural persons who ultimately own or control the entity — become reportable in their own right, and the bank must capture and, where applicable, report each one's tax residency. In substance the population of controlling persons overlaps heavily with the beneficial owners you already identify at onboarding: directors, shareholders above the relevant threshold, partners, and the sole proprietor of an unincorporated business.

This overlap is an opportunity, not a coincidence. The same significant-stakeholder information that supports your AML beneficial-ownership analysis can populate the CRS controlling-person fields, provided your onboarding journey captures it once and reuses it. Banks that treat tax reporting and AML as separate questionnaires end up asking the customer for the same names twice and reconciling two lists later. The deeper work of resolving ownership chains and tracing control sits with your AML programme, and our guide to beneficial ownership and entity resolution covers that analysis; at onboarding the goal is simply to capture a clean, structured stakeholder list that both regimes can draw on.

The cost of collecting it badly

Poor tax-data collection is expensive in ways that do not show up until later. A self-certification that is missing, internally inconsistent, or unsigned is not a small defect — under both FATCA and CRS the bank may be unable to rely on it, which means remediation. Remediation at scale means an operations team writing to live customers, waiting for replies, escalating, and in some cases restricting accounts until a valid certification is received. Customers who completed onboarding weeks ago do not understand why they are being asked again, and relationship managers absorb the friction.

The failure modes are predictable:

• Free-text residency instead of a structured country and TIN, so the data cannot be validated or exported.
• No look-through trigger, so a passive NFE is opened without any controlling-person tax data, and the gap is only discovered at reporting time.
• Declarations on paper or PDF, detached from the rest of the application, with no record of who certified what and when.
• No reasonableness check, so a certification that contradicts the entity's own incorporation or address details is accepted unquestioned.

Each of these is cheap to prevent at the point of capture and costly to fix afterwards. The discipline is the same one that governs the wider corporate account-opening process: ask the right structured question once, at the right step, and validate it before the application moves on.

How BAOS captures the FATCA declaration at onboarding

The Creodata Business Account Opening System handles tax declarations as part of its guided nine-step application wizard rather than as a detached form. Step 4 of the wizard is the Compliance step, and it is here that the applicant completes the FATCA declaration alongside the PEP declaration and the significant-stakeholder (beneficial owner) information for directors, shareholders, partners, or the sole proprietor. Because the wizard auto-saves to draft between steps, a business that needs to confirm its tax position before certifying can leave and resume the application later without losing what it has entered.

Capturing the declaration inside the structured flow has three practical effects. First, the FATCA declaration is bound to a specific application and applicant, with the bank's append-only audit log recording the action — so there is a defensible record of what was certified and when. Second, the significant-stakeholder list collected in the same step is the same list your compliance staff use for KYC and beneficial-ownership review, which removes the double-keying problem described above. Third, the compliance screening service and the staff compliance-review workflow let an officer examine the declaration in context — against the entity details from step 1 and the documents uploaded at step 9 — rather than in isolation, supporting the reasonableness check that both regimes expect.

A clear word on scope: BAOS captures the FATCA declaration and the structured stakeholder data that supports tax classification. It does not generate CRS reports, build XML returns, or file with a tax authority. Reporting remains a downstream process in the bank's tax-reporting tooling. What BAOS gives that process is clean, validated, attributable input — which is precisely the part that goes wrong when declarations are collected on paper. Because the platform is multi-tenant and white-label, the exact declaration fields and the document checklist can be configured per institution without code changes, so a bank can align the wording of its self-certification with its own legal and tax review.

Where tax declarations sit in the wider onboarding record

A FATCA declaration is one strand of a business application that also includes account selection, facilities, signatories, the signing mandate and the board resolution. Its value to the bank depends on living inside the same auditable record as everything else. When a declaration, the supporting document checklist, the stakeholder list and the compliance officer's review all share one application and one audit-ready onboarding trail, the bank can answer a regulator's question about any single account quickly and completely — which is the real test of whether tax-information collection has been done well. Tax declarations captured at onboarding then feed naturally into the ongoing monitoring your AML programme runs after the account is live.

Frequently asked questions

Does Creodata BAOS generate FATCA or CRS reports for the tax authority?

No. BAOS captures the FATCA declaration during the Compliance step of its account-opening wizard, together with the structured significant-stakeholder data that supports entity and controlling-person classification, and it stores that data in an auditable record tied to the application. It does not produce CRS returns, build reporting XML, or file with any tax authority. Report generation and filing remain a downstream process in the bank's own tax-reporting tooling; what BAOS provides is clean, validated, attributable input to that process rather than declarations collected on detached paper or PDF forms.

What is the difference between an active and a passive non-financial entity, and why does it matter at onboarding?

Under the Common Reporting Standard, a non-financial entity is broadly active if it mainly carries on a trade or business and earns active income, and passive if it mainly holds assets and earns passive income such as dividends, interest or rent. The distinction matters because a passive NFE triggers a look-through requirement: the bank must identify the entity's controlling persons and capture each one's tax residency, not just the entity's own. Establishing the classification at onboarding tells you immediately whether you also need controlling-person data, so you can collect it in the same session rather than reopening the file later.

How does collecting tax declarations at onboarding reduce later remediation?

Collecting a structured, validated self-certification while the applicant is still completing the application avoids the most expensive failure mode in tax-information reporting: discovering at report time that declarations are missing, inconsistent or unsigned, and then having to write to live customers to fix them. Capturing residency as a structured country and TIN, triggering the look-through where the entity is a passive NFE, and recording who certified what and when all happen at the point of capture, where they are cheap. The alternative — chasing self-certifications after the account is open — produces low response rates, partial answers and a backlog an examiner can see.

The FATCA declaration is one step in a much larger onboarding discipline. For the full picture, read our complete guide to business account opening, see how Creodata captures tax, compliance and ownership data in one guided journey on the Business Account Opening System product page, and book a demo to walk through the Compliance step with our team.