Etsy payment reconciliation for a month-end close
Last updated: 2026-07-28
Written and reviewed by Seller Profit Guard Editorial Team.
A month-end Etsy reconciliation bridges opening balance to closing balance across all in-period account movements, then explains deposits and unresolved timing separately. Freeze the source period, retain reserves and adjustments, and carry documented exceptions forward. Do not force the month to zero or treat deposits as sales or profit.
How is month-end different from a payout check?
A payout check asks whether a transfer is supported by eligible account activity around one deposit. Month-end asks whether the complete period's opening balance, sales, fees, refunds, labels, ads, reserves, credits, adjustments, and deposits explain the closing balance. It requires a controlled cut-off and an exception roll-forward, not just a collection of deposit receipts.
Download the month-end source after allowing for known posting delays, then record the actual first and last row dates. Preserve the opening balance carried from the prior close and identify rows dated in the month but posted or made available later. A locked close does not mean every timing difference disappears; it means each difference has an evidence-based classification and owner.
| Close layer | Control | Evidence |
|---|---|---|
| Opening balance | Agree to prior closing record | Prior signed close |
| In-period movements | Classify every statement row | Monthly statement |
| Deposits | Bridge transfers separately | Deposit export and bank |
| Timing differences | Age and assign | Later account evidence |
| Closing balance | Recalculate from movements | Payment Account |
| Exceptions | Roll forward with owner | Issue log |
How should reserves and adjustments be handled?
Keep reserve and adjustment rows in their platform-provided categories and explain their balance effect from authenticated evidence. A reserve can affect availability without changing the original sale identity. An adjustment can correct a prior movement or introduce a new account event. Netting either into sales destroys the audit trail.
Do not publish a general reserve timetable or infer account status from one seller's row. Record amount, direction, date, description, related reference, current balance impact, evidence source, and whether further review is required. Account-specific policy or eligibility questions belong with Etsy's current authenticated guidance.
What belongs in the exception roll-forward?
Carry forward every material unresolved sale, fee, refund, label, deposit, reserve, or adjustment with first-seen date, amount, currency, source row fingerprint, suspected explanation, evidence requested, owner, and next review date. Preserve prior notes rather than replacing them. The log should show whether an exception aged, changed, split, combined, or closed.
Set seller-defined materiality for review effort, but do not use it to delete small differences from the mathematical bridge. Aggregate low-value items transparently when appropriate, and retain the count and amount. Escalate old or high-impact exceptions faster than routine posting delays.
- Freeze the source set and record its coverage.
- Agree opening balance to the prior close.
- Classify every movement without silent netting.
- Age and assign exceptions.
- Reopen the close only through a dated change log.
Month-end close questions
Must closing balance be zero? No. It must agree with the account evidence after movements and transfers.
Can a deposit after month-end belong to the month? Its underlying availability can relate to earlier activity, but the cash transfer retains its actual date.
Should refunds remove original sales? No. Preserve both events and reconcile their separate dates and categories.
When is a close final? When required controls pass and every material exception is resolved or formally carried forward.
Does a signed close certify accounting statements? No. This is an operational reconciliation, not tax, accounting, legal, or audit assurance.
How should a month-end close be reopened?
Reopen only through a dated change record. Identify the closed period, prior report fingerprint, triggering evidence, affected rows, original classification, new classification, bridge difference, approver, and rollback. Recalculate the smallest affected scope, then determine whether the closing balance, deposit explanation, exception aging, or next-period opening balance also changes.
A late fee credit may close one prior exception and change the next period's opening explanation without rewriting the original sale. A corrected mapping can affect many rows and therefore requires regression fixtures before the period is reissued. Preserve both reports so reviewers can distinguish a later event from an earlier error.
Use a subsequent-event note when the original close was correct with the evidence then available and later activity merely resolves timing. Use a correction when the prior source, mapping, rule, or calculation was wrong. This distinction prevents normal posting delays from being presented as defects and prevents real defects from disappearing into timing language.
Which records make this month-end close 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 month-end close
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 month-end close 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 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.
- 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.