deepidv
All AI Prompts
FinTechTask Prompt

Compliance Prompt for Foreign Entity BOI Filing and CTA Exemption Audits

This **Luna** task prompt takes your corporate onboarding workflow and the **FinCEN August 2026 final rule** on **CTA exemptions**, then rewires **KYB** to the new scope. Luna, the deepidv compliance overseer, applies the **permanent domestic exemption** so U.S.-formed entities skip **BOI** collection while foreign reporting companies stay in scope, returns an entity-scoping matrix that routes each applicant to the right path, a KYB parsing configuration that verifies **foreign entity BOI disclosures** and maps **non-U.S. ultimate beneficial owners** in sub-150ms, a control map rated against the **Corporate Transparency Act**, and an audit trail spec for examination. Built for BSA officers and onboarding engineers at fintechs who must retire domestic BOI collection cleanly while tightening beneficial ownership verification on cross-border corporate customers.

Compliance Prompt for Foreign Entity BOI Filing and CTA Exemption Audits

How to use this prompt

  1. 1

    Open Luna in the deepidv dashboard and paste the full prompt, or run it in Claude, ChatGPT, or Gemini if you are drafting the onboarding update outside the platform.

  2. 2

    Replace the INPUT section with your corporate onboarding flow, the FinCEN final rule sections you are working from, the KYB and BOI checks each stage runs today, and your entity-type routing.

  3. 3

    Run the prompt and read the entity-scoping matrix first: it routes each applicant to exempt-domestic or in-scope-foreign before any BOI collection fires.

  4. 4

    Hand the KYB parsing configuration to your onboarding engineer and route the CTA control map to your BSA officer; start with any foreign-UBO path rated gap.

  5. 5

    Re-run the prompt when FinCEN issues further guidance and after each onboarding-flow change so the scoping and parsing rules stay aligned before your next examination.

The prompt

Luna, update our corporate onboarding workflows following FinCEN's August 2026 final rule establishing permanent domestic CTA exemptions. Configure automated KYB parsing rules to verify foreign entity BOI disclosures and map non-U.S. ultimate beneficial owners in sub-150ms parameters.

ROLE
You are Luna, the deepidv compliance overseer. You apply a final rule to a firm's corporate onboarding, re-scope who must file, and configure the KYB parsing that verifies the entities that remain in scope, all inside the firm's latency budget.

CONTEXT
The FinCEN August 2026 final rule establishes permanent domestic exemptions under the Corporate Transparency Act, so U.S.-formed reporting companies no longer file beneficial ownership information with FinCEN while foreign reporting companies registered to do business in the United States remain in scope. Onboarding must retire domestic BOI collection cleanly, keep risk-based KYB on domestic entities, and tighten verification on cross-border corporate customers, resolving each non-U.S. ultimate beneficial owner inside a sub-150ms budget.

INPUT, the user will paste:
- The corporate onboarding flow and the verification stages each entity type runs today
- The FinCEN final rule sections the firm is working from, with any effective date
- The KYB and BOI checks currently wired, and where in the flow they sit
- The entity-type routing and any parent-subsidiary rules the firm applies
- The latency budget for UBO resolution, and any open scoping questions the compliance team is tracking

TASKS
1. Scope each applicant type against the final rule, separating exempt domestic entities from in-scope foreign reporting companies.
2. Configure KYB parsing rules that verify foreign entity BOI disclosures and resolve each non-U.S. ultimate beneficial owner inside the sub-150ms budget.
3. Map the firm's onboarding controls against the Corporate Transparency Act obligations that remain and rate coverage.
4. Specify the audit trail retained per onboarded entity so a scoping decision can be defended at examination.

OUTPUT FORMAT, return the following structured response:

1. ENTITY-SCOPING MATRIX
- Each applicant type routed to exempt-domestic or in-scope-foreign, with the final-rule reference behind the call
- The classification signal that decides the route, and the fallback when it is ambiguous

2. KYB PARSING CONFIGURATION
- The parsing rule that verifies each foreign entity BOI disclosure and resolves the ownership chain to each non-U.S. ultimate beneficial owner
- The placement of the UBO resolution step against the sub-150ms budget, and the flag rule for an unresolvable chain

3. CTA CONTROL MAP
- Each remaining Corporate Transparency Act obligation, rated covered, partial, or gap, with the evidence
- The onboarding change that closes each gap

4. AUDIT-TRAIL SPEC
- The evidence bundle retained per onboarded entity, including the scoping decision and its rule reference
- The escalation and enhanced due-diligence routing when a foreign UBO cannot be resolved

Cite the final-rule section references where you can. Where the onboarding input or the rule text is insufficient to settle an entity's scope, flag it as an open question instead of guessing.

Test it in Claude or another LLM

This prompt is built for the Luna agent inside deepidv, where Luna updates a firm's live corporate onboarding to the FinCEN August 2026 final rule and configures KYB parsing that verifies foreign entity BOI disclosures. You can dry-run the same workflow in any general LLM first with synthetic onboarding and rule data to see the scoping-matrix shape before pointing it at real systems.

  1. 1

    Paste the full prompt into Claude, ChatGPT, or Gemini, but replace the opening 'Luna,' with a role instruction such as 'Act as a KYB and AML compliance architect updating corporate onboarding to the FinCEN CTA final rule and configuring foreign-entity BOI parsing.' Keep the four OUTPUT sections exactly as written.

  2. 2

    Under the INPUT section, paste the synthetic sample block below so the model has an onboarding flow, the final-rule references, and current KYB checks to update.

  3. 3

    Add one framing line: 'This is synthetic test data. Where an entity's scope cannot be settled from the input, flag it as an open question instead of guessing, and never claim coverage the input does not support.'

  4. 4

    Check the output shape: an entity-scoping matrix routing exempt-domestic versus in-scope-foreign, a KYB parsing configuration that maps non-U.S. UBOs in sub-150ms, a CTA control map with covered/partial/gap ratings, and an audit-trail spec. If any section invents an entity the input does not list, tighten the role line and re-run.

  5. 5

    Once the output shape is right, run it live in the deepidv dashboard where Luna updates your real onboarding workflow and configures the KYB parsing rules.

Synthetic sample data to paste alongside the prompt

Fake test data, safe to share with any LLM. Swap in your own once the output looks right.

CORPORATE ONBOARDING FLOW (synthetic, fake):
- Stages: applicant intake, entity-type classify, BOI collection, UBO resolution, sanctions screen, approve
- Applicant sample (fake): 2 U.S. LLCs (refs ENT-TEST-01/02), 1 UAE free-zone company (ENT-TEST-03), 1 Cayman holding co (ENT-TEST-04)
FINCEN FINAL RULE (fake): permanent domestic CTA exemption, ref FINCEN-CTA-TEST-2026-08; foreign reporting company scope retained, ref FINCEN-CTA-TEST-2026-08B
CURRENT KYB CHECKS (fake): BOI collected from all entities; UBO resolved via registry pull; OFAC screen on named owners; no foreign-registry parsing
LATENCY BUDGET (fake): UBO parse hard cap 150ms; intake soft cap 1800ms; peak 400 onboards/hour
OPEN ITEM (fake): whether a domestic subsidiary of a foreign parent inherits foreign scope, fake ref SCOPE-TEST-XX

FAQ

What changed under the FinCEN August 2026 final rule?

The final rule establishes permanent domestic exemptions under the Corporate Transparency Act, so U.S.-formed reporting companies no longer file beneficial ownership information with FinCEN while foreign reporting companies registered to do business in the United States stay in scope. For onboarding that means retiring domestic BOI collection and tightening verification on cross-border corporate customers. This prompt rewires KYB to the new scope.

How does Luna verify a foreign entity BOI disclosure?

Luna parses the foreign reporting company's filing, resolves the ownership chain to each non-U.S. ultimate beneficial owner, and checks the disclosed owners against the entity's registry and sanctions data inside a sub-150ms budget. The parsing configuration flags a chain that cannot be resolved to a natural-person owner rather than passing an opaque structure through.

Does dropping domestic BOI collection reduce KYB rigor?

No. The exemption narrows who must file with FinCEN, not the firm's obligation to know its business customers. Luna keeps risk-based KYB on domestic entities and shifts collection effort toward the foreign reporting companies that remain in scope, so onboarding follows the final rule without loosening beneficial ownership diligence where it still matters.

Can I use this prompt outside the deepidv dashboard?

Yes. The structure works in Claude, ChatGPT, or Gemini as a KYB scoping framework and returns the entity-scoping matrix, parsing configuration, control map, and audit-trail spec. Live KYB parsing and UBO resolution against your real onboarding data only run inside the deepidv dashboard through Luna.

Run it with live verification data

These prompts work in any LLM. Inside the deepidv dashboard, Luna, Arbiter, and Arc run them against your real sessions, screening lists, and audit trails.

Book a Demo