Including multi-year catch-up - with the footing check that proves the conversion is right.
Walmart's settlement report runs on the marketplace's own payment cycle rather than anything resembling your calendar, and its fee structure is category-based: referral fee percentages vary by department, WFS fulfillment fees arrive as separate rows from the sale they belong to, and adjustments (shipping credits, dispute outcomes) post days after the orders they touch. Sellers doing their own books usually discover the problem at month-end, when the deposit total matches nothing they can reconstruct from order reports.
| Report line | Books category |
|---|---|
| Item sale rows | Sales |
| Referral fee (category-based %) | Platform fees |
| WFS fulfillment fee | Platform fees |
| Customer return rows | Refunds |
| Account reserve holds | Transfers/reserves |
Walmart settlement reports are downloadable per payment cycle for prior periods, so catching up means converting a stack of cycle reports in order. Watch for account reserve holds in older files - they post as transfers rather than fees, and older books often expensed them by mistake.
QuickBooks bank feeds want one line per money movement against a deposit, so FootingKit summarizes each payout into category lines dated to the deposit date; order-level detail stays in the reconciliation report, out of your register.
Xero statement imports work best when each payout arrives as a small set of coded lines, so FootingKit groups by payout and carries the payout id in the Reference field - bank rules handle the recurring coding from the second month on.
Yes - WFS fulfillment fees map to their own fee line so per-settlement margin reporting stays accurate.
Usually a reserve hold or a late-posting adjustment; both appear as distinct categories in the converted file so the gap explains itself.
Convert your Walmart file - done-for-you from $149
FootingKit converts marketplace settlement reports into QuickBooks- and Xero-ready books, footed to the penny.