Amazon FBA Reimbursement Audit Checklist: Recover Every Dollar

Amazon's fulfillment network processes millions of units daily, and errors happen at scale. Lost units during inbound shipment, warehouse damage, customer return discrepancies, incorrect weight/dimension charges, and removal order mistakes all represent money Amazon owes you. This checklist walks through every reimbursement category systematically, organized by where you find the data in Seller Central, so you can audit your account efficiently and file claims for every recoverable dollar.

Understanding Amazon's reimbursement windows and your recovery rights

Amazon operates two critical time windows that determine your reimbursement eligibility:

• 75-day automatic reimbursement window: Amazon monitors for certain errors (lost inventory during receive, warehouse damage) and issues automatic reimbursements within 75 days when their systems detect issues
• 180-day claim filing window: You have 180 days from when an issue occurs to file a manual claim if Amazon did not automatically reimburse you

The practical implication: automate your monitoring to catch issues Amazon misses before the 180-day deadline passes. Waiting until day 170 to audit six months of activity creates unnecessary urgency and increases the chance of missing recoverable money.

Amazon is legally required to reimburse you when they lose or damage inventory they accepted into FBA, but you must identify and document the discrepancies. The burden of proof lies with you.

Audit frequency and timing strategy

Run full audits on this schedule based on your business size:

Set calendar reminders 30 days before your oldest potential claims expire. This gives you buffer time to gather documentation and respond to Amazon if they request additional information.

Checklist section 1: Inventory Ledger discrepancies

The Inventory Ledger (Reports → Fulfillment → Inventory Ledger) is your authoritative record of every inventory movement in FBA. Start here.

Lost inventory during inbound shipment

What to look for: Units marked as "shipped" in your shipment tracking that never show a corresponding "Receipts" entry in the Inventory Ledger.

How to audit:

1. Pull your Inventory Ledger for the past 180 days
2. Export your shipment records (Shipments → Track Shipments → filter by "Delivered" status)
3. For each delivered shipment, verify that every SKU and quantity shows a matching "Receipts" event in the Ledger within 7-10 days of delivery
4. Flag any shipment where received quantity is less than shipped quantity

Example of what to flag: You shipped 50 units of SKU ABC123 in shipment FBA15XYZ on March 1. Shipment shows "Delivered" on March 5. Your Inventory Ledger shows a "Receipts" entry for only 45 units of ABC123 on March 7. The 5-unit discrepancy is reimbursable if Amazon doesn't automatically reimburse within 75 days.

Documentation needed: Shipment ID, tracking information showing delivery, packing list or box content information showing you sent the full quantity.

Warehouse damage and lost inventory

What to look for: "Damaged" or "Lost" entries in the Inventory Ledger event-type column.

How to audit:

1. Filter your Inventory Ledger by event type: "Damaged" and "Lost"
2. For each event, check if there's a corresponding "Reimbursement" entry for the same SKU, quantity, and date
3. Flag any damage/loss event older than 75 days with no reimbursement

Amazon should automatically reimburse warehouse damage and lost inventory, but their systems miss cases regularly—especially when damage occurs in the first 30 days after receiving inventory, or when units are lost during internal transfers between fulfillment centers.

Documentation needed: Inventory Ledger showing the damage/loss event with no corresponding reimbursement within 75 days.

Inventory found after being marked lost

What to look for: "Found" events in the Ledger where Amazon relocates inventory they previously marked as lost—but never reverses a reimbursement they issued.

This is rare but worth checking. Filter for "Found" events, cross-reference with your reimbursement history. If Amazon reimbursed you for lost inventory then later found it, they should deduct the reimbursement when they return the units to your active inventory. Occasionally this deduction doesn't happen, and you've been paid twice for the same inventory. Amazon will eventually claw this back if they catch it, so flag it proactively to avoid surprise deductions later.

Checklist section 2: Customer returns and removal orders

FBA Customer Returns reports and removal order reports contain two distinct reimbursement categories.

Customer return discrepancies

What to look for: Returns where the customer received a refund but the unit was never returned to your inventory or marked as damaged/unsellable in Amazon's system.

How to audit:

1. Download your FBA Customer Returns report (Reports → Fulfillment → Customer Returns)
2. For each return, check the "Detailed Disposition" column
3. Flag returns with disposition status "Pending" or blank that are older than 45 days
4. Cross-reference flagged returns with your Inventory Ledger—if the unit never shows up as "Customer Return," it's reimbursable

Example: Customer returns a $40 item on April 1. Return report shows "Disposition: Pending." You check the Inventory Ledger 50 days later and find no "Customer Return" event for that unit. Amazon refunded the customer but neither returned the inventory to you nor logged it as damaged. You're owed a reimbursement.

Documentation needed: FBA Customer Returns report entry, Inventory Ledger showing no corresponding return event within 45 days of the return date.

Removal order errors

What to look for: Removal orders where the quantity shipped back to you (or disposed of) is less than the quantity you requested.

How to audit:

1. Download your removal order reports (Reports → Fulfillment → Removal Order Detail)
2. For each removal order, compare "Requested Quantity" with "Shipped Quantity" or "Disposed Quantity"
3. Flag any order where shipped/disposed is less than requested
4. For removals shipped to you, verify the physical quantity received matches Amazon's reported shipped quantity

This category catches both Amazon's internal errors (they lost units before removal) and shipping errors (they report shipping 20 units but only 18 arrive in your physical count).

Documentation needed: Removal order report showing discrepancy, photos of received shipment and inventory count if claiming physical shortage.

Checklist section 3: Fee and dimensional weight errors

Amazon calculates fulfillment fees based on product dimensions and weight. Errors in their measurement systems can overcharge you for months before you notice.

Incorrect dimensional weight charges

What to look for: Products where Amazon's recorded dimensions or weight are larger than your actual product specifications.

How to audit:

1. Go to Inventory → Manage All Inventory
2. For each product, click "Edit" → "Vital Info" tab → check the dimensions and weight Amazon has on file
3. Compare with your actual product dimensions (measure and weigh a unit if you don't have specs documented)
4. Flag any product where Amazon's dimensions are larger
5. Pull your FBA fee reports and calculate the overcharge amount based on fee differences between Amazon's recorded size tier and your product's actual size tier

Common scenario: Your product measures 8" × 6" × 2" and weighs 10 oz (small standard size). Amazon's system records it as 10" × 8" × 3", 14 oz (large standard size). You've been paying large standard fees instead of small standard fees on every order. The difference is approximately $0.50-$1.00 per unit depending on the specific dimensional bracket.

If you're fulfilling 200 units per month of this product and the error has existed for 6 months, you're owed $600-$1200 in fee overcharges.

Documentation needed: Photo of your product on a measuring device showing actual dimensions, product weight specification, comparison showing Amazon's recorded dimensions, sample FBA fee report highlighting the overcharged fee per unit.

Fee discrepancies on multi-unit packs

If you sell multi-packs (2-pack, 3-pack, etc.), Amazon sometimes applies single-unit dimensions instead of the full pack dimensions, or miscalculates weight for bundled products. Audit each multi-pack SKU individually using the same process as dimensional weight errors.

Checklist section 4: Destruction and disposal reimbursements

What to look for: Unfulfillable inventory that Amazon disposed of due to warehouse damage or contamination, where Amazon was at fault.

How to audit:

1. Filter your Inventory Ledger for "Disposal Complete" events
2. For each disposal, check if the original reason the inventory became unfulfillable was due to Amazon error (warehouse damage) versus customer damage (customer return in unsellable condition)
3. Flag disposals of warehouse-damaged inventory where no reimbursement was issued

Amazon should automatically reimburse when they dispose of inventory they damaged, but reimbursements sometimes fail to trigger if the damage event and disposal happen in different accounting periods.

Documentation needed: Inventory Ledger entries showing the damage event caused by Amazon (not customer return damage), followed by disposal, with no corresponding reimbursement.

How to file claims efficiently once you've completed the audit

After running through this checklist, you'll have a list of flagged discrepancies. File claims through Seller Central:

1. Go to Help → Contact Us → Select "Selling on Amazon" → "Fulfillment by Amazon" → "FBA Inventory Reimbursement"
2. Submit one case per issue category (don't combine lost inventory and fee errors in the same case)
3. Include concise documentation: the specific report data, date ranges, and what you're claiming
4. Reference Amazon's policy requirements: cite the 180-day window and Amazon's responsibility under FBA terms

Typical response time is 2-7 business days. If Amazon denies the claim, respond with clarifying documentation. Approximately half of initially denied claims get approved on appeal when you provide clearer evidence.

Automating the audit process

Manual audits work for smaller catalogs, but become impractical above 50 SKUs or 1000 monthly units. At that scale, consider automation:

• Export and script approach: If you're comfortable with spreadsheets and basic scripting, export all relevant reports monthly and build formulas to flag discrepancies automatically
• Third-party audit tools: Services like SageSeller's reimbursement module automatically scan your Inventory Ledger, return reports, and fee data to identify reimbursable discrepancies without manual report checking
• Hybrid approach: Use automation for high-frequency checks (weekly scans of recent data) and run manual deep-dive audits quarterly to catch anything automation might miss

Automation doesn't eliminate the need to understand what you're auditing for—it just scales the process once you know what patterns to monitor.

Common reasons Amazon denies legitimate claims and how to respond

Even with proper documentation, Amazon sometimes denies valid claims. The most common denial reasons and how to respond:

"We show this inventory was received" — Amazon references a receive date, but your Inventory Ledger shows a quantity discrepancy. Response: Provide side-by-side comparison of your shipment packing list and their Receipts entry showing the shortage.

"This falls outside the reimbursement window" — Amazon claims the issue occurred more than 180 days ago. Response: Demonstrate the date you're claiming from (usually the date the discrepancy became identifiable in reports, not the original transaction date). For example, if a customer return was marked "Pending" on day 1 but didn't age into reimbursable status until day 45, your 180-day clock starts at day 45.

"Insufficient documentation" — Vague rejection. Response: Ask specifically what documentation is missing and provide it. Often this means they want photos, weight specs, or more detailed Inventory Ledger exports.

If Amazon denies a claim twice and you're confident in your documentation, escalate by requesting supervisor review in your case response. Escalation doesn't guarantee approval but triggers a more thorough review by a different team member.

Tracking recovered amounts and projecting future reimbursements

Maintain a simple tracking spreadsheet with these columns:

• Claim submission date
• Issue category (lost inventory, customer return, fee error, etc.)
• SKUs affected and quantity
• Claimed amount
• Resolution date
• Reimbursed amount (actual approval may differ from claim)
• Denial reason (if denied)

This tracking serves two purposes: it helps you identify patterns in Amazon's errors (certain SKUs consistently have receive discrepancies, specific FCs have higher damage rates), and it lets you project expected monthly recovery amounts for budgeting purposes.

Recovery amounts depend entirely on your fulfillment volume, product mix, and how aggressively you audit. Sellers running tight audit processes typically identify reimbursable discrepancies across multiple categories each month, but actual amounts vary based on individual circumstances and Amazon's performance in your specific fulfillment centers.