How to Set Up and Use Tally Integration in Onsite
How to set up the Onsite-Tally integration and push transactions from Onsite directly into Tally as vouchers. This covers the one-time setup (connection, agent installation, ledger mapping, party mapping, cost centre mapping, and bank mapping), and the daily workflow for pushing records to Tally.
What the Integration Does
Onsite’s Tally integration pushes approved transactions from Onsite into Tally as vouchers automatically. This eliminates double data entry between Onsite and your accounting software.
Transactions pushed from Onsite appear in Tally’s Day Book with the party name, amount, project reference, and narration details.
Before You Start
- You need Admin access in Onsite
- Tally must be installed and open on the machine that will act as the agent
- Have your Tally company name ready — it must be entered exactly as it appears in Tally (case sensitive)
- All Onsite bank accounts should be configured in Settings before mapping banks to Tally ledgers
- Decide the Sync Window start date — this is the earliest transaction date that will be available to push. Set it to your financial year start to include all records from that date.
Transaction Types Supported
| Onsite Transaction | Tally Voucher Type |
|---|---|
| Sales Invoice | Sales |
| Material Sales | Sales |
| Material Purchase | Purchase |
| Subcontractor Expense | Purchase |
| Equipment Expense | Purchase |
| Other Expense | Purchase |
| Site Expense | Purchase |
| Payment In | Payment |
| Payment Out | Payment |
| Party to Party Payment | Journal |
Accessing the Tally Integration
Open your Tally integration page in a browser:
sync.onsiteteams.com/tally/your-username
Replace “your-username” with your Onsite account username.
The page shows tabs for each transaction type: Sales Invoices, Material Sales, Material Purchases, Subcon Expenses, Equipment Expenses, Other Expenses, Site Expenses, Payments In, Payments Out, and P2P Payments.
Top toolbar buttons:
| Button | What It Does |
|---|---|
| Fetch from Onsite | Refreshes the list with the latest transactions from Onsite |
| Refresh Integration Checks | Re-validates all mappings (parties, ledgers, banks) |
| Push Selected to Tally | Pushes all checked records to Tally via the agent |
| Download Report | Exports the current tab view as a file |
Part 1: One-Time Setup: Connection
Go to Tally Settings (top right of the integration page).
Click the Connection tab.
| Field | What to Enter |
|---|---|
| Onsite Authentication | Your registered mobile number. Click Save OTP after verifying. |
| Sync Window — Fetch records from | The earliest date you want to sync. Set this to the start of your financial year (e.g. 1 April 2025) to include all records from that date. |
| Tally Company Name | Enter the company name exactly as it appears in Tally, including spaces and capitalisation. |
| Voucher Number Template | The format for auto-numbering vouchers pushed to Tally (e.g. ONS-{year}-{number}). |
Click Save.
⚠️ The authentication token occasionally expires. If records stop syncing, return to Connection and re-verify your mobile number.
Part 2: One-Time Setup: Tally Agent
The Tally Agent is a small program that runs on the computer where Tally is installed. It receives push requests from Onsite and posts them into Tally. The agent must be running for any push to work.
Installing the Agent
- Click Download Agent (Windows .zip) and install it on the machine running Tally
- In the Register a New Agent section, enter a machine label (e.g. “Office-PC” or “Accountant Laptop”)
- Click Generate Key
- Copy the key and paste it into the agent installer on the Tally machine
- The agent appears in Registered Agents with status Active
💡 Only one active agent per machine is needed. The agent must be running in the background whenever you push records to Tally. If the machine is off or the agent is closed, records will queue but not post.
⚠️ If the agent shows Revoked, generate a new key in Tally Settings under Agents and reconfigure the agent on the machine.
Part 3: One-Time Setup: Voucher Type and Ledger Mapping
Click the Accounts tab in Tally Settings.
For each Onsite transaction type, map it to the correct Tally Voucher Type and Ledger.
| Onsite Expense Type | Mode | Voucher Type | Example Ledger |
|---|---|---|---|
| Material Purchase | Itemwise | Purchase | Purchase — Materials |
| Subcontractor Expense | Lumpsum | Purchase | Subcontractor Charges |
| Equipment Expense | Lumpsum | Purchase | Purchase — Materials |
| Other Expense | Lumpsum | Purchase | Purchase — Materials |
| Site Expense | Lumpsum | Purchase | Purchase — Materials |
| Sales Invoice | Lumpsum | Sales | Sales — Services |
| Material Sales | Lumpsum | Sales | Sales — Services |
| Payment In | — | Payment | Bank or Cash ledger |
| Payment Out | — | Payment | Bank or Cash ledger |
| P2P Payment | — | Journal | Cash |
Mode controls how items are posted in Tally:
| Mode | What It Does |
|---|---|
| Itemwise | Each material line item is posted separately in the Tally voucher (used for Material Purchase to maintain stock ledger accuracy) |
| Lumpsum | The entire transaction is posted as a single line in the Tally voucher |
Additional settings on the Accounts tab:
| Setting | What to Configure |
|---|---|
| Round off account | The ledger used for rounding differences (e.g. Round Off Account) |
| Default cash ledger | The ledger used for payments where no bank account is mapped |
| Auto-create missing ledgers | When ON, Onsite creates new ledgers in Tally automatically for unmapped items. Use carefully — it can create duplicate ledgers if naming is inconsistent in Tally. |
| Helper Ledgers | Map freight, additional charges, or other surcharges for purchase and sales vouchers |
Click Save Accounts when done.
Part 4: One-Time Setup: Party Mapping
Click the Parties tab in Tally Settings.
All Onsite parties (vendors, clients, subcontractors) are listed here. Each must be mapped to the corresponding ledger in Tally before records involving that party can be pushed.
Step 1: Auto Match
Click Auto match by exact name.
Onsite will attempt to match parties with the same name in Tally automatically.
Step 2: Manual Match Remaining Parties
For any parties that were not matched automatically (names differ between Onsite and Tally), select the correct Tally ledger from the dropdown next to each party.
Step3: Save
Click Save Parties.
⚠️ Unmapped parties block the push. If a party is not mapped when you push, Onsite shows a warning. You can choose to auto-create the ledger in Tally or map the party first and retry.
💡 Run Refresh Integration Checks after adding any new party in Onsite or Tally to detect new unmapped parties before they cause a push failure.
Part 5: One-Time Setup: Cost Centres
Click the Cost Centres tab in Tally Settings.
Cost centres allow project-wise expense tracking in Tally. Each Onsite project is mapped to a Tally Cost Centre.
- Enable the Tag vouchers with Cost Centres (per-project) toggle
- For each Onsite project, select the corresponding Tally Cost Centre from the dropdown
- Click Save Cost Centres
⚠️ If cost centre mapping is not configured, vouchers are posted to Tally without any project tag. Even if your Tally company has cost centres enabled, they will not be applied unless this mapping is completed.
Part 6: One-Time Setup: Banks and Cash
Click the Banks and Cash tab in Tally Settings.
Each Onsite bank account is listed. Map each to the corresponding ledger in Tally.
- Find the bank account (e.g. HDFC Bank — A/c: 1234567890)
- Select the matching Tally bank ledger from the dropdown
- Click Save Banks
💡 If a payment record has no bank account linked, it posts to the Default cash ledger configured in the Accounts section. Ensure the default cash ledger is set correctly before pushing any payment records.
Part 7: Pushing Records to Tally (Daily Workflow)
Once setup is complete, follow this process each time you want to push transactions:
Step 1: Fetch Latest Records
Click Fetch from Onsite to load the latest approved transactions.
Step 2: Review Records
Each tab shows the following columns for each transaction:
| Column | What It Shows |
|---|---|
| Date | Transaction date in Onsite |
| Onsite Ref | Onsite reference number (e.g. INV-25-001) |
| Party | Vendor or client name |
| Project | Project the transaction belongs to |
| GST | GST amount |
| Amount | Total transaction amount |
| Status | Pending (not yet pushed) or Synced (already in Tally) |
Step 3: Select and Push
Tick the checkboxes next to the records you want to push. Click Select All to push everything in the current tab.
Click Push Selected to Tally.
A results dialog appears for each record:
| Result | Meaning | What to Do |
|---|---|---|
| Queued | Record sent to the agent and will appear in Tally shortly | Wait a moment and check Tally’s Day Book |
| Warning | Party not mapped — will be auto-created in Tally if auto-create is on | Review the auto-created ledger in Tally for accuracy |
| Failed | Push failed | Check party mapping, ledger mapping, and agent status. Fix the issue and retry. |
Step 4: Verify in Tally
Open Tally and go to Day Book. Each pushed record appears with the party name, amount, and narration containing the Onsite project and reference details.
Tips
- Set the Sync Window date to your financial year start during initial setup. This makes all records from that date available to push. It cannot be moved backward later without re-verification.
- Run Refresh Integration Checks any time a new party, project, or bank account is added in either Onsite or Tally. This detects new unmapped items before they block a push.
- Use Auto-create missing ledgers carefully. It is helpful for keeping pushes moving but creates ledgers automatically in Tally. If Onsite party names differ from Tally ledger names, auto-create may add duplicates.
- The agent must be running on the Tally machine at the time of push. Records stay in Queued state until the agent comes online. If records stay Queued for more than a few minutes, check that Tally is open and the agent is active.
- Push records regularly rather than accumulating weeks of backlog. Large batches take longer and make it harder to investigate individual push failures.
- Material Purchase uses Itemwise mode. This posts each material line item separately in Tally, which is important for maintaining accurate stock ledger entries. All other expense types use Lumpsum mode.
If Something Goes Wrong
| Problem | Likely Cause | What to Do |
|---|---|---|
| Records not appearing in Tally after push | Agent not running on the Tally machine | Check the agent status in Tally Settings, Agents. Restart the agent if needed. |
| Party not mapped warning on push | Party not in the Parties mapping list | Go to Tally Settings, Parties, find the party, map it to the correct Tally ledger, and retry the push |
| Authentication or OTP expired | Session token has expired | Go to Tally Settings, Connection, and re-verify your mobile number |
| Wrong voucher type posted in Tally | Incorrect mapping in Accounts settings | Go to Tally Settings, Accounts, correct the voucher type for that transaction type, and re-push |
| Agent shows Revoked | Agent key was deactivated | Generate a new key in Tally Settings, Agents, and reconfigure the agent on the Tally machine |
| Cost centre not appearing on vouchers in Tally | Cost centre mapping not configured or toggle not enabled | Go to Tally Settings, Cost Centres, enable the toggle, map all projects, and save |
| Duplicate ledgers being created in Tally | Auto-create is ON and party names differ between Onsite and Tally | Turn off Auto-create in Accounts settings. Map parties manually in the Parties tab. Delete duplicates from Tally. |
| Records stay Queued and never post | Tally is closed or agent is inactive | Open Tally on the agent machine and ensure the agent program is running |