Journal Vouchers in Tally for Marketplace Fees
Between your gross marketplace sales and the payout in your bank sits a long tail of deductions: referral commission, closing fees, shipping and fulfilment charges, advertising, and tax collected at source. In TallyPrime these belong in Journal vouchers (or Purchase vouchers, where you book against the platform's fee invoices) — and booking them correctly is what makes your party ledger reconcile and your input GST credit claimable. Here is the working method.
Know your fee heads
Fee names differ by platform, but they cluster into a handful of accounting heads:
| Fee head | Examples from settlement reports | Suggested ledger |
|---|---|---|
| Commission | Referral fee, closing fee, collection fee | Marketplace Commission |
| Logistics | Weight handling, shipping fee, FBA fulfilment, pick and pack | Shipping and Fulfilment Fees |
| Advertising | Sponsored products, PLA charges deducted in settlement | Advertising — Marketplace |
| Storage and other | Warehouse storage, removal fees, service charges | Marketplace Other Charges |
| Tax collected at source | TCS under GST Section 52 | TCS Receivable (Current Assets) |
Resist inventing a new ledger for every fee label the platforms dream up — map new labels into these stable heads and your P&L stays readable across years.
The journal entry pattern
For a fee deduction the entry is: debit the expense ledger, debit input GST (the platforms charge GST on their fees and issue tax invoices for them), credit the marketplace party ledger. For TCS: debit TCS Receivable, credit the party ledger. In import XML terms each line lives in ALLLEDGERENTRIES.LIST with debits as negative amounts flagged ISDEEMEDPOSITIVE Yes — the same convention as every Tally voucher, covered in our XML import guide.
Input GST on fees: real money, commonly lost
Marketplace fees carry GST, and registered sellers can generally claim that as input credit — but only if it is booked to input tax ledgers and matches the invoices the platform uploads against your GSTIN. Sellers who book fees gross (expense including GST, no input ledger) quietly overpay tax every month. Two cautions: claim credit from the platform's fee invoices rather than deriving it loosely from settlement rows, and reconcile against GSTR-2B before claiming. Eligibility and blocked-credit rules have nuances, so have your CA confirm the treatment for your registrations.
A quick monthly discipline keeps the credit intact:
- Download the platform's fee tax invoices for the month, not just the settlement file.
- Tie the input GST booked in your journals to those invoices.
- Match against GSTR-2B before claiming, and park unmatched amounts rather than claiming them.
- Investigate gaps the same month — platform invoices occasionally lag a period.
TCS is an asset, not an expense
The TCS a marketplace deducts under Section 52 is deposited against your GSTIN and becomes claimable credit once you accept it on the GST portal. Booking it as an expense both overstates costs and abandons the credit. Debit it to a TCS Receivable ledger under Current Assets, then clear that ledger when the credit lands in your cash ledger. Rates and mechanics are prescribed under GST law and have changed over time — confirm current rates with your CA rather than hard-coding them into a spreadsheet.
Where sellers also face income-tax TDS deducted by platforms under its own provisions, keep that in a separate receivable ledger from GST TCS — the two credits are claimed through entirely different mechanisms, and merging them into one ledger creates a reconciliation knot at year end that takes hours to untangle. Naming the ledgers explicitly (TCS Receivable — GST, TDS Receivable — Income Tax) prevents the mix-up at entry time, and your CA will thank you when the two figures head to different sections of the returns.
Granularity and automation
One journal per settlement period per fee head is the practical sweet spot — detailed enough to analyse, compact enough to audit. Daily journals drown the Day Book; one monster journal per quarter hides cost trends and makes error isolation miserable. What makes it hard manually is volume and classification: an Amazon settlement file can contain dozens of fee types across thousands of rows. TallySutra classifies every fee row from Amazon, Flipkart and Meesho reports into your mapped ledger heads, splits out the GST portions, books TCS to your receivable ledger, and produces balanced journal vouchers that reconcile to the payout — all held for CA approval before a single entry reaches Tally, with duplicate-safe re-imports if a report is processed twice. The receipts side of the same settlement is covered in the settlement receipts guide; see who this workflow fits for the end-to-end picture.
Frequently asked questions
Should marketplace fees be booked as journal or purchase vouchers?
Both work. Journals against the party ledger are the common pattern for settlement deductions; purchase vouchers make sense when you book against the platform's monthly fee tax invoice. Pick one convention with your CA and keep it consistent.
Can I claim GST input credit on Amazon and Flipkart fees?
Generally yes — platforms charge GST on fees and upload invoices against your GSTIN. Book the tax to input GST ledgers and reconcile with GSTR-2B before claiming. Your CA should confirm eligibility for your specific case.
Is TCS deducted by marketplaces an expense?
No. TCS under GST Section 52 is a recoverable credit. Book it to a TCS Receivable ledger under Current Assets and clear it when you accept the credit on the GST portal.
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