Establishing secure connection…Loading editor…Preparing document…

Treasury Authorization Form

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

Treasury Collateral Management and Monitoring (TCMM) Agency Authorization Form

Last Updated 09/11

Section 1 – General Information

Create Security Account

Delete Security Account

Add New User(s)

Delete User

Section 2 – Agency Information

Security Account:

Name of Agency:

Name of Bureau:

Address:

City: State: Zip code:

Circle One (will be verified by another agency authorized individual)

Section 3 – User Profile(s)

The individuals listed below are collateral contacts under the terms of Title 31 of the Code of Federal Regulations Part 202 or Part 225 and are authorized agency users of TCMM. Each user must have a unique and valid e-mail address.

Name
Title
E-mail Address (not shared)
(Area Code) Phone #

Section 4 – Agency Official Authorization

By signing below the Agency Official certifies that he/she is duly authorized by the Agency to designate individuals who can manage collateral accounts and serve as user(s) of TCMM.

Name (print)

Signature

Title (required)

Phone

Date

E-mail Address

Fax

Please mail or fax the completed form to the TCMM Treasury Support Center

Mailing Address:

TCMM Treasury Support Center

Federal Reserve Bank of St. Louis

P.O. Box 442

St. Louis, MO 63166

Fax:

866-707-6574

Overnight Address:

TCMM Treasury Support Center

Federal Reserve Bank of St. Louis

1421 Dr. Martin Luther King Drive

St. Louis, MO 63106-3716

Internal Use Only

Date/Time Confirmed with Authorizer:
Initials:
Date/Time Verified Authority and Title:
Initials:
Date Entered:
Initials:
Date Entry Verified:
Initials:

General Notices

To access TCMM, Users may be issued authentication credentials such as a username and password. We (the United States Department of the Treasury and its designated agents) may rely upon the authentication credentials alone to provide access to TCMM. We may act upon on any electronic message that we establish to be associated with a known set of authentication credentials as if the message consisted of a written instruction bearing the ink signature of one of the Agency’s duly authorized officials. An Agency accepts sole responsibility for and the entire risk arising from the use of authentication credentials by its Users.

All Users must agree to terms and conditions governing access to TCMM. These terms and conditions can be found on the Web site(s) of the application(s) providing TCMM. These terms and conditions include provisions requiring Users to maintain the confidentiality of their authentication credentials, to report the possible theft or compromise of their authentication credentials, and to take action whenever they no longer require access or require access to a lesser extent than is currently the case. These terms and conditions are subject to change from time to time. We may have Users “click-thru” these terms and conditions before first use, on a periodic basis, or whenever they change, to reflect their continued agreement to these terms and conditions.

We will not be liable for any loss or damage resulting from a problem beyond our reasonable control. This includes, but is not limited to, loss or damage resulting from any delay, error or omission in the transmission of any electronic information, alteration of any electronic information, any third party's interception or use of any electronic information, a failure of services provided by an Internet service provider, and malicious activity received from or introduced by a third party. Additionally, we are not liable for loss or damage resulting from acts of war, acts of terrorism, acts of God or acts of nature.

Except as otherwise required by law, in no event will we be liable for any damages other than actual damages arising in connection with TCMM services, including without limitation indirect, special, incidental or consequential damages.

Except as otherwise required by law, WE DO NOT MAKE ANY WARRANTIES, EXPRESS OR IMPLIED (INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE), WITH RESPECT TO ANY SOFTWARE, INFORMATION, SERVICE, OR OTHER ITEM PROVIDED BY, LOCATED ON, DERIVED FROM, ASSOCIATED WITH, REFERRED TO BY, OR LINKED TO BY TCMM SERVICES. EVERYTHING IS PROVIDED "AS IS."

Privacy Act Statement

We are authorized to request the information on this form by 31 U.S.C. §§ 321, 323, and 3301, 3302, 3303, and 3304. We need this personal information to help authenticate and determine who is responsible for viewing potentially sensitive information or engaging in a transaction. Furnishing this information is voluntary but an Agency will not have access to TCMM services, unless the information is furnished.

From systems including those used to provide TCMM services, the parties to whom we disclose information may include:

• Appropriate Federal, state, local or foreign agencies responsible for investigating or prosecuting the violation of, or for enforcing or implementing, a statute, rule, regulation, order, or license, but only if the investigation, prosecution, enforcement or implementation concerns a transaction(s) or other event(s) that involved (or contemplates involvement of), in whole or part, an electronic method of collecting revenues for the Federal government. The records and information may also be disclosed to commercial database vendors to the extent necessary to obtain information pertinent to such an investigation, prosecution, enforcement or implementation.

• Commercial database vendors for the purposes of authenticating the identity of individuals who electronically authorize payments to the Federal Government, to obtain information on such individuals' payment or check writing history, and for administrative purposes, such as resolving a question about a transaction.

• A court, magistrate, or administrative tribunal, in the course of presenting evidence, including disclosures to opposing counsel or witnesses, for the purpose of civil discovery, litigation, or settlement negotiations or in response to a subpoena, where relevant or potentially relevant to a proceeding, or in connection with criminal law proceedings.

• A congressional office in response to an inquiry made at the request of the individual to whom the record pertains.

• Fiscal agents, financial agents, financial institutions, and contractors for the purpose of performing financial management services, including, but not limited to, processing payments, investigating and rectifying possible erroneous reporting information, creating and reviewing statistics to improve the quality of services provided, or conducting debt collection services.

• Federal agencies, their agents and contractors for the purposes of facilitating the collection of revenues, the accounting of such revenues, and the implementation of programs related to the revenues being collected.

• Federal agencies, their agents and contractors, to credit bureaus, and to employers of individuals who owe delinquent debt only when the debt arises from the unauthorized use of electronic payment methods. The information will be used for the purpose of collecting such debt through offset, administrative wage garnishment, referral to private collection agencies, litigation, reporting the debt to credit bureaus, or for any other authorized debt collection purpose.

• Financial institutions, including banks and credit unions, and credit card companies for the purpose of revenue collections and/or investigating the accuracy of information required to complete transactions using electronic methods and for administrative purposes, such as resolving questions about a transaction.

• Appropriate agencies, entities, and persons when (1) the Department suspects or has confirmed that the security or confidentiality of information in the system of records has been compromised; (2) the Department has determined that as a result of the suspected or confirmed compromise there is a risk of harm to economic or property interests, identity theft or fraud, or harm to the security or integrity of this system or other systems or programs (whether maintained by the Department or another agency or entity) that rely upon the compromised information; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with the Department’s efforts to respond to the suspected or confirmed compromise and prevent, minimize, or remedy such harm.

Enter text✕

What the Treasury Authorization Form Is and When it’s Used

A Treasury Authorization Form is a formal written or electronic document that grants authority to an individual or role to initiate, approve, or manage treasury actions such as wire transfers, ACH payments, account access, check issuance, or investment instructions. Organizations use it to document delegated authority, specify transaction limits and permitted account numbers, and require identity and verification controls. The form protects the organization by creating an auditable record of who may act on behalf of the treasury, under what conditions, and for which accounts or transaction types.

Why a Clear Treasury Authorization Form Matters

A precise authorization form reduces operational risk, clarifies internal controls, and provides evidence for banks and auditors that signature authority was properly granted.

Why a Clear Treasury Authorization Form Matters

Who Typically Completes and Signs This Form

The Treasury Authorization Form is completed by finance teams, corporate secretaries, or HR when assigning treasury roles and by business owners when delegating authority.

  • Chief Financial Officer or Treasurer — authorizes high-level account and payment permissions for executives and treasury staff.
  • Controller or Finance Manager — documents routine payment signers, daily limits, and reconciliation responsibilities.
  • Bank Relationship Officer or Compliance Officer — verifies signers, accepts the form for bank onboarding or changes.

Banks, auditors, and internal stakeholders rely on this written authorization to validate actions and trace approved payment flows.

Core Elements of a Professional Treasury Authorization Form

A professional form is clear about scope, identity, transaction limits, and authentication. It should support auditability, be compatible with electronic signing, and include revocation terms.

Authorization Scope

Specify exactly which accounts, payment types (ACH, wire, checks), and transaction thresholds the signer may approve, including single-transaction and aggregate limits for clarity and control.

Designated Signers

List full legal names, titles, and unique identifiers for each authorized person, plus the order of approvals and any required dual-signature conditions to prevent unilateral high-value transactions.

Bank Details

Include bank name, ABA routing number, account number, and account type. For multiple accounts, attach a schedule that the bank can reference when processing instructions.

Authentication Methods

Describe required authentication such as in-person notarization, two-factor confirmation, bank-hosted verification, or RON; detail acceptable ID documents and verification steps.

Effective and Expiration Dates

State the effective date and any expiration or review date. Tie authority to corporate resolutions or board minutes when applicable to prevent stale permissions.

Revocation and Amendments

Include processes for revocation, notice to banks, and procedures for amending signers or limits; require written confirmations and specify how quickly banks must act on revocations.

Required Security and Compliance Details

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit Trail: Tamper-evident logs with timestamps
Authentication: Multi-factor or bank verification
Regulatory Fit: ESIGN and UETA compliant
Healthcare Data: HIPAA compliant (BAA required)
Records Standard: 21 CFR Part 11 available as needed

Step-by-Step: Completing and Submitting the Form

Follow these sequential steps to prepare, verify, and deliver the Treasury Authorization Form to the receiving bank or internal governance body.

  • 01
    Prepare Document: Populate all fields and attach supporting corporate resolutions.
  • 02
    Verify Identities: Collect IDs and run bank-required identity checks.
  • 03
    Obtain Signatures: Have authorized signers sign in correct order and date.
  • 04
    Submit to Bank: Deliver via bank portal, secure email, or in-person with required notarization.

How to Configure an Online Workflow for the Form

Configure an electronic workflow to route the form, enforce signer order, and capture an audit trail for compliance and bank acceptance.

Field Configuration
Authorization Type Define ACH, wire, checks, or full account access
Signers & Order Set signer sequence and conditional co-sign rules
Authentication Enable SMS code, KBA, or bank identity checks
Attachments Attach board resolution, ID, and recent bank statement

Where to Send or File the Completed Form

Select the receiving channel that the bank or internal policy requires. Retain copies and the audit record after submission.

  • Bank Upload: Use the bank’s secure portal for fastest processing and acceptance
  • In-Person Delivery: Bring original with ID and notarization if required by bank
  • Secure Email: Deliver encrypted PDF only when accepted by the bank
  • Internal Records: File a signed copy with treasury and corporate secretary

Digital Signing and Platform Considerations

Use a platform that supports secure e-signing, audit trails, and the authentication levels required by your bank and compliance teams.

  • File Formats: PDF, DOCX, and secure HTML supported
  • Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
  • Compliance: ESIGN, UETA, SOC 2, HIPAA (BAA)

Typical Timelines and Processing Expectations

Timelines depend on the bank’s onboarding process, notarization, and whether additional verification is required. Allow extra time for high-value authority changes.

Internal Approval:

2–10 business days depending on board or executive scheduling

Bank Processing:

1–5 business days after bank receipt and verification

Notarization Lead Time:

Same‑day to 3 business days depending on availability

Remote Notarization:

RON sessions may add 1–3 days for identity proofing and recording

Revocation Notice Period:

Banks typically act on revocation within 1–3 business days after notice

Common Mistakes That Cause Delays

  • Using informal titles or nicknames instead of the signer’s exact legal name, creating bank rejections or additional verification requests.
  • Omitting supporting corporate resolution or proof of authority, which many banks require before accepting new signatories.
  • Entering incorrect account or routing numbers, resulting in failed or misdirected transfers and possible recovery costs.
  • Failing to specify transaction limits or co-sign requirements, allowing ambiguous interpretation and potential internal disputes.

Risks and Potential Consequences of Errors

Unauthorized Transfers: Financial loss risk
Bank Rejection: Operations delayed
Audit Findings: Regulatory scrutiny
Compliance Violations: Contractual breach risk
Reputational Harm: Stakeholder confidence reduced
Recovery Costs: Time and legal expense

eSignature Vendor Pricing Snapshot for Treasury Forms

Compare common eSignature providers on starting price, trial availability, bulk send, audit capability, HIPAA support, and envelope limits to inform platform selection.

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 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/yr Varies Varies Varies

Practical Examples of Common Use Cases

These examples show how organizations use a Treasury Authorization Form to align banking operations with internal controls and compliance.

Corporate Treasury Update

A mid-sized company updated signatory limits after a board resolution to reduce fraud exposure by adding two signers.

  • Dual-signature requirement added for transfers above $50,000.
  • The bank accepted the revised form after receiving the board minutes and two signed authorization pages with notarization.

New Account Onboarding

A nonprofit opened a new operating account and designated three authorized signers to separate duties.

  • One signer for deposits, two required for disbursements.
  • The organization uploaded the form and supporting resolution to the bank portal, enabling immediate online access and ACH setup.

Frequently Asked Questions and Practical Answers

Answers to common questions about legality, notarization, and eSigning for Treasury Authorization Forms to help avoid delays and compliance issues.


Need help? Contact support

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