Importing E-Commerce Sales Data into TallyPrime

Selling on major online marketplaces like Amazon, Flipkart, or Meesho offers massive scale, but it also creates a complex accounting challenge. E-commerce platforms act as intermediaries, collecting client payments, withholding commission fees, deducting statutory taxes, and sending consolidated bank payouts.

To maintain accurate tax records, accountants must reconcile e-commerce payouts, returns, shipping expenses, and withholding taxes. Manually posting these transactions for thousands of weekly orders is highly inefficient.

Understanding the Amazon/Flipkart Settlement Report Columns

Before you can import data to Tally Prime, you must understand what each column in the marketplace settlement report means. Amazon's settlement report (available in Seller Central → Reports → Payments) and Flipkart's settlement statement include the following key fields:

Key Components of E-Commerce Payout Sheets

Marketplaces provide weekly or monthly settlement sheets. To record these correctly in Tally, you must identify and map the following key fields:

Handling Multi-State GST & Place of Supply

Unlike physical retail, e-commerce involves shipping to customers all over India. Under GST rules, the tax ledger is determined by the customer's state (the Place of Supply):

• Intra-State Sales: If the customer's shipping address is in your registered state, split the tax into Output CGST and Output SGST.
• Inter-State Sales: If the customer is in a different state, map the entire tax component to the Output IGST ledger.

The settlement report typically contains the buyer's state or PIN code. You must group orders by destination state and create separate Tally sales vouchers (or use GST class allocation) for intra-state vs. inter-state sales to ensure your GSTR-1 is correctly split into B2B/B2C with the right tax type.

Recording Statutory TCS and TDS Journal Entries

Before transferring your payout, Amazon and Flipkart deduct GST TCS (under Section 52) and Income Tax TDS (under Section 194O). You must record these deductions in a Journal voucher (F7) to reconcile the debtor ledger:

Debit: TDS 194O Receivable                 -- [1% of Gross Sales u/s 194O]
Debit: GST TCS Receivable                  -- [1% of Net taxable sales]
Debit: E-commerce Commission Expense       -- [Marketplace commission fees]
Debit: Input SGST / CGST (on commission)   -- [GST on Marketplace fees]
Credit: Marketplace Sundry Debtor          -- [Total Deductions Withheld]

Note: You can claim Input Tax Credit (ITC) on the marketplace commission fees. Ensure the invoice provided by the platform reflects in your GSTR-2B.

Monthly Settlement Reconciliation with Bank Deposits

Amazon and Flipkart typically remit funds every 7–14 days. Each bank deposit corresponds to a specific settlement cycle (identified by a Settlement ID in the report). To reconcile:

1. Download the settlement report for the specific settlement ID from Seller Central.
2. Total the Net Settlement Amount column — this should match the bank credit in your statement.
3. Post the Journal entry reducing the Marketplace Sundry Debtor balance (step above).
4. Post a Receipt voucher debiting your Bank Account and crediting the Marketplace Debtor to clear the balance.
5. Reconcile the bank book — the bank ledger balance should now match your bank statement running total.

At month-end, the GST TCS Receivable balance should match the TCS amounts reflected in your GSTR-2A/2B. The TDS 194O Receivable balance should match the TDS reflected in your Form 26AS.

Manual Import vs. Automation Tools: A Comparison

Many sellers manually copy settlement data from Excel into Tally — a workable approach for a few dozen orders per week but unsustainable at scale. Here is how manual entry compares to automation:

Common Import Errors and How to Fix Them

Whether you import data manually or use a tool, these are the most frequent errors and their solutions:

• Duplicate vouchers: Importing the same settlement report twice creates duplicate sales entries. Fix by checking the Settlement ID before import and deleting duplicates via Tally's Voucher Alteration screen.
• Wrong GST ledger (CGST/SGST vs IGST): Caused by missing state-code logic. Fix by verifying the buyer's state column and applying GST class-based allocation rules in Tally.
• TCS not posted as receivable: Sellers sometimes expense TCS directly to P&L. This is incorrect — TCS is a tax asset. Fix by creating a GST TCS Receivable ledger under Current Assets and adjusting past entries via a correcting journal.
• Missing commission ITC: If the platform's GST invoice for commission doesn't reflect in GSTR-2B, you cannot claim ITC for that period. Follow up with the marketplace and defer ITC to the period it appears.
• Returns not reversed: Customer return adjustments in settlement reports must be posted as sales returns (credit notes). Omitting them overstates turnover and GST liability.

Streamlining E-Commerce Accounting with TrulyInvoice

Reconciling multi-state sales, returns, and payout deductions manually is a major source of bookkeeping errors. This is where TrulyInvoice simplifies your workflow.

TrulyInvoice reads your bank statement PDFs, extracts the transaction rows, and maps details directly into Tally Prime receipt and payment vouchers. It helps match ledger names and flags duplicate entries before they enter Tally. By managing your e-commerce payout flows on a flat subscription of plans starting at ₹399/month, TrulyInvoice helps you maintain audit-ready books without manual data entry errors — freeing your accountant to focus on analysis, not data-punching.