Relay reads Tally XML exports and turns their vouchers into Channel documents. It is an operator tool, not a live connector. You create a grant that says which Tally company and which seller it covers, paste an export into the Exchange tab, supply the mapping from party ledgers to network members and from stock items to SKUs, and load it. Each load is saved as a run, with retries and a safety net for repeated failures. The workspace has five tabs: Overview, Grants, Exchange, Delivery history and Delivery health.
01
Tally voucher ingestion
AvailableTurn a Tally XML export into sales documents in Channel. Loading the same export twice duplicates nothing, and problems are reported rather than dropped.
The loader reads each voucher and maps it to a Channel document type. Party ledgers and stock items must be mapped to network members and SKUs; anything unmapped, malformed or of an unknown voucher type is reported as an exception rather than dropped. Amounts are read exactly and stored as positive values, because Tally signs amounts by ledger convention. Loading is safe to repeat, so the same export can be sent twice.
- Voucher types read: Sales, Purchase, Credit Note, Debit Note, Receipt
- Exception types: malformed voucher, unknown voucher type, missing ledger, unmapped party
- A batch is all or nothing, and two identical batches sent at the same time load once
- Exports up to 5,000,000 characters per batch
Where to find it: Relay workspace, Exchange tab
02
Grants and saved runs
AvailableLoading is allowed only under an active grant, and every batch is a run that can be retried or set aside.
A grant names a source system, a source company and the seller it covers, at primary or secondary level. Loading is refused without a matching active grant. Each batch is saved as a run with its inputs, so a failed run can be retried. After three failed attempts a run is set aside, and the source data must be corrected and sent again. Revoking a grant needs a reason.
- A run is set aside after 3 failed attempts; a set-aside run cannot be retried
- A retried run whose grant was revoked is refused
- The seller must match the grant's scope
Where to find it: Relay workspace, Grants and Delivery history tabs
03
Delivery-health monitoring
AvailableA seven-day view for each grant: freshness, failures and exception volume.
The Delivery health tab reports, for each grant, the hours since the last completed run, the number of failed and set-aside runs, documents loaded against duplicates, and the volume of record-level exceptions.
- Seven-day window for each grant
- Hours since the last completed run shows how fresh the data is
Where to find it: Relay workspace, Delivery health tab
04
Master-data mapping
RoadmapMapping with suggestions and approval is planned only. Today mappings are typed in for each batch.
In the Exchange tab the party-ledger and stock-item mappings are typed as comma-separated pairs for each batch. There is no mapping screen, saved mapping or approval step.
- Planned only
- Mappings are entered for each batch
05
Busy adapter
RoadmapThere is no working Busy adapter.
A grant can be created for Busy, but loading needs an active Tally grant, so nothing is loaded for Busy. Only the interface and test data exist.
- Planned only
- A Busy grant can be created; it cannot load data
06
Data-quality scoring and reconciliation
RoadmapA combined data-quality score and automatic reconciliation matching are not built.
Run history, set-aside runs and delivery health are available. A combined score and automatic matching are planned only.