What you receive
- Per-line supplied charge versus processed units × your matching per-unit rate
- Mismatch queue ranked by absolute difference with your tolerance
- Removal-order groups with line counts, first/last processed dates, and span
- Positive and negative fee differences totaled separately, never netted
- Removal, disposal, and per-rate summaries including unused supplied bands
Who it is for
FBA sellers, agencies, and finance teams reconciling per-unit removal and disposal charges that arrive across many dated transaction lines against their own current rate card before a human reviews the source report.
Delivery: usually a structured result, workbook, or ZIP depending on the tool.
How it stays safe
Friday performs arithmetic only on the seller-redacted processing lines and rate-card bands you provide. It reads no Amazon account, removal order, transaction report, or current removal/disposal rate table and verifies no value. The recompute is processed units × your exact matching action, size-tier, and weight-band rate; Friday looks up no rate, infers no size tier, and does not model liquidation, hazmat, minimum, or other charges. Grouping lines under a removal-order alias is context, not a timing finding. A difference is not proof Amazon billed incorrectly, a credit is due, or a dispute is available. Friday files no case, requests no reimbursement, cancels or creates no removal order, changes no shipment, inventory, fee, listing, or seller account, and does not publish listings. A human must verify the source report and current FBA removal and disposal fee guidance before acting.
Synthetic sample
See the deliverable structure before buying
{
"charge_count": 6,
"removal_order_count": 3,
"used_rate_count": 3,
"processed_units": 94,
"total_reported_fee": 128.67,
"total_recomputed_fee": 128.22,
"total_fee_discrepancy": 0.45,
"possible_overcharge_exposure": 0.75,
"possible_undercharge_exposure": 0.3,
"mismatch_count": 2,
"high_charge_count": 1,
"review_queue_preview": [
{
"priority_rank": 1,
"charge_reference": "NW-RMV-002",
"removal_order_alias": "RO-NW-71",
"action": "REMOVAL",
"reported_fee": 6.0,
"recomputed_fee": 5.25,
"fee_discrepancy": 0.75,
"status": "review_mismatch"
},
{
"priority_rank": 2,
"charge_reference": "NW-DSP-004",
"removal_order_alias": "RO-NW-88",
"action": "DISPOSAL",
"reported_fee": 11.34,
"recomputed_fee": 11.64,
"fee_discrepancy": -0.3,
"status": "review_mismatch"
},
{
"priority_rank": 3,
"charge_reference": "NW-RMV-006",
"removal_order_alias": "RO-NW-93",
"action": "REMOVAL",
"reported_fee": 91.8,
"recomputed_fee": 91.8,
"fee_discrepancy": 0.0,
"status": "review_high_charge"
}
],
"removal_order_summaries_preview": [
{
"removal_order_alias": "RO-NW-71",
"charge_line_count": 3,
"processed_units": 19,
"processed_span_days": 14,
"reported_fee": 22.62,
"recomputed_fee": 21.87,
"mismatch_count": 1
},
{
"removal_order_alias": "RO-NW-88",
"charge_line_count": 2,
"processed_units": 15,
"processed_span_days": 2,
"reported_fee": 14.25,
"recomputed_fee": 14.55,
"mismatch_count": 1
}
],
"publish_status": "draft_needs_review",
"safety": "Arithmetic on seller-supplied processing lines and rates only. A difference is not proof Amazon billed incorrectly or that a credit is due; no case is filed and no removal order, shipment, inventory, fee, listing, or account is changed."
}
This sample uses synthetic facts. Your output is generated only from the facts you submit.