Blog

Per Unit FBA Removal Billing 2026: Journal Entries & Monthly Checklist

Turn Amazon's 2026 per unit FBA removal billing into ready journal entries, a monthly reconciliation checklist, tax substantiation steps, and automation...

Marcus Brandt, Head of Seller Accounting at BeanHawk

By Marcus Brandt · Head of Seller Accounting

Updated October 6, 2026

Per Unit FBA Removal Billing 2026: Journal Entries & Monthly Checklist

Per Unit FBA Removal Billing 2026: Journal Entries & Monthly Checklist

Fulfillment units processed for removal billing

Amazon now charges FBA removal and disposal fees per unit at the moment each unit is processed, not as a single lump sum when the order closes. The immediate accounting action is to pull Payments > Transaction view and reconcile each Service Fee line tagged “FBA Removal Order” against your inventory and cost of goods sold records, watching closely for partial orders and duplicate charges that can slip through unnoticed.


TL;DR:

  • Per-unit removal fees now post immediately during processing, increasing reconciliation complexity and requiring frequent seller account reviews.
  • Removal orders can take several months to fully process, with fees appearing at various points rather than in a single lump sum.
  • Record all removal expenses promptly and match them against shipment, return, or disposal confirmations for accurate financial reporting.
  • Automated monitoring tools help flag mismatched charges and streamline reconciliation across multiple FBA accounts, saving time and reducing errors.
  • Proper documentation of disposal and removal processes is essential for supporting inventory valuation adjustments and avoiding tax audit issues.

Beanhawk
Keep FBA Charges Reconciled
BeanHawk continuously monitors FBA ledger events and posts settlements to QuickBooks or Xero for accurate financial reconciliation.
Visit BeanHawk

Table of Contents

What changed and where to find removal charges in Seller Central

Amazon’s own forum posts describe a timing change, not a rate change: removal and disposal fees are now charged as units are processed rather than billed together when the full removal order completes. Different notices have cited March 1, 2026 and May 1, 2026 as effective dates, so treat the most recent Seller Central announcement as authoritative for your account and confirm the date against your own notifications.

The practical effect is that one removal order can now generate many small charges spread across weeks, each tied to a specific unit’s disposition rather than one bundled fee.

You can find these charges in a predictable spot:

  • Go to Payments > Transaction view inside Seller Central.
  • Filter for Service Fees.
  • Look for line items labeled “FBA Removal Order” with the associated order ID.
  • Export the filtered view to cross-reference against your removal order report.

Per-unit billing increases reconciliation complexity because charges now post incrementally instead of as one lump sum per removal order, and partial order failures can still generate unit-level charges even when the broader order never completes. That means a bookkeeper closing the books on a monthly cycle can no longer wait for one tidy total; the charges arrive in pieces, and some may land after the units themselves have already shown up back in a warehouse or been disposed of.

Removal order lifecycle and how long it actually takes

Matching the paperwork to the physical reality starts with understanding the timeline Amazon itself describes. According to seller forum guidance, removal orders can take several months to process fully at fulfillment centers, plus additional time for carrier delivery. That means a removal order you initiate in January might not fully resolve until April, with fee charges posting at several points along the way rather than at a single milestone.

A removal order typically moves through these states:

  1. Requested, when you submit the removal order in Seller Central and Amazon begins queuing the units.
  2. Pending, while units sit in the fulfillment center awaiting pick and pack for removal or disposal.
  3. Processed, when Amazon pulls the specific unit and the per-unit fee posts to Transaction view.
  4. Shipped or disposed, when the unit either enters carrier transit back to you or is confirmed destroyed, each outcome carrying its own documentation.

Partial and failed orders add a layer of complexity that catches many sellers off guard. A removal order can process some units successfully while others remain pending, get lost, or get flagged for a different disposition, which means you may see fee charges for units that never arrive and no charges yet for units still queued. Treat every removal order as an open item until every unit inside it reaches a final state, not just when the order status first changes.

How to record removal fees, returns, and disposals on your books

The core accounting question is simple: is this a period expense, or does it change the carrying value of inventory you still own? Most removal fees are the former. The fee itself, what Amazon charges to pull a unit out of fulfillment, is a service cost tied to the removal action, not a change in what the unit is worth.

Recommended account mapping:

  • Post the per-unit removal or disposal fee to a Fulfillment / Removal Expenses account as a period expense when it is charged.
  • Adjust the inventory asset account only when inventory is actually returned to you or demonstrably disposed of, not merely when a fee posts.
  • Keep returned inventory in transit in a separate inventory-in-transit account until you have physically received and counted it, since Amazon’s own records still show the units as its responsibility until delivery completes.
  • Record a disposal write-off only once you have Amazon’s disposal confirmation, not the same day you submit the removal request.

The trickiest timing issue is when a fee posts before the unit’s final disposition is clear. If a removal order was created near month end and you reasonably expect a batch of units to process within days, a short-term accrual for the anticipated fee keeps your interim financials closer to reality; reverse and true up the accrual once the actual per-unit charges land in Transaction view.

Pro Tip: Never record inventory as returned stock until you have a packing slip or receiving count in hand; Amazon’s transaction timestamp and your physical receipt date are rarely the same day.

Sample journal entries and a monthly reconciliation checklist

Three scenarios cover most of what shows up in a removal order batch.

Removal fee expense, posted when the per-unit charge appears in Transaction view:

  1. Debit Fulfillment / Removal Expenses, credit Amazon Clearing or Accounts Payable (matched to the settlement line that includes the fee).

Return to seller, when a unit is shipped back to you: 2. On shipment confirmation, debit Inventory in Transit and credit the prior accrual (or Accounts Payable if no accrual existed); on physical receipt, debit Inventory and credit Inventory in Transit at the unit’s original cost basis.

Disposal or write-off, when Amazon confirms destruction: 3. Debit Disposal Expense and credit Inventory for the unit’s carrying value, referencing the Amazon disposal confirmation number in your memo field.

A simple monthly checklist keeps these entries from piling up into a quarter-end scramble:

  • Export Transaction view and filter for every line labeled “FBA Removal Order.”
  • Pull the removal order report and match ASIN and SKU counts against the Transaction view export.
  • Flag any removal order with units still in a pending or in-transit state for next month’s follow-up.
  • Save order-level PDFs or screenshots of disposal confirmations before Amazon’s interface refreshes old data.

Doing this monthly, rather than scrambling at year end, is what keeps per-unit billing from becoming a backlog of unmatched charges.

Tax and valuation: when removals support a write-down

Not every removal justifies a change in inventory value for tax purposes, and getting this wrong is an audit risk. The IRS practice unit on lower of cost or market requires that any write-down to market value, including for subnormal or disposed goods, be supported by consistent valuation methods and documented evidence, not a unilateral judgment call made after the fact.

For subnormal goods specifically, the guidance ties acceptable valuation to actual offering for sale or sale within the 30 days surrounding inventory date. That means if you want to write down a batch of removed, damaged, or obsolete units, you generally need evidence you tried to sell them at a reduced price around that window, not just a note that they seemed unsellable.

Contemporaneous documentation to keep on hand for any removal that affects valuation:

  • The removal order record itself, including order ID and unit counts.
  • The Transaction view charge lines showing the per-unit fees applied.
  • Disposal confirmations from Amazon when units were destroyed rather than returned.
  • Photos or carrier receiving documentation when units came back damaged.

Treasury’s own inventory cost regulations reinforce that inventory methods must clearly reflect income and be applied consistently year over year, which rules out switching valuation approaches opportunistically around a large removal event.

Common pitfalls worth watching for: inconsistent valuation methods applied from one removal batch to the next, missing the 30-day sale or offering evidence that subnormal valuation requires, and failing to link Amazon’s removal order IDs back to the specific tax records that justify a deduction or write-down. Any of these can turn a reasonable write-down into a disallowed one under examination.

Evidence chain supporting inventory write-down

A practical reconciliation playbook for accountants

Treat per-unit removal billing as a recurring monthly close task rather than a once-a-quarter cleanup. Four exports form the backbone of the process:

  • Transaction view, filtered to Service Fees, for the actual per-unit charges.
  • The removal order report, for expected unit counts and statuses.
  • Settlement reports, to confirm which settlement period absorbed each fee.
  • An inventory snapshot CSV, pulled before and after the removal batch to spot discrepancies.

With those in hand, the reconciliation itself follows a consistent sequence: mark any removal order still showing pending units, book a short-term accrual if charges are expected before period close, match every charged unit in Transaction view against its corresponding removal line item, and only then adjust the inventory ledger once a unit’s final disposition, return or disposal, is confirmed.

Two touchpoints lend themselves well to automation: posting the per-unit fee entries to your ledger as they appear, and matching charged units back to specific SKUs without manual lookup. Manual review still belongs on duplicate charges for the same unit, charges tied to an ASIN that doesn’t match your removal order report, and any fee that posts weeks after the order’s expected completion window.

Pro Tip: If a SKU shows a Transaction view charge with no corresponding line in your removal order report, treat it as a discrepancy worth a support case, not a rounding error to absorb.

How automation and continuous monitoring reduce reconciliation risk

Per-unit billing turns what used to be a handful of lump-sum entries per month into dozens or hundreds of small line items, which is exactly the kind of volume that manual bookkeeping handles poorly. We built our monitoring to track inbound shipments and FBA ledger events continuously, so a mismatch between what Amazon charged and what your removal order actually processed gets flagged close to when it happens rather than discovered months later during a reconciliation sweep.

Specific ways this applies to removal accounting:

  • We watch ledger events as they post, so a per-unit removal or disposal fee is matched to its originating order without waiting for a manual export.
  • We automate settlement posting into QuickBooks and Xero, which means charged units map to the right expense account without rekeying each Transaction view line by hand.
  • We centralize inventory economics across channels, so a removal batch shows up against the same SKU record you use for cost of goods sold and reorder decisions.

For accountants managing several FBA accounts at once, this kind of ongoing matching is the difference between a monthly close that takes an afternoon and one that takes a week chasing line items.

What accountants should prioritize under per-unit billing

The single biggest shift this billing change demands is treating removal fees as a running ledger reconciliation task, not a once-a-quarter catch-up. Unit-level charges arrive on Amazon’s schedule, not yours, so the firms that stay current are the ones checking Transaction view weekly rather than monthly.

Preserve every removal order record and disposal confirmation as you go. Amazon’s interface does not make historical data easy to retrieve months later, and tax positions built on write-downs need that paper trail intact.

Finally, loosen the wall between operations and accounting. The person creating removal orders and the person closing the books need to compare notes regularly, because a removal order initiated in one period and completed in another is exactly where mismatched expectations turn into misstated COGS.

, Tim

BeanHawk: automated settlement posting for per-unit removal charges

Reconciling dozens of incremental per-unit charges by hand is exactly the kind of work we built to disappear. Our platform monitors inbound shipments and FBA ledger events continuously, catching mismatches between charges and activity, and posts settlements directly into accounting software so charged units land in the right expense account without manual rekeying.

Beanhawk

What this looks like in practice:

  • Continuous monitoring of ledger events, including FBA Removal Order charges as they post.
  • Automated settlement posting to accounting software without taking a commission on recovered funds.
  • Centralized inventory economics across sales channels, so removal activity stays tied to consistent SKU-level cost records.

If you want to see what this catches before committing to anything, start with our free FBA reimbursement audit to find missing or misreconciled charges in your own account.

FAQ

How do I cancel my FBA account?

Amazon FBA account cancellation is handled through Seller Central account settings, and the specific steps depend on whether you want to close the whole seller account or just stop using FBA services while keeping the account active. Before canceling, resolve any open removal orders and pending reimbursements so you do not lose access to historical transaction records needed for accounting purposes.

Can I make $1,000 a month selling on Amazon?

Earnings on Amazon vary enormously by product category, pricing, and how well a seller manages costs like storage, fulfillment, and removal fees, so there is no fixed outcome tied to any specific monthly figure. Profitability depends on tracking all fee categories accurately, including the newer per-unit removal and disposal charges, against actual sales revenue.

How does Amazon reimbursement work?

Amazon reimburses sellers when inventory is lost, damaged, or mishandled in its fulfillment network, typically crediting the seller’s account once a claim is verified. Reimbursements post as separate line items in Transaction view and should be matched against the original inventory loss event for accurate bookkeeping; automated tools like ours track these ledger events continuously to flag reimbursements that were never issued.

What does a close listing do on Amazon?

Closing a listing removes the offer from Amazon’s marketplace so it no longer appears to buyers, but it does not automatically remove the associated inventory from fulfillment centers. Sellers still need to submit a separate removal order to have that inventory returned or disposed of, which is the action that triggers the per-unit removal and disposal fees covered in this guide.

See it in BeanHawk

Every settlement becomes one clean journal

BeanHawk parses each marketplace payout line by line and posts a single summarized journal to QuickBooks or Xero — sales, fees, refunds, facilitator tax, and reimbursements mapped to the right accounts, balanced to the penny.

  • ✓Debits equal credits or it won't post — no more deposits booked as revenue
  • ✓Marketplace facilitator tax routed to a liability account, out of your income
  • ✓The net deposit lands in a clearing account that matches your bank feed exactly
See the QuickBooks & Xero sync →
app.beanhawk.com/books/settlementsBeanHawkDashboardReimbursementsBooksInventoryChannelsJRJordan R.Owner · Pro planSettlement → journalSettlement #90417Amazon · 14-day payout1,204 orders3,918 fee lines212 refunds1 net deposit$6,853.70 depositedOne deposit hidesa dozen line items.autoJournal entryPostedACCOUNTDRCRProduct sales12,480.00Referral fees1,872.00FBA fulfilment fees2,104.50Refunds640.00Facilitator tax (liability)1,014.20Reimbursements218.40Bank — net deposit6,853.70Balanced15,630.5015,630.50→ QuickBooks→ Xero

Put this on autopilot

BeanHawk recovers what Amazon owes you and keeps your books penny-accurate, every channel included, from $19/mo.