Request demo

KYC checks completed. Complex cases ready for review.

Across brings documents, identity checks, screening, and risk context together. Routine work runs within your bank’s controls; analysts receive a complete file for the decisions that need judgment.

Request a demo

Automated workflow

  1. System event

    Alert TM-20418 arrives. Check the cash deposits against the customer’s KYC profile and linked records.

  2. Across

    Checked: Documents and identity · Screening and risk context · Bank policy.

    Escalate for SAR review

  3. Sample alert · TM-20418

    Alert stays open
    • Nine cash deposits in 12 days Transaction monitoring · three branches $86,250
    • Expected cash activity KYC profile · consulting firm None
    • Account at the same address Core banking · mailing address 1 linked

    Your BSA officer decides whether to file.

    Narrative drafted for your BSA officer.

    1. T-07 Cash split across days and branches: escalate AML policy, §4.2
    2. K-03 Activity outside the expected profile: L2 review CDD procedures, p. 9
    3. S-01 Escalated alerts: draft the narrative for BSA officer approval BSA officer interview 1

Today the analyst spends hours tracing the customer story.

Identity documents, screening results, account data, and previous reviews live in separate systems. Important context can stay hidden while an analyst checks each source by hand.

01

Scattered evidence

Customer information arrives from documents, core banking, KYC, and screening tools.

02

Missing risk context

A screening result means little without the customer profile and the bank’s policy.

03

Repeated manual work

Analysts collect the same records again to explain a review or reconstruct it for an audit.

01 One customer. Four places to look.
DocumentsIdentity and business records
Core bankingAccount activity and relationships
KYC profileExpected activity and prior reviews
ScreeningMatches and screening results
The analyst traces the connections
02 Connect screening to the customer profile and policy03 Repeat the checks for review and audit
Manual review

Across connects context across systems and provides one customer view.

Across automates the background checks and assembles the evidence. Each conclusion links to its source, and regulated steps follow the bank’s fixed controls.

Customer 55102

Ready for analyst review

Activity, profile, and prior reviews in one customer view.

Expected cash
NoneKYC
Cash deposits, 12 days
$86,250Transaction monitoring
Watch lists
ClearScreening
Linked accounts
1, same addressCore banking
Prior alerts
1, same patternCase management
Escalate for SAR review

Your BSA officer decides whether to file.

Built from how you review.

Much of your review judgment lives with your analysts and BSA officer, not in your written procedures. The Architect reads your policies and past dispositions, then asks your team about the gaps.

  1. Policies, procedures, past dispositions, and answers from your analysts and BSA officer.

    • AML policy
    • CDD and EDD procedures
    • SAR procedures
    • Analyst and BSA officer interviews
    • Architect asks:Draft the narrative before you decide to file? BSA officer answers:Yes, draft it for my approval.

  2. The Architect drafts plain-language rules from those sources. Your compliance lead reviews them.

    • T-07 AML policy, §4.2 Cash split across days and branches: escalate
    • K-03 CDD procedures, p. 9 Activity outside the expected profile: L2 review
    • S-01 BSA officer interview 1 Escalated alerts: draft the narrative for BSA officer approval
    • E-02 EDD procedures High-risk customers: refresh EDD every 12 months

  3. A versioned graph with fixed rules for regulated steps, and judgment only where an analyst would use it.

    • Check Transaction pattern · Expected activity · Screening result
    • Draft L1 disposition · SAR narrative · Lineage
    • Review Analyst confirms · BSA officer approves · Logged decision

  4. The Operator catches policy changes. Past cases re-run before your team approves the change.

    • Cash split across branches Escalated
    • Payroll deposits, known employer Closed with reason
    • Watch-list name match, different birth date Closed with reason
    • T-07: escalate at was 3 branches, now 2 branches Alert TM-0391 now escalates ·Awaiting compliance approval

How we’ll measure the pilot.

Targets we agree with you before the build, scored on synthetic cases your analysts review.

Time from a new onboarding case to a CDD file ready for review, against your current baseline.

Every close, escalation, and SAR draft links each fact to the system and record behind it.

Apply a real policy change and re-run the pilot cases without engineering work.

Questions to askCheck the answer against your own cases

Questions to ask any compliance AI.

  1. Which steps are fixed, and which use judgment?

    Why it matters: Regulated steps have to run the same way every time.

    Across: Regulated steps run as fixed rules. Judgment is used only where an analyst would use it.

  2. Can you trace every fact to its source?

    Why it matters: Examiners ask for the path from source to disposition.

    Across: Every fact in a disposition links to the system and record behind it.

  3. Why it matters: A conclusion built on missing data stays wrong until someone notices.

    Across: Across winds the record back to that date and rebuilds the conclusions it affects.

    • Core banking address feed: 9 days late
    • May alert TM-0412: closed to re-review
    • Rebuilt from May 14 , awaiting analyst

  4. Who makes the final call?

    Why it matters: A decision to file belongs to your BSA officer.

    Across: Across drafts the narrative and the evidence. A person approves before anything is filed.

Start with your hardest alerts.

A three-week pilot on synthetic data, scoped to one workflow: KYC onboarding, alert triage, or SAR drafting.

  1. Week 1
    • Policies and procedures
    • Representative cases, as synthetic data
    • Recorded analyst interviews
  2. Week 2
    • Writes the rulebook in plain language
    • Your compliance lead reviews it
    • Maps each system’s fields to one record
  3. Week 3
    • Tested on held-out synthetic cases
    • Your analysts review each disposition
    • Results against the agreed targets
  4. Your decision

    Use the results to decide whether to connect your core, KYC, monitoring, and case management systems.

What we need to start.

  • AML policy Alert rules, thresholds, and escalation
  • CDD and EDD procedures Risk ratings and expected activity
  • SAR procedures Narrative standards and approvals
  • Field lists For core, KYC, monitoring, screening, and cases
  • Representative cases As synthetic data, with your team’s decisions
  • Recorded interviews With an analyst and your BSA officer
How it connectsPermissions, approvals, and your systems of record

Across runs where the work happens.

Your systems trigger the process and remain the source of truth. Across returns the result to the operational workflow, with a review package when a person needs to decide. The integration and review interface are configured for your use case and existing systems.

Work arrives

New onboarding case or updated customer record

  • Core banking
  • KYC and screening
  • Transaction monitoring
  • Case management

Across

Context.
Rules.
Decision.

Sources attached

Routine work

Complete eligible routine checks, within the configured controls.

Ready for review

Review-ready customer file, with the reasoning and evidence ready.

across / new run start here

Let us help you get work done.

Request a demo See customer stories