Pricing E-commerce Accounting Services as a CA
Pricing marketplace seller engagements is harder than pricing a traditional trading client, because the work does not scale with turnover, it scales with order count, channel count and mess. A seller doing five thousand small Meesho orders is more work than one doing the same turnover in two hundred B2B invoices, and a seller with high return rates is more work than either. This article covers the pricing structures that fit this reality and the cost drivers to price against. It deliberately quotes no market rates, your costs, your market and your positioning set those, but it will give you a defensible structure.
Price against the real cost drivers
Four variables predict effort far better than turnover does:
- Order volume: rows to import, match and reconcile each month.
- Channel count: each of Amazon, Flipkart and Meesho adds report formats, settlement cycles and a reconciliation stream.
- Exception rate: returns, disputes and mismatches consume senior time; a high-returns category client can generate several times the resolution work of a clean one.
- Data discipline: a client who sends complete files on schedule costs less to serve than one who must be chased, a difference worth pricing explicitly.
Automation reshapes this cost curve: when imports and order-level matching are automated, volume becomes cheap and exceptions become the cost centre. That shift is what makes per-order pricing viable at all, and it is measurable if your tooling reports match rates and exception counts per client, as TallySutra's CA workspace does.
Three structures that work
| Model | How it works | Fits | Watch out for |
|---|---|---|---|
| Banded fixed fee | Monthly fee by order-volume band, e.g. up to 500, 500 to 2,000, 2,000 plus | Most engagements; predictable for both sides | Set band edges from your measured effort, and revisit annually |
| Fixed plus per-channel | Base fee plus an add-on per marketplace | Multichannel sellers; scope stays visibly linked to work | Base must cover review and advisory, not just processing |
| Fixed plus exception rider | Standard fee, with a defined threshold for included exceptions and a rate beyond it | High-returns categories; aligns client incentives with clean data | Requires tooling that counts exceptions credibly |
Pure hourly billing is the weakest fit: automation collapses the hours while the value delivered rises, so hourly pricing punishes you for improving your own process. If you automate, some model that decouples fee from hours is close to mandatory, a point developed in our scaling article.
Scope lines that protect the fee
Most fee erosion on these engagements is scope creep, not underpricing. Lines worth drawing explicitly in the engagement letter: monthly books and settlement reconciliation are the core; GST return filing is a separately stated scope; historical clean-up beyond the agreed opening position is a one-time project fee; fee-dispute pursuit with marketplaces beyond reporting the findings is an add-on; and additional channels added mid-year adjust the fee from the month they start. Also state the client's data obligations, files on schedule, in the agreed formats, and reserve the right to bill chase time. None of this is aggressive; it converts invisible work into visible choices for the client.
Selling the price: show the deliverable
The strongest pricing conversation for this service is a demonstration, not a discount. An order-level settlement reconciliation, showing exactly what the marketplaces deducted and which orders remain unpaid, is something most sellers have never seen; our payout-gap explainer is the customer-facing version of that story. Position the monthly fee against what it protects: clean, evidence-backed books, early detection of short payments, and a reconciliation an auditor or a GST officer can be shown without a scramble. Sellers compare your fee to software prices and freelance bookkeepers; the answer is not to match those prices but to make the deliverable visibly different, review, judgement and accountability on top of the pipeline. A pilot month at a defined fee, with the reconciliation as the showpiece, converts better than a brochure ever will. One more discipline protects the whole structure: re-price on data once a year. Pull each client's order volumes, channel count and exception load from your tooling, compare them against the band or rider the client sits in, and move the ones that have drifted. An annual re-pricing framed as a data review is a far easier conversation than an ad hoc increase, because the evidence does the negotiating for you.
Frequently asked questions
Should marketplace bookkeeping be priced as a percentage of turnover?
It is a poor proxy: effort tracks order count, channels and exception load, not turnover. Two clients with identical turnover can differ several-fold in work. Banded or per-channel structures track cost drivers far better.
How do I price a client whose data arrives late and incomplete?
Name the behaviour in the engagement letter: define the delivery schedule, include a defined amount of chasing, and price beyond it. Some firms offer a small discount for on-schedule data instead, framing the same economics positively.
Does automation mean I should charge less?
Automation lowers your cost, not the value of clean, reconciled, evidence-backed books. Keep pricing tied to the deliverable and the accountability you provide, and let automation improve your margin and turnaround instead of your price.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo