Skip to main content
Use the @bijection/connectors/tally entrypoint to declare TallyPrime / Tally.ERP 9 resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Ledger masters

​
pull: AlterID windows up to the company’s AltMstId, carried between passes

The following example matches configuration standard.

​
Configuration: standard

Case: tally/ledgers/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: tally. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: ledgers
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Vouchers

​
pull: AlterID windows up to the company’s AltVchId, carried between passes

The following example matches configuration standard.

​
Configuration: standard

Case: tally/vouchers/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: tally. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: vouchers
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Reads Tally’s XML server: Tally running as a server (HTTP server or “TallyPrime acts as Server/Both”, port 9000 by default) with the company loaded. Setup baseUrl is http://<tally-host>:9000/. Security: Tally has no TLS and no authentication. Anyone who reaches the port can export every loaded company and import (post) vouchers and masters. This recipe therefore requires a network relay route: the connection’s typed setup carries network: { relay: "<group>", target: "<name>" }, the base URL’s host and port equal that relay target’s, and plain http:// is admitted only on a relay route. The leg from the relay to Tally is cleartext on the customer’s network, so every ledger and voucher crosses it unencrypted. The customer must bind Tally’s port to, or firewall it so it accepts connections only from, the relay host (or run the relay on the Tally machine and reach it by loopback); a Tally port open to a wider network is open to every host on it. Never expose it publicly. The platform requires a credential envelope on every HTTP-contract connection, and Tally checks none: bind an api_key envelope (placement: "header", a name Tally ignores such as x-bijection-tally, any value) whose allowed_resource_origins names the Tally origin. It confines where requests go and authenticates nothing. Each request POSTs one text/xml export envelope declaring a TDL collection with ISINITIALIZE="Yes" and only the methods read, for company (SVCURRENTCOMPANY; omitted, Tally’s current company). Answers are UTF-8 XML decoded by the host (at most 4,096 elements per answer). A STATUS other than 1 fails the page. Every pass first reads the company’s last alteration id ($AltMstId for ledgers, $AltVchId for vouchers), then reads the objects with $AlterID > lo AND $AlterID <= lo + window up to it (window 300 ledgers or 200 vouchers). An object’s current alteration id is unique, so a window is bounded; an object altered mid-pass moves above the walk and is read later, so none is skipped. The next pass starts above the bound this one reached, reading only altered objects; a lower bound (a restored or rewritten company) restarts from zero. Tally’s own reference documents MasterID and $CmpVchID but not AlterID, AltMstId or AltVchId; they are what Tally integrations commonly use, and this recipe depends on them. Records are keyed by GUID; the version is the ALTERID text exactly as Tally writes it (Tally may pad numbers with a space). ledgers publishes the NAME attribute, MASTERID, ALTERID, PARENT, OPENINGBALANCE and CLOSINGBALANCE; vouchers publishes DATE, VOUCHERTYPENAME, VOUCHERNUMBER, PARTYLEDGERNAME, AMOUNT and NARRATION over period (SVFROMDATE/SVTODATE, default 19000101 to 20991231). methods adds scalar native methods. Values stay Tally’s text: amounts as written (negative is a debit), dates YYYYMMDD. Deletions are not observed: a deleted object leaves no row and absence withdraws nothing. Tally sometimes writes character references XML 1.0 forbids; such an answer fails rather than being repaired. Nothing is written to Tally. Nothing here has run against Tally or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.