Flipkart Commission & Fees Accounting in Tally
Flipkart's fees routinely eat 25-40% of a seller's gross sale value depending on category, price band and return rates, yet many sellers book them as a single "marketplace charges" lump, or worse, never book them at all and just record net receipts as sales. Both approaches destroy margin visibility and understate turnover for GST. Here is how to structure fee accounting in TallyPrime properly.
Know the fee columns before you build ledgers
The Flipkart settlement report itemises deductions per order item. The recurring ones are: Commission (category-based percentage of sale value), Collection Fee (charge for payment collection), Fixed Fee (flat per-item charge by price band), Shipping Fee (forward logistics), Reverse Shipping Fee (logistics on customer returns) and GST on Fees (tax Flipkart charges on all of the above). The report also shows TCS and TDS, but those are recoverable taxes, not fees, and belong in asset ledgers; see our TCS and TDS treatment guide for that side.
A ledger structure that earns its keep
| Ledger | Group in Tally | Why separate |
|---|---|---|
| Flipkart Commission | Indirect Expenses | Tracks category rate changes and negotiation impact |
| Flipkart Collection Fee | Indirect Expenses | Scales with order value; useful for pricing decisions |
| Flipkart Fixed Fee | Indirect Expenses | Hits low-ticket items hardest; informs minimum viable price |
| Flipkart Shipping Fee | Indirect Expenses | Compare against your own logistics alternatives |
| Flipkart Reverse Shipping Fee | Indirect Expenses | Your returns cost signal; watch it per SKU |
| Input GST on Marketplace Fees | Duties & Taxes | Claimable ITC, not a cost (confirm with your CA) |
The payoff of granularity is diagnostic power. When reverse shipping fees climb, you have a returns problem on specific SKUs. When the effective commission percentage moves, Flipkart changed the rate card or your listings shifted category. A single lump-sum ledger tells you none of this.
The journal entry pattern
Book sales at gross Sale Amount from the sales/GST report, against the Flipkart party ledger. Then, per settlement (or per NEFT group), post the fee journal: debit each fee ledger for that group's totals, debit Input GST on Marketplace Fees for the GST-on-fees total, and credit the Flipkart party ledger. Combined with the bank receipt for Settlement Value and the TCS/TDS entries, the party ledger nets to only the unsettled balance. Booking gross sales matters for GST: your GSTR-1 turnover must reflect invoice values, not net receipts, and the fee GST is separately claimable as input credit in most registered-seller situations, though eligibility should be confirmed with your CA.
Why per-item fee posting beats monthly lump sums
Monthly fee totals keep the books balanced but hide unit economics. Because the settlement report is order-item-level, each row's fees can be attributed to the item sold. That enables true contribution margin per SKU: sale value minus product cost minus that row's actual fees. Sellers who do this consistently discover that some fast-moving SKUs are unprofitable after reverse shipping and fixed fees, a fact invisible in aggregate accounting. The practical obstacle is volume; nobody posts three thousand fee journals by hand. TallySutra's Flipkart import generates the fee entries automatically from the settlement report you upload, itemised per fee type and balanced against the party ledger, with an exception queue catching rows where fees look wrong before they hit your books. It works purely on files exported from Seller Hub; nothing connects to your Flipkart account. You can compare this approach with other tools on our ecom2tally comparison page.
Fee accounting mistakes to stop making
- Netting fees against sales: understates both turnover and expenses; a GST notice risk and an analysis dead-end.
- Expensing GST on fees: leaves claimable input credit on the table every single month.
- Ignoring reverse shipping: it is the fee most correlated with real business problems (product quality, sizing, listings).
- One combined ledger: balances, but answers no question you will ever ask.
Set the ledger structure once, automate the posting, and your P&L starts telling you which products actually make money on Flipkart, which is the question fee accounting exists to answer.
It also pays to review the fee ledgers against Flipkart's announced rate-card revisions. Flipkart publishes commission and fee changes to sellers in advance, and a ledger structure that isolates each fee type lets you quantify the impact on your actual sales mix within a month of the change taking effect. Sellers who do this adjust pricing or listings quickly; sellers with lump-sum fee accounting only notice when annual profit disappoints. The same itemised history also feeds pricing decisions for new SKUs, because expected fees per price band and category can be read straight out of your own past data instead of estimated.
Frequently asked questions
Should Flipkart fees be deducted from sales or shown as expenses?
Shown as expenses. Sales should be booked at gross invoice value from the sales/GST report, because GST returns require invoice-level turnover. Fees then appear as itemised indirect expenses. Netting fees against sales understates turnover, creates GST reconciliation mismatches, and hides your true cost of selling on the marketplace from the profit and loss account.
Can I claim input credit on the GST Flipkart charges on its fees?
In most cases a GST-registered seller can claim GST on marketplace fees as input tax credit, since the fees are services used in the course of business. The settlement report's GST on Fees column gives you the amount per order item. Eligibility and the matching against GSTR-2B depend on your specific situation, so confirm the treatment with your CA.
How do I track fees per product rather than per month?
Use the fact that the settlement report is order-item-level: each row carries the fees for one item, so fee cost can be attributed to the SKU sold. Doing this manually is impractical at volume, which is why automated imports that preserve item-level detail, rather than posting monthly lump sums, are what make per-SKU contribution margin analysis possible in Tally.
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