Payment settlement SLAs: what to agree before choosing a processor

A promise of next-day settlement needs a defined starting event and an ending event. Ask whether the clock begins at authorization, capture, batch submission, or another point, and whether the promised result is an available processor balance, a payout being sent, or money reaching the bank. These are different events, and finance needs the event that makes the cash usable.

Stripe's documentation distinguishes payout schedules and settlement timing and describes how country, payment method, and other factors can affect payouts. Use that distinction when evaluating any provider; do not assume Stripe's particular timetable applies to a different product or merchant account. Write down the contractual definition for your legal entity and the payment methods your customers actually use.

Ask how business days, weekends, public holidays, cutoff times, and time zones affect the expected date. Use a sample transaction captured late on a Friday, one taken before a local holiday, and one settled in a different currency. The provider should explain the sequence without switching between calendar days and business days halfway through the answer.

Compare the expected arrival with payroll, inventory purchases, and supplier commitments. A regular payout may still arrive too late for the bank's payment cutoff. Keep a forecast buffer based on the business's own obligations and observed settlement behavior. Do not count a scheduled release as cash already available to spend, especially during onboarding or a period of unusually high sales.

Discuss reserves, risk reviews, refunds, disputes, and negative balances before comparing only the headline payout speed. Request the conditions that apply to your account, the way amounts are calculated, and how releases appear in reports. Do not assume a reserve has a guaranteed release date unless the agreement establishes one and its conditions are understood.

For an illustrative cash-planning case, a merchant expects $20,000 of sales proceeds but the provider retains $2,000 under the account's reserve arrangement. The forecast needs the expected net receipt and a separate record of the held balance. That illustration is not a typical reserve rate. The actual terms may use a different amount, timing, or calculation and should be reviewed with the provider.

Ask for a sample settlement file and the corresponding bank reference. Finance should be able to connect gross payment activity, fees, refunds, disputes, and adjustments to the payout total. Stripe provides payout reconciliation reporting, while Adyen documents settlement reconciliation using its reports. Check the reporting tools and fields available for the product you will buy, including any plan or integration requirements.

Test a payout spanning a reporting cutoff. A sale captured in one month may reach the bank in the next. Your accounting team needs the transaction dates and the settlement trail to explain the intervening processor balance. Request stable identifiers and downloadable history so a changing dashboard does not leave the company unable to reconstruct an older deposit.

Ask how a failed or returned payout is reported, who can correct bank details, and what verification is required before another attempt. Confirm whether the retry receives a new identifier and how both attempts appear in reports. Avoid a workflow in which an emailed account change is enough to redirect funds without independent verification and appropriate approval.

Identify an escalation route for a material missing payout, the information support requires, and the response commitment in your agreement. Response time and resolution time are different promises. Keep processor transaction references, the payout identifier, expected date, bank evidence, and case history together. That makes the problem actionable and prevents the same missing payment from being investigated repeatedly by different teams.

During an approved pilot, compare actual capture, availability, payout, and bank-credit dates with the agreed definitions. Include ordinary sales, refunds, a weekend, and any payment method material to the business. Separate a timing exception from a reporting problem. A payout can arrive correctly while finance still lacks the details needed to reconcile it.

Use the result to finalize the operating calendar and assign someone to monitor deviations. Recheck terms after adding a country, currency, entity, or payment method, since the earlier timing may not carry across. The useful SLA leaves the company able to forecast cash, explain a delay, and escalate it with evidence. An attractive headline cannot perform those jobs without the underlying definitions and reporting.