Flipkart GST Report to Tally: Complete Import Guide
The Flipkart sales report, often called the GST report, is the file your GSTR-1 lives or dies by. It is the invoice-level truth of what you sold, at what tax rate, into which state. Import it into TallyPrime correctly and GST filing becomes a printout; import it wrong and you spend quarter-end reconciling mismatches with your CA. This guide covers the columns, the mapping and the traps.
Reading the report's columns
Each row is one order item event. The columns that matter for accounting:
| Column | Meaning | Drives in Tally |
|---|---|---|
| Order Item ID | Unique item identifier | Voucher reference, duplicate detection |
| Event Type | Sale or Return | Sales voucher vs credit note |
| Invoice No / Date | Legal invoice reference | Voucher number and date |
| Taxable Value | Pre-tax value | Sales ledger amount |
| IGST / CGST / SGST | Tax amounts by type | Output tax ledgers |
| Invoice Amount | Total including tax | Party ledger amount |
| Customer's Delivery State | Destination of supply | Place of supply, IGST vs CGST/SGST logic |
Place of supply: the column sellers ignore
Customer's Delivery State is not metadata; it determines tax type. Deliveries within your registration state carry CGST+SGST; deliveries to other states carry IGST. The report already splits the amounts correctly, so your job is to preserve that split, not recompute it. In Tally that means the imported voucher must select the right tax ledgers per row and record place of supply so GSTR-1's state-wise B2C tables come out right. Flattening everything into one tax ledger is the most common manual-entry corruption, and it is invisible until the GSTR-1 state summary disagrees with the report.
Ledger structure for a clean import
- One sales ledger per GST rate (Sales @5%, Sales @12%, Sales @18%...), because rate-wise reporting is mandatory.
- Output IGST, Output CGST, Output SGST ledgers under Duties & Taxes.
- Flipkart as the party ledger, carrying Invoice Amount per voucher.
- A Sales Returns route for Event Type = Return rows, posted as credit notes referencing original invoices; the detail is in our credit notes guide.
Import mechanics: manual vs file-based automation
Manual entry from this report means one voucher per invoice with correct rate ledgers, tax split and state, hundreds of times. The realistic alternative is file-based conversion: TallySutra takes the GST report exactly as downloaded from Seller Hub, validates every row, and generates TallyPrime vouchers with rate-wise ledgers, correct IGST/CGST/SGST allocation and place of supply preserved from the delivery state column. Rows that fail validation, an unknown GST rate, a tax split that does not sum to Invoice Amount, a duplicate Order Item ID, go to an exception queue instead of your books, and a CA review step gates the final export to Tally XML. Uploads are duplicate-safe, so re-downloading a corrected report and importing again cannot double-book sales. TallySutra works only on the files you upload; it has no API access to Seller Hub, and it prepares your books rather than filing returns, so GSTR-1 submission stays with you or your CA.
Aligning books to GSTR-1
- Total Taxable Value and tax by rate from the report; compare with Tally's rate-wise sales summary. They must match to the rupee.
- Compare state-wise totals against Tally's place-of-supply data for the B2C tables.
- Reconcile credit notes: Return rows in the report versus credit notes in Tally versus GSTR-1's credit note section.
- Cross-check TCS: the GST portal's TCS credit (0.5% u/s 52, reported by Flipkart) should correspond to your net taxable supplies; differences usually trace to returns timing, as covered in the TCS and TDS guide.
Where figures disagree, trust the drill-down: because both the report and (if imported at item level) your Tally data reference Order Item IDs, mismatches can be traced to specific rows rather than argued about in aggregate. That traceability is the entire payoff of importing the GST report properly, and it is what your CA will thank you for at filing time. Final tax positions, as always, are your CA's call; the books' job is to make that call easy.
One last discipline: never mix report versions. If you re-download a period after Flipkart posts corrections, treat the newer file as the source of truth, re-run the comparison totals, and let a duplicate-safe import pick up only the genuinely changed rows. Books built from a mixture of old and new exports are the hardest kind to debug, because every total is almost right. A single authoritative file per period, archived unedited alongside the Tally data generated from it, keeps the audit trail exactly as clean as the numbers.
Frequently asked questions
Is the Flipkart sales report enough to prepare GSTR-1?
For your Flipkart sales, largely yes: it carries invoice numbers and dates, taxable values, rate-wise IGST/CGST/SGST splits, and delivery states for place of supply, which is what GSTR-1's tables need. You still combine it with sales from other channels, and filing itself happens on the portal or through filing software with your CA. TallySutra prepares the Tally books, not the filing.
Why do IGST and CGST/SGST both appear in the report?
Because tax type depends on each order's destination. Items delivered within your GST registration state attract CGST plus SGST; items delivered to any other state attract IGST. The report computes this per row using the Customer's Delivery State. Your import must preserve the per-row split rather than recomputing or merging it, or your state-wise GSTR-1 tables will not reconcile.
What validation should happen before rows become vouchers?
At minimum: the tax amounts plus Taxable Value should equal Invoice Amount, the implied GST rate should be a real slab, the Order Item ID should not already exist in your books, and Return rows should match an original sale. Automated imports like TallySutra run these checks and quarantine failures in an exception queue, which is safer than discovering bad rows inside Tally later.
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