Free · No account required · CSV template tool

Fee Check

Compare your documented expected fees with actual charged fees by transaction and fee type.

Switching tools or leaving this page clears the working session. Download results first.

Use payout references for bank matching, transaction plus fee type for Fee Check, and return reference plus SKU for Return Match. Report requirements

1. Prepare the two templates

Copy values from your source exports into these exact columns. Retain original reports separately. This tool does not recognize native marketplace headers, calculate contractual fees, convert currencies, or infer missing references.

Column definitions and matching rules
row_id
A unique ID for each source record within each file. Duplicate IDs block the run.
account
Stable seller account/provider ID. Must match exactly between the two files.
reference
Payout or transaction reference shared by both files. Exact, case-sensitive match.
component
The fee type, e.g. referral_fee. Each fee component matches separately.
currency
USD, GBP, EUR or CAD. Currencies never combine or convert.
value
Nonnegative decimal, at most 2 places. No commas or symbols. Negative reversals are unsupported; prepare a documented net amount separately.
state
Expected: ready or pending. Actual: ready only. Include only posted/confirmed actual records. Pending expectations remain pending even if values match.
Grouping
One expected row per account/reference/component/currency. Several distinct actual rows may match it, for partial receipts. Duplicate-looking events with different row IDs require your review.

Both files must cover the same scope and cutoff. Missing matches can mean timing, incomplete evidence or mismatched keys. They are not automatically discrepancies owed to you. Maximum 10,000 records and 2 MB per file. No tolerance is applied: a one-cent difference is shown.

2. Add your prepared CSVs

These files are processed in this browser and are not uploaded or saved to your account. Download your result before leaving. The existing inventory workspace has a separate upload-and-save workflow.