WorkflowDeposit Operations & Account Servicing

Account Maintenance Requests

Every account maintenance request read field by field, checked for account takeover and signed by two specialists before the record moves

Every change checked twice, and takeovers stopped before the record moves.

See one case, screen by screen ↓
demo$279,210.55protectedthat a forged payable-on-death form would have passed to a stranger at death, held for a callback and declined with the record unchanged, on the sample data
demo1,412requestsof 2,214 received in one day sorted into the low-risk lane in four groups for a checker, with one in 20 opened in full, on the sample data
demo241requestsdeclined in the sample September because the customer denied them on a callback to the contact of record
target100%of requests with a takeover signal called back on a number on file 90 days or more, before anything posts
In short

What is Account Maintenance Requests?

An account maintenance request asks a bank to change an account's owners, signers, mailing address, phone or payable-on-death beneficiaries. Account Maintenance Requests is account maintenance request software for deposit operations: agents read each request and its documents into only the fields that change, confirm the requester's authority, compare the signature with the card on file and look across 90 days for account takeover and elder exploitation. A specialist approves or holds, and a second specialist checks before anything changes.

AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →

Updated

The problem

Why an account maintenance request is the easiest way into an account

An account maintenance request changes who owns an account, who may sign on it, where its mail goes, which phone the bank calls and who receives the money at death. It arrives as a paper form by mail, a branch upload, a secure message or a contact center call. A specialist finds the customer in the core banking system, opens the signature card in document imaging, checks authority and the signature by eye, and keys the change. A second person re-reads the keyed fields, not the document.

The same changes are the first step of account takeover and elder financial exploitation. A fraudster changes the phone, then the address, then adds a beneficiary, and every later fraud alert reaches the fraudster. The phone changed last week, the device enrolled yesterday and the same mailbox on another older customer's request sit in other systems, so a forged form with a matching name passes. Meanwhile clean changes wait in the same queue as risky ones.

typical$27billionof suspicious activity in 155,415 elder financial exploitation reports to FinCEN in one year, June 2022 to June 2023
typical$28.3billiona year in losses to older adults from financial exploitation, by an AARP estimate
typical10business daysa large bank publishes as its time to process a beneficiary change once the signed form arrives
Where a flagged request's minutes goestimated
By hand77 minutes
With the solution21 minutes
  • Finding the customer and opening the signature card and earlier documents10 → 1 min
  • Reading the form and keying the change12 → 2 min
  • Checking authority and comparing the signature10 → 3 min
  • Looking across calls, devices and other requests for takeover signs20 → 3 min
  • Choosing a safe number and making the callback15 → 8 min
  • The second specialist's check, with the evidence10 → 4 min

Estimated split for one request with a takeover signal, worked by hand and with the solution; the callback itself still takes a person's time.

How it works

How a maintenance request moves

Six agents read the change, check authority and the signature, sweep 90 days for takeover and book the callback; two specialists sign.

What comes in
Requests in46,000 a month · branches, mail, contact center, digital banking
Agents at work
Intake agentonly the fields that change
Then
Authority agentcard, resolution, POA
Signature agentagainst the card on file
Then
Takeover agent90 days, every channel
Then
Callback and update agentsnumber of record, core update
A person decides
Specialist and checkerone approves or holds, a second signs
What comes out
Core updated and read back
Confirmations to old and new address
Takeovers to Elder Financial Protection
One case, step by step

One account maintenance request, from the form to the protection case

Tuesday, October 20, 2026, at Corvane National Bank's deposit operations. Here is one account maintenance request, a mailed form for an 81-year-old customer, screen by screen in the working solution, and a business signer change checked the same morning.

  1. 01Tue Oct 20, morning

    Her requests, sorted by what each one needs

    Talia Brennan · Deposit Operations Specialist

    Talia's queue shows 14 requests due today, 2 with takeover signals and 1 with a checker. Each request is one sentence the agents wrote, grouped as takeover signals, ready for approval, with someone else, and exceptions. Above it, the team's day: 2,214 requests received Monday, 1,412 in the low-risk lane, 647 for specialists, 155 with signals and none late.

    Mon Oct 19, 6:43 p.m. The Takeover agent found 5 signals on AM-2026-118204, score 0.94, and 2 linked requests by the same mailbox.

  2. 02One click

    Only the fields that change, before and after

    Intake agent

    Request AM-2026-118204 came by mail on Mon Oct 19 at 4:12 p.m.: form DO-114 for Eleanor M. Watts, 81, a customer since 1987. The Intake agent read 11 fields at 0.97 or higher and shows only the four that would change: the mailing address on all three accounts, Dale R. Pruitt, "nephew", 100%, as payable-on-death beneficiary on Statement Savings ••6083 and on 12-month CD ••7710, and a replacement debit card. Each requested value carries a clip of the line it came from.

    If this were approved: $279,210.55 would pass to Dale R. Pruitt at her death.

  3. 03One click

    Every value opens the line of the form it came from

    Talia Brennan · Deposit Operations Specialist

    The clip under the new mailing address opens source 1: form DO-114, line 4, scanned by the mail center at the Delmont Operations Center on Mon Oct 19 at 4:12 p.m., with 9080 Ridgeline Parkway, Suite 212, Kellerton, OH 43219 highlighted and the envelope postmarked Kellerton, Oct 16. Opening a source is recorded on the audit trail.

  4. 04On the documents

    Authority confirmed, and a signature that does not match the card

    Authority agent and Signature agent

    Mrs. Watts is the sole owner of all three accounts, so she alone may make the change, and no power of attorney is on file. The Signature agent compares line 10 of the form with her signature card of Jun 12, 2009: a match of 0.58, under the 0.85 threshold, with the "W", the slant, the even pressure and the size differing. Policy DM-7 needs a 0.85 match or a verified callback for a beneficiary change over $100,000.

    The Signature agent gives a score, never a decision; below 0.85 it always goes to a person.

  5. 0590 days back

    The phone was changed six days ago, to the beneficiary's number

    Takeover agent

    The timeline reads every channel: a digital banking password reset with a voice code on Tue Oct 13; a contact center call on Wed Oct 14 that changed the phone on file from 330-555-0148 to 216-555-0192 with the one-time code skipped; a new device enrolled on Thu Oct 15; an external account ending 9921 added on Fri Oct 16; the form on Mon Oct 19. The Kellerton address is a private mailbox 128 miles from her home, and 216-555-0192 is the phone the form gives for the beneficiary.

    The same mailbox is on AM-2026-117952 (Harold Benning, 79, denied on callback) and AM-2026-118166 (Lorraine Duvall, 84, callback booked).

  6. 069:32 a.m.

    One choice: she holds it for a callback

    Talia Brennan · Deposit Operations Specialist

    With five signals and a takeover score of 0.94, where a callback is required at 0.40, the agents recommend a hold. Talia holds the request. The hold records the reason, the number to call, 330-555-0148, on file since Jun 12, 2009, the number never to call, 216-555-0192, which is in the request, and the deadline of 1:30 p.m., four business hours away. Sending it to the checker instead would have needed an override reason code and a note.

    Nothing on Mrs. Watts's record changes while the request is held.

  7. 079:34 a.m.

    A callback to the contact of record, not the number in the request

    Callback agent and Talia Brennan

    The Callback agent chose 330-555-0148: the newest number on file for 90 days or more and not in the request, and the number the Oct 14 call took off her record. Its script never reads the request back. In a 4 min 12 s call, Mrs. Watts answers two questions that are not on the form, and says that on Oct 13 a man calling as "the bank's fraud department" asked her to read him a code. Talia records the outcome: denied by the customer.

    "I never sent a form. I don't know a Dale Pruitt and I haven't moved."

  8. 089:38 a.m.

    Elder Financial Protection takes the case, with the record unchanged

    Grace Whitford · Elder Financial Protection Specialist

    The request is declined and becomes case EFP-2026-0412, with the two linked requests. Grace proposes four protective actions, each approved by her and checked by Marcus Oyelowo: restore the phone to 330-555-0148, remove the device enrolled Oct 15, remove the external account ending 9921, and block debit card ending 4402 and reissue it. The case names the trusted contact, Ruth Keller, her daughter, named May 14, 2019, drafts an Ohio Adult Protective Services referral and refers the case to Financial Crimes Investigations, whose work is not shown here.

    Mailing address still 418 Linden Hollow Road, no beneficiary on ••6083 or ••7710, no card mailed, $291,690.72 with no transfer out.

  9. 09Before it is sent

    What the customer sees reveals nothing

    Update and notice agent

    Mrs. Watts's digital banking message says the bank received a request, did not make the changes, called her on the number it has had on file and will write to her home address, and that it will never ask for a code or a password. It goes to her address of record and her own device. Nothing confirms a beneficiary name or a new address to whoever sent the form.

    Checked before it was sent: no mention of a referral, an investigation or a report.

  10. 109:41 a.m.

    A business signer change, checked against the evidence

    Marcus Oyelowo · Deposit Operations Specialist, checker

    The same morning, Talia approved AM-2026-118211 for Kessling Millwork LLC at 9:12 a.m.: a corporate resolution adds Nadia Ferro, the CFO, and removes Glen Ashby as signers on Business Checking ••5530 and Business Money Market ••5548, with two signatures still required over $25,000. Marcus ticks five checks himself, including beneficial owners of 45%, 30% and 25% adding to 100% and Nadia Ferro's identity verified at 0.99 with no sanctions match. He signs, and the core update posts, is read back and a confirmation is drafted to the business address of record.

    A maker cannot check their own request.

Who it’s for

Built for everyone who touches an account maintenance request.

The same request, seen by the people who review it, check it, protect the customer, run the desk and audit it: what their day looked like, and what it looks like now.

TB
Talia BrennanDeposit Operations Specialist · 35–50 requests a day in the Ohio and Pennsylvania queue
Deposit Operations Specialist
Before
Finds each customer in the core, opens the signature card in document imaging, compares the signature by eye and keys the change; fraud checks happen only if someone notices.
Now
Opens one request with only the fields that change, each tied to its line, the takeover signals beside them and a callback number chosen for her. She holds, approves or overrides with a reason.
MO
Marcus OyelowoDeposit Operations Specialist · checks other specialists' changes and the low-risk lane
Deposit Operations Specialist, checker
Before
Re-reads the maker's keyed fields, not the document and not the account's recent history.
Now
Checks the same evidence the maker saw, ticks his own checklist, signs or returns with a reason code, and approves clean groups with one in 20 opened in full.
GW
Grace WhitfordElder Financial Protection Specialist · protective actions, trusted contacts and referrals
Elder Financial Protection Specialist
Before
Hears about a suspected exploitation after the change has posted and the money has started to move.
Now
Receives the case with the record unchanged, the call summary and the linked requests, and proposes protective actions that a second person checks.
LC
Lena CastellanosDeposit Operations Manager · the same-day target, staffing, returns and the monthly report
Deposit Operations Manager
Before
Watches clean changes wait in the same queue as risky ones, and builds the monthly numbers by hand.
Now
Sees the team's day against the same-day target and four-hour callbacks, reassigns requests in bulk, and approves a monthly report the agents draft from the trail.
HV
Harriet VanceInternal Audit · tests maintenance files and builds the examiner pack
Internal Audit
Before
Tests maintenance files by gathering the form, the signature card, the call notes and the approvals from separate systems.
Now
Filters the trail of every action by people and agents and builds an examiner, internal audit or BSA officer pack in one step, with redaction applied.
Built on the engine

6 agents. Each with one job, and hard limits.

Six agents read the change, check authority and the signature, sweep 90 days for takeover and book the callback; two specialists sign.

Intake agent

Reads every request, whether a form, a branch upload, a secure message or a call note, classifies the change types, reads each field with a confidence and finds the customer and accounts.

  • Never guesses a value under 0.95
  • Never matches a customer on a name alone
Authority agent

Confirms the requester may make the change: an owner or signer on the card, the officer a resolution names, the powers a power of attorney grants. Lists the documents the change type needs.

  • Never accepts a power of attorney for a beneficiary change without an express grant
  • Never waives a document
Signature agent

Compares the signature with the card on file and gives a score with the features that differ.

  • A score, never a decision
  • Below 0.85 always goes to a person
Takeover agent

Sweeps 90 days of changes, contact center calls, devices, card requests and external accounts, links the same phone or mailbox across customers, scores takeover and elder exploitation patterns and writes "If this were approved".

  • Never decides
  • Never shows or mentions a SAR
  • Never contacts the customer
Callback agent

Chooses the contact of record, on file 90 days or more and not in the request, drafts a script that does not read the request back, and summarizes the call.

  • Never calls a number in the request or one changed in the last 90 days
  • Never records an outcome itself
Update and notice agent

Drafts the core update field by field; after the checker signs, posts it and reads it back, and drafts confirmations to the old and the new address.

  • Never posts on one signature
  • Templates only
Deposit Operations Specialist

Approves or holds; a second specialist checks. The agents propose; a named person decides.

Ask in plain words

Ask about any request, in plain words

Ask about any request, signal, document or rule, or say what to prepare. Every answer points to its source.

Why is the signature flagged on AM-2026-118204?

The Signature agent scored line 10 of the form at 0.58 against Mrs. Watts's signature card of Jun 12, 2009; the threshold is 0.85. The "W" is formed differently, the slant is gone and the pressure is even, as traced signatures often are. Policy DM-7 needs a 0.85 match or a verified callback for a beneficiary change over $100,000.

Who else has the Kellerton mailbox or the new phone?

The mailbox 9080 Ridgeline Pkwy Ste 212 is on two other requests this month: AM-2026-117952 for Harold Benning, 79, denied on callback, and AM-2026-118166 for Lorraine Duvall, 84, with a callback booked. The phone 216-555-0192 is on no other customer; it came onto Mrs. Watts's record on Oct 14.

Approve the USPS address matches

612 address changes match a permanent USPS change of address by the same customer, with no signal in 90 days. One in 20 is opened in full: 31 sampled, and one was pulled out because its forward is temporary. Each customer gets a confirmation at the old and the new address. You approve as checker.

Build the examiner pack for AM-2026-118204

The pack holds the form and its read lines, the 2009 signature card and the score, the 90-day history, the callback summary, every decision with its reason, and the protection case's actions, with account numbers masked. Nothing in it names a report to FinCEN.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

An account maintenance request: only the fields that changeRequest AM-2026-118204 for Eleanor M. Watts, 81: the new mailing address, a payable-on-death beneficiary on two accounts and a replacement debit card, each clipped to its line on form DO-114, beside five takeover signals with a score of 0.94 and what approving would let someone do.
The specialist's queue, sorted by what each request needsTalia Brennan's requests on Tue Oct 20: 14 due today, 2 with takeover signals, 1 with a checker, each in one sentence the agents wrote, with the team's day of 2,214 requests and bulk assignment.
Every value opens the line of the form it came fromThe clip under the new mailing address opens form DO-114, line 4, as scanned at the Delmont Operations Center, with the envelope postmarked Kellerton, OH. Opening a source is on the audit trail.
The signature card, the signature and the authority checkThe form's signature compared with Mrs. Watts's signature card for the account, dated Jun 12, 2009: 0.58 against the 0.85 threshold, with the features that differ, next to the authority checklist and policy DM-7.
90 days across every channel, and the same mailbox on other customersA password reset, a phone change that skipped the one-time code, a new device and an external account in six days, then the form; and the same private mailbox on two other older customers' requests this month.
One choice: hold for a callbackThe hold records the reason, the number to call, the number never to call because it is in the request, and the four-business-hour deadline. Nothing on the record changes while it is held.
A callback to the contact of record, scripted and summarizedThe Callback agent chose the landline on file for 17 years and drafted a script that never reads the request back; the specialist records the outcome, denied by the customer.
Elder financial exploitation: the protection case, with the record unchangedCase EFP-2026-0412: what happened, cited step by step, four protective actions each with a maker and a checker, the trusted contact, an Adult Protective Services referral and a referral to Financial Crimes Investigations.
What the customer sees reveals nothingThe neutral digital banking message for a held request, checked before it is sent: no referral, investigation or report mentioned, and nothing confirmed to whoever sent the form.
Maker-checker on a business signer changeMarcus Oyelowo checks a corporate resolution for a bank account change at Kessling Millwork LLC: one signer added, one removed, beneficial owners adding to 100%, the new signer's identity verified. He signs, and the core update posts and is read back.
Clean changes cleared in groups, with a sample1,412 low-risk requests in four groups, 72 sampled one in 20; 611 address changes matching a permanent USPS change of address approved at once, and one with a temporary forward pulled out for a specialist.
Exceptions, with what the agents may not decideAn agent under a durable power of attorney asks to name himself payable-on-death beneficiary without an express grant. The specialist declines, sends to Legal or moves it to Elder Financial Protection, with a reason code and a note.
The audit trail and the examiner packThe examiner pack for one request, built from the trail: the form and fields read, the signature card and score, the 90-day history, the callback, every decision with who, when, why and the evidence, and the agent versions, masked to the last four.
Governance

Built for account maintenance: two signatures, cited, on the record.

A maker and a checker on every changeEvery change to signers, owners, addresses, phones, beneficiaries, trusted contacts and beneficial ownership, and every protective action needs one person who approves and a second who checks, and every low-risk group is approved by a checker. The maker never checks the same request, and nothing changes on one signature.
Callbacks only to the contact of recordA takeover score of 0.40 or more needs a callback before any change. Callbacks go only to a number on file 90 days or more, never one in the request, and the specialist, not the agent, places the call and records the outcome.
Every value cites its sourceEach requested value carries the line of the form or document it came from, and each takeover signal its evidence. Opening a source is recorded on the audit trail.
No tipping offSAR confidentiality is locked on: no deposit operations screen, letter or customer view shows whether a SAR exists. Referrals to Financial Crimes Investigations are sent, and its work is never shown here.
Agents propose, people decideAgents never post, never call the customer and never decide a hold or a referral. Overrides need a reason code (OV-1 to OV-5) and a note, and returns a reason code (RC-1 to RC-5). Prompts and models are versioned, and a new version runs on last month's 45,870 requests before it goes live, and Compliance signs the comparison.
A complete trail and an examiner packEvery action by people and agents is recorded with who, what, when, why and the evidence. Packs for examiners, internal audit and the BSA officer mask account numbers to the last four, and records are kept five years after the account closes.
Configuration

Your account maintenance rules, as settings

Callback thresholds, the contact-of-record rule, the low-risk sample and retention are settings. They belong to the Administrator; each change is a new version, and locked items need Compliance.

SettingDefaultChoose from
Callback required at a takeover score of0.400.30 · 0.40 · 0.50
Elder Financial Protection suggested at0.800.70 · 0.80 · 0.90
A callback number must have been on file at least90 days60 · 90 · 180 days
Callback within, from the hold4 business hours2 business hours · 4 business hours · 1 business day
No answer: tries before a letter to the address of record2 tries2 · 3 tries
Low-risk lane sample, opened in full before a group is approved1 in 201 in 10 · 1 in 20 · 1 in 50
Keep records for5 years after the account closes5 · 7 years after closure
Connections

Works with the systems deposit operations already runs on

Core banking systemcustomer search, accounts, maintenance posting and read-back
Document imagingforms, signature cards, corporate resolutions, powers of attorney and faxes
Customer contact historycontact center calls and the changes they made
Digital banking platform and card processorsessions, devices, external accounts and messages; card requests, blocks and reissues
Address validation serviceUSPS change of address matches, private mailbox flags and distance from home
Case management and correspondenceprotection cases and referrals; letters and mailing records
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
100%
of requests with a takeover signal called back on a number on file 90 days or more, before anything posts
Every flagged request
called before it posts
target
100%
of changes to signers, owners, addresses, phones and beneficiaries signed by a maker and a second specialist, each field tied to its document
target
Sameday
for clean requests received by 2 p.m., against up to 10 business days for a beneficiary change today
Todayup to 10 days
With agentssame day

“demo” = seen in the working solution, on its sample data · “target” = the design goal, to be measured in the live solution · “estimated” = our estimate · “typical” = published figures (the December 2024 Interagency Statement on Elder Financial Exploitation, citing FinCEN's 155,415 elder exploitation reports tied to $27 billion of suspicious activity from June 15, 2022 to June 15, 2023, and AARP's $28.3 billion estimate of annual losses; a large bank's published turnaround of up to 10 business days for a beneficiary change). Rules named: 31 CFR 1020.320 on SARs and their confidentiality; 31 CFR 1010.430 on records; 31 CFR 1010.230 on beneficial ownership. Corvane National Bank and the customers, businesses, people, addresses, phone numbers and account numbers named on this page are fictional: characters and sample data in the working solution.

Questions

What deposit operations teams ask about account maintenance request software.

What is Account Maintenance Requests?

An account maintenance request asks a bank to change an account's owners, signers, mailing address, phone or payable-on-death beneficiaries. Account Maintenance Requests is account maintenance request software for deposit operations: agents read each request and its documents into only the fields that change, confirm the requester's authority, compare the signature with the card on file and look across 90 days for account takeover and elder exploitation. A specialist approves or holds, and a second specialist checks before anything changes.

How does it spot account takeover in a change of address or phone request?

The Takeover agent reads 90 days of contact center calls, digital banking devices, external accounts, card requests and earlier changes together, and links the same phone or mailbox across customers. In the sample case it found the phone on file changed six days before the form, to the number the form gave for the new beneficiary, and the new address was a private mailbox already on two other older customers' requests. A takeover score of 0.40 or more needs a callback before any change.

How is a payable-on-death beneficiary change handled for an older customer?

The agents show what approving would let someone do, in plain words and dollars, such as $279,210.55 passing to a person new to the bank at the customer's death. Policy DM-7 in the working solution needs a 0.85 signature match or a verified callback for a beneficiary change over $100,000. Suspected exploitation goes to the Elder Financial Protection team with the record unchanged, where protective actions, the trusted contact and an Adult Protective Services referral are each made by one person and checked by another.

Can it add an authorized signer to a business account from a corporate resolution?

Yes. The agents read the corporate resolution and the new signature card, confirm the certifying officer, list the signers added and removed, and update the beneficial ownership certification with each owner's percentage. A new signer's identity is verified before the change. The checker ticks each check against the same evidence, signs, and the core update posts and is read back.

Does a customer ever see that a request was referred for investigation?

No. SAR confidentiality is locked on, so no deposit operations screen, letter or customer view shows whether a SAR exists. The message for a held request says only that a request was received, the changes were not made and the bank will call on the number it has on file, and it is checked for any mention of a referral before it is sent.

Can clean requests clear the same day?

That is the design target for clean requests received by 2 p.m. Low-risk changes, such as an address change matching a USPS change of address or a phone change from a verified digital session, are grouped so a checker approves a group at once, with one in 20 opened in full. Every address change sends a confirmation to the old and the new address.

Do people stay in control of every change?

Yes. Agents propose, cite and recommend; they never post, never call the customer and never decide a hold or a referral. Every change needs a maker and a checker, the maker cannot check their own request, and sending a flagged request on needs an override reason code and a note.

How does it go live at our bank?

The Agentic Solution Engine builds and deploys it from your requirements and documents: your maintenance forms, change-type policy, callback standard and notice templates, connected to your core banking system and document imaging. It goes live once every quality gate has passed.

See it on
your maintenance requests.

We'll run Account Maintenance Requests on a sample of your own past maintenance forms and changes.