Scope of Reporting
Specify the types of transactions and thresholds covered, including the data elements that must be collected for each SAR and the circumstances that trigger a TC.
A written agreement reduces ambiguity about reporting obligations, documents record retention requirements, and creates a clear audit trail for later review. It supports timely escalation, protects institutions from regulatory exposure, and establishes who is responsible for transaction confirmation and SAR submissions under internal policy and applicable law.
Teams that commonly complete this agreement include compliance, legal, and operations staff who manage transaction monitoring and reporting processes.
Use the agreement as a shared reference for internal workflows, external counterparty confirmations, and evidentiary needs during audits or regulatory inquiries.
The CCO typically signs to accept responsibility for SAR-related processes and attest that internal controls are in place. That signer confirms escalation pathways, retention policies, and the accuracy of information used for filing.
A firm or in-house counsel may sign to confirm that legal review occurred, to document privileged communication expectations, and to establish responsibilities for handling privileged material during SAR investigations.
Specify the types of transactions and thresholds covered, including the data elements that must be collected for each SAR and the circumstances that trigger a TC.
Define which department or individual prepares the report, who conducts reviews, and who authorizes submission to regulators or communications to counterparties.
State restrictions on disclosure, privilege handling, and redaction requirements to protect investigations and legal rights.
Outline retention periods for originals, working papers, and audio/video records, and identify the system of record for stored documents.
Describe how transaction details are confirmed, which documents support confirmations, and how discrepancies are resolved before filing.
Require timestamps, signer attribution, and preserved audit logs for all electronic signatures and system actions tied to the agreement and filings.
| Field | Configuration |
|---|---|
| Routing | Sequential approval by compliance then legal |
| Authentication | Email or SMS code with optional KBA |
| Attachments | Require supporting documents before submit |
| Retention | Auto-archive executed files to secure repository |
Verify that the chosen platform meets encryption, retention, and audit requirements and can produce admissible records for internal and external review.
Provide upon payer request; no fixed IRS deadline
Provide recipient and IRS by January 31
Individual return due April 15 (Oct 15 with extension)
File per regulator timing; internal escalation should be immediate
Retain supporting records per agency retention rules
Gather transaction logs, account statements, and counterparty information
Compliance and legal assess suspicion and supporting evidence
Designated officer signs and approves filing or confirmation
Submit to the regulator or counterparty and archive the executed record
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | Yes, 7-day | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |