Skip to content
INDEPENDENT FINANCIAL EDUCATION Clear explanations. Better questions.
EasyLoanWorld Your guide to financial clarity
Explore guides
Menu
FINANCIAL GUIDE Business Finance

Business ACH Debits: Report Quickly, Then Check Controls

Report a suspected unauthorized business ACH debit promptly, preserve the transaction details, and review bank controls while keeping legitimate supplier payments from being missed.

A black rotary telephone with its handset resting on top and a cord beside it.
Illustrative photograph by Quino Al / Unsplash (Unsplash License).

Estimated reading time: 8 minutes

Suspect unauthorized business ACH debits from your U.S. account? Contact your bank immediately using a verified business-banking or treasury-management contact. Don’t wait for the monthly statement or finish investigating every detail before reporting the suspected debit.

  1. Report the specific transaction. Give the amount, account, displayed originator and settlement information available. Say what you recognize and what you don’t; an unfamiliar description alone doesn’t establish fraud.
  2. Ask for the bank’s required next action. Confirm its reporting cutoff, the form or statement it needs, how to submit it and whether any immediate account protection is appropriate.
  3. Keep proof of the report. Record the time, time zone, contact, case number and acknowledgment. If the bank requests a written follow-up, submit it through the confirmed channel and keep that confirmation too.
  4. Assign a follow-up owner. Have one authorized person track the bank’s response and another review upcoming legitimate payments if controls are changed. Reporting the debit and adjusting future controls are separate tasks.
A compact incident record to prepare while contacting the bank
Record What to capture
Transaction Amount, displayed description, originator or company ID and trace/reference number if available
Timing When you discovered it, the settlement date confirmed by the bank and the applicable reporting cutoff
Authorization question Relevant vendor agreement, expected debit amount and why this transaction appears unauthorized or incorrect
Response Bank case number, required documents, submitted date/time and the next promised update

Use this record to support the report, not as a reason to postpone it. Ask the bank to identify information you can’t see in the online transaction description.

Business ACH debits: reporting isn’t the same as returning

SouthState’s ACH guidance describes a return deadline for unauthorized or improper corporate ACH debits: opening of business on the second banking day after settlement. That’s a deadline for the return, not permission for you to wait until then to report it.

For a customer-notification example, U.S. Bank’s deposit agreement, effective May 11, 2026, says to notify the bank by 5 p.m. Central Time on the business day after settlement for an unauthorized ACH debit under its business-customer provisions.

For example, if settlement is Monday and Tuesday is the next business day, that stated cutoff is Tuesday at 5 p.m. Central—not Wednesday. This illustrates that agreement, not every bank’s deadline.

Ask your bank to confirm the settlement date, reporting cutoff, required information and submission method. Keep its acknowledgment.

SouthState recommends daily transaction review and immediate escalation of suspected fraud. Review unfamiliar payees, unusual amounts and unexpected activity. Don’t substitute consumer-account timelines for these corporate-account rules.

Business ACH debits: keep reporting, investigation and account correction distinct

Suppose a business owner reports a questioned debit and receives a case number. That establishes a contact record. It doesn’t, by itself, establish that a return was completed, that money was restored or that the bank determined the debit unauthorized.

Keep the reported transaction and acknowledgment together, then add the bank’s actual request for any written statement or supporting records. If the bank supplies a cutoff, record its date, time and time zone exactly. Don’t replace it with a general timeline found for another bank.

If the statement is submitted later, retain its own confirmation. A phone acknowledgment and receipt of the written follow-up can be different events. Ask which required steps remain open rather than assuming the first case number proves the entire process complete.

When the account changes, record the actual posted amount, description and date. If the bank describes a credit as conditional or subject to review, preserve that qualification. The business’s cash record shouldn’t turn an unresolved process into a final recovery promise.

This organizer supplies no additional reporting period or extension. Contact the bank promptly, using the applicable business-account instructions, while gathering missing details. Completing a detailed internal investigation shouldn’t delay the initial report.

Business ACH debits: test the blocked-invoice replacement risk

Return to the fictional legitimate $1,250 supplier debit blocked because its ID was absent from the allowable list. Adding the verified ID addresses future debits under the cited Chase workflow. The particular invoice still needs its own payment resolution.

Suppose the supplier resubmits $1,250 while an employee independently sends a separate $1,250 replacement transfer. If both actually settle for that same invoice, account outflows total $2,500, which is $1,250 more than the single intended payment.

Keep two transaction rows with their actual references, dates and methods. Match each to the supplier’s account record. A replacement marked sent and a resubmission merely pending are different statuses; don’t treat both as final until the records support it.

The arithmetic identifies a possible duplicate payment under these assumptions. It doesn’t establish an immediate refund right, determine which transaction can be reversed or authorize withholding another invoice. Ask the bank and supplier how the actual entries will be reconciled.

If only one transaction settles, update the other row with its confirmed outcome rather than retaining a false $2,500 final outflow. An attempted payment that fails isn’t another completed payment, though any actual fee needs its own separate record.

Equal amounts can represent different bills

For an independent variation, suppose two legitimate supplier invoices each total $1,250 and two confirmed debits are properly assigned one to each invoice. Their $2,500 combined outflow isn’t a duplicate merely because the amounts and vendor match.

Use invoice identifiers, expected dates and transaction references to distinguish that case from paying one invoice twice. A rule that flags equal amounts can prompt review; it can’t supply the underlying transaction match.

If a vendor uses a changed company ID, verify the explanation through a trusted contact and check the bank’s actual service requirements. Don’t assume the familiar vendor name on an email establishes that a new ID or payment instruction is genuine.

Likewise, an existing allowable ID doesn’t prove every debit amount is correct. Keep the vendor agreement, expected amount or limit and account activity connected. A control setting and a transaction’s substantive authorization are separate questions.

Business ACH debits: assign responsibility for the next legitimate payment

When account controls change, give one authorized person responsibility for the disputed item and a named person responsibility for legitimate upcoming payments. Those may be different tasks even when the same bank contact helps with both.

Record which vendors could be affected, which invoices are unpaid and what confirmed payment route will be used. A broad note saying “ACH blocked” can conceal a supplier deadline or an expected payroll-related debit that still needs attention.

Ask what happens to exceptions if the usual reviewer is unavailable and which cutoff governs the actual service. Keep the bank’s answer with the procedure. Don’t assume every blocked entry will wait indefinitely for a manual decision.

After an incident, compare the bank activity, supplier ledger and internal payment record. Identify unresolved differences rather than creating a balancing adjustment simply to make totals agree.

The completed file should distinguish the suspected debit, report, actual account action, future control and each legitimate bill still needing payment. This supports prompt follow-up without turning a control change into a recovery guarantee.

Set controls without blocking legitimate payments

The Chase Connect debit-block guide describes blocking future ACH debits except those using allowable IDs. It allows vendor limits and review of blocked transactions. Before enrollment, identify legitimate vendors and the IDs needed to keep their debits working.

There’s an important distinction after a legitimate payment is blocked: Chase says adding the payee allows future debits only. The blocked transaction must be resubmitted; adding the payee doesn’t itself pay that bill.

For Chase Connect, the guide says transactions submitted after 9 p.m. Eastern from IDs not on the allowable list are automatically blocked without a decision opportunity. Verify your own service’s rules.

For example, suppose a legitimate $1,250 supplier debit is blocked because its ID wasn’t on the allowable list. In the Chase workflow described above, adding the verified ID addresses future debits; it doesn’t settle the blocked $1,250 invoice. Coordinate resubmission with the supplier and confirm the result before sending a separate replacement payment. Keep the vendor conversation and bank status together so the same bill isn’t paid twice.

Ask which controls your account supports, who will review exceptions and what happens when nobody responds. Check the bank’s decision cutoff. Don’t assume every transaction will remain available for manual approval.

For ongoing use, record each legitimate vendor’s verified ID, expected amount or agreed limit, review owner and backup contact. Recheck changes through a trusted vendor contact. An allowable-list entry is a control setting, not proof that every future debit from that vendor is the correct amount.

Sources checked October 25, 2026. These are bank-specific examples, not a universal reporting deadline or a recovery guarantee.

If an invoice payment is also in doubt, review payments made after bank details changed. Use a business bank reconciliation to keep the disputed debit separate from other outstanding items.