Menu
A direct comparison

A CSV import isn’t GST-correct bookkeeping.

A one-time export, a generic connector, or a flat order-to-voucher pusher gets orders into your ERP. It doesn’t get them in correctly -- place of supply, B2B, exports, and returns all need real logic a plain import was never built to have.

Side by side

Where a basic import breaks.

TopicBasic CSV import / generic connectorLedgeree
Place of supplyUses the company's registered state as a fixed constant, or the billing address -- inter-state orders often get CGST+SGST instead of IGST, or vice versa.
Resolved per fulfillment against the actual warehouse's mapped ship-from state vs. the customer's ship-to state -- correct even across multiple warehouses.
Multiple GST rates in one dayEither blended into one number, or requires the ERP's own tax engine to be configured correctly per item -- rarely is.
Every distinct GST rate present in a day's aggregate gets its own correctly-split Sales + CGST/SGST(or IGST) line, automatically.
B2B ordersA basic order-row import may not create or match a GSTIN-linked party ledger, so B2B treatment has to be configured and verified separately.
Detected automatically, matched to a dedicated party ledger by GSTIN (never by name), posted as its own voucher with the GSTIN correctly recorded.
Export ordersNo concept of export vs. domestic -- either posted at the normal domestic rate (wrong) or skipped entirely.
Detected by ship-to country, zero-rated under your LUT automatically, LUT financial-year staleness blocked, one voucher per shipment.
ReturnsEither not synced at all, or silently reversed against the original Sales entry -- gross sales and returns don't stay visible separately.
Real Sales Return vouchers on the return date's own state; same-day returns excluded before they're ever posted at all.
Voucher numberingA one-time import doesn't need a sequence at all -- run it twice and you get duplicates.
Gap-free by design: a counter is only consumed once Tally confirms the push actually succeeded, never before.
What happens when a push failsNothing -- a one-shot import either fully succeeds or you're left to figure out what didn't import and re-run it by hand.
Automatic retry with backoff, then a clear failure log with the real ERP error message -- and a cap-based pause-and-prompt that never drops an order.
Itemized / Stock Item accuracyA raw import either skips inventory detail or fails silently against Stock Item names that don't match.
Optional itemized billing auto-maps SKUs against your real Tally Stock Item list, and hard-blocks (never guesses) on an unmapped one.
No ERP at allNot applicable -- there's nothing to import into.
Ledgeree Books gives you a compliant daybook and GST-liability tracker standalone, no ERP required.

See the difference on your own orders.

A 5-day free trial is enough to watch a real day’s shipments post correctly.

Start free trial