A SaaS bank-debit payment is still processing: choose the right follow-up

Retrieve the payment record linked to the invoice and check its current state, submission date and any required action. A payment still processing needs different follow-up from one that has failed. Confirm whether the integration is showing the latest processor state or an older event before asking the customer to start again.

Stripe describes ACH Direct Debit as a delayed-notification method, with success or failure acknowledgement that can take several business days. It also explains that the method is not guaranteed. Use the actual payment's status and applicable timing information rather than applying the immediate-response expectations of a card payment.

Record the invoice balance, payment-attempt identifier and amount being processed. Check for another attempt or a separate transfer already associated with the same obligation. Customer support should see that a payment is underway before sending a reminder that implies no action has been taken.

If the customer offers to pay by card while the debit remains pending, have the payments owner establish what can safely be done with the original attempt. Explain the situation accurately and follow the supported process. A second payment may resolve an urgent need, but it also requires a plan to identify and correct any eventual duplicate receipt.

Decide how the business handles access while an authorized debit is processing, consistent with the agreement and risk policy. Record who can approve an exception and when it will be reviewed. Avoid letting a technical invoice status independently decide a commercial question that the team has never discussed.

For illustration, a renewal debit submitted just before a weekend may still be processing when an automated overdue reminder runs. Review the payment timeline and configured behavior before escalating the account. If the business permits continued access during processing, verify that the product and support systems reflect that policy without marking unconfirmed funds as collected.

Track the relevant stages in the cash reconciliation. Stripe distinguishes the timing of funds becoming available in its balance from the payout schedule that moves them to the business's bank. A successful customer payment and a bank deposit are therefore related events with potentially different dates.

Use supported expected dates in the forecast and identify uncertain items separately. If the payment later fails or is returned, update the invoice follow-up and cash expectation from the actual event. Preserve the original attempt so the accountant can explain the sequence rather than seeing an unexplained change from paid to unpaid in a later export.

Maintain a short list of processing payments with amounts, submission dates, current status and owners. Escalate items outside the expected process using the provider's support route. Once an outcome is confirmed, reconcile the invoice, customer communication and any subsequent collection attempt.

Review whether reminders, access changes or manual follow-ups created unnecessary customer friction during the delay. Adjust the workflow where evidence shows a problem, and test it with a representative delayed payment. The completed process should collect the authorized amount once, preserve the customer's service decision and give finance a traceable path from attempt to cash.