I imported a settlement CSV straight into QuickBooks without checking it first. Three fee columns had blank values instead of zeros, so QuickBooks silently dropped those rows. I was off by $4,200 on the reconciliation and spent two days hunting for the discrepancy. Now I validate every settlement file before conversion — the tool caught 67 blank amount fields in my last batch that would have caused the same nightmare.
Amazon Settlement CSV Validator
or drop files here .csv, .txt, .xls, .xlsx, .xlsm (up to 50 MB)
Free 5-row preview · No sign-up required
Invoice import blocked if Sales Tax enabled in QBO
Validate Complete
Your converted file is ready!
Download now before closing this page
Validation Report Format
Showing valid rows only (download includes all rows + errors)
All rows valid
| $ |
|---|
+ more rows
valid rows
invalid rows skipped from preview
credits
| Row | Column | Value | Error |
|---|---|---|---|
Showing first 50 errors. more errors not shown.
more errors hidden. Download the full validation report to see all errors.
Validation Report Download
The download includes your original file with an added "Validation Error" column showing error messages for each row. Valid rows have an empty error column.
• credits
Use credits to download
Click any download button to use your credits
- Full CSV & Excel export
- Google Sheets export
- Instant browser download
for credits
One-time payment
256-bit SSL encryption
14-day money-back guarantee
PCI DSS compliant
Powered by Paddle
Want to save on credits?
Buy bundles and get up to 27% off. Perfect for recurring monthly conversions.
Liked the preview?
Upload your actual file to get the real conversion
Check your Amazon Settlement Report V2 for missing columns, data errors, and formatting issues before importing to QuickBooks.
Free preview — then from $5. Save with bundles.
Free preview before you pay
Files never leave your browser
No account needed to start
Validation Questions Answered
What settlement report should I use?
Use Settlement Report V2 (Date Range Report) from Seller Central. This is the only report that matches your bank deposits.
Is this tool free?
First transactions are free to preview. Full conversions use credits based on transaction count.
What happens to my data?
Your file is processed entirely in your browser. No data is uploaded to our servers.
How Validation Works
1
Export from Amazon Seller
Reports → Payments → All Statements → Download Flat File V2
2
Upload CSV
Upload your Settlement Report V2 export file
3
Review Validation Results
Check your Amazon Seller data for errors and warnings
Issues are flagged inline with clear fix suggestions — review and correct before you import.
How People Use This
Amazon changed their settlement format mid-quarter and my old import workflow broke silently. I had two weeks of unreconciled deposits before I noticed. The validator immediately flagged that the column headers had changed and three new transaction-type values weren't in the expected set. Caught the schema drift before it wrecked my books.
A client re-saved their settlement CSV in Excel before sending it to me. Excel converted the settlement-id to scientific notation and corrupted half the date columns. The validator showed me exactly which 890 rows had unparseable dates and which settlement IDs were mangled. Instead of importing garbage into my tax prep software, I asked the client to re-download the original file.
I was converting settlement reports to QuickBooks journal entries and kept getting amount mismatches. The validator found 23 rows where amount-description didn't map to any known fee category — turned out Amazon had introduced new fee types that my conversion template didn't handle. Saved me from booking $1,800 in fees to the wrong accounts.
Why Validate Before Converting?
Catch Issues Early
Bad data causes conversion failures and import errors. Missing columns, wrong date formats,
or invalid values can waste hours troubleshooting QuickBooks import rejections.
Validating first identifies exactly which rows have problems before you process.
What This Tool Checks
We validate your Amazon settlement export against the expected schema:
- Required columns present (settlement-id, amount-description, amount)
- Date formats parseable (ISO 8601)
- Currency values valid
- Transaction types recognized
You get a detailed error report with row numbers to fix issues at the source.
Your Data Stays Private During Validation
Every Row Checked
Each record is validated against format rules. Catch errors before they reach your platform.
Runs in Your Browser
Validation happens locally. Your data never leaves your browser.
GDPR Compliant
No files uploaded, no data retained. Full EU privacy compliance.
// PRICING //
Choose the plan that fits your needs
Pay as you go
Just start processing on any tool page
$1/credit
Tools processing starts from 5 credits. Then 1 credit = 1k rows. No sign-up needed.
OR
Credit Bundles
$
/Credit
One-time purchase
- No monthly commitment
- Credits valid for one year
- Access to all tools
- Full file downloads
Monthly Bundles Pro
$
/Credit
Best for professionals and content creators
Annual Discount
Per month, billed annually:
Save 20% more
- Credits refresh monthly
- Priority processing
Purchase Credits
- Full CSV & Excel export
- Google Sheets export
- Instant browser download
for credits
256-bit SSL encryption
14-day money-back guarantee
PCI DSS compliant
Powered by Paddle
Do unused credits expire?
One-time credit bundles are valid for one year. Subscription credits refresh monthly. You can use credits across any tool, anytime.
Is my data secure?
Files process entirely in your browser. We're GDPR compliant with TLS encryption.
Can I get a refund?
Yes! Full refund within 14 days if no credits used. Partial refund for unused credits anytime. Contact sup@spreadsheetbroccoli.com.
Powered by
Paddle
Terms of service applies. VAT included where applicable.
More credits - more savings
Buy bundles and get up to 60% off. Perfect for recurring monthly conversions.
Why Validate Before Importing?
Column Validation
Checks for required columns like settlement-id, amount-description, and amount.
Data Type Checking
Validates dates, currencies, and enum values match expected formats.
Row-Level Errors
Get specific error messages with row numbers for quick debugging.
Fee Type Detection
Validates amount-description values map to known fee categories.
Browser-Based
Files processed locally. Your financial data never leaves your computer.
Instant Results
Get validation results in seconds, even for large settlement files.
Common Target Import Errors
Issues you might encounter when importing Source data to Target - and how we solve them
Missing Settlement ID
The 'settlement-id' column is required but not found
File exported without 'settlement-id' column
Column with values like '16427587891'
Ensure you're using Settlement Report V2 (Date Range Report)
Go to Seller Central → Reports → Payments → Date Range Reports
Missing Amount Description
The 'amount-description' column is required for fee categorization
File without 'amount-description' column
Column with values like 'Commission', 'Principal', 'FBAPerUnitFulfillmentFee'
This column identifies fee types for proper Chart of Accounts mapping
Re-export using Settlement Report V2 format
Invalid Amount Value
The 'amount' column contains non-numeric values
N/A or (blank)
-15.00 or 49.99
Amount must be a numeric value (negative for fees, positive for revenue)
Check for cells corrupted by Excel or manual editing
Unknown Transaction Type
The 'transaction-type' value is not recognized
Sale or Payment
Order, Refund, ServiceFee, Adjustment, Transfer
Amazon uses specific transaction type values
Ensure data hasn't been modified after export
Invalid Date Format
Date columns contain unparseable values
01/15/25 (ambiguous format)
2025-01-15T00:00:00+00:00 (ISO 8601)
Amazon exports dates in ISO 8601 format
Don't open in Excel before validating, or export again
Character Encoding Problem
File contains characters that couldn't be decoded properly
Special characters appearing as ??? or garbled text
Proper text with accented characters
Amazon uses ISO 8859-1 encoding, not UTF-8
Re-download the file without opening/saving in another program
Wrong Report Type
File appears to be an Orders report, not Settlement report
Columns like 'item-price' without 'amount-description'
Columns: settlement-id, amount-description, amount
Use Settlement Report V2 for bank reconciliation, not Orders report
Go to Reports → Payments → Date Range Reports, not Orders report
Frequently Asked Questions
Your data never leaves your device. All files are processed entirely in your browser using client-side JavaScript - no data is stored on our servers or sent anywhere. There's no account to hack, no database storing your files, and no API connections to your bank or accounting software. You upload, convert, download, and we forget it immediately.
No payment or signup required. You can upload your file, see a free preview of the conversion results, and verify everything looks correct before paying anything. If it doesn't work for your files, you haven't wasted any money. We only charge when you're satisfied and ready to download the final converted file.
You can, but free scripts and AI often miss edge cases that break real-world data: missing SKUs, currency formatting quirks, tax calculation errors, or date format mismatches. We have battle-tested validators specifically designed for accounting software imports that catch these issues before they corrupt your books. Plus, you get instant browser-based conversion without installing Python or managing dependencies.
Required columns include: settlement-id (unique identifier), transaction-type, amount-type, amount-description, and amount.
Use Settlement Report V2 (Date Range Report) from Seller Central. This is the only report that matches your bank deposits.
Amazon exports use ISO 8859-1 encoding, not UTF-8. If you open in Excel and re-save, it may corrupt special characters. Download and upload directly.
First transactions are free to preview. Full conversions use credits based on transaction count.
Your file is processed entirely in your browser. No data is uploaded to our servers.
Settlement Report V2 contains fees and matches bank deposits. Orders report shows order details but doesn't reconcile with your bank.
V2 is the newer format with more detailed transaction descriptions. Amazon switched to V2 in 2015, though older accounts may still use V1. Request V2 format from Amazon seller support if needed.
Archived reports can't be imported via API. Log into Amazon Seller Central and click the 'Request Report' button to un-archive your settlement files before validation.
Use Excel's Text Import Wizard and select 'Tab' as the delimiter. Settlement reports are tab-separated, not comma-separated like standard CSV files.
Process settlement reports one period at a time to catch errors early and ensure accurate reconciliation across different settlement cycles.
After Validation: Convert Your Settlement Report V2
Once your Amazon Seller export passes validation, convert it to your accounting format
Amazon Seller
Settlement Report V2
Your validated export
→
Quickbooks Desktop
IIF File
Tab-delimited Intuit Interchange Format for Desktop
settlement-id → DOCNUM
deposit-date → DATE
amount-description → ACCNT
Amazon Seller
Settlement Report V2
Your validated export
→
Quickbooks Online
Journal Entry
Double-entry accounting with debits/credits
settlement-id → JournalNo
deposit-date → JournalDate
amount-description → Account Name
Amazon Seller
Settlement Report V2
Your validated export
→
Xero
Bank Statement
Bank transactions for reconciliation
deposit-date / settlement-end-date → Date
amount → Amount
transaction-type → Payee
Amazon Seller
Settlement Report V2
Your validated export
→
Xero
Sales Invoice
Sales invoices for accounts receivable (B2B, payment terms)
settlement-id → InvoiceNumber
deposit-date / settlement-end-date → InvoiceDate
— → ContactName
🥦
Quick question before you go
Help us improve—what stopped you today?
🎉
Thank you!
Enter your email to claim your welcome bonus