Remote deposit capture enrollment

How do we enroll a business or consumer in remote deposit capture with eligibility, limits and the agreement handled in one request?

Run enrollment as a decision with the agreement inside it. Callvu identifies the customer, checks eligibility against the account's history and the bank's policy, sets the deposit limits by tier, delivers the remote deposit agreement and captures its acceptance, routes a limit above the automatic range to treasury or deposit operations in the Decision Desk, and enables the service in the deposit platform with the limits and the agreement on the record.

In scopeSimpleCallvu moves: prefill, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 6, 2026.

The problem today

The business is enabled with a limit someone guessed, and the agreement is signed after the first deposit.

Today, without Callvu

A business asks for remote deposit. The relationship manager emails an agreement, enables the service in the deposit platform so the customer can start, and sets a daily limit from a conversation. The signed agreement arrives a week later, or the business deposits for a month on an unsigned one. A consumer enrolls in the app with a limit that was set for everyone.

Remote deposit capture is a credit and fraud decision. The interagency guidance expects the bank to assess the customer's risk, set limits, obtain an agreement with the customer's obligations (image quality, retention and destruction of the original items, duplicate presentment), and monitor. Under the UCC and Reg CC the bank bears the risk of a duplicate presentment unless the agreement and the process shift it.

The enrollment decision is also where the limit lives, and a limit set by conversation is a limit nobody can explain to the examiner.

How it runs

From the requestto the system of record.

A business or consumer requests remote deposit capture in the app, online, with a relationship manager, or on a call. Callvu identifies the customer and opens the enrollment.

Customer: Requests the service, confirms the accounts and the expected volume, accepts the agreement, and receives the limits.
Treasury or deposit operations: Decides limits above the automatic range and exceptions in the Decision Desk, and sees every enrollment with its agreement and limits.
Callvu: Identifies, checks eligibility, sets limits by tier, delivers and captures the agreement, routes exceptions and enables the service.

Prefill and eligibility
The customer's accounts, their age and history (returned items, overdrafts, average balances), the relationship and, for a business, its type and risk rating are read from the core. Eligibility runs from the bank's policy: account age, standing, returned-item history, and for a business the risk rating.
Decide the limits
The tier from the policy sets the daily and per-item limits and the holds for deposits over them. A requested limit above the tier, or a business with an elevated risk rating, goes to treasury or deposit operations in the Decision Desk with the history and only the allowed outcomes: approve, approve a lower limit, or decline.
Agreement and acceptance
The remote deposit agreement with the customer's obligations (endorsement, image quality, retention and destruction of originals, no duplicate presentment, limits and funds availability) is delivered and accepted on a process-controlled screen with a timestamp. For a business, the authorized signer accepts.
Write back
The service is enabled in the deposit platform with the accounts, the limits and the tier, and the agreement, the eligibility result and the limit decision are written to the record. The customer receives the limits and the instructions.

Where it ends: The service is live with limits the policy set or a person approved, the agreement accepted and on file, and the eligibility result recorded. The Decision Trace shows the tier and the decision; the Audit Trace shows every step.

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

Interagency guidance on risk management of remote deposit capture (FFIEC, 2009): The bank identifies and assesses the risks of remote deposit capture, performs customer due diligence appropriate to the risk, establishes limits and monitoring, and obtains a contract that sets the customer's obligations, including image quality, retention and destruction of original items, and the bank's rights. The enrollment decision and its evidence are what examiners review.
Check 21 and Reg CC substitute checks and electronic items (12 CFR part 229 subpart D, and 229.34 warranties): A bank that accepts a remotely deposited item makes warranties on the image, including that no duplicate will be presented; the remote deposit agreement allocates the customer's responsibility for a duplicate presentment and the bank's recourse.
Reg CC funds availability (12 CFR 229.10 to 229.13): Remote deposits are not made in person; the availability schedule and any exception holds apply, and the agreement states how the bank treats them.
Bank Secrecy Act customer due diligence (31 CFR 1020.210): For a business, the service and expected volume form part of the customer risk profile; an elevated rating routes the enrollment to a person.

Company policies

Eligibility conditions and the limit tiers are the bank's remote deposit policy and are applied by Callvu.
No service is enabled before the agreement is accepted on the record.
A limit above the tier or a customer with an elevated risk rating needs a decision in the Decision Desk.
The deposit platform is the system of record for the service and its limits; the agreement lives with the customer record.

Controls

Eligibility check against the core's account history.
Limit tier applied from policy, with routing above it.
Agreement delivery and acceptance on a process-controlled screen.
Authorized signer check for a business acceptance.
Single enablement write with limits and tier.
Record of the eligibility result and the limit decision.

Clocks and deadlines

Enablement: After the agreement is accepted, not before.
Decision Desk review: The reviewer is nudged on the policy's schedule and the customer sees the status.
Limit review: Limits are reviewed on the policy's cycle from the enrollment date, as its own process.

Documents and checks

The eligibility result from the account history
The limit tier and any limit decision with the decider
The remote deposit agreement as accepted, with the signer and timestamp
The enablement record in the deposit platform
The instructions and limits sent to the customer

In the Decision Trace

The eligibility rules applied and their results.
The tier and the limits, and any person's decision above it.
The agreement acceptance and who accepted.
What was enabled and where.

In the Audit Trace

The request, its channel and time.
The Decision Desk step where there was one.
The agreement delivery and acceptance.
The enablement write.

The handoff

Between the front doorand the back office.

The front door

The app, online, a relationship manager or a call. The customer accepts the agreement on their own screen; a business signer on theirs.

The back office

Treasury or deposit operations decides only limits above the tier and exceptions. The deposit platform is enabled from the decided case, with the agreement attached.

The Decision Desk

A limit above the tier or an elevated-risk business goes to treasury or deposit operations in the Decision Desk with the history and only the allowed outcomes: approve, approve a lower limit, or decline.

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.

Can the service be enabled before the agreement is signed?

No. The agreement is accepted on the customer's screen first, and the enablement write follows it.

How are limits set?

By tier from the bank's policy, based on the account's history and the relationship. A limit above the tier is decided by treasury or deposit operations in the Decision Desk.

What does the agreement cover?

The customer's obligations: endorsement, image quality, retention and destruction of originals, no duplicate presentment, the limits and funds availability.

Related processes

Large-deposit and exception holds Treasury and ACH origination onboarding Returned deposit item handling 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.