The bank portal is unavailable before a payment run

Record the error, affected users and time observed. Check the bank's known status or support channel using a saved contact or the institution's established website. Avoid following a fresh sign-in link from an unsolicited outage message. Determine whether the problem affects one user, the portal generally or the payment service itself.

A portal failure can hide the status of instructions already submitted. Before preparing a replacement, list the last acknowledged payments and any that were being submitted when access failed. Ask the bank to confirm those references. Treat unknown status as an unresolved item, not proof that the instruction failed.

Use the bank's verified account-recovery process for a locked user or unavailable authentication device. Keep the authorized administrator involved. Sharing another employee's password or approving an unfamiliar authentication prompt can turn an access problem into a security incident. If compromise is suspected, tell the bank immediately and follow its incident instructions.

FFIEC guidance treats authentication, access monitoring and layered controls as related protections. A continuity procedure should preserve those protections. Establish a backup authorized user and recovery contact in advance; it is harder to arrange legitimate authority during the hour before a payment cutoff.

Where the business uses a nonbank banking interface, identify the provider and the bank that holds the funds. The FDIC notes that technical problems with nonbank services can impede access. Ask which party can answer balance and payment-status questions under the actual arrangement. Do not assume the underlying bank can accept direct instructions from every platform customer.

Review the payments due before the expected restoration time. Identify which require immediate escalation and which can wait without changing an obligation. Contact the payment owner to assess consequences, including payroll, tax or contractual considerations. The bank's outage does not itself establish a revised legal due date.

Ask the bank about an authorized alternative, such as its documented assisted-payment process or an already approved backup channel. Confirm required signatures, verification, fees and cutoffs. Do not create an improvised route through an employee's personal account or another entity's funds without proper authority and advice.

Choose one person to coordinate releases across the normal and fallback channels. Record which pending instruction has been canceled or confirmed failed before creating a replacement. If cancellation cannot be confirmed, discuss the risk with the authorized finance lead and bank rather than assuming a duplicate can easily be recalled.

Download the bank activity and payment acknowledgments as soon as normal access is restored. Match them to the exception log, including manual instructions and any fees. Check for queued payments that processed after the fallback was used. Resolve duplicates and missing items promptly with the bank and the relevant recipient. Review unexpected beneficiary changes and user activity during the interruption as well. If the original cause remains unexplained, preserve the access logs available to the company and ask the bank whether further investigation is needed.

Document the actual duration, affected service and steps that worked. Update contact details and backup-access arrangements, then close temporary permissions. Give the accountant a complete payment history so the monthly reconciliation reflects what happened during the interruption rather than only what later appeared in the restored feed.