Where to get reliable Etsy payment reconciliation data
Last updated: 2026-07-28
Written and reviewed by Seller Profit Guard Editorial Team.
Use order exports to identify what sold, Payment Account or monthly statements to classify money movements, deposit exports and bank records to confirm cash transfers, and private records to calculate product contribution separately. Record each file’s period, grain, currency, columns, and download date; no single export proves every layer.
What does each Etsy export prove?
Order and order-item exports support sale identity, SKU, quantity, product and shipping amounts, and order timing at their documented grain. Etsy Payments sales or Payment Account activity supports financial movements and categories. Deposit exports support payout timing and amounts. The authenticated Payment Account provides current balance and context that may not fit one static file.
Source names and columns can change. Save the original heading map and confirm the official download instructions at the time of use. A report downloaded for one period can include related activity outside a simple sales-date filter, so record actual row coverage rather than assuming the requested dates define every included event.
| Source | Best use | Does not prove |
|---|---|---|
| Order items | SKU and line-item identity | Complete account movement |
| Orders | Order-level totals and references | Deposit composition |
| Payment Account/statement | Sales, fees, refunds, services, adjustments | Private product cost |
| Deposits | Transfer amount and timing | Order profit |
| Bank | Cash received | Marketplace row classification |
| Private cost records | Contribution economics | Statement balance |
How should source files be cataloged?
Create a source register with filename or controlled identifier, shop, account, export type, requested period, observed row period, timezone, currency, row count, column count, download time, checksum, storage location, and operator. Record whether the file is untouched, redacted, normalized, or derived.
A checksum proves the working source has not changed; it does not prove completeness or truth. Pair it with source-coverage checks: required columns, expected currencies, row categories, date boundaries, duplicates, blank references, and control totals.
When is authenticated account evidence required?
Use authenticated Etsy evidence when a reserve, failed deposit, currency conversion, regulatory charge, suspension, or account-specific adjustment determines the explanation. Public help pages define general categories but cannot reveal a seller's exact balance movement or eligibility.
Capture only the minimum private evidence required for the seller's own record. Do not copy screenshots or account details into public content. Record the observation date, visible label, amount, related reference, and action taken in a controlled log.
- Official help explains general export and account concepts.
- Exports supply reproducible row evidence.
- Authenticated screens explain current account-specific state.
- Bank evidence confirms cash receipt.
- Seller records supply private costs, not platform movements.
Reconciliation data-source questions
Can one CSV replace the Payment Account? No single source should be assumed complete for every identity, movement, balance, and deposit question.
Should bank records be uploaded? The browser workflow does not require public upload; keep sensitive identifiers controlled.
What if columns change? Stop, update the field map, test the new schema, and retain the prior mapping version.
Can screenshots replace exports? Use them as supporting account evidence, not as a scalable row-level substitute when an official export exists.
How long should sources be retained? Follow applicable business, privacy, legal, and accounting requirements; the tool does not set a universal retention period.
How should source completeness be challenged?
Compare observed columns, categories, currencies, date limits, control totals, and row counts with the export request and prior source register. Look for truncated downloads, repeated headers, blank trailing sections, locale-specific decimal separators, timezone shifts, and filters retained from an account screen. A syntactically valid CSV can still be incomplete for the reconciliation question.
Use cross-source reasonableness without pretending one source must equal another at the same grain. Order counts can be compared with distinct matched sale references; statement category totals can be recalculated from rows; deposits can be compared with bank transfers; opening and closing balances can be bridged. Differences become investigation prompts, not automatic corrections.
When a source is replaced, record why, retain the original fingerprint, and rerun coverage checks before matching. Do not splice rows from multiple downloads without a deterministic de-duplication key and documented precedence. A derived combined file must list every contributing source.
Which records make this reconciliation source map defensible?
Use three evidence layers without merging their jobs. Order exports explain what sold and at what line-item grain. Payment Account or monthly-statement activity explains sales, fees, refunds, shipping labels, advertising, reserves, adjustments, and deposit movements. The bank confirms cash received. Private SKU, labor, packaging, fulfillment, and replacement costs belong in a separate contribution review; they do not repair a statement mismatch.
Record shop, currency, export type, requested period, actual earliest and latest row dates, download time, column map, and any filter applied before matching. Preserve signs and row categories. A net amount can help verify arithmetic, but it should not erase the components that explain the balance. If Etsy changes an export or account label, retain the raw heading and document the normalized category beside it.
A row is evidence only within its scope. An order ID can support a direct match, but a deposit is normally a transfer of available balance rather than an order-level sale. A refund can occur outside the original sale period. A shipping-label adjustment can arrive later. Keep these timing differences visible instead of forcing every row into the same day or payout.
- Preserve source files and work from a local copy.
- Normalize currency, signs, dates, and row types before matching.
- Prefer stable transaction or order references over amount-only matches.
- Retain unmatched and timing-difference rows with an owner and next review date.
- Keep profit, tax, accounting, and policy conclusions outside the tool's operating scope.
Privacy boundary for reconciliation source map
Payment reconciliation does not require publishing buyer names, delivery addresses, private messages, payment credentials, marketplace passwords, bank account numbers, or raw order histories. Use a redacted transaction key, date, category, currency, gross amount, fee, net amount, deposit reference, and match status. Keep the untouched export and bank evidence in controlled seller storage.
Seller Profit Guard is designed to process supported files locally in the browser. A reconciliation export can still reveal shop volume, fee exposure, refund patterns, reserves, and cash timing, so treat it as a confidential business record. For support, share column names and a made-up example that reproduces the mapping issue. Never paste real buyer or order rows into a public community, email draft, or AI prompt.
- Use public dummy data for demonstrations and tests.
- Remove buyer, address, message, credential, and bank-identifier fields.
- Do not copy private CSV files into the active public-content directory.
- Store source fingerprints and aggregate counts instead of raw rows in operator reports.
- Escalate tax, legal, accounting, reserve, suspension, or account-policy questions to the appropriate official or professional source.
How to apply this reconciliation source map in the reconciliation tool
Open Payment Reconciliation and load a supported order export plus the relevant Payment Account or monthly-statement export. Confirm the date, amount, currency, category, order reference, fee, refund, and deposit mappings before reading the summary. Start with source-quality warnings. A high match rate built on the wrong amount column or duplicated order-level totals is not a reliable result.
Review direct matches, unresolved sales, unresolved statement rows, refunds, deposits, fee categories, and formula checks separately. Export the private exception list and record the source period, matching rule, unresolved amount, owner, evidence requested, decision, and next review date. Re-run after late rows arrive or an adjustment is explained. The useful output is a controlled exception queue, not a promise that the account is profitable or the bank balance is correct.
- Preserve and fingerprint the source exports.
- Confirm date, currency, sign, category, and reference mappings.
- Run direct-reference matching before bounded fallback rules.
- Separate timing differences from unexplained exceptions.
- Bridge statement activity to deposits without treating deposits as sales.
- Assign every material unresolved row and retain the closing evidence.
Related resources
- Open Etsy Payment Reconciliation: Compare order exports with Payment Account or monthly-statement activity in the browser.
- Read the Etsy Payment Account reconciliation guide: Review the source hierarchy, balance bridge, row categories, and investigation sequence.
- Estimate SKU-level Etsy contribution: Keep product economics separate from the cash-movement reconciliation.
- Review local-first CSV privacy: Understand which fields are needed and which buyer or address fields should remain private.
- Read the editorial policy: See how sources, corrections, review dates, and AI assistance are handled.
Sources and further reading
- Etsy Help: Download Sold Transaction Spreadsheets: Official export workflow for order items, orders, Etsy Payments sales, and Etsy Payments deposits.
- Etsy Help: Manage Your Payment Account: Official reference for sales, fees, refunds, shipping, seller services, monthly statements, balances, and deposits.
- Etsy Help: Fees and Taxes for Selling: Official overview of fee categories and account treatment; exact charges vary by country, currency, service, and shop activity.
- Etsy Help: Issue a Full or Partial Refund: Official refund workflow and Payment Account impact reference.
- Seller Profit Guard reconciliation methodology: Evidence hierarchy, local-first data handling, contribution scope, editable assumptions, and result limitations.
Related Seller Profit Guard tools
- Open Etsy Payment Reconciliation: Compare order exports with Payment Account or monthly-statement activity in the browser.
- Read the Etsy Payment Account reconciliation guide: Review the source hierarchy, balance bridge, row categories, and investigation sequence.
- Estimate SKU-level Etsy contribution: Keep product economics separate from the cash-movement reconciliation.
- Review local-first CSV privacy: Understand which fields are needed and which buyer or address fields should remain private.
- Read the editorial policy: See how sources, corrections, review dates, and AI assistance are handled.
- Etsy Payment Reconciliation: Inputs and Match Rules: Continue the Etsy payment evidence, exception, and control workflow.
- Etsy Deposit Reconciliation: A Weekly Worked Example: Continue the Etsy payment evidence, exception, and control workflow.
- Etsy Month-End Reconciliation: Close Without Guessing: Continue the Etsy payment evidence, exception, and control workflow.
- Etsy Payment Reconciliation: 12 Errors to Fix: Continue the Etsy payment evidence, exception, and control workflow.
- Etsy Reconciliation Thresholds: When to Investigate: Continue the Etsy payment evidence, exception, and control workflow.
Next step: Open Etsy Payment Reconciliation.
This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.