TL;DR: The revenue dashboard will say the weekend went great days before the bank account agrees — payouts lag sales, processors can hold rolling reserves against spiking volume, and a slice of the weekend’s orders will be contested well into the new year. The cash playbook: map the settlement calendar before the weekend, keep fraud screening honest at volume (manual review the weird big ones, don’t blanket-decline), treat refunds as the cheap alternative to chargebacks, and fight the chargebacks you can win with the evidence you set up in advance — delivery confirmation, clear descriptors, documented policies. BFCM has two scoreboards; this is the one that pays the January bills.

Two weeks from now, every e-commerce group chat fills with revenue screenshots. This post is about the other scoreboard — the one that determines whether the weekend’s number survives contact with settlements, reserves, fraud, and the chargeback window that stays open long after the ads stop.

Payouts: the lag is a plan item, not a surprise

Sales land Friday. Settlements land on your processor’s schedule — days later at the best of times, stretched further by US Thanksgiving banking closures sitting right in the middle of the weekend. Meanwhile the weekend’s costs clear immediately: ad accounts bill as they spend, shipping labels charge at purchase, staff get paid on payday regardless.

We flagged the shape of this in the BFCM ops checklist; the specific November 20 action is a one-page settlement map: expected payout dates by channel for sale-weekend volume, against the committed outflows of the same ten days. If the map shows a squeeze, the fixes are all easier now than mid-squeeze — delay a discretionary payment, pre-arrange the line, or simply know and relax.

Reserves are the sharper version. Processors manage their own risk, and a store suddenly doing many multiples of normal volume — especially a newer store, or one whose dispute rate has been creeping — can find a rolling reserve applied: a percentage of payouts held back for weeks or months. You reduce the odds by looking like what you are (a planned promotion, not a bust-out): keep your processor profile current, and for very large planned spikes on smaller accounts, telling your processor in advance is a real thing that real merchants do.

Fraud at volume: screen like it’s your money, because it is

Card-not-present fraud concentrates exactly where attention dilutes — peak weekends. The failure modes come in pairs: wave everything through and eat the chargebacks (card networks put the liability on the merchant for most online fraud), or panic-tighten the filters and decline a pile of legitimate unusual-looking orders at the highest-intent moment of the year.

The balanced setup, configured before the rush: platform fraud scoring respected (actually look at the high-risk flags rather than bulk-approving the queue), a manual-review lane for the orders worth a human minute — unusually large baskets, mismatched billing/shipping on high-value orders, rush shipping on brand-new accounts, multiple cards against one address — and known-good signals (returning customers, matched addresses) left unharassed. The goal isn’t zero fraud; it’s keeping fraud losses inside the allowance your October margin math already priced, without strangling conversion.

One specifically evil seasonal pattern deserves its own line: triangulation and reshipper fraud spike in Q4, and so does plain friendly fraud — real customers disputing real purchases in January when the credit card bill arrives. The defence for that one is the next section.

Chargebacks: the January tax on a December weekend

A chargeback costs you the product, the revenue, a fee on top, and a tick against your dispute ratio — the metric that, pushed too high, triggers the monitoring programs and reserve conversations above. Q4 orders generate their disputes on a lag, landing December through February. The playbook:

Prevent the preventable. Most non-fraud disputes are communication failures wearing a dispute costume: a billing descriptor that doesn’t match your store name (“what is this charge?”), shipping promises missed without proactive emails, a return process hard enough that the cardholder’s bank felt easier. Every one of those is a settings-and-template fix available this week — and it’s why the ops checklist had you publish cutoffs and pre-write support macros.

Make refunds easy — strategically. A refund costs the margin; a chargeback costs the margin, the fee, and the ratio. For low-value disputes-in-the-making, the fast refund is frequently the profitable move, however it feels in the moment. Decide the threshold policy now (“under $X, resolve instantly”) so the support team isn’t making margin calls one ticket at a time.

Fight the winnable with pre-built evidence. Representment succeeds on documentation: delivery confirmation with signature where stakes justify it, order metadata (IP, device, address match), the customer’s account history, your displayed policies, and any support correspondence. Stores that win disputes aren’t luckier; they set up the evidence trail before the orders happened and respond inside the deadlines with a tight packet. Friendly-fraud disputes on delivered, confirmed orders are very fightable. Actual stolen-card fraud usually isn’t — eat it, tune the screening, move on.

Watch the ratio weekly through the season. Dispute rate sits beside contribution margin and CPA on the weekend’s real dashboard. It’s the earliest warning that something upstream — a descriptor, a shipping promise, a product listing overpromising — is manufacturing January problems at December volume.

The bookkeeping that holds it together

All of this lands, finally, in the books: the weekend’s settlements arriving net of fees, refunds, reserves and disputes are the most complicated payouts of the year — precisely the settlement-versus-revenue problem from our Shopify bookkeeping post at maximum intensity. If A2X-style channel accounting is in place, December’s reconciliation is routine and January’s HST remittance (funded by the automatic set-asides, right?) is a transfer, not a trauma. If the books still run on “deposit equals revenue,” this is the month that decides to fix it — because this is the month the gap gets expensive.

Frequently asked questions

How long after BFCM until I actually have the cash?
Typically days per payout cycle, extended by the US holiday calendar, with marketplaces running their own (often slower) settlement schedules — and any reserve stretches a slice of it to weeks or months. Build the map from your actual processors’ published schedules; it’s a thirty-minute exercise that de-dramatizes December.

What dispute rate gets me in trouble?
The card networks’ monitoring thresholds sit around the high-zero-point-something percent of transactions, with programs and penalties beyond them — but practical trouble (reserves, holds, nervous processors) starts well below the formal lines. Treat anything trending toward half a percent as a fire worth finding.

Should I require signature on delivery for everything during BFCM?
No — friction costs more than it saves at low order values. Set a value threshold where signature/confirmation kicks in, use tracked shipping universally (tracking data is chargeback evidence), and reserve the heavy verification for the manual-review lane’s flagged orders.

Is it worth fighting chargebacks or should I just accept them?
Triage: genuine stolen-card fraud, concede and tune screening; friendly fraud on confirmed-delivered orders, fight — win rates with good evidence packets are meaningfully high and the ratio benefits either way from fewer repeat offenders. The deciding factor is evidence you either collected automatically or didn’t.

My processor emailed about a reserve. Panic?
No — respond. Reserves are risk math, and the inputs are negotiable over time: dispute ratio trending down, fulfilment proof, financials showing the spike was a planned promotion. Keep payouts mapped so the held percentage doesn’t surprise the cash plan, and revisit with the processor once the season’s data proves out.


The weekend’s marketing scoreboard takes care of its own publicity; the cash scoreboard is the one that needs an owner. YBL runs it for e-commerce clients straight through the season — settlement maps, reserve and dispute tracking, channel-true books, and a January remittance that’s already funded. If you want December’s numbers to mean what they say, that’s the service.

Get financial strategy insights for growing Canadian businesses including cash flow, tax planning, and operational finance. Delivered monthly.