Tally Export Center
Preview · Running on the merchant’s Windows PC
PRISM Tally Bridge
·v0.9.2Connected to Tally Prime
localhost:9000·Company: SPAA SUPPLIER LLP·Tally Prime 6.0.2
Last sync
just now
Voucher queue
5 pendingActivity log
auto-scroll
Cloud-side queue · what the Bridge picks up
Vouchers ready
90
Pending batches
7
Failed
0
Total amount
₹2,02,592.40
sales
Sales
POS bills → Tally sales vouchers
64
₹1,48,273.00
purchase
Purchases
Supplier bills → purchase vouchers
4
₹54,319.40
receipt
Receipts
Cash, UPI, card receipts on completed bills
0
₹0.00
No batches yet.
payment
Payments
Supplier payments out (planned module)
0
₹0.00
credit-note
Credit Notes
Sales returns (planned module)
0
₹0.00
debit-note
Debit Notes
Purchase returns (planned module)
0
₹0.00
stock-item
Stock Items
Item master export with HSN + GST
12
₹0.00
ledger
Ledgers
Customers + suppliers as Tally ledgers
10
₹0.00
PRISM Tally Bridge — auto-sync architecture
How it works
TallyPrime exposes a built-in HTTP/XML server on port 9000(and JSON in 7.0+). It is free in every edition, but only callable from the same machine. To push our cloud bills into a CA's Tally without manual import, we ship a small Windows agent — the PRISM Tally Bridge — that the CA installs once.
The Bridge polls our cloud queue every few minutes, reads pending vouchers, and POSTs each one to http://localhost:9000. On success it advances the batch to accepted; on failure it returns to failed with the Tally error attached, ready for retry.
Same approach used by Biz Analyst, Anjok Tally Sync, and Zoho's Tally Connector — well-trodden ground.
Wire diagram
PRISM Cloud
vouchers queue
PRISM Tally Bridge
Windows agent · same PC as Tally
TallyPrime
Silver/Gold · all editions
For CAs already on cloud Tally
If the CA uses Tally on Cloud (Reverie, NTT, NetForChoice, or Tally Solutions' own OCI offering), the Bridge runs on the same Windows VPS as Tally — no end-user install. We can also run it as a Docker container if the VPS allows. Either way, the sync is fully transparent to the CA after one-time setup.
Today, in this POC
The state machine on each batch above ( pending → exported → accepted | failed → pending) mirrors what the Bridge will drive in production. Today the buttons advance the state for a demo; the XML and CSV downloads produce the exact payloads the Bridge will POST. Drop those XMLs into TallyPrime via F1 → Import → XML to see them land natively.