How to Convert Amazon Seller CSV Reports to Excel

Amazon Seller Central hides most of your real business numbers inside CSV downloads — order reports, settlement reports, and payment transaction exports that look like gibberish when opened carelessly. The reports live under Reports > Payments, where you will find the Transaction view, All statements, and Date Range Reports. Settlement reports can also be requested and downloaded as CSV from the same area. The fastest clean route is: download the CSV, import it into Excel through Data > From Text/CSV (not by double-clicking), fix the column types, and you have a workbook ready for bookkeeping and profit analysis.

The reason so many sellers struggle is not the download — it is what Excel does to the file on the way in. Amazon's CSVs contain money columns that Excel may read as text, dates in formats that sort wrong, SKUs like "3-2026" that Excel converts into March 2026, and settlement files with extra header rows that break column alignment. Once you learn the import wizard and a handful of cleanup habits, turning any Amazon seller report CSV into Excel becomes a two-minute job instead of a monthly headache.

Below you will find three numbered methods to get the file into Excel, a table of the four main report types and their quirks, a walkthrough of how to decode a settlement report and build a profit pivot, and fixes for every common breakage — decimal commas on EU marketplaces, mixed date formats, and multi-currency amounts.

The 3 Best Ways to Open an Amazon Seller CSV in Excel

Method 1: Double-click the CSV (quick but fragile)

Double-clicking the downloaded file opens it in Excel instantly, and for a quick glance at an order report it is often enough. Excel parses the comma separation automatically and shows you the data. This is the route most sellers take first, and it is also the route that silently corrupts the most data.

It breaks in specific, repeatable ways. Dates like 01/02/2026 can be interpreted as February 1 or January 2 depending on your locale, and once Excel converts them you cannot always tell which rows flipped. SKU codes with leading zeros (0034-BLK) lose the zeros. SKU-like values such as 3-2026 or 1/4 cup scoop get converted into dates. Currency columns on EU marketplace reports may arrive with decimal commas that Excel treats as text, so SUM formulas return zero. For viewing only, double-clicking is fine. For anything you will calculate on — bookkeeping, profit analysis, tax prep — do not trust it. See Method 2 or read our guide to fixing mangled csv-to-excel-decimal-comma issues for more on the decimal-comma trap.

Method 2: Use Excel's Data > From Text/CSV import wizard (the safe route)

This is the method to use for every report that matters. The import wizard lets you declare the encoding, the delimiter, and — critically — the data type of each column before Excel touches the data. That is how you stop dates from being guessed and SKUs from being destroyed.

In Excel, go to Data > From Text/CSV (in newer versions it may read "Get Data > From File > From Text/CSV").
Select your downloaded Amazon CSV and click Import.
In the preview dialog, set File Origin to 65001: Unicode (UTF-8) — Amazon exports are UTF-8, and this keeps accented characters and symbols intact.
Set the delimiter to Comma.
Click Transform Data to open Power Query, or Load for a quick import. Use Transform Data when you need column-type control.
In the Power Query editor, check the type icons on each column header. Change amount and fee columns to Decimal Number, date columns to Date, and — this is the important one — sku and asin columns to Text.
Watch for an extra header row or footer rows: Amazon settlement CSVs sometimes ship with summary lines at the top. Remove them with Remove Top Rows / Remove Bottom Rows before typing columns.
Click Close & Load.

What you get is a clean table where dates are dates, amounts sum correctly, and SKUs survive. It takes about a minute once you have done it twice, and it is the only import method that reliably survives EU marketplace files. For a deeper walkthrough of column-type control during import, see csv-to-excel-column-mapping. If you also work with Etsy exports, the same wizard-first discipline applies — we cover that in csv-to-excel-etsy-seller.

Method 3: Use a free online converter (no wizard needed)

If you do not want to think about encodings and column types — or you are converting on a machine without Excel's full import tools — a free online converter is a legitimate shortcut. The free CSV to Excel converter takes your Amazon CSV upload and returns an .xlsx workbook you can open immediately, with the conversion handled server-side. This is handy when a settlement CSV has encoding problems your local Excel keeps mangling, because the conversion does not depend on your machine's regional settings.

The trade-off is control: an online converter cannot ask you whether a column should be Text or Number the way the wizard does. So after downloading the converted workbook, still spot-check your SKUs for leading-zero loss and your dates for locale flips, and fix them before doing math. For sellers who process dozens of marketplace exports a month, combining the two approaches works well — convert the bulk file online, then run the final cleanup with a batch-convert-csv-to-excel workflow for repetitive monthly reports.

Which Report Should You Download? (Comparison Table)

Not all Amazon exports are equal. Each report type has different quirks, and knowing which file you need saves you from cleaning the wrong one.

Report type	What it's for	CSV quirks to expect	Cleanup priority
Order reports	Listing every order with buyer, SKU, quantity, and item price	Dates can import as text; SKU codes may be mangled into dates by double-click opens	Medium — mostly dates and SKUs
Settlement reports	Your payout accounting: sales, fees, refunds, reimbursements, taxes per settlement period	Extra header/footer summary rows; many columns; fee and refund columns may arrive as text; decimal commas on EU marketplaces	High — this is the money file, clean it properly
Payments / Transaction view	Itemized list of every transaction feeding the settlement	Very long row counts; "Other" transaction types mixed in; multi-currency columns	Medium-high — filter out noise before analysis
Inventory reports	Stock levels, stranded inventory, replenishment alerts	ASIN and SKU columns with leading zeros; large file sizes	Low — mostly a SKU-preservation job

For profit analysis, the settlement report is the one that matters. Everything else feeds into it or reconciles against it.

Decoding a Settlement Report: Columns and the Profit View

A settlement CSV is intimidating the first time — dozens of columns with names Amazon never explains in plain language. Here is what the key ones mean and how to turn them into a profit view.

The columns that matter

Transaction type — labels each row: Order, Refund, Fee Adjustment, Reimbursement, Service Fee, and others. This is the column you group by.
Principal — the gross amount of the sale before Amazon's cuts.
Fees (various fee columns) — referral fees, FBA fulfillment fees, storage fees. These are negative amounts that eat your margin.
Refunds — rows where the principal is returned to the buyer, plus the fee reversals that accompany them.
Reimbursements — Amazon paying you back for lost or damaged FBA inventory. Positive for your P&L.
Marketplace facilitator tax — sales tax Amazon collects and remits on your behalf in certain jurisdictions. It appears on the report but is not your revenue; do not count it as income.

Building the profit pivot

Import the settlement CSV with Method 2, making sure every money column is Decimal Number.
Select any cell in the table and choose Insert > PivotTable.
Drag Transaction type into Rows.
Drag Principal and each fee/amount column into Values, set to Sum.
Add a calculated field (or a formula column beside the pivot) that nets them: = Principal + Reimbursements − Fees − Refunds for each row type, and a grand total for the period.
Refresh monthly: paste the new settlement CSV rows into the source table, refresh the pivot, and your profit view updates.

That pivot is your real seller P&L for the settlement period. When a month looks off, filter the transaction-type rows to Refund or Fee Adjustment and drill down to the offending orders. Once you have the pivot habit, layering a visual summary on top becomes easy — our csv-to-excel-charts-dashboard guide shows how to turn the same table into a readable dashboard.

When It Breaks: Amazon CSV Troubleshooting

These are the five breakages Amazon sellers hit most often, with the fix for each.

Decimal separators in EU marketplaces. German, French, Spanish, and Italian marketplace exports use the decimal comma (12,99) while your Excel may expect a decimal point. If amounts import as text and your SUMs return zero, this is why. Fix: in the import wizard's Transform step, change the column locale — in Power Query, change type using the correct locale (e.g., German) so 12,99 becomes a number. Full details in csv-to-excel-decimal-comma.

Dates in mixed formats. Some exports mix MM/DD/YYYY order rows with DD/MM/YYYY summary rows, or ship dates as text. Excel then sorts January before February wrong, or fails to sort at all. Fix: in Power Query, set the date column's locale explicitly when typing it, or use DATEVALUE with a helper column. Our csv-date-format-fix-excel walkthrough covers the exact steps.

Multi-currency amounts. If you sell on multiple marketplaces, amount columns may contain GBP, EUR, or USD values side by side, sometimes with a currency code column and sometimes not. Fix: keep the marketplace or currency column, convert everything to your home currency in a helper column with a rate table, and never sum across currencies directly.

Hidden columns and extra header rows. Settlement downloads sometimes open with a title row, blank rows, or repeated header rows mid-file. Fix: in Power Query use Remove Top Rows and filter out any row where the header text repeats, or open the CSV in a text editor first and delete the junk lines before importing.

SKUs turning into dates or losing leading zeros. 3-2026 becomes March 2026, 0034 becomes 34. Fix: always import the SKU and ASIN columns as Text in the wizard (Method 2), and never double-click-open a file you intend to match against your inventory system. If the damage is already done, re-download and re-import — there is no reliable way to recover mangled SKUs after the fact.

Reconciling against your own records. Once the report is clean, compare its totals to your bank payouts and your inventory system before treating them as final. VLOOKUP your cleaned SKU column against your product list to catch typos and discontinued items, and flag any transaction type you cannot explain — a mystery fee in one settlement often becomes a real charge in the next.

Your 60-Second Amazon CSV Checklist

[ ] Downloaded from Reports > Payments (Transaction view, All statements, or Date Range Reports) as CSV
[ ] Imported via Data > From Text/CSV, not double-click
[ ] Encoding set to UTF-8, delimiter to comma
[ ] SKU and ASIN columns typed as Text
[ ] Money columns typed as Decimal Number (right locale for EU marketplaces)
[ ] Date columns typed as Date with the correct locale
[ ] Extra header/footer rows removed before loading
[ ] Settlement report: profit pivot built on transaction type
[ ] Spot-check: SUM of a money column is non-zero, dates sort correctly, SKUs intact

csvtoexcel.site team
We build free, private, browser-based file tools. Every guide is written and tested by our editors.