ACH PAYMENT OPERATIONS
Submission is only the beginning of an ACH payment; authorization, settlement, returns and reconciliation still need owners.
ACH can fit the right invoice or recurring workflow, but a submitted entry can still settle later, return or need customer follow-up. Keep authorization, status and reconciliation in one explainable cycle.
See How the Review WorksAUTHORIZED→SCHEDULED→SUBMITTED↔SETTLED / RETURNED
HOW AN ACH PAYMENT MOVES
Follow the payment past “submitted.”
The hard part is not sending the entry. It is knowing what the customer authorized, when the status changed, who owns a return and which record closes the balance.
WHAT MUST NOT BREAKA submitted ACH entry should not be treated as final revenue before settlement or return status, customer communication and accounting ownership are clear.
THREE ACH USE CASES
Invoices, recurring debits and account collections need different ACH controls.
A customer pays a known balance
Keep the invoice, authorization, entry, receipt and balance adjustment connected.
The schedule repeats
Keep terms, amount changes, cancellation, account updates and failed-payment handling visible.
A business manages ongoing receivables
Define who monitors status, handles returns and closes the customer and accounting records.
THE STRESS TEST
A return should not send your team hunting for the original authorization.
Map the full distance between customer permission, the submitted entry, settlement or return, follow-up and the final ledger result. The exact rules and timing depend on the entry type and provider.
AUTHORIZATIONWhat the customer approved
ENTRYWhat was submitted and when
STATUSPending, settled or returned
RESOLUTIONNotify, correct and reconcile
WHERE THE DECISION BREAKS
Catch the missing authorization, return or reconciliation step before the balance is closed.
Submitted becomes “paid” too early
The balance closes before the return window and final status are understood.
Return code has no owner
The processor report changes, but billing, support and accounting do not.
Retry becomes a guess
The team resubmits without a clear rule, notice, authorization basis or record of the prior return.
WHAT A REVIEW COVERS
Start with the authorization. End with the settled—or returned—record.
MERCHANT INPUT
Trace one authorization and outcome
Bring the agreement or invoice, authorization, debit schedule, settlement or return, notices and accounting close.
DATA ONE WORK
Map authorization, submission and returns
Assign ownership to each pending, settled, returned and customer-follow-up state.
NEXT STEP
Give every state a next action
State what can stay and what must change before a submitted entry can close the balance reliably.
You leave knowing which authorization, status or reconciliation step needs attention. Entry rules, timing and provider requirements still require confirmation.
QUESTIONS BEFORE DECISIONS
Before relying on ACH, resolve these six operating questions.
When does ACH make sense for a business?
ACH can fit invoice, recurring or account-based payments when the customer authorization, timing, return handling and reconciliation process are clear. Compare it with card and check workflows rather than treating it as an automatic replacement.
Is an ACH submission the same as final payment?
No. A submitted entry may settle later or return. Keep the pending, settled and returned states visible until the bank, customer and accounting records agree.
What authorization record should we keep?
Keep the authorization method, terms, amount or calculation, timing, cancellation process and customer record required for the proposed entry type. Exact requirements need qualified review.
How should ACH returns be handled?
Assign an owner for the return code, customer notice, account update, retry decision, fee treatment and accounting correction. Do not assume every returned entry may be retried.
Can card and ACH live in the same billing process?
They can share an invoice or customer record, but authorization, timing, decline or return handling and dispute paths differ. The workflow should keep those differences visible.
What should we bring to an ACH review?
Bring one agreement or invoice, the authorization language, payment schedule, return examples, customer-support steps and the processor and accounting reports for a complete cycle.
A clear next step