India Audit Lens
Pair, approve, and troubleshoot a Tally Bridge
Pair the approved Windows bridge service to the firm, keep the one-time token private, approve the device, review discovered Tally companies/entities and events, link only the correct clients, and revoke a…
By India Audit Lens product team · Updated 2026-07-17
Prepare the device
Confirm the Windows device is firm-managed or explicitly approved, patched, encrypted, and protected under the firm's endpoint policy. Verify Tally company access and identify the client/company mappings the bridge should serve. Ensure the operator can install/run the approved bridge service and understands the pairing token is a secret. Do not pair from a shared chat, screen recording, or public support session.
Start pairing
Navigate to Settings → Integrations → Tally Bridge. Confirm the page title Tally bridges. Click Pair new bridge. Enter a non-sensitive Bridge label, such as an approved device/office identifier; do not put a client PAN, password, or account number in the label. Continue to generate the pairing token/instructions. Copy the token directly into the approved bridge installer/service. Do not store or screenshot the token. Close the token step after the device reports pairing.
Approve the bridge
Return to the bridge detail and verify label, fingerprint prefix, deployment mode, and pending state through an independent device check. Click the approval action only for the exact expected device. Wait for Bridge activated. Refresh and verify online/last-seen state. Review Companies and wait for discovery/sync rather than creating duplicate bridges.
Link companies and entities
Open a discovered company and verify name, company identifier, financial period, and freshness against the approved client records. Use Link client to select the correct AuditLens client. In Entities, select only the data entities required for the approved scope. Save and verify the link/entity selection. Review edit history when a mapping changes.
One bridge may serve multiple companies/clients, but tenant and client separation still depends on correct mappings. Similar company names are not sufficient proof.
Review events and health
Open the bridge detail and click Refresh. Review last seen, device/agent information, discovered companies, sync/freshness, and recent events. Inspect failure/retry messages and edit history before re-pairing. Check the local service, network, Tally availability, and company permissions on the device.
Revoke a bridge
Confirm the device is lost, compromised, retired, or no longer authorised. Identify every client/company that depends on it and plan continuity. Click Revoke, enter the required reason, and confirm. Wait for Bridge revoked and verify it cannot resume syncing. Remove/disable the local service and rotate any related secrets under the deployment procedure.
Revocation is not a deletion of historical import evidence. Do not use it to conceal sync history.
Expected result
Only the approved device is active, companies are linked to the correct clients, entity scope is intentional, sync/events are reviewable, and retired/compromised bridges are revoked.