Back to Details

amz-reimbursement-audit

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Reimbursement Audit

报销审核

Amazon changed how it values reimbursements: for inventory lost or damaged in a fulfillment center, it now pays on your product manufacturing (sourcing) cost rather than selling price, and you set that cost in Seller Central. Amazon still runs automated reconciliation and proactively reimburses many warehouse lost and damaged cases on its own. manual claims are for the cases its system did not catch, or closed without paying, and for getting the cost basis right. This skill builds the claim packet that actually gets paid for the cases that fall through.
亚马逊修改了报销估值规则：对于配送中心丢失或损坏的库存，现在将按照产品的制造（采购）成本而非销售价格进行赔付，卖家需在Seller Central中设置该成本。亚马逊仍会进行自动对账，并主动赔付许多仓库丢失和损坏的案例。手动索赔适用于系统未捕捉到、或未赔付就结案的案例，以及用于修正成本依据的情况。本技能可生成能成功获赔的索赔包，覆盖那些被遗漏的案例。

When to use this

使用场景

  • Units lost or damaged in the warehouse that automated reconciliation never reimbursed, or reimbursed for less than expected.
  • A refund processed for a customer but the unit was not returned, or returned damaged.
  • Old reimbursement habits that no longer match the current policy.
  • Multiple claim-eligible events sitting past the filing-window risk.
  • 仓库中丢失或损坏的库存，自动对账从未赔付，或赔付金额低于预期。
  • 已为客户处理退款，但库存未退回或退回时已损坏。
  • 旧的报销习惯不符合当前政策。
  • 多个符合索赔条件的事件即将超出申报窗口期。

The framework. The Four Claim Cases

框架：四类索赔案例

Every Amazon reimbursement case is one of four types. Each has a different evidence requirement, but all four now require cost-basis proof if the seller wants the higher payout.
CaseWhat happenedTrigger reportEvidence required
LostInbound or warehouse lossReconciliation, Inventory Adjustmentsshipment IDs, units lost, manufacturing cost
Warehouse damagedAmazon-caused damageInventory Adjustments code reasonsadjustment IDs, unit cost
Customer returnRefund issued, no return or damaged returnReturns report, Reimbursements reportorder ID, refund date, return status, cost
Fee errorWrong fulfillment fee or referral feePayments reportthe wrong charge, the right charge, the delta
For every case, build cost basis once: the manufacturing (sourcing) cost per unit from the supplier invoice. Amazon defines manufacturing cost as your cost to source the product and excludes shipping, handling, and customs duties. so use the per-unit invoice price, not the fully landed cost. Same number for every future claim on that SKU, set on the Manage Your Sourcing Cost page in Seller Central.
每个亚马逊报销案例都属于以下四类之一。每类的证据要求不同，但如果卖家想要更高赔付，四类案例现在都需要成本依据证明。
案例类型事件描述触发报告所需证据
丢失库存入库或仓库内丢失对账报告、库存调整报告发货ID、丢失数量、制造成本
仓库损坏亚马逊导致的损坏库存调整报告（代码原因）调整ID、单位成本
客户退货已退款，但库存未退回或退回损坏退货报告、报销报告订单ID、退款日期、退货状态、成本
费用错误配送费或推荐费错误付款报告错误收费金额、正确收费金额、差额
对于每个案例，只需计算一次成本依据：从供应商发票中获取的单位制造（采购）成本。亚马逊将制造成本定义为产品的采购成本，不包含运费、手续费和关税。因此请使用发票上的单位价格，而非完全落地成本。该SKU未来所有索赔都使用同一数值，需在Seller Central的“管理采购成本”页面设置。

The 60-day window

60天窗口期

Claims must be filed within 60 days of the triggering event. Anything older is unrecoverable. The first job of any audit is to scan for events near the window edge and file those first.
索赔必须在触发事件发生后的60天内提交。超过期限的无法追回。审核的首要任务是扫描接近窗口期截止日期的事件，并优先提交这些索赔。

Step by step

步骤说明

  1. Collect inputs. The Reconciliation, Inventory Adjustments, Returns, and Payments reports the user can paste. Plus a supplier invoice to read the manufacturing (sourcing) cost per unit for the SKUs involved.
  2. Compute cost basis per SKU. Per-unit manufacturing (sourcing) cost from the supplier invoice. exclude freight, duty, and handling, since Amazon's manufacturing- cost definition leaves them out. This is the number Amazon now wants, set on the Manage Your Sourcing Cost page.
  3. Classify every reimbursable event into one of the four claim cases.
  4. Run the window check. Sort by days since the event. Anything inside 60 days is recoverable. Anything beyond is lost. file the at-risk cases first.
  5. Build the packet per case. Claim narrative, evidence list, cost basis calculation, and the exact case form to open in Seller Central.
  6. Track and follow up. Amazon often denies on a technicality. Plan a follow-up round with the cost-basis evidence attached again.
  7. Run the quality check, then deliver.
  1. 收集输入信息：用户可粘贴对账报告、库存调整报告、退货报告和付款报告。此外还需要供应商发票，以获取涉及SKU的单位制造（采购）成本。
  2. 计算每个SKU的成本依据：从供应商发票中提取单位制造（采购）成本，排除运费、关税和手续费，因为亚马逊的制造成本定义不包含这些费用。这是亚马逊当前要求的数值，需在“管理采购成本”页面设置。
  3. 分类所有可报销事件：将每个事件归入四类索赔案例中的一类。
  4. 窗口期检查：按事件发生后的天数排序。60天内的事件可追回，超过的则无法追回。优先提交临近截止期的案例。
  5. 为每个案例生成索赔包：包含索赔说明、证据清单、成本依据计算，以及在Seller Central中提交索赔的具体路径。
  6. 跟踪与跟进：亚马逊常因技术细节拒绝索赔。计划一轮跟进，再次附上成本依据证据。
  7. 质量检查，然后交付。

Output format

输出格式

undefined
undefined

Reimbursement Audit. [SKU or catalog]

报销审核. [SKU或目录]

Cost basis per SKU: [SKU] . [$ per unit] . source: [supplier invoice, sourcing cost]
每个SKU的成本依据: [SKU] . [单位美元价格] . 来源: [供应商发票，采购成本]

Claim packet

索赔包

Case 1. [type] . event date . days remaining . units . $ at stake Narrative: [one-paragraph factual story] Evidence: [list] Cost basis: [$] Where to file: [exact Seller Central path]
...
案例1. [类型] . 事件日期 . 剩余天数 . 数量 . 待赔付金额 说明: [一段事实性描述] 证据: [列表] 成本依据: [美元金额] 提交路径: [Seller Central具体路径]
...

Priority order

优先级排序

  1. [Cases inside 14 days of window edge]
  2. [Cases by dollar size]
undefined
  1. [距离窗口期截止14天内的案例]
  2. [按金额大小排序的案例]
undefined

Worked example

示例

A seller has 24 units of a 22 USD product lost in an inbound shipment 53 days ago, plus 8 refunds where the units never returned, average 31 days ago.
Cost basis: 6.40 per unit, the manufacturing (sourcing) cost read straight off the supplier invoice, freight and duty excluded. Lost case: 24 units x 6.40 = 154 USD owed, filed inside the 60-day window with the cost evidence and the shipment ID, on day 53. Customer-return cases: 8 separate cases, filed in priority order, average 29 days remaining. Amazon's automated reconciliation may have already reimbursed some of these. the audit is for the cases it missed or closed without paying, and to make sure the sourcing cost is set so the payout is on cost basis rather than a lower default.
某卖家有24件售价22美元的产品在入库发货时丢失，距今53天；另有8笔退款，库存未退回，平均距今31天。
成本依据：单位6.40美元，直接从供应商发票读取的制造（采购）成本，不含运费和关税。丢失库存案例：24件 × 6.40美元 = 154美元待赔付，在第53天提交索赔，附上成本证据和发货ID，仍在60天窗口期内。客户退货案例：8个独立案例，按优先级提交，平均剩余29天。亚马逊的自动对账可能已赔付其中部分案例，本次审核针对遗漏或未赔付的案例，并确保设置采购成本，使赔付基于成本依据而非较低的默认值。

Quality check

质量检查

  • Cost basis per SKU is computed before any claim narrative is written.
  • Every event is classified into one of the four cases.
  • The 60-day window is checked first. at-risk cases are filed before larger ones.
  • Each packet has narrative, evidence list, and cost basis attached.
  • A follow-up plan exists for the common Amazon initial denial.
  • 先计算每个SKU的成本依据，再撰写索赔说明。
  • 每个事件都归入四类案例中的一类。
  • 首先检查60天窗口期，临近截止期的案例优先提交。
  • 每个索赔包都包含说明、证据清单和成本依据。
  • 针对亚马逊常见的首次拒绝情况制定跟进计划。

Common mistakes

常见错误

  • Assuming automation catches everything. Amazon proactively reimburses many warehouse lost and damaged cases, but not all. the ones it misses or closes without paying still need a manual claim inside the window.
  • Filing without cost evidence. The default payout dropped sharply. cost basis is the difference between recovering 40 cents and 100 cents on the dollar.
  • Missing the window. Events past 60 days are lost.
  • Submitting and giving up after one denial. Amazon often denies first, accepts on resubmission with the same evidence.
  • 假设自动化能覆盖所有情况：亚马逊会主动赔付许多仓库丢失和损坏的案例，但并非全部。遗漏或未赔付的案例仍需在窗口期内提交手动索赔。
  • 未提供成本证据就提交索赔：默认赔付金额大幅降低。成本依据是收回全额赔付与仅收回少量赔付的关键差异。
  • 错过窗口期：超过60天的事件无法追回。
  • 提交一次被拒就放弃：亚马逊常先拒绝，重新提交相同证据后会接受索赔。

Built by Jay GPT Pro

由Jay GPT Pro开发

Part of Amazon Pro Skills. Production-grade skills for serious Amazon sellers. Free and open. Built by Jay Margaliot.
I share a new AI play for Amazon sellers every week, free, in my WhatsApp group. Join here: https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY
属于Amazon Pro Skills系列。为专业亚马逊卖家打造的生产级技能。免费开源。由Jay Margaliot开发。
我每周会在WhatsApp群组中分享一个面向亚马逊卖家的新AI玩法，免费加入：https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY