CSV Format Guide
Understand the CSV formats ReimburseOps accepts, which fields are required, and how to download your reimbursement report from Amazon Seller Central.
File Requirements
- Format:
.csv - Encoding: UTF-8 (preferred)
- Delimiter: Comma (preferred)
- Header row: Required — ReimburseOps uses headers for auto-mapping
Reimbursement CSV
This is your primary input. Download it from Amazon Seller Central.
Required Fields
| Logical Field | Description |
|---|---|
reimbursement_date | Date the reimbursement was issued |
reimbursement_amount | Dollar amount paid out |
fnsku or asin | Product identifier (at least one required) |
Recommended Fields
| Logical Field | Description |
|---|---|
event_type | Type of reimbursement event (e.g., WAREHOUSE_DAMAGE, LOST_INBOUND) |
quantity | Number of units involved |
currency | Currency code (e.g., USD) |
reference_id | Amazon’s internal reference for the case |
The more fields you include, the better ReimburseOps can detect inconsistencies. But only the three required fields are needed to run an audit.
How to Download from Amazon Seller Central
- Log in to Seller Central
- Navigate to Reports → Fulfillment → Reimbursements
- Select a date range — longer ranges give more data to analyze
- Click Generate Report
- Download the resulting CSV file
Amazon’s column headers vary slightly by marketplace, but ReimburseOps’s auto-mapper handles the common variations.
Sourcing Cost CSV
Optional but recommended. Enables the Under Reimbursed rule.
Required Fields
| Logical Field | Description |
|---|---|
sourcing_cost | Your per-unit cost for the product |
fnsku or asin | Product identifier (must match your reimbursement data) |
You can include additional columns — ReimburseOps ignores anything it doesn’t need.
Tips for Cost Data
- Use the same identifier type (
fnskuorasin) as your reimbursement CSV for best matching - If you track costs per batch, use the most recent cost per SKU
- ReimburseOps always uses the latest cost record when multiple entries exist for the same FNSKU
Field Auto-Mapping
When you upload a CSV, ReimburseOps:
- Reads all column headers
- Compares them against known Amazon header variations
- Suggests a mapping for each logical field
- Shows you a preview with sample rows
You can override any suggestion before confirming. Common Amazon headers like amount-total, fnsku, asin, and approval-date are recognized automatically.
Matching Logic
ReimburseOps links reimbursement records to cost records using:
- Primary match: FNSKU — the most reliable Amazon identifier
- Fallback match: ASIN — used only when FNSKU is unavailable
SKU-based matching is not supported in the current version to avoid false matches across marketplace variations.