Updating Stale Banking Details for Enterprise Customers

Updating stale banking details for enterprise customers takes more than an email announcing a new account. Suppliers need a structured process that gets the change to the right people, through security checks, and into the system that releases payment. The job is finished when the money reaches the right account.

Why banking details go stale in enterprise vendor records — and why nobody sends an alert

Banks have a contractual relationship with their own account holders. When a supplier changes banks or account numbers, its bank has no mechanism or obligation to notify those customers. There is no payer alert to switch on. The customer generally learns about the change from the supplier or when a payment fails, so a perfectly tidy vendor record can become wrong overnight.

Bank changes can also affect many records at once. In early 2025, Mercury Bank ended its partnership with Evolve Bank & Trust and moved the customers this affected to Choice Financial Group and Column N.A., banks it already worked with. Those users had to update banking details wherever they were stored. When suppliers have duplicate vendor records or staff leave, it is easier to miss a customer. Because no external system triggers a general update, suppliers must run their own process to get enterprise customers to act.

What happens when an enterprise customer pays to a stale account

ACH payments follow routing and account numbers. Most will not automatically find a supplier’s new account. Until the customer updates its system, payments can keep heading to the old one. Tracing, reversing, and reissuing them requires coordination across two finance teams, often over days or weeks. Even when an AP team wants to help, it must work through ERP controls and payment approvals, so a request sent on Monday may not reach the payment queue until the next week.

NACHA’s Notification of Change mechanism provides a correction path when information in an ACH entry is incorrect or outdated. Its rules require the company receiving the notice to update the customer record within six banking days, or before initiating another entry to the account, whichever is later. Failure to update may result in additional fees. This is not a substitute for proactive outreach.

Dun & Bradstreet’s Q2 2026 U.S. Accounts Receivable Industry Report shows that a meaningful share of receivables in multiple industry segments are severely delinquent, at 91+ days past due. Avoidable routing problems add friction to that backlog. They can push invoices past due dates, distort aging metrics, and put pressure on liquidity where margins are thin.

The fraud risk that makes a casual update process dangerous for your enterprise customer

To an enterprise AP team, a legitimate banking change can look uncomfortably like fraud. An attacker impersonates a supplier, often through a compromised email account, and asks AP to redirect future payments. The invoice and vendor relationship may both be genuine. That is the trap. The attack exploits a trusted process rather than breaking it, and it can remain undetected until the real supplier asks about missing payments.

Trustmi’s Benchmark Report says that 85% of payment fraud attacks start in email and get past email security. Bank letterhead and voided checks do not resolve the problem because they can be forged, intercepted, or swapped, and neither proves account ownership. A familiar-looking attachment is not a security clearance. From the supplier’s perspective, this explains why a routine request can trigger detailed scrutiny.

NACHA’s 2026 ACH fraud-monitoring rules require originators to implement risk-based processes to identify entries authorized under false pretenses, including business email compromise and vendor impersonation. Enterprise AP teams thus have good reasons to ask for more than an email. Their caution protects the payment relationship, even when it slows the change.

Why enterprise customers are harder to update than smaller ones

In a large company, the person who receives an invoice is usually different from the person who changes a vendor record. AP, procurement, and vendor master data management may operate as separate teams with separate workflows. A helpful invoice contact may not have access to change the record. The request then needs a handoff.

Procurement portals such as Coupa and Ariba add another distinction. They can serve as the submission point, while the ERP vendor master remains the authoritative record. An email may not count as a request unless the change also enters the portal with the required documents and format. Formal approval and a separate verification call can follow. Each step has a purpose, but each also creates somewhere for the request to stall.

A change can reach one record while leaving the active payment record untouched. Meanwhile, high-volume AP teams are likely to deprioritize requests that arrive incomplete or outside their standard process. The supplier’s task is to discover the required route, rather than assume that one message to one contact will cover it.

How to identify which enterprise customers are working from stale details

To move from diagnosis to action, start by separating confirmed problems from accounts that need review. Payments arriving at a former account are the clearest evidence. Failed or returned ACH entries also signal stale records. Less direct clues include previously punctual payments becoming late without a dispute or credit hold, or invoices marked approved and scheduled in a customer portal that remain unpaid.

Check whether customer account records still contain details that predate a known banking change. Also review customers for whom the update was sent but receipt was never systematically confirmed. Silence is not proof of a successful update.

After a bank migration, account change, or entity restructure, assume every enterprise customer may be affected until you have checked otherwise. Prioritize large upcoming payments and amounts due in the current cycle. Then cross-reference the payment method, since wire and ACH customers depend on banking details, while check and card customers may be affected differently or not at all.

Finding the right contacts inside an enterprise customer's organization

Start with your AR team, which may already know someone beyond the invoice email alias. Ask who is in charge of vendor master changes as well as who handles invoices. Those are different questions with different destinations. Where a dedicated Vendor Management or Supplier Relations team exists, it should be the primary contact. Without one, the AP Manager or Controller typically has the relevant access.

For customers who use a portal, check the vendor profile for a contact name or a way to reach the help desk before sending email. The portal administrator or procurement operations team may be the right entry point. This avoids opening an unrelated email route while a portal request is already moving through another workflow. Two routes are not automatically faster than one.

A named account manager or customer success contact can help make an internal introduction. Use that relationship to find the finance or procurement owner. Record each person’s name, role, and response as you go. If the request later stalls, that contact history will show where the handoff stopped.

Structuring the update request so enterprise AP teams can process it quickly

Use a clear subject line and opening sentence that identify the message as a banking detail update. Make the request easy to recognize immediately. Include the supplier’s full legal name as it appears in the customer’s vendor master and the vendor ID, if known. Then provide the former bank name and account number’s last four digits, the new details, and the effective date.

The request should also name a contact and direct phone number for out-of-band verification. Offer to participate in that call. Ask upfront whether the customer requires a formal W-9, a bank verification letter obtained directly from your bank, or a signed company letter. Supplying the right documents first is quicker than playing attachment tennis. Those documents should support verification.

If the customer uses a vendor self-service portal, submit there at the same time as the direct outreach and note that the portal submission is pending. This gives AP a request to look up. If you have a lot of customers, use the same template for the core information, but choose the documents and the way you send them to fit what each customer needs.

Working with enterprise verification controls rather than against them

Name a senior finance contact who can take the callback for verification. Provide a direct number, but recognize an important limit. AP should confirm the change using a number obtained from its verified records. Availability helps the check move quickly without asking the customer to weaken it.

Approval may still involve more than one person. Segregation of duties means the person processing the change is typically not the person approving and releasing payment. Follow up with both where needed, or with the first contact so they can pass the update onward. Some customers also use bank account monitoring tools that can trigger re-verification after a change, even when documentation has already been submitted.

Cooling periods create a separate timing constraint. Many enterprise customers hold payments for a fixed window after a banking change. Plan outreach so that window expires before the next payment is due. The objection that verification takes too long is understandable, but a failed check or fraud hold takes longer to resolve than a clean approval.

Following up when the request stalls inside the customer organization

Set the follow-up cadence before sending the request. If you have yet to hear back within a set time, typically three to five business days, follow up directly with more than a forwarded copy of the original email. Give the date of that email and name the step that still needs action, such as portal acknowledgment, the verification call, or AP manager sign-off. Ask for a timeline.

After two unanswered follow-ups, escalate to the contact’s manager or a parallel contact in the organization. Keep the original person copied or ask them to introduce you so they know you are taking the request to someone else. For high-value accounts with a payment actively at risk, have your senior finance contact or account relationship owner call their counterpart. Frame it as coordination. The aim is to unblock a change.

If direct contact still gets you nowhere, use any formal supplier dispute or inquiry channel to get a case logged. Keep a written record of who was contacted, when, what they said, and the next step. That record supports escalation and any later dispute over a delayed payment. When you have a lot of customers, a set workflow keeps requests that have stalled in view without relying on someone to remember them.

Confirming the update is live before the next payment cycle

Ask the customer to confirm that the new banking details are active in both the vendor master and payment system. An acknowledgment is not that confirmation. Neither is a status of “processed” if it leaves the next payment’s destination unclear. For portal-managed relationships, check the supplier-facing vendor record where available, but still distinguish a displayed change from confirmation that payment will use it.

Time this check against the customer’s payment schedule. For weekly or bi-weekly batches, confirm the update at least two to three business days before the next run. When the first payment reaches the new account, log it as confirmed. That is the definitive proof of correct routing. If payment still reaches the old account, work with the customer’s vendor master team to check for duplicate records.

For a change affecting multiple customers, maintain separate milestones for request sent, verification completed, update confirmed active, and first payment received. Combining them into a single “done” status hides unfinished work. Banking details will go stale again as accounts and the way businesses work together change. Reliable payment depends on making this a repeatable process, with a clear owner and a finish line beyond the sent folder.