Push every bill, payment and invoice from Onsite to Tally — automatically.
Stop re-typing site spend, vendor bills and sales invoices into Tally at month-end. The Onsite × Tally integration journals every approved transaction directly into your books — with GST split, party ledgers, cost centres, and TDS deductions handled correctly out of the box.
Construction firms lose days every month re-entering Onsite data into Tally.
Site teams already approve material purchases, subcon bills, salary payouts and customer invoices in Onsite. Then accounts spends a week re-typing all of it into Tally. Errors stack up. GST returns drift. Reconciliation becomes a nightmare. We’ve watched too many clients live this.
Hours wasted on manual entry
An accountant can spend 2–4 days a month copying approved Onsite records into Tally vouchers — line by line, GST split by GST split.
Data drift between systems
Onsite has the source of truth on what the site actually spent. Tally has the books. They diverge. GST returns are filed from wrong numbers.
Cost-centre allocation breaks
Project-wise cost tracking falls apart when the data hop is manual. P&L by site becomes guesswork instead of reporting.
A small agent. Your existing Tally. Zero re-entry.
You install a lightweight desktop agent on the machine running TallyPrime. The agent listens for approved transactions from your Onsite cloud account and posts them into Tally as proper double-entry vouchers — without ever exposing Tally to the public internet.
Approve in Onsite
Site managers and project leads approve bills, payments and invoices in Onsite the way they already do. Nothing changes about your daily workflow.
Cloud builds the voucher
Our cloud picks up each approved record, applies your tax / ledger / cost-centre mappings, builds a balanced double-entry voucher, and queues it for the agent.
Agent posts to Tally
The on-prem agent picks up the queued voucher and posts it into Tally — with auto-creation of missing party ledgers, TDS legs, and GST classification.
Every voucher type a construction firm actually uses.
Built for the realities of Indian construction accounting — multi-state GSTINs, retentions, mobilization advances, P2P labour payments, the lot.
Posts as Purchase voucher with lump-sum or itemwise expense legs, vendor credit, full GST split, additional charges, discounts, retention and TDS deductions.
Vendor payouts, customer receipts, cash withdrawals — routed to the right Tally bank ledger via your bank-account mappings.
Petty spend at the site — fevicol, paint, stationery — booked as configurable Tally voucher type (Journal / Payment / your custom type) with cost-centre tagging.
Project-wise cost-centre tagging on every leg — your Tally P&L by Cost Centre report finally gives you per-site profitability without manual journal entries.
Customer-side invoices with proper output GST direction, TDS deductions on income, and bill-wise allocation when bill numbers are present.
Site supervisor pays a labourer or subcontractor from petty cash. Booked as a Journal voucher: DR receiver, CR sender — cost-centre tagged.
State-aware intra/inter classification, per-rate tax legs, automatic CGST + SGST / IGST split — driven by GSTINs, not Onsite’s per-kind tags.
Map each Onsite deduction to a Tally TDS module entry, plain ledger, or skip — your retention against subcon bills posts to the right liability ledger automatically.
New vendor or labourer in Onsite? The agent creates the ledger in Tally inline before posting the voucher — under the right group, with GSTIN tagged.
Tally stays on your premises. Always.
Your books never leave your network. The agent runs locally, polls our cloud over HTTPS for queued transactions, and posts them to Tally on localhost:9000. No port forwarding, no VPN, no Tally on the cloud.
Outbound-only agent. The on-prem agent makes outbound HTTPS calls to our cloud. It never opens an inbound port — your firewall configuration stays untouched.
Per-machine API keys. Each agent install gets a long-lived bearer key. Revoke a key from the dashboard the moment a machine is decommissioned.
Tally credentials never leave Tally. The agent uses Tally’s standard XML import on localhost:9000 — no Tally login is sent to our cloud.
Idempotent retries. Network glitch mid-push? The agent’s outbox replays the acknowledgement on next tick. Tally’s duplicate-voucher rejection makes the redelivery safe.
Auditable. Every push has a queue ID, a saved request envelope, and a Tally response — open the diagnostic file on any failed push to see exactly what was sent and what came back.
Cloud picks up approved records
localhost:9000 Tally
Live in under an hour. No code. No consultants.
Most clients go from “we just signed up” to “first voucher posted in Tally” in 30–45 minutes. Here’s the path.
Connect Onsite
Log in with your Onsite-registered mobile + OTP. We pull your party master, projects, deductions, bank accounts and GSTINs automatically.
~5 minInstall the agent
Download the Windows installer from your dashboard. Run on the machine running TallyPrime. Paste the agent key. The agent connects.
~5 minMap your ledgers
Searchable dropdowns let you map Onsite parties, expense types, GSTINs, taxes, TDS, retentions, cost centres, banks — all from your Tally chart of accounts.
~30 minPush your first voucher
Pick a transaction. Click Push. Open Tally → Day Book → see it land. Pre-flight checks catch any missing mappings before they reach Tally.
~2 minCommon questions, answered.
Yes — Silver, Gold, Server, Multi-User, and TallyPrime on Cloud (TPoC). The agent only needs HTTP access to localhost:9000. It works against any TallyPrime 2.x – 7.x installation. We’ve tested on fresh installs, multi-GSTIN setups, and Server editions with 50+ concurrent users.
The agent queues. As soon as Tally is open and reachable, it drains the queue. You don’t have to keep Tally running 24/7 — the cloud holds the queue patiently.
No. Every push carries an Onsite record id; the cloud refuses to re-enqueue an already-synced record. Tally itself rejects duplicate voucher numbers, which our agent classifies as “already posted” and acknowledges back as success.
You map each of your company’s GSTINs to its registration name in Tally (F11 → GST → Set/Alter GST Details). Each voucher carries a <GSTREGNUMBER> tag so the line lands on the correct state’s GSTR-1 — no manual filing reshuffles.
Yes. The Push page shows every fetched transaction with pre-flight warnings (missing mappings, unresolvable GST rates, etc.). Push individual records, batches, or everything — your call.
Each Onsite deduction maps to one of: Tally’s native TDS Module (with TDS section + nature of payment), a plain ledger credit, or “skip”. Retentions (purchase-side and subcon holdback) map the same way. Discounts split between purchase-side “Discount Received” (income) and sales-side “Discount Allowed” (expense) so your P&L stays clean.
Cloud: the dashboard you log into, the voucher build engine, all Onsite-side fetching, and the queue. On-prem: a tiny Python agent (~12 MB bundle, includes its own Python interpreter) that polls the cloud and POSTs to Tally locally.
No. The agent talks to Tally on localhost:9000 using Tally’s standard XML import gateway — no username or password is involved on Tally’s side, and nothing about your local Tally setup is shipped to our cloud.
Stop re-entering. Start integrating.
The Onsite × Tally integration is included on most Onsite plans. Set it up today and post your first voucher in under an hour.
No credit card required · Go live in under a day · Dedicated onboarding manager included