How to import purchase invoices into TallyPrime — every method, compared

There are three ways to get a GST purchase bill into TallyPrime, and they sit on a clear trade-off between effort and scale. You can type it in by hand as a Purchase voucher (F9) — total control, no setup, but minutes per bill. You can import a batch from Excel, XML, or JSON using Tally's native Import Data — fast when the data is already digitised and GST-correct. Or you can automate the capture — software reads the bill, validates the GST fields, and creates a reviewable voucher or draft transaction. That third route now includes Tally's own TallyIra / Docs by Ira workflow as well as third-party tools like MoneyMistri. This guide covers all three: the exact steps for manual entry, how native import works and where it breaks, and what automated bill-to-voucher actually does — so you can match the method to your volume.

The three routes at a glance

Method 1 — enter it manually as a Purchase voucher (F9)

The built-in way, and the right one when volume is low. In TallyPrime:

1. Open the purchase voucher. Press Alt+G, choose Create Voucher, and press F9 for Purchase — or from the Gateway of Tally, open Vouchers and press F9. Use Ctrl+H to switch between Item Invoice (goods) and Accounting Invoice (services).
2. Pick the registration (if you have more than one). Press F3 and select the GST registration this purchase belongs to.
3. Enter the supplier invoice number and date exactly as printed on the bill.
4. Select the supplier in Party A/c name (or Cash/Bank for a cash purchase), and set the Place of Supply in the Party Details screen.
5. Select the purchase ledger — one that is marked as GST applicable.
6. Add the line items — stock items with quantity and rate (Item Invoice), or service ledgers with amounts (Accounting Invoice).
7. Apply the GST ledgers — CGST and SGST/UTGST for a local purchase, IGST for interstate (and Cess if it applies).
8. Save with Ctrl+A.

It's reliable and costs nothing extra. It's also where data-entry errors enter your books — a transposed GSTIN, an invoice number typed as "312" instead of "KSE/2025-26/0312", the wrong tax head. None of those announce themselves; they surface weeks later, at GSTR-2B reconciliation, when a credit you expected isn't there.

Method 2 — import from Excel, XML, or JSON

TallyPrime imports both masters (ledgers, stock items) and transactions (vouchers) natively. Press Alt+O for Import, choose Masters or Transactions, and point Tally at the file. Excel import has been supported since Release 4.0, and Release 7.0 added JSON alongside the long-standing XML format. Import masters first, then transactions, so the parties and items a voucher refers to already exist when it lands.

The catch is in the word clean. Tally imports what you give it: if a row is missing a mandatory field, names a ledger that doesn't exist, carries an invalid GSTIN, or duplicates an existing voucher, Tally raises an exception and parks the row rather than guessing. So import is excellent for moving structured data into Tally — a migration, an export from a billing app — but it does nothing to turn a PDF or a photo of a supplier's bill into that structured row. Something still has to digitise and GST-validate the bill first.

Method 3 — automate the capture (extraction + connector)

This is the route built for the common case: dozens of paper or PDF purchase bills a month that nobody wants to retype. The shape is always the same — software reads the bill (a job that needs more than plain OCR; see GST invoice OCR for Tally), validates the GST fields deterministically, lets a human review and correct, then writes a finished Purchase voucher into Tally.

The writing step uses Tally's own data gateway. TallyPrime runs a built-in HTTP server (default port 9000) that accepts vouchers posted as XML in Tally's native structure, so a local connector can push a validated voucher straight in — and read it back to confirm it actually landed. That is the pipeline MoneyMistri runs end-to-end, with a deterministic GST gate (GSTIN checksum, tax-mode and totals consistency) before anything reaches the connector. The anatomy of the voucher itself is covered in Tally purchase voucher automation.

"Doesn't TallyPrime do this itself now?"

Yes, partly. Tally now lists TallyIra / Docs by Ira as an AI invoice processor that scans or imports supplier invoices and creates draft transactions inside TallyPrime. That is an important change: for many Tally operators, the first comparison should be TallyIra versus a third-party automation tool.

The distinction is workflow. TallyIra is designed around draft-voucher creation inside the Tally environment. MoneyMistri is designed around owner-side capture, shared review with the accountant, deterministic GST validation before posting, and read-back verification after the connector writes to Tally. If you only need a Tally-native draft from a bill image, evaluate TallyIra. If you need capture outside Tally, GST gates, collaboration, and books that surface leaks, evaluate a pipeline like MoneyMistri.

What every method must get right

Whichever route you choose, a GST purchase voucher is only useful if a few fields are exactly right — because they are what your input tax credit depends on:

• The supplier GSTIN, character for character. A wrong one routes the invoice into a different buyer's GSTR-2B, and your credit with it. Validate it before posting.
• The invoice number exactly as printed (up to 16 characters under Rule 46). "312" and "KSE/2025-26/0312" will not reconcile against your 2B.
• The right tax heads — CGST + SGST/UTGST for a local purchase, IGST for interstate, driven by place of supply. Booking the wrong head is wrongly availed credit even when the total matches.
• HSN/SAC and rate per line, so the taxable value and tax foot correctly.

Get these right at entry and the month-end 2B match is quick; get them wrong and you are hunting mismatches under a deadline. That is the real reason automation pays off above a certain volume — not the typing it saves, but the errors it refuses to let through.

TallyPrime navigation, shortcut keys, import behaviour, the port-9000 gateway, and TallyIra status described here reflect public Tally sources checked in June 2026. Tally updates its software and help docs regularly, so confirm the current steps on help.tallysolutions.com before relying on specifics.