Add the Buyer Name to the Delivery Challan Register in TallyPrime

Here is a small thing that wastes a surprising amount of time.

A customer calls and says a delivery is missing. You open the Delivery Challan Register in TallyPrime to find the challan. The register shows you challan numbers and dates. It does not show you who each challan went to.

So you open one. Wrong party. Escape. Open the next. Wrong party. Escape. Open the next.

If you issue ten challans a day, finding last Tuesday’s challan for a particular customer means opening challans one at a time until you hit the right one, while the customer waits on the phone.

Why the register works this way

The Delivery Challan Register is a voucher register. It lists vouchers of that type in date order, and its default columns describe the voucher itself rather than the party it was raised against.

The party name is not missing from your data. It is on the challan. It is simply not one of the columns the register displays, and TallyPrime does not offer it as a standard column option in that register.

What we change

The customisation adds the buyer name, the ledger name the challan was raised against, as a column in the Delivery Challan Register.

That single column changes how the register is used. Instead of a chronological list you have to open one by one, you get a register you can scan, sort, and filter by customer. Finding a challan becomes a five second job rather than a five minute one.

Because the buyer name is now on the register itself, you can also do things that were awkward before:

• See at a glance every challan raised for one party in a period
• Spot challans raised to the wrong party before they become invoices
• Hand the register to someone who does not know your challan numbering and have them still find what they need

The video above shows the column in place on a live company.

The wider point about registers

We mention this one often when people ask what TDL customisation is good for, because it is so ordinary. Nobody would describe a missing column as a business crisis. It is the kind of thing you work around for years without ever raising it, because it feels too small to complain about.

But the workaround has a cost, paid daily, by whoever happens to be answering the phone. Most of the customisation work we do is exactly this shape: not reinventing your accounting, just putting the information you already have where the person using it can see it.

If there is a report in your Tally that you always export to Excel before it becomes useful, that is usually a sign the same kind of fix is available.

Worth checking first

Before asking for this, look at how your challans are actually raised. If your team enters the buyer as a plain narration rather than selecting a party ledger, the name is not in a field the register can display, and the fix starts with how the voucher is entered rather than how the register is drawn.

That is the sort of thing we check before quoting, because it changes the answer.

Talk to us

We are a Tally 3 Star Partner in Himmatnagar and TDL customisation is our core work. If your Delivery Challan Register is costing your team time, it is a small job to fix.