Amazon Commission & Fees: Ledger Treatment in Tally
Amazon's fees are the single biggest gap between your invoiced sales and your bank deposit, yet many sellers book them as one lump called marketplace charges. That hides margin problems, complicates GST input credit, and makes reconciliation guesswork. A better approach: mirror Amazon's own fee taxonomy in your Tally ledger tree, so every settlement row has a natural home.
Where fee data comes from
Fees live in the settlement flat file as rows with amount-type ItemFees (order-linked fees) plus various other-transaction rows (subscription, storage, and service charges). Each carries an amount-description — Commission, FixedClosingFee, Shipping chargeback, and so on — and a negative amount, since it reduces the payout. Amazon also issues tax invoices for its fees, which are your documentary basis for claiming input credit on the GST charged; the settlement rows and the fee invoices should reconcile with each other.
A ledger tree that mirrors Amazon's fee families
| amount-description | Suggested Tally ledger | Group |
|---|---|---|
| Commission | Amazon Referral Fees | Indirect Expenses — Marketplace Fees |
| FixedClosingFee | Amazon Closing Fees | Indirect Expenses — Marketplace Fees |
| Shipping chargeback | Amazon Shipping Recovery | Indirect Expenses — Fulfilment |
| FBA-related fee lines | Amazon FBA Fees (see below) | Indirect Expenses — Fulfilment |
| Refund-linked fee reversals | Same ledger as the original fee | — (posted as reversal) |
Two design rules make this durable. First, fee reversals go back to the original fee ledger, not to income — when a refund triggers a commission reversal, netting it against Amazon Referral Fees keeps the ledger equal to your true fee cost. Second, keep fulfilment costs (shipping, FBA handling and storage) separate from selling costs (referral, closing), because the two move differently as your mix of FBA and self-ship changes. The FBA family is big enough to deserve its own article — see the FBA fees accounting guide.
GST input credit on Amazon fees
Amazon charges GST on its fees, and for a registered seller this is generally claimable input tax credit on business expenses — subject to the usual ITC conditions, so have your CA confirm eligibility and any restrictions for your case. Practically:
- Book the taxable fee and its GST separately, with GST going to input credit ledgers.
- Match claimed ITC against Amazon's fee invoices, and check the invoices surface in your GSTR-2B before claiming.
- Watch refund months: fee reversals come with corresponding tax adjustments that must also reverse in your ITC workings.
Summary posting vs row-level posting
You can post fees two ways. Row-level booking creates a fee entry per order — perfect traceability, heavy voucher volume. Settlement-level summary booking totals each amount-description per settlement-id into one voucher — compact, and still reconciles because the settlement file remains your drill-down. Most sellers are best served by summary posting with the raw file archived; row-level suits sellers whose CA wants order-level cost audit trails. TallySutra supports the summarised pattern out of the box: each uploaded settlement file becomes a small set of balanced vouchers with every amount-description mapped to your chosen ledger, and the mapping is remembered for the next upload. You can see the workflow on the Amazon to Tally solution page.
Checks that keep fee accounting honest
- Sum of all fee ledgers for a settlement equals the total ItemFees and charge rows in that settlement-id.
- Referral fee as a percentage of Principal stays within your category's expected band month over month; drift means category changes or errors.
- GST input claimed on fees ties to Amazon's fee invoices for the period.
- Fee reversals in refund-heavy months are visible as credits inside the fee ledgers, not as stray income.
Fee accounting is unglamorous, but it is where marketplace profitability becomes measurable. If you would rather not hand-classify settlement rows every cycle, the conversion is exactly what TallySutra plans cover — upload the file, review the exceptions, and let the ledger mapping do the rest.
A ten-minute month-end fee review
Once the ledger tree is in place, a short monthly review keeps it earning its keep. Pull the marketplace fee group in Tally and scan four things: the referral fee ratio against Principal for the month, which should sit steadily inside your category's band; the closing fee total against units shipped, which should track volume almost linearly; any balance in the unclassified fee suspense ledger, which should be zero or freshly explained; and the credit entries inside fee ledgers, which should correspond to the month's refund activity. Ten minutes, four glances, and most fee-side surprises — a category reclassification, a fee schedule change Amazon announced that nobody read, a misfiring ledger mapping — surface while they are one month old. Sellers who skip this review tend to meet the same surprises at year end, aggregated and expensive to unpick, when the CA asks why selling costs jumped mid-year and the answer is buried across eighteen settlement files nobody wants to reopen.
Frequently asked questions
Should Amazon fees be netted against sales instead of booked as expenses?
Book them gross. Your sales are what you invoiced the customer (per the MTR); Amazon's fees are your cost of selling, and netting them into revenue understates both turnover and expenses — a problem for GST turnover reporting and for margin analysis. Gross booking also lets each settlement reconcile line by line. Your CA should confirm presentation for your entity, but gross is the standard treatment.
Can I claim GST input credit on every Amazon fee?
GST charged on genuine business-expense fees is generally creditable for a registered seller, but eligibility depends on the usual ITC conditions — possession of a valid tax invoice, the supply appearing in GSTR-2B, and no blocking provisions applying. Claim against Amazon's fee invoices rather than settlement rows alone, and have your CA confirm treatment for any unusual fee categories.
How do I handle a fee that appears in the settlement file but has no obvious category?
Do not force it into a familiar ledger. Park it in a clearly named suspense ledger such as Amazon Fees — Unclassified, keep the settlement row reference, and resolve it when Amazon's fee invoice clarifies the nature. In TallySutra, such rows go to the exception queue automatically so they cannot silently distort your expense ledgers.
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