Cybersecurity
The Vendor Changed Banks: A Year-End Payment Checklist for Northeast Louisiana Businesses
November 20, 2026 · 8 min read · Josh Haber

A clean email and a correct logo are not proof the bank account changed. A callback checklist for owners and bookkeepers in West Monroe, Monroe, Ruston, and Northeast Louisiana before the next ACH goes out.
A supplier you have paid for years sends a short note the week before Thanksgiving. New bank. Please update the ACH before the next draw, the parts statement, or the insurance premium. The logo is right. The thread looks familiar. Someone is trying to clear the queue before the holiday.
That note is the ordinary shape of business email compromise. The FBI's 2025 Internet Crime Report, released in 2026, recorded 24,768 of these complaints and $3,046,598,558 in reported losses. That is about $123,000 per complaint. The figure counts only what people filed with the Internet Crime Complaint Center, and the losses are real invoices.
Microsoft's Digital Defense Report, published October 1, 2026 and covering July 2025 through June 2026, puts a second number beside that one. Microsoft detected more than 46 million business contact impersonation attacks in the prior 12 months: messages where someone pretends to be an owner, a coworker, a vendor, or a payroll contact. The opening message got quieter. The share of first messages that asked for money or a document fell from 17% in October 2025 to 3% by June 2026. "Do you have a moment?" comes first. The bank account comes after someone replies.
If you run a company in West Monroe, Monroe, Ruston, or Bastrop, and the bookkeeper is also the office manager, you need that rule written down before the Friday rush.
Why year-end is when this lands
November and December stack payments that are easy to hurry: a draw before the shutdown, a clinic's suppliers and insurance renewal, a dealer's parts statements, bonuses and prepaid expenses so the year closes clean. Each one is a normal week here, and a believable reason to skip a phone call.
The request shows up in three ways. All three use the same rule.
The mailbox is real, and someone else can read it. The attacker has a session, an inbox rule, or an app the company already approved. The message continues an old thread. Multifactor authentication may already have been completed by the real user. Adversary-in-the-middle phishing is built for that: the user finishes a normal sign-in, and the attacker keeps the session. MFA still belongs on every account. It does not read the routing number about to be saved. The identity article on this blog covers the login. The October article on app permissions covers the forward or extra app that can remain after a password change.
The mailbox is fake, and the name is real. A lookalike domain, a display name, or a QR code on a phone the office filter never sees. During that same year, Microsoft detected more than 145 million QR-code phishing attacks in Defender for Office 365. A phone in a truck is outside the filter on the office PC.
The vendor is real, and their mailbox was the one taken over. Your mail protection did its job. Theirs did not. The invoice number is right because the attacker read the thread. What they do not have is the phone number you saved last quarter from a bill you already paid.
Payroll sits on the same page. A direct-deposit change, a bonus sent to a "new account before Friday," or gift cards from an owner who is "in a meeting" is the same request with a shorter story.
The one-page rule
Hand this to the person who pays bills. An owner does not have to live in the bank portal. An owner does have to back the employee who slows a rush down.
- No change to where money goes without a callback. That covers ACH, a wire, a cashier's check, payroll direct deposit, and a new vendor's first payment. An emailed W-9 goes in the file. The callback is the phone call.
- Keep a vendor card outside the inbox. Record the legal name, the last four digits of the account you already pay, and a phone number from the contract, a statement you verified earlier, or a main line you have dialed before. A shared spreadsheet is fine when only a few people can edit it. The inbox is the wrong cabinet. That is the box the attacker is reading.
- Call the saved number. Leave the number in today's signature unused, and skip the reply that asks "is this really you?" Read the new routing and account numbers to a person you can name. Write the date, that name, and the number you dialed on the request before anyone saves the change.
- A Teams chat, a text, or a reply on the same thread does not count. Microsoft reported a 502% year-over-year rise in confirmed malicious voice-phishing activity over Teams in this period. A familiar voice, or a chat that says "yes, use the new account," can belong to the same person who sent the email. Dial the number you already had. If the only number in the building is the one in the message, stop and use a second source: the vendor's published main line, a prior statement, or the owner who hired them.
- Slow down the opener that asks for nothing. When a note from a vendor, an owner, or HR starts with "Are you at your desk?" and the next note is banking, payroll, or gift cards, use the known number before anyone answers. Pausing on a strange link still matters. A perfect thread needs this other pause.
- In a larger office, the person who edits the vendor record should not be the only person who releases the payment. In a five-person company, the owner looks at every bank-detail change before it is stored. Write that down, so nobody is left to "just get it out" from a job site in Sterlington or Ruston.
- Put a dollar figure in the rule that matches a normal week. Under that line, a changed bank account still gets the callback. Over it, two people sign off. A new vendor gets the callback even when the first bill is small. The modest payment is how a new account becomes a trusted one.
- Ask whoever runs Microsoft 365 three questions this month. Can a mailbox forward mail outside the company without anyone noticing? Does external mail show as external? Do you publish DMARC, so a customer is less likely to get a fake invoice that appears to come from your domain? Those settings shrink the easy path. The phone call stays. If NewRockIT manages the tenant, the review is part of the work. If someone else does, the questions are fair to send.
- When the money has already moved, call the bank the same day, then file at ic3.gov. Name the payment, the account, and the time it left. That call is the recovery step the office still controls.
Myths that get a real invoice paid to the wrong place
- "It was on the existing thread." A stolen mailbox continues the thread. The thread is context, not proof of who is typing.
- "They knew the invoice number and the job name." Anyone reading the mailbox knows both.
- "MFA is on, so this cannot happen here." MFA stops a large share of simple password attacks. Stolen sessions, and a prompt the user already approved, are documented ways past the second factor. Keep MFA. Put the callback beside it.
- "The bank will catch it." Banks stop some fraud. They also release an ACH an employee approved.
- "We would have noticed the grammar." The Microsoft figures say the first message usually asks for nothing. Judge the request to move money.
- "We are too small for this." A materials payment, a parts statement, or one payroll change is a normal amount. The FBI total is large because the payments belong to ordinary companies.
- "The email filter replaced the callback." A filter cannot see that a supplier's real account was taken over last night, and it cannot see a QR code scanned on a phone.
How NewRockIT fits
The payment rule belongs to the owner and the bookkeeper. What we take is the mailbox, so fewer of these notes arrive inside a thread the office already trusts.
On tenants we manage, that is identity, mail protection, a look at forwarding rules and app consent, and a direct answer when a sign-in or a rule looks wrong. A filter that catches a lookalike domain earns its place. A mailbox that is both Global Admin and the accounts-payable login does not.
The phone call stays in the process, and the hours stay honest. Human support is Monday through Friday, 8:00 AM to 5:00 PM Central. Monitoring of covered systems can run continuously. The person who sits down with the bookkeeper is the same founder who administers the tenant, whether the office is a shop in West Monroe, a clinic in Monroe, a contractor in Ruston, or a remote team on the same Microsoft 365 setup.
The bottom line
The useful year-end project is a phone number saved before the email arrives, and a bookkeeper who is allowed to use it when the note says urgent. The FBI complaint totals and Microsoft's 2026 report describe the same pattern: a trusted name, a quiet opener, and a real payment. MFA, mail protection, and a backup you have actually restored still belong in the plan. The question later is who approved the new account. The callback is the answer.
Related: Cybersecurity services · Contact NewRockIT


