How to Track FBA Reimbursements and Match Payouts to Cases

Short answer: To track FBA reimbursements, download the Reimbursements report from Seller Central, match each row to your dispute by case-id first, and fall back to FNSKU plus an approval-date window when no case ID is present. Keep a simple case log with the case ID, the LPN of the returned unit, and a status, then reconcile it against the report once a month so nothing approved, denied, or reversed slips through.

Key takeaways

• The Reimbursements report is the source of truth for what Amazon actually paid, but it does not contain the LPN of the returned unit.
• Match payouts to disputes by case-id first. When the case-id is blank, use FNSKU plus a date window around the approval-date.
• Capture the case ID from the Seller Support email the moment it arrives, and write it next to the LPN in your case log.
• Track both cash and inventory reimbursements, because a unit returned to your stock is a resolution too.
• Reimbursements can be reversed later, so a case is not truly closed until it survives your next reconciliation.
• A 30-minute monthly routine is usually enough to keep a clean, auditable record of every dispute.

Why do you need to track FBA reimbursements at all?

You need to track reimbursements because filing a dispute is only half the job; the money only counts once it shows up in the report and stays there. Without a log, approved cases, partial payouts, and quiet reversals are almost impossible to spot.

Most sellers who dispute returns do the hard part well. They photograph the returned unit, read the LPN sticker, and file a clear ticket. Then the case disappears into their inbox, and a few weeks later nobody remembers whether it was paid.

That gap matters for three reasons. First, Seller Support sometimes approves a smaller amount than you expected, or reimburses inventory instead of cash. Second, some cases are closed without a payout and need a follow-up. Third, a reimbursement can be reversed later, and a reversal will not come with a friendly reminder.

If you are new to disputes, start with what an FBA return dispute is and when you can file one. This article assumes you already file cases and now want to know which ones actually paid.

Where do you download the Reimbursements report?

You download the Reimbursements report from the Reports area of Seller Central, usually under the fulfillment or FBA reports section. Menu names change from time to time, so if you cannot find it, search "Reimbursements report" in Seller Central Help.

Once you find it, you will pick a date range and request a download. Report downloads in Seller Central are limited to date ranges, so you cannot always pull your entire history in one file. Plan to download in monthly chunks and keep each file with a clear name, for example "reimbursements-2026-06.csv".

The report is a flat table: one row per reimbursement event. A single case can produce more than one row, for example when several units are reimbursed or when a payout is later adjusted. Treat each row as an event, not as a case.

Which other reports help with reconciliation?

Two other reports make matching much easier. The FBA Customer Returns report lists every returned unit and includes the license-plate-number column, which is the LPN printed on the sticker. Your removal order records tell you which returned units physically came back to you.

If the difference between these sources is fuzzy, read removal orders vs. customer returns reports before building your routine. Knowing which report answers which question saves a lot of confusion later.

What does each column in the Reimbursements report mean?

Each column in the Reimbursements report describes one part of a payout: when it was approved, why, for which product, and whether you got cash or inventory. You only need about a dozen columns to reconcile disputes reliably.

The table below lists the key columns, what they mean, and how you use them when matching payouts to your own cases. Column names can shift slightly over time, so compare against the header row in your own download.

Notice what is missing: there is no LPN column. That single fact shapes how every seller has to match payouts, which is the topic of the next section.

How do you match a payout to your dispute?

Match a payout to your dispute by looking up the case-id from the report in your case log first. If the row has no case-id, match on FNSKU and look for approval dates within a reasonable window after you filed.

Step one: match on case-id

The case-id is the cleanest link between your dispute and Amazon's payout. When you filed the ticket, Seller Support replied by email with a case ID. If you logged that ID next to the LPN, a report row with the same case-id is a direct match.

For example, suppose your log shows case ID 31847260593 for a returned cordless hair clipper kit with LPN LPNR8K2M4QX7T. If the report contains a row with case-id 31847260593, fnsku X00ABC1234 and a cash amount, you can mark that dispute as reimbursed and record the amount.

Step two: fall back to FNSKU plus a date window

Some rows arrive with the case-id blank, or with a case ID you never logged. In that case, filter the report by the FNSKU of the returned unit. Then look for approval dates that fall after your filing date and within a window you define for yourself.

There is no official window for this. Pick one that fits your experience, keep it consistent, and treat any match found this way as "probable" rather than "confirmed". If you have several open disputes on the same FNSKU, match the oldest open case first and note the assumption in your log.

Why is the LPN not in the Reimbursements report?

The LPN identifies one physical returned unit inside the returns process, while the Reimbursements report is organized around financial events tied to orders, SKUs, and cases. The two systems simply do not share that field.

That is why your own case log is the bridge. The FBA Customer Returns report connects the LPN to the order and FNSKU, and your case log connects the LPN to the case ID. For a deeper look at the sticker itself, see LPN stickers explained.

How should you set up a case log?

A case log is a simple table with one row per disputed unit, keyed by LPN, that records the case ID and a status. It can live in a spreadsheet, as long as everyone on your team updates the same file.

Keep the columns minimal so you actually maintain them. A good starting set looks like this:

• LPN of the returned unit, copied exactly from the sticker.
• FNSKU, ASIN and SKU, so you can filter the Reimbursements report quickly.
• Amazon order ID, if you have it from the returns report.
• Date filed and case ID from the Seller Support email.
• Issue type, for example wrong item returned or incomplete set.
• Status, using a fixed list of values.
• Amount reimbursed, reimbursement type (cash or inventory), and reimbursement-id.
• Notes, for follow-ups and reversal details.

Which statuses should you use?

Use a short, fixed list so the log stays readable. Five statuses cover nearly every situation:

• Ready: evidence is complete and the ticket text is written, but not yet filed.
• Filed: submitted in Seller Central, waiting for a reply or case ID.
• Needs info: Seller Support asked for more photos or details.
• Reimbursed: a matching row exists in the Reimbursements report.
• Denied: the case was closed without a payout and you decided not to pursue it further.

Avoid free-text statuses like "maybe paid?" or "check later". They feel convenient in the moment and make monthly reconciliation much slower.

How do you capture case IDs from Seller Support emails?

Capture the case ID by copying it from the first Seller Support reply into your case log the same day, next to the LPN you disputed. The reply email is the most reliable place to find it.

When you file a case through Seller Central Help or Get support, Seller Support replies by email with a case ID. Later messages on the same case, such as requests for more information or the final decision, usually reference that same ID. Search your inbox for the ID whenever you need the full history.

A few habits make this painless:

1. Create an email folder or label for Seller Support replies and filter incoming case emails into it.
2. When a new reply arrives, open your case log and find the row by LPN or by the date you filed.
3. Paste the case ID into the row and change the status from ready to filed if you have not already.
4. If the email asks for more information, set the status to needs info and add a note with the request.
5. When a decision email arrives, note the outcome, but wait for the Reimbursements report before marking the case reimbursed.

Some tools automate this step. Return Disputes, for example, lets you forward Seller Support emails so case numbers and decisions attach to the right unit, then matches them against the Reimbursements report. Whether you automate it or not, the principle is the same: the case ID must end up next to the LPN.

What happens when a reimbursement is reversed?

A reversal means Amazon took back all or part of a reimbursement it had already paid, and it appears as a separate event rather than a change to the original row. Your log should record the reversal and reopen or close the case deliberately.

Reversals can happen for several reasons, for example when a unit that was reimbursed is later found or received. You do not need to know every cause to handle them well. You just need to notice them.

During reconciliation, look for rows that reference a case-id or FNSKU you already marked reimbursed, especially rows with negative amounts or inventory adjustments. When you find one, add the reversal amount and date to the notes column and decide whether the reversal is correct. If you believe it is not, you can open a follow-up case and reference the original case ID and reimbursement-id.

This is why "reimbursed" should mean "reimbursed as of the last reconciliation", not "closed forever". Keep the row visible rather than archiving it immediately.

Cash vs. inventory reimbursements: what is the difference?

A cash reimbursement pays you money for the unit, while an inventory reimbursement resolves the case by adding a unit back to your sellable stock. Both count as a resolution, but they affect your books differently.

You can tell them apart with two columns. If quantity-reimbursed-cash is greater than zero, you were paid in money and amount-total shows how much. If quantity-reimbursed-inventory is greater than zero, the resolution was stock, and the cash amount may be zero.

Record the type in your case log. An inventory reimbursement on a makeup brush set means your available quantity should rise, so cross-check your inventory rather than waiting for money that will never arrive. Mixing the two types up is one of the most common reasons a case looks "unpaid" when it was actually resolved.

How do you run a monthly reimbursement reconciliation?

Run a monthly reconciliation by downloading the latest Reimbursements report, matching every row to your case log by case-id and then by FNSKU, and updating statuses, amounts, and reversals. For most sellers this takes well under an hour once the log is in shape.

Here is a routine you can follow on the same day each month:

1. Download the Reimbursements report for the previous month, plus a small overlap with the month before to catch late rows.
2. Remove duplicate rows by reimbursement-id so each event is counted once.
3. For every row with a case-id, find the matching case in your log and set it to reimbursed, recording amount-total, the reimbursement type, and the reimbursement-id.
4. For rows with no case-id, filter by FNSKU and match to open cases filed before the approval-date, using your chosen date window. Mark these matches as probable.
5. Scan for negative amounts or adjustments on cases you already marked reimbursed, and record any reversals.
6. Review every case still marked filed. If it has been open longer than you are comfortable with, check the email thread and consider a polite follow-up.
7. Review every case marked needs info and make sure the requested photos or details were actually sent.
8. Total the month: cases filed, reimbursed, denied, still open, and the cash and inventory recovered.
9. Save the downloaded report and a copy of the log with the month in the file name, so you have an audit trail.

Over a few months, this routine will also show you patterns: which products return most often in bad condition, and which issue types are most often approved. That feedback loop improves the tickets you write, which is covered in writing a Seller Support ticket that gets approved.

A worked example of one reconciliation

For example, imagine your log has four open disputes at the start of the month. The report shows one row with a case-id that matches a returned kitchen knife set, paid in cash. A second row has no case-id but matches the FNSKU of a pair of wireless earbuds with charging case you disputed earlier, approved after your filing date.

You mark the first as reimbursed and the second as reimbursed (probable). The third case, a blender with attachments, has a decision email saying it was denied, so you mark it denied. The fourth, a phone case bundle, is still waiting, so it stays filed and gets a note to check again next month.

LPN            FNSKU       Case ID      Status                 Type
LPNR8K2M4QX7T  X00ABC1234  31847260593  Reimbursed             Cash
LPNT5W9Q2HB3K  X00DEF5678  31851174220  Reimbursed (probable)  Cash
LPNQ7J3N8VZ1R  X00GHI9012  31853902418  Denied                 -
LPNM2K6P4XW9D  X00JKL3456  31860027731  Filed                  -

Frequently asked questions

Does the Reimbursements report show which returned unit was paid?

No. The Reimbursements report does not include the LPN, so it cannot point to a specific physical unit on its own. You connect a payout to a unit through the case-id, or through FNSKU and dates, and then through your own case log that stores the LPN.

What if a reimbursement row has no case-id?

Filter the report by the FNSKU of your disputed unit and look for approval dates after your filing date, within a window you choose and apply consistently. Mark any match found this way as probable, and match the oldest open case first when several share the same FNSKU.

How often should I reconcile reimbursements?

Monthly works well for most sellers because reports download by date range and a month is a natural chunk. If you file a large number of disputes, a lighter weekly check of new Seller Support emails plus a monthly report reconciliation keeps the log accurate without much effort.

Can Amazon take back a reimbursement it already paid?

Yes, a reimbursement can be reversed later, and the reversal shows up as its own event. Keep reimbursed cases visible in your log, check for negative amounts or adjustments on known case IDs each month, and open a follow-up case if you believe a reversal is incorrect.

Is an inventory reimbursement as good as cash?

It depends on your situation. An inventory reimbursement puts a sellable unit back into your stock, which has value if the product sells, while cash is immediate. Either way, record the type so you do not chase a cash payout for a case that was already resolved with inventory.