Authorized signer add or remove

How do we add or remove an authorized signer on an account without the resolution and the ID arriving by email?

Run the signer change as a case with two parties. The account owner or the business authorizes the change and provides the resolution; the new signer identifies themselves on their own phone; Callvu checks both, routes any exception to deposit operations, and updates the signers in the core and the signature system together. Live at Bank Leumi, under national rules outside the US.

Live at Bank LeumiComplex: multi-party handoffsCallvu moves: prefill, chase and verify, decide, write back

Last updated November 6, 2026.

The problem today

The core says one thing about who can sign, the signature system says another, and the resolution is in someone's inbox.

Today, without Callvu

A business emails the branch: add our new controller as a signer, remove the one who left. The banker asks for a resolution and a copy of the controller's license. They arrive over three days, from two people. The banker updates the core; the signature card system is updated the following week by someone else, or not at all. The departed signer can still draw a check for a month.

The bank's CIP policy applies identification and verification to every signer, and the beneficial ownership record changes when the new signer is also a control person. Done by email, the verification is whatever the banker remembered to do, and the record is a scan.

Removal is the urgent half and the one that waits. A removed signer is a fraud risk every day the two systems disagree.

How it runs

From the requestto the system of record.

An account owner, or an authorized representative of a business, requests a signer change in a branch, on a call, online or by a message to their banker. Callvu opens a case for the account and identifies the parties who must act.

Account owner
Authorizes the change and, for a business, provides the resolution or equivalent naming the new signer and the authority granted.
New signer
Identifies themselves with a document, accepts the authority, and signs, on their own phone.
Deposit operations
Reviews exceptions and sees every signer change with its resolution and identification.
Callvu
Prefills, chases each party, verifies, routes exceptions and writes the signers to the core and the signature system together.
  1. Prefill the account and its signers

    Callvu reads the account, its current signers and the entity's record from the core and prefills the request. The owner marks who is added and who is removed, and the authority each signer has.

  2. Removal first

    A removal needs the owner's authorization and nothing from the departing signer. Callvu writes the removal to the core and the signature system as soon as the authorization is verified, so the window closes the same day.

  3. Chase and verify the resolution

    For a business, the resolution or equivalent is requested from the authorized representative with a link. It is read and checked against the entity's record: the right entity, the right signatories, the authority named.

  4. Chase and verify the new signer

    The new signer receives a link, provides their identification document, and is verified and screened under the bank's CIP policy. If they are also a control person, the beneficial ownership record is updated. The signature is captured on a process-controlled screen.

  5. Decide

    A verified owner authorization, a resolution that matches the entity, and a signer whose identification verified clean update automatically. A mismatch, a screening hit, or a resolution that does not match routes to deposit operations in the Decision Desk with only the allowed outcomes.

  6. Write back

    The signers and their authorities are written to the core and the signature system in one step, with the resolution, the identification and the signature attached, and a confirmation goes to the account owner.

Where it ends: The core and the signature system show the same signers with the same authorities, the resolution and the identification are on file, and the removal took effect the day it was authorized. Every step is in the Decision Trace and the Audit Trace.

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.

The handoff

Between the front doorand the back office.

The front door

The owner starts the case in any channel; the new signer enters through a link and acts on their own phone. Identification and signature happen on process-controlled screens.

The back office

Deposit operations receives only the exceptions. The core and the signature system are written in one step from the verified case, and nobody updates one and forgets the other.

The Decision Desk

  • A resolution that does not match the entity, a signer whose identification does not verify, or a screening hit goes to deposit operations in the Decision Desk with the case and only the allowed outcomes: request another document, approve with a safeguard, or reject the change.
  • A new signer who has not responded is nudged until they act; the owner sees what is outstanding.

Proof

Live at Bank Leumi.Published results only.

Each result is a published claim, with its code on agents.callvu.com, where its status, source and last verified date are kept.

Bank Leumi reached a 94% average completion rate.

BNK-16 · Customer-attested · verified 2026-11-02

Bank Leumi cut data errors by 77%.

BNK-03 · Customer-attested · verified 2026-11-02

Bank Leumi cut digital development timelines by 91%.

BNK-17 · Customer-attested · verified 2026-11-02

Questions

What buyers ask next,answered plainly.

Does the new signer have to come into the branch?

No. They receive a link, provide their identification, accept the authority and sign on their own phone. The owner sees the case fill.

How fast is a removal?

The same day the owner's authorization is verified. The removal is written to the core and the signature system before any addition is processed.

What stops the core and the signature system from disagreeing?

They are written in one step from the same verified case. One cannot be updated without the other.

What if the resolution does not match the entity record?

The case goes to deposit operations in the Decision Desk with the mismatch and only the allowed outcomes. Nothing is written until a person decides.

Related 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.