BFCM Client-Readiness Checklist for Accounting Firms

Black Friday doesn't break client books. It multiplies whatever was already wrong with them — and the multiplication is decided in September, not November.

---

The client meant it as good news. "Biggest Black Friday we've ever had — up forty percent." Then you opened the file in early December and saw what forty percent up actually looks like: nine days of payouts matching nothing, a few thousand individual sales receipts nobody can tie to a deposit, sitewide discounts that vanished somewhere between Shopify and QuickBooks, and a gift-card push sitting in November revenue where a liability should be. You fixed it in January — the month you had time for exactly none of it.

Most firms file that under seasonal weather: BFCM belongs to the clients. The firm's job starts when the dust settles. It sounds like humility. It's actually the lie that schedules your worst January every year.

Here's the mechanical truth: volume doesn't create a single one of those defects. It multiplies them. A store's books survive BFCM or don't based on configuration that is checkable right now, in September — which makes this a BFCM accounting firm client checklist rather than a cleanup guide: five checks per client, about an hour each, run while every fix is still routine work.

If you already run the October tax-season audit across your client book, this is the same prevention pattern moved one month earlier and pointed at one specific event. The two chain naturally: sweep for BFCM in September, audit for tax season in October, freeze in December.

Volume Multiplies Configuration — That's the Whole Threat Model

Every way an e-commerce file degrades is per-order. An unmapped product fails once per order that contains it. A per-order sync posts one more receipt per order. A gift card misbooked as revenue misbooks once per card sold.

At August volume, all of that is background noise — three failed rows in a log, a slightly bloated file, a small revenue overstatement. BFCM week can run a month of orders in five days. The same configuration now produces hundreds of failed rows, thousands of receipts, and a revenue misstatement big enough to change the client's tax picture — during the exact week the client is too busy to answer a single question.

And it's the same logic as the December freeze in the tax-season calendar: the worst time to change a client's books structurally is peak volume. September is the last calm month. Everything below should be finished before October ends.

The BFCM Accounting Firm Client Checklist: Five Checks per Client

Run these in order, per e-commerce client. The first four are file checks; the fifth is a conversation.

Check 1: Books current through August — the non-negotiable

Nothing else on this list works against stale books. You can't stress-test a recording method or verify a mapping when the last reconciled month is May — every check needs a known-good baseline, and every BFCM-week anomaly needs a clean "before" to be visible at all.

The check: the August close is done and locked. Payouts traced, clearing account at zero or composed of named in-transit payouts, sales tax tied out. The month-end close checklist for e-commerce clients is the 30-minute runsheet for exactly this.

If it fails: catch the client up now, at normal rates. A client three months behind in September is a client whose November will have to be reconstructed instead of verified — and reconstruction of a BFCM month is the single most expensive job in e-commerce bookkeeping.

Check 2: The recording-method stress test

This is the check most firms skip, and it's the one that produces the December horror files. A client syncing every order into QuickBooks as an individual sales receipt is tolerable at 400 orders a month. At BFCM pace, per-order posting becomes thousands of transactions in days: none matching any deposit, reports crawling, reconciliation reduced to forensic matching.

The check: for each client, note the sync method and the projected November volume. Any client at meaningful volume still posting per-order gets flagged for conversion to daily-summary posting — one journal entry per day, flowing through a clearing account to a payout match. The full method, with the worked example and account structure, is in how to record Shopify sales in QuickBooks Online.

If it fails: convert in September or early October, never later. A method conversion is a calm afternoon now — remap, verify one day's entry, done. The same conversion attempted mid-November is an engine swap in flight, on the client's biggest month, with no slow week to catch a misfire.

Check 3: The error backlog, cleared to zero

Sync errors are configuration failures wearing a per-order costume — "product not mapped," "customer not found" — and configuration failures scale linearly with orders. The three rows that failed quietly in August are the same three causes that will fail hundreds of times in BFCM week.

The check: open each client's sync error log and clear it — in LedgerPort, filter the Audit Log to Status: Error, and each row tells you which record never reached QuickBooks and why. Fix the causes, not the rows: add the mapping, create the customer, then re-push the affected records.

If it fails — and one more thing even if it passes: ask the client what's launching for BFCM. New bundles, limited SKUs, and doorbuster products don't exist in QuickBooks yet, which means the cleanest August log in the world says nothing about November. Get the BFCM catalog mapped as it's created, not discovered as an error wave on Black Friday morning.

Check 4: Discount and gift-card mapping, verified with a test order

BFCM is discount season, and Q4 is gift-card season — and both hit accounts that sit dormant the rest of the year, which is why nobody has looked at them since last winter.

The check, two parts. First, discounts: confirm the client's sitewide and code discounts post to a visible contra-revenue line rather than disappearing into a netted figure, so gross sales, discounts, and net revenue each survive into QuickBooks. Second, gift cards: confirm card sales post to a liability account and card redemptions draw it down — a gift card sold is cash received against a promise, not revenue, and a Q4 setup that books cards straight to income overstates the year's biggest month by the size of the client's whole card push. The full liability-to-redemption lifecycle is in our gift card and store credit accounting guide.

If it fails: fix the mapping now and reclassify the year-to-date balance while it's small. Worth knowing as you triage tooling: automatic liability handling for gift cards is uncommon in sync tools — LedgerPort does it on the Enterprise plan, issuing to and redeeming from the liability account as orders sync. For clients on other setups, this check is manual, and it's due before November either way.

Check 5: The cash conversation — the PO-vs-payout gap

The first four checks protect the books. This one protects the client, and it's where the sweep turns into advisory work.

Here's the gap: BFCM inventory gets paid for in September and October — purchase orders, deposits, freight — while the revenue doesn't land until late November, the payouts days after that, and January claws some back as returns. The result is a cash trough in October that arrives precisely when the client's dashboard says they're about to be rich. Clients who don't see it coming fund it badly: emergency credit, delayed supplier payments, or a canceled reorder that costs them the season's second wave.

The check: does this client know, week by week, where their cash low point is? If not, September is the month to build them a 13-week cash forecast — a genuine, billable deliverable, and the conversation most likely to make a client call yours "the firm that saw it coming."

The Capacity Math: BFCM Aftermath Is January's Workload

Now the arithmetic that makes this a partner-meeting decision rather than a nice idea.

The sweep costs about an hour per client — call it a day and a half of one senior's September, billable as the advisory work it is. Flagged fixes (a method conversion, a mapping cleanup) add a few calm hours each, also at normal rates.

Skip it, and the same defects come back as January work — ten to twenty reconstruction hours per broken file, landing in the exact weeks the tax-season pile-up already owns, displacing prep hours you'd already sold. Same defects, same fixes; the only variable is whether you buy them at September prices or January prices.

The September Email That Positions the Firm

The sweep only lands if clients experience it — so don't just run it, announce it. One email, sent this month, does more for retention than most quarterly reviews:

Subject: Getting [Store] ready for Black Friday — our side of it

Ahead of BFCM we're running a readiness check on your books this month: confirming everything is current through August, stress-testing how your sales post to QuickBooks at holiday volume, clearing any sync errors, and verifying discounts and gift cards are set up to record correctly. Most of this needs nothing from you — we'll flag anything that does.

Two things on your side: send us your BFCM product list when it's final so new items are mapped before launch, and grab 30 minutes with us in the next two weeks to look at your cash position through November — inventory bills land months before the revenue does, and we'd rather you see that curve now.

Pair it with the store-owner edition of this post — BFCM finance prep for store owners — as the client's own homework. A firm that sends this in September isn't a vendor that closes the books. It's the firm that saw November coming.

That's the whole trade this post is offering: five checks and one email now, or the forty-percent-up file in January. If you'd rather run the sweep with the sync method, mappings, and error log already handled by the platform, book a CPA onboarding call — we'll walk your first client through all five checks with you, before the volume shows up.