Exercise 9

Sales Vouchers With Multiple Items

Published 3 Oct 2026

---

This exercise imports Sales Invoices that carry several stock items. Rows sharing the same Invoice No. become one voucher with one stock item line per row. It builds on the previous exercise, using SCROLL to group the rows, and Sum(Column(...)) to post the invoice total to the Party Ledger.

The Excel sheet

---

Step 1 — Create the masters

The voucher refers to four masters: the Party Ledger (Column C), the Sales Ledger (Column D), the Unit (Column G) and the Stock Item (Column E). udiMagic processes MASTER tags before VOUCHER tags, so anything that doesn't exist yet in Tally is created in the same import. The UNIT master must come before the STOCKITEM, because the Stock Item uses the Unit as its base unit.

<!-- Create Party LEDGER Master (Column C) -->
<MASTER TYPE="LEDGER">
  <NAME.LIST>
    <NAME COLUMNREFERENCE="C"/>
  </NAME.LIST>
  <!-- Group is hard coded -->
  <PARENT>Sundry Debtors</PARENT>
  <ISBILLWISEON>Yes</ISBILLWISEON>
  <AFFECTSSTOCK>No</AFFECTSSTOCK>
  <ISCOSTCENTRESON>No</ISCOSTCENTRESON>
</MASTER>

<!-- Create Sales LEDGER Master (Column D) -->
<MASTER TYPE="LEDGER">
  <NAME.LIST>
    <NAME COLUMNREFERENCE="D"/>
  </NAME.LIST>
  <PARENT>Sales Accounts</PARENT>
  <ISBILLWISEON>No</ISBILLWISEON>
  <ISCOSTCENTRESON>No</ISCOSTCENTRESON>
  <!-- Yes, because this ledger is used with Stock Items -->
  <AFFECTSSTOCK>Yes</AFFECTSSTOCK>
  <USEFORVAT>No</USEFORVAT>
</MASTER>

<!-- Create UNIT Master (Column G). Must come before the StockItem. -->
<MASTER TYPE="UNIT">
  <!-- The UNIT Master does not support Aliases : use NAME directly -->
  <NAME COLUMNREFERENCE="G"/>
  <ISSIMPLEUNIT>Yes</ISSIMPLEUNIT>
</MASTER>

<!-- Create STOCKITEM Master (Column E) -->
<MASTER TYPE="STOCKITEM">
  <NAME.LIST>
    <NAME COLUMNREFERENCE="E"/>
  </NAME.LIST>
  <!-- Empty PARENT = no Stock Group (udiMagic default) -->
  <PARENT/>
  <BASEUNITS COLUMNREFERENCE="G"/>
</MASTER>

Step 2 — Declare the key column and scroll the stock items

CELLREFERENCE="A1" on XMLTAGS declares Column A (Invoice No.) as the key field. SCROLL="YES" on ALLINVENTORYENTRIES.LIST then tells udiMagic to keep adding one stock-item block for every following row that carries the same Invoice No. (see udiMagic XML tags).

<XMLTAGS xmlns:UDF="TallyUDF" CELLREFERENCE="A1">
...
<ALLINVENTORYENTRIES.LIST SCROLL="YES">

Invoice No.	Excel rows	Stock item lines in the voucher
11077	2–4	3 (Silk Thread, Cotton Fabric, Embroidery Needle)
11078	5	1
11079	6–7	2 (Silk Thread, Cotton Fabric)
11080	8	1
11081	9	1

Step 3 — Write the Voucher tags

The Party Ledger is debited under LEDGERENTRIES.LIST with the total of all item amounts of the invoice (Round(Sum(Column(I#)),2)*-1), both in the ledger entry and in its bill allocation. Each scrolled stock-item block carries the Stock Item, Qty, Rate and Amount of its own row, and credits the Sales Ledger through its ACCOUNTINGALLOCATIONS.LIST. To see the exact structure Tally uses, enter one sample invoice and export it from Gateway of Tally >> Display >> Daybook >> Alt+E.

<!-- VOUCHER : one invoice can contain multiple stock-item rows -->
<VOUCHER>
  <!-- Unique voucher ID from Invoice No. (Column A) -->
  <GUID FORMULA="=+&quot;udi-MLKIYT&quot; &amp; A#"/>
  <DATE COLUMNREFERENCE="B"/>
  <EFFECTIVEDATE COLUMNREFERENCE="B"/>
  <VOUCHERTYPENAME>Sales</VOUCHERTYPENAME>
  <VOUCHERNUMBER COLUMNREFERENCE="A"/>
  <!-- Narration mapped directly from Column J -->
  <NARRATION COLUMNREFERENCE="J"/>
  <ISINVOICE>Yes</ISINVOICE>
  <PERSISTEDVIEW>Invoice Voucher View</PERSISTEDVIEW>

  <!-- Party (Client) from Column C -->
  <PARTYNAME COLUMNREFERENCE="C"/>
  <PARTYLEDGERNAME COLUMNREFERENCE="C"/>
  <BASICBASEPARTYNAME COLUMNREFERENCE="C"/>
  <BASICBUYERNAME COLUMNREFERENCE="C"/>

  <!-- Party Ledger : Debit = total of all item amounts for the invoice -->
  <LEDGERENTRIES.LIST>
    <LEDGERNAME COLUMNREFERENCE="C"/>
    <ISDEEMEDPOSITIVE>Yes</ISDEEMEDPOSITIVE>
    <AMOUNT FORMULA="=+Round(Sum(Column(I#)),2)*-1"/>
    <BILLALLOCATIONS.LIST SKIP="=Len(trim(A#))=0">
      <NAME COLUMNREFERENCE="A"/>
      <BILLTYPE>New Ref</BILLTYPE>
      <AMOUNT FORMULA="=+Round(Sum(Column(I#)),2)*-1"/>
    </BILLALLOCATIONS.LIST>
  </LEDGERENTRIES.LIST>

  <!--
    Stock-item rows are scrolled according to Invoice No. in Column A.
    Therefore:
      Invoice 11077 -> 3 item rows
      Invoice 11079 -> 2 item rows
    while invoices with one row remain one-item vouchers.
  -->
  <ALLINVENTORYENTRIES.LIST SCROLL="YES">
    <STOCKITEMNAME COLUMNREFERENCE="E"/>
    <ISDEEMEDPOSITIVE>No</ISDEEMEDPOSITIVE>
    <RATE COLUMNREFERENCE="H"/>
    <AMOUNT COLUMNREFERENCE="I"/>
    <ACTUALQTY COLUMNREFERENCE="F"/>
    <BILLEDQTY COLUMNREFERENCE="F"/>
    <!-- Sales Ledger from Column D -->
    <ACCOUNTINGALLOCATIONS.LIST>
      <LEDGERNAME COLUMNREFERENCE="D"/>
      <ISDEEMEDPOSITIVE>No</ISDEEMEDPOSITIVE>
      <AMOUNT COLUMNREFERENCE="I"/>
    </ACCOUNTINGALLOCATIONS.LIST>
    <!-- Existing inventory/godown structure retained -->
    <BATCHALLOCATIONS.LIST>
      <GODOWNNAME>Main Location</GODOWNNAME>
      <BATCHNAME>Primary Batch</BATCHNAME>
      <DESTINATIONGODOWNNAME>Main Location</DESTINATIONGODOWNNAME>
      <AMOUNT COLUMNREFERENCE="I"/>
      <ACTUALQTY COLUMNREFERENCE="F"/>
      <BILLEDQTY COLUMNREFERENCE="F"/>
    </BATCHALLOCATIONS.LIST>
  </ALLINVENTORYENTRIES.LIST>
</VOUCHER>

---