Reconciliation mappings for parties and ledger heads
Map a deductor's TAN or a vendor's other GSTIN to the party ledger in the books, and tell the app which books ledgers are TDS receivable, GST input, sales and so on, for one client or as firm defaults.
Books name parties and ledgers in their own words. Mappings tell the reconciliation how to read them. Everyone can see mappings; managers, partners and the owner change them. A saved mapping is used by the next run.
Party mappings (per client)
Choose a client, then Add a party mapping:
- A deductor's TAN to a party ledger: for AIS, TIS and 26AS against the books (R4).
- Another GSTIN of a vendor to its ledger: when a vendor bills from a GSTIN the books do not hold.
Give the Party ledger (as in the books), and a Payment nature when the deductor deducts
under several sections (for example professional fees or rent), written in lower case with
underscores, such as professional_fees.
Ledger heads
Ledger head rules say what a ledger is: TDS receivable, GST input (IGST, CGST, SGST or cess), RCM payable, interest income, rent income, professional receipts, sales, purchases, a blocked-credit review head, or other. Match on the ledger name, its group or its primary group, and give the Name in the books. Rules can be set for one client or as firm defaults for every client.
Suggestions from an R4 run
Opened from an R4 run, the page lists Ledgers with TDS whose deductor is not mapped, with the TDS in the books and the closest deductor in Form 26AS. Map it opens a party mapping filled with the ledger and the suggested TAN for you to check and save.
Example
A synthetic client's books hold a ledger "Rent received - Shop 2" with TDS. The R4 run suggests
the closest deductor (TAN shown masked). You add a party mapping from that TAN to the ledger with
payment nature rent.
Last reviewed 27 October 2026