Business Receivables Management: Cash, Data and Controls

Match collection methods to how customers actually want to pay

Business customers may pay by ACH credit, ACH debit, check, card, wire or an online portal. The best collection mix reflects invoice size, customer type, urgency and cost. For a recurring $500 subscription, ACH debit may reduce manual follow up. For a $500,000 commercial invoice, the customer may prefer ACH credit or wire. For retail sales, card acceptance may be unavoidable even though processing cost is higher.

Segment the receivables book rather than forcing one method on every customer. Review payment volume, average amount, days to payment and processing cost by channel. A company can encourage lower cost electronic methods for routine invoices while retaining checks for customers that still require them. The objective is not to eliminate every old rail. It is to reduce friction and uncertainty for the largest and most frequent cash flows.

Measure the time from customer action to usable cash

Settlement speed should be measured from the customer’s payment action to funds that the business can use, not merely to the moment a portal says paid. Mail time affects checks, processor funding affects cards, and ACH settlement depends on the entry and schedule. A method that appears fast at initiation can still create a day of hidden float if the provider batches late or the bank places a hold.

Build a simple metric for each channel: customer initiated date, bank credit date and availability date. If mailed checks average four days from customer mailing to usable cash while lockbox reduces that to two, the improvement is measurable. If card sales settle next day but net of fees and chargebacks, the cash forecast should use the net settlement pattern. This data helps treasury improve working capital without guessing.

Capture remittance data with the payment wherever possible

Cash application becomes expensive when finance receives money without enough information to identify the invoice. Encourage customers to include invoice numbers or structured remittance data in ACH and wire instructions. Lockbox services can capture check and remittance documents, while merchant processors can provide order references. The exact technology matters less than preserving a reliable link between payment and receivable.

Measure unapplied cash daily. If $180,000 sits in the bank but accounting cannot identify the customers, the business has cash but poor receivables visibility. Create rules for common partial payments, deductions and consolidated remittances. The accounts receivable team should not need to search email each morning to explain bank deposits. Better payment data shortens reconciliation and gives credit teams more accurate information about which invoices are truly outstanding.

Design for returns, chargebacks and deposit exceptions

Every collection rail has exceptions. ACH debits can return, card payments can charge back and checks can be returned or duplicated. Treasury should define how each exception is routed to accounts receivable and when the customer account is reopened. A returned payment that remains marked paid in the accounting system creates false cash and credit information.

Use reason codes and aging. If an ACH debit returns for insufficient funds, the follow up may differ from an unauthorized return. If a remote deposit check is rejected because the image is unreadable, the team may be able to rescan it. A card chargeback may require evidence by a specific deadline. The process should prevent a failed collection from disappearing into a generic bank fee account at month end.

Protect inbound payment channels from fraud and account misuse

Receivables are not risk free simply because money is coming in. Fraudsters can use unauthorized ACH debits, counterfeit checks, stolen cards or manipulated refunds. Businesses also face credit push scams where customers are tricked into sending to fraudulent instructions. Protect any communication that tells customers where to pay. Changes to the company’s receiving bank account should use authenticated channels and advance notice.

Monitor unusual refunds and outbound corrections because a compromised receivables system can become a route for money to leave the company. For remote deposit, secure physical checks after scanning and destroy them according to policy after the retention period. For merchant services, restrict who can issue refunds or change settlement accounts. Inbound cash management and outbound fraud control are linked through the same systems and users.

Build the daily cash position from reconciled receipts

Treasury needs a reliable view of what actually settled today. Combine bank reporting, lockbox files, ACH receipts, card settlement and remote deposit into one daily cash view. A company using several banks should distinguish available balance from ledger balance and know which receipts are still pending. This is the foundation for deciding how much cash can be swept, invested or used to pay debt.

Track the portion of receipts that automatically post to customer accounts. If 92 percent of daily cash is matched without manual work, focus improvement on the remaining 8 percent rather than redesigning the whole process. Receivables management succeeds when collection speed, data quality and treasury visibility improve together. Faster settlement that produces more unexplained deposits is not a complete improvement.

Editorial Verdict

Sources

• Federal Reserve FedACH Services
• OCC Payment Systems handbook
• FDIC remote deposit capture risk guidance

Primary, regulatory and payment network sources were checked for this update. Bank specific terms can change after publication.