Sync Amazon Payouts to Google Sheets: A Guide

Last verified: June 2026

If you're running an Amazon business and still copying settlement figures into a spreadsheet by hand, you're wasting time on a task that should have been automated years ago. Amazon's settlement reports contain everything — gross sales, FBA fees, advertising charges, refunds, shipping credits — but they land in Seller Central as flat files, not in the financial dashboard you actually need.

Google Sheets is the obvious destination for most growing brands: flexible, shareable, and powerful enough to build a real reconciliation workflow without enterprise BI software. The problem is getting the data there reliably, and keeping it fresh. Do it manually and you'll spend hours every fortnight. Do it badly and you'll make decisions on stale numbers. And if you're running multiple channels alongside Amazon — something covered in our guide to multi-channel inventory forecasting — the reconciliation burden compounds fast.

This guide covers every method, from a five-minute manual export to a full SP-API pipeline. Pick the one that matches your technical comfort level and how fresh you need the data.

Before you start

• Active Amazon Seller Central account with at least one completed settlement period
• Google account (for Google Sheets and, if using the API method, Google Cloud Platform)
• Subscription to a third-party connector tool — required for the connector method
• Amazon Selling Partner API developer registration — required for the direct API method (apply via developer.amazon.com)
• Google Cloud Platform project with the Google Sheets API enabled — required for the direct API method

Methods at a glance

Method 1: Manual export and import

This is the baseline. No setup, no subscriptions — just you and a CSV. It works, but it doesn't scale. Expect to spend 30–60 minutes per settlement period once you factor in downloading, cleaning, and formatting. If you're reconciling two Amazon marketplaces plus a Shopify store, that's a meaningful chunk of your month, every month.

1. Open Seller Central and navigate to Payments → All Statements.
2. Find the settlement period you want to export — Amazon settles approximately every 14 days.
3. Click the Download button in the Actions column for that settlement. Choose either the flat file (tab-delimited) or the CSV format — CSV is easier to work with in Sheets.
4. Open Google Sheets and create a new spreadsheet (or open your existing reconciliation file).
5. Click File → Import, then Upload, and select the downloaded CSV file.
6. Choose "Insert new sheet(s)" in the import dialog so you don't overwrite existing data — this keeps previous settlement periods intact.
7. Rename the new tab with the settlement date (e.g. "Settlement 2026-06-15") so you can track periods chronologically.
8. Build summary formulas on a separate dashboard tab using SUMIF against the amount-description column — the settlement report field definitions explain every line type including FBA fees, per-unit selling fees, refunds, and shipping credits.

The limitation is obvious: you repeat this process every single settlement period. Miss one export and you've got a gap in your data.

Method 2: Using a Google Sheets add-on for semi-automation

Several Google Workspace Marketplace add-ons pull Amazon Seller Central data — including settlement and payout data — directly into Sheets on a schedule. Setup takes under an hour and doesn't require any coding. The trade-offs: fully automated, high-volume syncs usually require a paid tier, and refresh cycles are typically daily rather than real-time.

1. Open Google Sheets and click Extensions → Add-ons → Get add-ons.
2. Search for an Amazon data connector in the Google Workspace Marketplace — look for tools that mention SP-API connectivity and settlement report support specifically.
3. Install your chosen add-on and grant the requested OAuth permissions to both your Google account and, in the next step, your Amazon account.
4. Launch the add-on from the Extensions menu and follow the authentication flow to connect your Amazon Seller Central account — you'll typically be redirected to an Amazon login screen to grant data access.
5. Select "Settlement Reports" or "Finance" as the data source in the add-on's report builder.
6. Configure your date range — most add-ons let you pull rolling windows (e.g. last 90 days) or fixed periods.
7. Click Run (or equivalent) to do an initial data pull into a designated sheet tab. Verify that columns like amount-type, amount-description, and amount are present — these are the core fields for reconciliation.
8. Set up a scheduled refresh — usually under the add-on's settings — to run daily or every few hours automatically.
9. Protect the data tab (right-click the tab → Protect sheet) so accidental edits don't overwrite incoming data.

One warning before you commit: some add-ons overwrite the entire data range on each refresh, which wipes any manual notes or custom formatting. Check the documentation for an "append" mode first.

Method 3: Third-party connector tool

Connector tools — middleware platforms that sit between Amazon and Google Sheets — handle authentication, scheduling, error handling, and data transformation for you. This is the most practical option for brands running multiple channels, since the same tool can pipe data from Amazon, Shopify, and other sources into a single Sheet. If you're managing the kind of omnichannel operations stack where financial data is scattered across platforms, a connector genuinely earns its subscription fee.

1. Sign up for a connector tool that supports both Amazon Seller Central (via SP-API) and Google Sheets as a destination — look in the "data pipeline" or "ETL for e-commerce" category on the Google Workspace Marketplace or similar directories.
2. Create a new connection or "flow" within the tool's interface.
3. Select Amazon Seller Central as the source and authenticate via the OAuth flow — you'll be redirected to Amazon to authorise the connection.
4. Choose your data object — select "Settlement Reports" or "Finance Events" depending on the tool's terminology.
5. Select Google Sheets as the destination and authenticate your Google account.
6. Specify the target spreadsheet and sheet tab where the data should land.
7. Map the fields you need — at minimum: settlement ID, settlement period, amount-type, amount-description, and amount.
8. Set the sync schedule — daily is standard; some tools support more frequent syncs on paid tiers.
9. Run a test sync and verify the row counts against your Seller Central settlement report for the same period.
10. Enable error notifications (usually an email alert setting) so you know immediately if an authentication token expires or a sync fails.

This approach is particularly useful if you're reconciling payments from other platforms too — see our guide on how to connect Stripe to QuickBooks Online for a comparable workflow on a different payment source.

Method 4: Full automation with the Selling Partner API

As of 2026, the SP-API is the official route for programmatic access to Amazon financial data — it replaced the legacy MWS entirely. This method gives you complete control over data transformation and scheduling, but it requires developer time upfront and ongoing maintenance as the API evolves.

1. Register as an SP-API developer at developer.amazon.com — you'll need to submit a use-case description; "private seller application" is the relevant category for in-house tools.
2. Create an IAM user and role in AWS following Amazon's SP-API access setup guide — SP-API uses AWS STS for authentication, so an AWS account is required.
3. Authorise your application in Seller Central under Apps and Services → Develop Apps, generating your LWA (Login with Amazon) credentials.
4. Open Google Cloud Console and create a new project (or use an existing one).
5. Enable the Google Sheets API within that project under APIs & Services → Library — official documentation at developers.google.com/sheets/api.
6. Create a service account in Google Cloud and download the JSON key — this is what your script uses to authenticate with Sheets.
7. Share your target Google Sheet with the service account's email address (give it Editor access).
8. Write a script (Python is the most common choice, with the boto3 and google-api-python-client libraries) that: (a) exchanges your LWA credentials for a temporary SP-API access token, (b) calls the listFinancialEvents or listSettlementReports endpoint, (c) parses the response, and (d) writes rows to your Sheet via the Sheets API's spreadsheets.values.append method.
9. Test the script locally against a small date range — verify the output matches your manually downloaded settlement CSV row for row.
10. Schedule the script using a cron job, Google Cloud Scheduler, or AWS Lambda to run on your desired cadence.
11. Log all runs to a separate "Sync Log" tab in your Sheet — record timestamp, rows written, and any errors so you can audit gaps later.

This is serious infrastructure, not a weekend project. But if you're already managing a complex international e-commerce operations stack and financial accuracy is non-negotiable, it's the right long-term foundation.

Building a basic Amazon payout reconciliation dashboard in Google Sheets

Whichever method you use to get data in, the reconciliation logic is the same. Your settlement data lands in a raw tab — call it Settlement_Raw. Your dashboard tab uses SUMIF and QUERY formulas to break it down into meaningful categories.

Here's a minimal dashboard structure that works with Amazon's standard settlement report fields:

• Gross product sales: =SUMIF(Settlement_Raw!B:B,"ItemPrice",Settlement_Raw!D:D)
• Amazon selling fees: =SUMIF(Settlement_Raw!B:B,"Commission",Settlement_Raw!D:D)
• FBA fulfilment fees: =SUMIF(Settlement_Raw!B:B,"FBAPerUnitFulfillmentFee",Settlement_Raw!D:D)
• Refunds issued: =SUMIF(Settlement_Raw!C:C,"Refund",Settlement_Raw!D:D)
• Net payout: Sum of the above — this should match your bank deposit within a few pence (rounding on Amazon's side).

If you want something more visual, the same dataset feeds well into Looker Studio — we've covered that workflow in detail in our Amazon to Looker Studio integration guide. And if you're reconciling across a broader finance stack, the principles here apply directly to similar workflows covered in our NetSuite Shopify integration guide.

Common errors and how to fix them

Settlement totals don't match bank deposits

Amazon payouts are bi-weekly lump sums that roll up gross sales, FBA fees, advertising charges, refunds, and various adjustments into a single transfer. You can't reconcile at the order level — you reconcile at the settlement level. The logic is: total gross sales minus all deductions (fees, refunds, taxes withheld) equals the net deposit. If there's still a discrepancy, check for reserve amounts — Amazon sometimes withholds a portion to cover potential A-to-Z claims.

IMPORTXML or IMPORTHTML formulas return blank or error

Amazon actively blocks web scraping requests, so any formula that tries to fetch data directly from Seller Central pages will fail silently or throw a #N/A. Don't spend time debugging these formulas — they won't work, full stop. Use the official methods in this guide instead.

Automated refresh overwrites custom formatting and notes

Many connector tools and add-ons replace the entire data range on each sync, not just new rows. Move your custom formulas, notes, and conditional formatting to a separate dashboard tab that references the raw data tab via formulas. Never edit the raw import tab directly. That way, refreshes overwrite the data tab cleanly without touching your work.

SP-API access token expires mid-run

SP-API access tokens are short-lived. If your script runs longer than the token validity window — possible with large historical data pulls — requests will start returning 401 errors. Build a token refresh function into your script that requests a new token before each batch of API calls, not just at startup. The SP-API documentation covers the LWA token exchange flow in detail.

CSV import date formats break formulas

Amazon's settlement CSV uses ISO 8601 date-time strings (2026-06-15T00:00:00+00:00), which Google Sheets may not automatically parse as dates. Wrap date columns with =DATEVALUE(LEFT(A2,10)) to extract the date portion, then format the column as Date. Do this once in your dashboard tab, not in the raw data tab.

Frequently Asked Questions

How do I export my Amazon settlement report to a spreadsheet?

Go to Payments → All Statements in Seller Central, find the settlement period you want, and click the Download button in the Actions column. Amazon provides the file in CSV or flat-file (tab-delimited) format — CSV imports cleanest into Google Sheets via File → Import. The full process is documented in Amazon's settlement download help page.

Can I automatically connect Amazon Seller Central to Google Sheets for free?

Truly free automation requires coding — specifically, a script using Google Apps Script or Python that calls the SP-API and writes to Sheets via the Google Sheets API, both of which are free to use. Third-party add-ons and connector tools may offer limited free tiers, but high-volume or scheduled syncs typically require a paid subscription. Amazon doesn't provide a native, no-code, free option.

How do I reconcile Amazon payouts?

Amazon reconciliation works at the settlement level, not the order level. Take your gross product sales from the settlement report, subtract all fees (selling fees, FBA fees, advertising), subtract refunds, and the result should match your bank deposit for that period. The settlement report field definitions document every line type so you can categorise deductions accurately.

What is the best way to track Amazon fees in Google Sheets?

Import your settlement CSV into a raw tab, then use SUMIF formulas on the amount-description column to aggregate each fee type — Commission, FBAPerUnitFulfillmentFee, VariableClosingFee, and so on. Build these SUMIFs in a separate dashboard tab so automated refreshes don't overwrite your formulas. Once you're processing more than a handful of settlements per month, a connector tool that appends new settlement data automatically is worth the subscription cost.

Choosing your method

If you're a one-person operation selling on a single Amazon marketplace and you reconcile once a fortnight, the manual CSV export is perfectly adequate — don't over-engineer it. If you're running multiple channels, need daily visibility, or your accountant keeps asking why the numbers don't tie out, a connector tool or add-on will pay for itself in hours saved within the first month.

The SP-API route is for teams with developer resources who need a pipeline they fully own — particularly relevant if you're building out a broader international CPG operations stack where off-the-shelf connectors don't cover every data source you need.

Whatever method you pick, get the reconciliation tab built properly once, protect it, and stop doing this by hand.