How it fits together

The four parts of Balancely, and what happens when a workflow runs.

The pieces

Application
Lives in: Your automation platform

What a platform signs in as: Client ID, Client Secret, redirect URLs and the permissions it may ask for.

Authorization
Lives in: Balancely

One application allowed to use one connection, with a set of permissions. Revoke it to stop that application at once.

Connection
Lives in: Balancely

One TallyPrime company on one computer you have paired. Every action works on this company.

Connector
Lives in: The computer with TallyPrime

A small Windows app. It only carries requests to TallyPrime.

Applications and connections are separate on purpose
You can cut off one platform without disconnecting TallyPrime. And the other way round.

What happens when a workflow runs

  • Your platform calls us

    It sends the step data to our API with its access token.

  • We work out who is calling

    The token tells us the application, the connection and its permissions.

  • We check before we write

    We check that ledgers, stock items, godowns and bill references exist in your company. We also check that the entry balances.

  • We build the entry

    The request becomes a TallyPrime voucher.

  • The connector delivers it

    The connector saves it in TallyPrime on your computer.

  • We confirm it landed

    We check that the entry is really in TallyPrime. Our reply shows what was saved.

Why nothing has to be opened on your network

You do not need port forwarding, a static IP, a firewall rule or a VPN.

What makes an automated entry safe

Every write is verified

We check that the entry is really in TallyPrime. Our reply shows what was saved.

A retry never doubles an invoice

If a step is sent again, it updates the same record. It never makes a second one. Send an Idempotency-Key header to control it yourself.

Checks happen before anything is written

We first check that every ledger, item, godown and bill in a request exists. So you get “the ledger X does not exist”, not a bare rejection.

Permissions

ScopeWhat it allows
tally.readRead ledgers, stock items, outstanding bills and transactions from the connected company.
tally.writeCreate invoices, payments, notes, journals and ledgers in the connected company.
connection.readSee which company and computer this connection points at.

The person who approves an application sees these exact sentences. Anything else is refused with forbidden.

Something missing on this page? Tell us and we will fix it.