Treasury and ACH origination onboarding

How do we onboard a business to ACH origination, wires and positive pay with the agreements, limits, credit approval and user setup in one case?

Run treasury onboarding as one case that ends with services live. Callvu prefills the business from the core, collects the service agreements and the authorized users from the customer, classifies the exposure the services create, routes the credit approval of the ACH and wire limits in the Decision Desk, runs the Nacha originator due diligence, sets up the users and entitlements under dual control, and enables each service in the treasury platform with the agreement and the limits on the record.

In scopeComplex: multi-party handoffsCallvu moves: prefill, chase and verify, classify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The business signed six agreements by email, the limit was approved in a reply, and the users were set up by phone.

Today, without Callvu

A business wants to run payroll by ACH, send wires and use positive pay. Treasury sales emails the agreements. Credit approves an exposure limit in an email thread. Operations sets up the online banking users from a phone call and enables services one at a time as the paperwork arrives. Weeks later the business is live with a limit nobody can find and a user who was never authorized by a signer.

ACH origination makes the bank an ODFI with obligations under the Nacha rules: an agreement with the originator, due diligence on its creditworthiness and its purpose, exposure limits monitored across settlement, and the originator's own obligations passed down. Wire origination needs the security procedure agreement under Article 4A. Each needs a signer's authorization, and the users who will act need entitlements set by someone authorized.

Onboarding is where the bank's risk on the relationship is decided, and it is usually decided in email.

How it runs

From the requestto the system of record.

A business asks for treasury services through treasury sales, a relationship manager, or online. Callvu identifies the business and opens the onboarding case with the services requested.

Business customer: An authorized signer accepts the agreements, names the users and their roles, and provides what due diligence requires.
Treasury sales: Starts the case, sees its status, and does not set limits or users.
Credit: Approves the ACH and wire exposure limits in the Decision Desk.
Treasury operations: Completes the setup from the approved case under dual control.
Callvu: Prefills, collects agreements and users, classifies exposure, routes approvals, runs due diligence, sets up and enables.

Prefill and classify
The business, its accounts, signers, beneficial owners and risk rating are prefilled from the core and the BSA system. The services requested (ACH origination by type, wires, positive pay, remote deposit) and the expected volumes classify the exposure and the due diligence required.
Chase and verify agreements and users
The master treasury agreement and each service schedule, with the security procedures, are delivered to the authorized signer and accepted on a process-controlled screen. The signer names the users, their roles and their limits; each user is identified and enrolled through their own link. The originator due diligence items (the nature of the ACH activity, the SEC codes, the originator's own policies where required) are collected.
Decide the limits
The ACH exposure limit (daily and multi-day settlement exposure by entry type) and the wire limit go to credit in the Decision Desk with the financials, the relationship and the exposure classification, and only the allowed outcomes: approve, approve a lower limit, approve with collateral or prefunding, or decline.
Set up and enable
Treasury operations completes the setup under dual control from the approved case: the users and entitlements, the limits, the security procedures (tokens, dual approval thresholds), the positive pay accounts and the ACH company IDs. Each service is enabled in the treasury platform with the agreement and the limits attached, and the business is told what is live.

Where it ends: The services are live with signed agreements, approved limits, due diligence and authorized users on the record, set up under dual control from one case. The Decision Trace shows the classification and the approvals; the Audit Trace shows every acceptance, decision and setup step. The Callvu moves in this process are prefill, chase and verify, classify, decide and write back.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

Nacha rules for ODFIs and originators (Nacha Operating Rules, Article Two): An ODFI must have an agreement with each originator binding it to the rules, perform due diligence on the originator, establish and monitor exposure limits across the originator's entries, and ensure the originator's authorization practices meet the rules; the ODFI warrants each entry it originates.
UCC Article 4A security procedures (UCC 4A-201 and 4A-202): The bank and the customer agree a commercially reasonable security procedure for verifying payment orders; the agreement sets the procedure, and the bank's liability for unauthorized orders depends on following it.
Bank Secrecy Act customer due diligence for higher-risk services (31 CFR 1020.210): ACH origination, wires and merchant-type activity raise the customer's risk profile; the services, expected activity and originator type are recorded in the BSA system.
Interagency guidance on authentication for business customers (FFIEC, 2021): Business online banking with payment capabilities requires layered authentication and controls such as dual approval and limits; the user setup applies them.

Company policies

No service is enabled before the signer accepts the agreement and credit approves the limits.
Users and entitlements are named by an authorized signer and set up under dual control.
Originator due diligence and the exposure limit are the bank's ACH policy under the Nacha rules.
The treasury platform and the core are the systems of record; the agreements and approvals are attached.

Controls

Prefill from the core and the BSA system.
Exposure classification by service and volume.
Agreement acceptance by an authorized signer on a process-controlled screen.
User identification and enrollment through individual links.
Decision Desk credit approval of limits.
Dual-control setup with entitlements and security procedures.
Service enablement with the record attached.

Clocks and deadlines

Credit decision: The approver is nudged on the policy's schedule; sales sees the status.
Limit review: Reviewed on the policy's cycle from enablement, as its own process.

Documents and checks

The master agreement and service schedules as accepted, with the signer
The user list with roles, limits and enrollment records
The originator due diligence items
The credit decision on limits
The setup record and the enablement confirmation

In the Decision Trace

The services, volumes and the exposure classification.
The credit decision, the approver and the reason.
The security procedures and entitlements set.
The dual-control record of the setup.

In the Audit Trace

Each acceptance and enrollment with time.
The Decision Desk step.
Each setup action and the second person.
The enablement.

The handoff

Between the front doorand the back office.

The front door

Treasury sales, the relationship manager or online; the signer and each user act on their own screens.

The back office

Credit approves limits in the Decision Desk; operations sets up under dual control from the approved case; nothing is enabled from an email.

The Decision Desk

The ACH and wire limits go to credit in the Decision Desk with the financials and the exposure classification, and only the allowed outcomes.
The dual-control setup requires a second operations person's confirmation on the case.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Banca Transilvania automated more than 100 workflows with Callvu.

BNK-04

Bank Leumi digitized all loan application and servicing workflows within six months, and dozens more processes since.

BNK-01

Questions

What buyers ask next,answered plainly.

Who sets the ACH exposure limit?

Credit, in the Decision Desk, with the financials and the exposure classification. The limit is on the record with the approver.

How are users authorized?

An authorized signer names them with roles and limits; each user enrolls through their own link, and operations sets them up under dual control.

When is the service live?

After the agreement is accepted, the limits are approved and the setup is confirmed by the second person, with the business told what is live.

Related processes

Business online banking users and entitlements Positive pay exception decisions Merchant services onboarding Try it in the sandbox All banking and credit unions processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.