Tally Prime Integration for Amazon Sellers: Complete Setup Guide
For Amazon sellers in India, Tally Prime remains the most widely used accounting software. But manually entering marketplace transactions into Tally is tedious, error-prone, and a massive drain on productivity. Every order, return, fee deduction, and settlement needs to be recorded as the correct voucher type with proper GST treatment. For sellers processing hundreds or thousands of orders per month, manual Tally entry is simply not sustainable. This guide walks you through how to integrate Tally Prime with your Amazon seller account using eVanik, automating voucher posting, GST entries, and ledger reconciliation.
Why Tally Integration Matters
Without integration, sellers face a constant backlog of accounting entries. Each Amazon order generates multiple accounting entries — a sales voucher, a receipt voucher for the payment, debit notes for marketplace fees, and potentially credit notes for returns. Multiply this by thousands of orders across multiple marketplaces, and you have an accounting nightmare. Late or inaccurate entries lead to incorrect financial statements, GST filing errors, and poor visibility into business profitability. Integration eliminates this bottleneck by automating the entire process.
Setting Up the Integration
The setup process through eVanik's Tally Prime Integration involves a few key steps. First, connect your Amazon Seller Central account to eVanik using SP-API credentials. This allows eVanik to pull your order, return, and settlement data automatically. Next, install the Tally connector module which creates a bridge between eVanik and your Tally Prime instance. The connector works with both Tally Prime and Tally ERP 9, supporting local and cloud-hosted installations.
During setup, you will configure your company preferences — the Tally company name, financial year, and base currency. The system then guides you through ledger mapping, which is the most critical step of the integration.
Ledger Mapping and Configuration
Ledger mapping tells the integration how to categorize each type of marketplace transaction in Tally. You need to map: Amazon sales to a sales ledger (typically under "Sales Accounts"), marketplace fees to an expense ledger (like "Marketplace Commission"), shipping charges to a logistics expense ledger, TCS to a duties/taxes ledger, and settlement receipts to your bank ledger. Each mapping ensures that transactions flow into the correct Tally accounts automatically.
For GST purposes, you also configure the tax classification — whether each ledger should attract CGST+SGST or IGST based on the supply type. The integration handles inter-state and intra-state tax treatment automatically based on the order details, so your GST entries are always accurate.
Voucher Types and Posting
The integration creates several voucher types in Tally: Sales vouchers for each order, Credit Notes for returns and refunds, Debit Notes for marketplace fee deductions, Journal vouchers for adjustments and write-offs, and Receipt vouchers for settlement payments. Each voucher includes all relevant details — order ID, customer information (for B2B invoices), item details, HSN codes, GST breakdowns, and marketplace reference numbers. This level of detail ensures your books are audit-ready.
Troubleshooting Common Issues
The most common issues during integration are: ledger mismatch errors (when a Tally ledger name does not match the mapped name exactly), duplicate voucher posting (usually caused by re-running a sync period), and GST rate mismatches between the product catalogue and Tally settings. If you encounter posting failures, check the error log in the OWS Accounting Pro dashboard for specific error messages. Most issues are resolved by correcting the ledger mapping or updating product HSN codes in the system.
Key Takeaways
- Manual Tally entry is unsustainable for sellers processing hundreds of orders per month
- Integration automates sales vouchers, credit notes, debit notes, and GST entries
- Correct ledger mapping is the most critical step — verify each mapping carefully
- GST treatment (CGST+SGST vs IGST) is handled automatically based on order data
- Check error logs for posting failures and resolve ledger mismatches promptly













































































