To ensure proper and timely reimbursement, a traveler must update their EFT bank account details in the payment system of record that holds their active reimbursement claim — in most organizations, that means the vendor or payee profile inside the travel and expense platform (SAP Concur, Oracle EPM, Chrome River, Coupa, or the government's travel system), not the HR directory and not the corporate card portal. Updating the profile alone won't redirect money already scheduled: any claim that has passed the "approved for payment" milestone usually requires the traveler to reopen or cancel it and resubmit with the new banking data attached.
The distinction matters because payments systems separate two things that look identical on screen. Your "payee profile" is a standing record used for future payments. A specific "payment instruction" is attached to a particular reimbursement at the moment it's released. Change the profile and a claim that's already in the payment run will still land in the old account. The five-channel map below shows where each update happens, and the deadline table that follows shows how much runway each system actually gives you.
Why Updating HR Records Does Not Redirect a Reimbursement
HR stores your bank details for payroll purposes, and payroll systems and expense systems are almost always separate databases with separate approval chains. A change submitted through the HR self-service portal typically triggers a payroll effective date — usually the next pay period — and has no connection to an open travel claim. Employees who update HR and assume the expense payment follows are the single most common cause of returned reimbursements.
The same logic applies to the corporate card issuer's portal. Card account details govern how the card is billed and credited, not how the company pays you back for out-of-pocket spend. A traveler who changes banks and updates only the card app will still receive reimbursement checks or ACH returns at the old account.
Government travelers face a third variant. In the U.S. federal system, banking information for travel reimbursement is maintained in the travel system's employee profile (historically tied to the EFT enrollment done at onboarding), and the Defense Finance and Accounting Service or the relevant agency pay center executes payment from that record. Changing it in the HR personnel system does not touch it.
The practical rule: identify the system that issued the reimbursement document number, and update there. If you can see the claim status online with a document or claim ID, that's the system of record.
The Five Places EFT Details Actually Live, and Which One Controls Payment
Most large employers run two to four of these systems at once, and each one holds its own copy of your bank data. Knowing which one pays you is the whole game.
| Channel | What it controls | Typical owner | Update latency before next payment run |
|---|---|---|---|
| T&E platform payee/vendor profile (Concur, Chrome River, Coupa, Oracle) | Future reimbursement payments tied to your employee or payee record | Travel & expense admin or finance shared services | Same day to 2 business days for verification; some tenants add a 24-hour bank-validation hold |
| Open claim's payment instruction | The specific reimbursement already submitted | The approver and the payment batch | Immediate if the claim hasn't entered the pay cycle; requires recall or resubmission once batched |
| HR/payroll self-service | Salary deposits only | Payroll | Next pay period, typically 1–2 weeks |
| Corporate card issuer portal | Card billing and statement credits | Card program administrator | 1–3 business days, affects card account only |
| Government travel system employee profile (e.g., EFT enrollment record) | Federal or agency travel reimbursement | Agency pay center (e.g., DFAS) | Usually 3–5 business days; changes after cutoff roll to the next cycle |
Two things follow from that table. First, the T&E platform profile is the standing record, but a claim's own payment instruction overrides it for that claim. Second, latency varies by channel by as much as ten-fold, so the channel you pick determines whether the fix lands this cycle or the next one.
Verification is the hidden variable in the first row. Many platforms run a bank-account validation step — either micro-deposit confirmation or a vendor service that checks the routing number against account ownership — and that step is what stretches "same day" into "sometime this week." Confirm the validation method on your platform's payee settings page before promising yourself the money by Friday.
How to Update Bank Details in the T&E Platform Payee Profile Step by Step
Names vary by tenant, but the path is consistent across Concur Expense, Chrome River, and Coupa. If your organization has customized labels, the same sequence applies with local wording.
1: Sign in to the T&E platform and open Profile (or My Account), then find the section labeled Bank Information, EFT/ACH Details, or Payment Method. 2: Select the reimbursement payment method — ACH/EFT direct deposit, not check — and enter the routing number, account number, and account type (checking or savings). 3: Complete any bank-validation step the tenant requires, such as micro-deposit confirmation or an instant account-verification service. 4: Save and note the confirmation or reference number the system displays. 5: Return to any open claim, expense report, or reimbursement request and check its payment method field; if it still points to the old account, edit the claim or ask your approver to return it so you can resubmit. 6: Email or ticket your finance shared-services desk with the claim ID and the update timestamp so the payment batch owner can confirm the change before release.
If the claim is already batched or paid, step 5 won't be enough on its own. Ask the pay desk whether the payment can be recalled before the bank file goes out; if it can't, the payment will return as an ACH return or be reissued, and you'll need to resubmit or wait for the return to post. Keep the confirmation number — it's the artifact that resolves disputes about when the change was made.
Open Claims Need a Payment Instruction Change, Not Just a Profile Edit
A claim that has cleared approval but not payment sits in a batched payment file, and the bank details attached to it were frozen at submission. Editing your profile now changes the default for the next claim, not this one. The fix depends on where the claim sits in the cycle.
If the claim is still in draft or returned status, edit the payment method directly in the claim and resubmit. This is the clean case, and it's why catching a bank change before approval matters more than any other timing factor.
If the claim is approved but not yet batched, ask your approver or the expense admin to return it, edit the payment instruction, and resubmit. Approval reversal is a routine transaction in every major platform; the delay is human, not technical.
If the claim is in the payment batch or already paid, the only paths are a recall before the bank file transmits or a return-and-reissue afterward. ACH returns typically take 2–5 business days to post, and reissue adds the next payment cycle on top. Build that into your cash-flow expectations rather than assuming the update is instant.
The Deadline Table: How Much Runway Each System Gives You
Payment cutoffs are set locally, but the pattern across systems is consistent enough to plan around. The figures below are planning approximations derived from typical published cycle structures; confirm the exact cutoff in your platform's payment calendar or with your pay desk.
| Milestone | Typical cutoff before payment run | What a bank change after this point does |
|---|---|---|
| Claim submitted and in approval | None — editable if returned | Edit the payment instruction and resubmit within the same cycle |
| Claim approved, pre-batch | 1–3 business days before the scheduled run | Ask for return-to-draft; usually lands in the same run if you act fast |
| Claim in payment batch | At the platform's scheduled bank-file transmission | Too late; payment goes to the old account and must be recalled or returned |
| Payment transmitted | Nothing you can change on your side | ACH return in 2–5 business days, then reissue on the next cycle |
| Check issued | Stop-payment window of 1–2 business days | Stop and reissue, or deposit the check into the new account |
The budget consequence is simple arithmetic. If your reimbursement is $1,200 and you miss the batch cutoff, you're waiting one full cycle plus the 2–5 business days for the ACH return — which for a monthly cycle can mean roughly five weeks between filing and cash in hand. That number is why the platform profile update deserves attention the day you change banks, not the day you file the claim.
What Happens to a Reimbursement Sent to a Closed Bank Account
A payment to a closed account doesn't vanish; it bounces back through the banking system, but the round trip costs time. ACH payments to closed accounts typically return within 2–5 business days with a return code indicating a closed account. The employer's pay center sees the return, marks the claim as returned, and reissues once valid banking data is on file.
Worse cases exist. If the account number was mistyped into a valid but wrong account, the funds may post to someone else's account, and recovery runs through the receiving bank's error-resolution process — often weeks, sometimes requiring a formal indemnity from your employer's bank. This is precisely why banks run name-and-account verification and why platforms add validation steps.
An edge case worth naming: some payroll and expense systems reject updates to bank details immediately after a change and impose a cooling-off period, a fraud control that many employees never see until it bites them. If your platform shows a "bank change pending review" status, don't submit another change — that resets the clock.
Updating Details on the Road: Mobile Apps, Security Checks, and the Call You Shouldn't Skip
Mobile expense apps let you edit payment methods, but many tenants restrict bank-detail changes to the web portal for security reasons. If the field is greyed out in the app, that's a policy setting, not a bug. Use the portal.
Expect identity verification on any bank change. Common controls include MFA, a confirmation email to the address on file, a manager notification, and in some organizations a callback from the pay desk to the phone number in the directory. Answer the callback — a missed verification call is a common reason a change sits in pending status past the payment cutoff.
While you're mid-trip, add one calendar reminder: one business day before your expected claim approval, check that the bank details on the claim itself still match the account you want paid. That single check catches nearly every closed-account return before it happens.
On the sensory side, the moment to picture is the airport gate area at 6 a.m., phone in hand, half-listening to a boarding call while you fumble through an app looking for a bank field that isn't there. That's the scenario that argues for making the update from a laptop at the hotel the night before, not in a departure lounge.
Government and Contractor Travelers: Agency EFT Enrollment Is a Separate Record
U.S. federal civilian and military travelers maintain banking information through their agency's EFT enrollment process, and the payment is executed by the agency pay center — for many defense travelers, DFAS. This record is separate from the HR personnel system and separate from the travel booking tool. Change it through the enrollment channel your agency publishes, and update the travel system profile if it holds a copy.
Contractor and grantee travelers reimbursed through a client's system fall under that client's vendor-master rules. If you're set up as a vendor, a bank change may require a new vendor form, a W-9 refresh, and a verification call to the vendor desk — a process measured in days to weeks, not minutes. Start it the day you change banks.
A region-specific wrinkle: international travelers reimbursed across borders may face correspondent-bank routing, currency-conversion fields, and IBAN or SWIFT requirements that domestic-only forms don't ask for. A routing number alone won't clear an international wire, and a partially completed international record will fail validation rather than pay.
The universal check for this category: ask the pay desk to confirm which record the payment will be drawn from before you file the claim, and get the answer in writing. A one-line email reply is cheap insurance against a five-week delay.
Six Failure Cases That Delay Reimbursement After a Bank Change
These are the scenarios where the update was made but the money still didn't arrive on time.
1: Profile updated, claim not updated. The standing record changed; the open claim's frozen payment instruction didn't. Most common failure by far. 2: Change made after the batch cutoff. The update was correct and timely in spirit, too late in mechanics. 3: Validation pending. Bank micro-deposit or verification service hadn't completed when the payment run drew the claim. 4: Joint or recently closed account. The old account number remained valid-looking in the profile because the traveler never edited it, and the bank closed it mid-cycle. 5: Typo that validated. A transposed digit that happens to be a live account passes format checks and posts to a stranger. 6: Cross-system assumption. HR or the card portal was updated; the T&E platform never was.
For each, the recovery is the same shape: contact the pay desk with the claim ID, the timestamp of your update, and the confirmation reference, and ask for the payment status specifically — batched, transmitted, returned, or reissued.
FAQ
Does updating my bank details in the expense app fix a claim that's already approved? Usually not by itself. An approved claim carries its own payment instruction, so the fix is to have the claim returned to draft, edit the payment method there, and resubmit before the batch cutoff. The profile edit only protects future claims. Ask the pay desk whether the specific claim can still be pulled from the batch.
How long does an ACH reimbursement take to come back after it hits a closed account? Banking industry return windows for closed-account ACH entries typically run 2–5 business days, and the reissue then waits for the next payment cycle. A monthly-cycle employer can therefore take about five weeks from filing to cash. Track the claim status rather than the bank balance during that window.
Can I update EFT details for someone else, like a spouse or a dependent traveler? No — banking changes are tied to the authenticated payee identity, and platforms log the change under the signed-in user. A dependent traveler or a colleague must make the change in their own session. Delegates with "act on behalf" rights can prepare a claim but generally cannot alter bank fields, a deliberate fraud control.
Is it safer to switch to paper checks while my bank details update? Checks introduce their own delays: printing and mailing typically adds 5–10 business days, plus a stop-payment window of 1–2 business days if the check goes astray. Direct deposit with a correctly validated account is faster in nearly every case. Use checks only as a bridge if your platform allows the switch without resetting the claim.
What's the difference between the routing number field and the account number field, and why do banks reject one but not the other? The routing number identifies the financial institution and must pass a checksum; the account number identifies you within it and is validated against bank records. A wrong routing number fails fast at the bank-file stage. A wrong account number can pass format checks and post to another person's account, which is why name-and-account verification exists.
Do I need to re-enroll in EFT every time I change banks? Rarely a full re-enrollment, but many organizations require re-verification, such as micro-deposits or a callback, after any bank change, and some impose a cooling-off period before the new details go live. Check the payee settings page for a pending status and don't submit a second change while one is in review.
Which system pays me if my employer uses both Concur and a separate payroll portal? The travel and expense platform pays travel reimbursements; payroll pays salary. The claim ID comes from the T&E platform, so that's the system of record for the reimbursement. Government travelers should confirm whether their agency pay center holds a separate EFT enrollment record.
Why did my reimbursement arrive as a check when I'd set up direct deposit? A failed bank validation, a closed account return, or a payee record flagged for manual review will push a payment to check or hold. The claim history usually shows the reason code. Fix the underlying bank record first, then ask the pay desk to reissue by EFT.
This article is general educational information about reimbursement payment processes, not financial, legal, or tax advice. Banking and payment rules differ by employer, platform version, agency, and country, so confirm the specific procedure with your organization's travel and expense administrator or pay center before acting. If a payment has gone to the wrong account, contact your employer's pay desk and your bank immediately; nothing here substitutes for their error-resolution process.