DEV Community

郭委
郭委

Posted on

Proving E-Commerce Income: What Shopify and Amazon Sellers Get Wrong

Proving E-Commerce Income: What Shopify and Amazon Sellers Get Wrong

E-commerce sellers face a verifier problem freelancers don't: your revenue is loud, but your income is quiet. A Shopify store doing $40,000 a month proves nothing about what you actually take home after COGS, ad spend, refunds, and fees. Verifiers who know this will ask questions your dashboard can't answer. Here's how to build the file.

Revenue is not income — say it before they do

The first thing a sophisticated verifier thinks when they see e-commerce numbers: "This is turnover, not profit." If your application presents gross sales as income, you've spent your credibility on the first line.

Lead instead with net owner compensation: what the business actually paid you (in salary, distributions, or draws) plus what you retained as profit. Every number downstream — averages, run-rates, trend lines — should reference that net figure, following the one-number-everywhere discipline.

The four documents that work for sellers

1. Bank statements with payout matching

Amazon pays out on 14-day cycles; Shopify Payments pays daily or weekly. What matters to a verifier is that the deposits in your bank statement reconcile with the platform's payout reports. Match three payout cycles exactly — dates, amounts, reference numbers — and the verifier can extrapolate the rest themselves.

2. Platform payout reports

Download from Seller Central (Settlement Reports) or Shopify (Payouts). These show gross, fees, refunds, and net per period. They're third-party-adjacent documents — issued by the platform, not by you — which makes them stronger than a self-made spreadsheet.

3. A profit-and-loss summary

One page, monthly, covering at least 12 months: revenue → COGS → ad spend → fees → refunds → net profit / owner draws. A verifier doesn't audit it; they check it's plausible against the bank deposits. If your P&L shows $8,000 monthly profit but your bank shows $2,000 in payouts, expect questions about where the rest went.

4. Tax filings (the anchor document)

A filed Schedule C (US), self-assessment (UK), or equivalent is the single most trusted document in the file — it's the one place you swore your numbers to a government. If your most recent filing is stale, pair it with current statements and a note reconciling the two periods. Tax offices accept exactly this combination.

E-commerce-specific traps

The refund and chargeback tail

Last month's revenue looks great until this month's refunds hit. Verifiers who've seen seller income before know this. Disclose your refund rate and show it's stable — a 3% refund rate, disclosed, is a non-issue; a discovered 11% is a rejection.

Inventory spend that lives on a credit card

If you buy inventory on cards, the spending is invisible in bank statements — which makes your deposits look like pure profit. Explain the COGS funding path in one line, or the verifier's mental math will conclude you're hiding debt.

Seasonality you didn't choose

Q4 spikes are standard for retail; a verifier comparing February to December without context will misread both. Use the unequal-months presentation: year-over-year same-month comparison beats sequential months for sellers.

Money stuck in platform balance

Amazon holds reserves; Shopify payout schedules delay cash. Your dashboard balance is not bank balance. Present settled, deposited funds only as income — where the money actually lands is what counts, not what's pending.

What the final application looks like

  1. An income letter stating net monthly owner compensation and its basis — generate it from your reconciled numbers with ProofLetter
  2. Bank statements with 3 payout cycles matched to platform reports
  3. One-page P&L covering 12 months
  4. Most recent tax filing
  5. One line each disclosing refund rate, COGS funding, and seasonality

Sellers who present gross sales get skeptical questions. Sellers who present reconciled net income with the tail risks disclosed get approved — because they've answered the verifier's questions in the file itself.

Related reading

Top comments (0)