GST is usually where marketplace data and accounting disagrees the most. The marketplace reports tax in its own terms; the ERP needs it in GST terms. Bridging the two is a specific, mechanical job.
Here is the path one order’s GST takes.
Step 1 — The order carries taxable events
A single order typically attracts GST on more than one component:
| Component | What carries GST |
|---|---|
| Sale of goods | Output GST on the taxable value. |
| Marketplace charges | GST on commission and fees where applicable. |
| Reverse / unregistered rules | Situations where the recipient accounts for tax. |
Each component has its own rate and its own GST head. A total or a blended rate flattens all of this into something useless for returns.
Step 2 — Marketplace data records the tax
Marketplace reports capture the GST values at order and settlement level: taxable value, HSN/SAC, rate, and the GST collected. TCS on ecommerce sales is tracked separately.
The data exists — but in the marketplace’s format, keyed to its own order and settlement identifiers.
Step 3 — Accounting needs GST-wise structure
For GST-wise accounting, the captured data must be re-expressed per head:
- Output GST on sales, broken by rate.
- Input GST on marketplace charges, eligible for claim.
- TCS available, mapped to the marketplace’s filings.
- GST on refunds, reversing the original tax lines.
Every line must trace back to an order, so a return value or an input credit can be questioned and answered.
Step 4 — The ERP receives GST-ready entries
The ERP posts entries with the right GST head and tax account per line. For Tally, this means GSTR-ready ledgers; for SAP and Zoho, mapping to their tax structures.
The ERP is not being asked to reinvent the GST data. It is receiving accounting that is already GST-correct and order-traceable.
Step 5 — Returns and books agree
Because the tax data was captured per order and posted per head:
- GST returns can be reconstructed from the books.
- TCS and TDS statements reconcile to marketplace filings.
- Input credit claims are supported by the underlying invoices and ledger lines.
What makes the flow survive scale
At low volume, a spreadsheet can hold the GST data. At scale, the flow has to be computed: every order decomposed, every head classified, every posting built and mapped into the ERP.
That is exactly what DeepEcom does between the marketplace and your ERP — turning order-level GST data into GST-wise accounting your books can reconcile.