Orders 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 before finalizing SKU margin or COGS journal.
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
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.
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.
Orders 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 before finalizing SKU margin or COGS journal.
Settlement includes a future or unknown fee type: SomeBrandNewFeeType2027.
Map this fee to an existing account or create a new account before exporting a clean journal.
Cost 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.
Refund 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.
Settlement 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.
Subscription 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. Do not silently spread across SKUs.
| ID | Severity | Status | Issue type | Amount | Source | SKU / ASIN | Why flagged | Suggested action | Trust note |
|---|---|---|---|---|---|---|---|---|---|
| RB-001 | High | Open | Missing COGS | 7 units | orders_stress.csv:14 + settlement_stress.csv:31-33 | NOCOGS | Orders 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-002 | High | Open | Unmapped fee category | -$5.00 | settlement_realistic_v2.tsv:34 | Account-level | Settlement 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-003 | Medium | Open | Account-level ad allocation | -$12.00 | settlement_realistic_v2.tsv:29 | Blank SKU | Cost 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-004 | Medium | Open | Refund period check | -$90.00 net | settlement_realistic_v2.tsv:20-22 | WIDGET | Refund 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-005 | Medium | Open | Settlement-only SKU | $212.00 net | settlement_stress.csv:36-37 | SETTLEONLY | Settlement 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-006 | Low | Open | Blank settlement SKU | -$44.99 | settlement_stress.csv:38-39 | Blank SKU | Subscription 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. |
Pass. Net Amazon payout equals the Amazon Clearing Account for the settlement period.
This is the control total before looking at SKU margin.
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.
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.
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.