Why Your Reseller Settlement Spreadsheet Drifts Every Month
2026-07-25
Settlement sheets can diverge when sale dates, final dates, file definitions, and edit history are mixed. Five operational risks and a manual review method.
Key takeaways
- Treating a sale-date estimate and a final settlement as the same value can create differences. Track whether fees, shipping, and returns have been reflected.
- The same 'sales amount' label can have different definitions. Check each channel's current official export guidance and file notes before merging columns.
- Product-name joins can fail when labels differ. A seller-controlled identifier with channel titles as aliases is one manual alternative.
- Overwriting cells removes earlier values. Preserving raw exports and appending correction events keeps evidence for reconciliation.
- Store cost assumptions such as fee rates and shipping as dated rows so you can inspect the inputs used for an earlier calculation.
At month end, settlement exports collected in one sheet may disagree with a figure recorded earlier. If the formula does not explain it, inspect whether sale-date estimates, final values, file definitions, and edit history have been mixed.
This article has no frequency data for these scenarios. It also does not assert any channel's file format or policy. It covers operational risks and a manual sheet structure for reconciling several exports.
- current official settlement and export guidance for the channels you use
- a status field showing whether a sale-date value is estimated or final
- separation between raw exports and transformed sheets
- a record of the value before each correction
Risk 1: estimates and final values share one field
A value recorded on the sale date may change in the later settlement. Depending on the transaction, fees, outbound or return shipping, cancellations, returns, or promotion contributions may be reflected at a different time.
Channels and transactions do not all follow one sequence. Keep estimated, final, and adjusted states separate, and use the channel's official settlement record as the source for final status.
Risk 2: identical labels are treated as identical amounts
One file's sales amount may be gross before fees while another's may be an expected payout. Tax, shipping, and cancellation treatment may differ too.
Build a mapping table when you first receive a file.
| Check | File A | File B | |---|---|---| | amount definition | gross / expected / final | gross / expected / final | | fees | separate / included | separate / included | | shipping | separate / included | separate / included | | cancellation or return | same file / separate file | same file / separate file | | date basis | sale date / settlement date | sale date / settlement date |
Do not guess. Check current official guidance and the notes in the actual export.
Risk 3: product titles become join keys
Color, size, condition, and included-item labels can vary between files for the same item. An exact-string lookup can miss those differences.
One manual alternative is a seller-controlled identifier with channel-specific titles stored as aliases. Which dimensions belong in the identifier depends on the operation. Start with the dimensions that must be settled separately; keep the rest as reference fields.
Risk 4: old values are overwritten
Typing a final payout over an estimate or replacing a stock count removes the earlier value. A later discrepancy is harder to trace without knowing what changed and when.
Preserve the original export. In the transformed sheet, append an adjustment row with the original row ID, adjustment date, and reason instead of deleting the old row.
Risk 5: cost assumptions exist only inside formulas
When fee rates, shipping, or return allowances exist only as formula constants, it is hard to inspect which assumptions produced an earlier result.
Move assumptions to a separate sheet with name, value, effective date, and source. Add a new row when a value changes. You can also review an example that records storage deadlines and cost assumptions together. This is a recordkeeping method, not a promise of profit accuracy.
A manual spreadsheet structure
Record one event per row
Give purchase, intake, sale, final settlement, return, and adjustment separate rows instead of repeatedly changing an item row.
Separate raw and normalized files
Do not edit the channel export. Match column names and definitions in another sheet.
Keep an internal identifier and the source ID
Join products on your internal identifier while preserving channel order and settlement IDs for comparison.
Attach an effective date and source to assumptions
For fees and shipping, record when you checked the official guidance and its link or document name.
Separate estimated, final, and adjusted states
Do not combine mid-period estimates and official final settlements into the same total.
This structure cannot guarantee that differences disappear. It preserves material for comparing the file, assumption, and adjustment where a difference appeared.
Settlement and profit records may feed tax work, but this article is not tax advice. Confirm filing basis, evidence requirements, and income classification with a qualified professional.
Resell Ops is still in development
We are building Resell Ops toward a single ledger for purchases, inventory, orders, settlements, and profit. There is no installable distribution yet, and those ledger functions remain in development. The manual sheet in this article works without waiting for the product.
Execution is being designed for the user's computer, with channel passwords, cookies, and sessions kept off our servers. We do not build purchase, raffle-entry, stock-grabbing, or security-control bypass features, and we do not advise bypassing channel policies.
We want to understand the columns and states you use today. Share the workflow and sticking points in the open chat below as design input; the build process is shared there too. Do not send account details, passwords, cookies, or order-level personal data.
Resell Ops is currently in development and is planned for August 2026. If you preregister through Kakao Open Chat, we will provide information about 30 days of free use after launch.
Frequently asked questions
What should I align first when merging settlement files? Align amount and date definitions before column names. Keep a mapping table based on current official guidance and the actual exports.
Can I keep using a spreadsheet? It may remain practical when volume and formats are simple and you can preserve raw records, definitions, and edit history. There is no fixed channel or file-count threshold.
Is sale-date margin final? Later costs or adjustments may apply depending on the transaction. Mark it as an estimate and reconcile it with the official settlement record.
If stock is the more urgent half of the problem, read What Happens When One Item Sits on Two Channels next.
This product is in development. There is no installable distribution yet, and inventory, order, and settlement functions are still being built. We are not affiliated with any channel. Channel terms of service may restrict automated access, and that judgment and its risk rest with the user.
This article was drafted with AI assistance and fact-checked and edited by platformholder.