Bookkeeper review sample. Demo numbers only. No real seller data.

Review bucket: can a bookkeeper trust the failure modes at a glance?

This page is a sample of how SkuSum should surface reconciliation exceptions before anyone trusts the SKU profit or exports a QuickBooks/Xero journal. The goal is not to hide the messy lines. The goal is to show what tied out, what did not map, why it was flagged, and what action a human should take.

The review rows below are grounded in existing realistic/stress report fixtures used by the app tests: Orders, Settlement, Advertising, and COGS forms. They are demo numbers, not real seller data.

Download review bucket CSVSee journal mapping draft

$6,550.00
Settlement deposit tied to clearing total
$0.00
Unexplained settlement-to-clearing difference
6
Review items before trusting SKU margin
2
High-severity items blocking journal export

Bookkeeper-facing summary

Books/control total: settlement deposit ties to the Amazon Clearing Account. No unexplained bank difference.

SKU model: usable for review, but not final until the high-severity items below are resolved.

Journal export: draft only. Blocked until missing COGS and unmapped fee category are classified.

At-a-glance review bucket

First view for a bookkeeper: six issues grouped by severity, each with source, why it was flagged, next action, and trust impact. The spreadsheet-style table is still available below for audit/export, but the cards are the main trust layer.

Resolve firstMissing COGS + unmapped fee block clean export
Review nextAds, refunds and settlement-only SKU affect SKU margin
Keep visibleBlank account-level rows should not be silently spread
RB-001
Missing COGS blocks SKU margin
HighOpen
Amount7 units
SKUNOCOGS
Sourceorders:14
settlement:31-33
Export impactBlocks SKU profit and COGS journal
Why flagged

Orders and settlement show 7 units sold, but the COGS form has no landed cost row for this SKU.

Suggested action

Add or confirm landed cost for NOCOGS before finalizing SKU margin or COGS journal.

RB-002
Unmapped future fee type
HighOpen
Amount-$5.00
SKUAccount-level
Sourcerealistic:34
Export impactBlocks clean journal classification
Why flagged

Settlement includes a future or unknown fee type: SomeBrandNewFeeType2027.

Suggested action

Map this fee to an existing account or create a new account before exporting a clean journal.

RB-003
Account-level ad spend needs allocation rule
MediumOpen
Amount-$12.00
SKUBlank SKU
Sourcerealistic:29
Trust impactAffects SKU contribution margin
Why flagged

Cost of Advertising appears in the settlement without a SKU, so it cannot be directly assigned to one product.

Suggested action

Allocate using advertising report ASIN/SKU detail when available, or keep as account-level contribution cost.

RB-004
Refund settled in current period
MediumOpen
Amount-$90.00 net
SKUWIDGET
Sourcerealistic:20-22
Trust impactPrevents false current-month SKU blame
Why flagged

Refund principal, refund commission, and shipping chargeback settled this period; original sale period still needs context.

Suggested action

Keep in current settlement for books, but flag the SKU analysis if the sale belongs to a prior period.

RB-005
Settlement-only SKU activity
MediumOpen
Amount$212.00 net
SKUSETTLEONLY
Sourcestress:36-37
Trust impactCatches order-model drift
Why flagged

Settlement has SKU activity, but the Orders form has no matching order rows.

Suggested action

Check date range, SKU aliasing, or whether this is a non-order adjustment before trusting SKU margin.

RB-006
Blank account-level settlement lines
LowOpen
Amount-$44.99
SKUBlank SKU
Sourcestress:38-39
Trust impactVisible account-level bucket
Why flagged

Subscription and adjustment lines are account-level settlement rows with no SKU value.

Suggested action

Keep in account-level bucket unless the seller wants a specific allocation rule. Do not silently spread across SKUs.

Spreadsheet-style detail table
IDSeverityStatusIssue typeAmountSourceSKU / ASINWhy flaggedSuggested actionTrust note
RB-001HighOpenMissing COGS7 unitsorders_stress.csv:14 + settlement_stress.csv:31-33NOCOGSOrders and settlement show 7 units sold, but the COGS form has no landed cost row for this SKU.Add or confirm landed cost for NOCOGS. Do not finalize SKU margin or COGS journal until resolved.Blocks SKU profit and COGS journal accuracy.
RB-002HighOpenUnmapped fee category-$5.00settlement_realistic_v2.tsv:34Account-levelSettlement includes a future/unknown fee type: SomeBrandNewFeeType2027.Map this fee to an existing account or create a new account before exporting a clean journal.Books can tie out, but journal classification is not trustworthy yet.
RB-003MediumOpenAccount-level ad allocation-$12.00settlement_realistic_v2.tsv:29Blank SKUCost of Advertising appears in the settlement without a SKU, so it cannot be directly assigned to one product.Allocate using advertising report ASIN/SKU detail when available, or keep as account-level contribution cost.Does not block books. Affects SKU contribution margin.
RB-004MediumOpenRefund period check-$90.00 netsettlement_realistic_v2.tsv:20-22WIDGETRefund principal, refund commission, and shipping chargeback settled this period; original sale period still needs context.Keep in current settlement for books, but flag the SKU analysis if the sale belongs to a prior period.Prevents "current month SKU is suddenly bad" confusion.
RB-005MediumOpenSettlement-only SKU$212.00 netsettlement_stress.csv:36-37SETTLEONLYSettlement has SKU activity, but the Orders form has no matching order rows.Check date range, SKU aliasing, or whether this is a non-order adjustment before trusting SKU margin.Catches drift between order-level model and settlement control total.
RB-006LowOpenBlank settlement SKU-$44.99settlement_stress.csv:38-39Blank SKUSubscription and adjustment lines are account-level settlement rows with no SKU value.Keep in account-level bucket unless the seller wants a specific allocation rule.Should not block books, but should stay visible so it is not silently spread across SKUs.

What tied out

Settlement to clearing

Pass. Net Amazon payout equals the Amazon Clearing Account for the settlement period.

This is the control total before looking at SKU margin.

SKU subtotal to settlement

Needs review. Most SKU lines reconcile, but the missing COGS and shared ad allocation affect per-SKU margin.

Do not use SKU kill/keep decisions until open items are resolved.

Journal export

Blocked. One fee category is unmapped, so the journal can be previewed but not exported as "clean".

This is the guardrail against silently wrong accounting entries.

Questions for reviewers

  1. Is the severity split right, or would a bookkeeper label any of these differently?
  2. Does "books tie out, SKU model needs review" make the trust boundary clear enough?
  3. Are the suggested actions specific enough to hand to a seller or junior bookkeeper?
  4. What column is missing for you to trust or reject the output quickly?
  5. Should journal export be blocked by high-severity items, or allowed with warnings?

Current product stance

A2X/QBO can be the control total. Sellerboard/Seller Central can be good enough for daily SKU decisions. SkuSum is exploring the reviewable bridge: SKU-level explanation that reconciles back to the settlement and makes the failure modes visible.

© 2026 SkuSum. All rights reserved. Back to skusum.com | Sample reconciliation | Journal mapping | Chrome extension