The Documentation Gap: What Authorities See That Founders Don't

When founders think about their structural position, they see what exists: the tax return that was filed, the bank account that works, the entity that was registered.

When an authority examines the same structure, they see what's missing. The gaps between records. The absence of documentation that would support a claimed position. The distance between what the formal structure says and what the evidence shows.

This difference in perspective — between the founder's view and the examiner's view — is a structural characteristic that becomes visible only under scrutiny.

Authorities look at evidence trails, not intentions

A common mental model: "I set up the entity correctly, I file my taxes, and my intentions are good — so my position is defensible."

Authorities do not assess intentions. They assess evidence. Transaction records, bank statements, travel patterns, communication timestamps, entity filings, tax returns — these form an evidence trail that tells a story independent of what the founder intended.

When that evidence trail is consistent with the claimed position, it supports it. When there are gaps — missing records, inconsistent information across different contexts, undocumented decisions — the gaps themselves become part of the assessment.

The structural observation: the evidence trail exists whether or not the founder has mapped it. Authorities see the full picture, including the absence of documentation. Founders typically see only what they've created.

Information flows between jurisdictions

Tax authorities, banks, and financial institutions increasingly share information across borders. The CRS (Common Reporting Standard) means bank account information in one jurisdiction may be automatically reported to the tax authority in another.

For founders with entities, accounts, or activities in multiple jurisdictions, this means the evidence trail is wider than what any single institution holds. A bank in one country, a payment processor in another, a tax filing in a third — each holds a piece of the picture. Information sharing assembles the pieces.

The structural implication: inconsistencies that exist across different contexts — different descriptions of business activity, different reported income figures, different entity information — may become visible when information from multiple sources is compared.

Retroactive documentation is viewed with skepticism

When founders discover documentation gaps, the instinct is to create the missing records. This is understandable — the gap exists, and filling it feels like solving the problem.

In practice, documentation created after the fact carries less weight than documentation created at the time of the decision or transaction. Authorities have seen enough retroactive documentation to treat it with appropriate caution.

The distinction matters: contemporaneous documentation — records created in the normal course of business, at the time of the relevant activity — is viewed as organic evidence. Retroactive documentation — records created specifically to address a gap identified later — is viewed as a response to scrutiny.

Both may be accurate. But their evidentiary weight is different. And the presence of retroactive documentation may itself raise questions about why the records didn't exist earlier.

Second-order effects of structural gaps

Documentation gaps don't exist in isolation. They cascade into other domains.

A tax residency position that lacks substance documentation may interact with banking relationships that depend on consistent answers. A bank inquiry about entity purpose may surface inconsistencies with information provided to a payment processor. Each gap makes the adjacent positions harder to defend.

These interconnections are rarely mapped upfront. Founders who address one gap often discover that it connects to others — and that addressing them requires a coherent narrative across all contexts, not just a fix in one.

The psychological weight also compounds. Founders who become aware of documentation gaps often find that the awareness creates persistent anxiety. The uncertainty about what might surface, when, and from which direction becomes a cognitive burden that affects decision-making capacity in unrelated areas.

The cost of mapping versus reconstructing

There is a consistent pattern in structural diagnostics: the cost of understanding the documentation landscape before an inquiry is a fraction of the cost of responding to an inquiry without that understanding.

This is not because mapping is cheaper in absolute terms. It is because mapping creates an organized, coherent picture of the structure — including its gaps — that the founder can act on deliberately. Reconstruction under pressure, by contrast, happens in compressed timelines, with incomplete information, and under the stress of an active inquiry.

---

Seeing what an examiner would see

The most valuable perspective shift for founders with cross-border structures is seeing their documentation through the eyes of someone who would examine it — not to find fault, but to understand what the evidence shows and where it falls silent.

Global Solo's Accountability dimension maps exactly this: what documentation exists, what would be expected, and where the gaps between them create structural exposure. Not as a compliance checklist, but as a clear picture of what the evidence trail actually looks like.

---

Visual: Founder View vs. Authority View

Key Takeaways

• Authorities assess evidence trails, not intentions; transaction records, travel patterns, and communication timestamps form a narrative independent of what the founder intended.
• Cross-border information sharing (CRS, bilateral treaties) means inconsistencies across jurisdictions may become visible when data from multiple institutions is compared.
• Retroactive documentation carries less weight than contemporaneous documentation; its existence may raise questions about why records were not created at the time.
• Documentation gaps cascade: a tax residency position lacking substance documentation interacts with banking relationships that depend on consistent answers.

References

• IRS Recordkeeping Requirements — What records the IRS expects businesses to maintain
• FinCEN Bank Secrecy Act — Anti-money laundering recordkeeping obligations

Check your risk profile →