Amazon deferred transactions, solved in the ledger — not at month end
Amazon's DD+7 policy holds payouts until seven days after delivery and keeps deferred transactions out of settlement reports. NeonPanel records every sale, fee, and COGS entry on its posted date and syncs it to QuickBooks or Xero — so a payout policy never decides which month your revenue belongs to
- Accounting
- Inventory
- Forecasting
- AI access
Trusted by 200+ ecommerce teams
DD+7 changed what settlement reports mean
Under DD+7, most consumer orders are held until seven days after confirmed delivery — and deferred transactions are excluded from settlement reports until released. A sale made March 28 can surface in an April settlement. If your Amazon accounting is driven by settlements, that sale lands in the wrong month, along with its fees and COGS.
- Month-end P&Ls misstate performance — each month loses its final days of sales to the next and inherits the previous month's tail
- COGS and fees follow the wrong dates — margin analysis by month becomes unreliable
- 1099-K stops matching the books — Amazon reports by transaction date while settlement-driven books follow release dates, so year end needs bridge schedules
Patch the settlement or record the transaction
The industry has two responses to Amazon deferred transactions: keep settlements as the source of truth and correct the totals with a month-end adjustment journal, or record every transaction on the date it happened so there is nothing to correct.
A corrected summary
- One accrual/reversal journal per marketplace per month
- Opening balance to establish — and keep right forever
- Totals corrected after the fact; order-level trace is not part of the mechanism
- A recurring moving part your accountant and auditor must re-explain
A ledger that was never wrong
- Every sale, fee, refund, and COGS entry on its posted date
- Nothing to accrue, reverse, or re-explain — no opening-balance ritual
- Every journal line traces to a specific transaction, order, and batch
- DD+7 visible where a delay belongs: Amazon A/R aging
Comparing tools? See the full feature-by-feature view: A2X vs NeonPanel
Posted date, clearing, A/R, cash
The mechanics follow a chain any controller will recognize — and every step syncs to QuickBooks or Xero as real journal entries, not an emulated report layer.
Record on posted dates
Every financial event — sales, shipping, promotions, referral and FBA fees — posts to a clearing account on the date it occurred, with COGS recognized at the sale using batch-level FIFO costing.
Statements confirm A/R
Settlements stop driving revenue recognition. When one arrives, it confirms which posted transactions Amazon now owes you — moving them from clearing into Amazon A/R with full traceability.
Payouts close to cash
When Amazon disburses, A/R closes against the bank deposit exactly. DD+7 shows up where a delay belongs — as Amazon receivable days you can see, age, and plan against.
Reconciliation that needs no extra motions
Because nothing is recorded on the wrong date in the first place, the reports that used to take bridge schedules now match on their own.
The ledger follows the same gross transaction-date logic as Amazon's 1099-K — year-end reconciliation is a direct match, with no bridge schedules or manual workarounds.
Amazon's monthly summary reports match the books by construction — no accrual journals to post, review, or reverse at month end.
Payouts close Amazon A/R against the actual deposit, so bank-feed matching in QuickBooks or Xero stays exact — the one job settlements are actually good at.
What finance teams get back
Previous attempts with inventory management platforms failed to extract even basic FBA data. NeonPanel finally delivered a reliable solution, pulling FBA numbers, invoices, and ledgers directly for accurate reconciliation. Roberto Auriemma, CEO, ZenART Supplies
Amazon deferred transactions FAQ
Deferred transactions are sales whose proceeds Amazon holds until a release condition is met. Under the standard DD+7 policy, funds from most consumer orders are held until seven days after confirmed delivery; B2B orders can be deferred for 30 days or more. Deferred amounts appear in Seller Central under Payments with a Deferred status and are excluded from settlement reports until released.
If your books are driven by settlement reports, revenue and fees are recorded when Amazon releases funds, not when the sale happened. Orders sold near month end land in the following month's P&L, launches and promotions look smaller in the period they ran, and year-end sales can shift across tax years. DD+7 does not change what you earn — it changes when settlement-driven books say you earned it.
No. Settlement reports only include released transactions. A sale stays out of your settlements — and out of settlement-based books — until its DD+7 hold ends. This is why settlement-driven accounting under DD+7 systematically misdates revenue, fees, and COGS.
Amazon's 1099-K reports gross activity by transaction date, and NeonPanel's ledger is built on the same posted-date logic — so the 1099-K ties out 100% automatically, with no bridge schedules or workaround spreadsheets. Settlement-driven books need those workarounds because their revenue follows release dates the 1099-K ignores.
No. DD+7 changes the timing of payouts, not the amounts. The correct accounting response is to treat it as a receivable and cash-timing question — visible as Amazon A/R days in NeonPanel — rather than letting it distort when revenue and costs are recognized.
Not with transaction-date accounting. Adjustment journals exist to correct totals that settlement-first tools recorded on release dates. NeonPanel records every transaction on its posted date, so there is nothing to accrue, reverse, or re-explain — and no opening balance to establish.
The same ledger runs the rest of your operation
See DD+7 handled correctly in your own ledger
Connect your Seller Central account and watch sales, fees, and COGS land on their posted dates — with settlements reduced to A/R and cash, the way they should be.