Amazon Payment Ahead of Matching (PAM) explained
Cost Optimisation
Published on
Contributors
Herbie King
Share

Amazon’s Payment Ahead of Matching (PAM) adds a new layer to vendor reconciliation
Amazon has introduced Payment Ahead of Matching (PAM), a change to how it handles eligible vendor shortage payments. RT7 has started seeing these entries in recent remittances, making this a timely check for anyone managing Amazon reconciliation.
The change can mean receiving money sooner. It also creates additional payment and reversal entries that finance teams need to match correctly to avoid double-counting or misstating outstanding balances.
What has changed?
Normally, Amazon deducts a shortage claim where its records show a difference between the quantity invoiced and the quantity received. Its matching process continues looking for the goods, and the deducted amount can be paid back once receipt is confirmed.
Payment Ahead of Matching changes the timing of that payment for eligible invoice lines.
Where historical delivery information suggests the goods are likely to be received and matched, Amazon can pay the shortage amount on the invoice due date, before matching is complete.
Eligibility is assessed at invoice-ASIN level. That means PAM may cover some of a shortage rather than its full value. Price discrepancies are excluded from the process.
Amazon’s guidance describes a period of 60 days after the invoice due date. If goods remain unmatched at that point, Amazon applies the relevant shortage deduction.
The advance is therefore provisional. Receiving it does not mean the shortage has been finally resolved.
What this looks like in practice
Take an invoice for $100,000 with a shortage claim of $30,000. In this example, the full shortage amount qualifies for PAM.
On the invoice due date, the entries look like this:
Entry | Amount |
|---|---|
Original invoice | $100,000 |
Shortage claim deduction | −$30,000 |
Payment Ahead of Matching | +$30,000 |
Payment before any other adjustments | $100,000 |
The vendor receives the full invoice amount upfront.
If Amazon subsequently matches the entire shortage, it reverses the $30,000 PAM advance and records a corresponding $30,000 shortage claim payment. Those entries offset each other. The vendor has received the money earlier, rather than receiving an additional $30,000.
If $10,000 remains unmatched at the end of the period, Amazon’s example shows these further entries:
Entry | Amount |
|---|---|
Reversal of PAM advance | −$30,000 |
Shortage claim payment | +$30,000 |
New deduction for the unresolved shortage | −$10,000 |
Net adjustment | −$10,000 |
The vendor is left with $90,000 against the original $100,000 invoice, before any other adjustments. The remaining $10,000 is still a shortage deduction and can be considered through the applicable dispute process.
Why this matters for your finance team
One invoice can now produce several related entries across different remittances.
Amazon’s guidance identifies references including “PAM” for the advance, “PAMR” for its reversal and “SCR” for a shortage claim payment. Following the relationship between those entries is essential to understanding the final position.
In the remittances RT7 has reviewed, a PAM reversal can also be linked to a shortage-related reference rather than directly to the original invoice. That makes matching by the original invoice number alone more difficult.
The main risk is treating related movements as separate receipts or recoveries.
An advance and a subsequent shortage claim payment may represent the same underlying amount. Without accounting for the corresponding reversal, a finance team could double-count receipts, misstate the outstanding balance or incorrectly report revenue.
The bookkeeping treatment needs to follow the business’s accounting policy consistently across the deduction, advance and reversal. The remittance description alone should not determine how an entry is posted.
What vendors should check now
Start by making whoever handles your Amazon reconciliation aware of PAM and its associated entries.
Then check the following:
Link the transactions. Trace the original invoice, shortage deduction, PAM advance and subsequent adjustments together.
Check the amount covered. An advance may cover only part of the shortage.
Track unresolved balances. Receiving a PAM payment does not establish that the underlying shortage is closed.
Check subsequent remittances. Look for the reversal and any remaining deduction when reviewing the final position.
Review posting rules. Make sure automated imports or manual processes do not count related payments twice.
If you use a recovery provider, ask how PAM is identified and taken into account before a recovery is reported or a fee is calculated.
What this means for shortage recovery
PAM adds another distinction to shortage recovery: money advanced by Amazon needs to be separated from amounts that remain unpaid and require further action.
A shortage deduction viewed in isolation may no longer give an accurate picture of the recoverable balance. The related advances and adjustments need to be checked first.
Based on RT7’s review so far, the change does not affect historical recovery work. Our immediate focus is on how PAM appears in new shortage transactions and how those entries flow through reconciliation and recovery reporting.
Keep the full invoice picture in view
Payment Ahead of Matching can improve the timing of cash receipts. It also adds more entries for finance teams to connect and explain.
That makes accurate Amazon reconciliation more valuable. Your team needs to see what the invoice was worth, what Amazon advanced, what it subsequently reversed and what remains genuinely outstanding.
RT7 is incorporating PAM into its reconciliation processes, including AVAR, to account for these additional movements.
If PAM entries are appearing in your remittances and you are unsure how they relate to your invoices, contact RT7 to discuss your Amazon reconciliation.

