Seller Profit Guard

Etsy payment reconciliation audit checklist and change log

Last updated: 2026-07-28

Written and reviewed by Seller Profit Guard Editorial Team.

A defensible Etsy reconciliation audit records source identity, schema, mapping version, matching rules, balance bridge, deposits, exceptions, privacy controls, approvals, and rollback. Every checked item links to evidence. Completion requires material exceptions to be resolved or formally carried forward; a clean checkbox list without reproducible totals is not proof.

What belongs in the source and schema checklist?

Record each source's controlled identifier, shop, type, requested and observed periods, timezone, currency, row count, column count, checksum, download date, storage location, and operator. Confirm the working copy can be traced to the preserved source and that prohibited buyer or address fields are not copied into reports.

Record mapping version and required fields. Test date parsing, currency partitioning, signs, row categories, order and transaction references, gross, fee, net, refund, and deposit fields. A schema change blocks interpretation until fixtures pass.

What belongs in the matching and balance checklist?

Verify exact-reference matching precedes fallbacks, grouped matches retain member rows, ambiguous candidates are rejected, tolerances have a documented basis, and manual overrides include owner and reason. Recalculate direct, grouped, fallback, timing, ambiguous, and unresolved counts and amounts from row classifications.

Agree opening balance to prior evidence, classify every movement, bridge deposits separately, and recalculate closing balance. Ensure refunds preserve original sales, credits remain visible, and deposits are not counted as revenue.

How should changes and exceptions be logged?

For every mapping, rule, threshold, allocation, or manual-resolution change, record timestamp, owner, old value, new value, reason, evidence, affected period, test fixtures, expected result, approval, rollback, and follow-up date. Preserve the prior report and identify rows recalculated under the new version.

For exceptions, record first seen, last reviewed, amount, currency, category, source fingerprint, suspected cause, evidence requested, owner, age, status, resolution, and closing evidence. Do not close an item merely because it falls below the current review threshold.

• Every checkbox links to evidence.
• Every rule has a version and fixtures.
• Every exception has an owner and age.
• Every change has a rollback.
• Every close preserves prior state.

Audit-template questions

Can the checklist certify financial statements? No. It is an operational control, not tax, accounting, legal, or audit assurance.

Must every weekly run use the full release checklist? Apply controls proportional to the change; formula, privacy, mapping, and public releases require the full gate.

How long should logs be retained? Follow applicable business, legal, privacy, and accounting requirements.

Who approves a manual override? Assign ownership appropriate to the business and preserve independent review where needed.

What is completion? Required controls pass, material exceptions are closed or formally carried, rollback exists, and reproduced totals match the approved report.

What evidence should accompany final approval?

The approval package includes the source register, checksums, observed coverage, schema and mapping version, normalization controls, matching-rule version, fixture results, class counts and amounts, opening-to-closing bridge, deposit support, exception roll-forward, manual overrides, privacy check, operator, reviewer, timestamp, and rollback. A signature without these artifacts does not make the result reproducible.

Reviewers should recalculate at least one control total and inspect a bounded sample from direct, grouped, fallback, timing, and unresolved classes. They confirm that ambiguous candidates were not accepted, deposits were separated from sales, original sales survived refunds, currencies stayed partitioned, and every material exception has evidence or formal carry-forward.

Approval states the exact scope: operational payment reconciliation for named sources and period. It does not certify product profitability, tax treatment, financial statements, platform compliance, or future deposits. Any later change follows the logged reopen procedure and preserves the approved prior state.

The reviewer also challenges negative evidence: missing categories, absent currencies, empty exception classes, sudden row-count drops, and controls that always pass. A zero count needs a coverage explanation, not celebration. Compare the package with the prior approved period and explain material changes in source schema, transaction mix, deposits, refunds, reserves, or matching classes. Record unresolved review questions separately from operator exceptions so approval pressure cannot silently close them.

Which records make this reconciliation audit template 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 audit template

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 audit template 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.

1. Preserve and fingerprint the source exports.
2. Confirm date, currency, sign, category, and reference mappings.
3. Run direct-reference matching before bounded fallback rules.
4. Separate timing differences from unexplained exceptions.
5. Bridge statement activity to deposits without treating deposits as sales.
6. 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 Data: Which Export Proves What?: 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.