CFO weekly payment KPI review

The CFO looking at payments quarterly is looking at history. The CFO looking at payments weekly is steering. For multi-brand operators where payment fees are the second- or third-largest line item on the P&L and freeze risk is existential, the weekly review is where finance earns its keep.

Here are the twelve KPIs that belong on the weekly CFO dashboard, the thresholds to alert on, and what escalation means for each.

1. Blended effective rate, last 7 days

Total fees / total volume across all brands, all processors. Alert if week-over-week delta > 10 bps. Root cause: downgrade rate climbing, interchange category shift, or hidden assessment fee.

2. Net settlement delta

Expected settlement vs actual, per bank account. Alert on any shortfall > 2% of daily volume. Root cause: payout delays, reserve increases, or processor holding funds silently.

3. Reserve balance trajectory

Total reserve held across all acquirers. Plot week-over-week. Alert on any single-acquirer increase > 1% of MTD volume. Reserves creeping up without a volume reason is leading indicator of acquirer concern.

4. Decline rate, all brands

Failed auth attempts / total auth attempts, last 7 days. Alert if any brand > 12% or week-over-week delta > 2 points. Root cause: issuer BIN block, descriptor degradation, or fraud model drift.

5. Chargeback rate by brand

Disputes opened / transactions settled (30-day trailing). Alert at 0.7% count or 0.9% dollar. Above 1.0% is card-brand program territory. See chargeback ratio guide.

6. Subscription rebill success

First-attempt rebill success rate. Target 85-92%. Alert if under 80% or week-over-week delta > 3 points. Dunning recovery audit triggers.

7. Refund rate

Refunds issued / transactions settled, weekly. Alert if > 6% or week-over-week delta > 1.5 points. Refunds climbing predicts chargebacks climbing 30-60 days later.

8. Working capital lock-up in reserves

Dollar value of all reserves / monthly volume. Benchmark: 15-30% for high-risk operators, 5-15% for standard. Climbing means capital efficiency dropping. See reserve calculation.

9. Processor concentration

% of weekly volume through largest single processor. Alert at 70% (concentration risk) and 90% (single-rail existential risk).

10. Dispute win rate, rolling

Won disputes / resolved disputes (30-day trailing). Alert if under 25%. Low win rate means rebuttal templates are weak or documentation is thin. See rebuttal playbook.

11. Open dispute queue

Disputes pending response. Alert at > 10 per brand. Response window is tight — missed responses are auto-losses.

12. Cash-to-settlement gap

Days of volume in-transit at any processor. Alert if > 5 days or 1.5x contract terms. Payout delays hurt working capital immediately.

How the review actually runs

15-20 minutes pulling data (or zero if dashboards are automated). 10 minutes reading the deltas and deciding what is red vs yellow. 5 minutes writing the Monday action list. The output is a Slack message to ops: "These three items need action this week, here's the first step on each, status update by Friday."

What to do with red items

• Effective rate jump: Pull interchange detail, identify downgrade reason, fix cart-side.
• Reserve increase without cause: Call the AOR rep, demand explanation, document.
• Decline rate spike: BIN analysis, descriptor audit, fraud tuning.
• Chargeback spike: Product quality review, refund policy audit, fraud tool tuning.
• Open dispute queue climbing: CS staffing review — someone is not responding.

Monthly rollup

At month end, aggregate the weekly reviews into the P&L commentary. CFOs who have weekly data write 2-paragraph narratives about payment cost. CFOs who look quarterly write "rate went up a bit, investigating."

The COO counterpart

The COO is running an 18-item monthly review on the same underlying data but looking at different cuts — vertical, brand, processor. CFO focuses on cash, rate, and concentration. COO focuses on operational signal. Together the two reviews catch 95% of issues. See COO monthly checklist.

What a well-run dashboard looks like

One screen, 12 tiles, colored red/yellow/green with trendlines. Shareable Slack snapshot. Threshold alerts auto-fire to email. Nothing more. CFOs who have tried to turn this into a BI project have ended up with worse dashboards than the quick weekly version.

Where this lives in the stack

Most operators build this in Looker, Mode, or a Google Sheet fed by Stripe/processor APIs. Orchestration platforms like multi-flow.pro provide the consolidated view out of the box. See pricing for the dashboard model, or apply for a weekly-review fit assessment on your current stack.

13. The Monday 9am cadence

Most effective teams run this review Monday mornings at 9am — early enough that red items can trigger action in the same week, late enough that weekend data has settled. 30 minutes; same attendees every week; same dashboard; decisions made real-time. Schedule discipline beats sophisticated tooling.

14. Integration with the executive dashboard

CFO compiles the weekly into a monthly narrative for CEO and board. Three bullet points: major movements, leading indicators, action items in flight. Board appreciates the trend line more than the absolute number. "Effective rate flat; chargeback ratio down 8 bps; processor concentration unchanged at 68%" is the one-paragraph update that builds trust over quarters.

15. Alerting versus reviewing

Real-time alerts (Slack, PagerDuty) fire for threshold breaches. Weekly review is for trends that alerts miss. Different instruments. Both needed. Operators who rely only on review miss same-day events; operators who rely only on alerts lose the pattern view.

16. When to bring ops in

Monthly ops handoff is the right cadence for most items. But acute issues (reserve increase notice, VIRP approach, sudden chargeback spike) need same-week ops engagement. Weekly review is where the CFO decides what to hand off vs what to watch another week.