> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sourcedock.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Needs a look: claims Amazon's reports can't prove

> 3 min read · You can still file these, but Amazon may say no. Every reason, and what to check first.

## In short

Amazon's reports can't prove these claims either way. You can still file them, but Amazon may say no, so they aren't in your **At risk** total.

Say Amazon took 1 box of pens out of your stock and paid nothing. The card says "Amazon took 1 out of your stock, so Amazon may owe you." Check it first, then **Copy claim details**, **File a claim** and **Mark as filed**.

![The pens card: Taken with no payment, 1 unit, Oct 30, Claim by Nov 29 (23 days left), \$2.00, and Amazon took 1 out of your stock, so Amazon may owe you.](https://mintcdn.com/sourcedock/DPrpNlPg24y_JX8m/images/deep-dives/claims-walkthrough/20-pens-needs-a-look-card.png?fit=max\&auto=format\&n=DPrpNlPg24y_JX8m\&q=85\&s=6a538a0cf4c5574e746c193e05d76281)

Pens: Amazon took 1 out of stock and paid nothing. Notice the words may owe, and no days tag under the money.

Its box starts with "This needs a look because Amazon's reports can't prove it either way, so Amazon may say no." Each claim then says what happened, why, what to check, and its last day. Ask Jax: "Why is this flagged?"

## More details

> [accordion] Taken, or graded again
>
> "Amazon took 3 out of your stock, so Amazon may owe you." Amazon took units out and paid nothing. It may say they weren't yours.
>
> A damage Amazon graded again later: Amazon logged damage, then called it something else. It's still a claim on the first damage, but Amazon often says no.

> [accordion] Amazon may have paid already
>
> **"SourceDock is checking Amazon's reimbursements report, which it couldn't read on its last syncs."** Amazon sometimes pays with a new unit instead of money, and only that report shows it. Nothing to do. It goes back to **Ready to claim** once the report comes in.
>
> **"Amazon paid for 3 units as damaged on the way in on Oct 26, 2026, but didn't say which units. It may be for these. Check before you file."** Check your reimbursements in Seller Central first.
>
> **"Amazon got fewer units than were sent and paid for some of them, but its payments don't say which shipment they were for."** You can ask about the rest, but Amazon may say no.

> [accordion] Amazon paid, then took it back
>
> **"Amazon paid you for this item, then took the money back. SourceDock has no return on file, so a new claim may be turned down."** The refund's line says "never returned, Amazon paid, then took it back · Needs a look". Look it up in Seller Central with the ids on the card.
>
> **"Amazon paid \$11.00 on Aug 8, 2026, then took it back on Aug 12, 2026. Check whether to file again."** It usually means Amazon found the units. Look up the **Reimbursement id** and **Taken back in** in Seller Central. File again only if the units are still missing.

> [accordion] A shipment that may have had a typo
>
> "The shipment said 12 and Amazon got 10. The purchases on SourceDock from before this shipment are fewer than it said, so the shipment may have had a typo. Check how many were bought before filing." Your purchases can't prove you sent that many. Check how many you bought, and fix the purchase if it's wrong.

> [accordion] Paid in part
>
> Amazon can pay for only part of a short box or a refund, and say which one. The claim then stays in **Ready to claim** for the units still unpaid. Its line says how much came in, like "Amazon paid \$36.00 of \$91.00 so far."

> [accordion] Amazon paid, then found it
>
> That's not a claim, even when Amazon's reports can't tie the payment to that unit. Details lists it as paid, with a note, like "Amazon paid you for these, then found them. Amazon may take the money back. There is nothing to file."


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.