Customer-to-transaction linkage checker

What does the customer-to-transaction linkage checker produce?

Link every supplied transaction to an exact customer-master ID. Identify orphan transactions, ambiguous customer matches, duplicate transaction IDs, invalid source facts and transactions outside recorded customer dates.

The working area above runs the supported validator in the browser. It keeps the result inspectable and preserves every unresolved item for responsible review.

What do you need before you start?

• A named owner has defined the task and the organization’s intended use.
• The customer has authority to use every supplied record, source or connection.
• Prepare the result in this browser and resolve visible input errors before exporting.

What information do you enter?

Prepare only the bounded inputs listed below for this validator.

• Frozen review date (required). Exact YYYY-MM-DD date from 1900 through 2200. Transactions and recorded customer dates cannot be after this date.
• Approved population and customer-master reference (required). Identify the transaction period, customer-master version, scope and responsible reviewer. The tool does not query live customer systems.
• The local dataset or structured record to inspect.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Complete fictional pack (ZIP). Fictional source data (JSON). Samples require tailoring. The fictional ZIP contains the same four CSV outputs as the customer pack. PDF and DOCX are not included in this tool's paid output.

How does the customer-to-transaction linkage checker work?

1. 1
   Define the scope

   Choose the exact customer-to-transaction linkage checker task, responsible owner and intended use.

2. 2
   Add supported inputs

   Provide only the information listed for the validator. Unsupported material must remain unresolved.

3. 3
   Inspect the result

   Review the result, assumptions, source basis and exceptions before relying on any output.

4. 4
   Approve or export

   A responsible person decides whether the record is complete enough for the organization’s next step.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• BSA/AML Examination ManualThe interagency examination baseline for bank BSA and AML programs. Risk assessment, customer due diligence, monitoring and reporting.Federal Financial Institutions Examination Council. Reviewed 2026-09-24.
• Statutes, regulations and guidanceThe official federal source index for current FinCEN guidance. Bank Secrecy Act and anti-money laundering guidance.Financial Crimes Enforcement Network. Reviewed 2026-09-24.
• Filing InformationThe official filing reference for BSA report preparation and data checks. BSA forms, electronic filing and current filing resources.Financial Crimes Enforcement Network. Reviewed 2026-09-24.

Common questions

What still needs review?

Confirm inputs and rules. Review exceptions and approve consequential actions.

This browser workspace does not provide legal advice, certify compliance, make a filing or authenticate a customer decision.

Unsupported cases must stop or remain visibly unresolved.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all financial crime and sanctions tools.

• Transaction feed schema validatorCheck fields, formats and permitted values. Try a free example, then review your inputs and the result. No account or payment required.
• Transaction completeness reconcilerCompare source-system totals with monitoring inputs. Try a free example, then review your inputs and the result. No account or payment required.
• Duplicate transaction detectorIdentify repeated records and ingestion errors. Try a free example, then review your inputs and the result. No account or payment required.
• Currency and timestamp normalizerPreserve original values alongside normalized working values. Try a free example. Review your inputs and result. No account or payment required.
• Monitoring scenario registerVersion purpose, parameters, ownership and testing. Try a free example, then review your inputs and the result. No account or payment required.