The challenge
Transaction batch files arriving in the institution's own XML format had to be manually re-entered into Tally, including creating ledger masters for every new party.
What we built
Our converter reads each batch XML, applies a configurable mapping, and generates Tally-compatible import files for both ledger masters and transactions - an entire batch lands in Tally in one import, named and classified correctly. Master creation and transaction posting run as separate steps, so a batch containing parties Tally has never seen loads safely in the right order, and the entire mapping lives in a configuration file the institution's own team can edit without any rebuild on our side. Payment details - mode, reference, date, bank and invoice amount - are now matched to each voucher by membership number and written automatically into Tally's add-on fields, removing what had been a manual keying step for every transaction. A re-run no longer risks a double posting either: the converter reads the list of vouchers already present in the client's Tally company, kept as a single master list beside the program, and holds back any order it has imported before, writing those to a separate file for review, with every run leaving a permanent record of what was suppressed.
The result
Before: manual re-entry of every batch. Now: one import per batch.