Establishing secure connection…Loading editor…Preparing document…

Legal SAR and TC Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

LEGAL SAR AND TC AGREEMENT

This Agreement is made and entered into as of (the Effective Date) by and between , with principal place of business at (hereinafter "Provider"), and , with principal place of business at (hereinafter "Client").

RECITALS

WHEREAS, Provider operates compliance, monitoring and reporting systems designed to identify and report suspicious activity in accordance with applicable anti-money laundering and counter-terrorist financing laws and regulations; and

WHEREAS, Client conducts transactions and activities that may give rise to obligations to report suspicious activity and to implement transaction controls, and desires to establish formal procedures for the submission of Suspicious Activity Reports ("SARs") and the operation of Transaction Controls ("TCs"); and

WHEREAS, the parties wish to set forth their respective duties, reporting channels, confidentiality obligations and remedies with respect to SARs and TCs;

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. DEFINITIONS

1.1 "SAR" means a written or electronic report submitted by Client or Provider describing activity that the reporting party reasonably believes involves funds derived from illegal activity, attempts to disguise the nature, location, source or ownership of funds, or otherwise appears suspicious under applicable law.

1.2 "Transaction Controls" or "TCs" means the policies, procedures, transaction monitoring rules, authorization thresholds, holds, and escalation mechanisms implemented to prevent, detect or respond to suspicious transactions.

1.3 "Confidential Information" means information disclosed under this Agreement that is designated confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure.

2. REPORTING OBLIGATIONS

2.1 Client shall promptly report to Provider any suspected reportable activity that arises in Client's operations or that Client becomes aware of in the course of transactions subject to this Agreement. Reports shall be made in the form and by the channels set out in Schedule A and in Section 9 (Notices). Unless otherwise required by applicable law, Client shall submit a written SAR within calendar days of the initial determination that an activity is suspicious.

2.2 Provider shall have the right to require additional detail with respect to a SAR and Client shall cooperate fully and furnish all supporting documents, records and explanations reasonably requested by Provider in connection with the SAR.

2.3 Client shall maintain internal records of SARs and related documentation for a minimum of years or for the period required by applicable law, whichever is longer.

3. TRANSACTION CONTROLS

3.1 Provider and Client shall jointly establish and document TCs that set authorization thresholds, monitoring parameters, and hold procedures. TCs shall include a mechanism to impose immediate holds on transactions meeting specified risk indicators pending investigation.

3.2 Authorization thresholds shall be set as follows: transactions exceeding USD, or transactions meeting other risk criteria set forth in the parties' joint risk matrix, shall require secondary approval by the designated compliance officer.

3.3 The designated compliance officer for monitoring and escalation is: , Contact: .

4. DATA SHARING, PRIVACY AND CONFIDENTIALITY

4.1 Information exchanged under this Agreement that constitutes Confidential Information shall be used solely for the purposes of compliance with SAR and TC obligations and shall not be disclosed to any third party except as permitted by this Agreement or required by law.

4.2 Notwithstanding the foregoing, either party may disclose Confidential Information to governmental or regulatory authorities to the extent compelled by law, provided that the disclosing party, if legally permitted, provides prompt notice to the other party to enable a protective order or other remedy.

4.3 The parties shall implement reasonable technical and organizational measures to protect Confidential Information against unauthorized access, alteration, disclosure, or destruction, consistent with applicable data protection requirements.

5. COMPLIANCE WITH LAW

Each party represents and warrants that it will comply with all applicable anti-money laundering, counter-terrorist financing and sanctions laws and regulations in performing its obligations under this Agreement. Nothing in this Agreement authorizes either party to violate applicable law.

6. AUDIT, RECORDS AND RETENTION

Provider shall have the right, upon reasonable notice and during normal business hours, to audit Client's compliance with the obligations set forth in this Agreement. Client shall make available records, systems access and personnel reasonably necessary to conduct such audit. Any audit shall be conducted in a manner that minimizes disruption to Client's business.

7. INDEMNIFICATION

Client shall indemnify, defend and hold harmless Provider and its officers, directors and employees from and against any and all losses, claims, damages, liabilities and expenses, including reasonable attorneys' fees, arising out of Client's breach of this Agreement, Client's failure to report SARs where required, or Client's violation of applicable law.

8. LIMITATION OF LIABILITY

EXCEPT FOR LIABILITY FOR GROSS NEGLIGENCE, WILLFUL MISCONDUCT OR INDEMNIFICATION OBLIGATIONS ARISING UNDER SECTION 7, IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING LOSS OF PROFITS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

9. NOTICES

Provider Notice Contact

Client Notice Contact

10. AMENDMENTS; WAIVER

This Agreement may be amended only by a written instrument executed by duly authorized representatives of both parties. No waiver of any provision of this Agreement shall be effective unless in writing and signed by the party against whom enforcement is sought.

11. COUNTERPARTS; ELECTRONIC SIGNATURES

This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Signatures transmitted by electronic means shall be deemed original signatures for all purposes.

12. GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the state of , without regard to its conflict of laws principles.

13. ENTIRE AGREEMENT

This Agreement, together with any Schedules hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings, whether written or oral, relating thereto.

14. SEVERABILITY

If any provision of this Agreement is held to be invalid, illegal or unenforceable under applicable law, such provision shall be deemed modified to the minimum extent necessary to render it enforceable, and the remaining provisions shall continue in full force and effect.

15. TERM AND TERMINATION

15.1 This Agreement shall commence on the Effective Date and shall continue for an initial term of years, and shall automatically renew for successive one-year terms unless either party provides written notice of non-renewal at least days prior to the end of the then-current term.

15.2 Either party may terminate this Agreement for cause upon written notice if the other party materially breaches this Agreement and fails to cure such breach within days after receipt of written notice specifying the breach.

SCHEDULE A — REPORTING CHANNELS AND FORMATS

ENTITY TYPES

Provider Entity Type:

Client Entity Type:

MISCELLANEOUS PROVISIONS

Any costs incurred in responding to lawful requests from governmental authorities for SAR-related information shall be borne by the requesting party unless otherwise agreed in writing. The obligations of confidentiality set forth herein shall survive termination of this Agreement for a period of years.

Provider - Print Name:

Provider - Title:

Provider - By:

Provider - Date:

Client - Print Name:

Client - Title:

Client - By:

Client - Date:

Enter text✕

What the Legal SAR and TC Agreement Is and When It Applies

The Legal SAR and TC Agreement documents roles, responsibilities, and information sharing between parties involved in suspicious activity reporting (SAR) and transaction confirmations (TC). It clarifies who must prepare internal records, how transaction details are verified, and the process for escalating potential compliance concerns. The agreement is commonly used by financial institutions, legal counsel, and corporate compliance teams to align procedures for collecting transaction data, preserving audit evidence, and meeting regulatory reporting expectations while enabling enforceable electronic execution under U.S. e-signature law.

Why an Explicit SAR and TC Agreement Matters

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.

Why an Explicit SAR and TC Agreement Matters

Typical Users and Teams That Complete This Agreement

Teams that commonly complete this agreement include compliance, legal, and operations staff who manage transaction monitoring and reporting processes.

  • Compliance teams managing AML and suspicious activity workflows
  • Legal counsel advising on reporting obligations and dispute risks
  • Operations or treasury staff reconciling and confirming transaction details

Use the agreement as a shared reference for internal workflows, external counterparty confirmations, and evidentiary needs during audits or regulatory inquiries.

Who Signs on Behalf of the Organization

Chief Compliance Officer

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.

Outside Counsel

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.

Essential Fields and Data Elements

Reporting Party: Name of the entity submitting SAR
Subject Identity: Full legal name and identifiers
Transaction ID: Internal reference or trace number
Date of Activity: MM/DD/YYYY format
Narrative Summary: Concise description of suspicious facts
Authorizing Signer: Name, title, and contact info

Primary Risks and Consequences of Errors

Regulatory Fines: Civil penalties or enforcement actions
Criminal Exposure: Potential for willful violation charges
Delayed Reporting: Missed regulator timelines
Data Integrity Failures: Compromised audit evidence
Client Liability: Counterparty disputes and damages
Reputational Harm: Loss of stakeholder trust

Common Preparation Mistakes to Avoid

  • Incomplete identifiers: leaving out TINs, account numbers, or legal entity suffixes that impede matching and validation
  • Vague narratives: failing to summarize suspicious behavior clearly, causing reviewers to request clarifying follow-up
  • Incorrect dates or time zones: inconsistent timestamps that complicate timeline reconstruction for investigators
  • Mismatched signatories: signatures by persons without authority or without documented delegation create enforceability concerns

Step-by-Step: Completing the Agreement

Follow these sequential steps to prepare, review, and execute a compliant SAR and TC Agreement.

  • 01
    Assemble data: Collect transaction records, account details, and supporting documents
  • 02
    Draft summary: Write a clear narrative of suspicious indicators and transaction context
  • 03
    Assign reviewers: Route to compliance and legal for verification and redactions
  • 04
    Execute electronically: Secure signatures, timestamps, and preserve the audit trail

Where to File or Send the Agreement and Related Reports

Determine internal routing and the external filing destination before finalizing the agreement to ensure compliance with reporting obligations.

  • Internal repository: Store executed agreement in compliance document management
  • Regulatory filing: File SARs with the appropriate regulator as required
  • Counterparty delivery: Send transaction confirmation to the counterparty when appropriate
  • Legal hold: Apply holds when litigation or inquiry is reasonably anticipated

Key Components to Include in a Professional Agreement

A thorough SAR and TC Agreement should define roles, data scope, timing, confidentiality, recordkeeping, and signature procedures so each stakeholder understands obligations and evidence standards.

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.

Roles and Responsibilities

Define which department or individual prepares the report, who conducts reviews, and who authorizes submission to regulators or communications to counterparties.

Confidentiality Rules

State restrictions on disclosure, privilege handling, and redaction requirements to protect investigations and legal rights.

Record Retention

Outline retention periods for originals, working papers, and audio/video records, and identify the system of record for stored documents.

Verification Procedures

Describe how transaction details are confirmed, which documents support confirmations, and how discrepancies are resolved before filing.

Execution and Audit Trail

Require timestamps, signer attribution, and preserved audit logs for all electronic signatures and system actions tied to the agreement and filings.

How to Configure an Online Workflow

Set up a digital workflow that enforces the review sequence, captures required fields, and stores audit evidence automatically.

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

Technical Considerations for eSigning and Storage

Verify that the chosen platform meets encryption, retention, and audit requirements and can produce admissible records for internal and external review.

  • Authentication: Email, SMS, or stronger KBA
  • File formats: PDF, DOCX supported
  • Integrations: CRM, ERP, and cloud storage

Important Filing Deadlines and Timing Expectations

Timelines vary by filing obligation; align internal escalation with regulatory deadlines and common tax reporting schedules to reduce exposure.

W-9 requests:

Provide upon payer request; no fixed IRS deadline

1099-NEC:

Provide recipient and IRS by January 31

Form 1040:

Individual return due April 15 (Oct 15 with extension)

SAR considerations:

File per regulator timing; internal escalation should be immediate

Recordkeeping:

Retain supporting records per agency retention rules

Key Processing Milestones From Draft to Filing

Track these milestones to ensure timely review, authorization, and submission of SARs and transaction confirmations.

01

Data Collection

Gather transaction logs, account statements, and counterparty information

02

Internal Review

Compliance and legal assess suspicion and supporting evidence

03

Authorization

Designated officer signs and approves filing or confirmation

04

Submission & Archival

Submit to the regulator or counterparty and archive the executed record

Select eSignature Pricing and Feature Comparison

Comparison of common vendor starting prices and feature availability relevant to SAR and TC workflows. signNow is listed first per vendor ordering rules.

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

Frequently Asked Questions and Troubleshooting

Answers to common questions about validity, corrections, notarization, and secure storage for the Legal SAR and TC Agreement.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users