Custom TDL, from a Certified Tally Partner
TallyPrime, changed to fit how you work.
Reports, voucher fields, print formats and checks, written in-house in TDL, Tally's own language. Quoted per change.
We write our own TDL too: our eCommerce and Excel sync add-ons run this way.
A new field on a voucher or master
- What it involves
- We add it to the entry screen and store it with the voucher, so reports and printouts can use it.
- What we need from you
- The field's name and type, which vouchers need it, and whether it's required.
- Worth knowing
- Tally's own invoice templates have a Custom Fields option: up to two per section, and not on the item table. If that's enough, you won't need TDL.
Add a field, and see it on the invoice
A sample invoice. Tick what your business needs on it.
Entry screen
- Party
- Sample Traders
- Item
- Sample item, 10 nos
- Transporter
- Entered here
Printed invoice
- Bill to
- Sample Traders
- Amount
- Sample figure
- Transporter
- Printed here
Most upgrades are fine. Some break a TDL
Tick what's true for you, then see what each release changed.
6 of 6 still to sort out.
What changed, from Tally’s notes
- 7.2
- New Inscribed V2 TCPs load only on 7.2 and later. Older TCP formats still load.
- 7.1
- Customisations using the discount calculation may not work as expected.
- 7.0
- XML or JSON imports with AED or SAR must use entity codes.
- From Tally.ERP 9
- Compiled files should run. Custom buttons on default shortcut keys, old toolbar buttons and F12 Configuration settings don't carry over.
Read 5 Nov 2026. Latest release found: 7.2, 12 Oct 2026. Not a full list: Tally doesn't publish one.
Sometimes TDL isn't the answer
What do you need? We'd rather point you to the right thing.
TDL fits
This is what TDL is for. Pick the change at the top of this page.
From your request to a loaded TCP
Step through it. Nothing touches your live company until you've tested it.
Your change, your TallyPrime release and a sample of what you want.
Step 1 of 4
Quoted per change
- Request
- Asked
- Quote
- After the check
- Build
- After the build
- Live
- After loading
First, whether Tally already does it. If not, a fixed quote for this change, which also says who keeps the source.
Step 2 of 4
Quoted per change
- Request
- Scoped
- Quote
- Quoted in writing
- Build
- After the build
- Live
- After loading
We work on a copy of your company. You try it with your own data.
Step 3 of 4
Quoted per change
- Request
- Scoped
- Quote
- Quoted in writing
- Build
- Tested by you
- Live
- After loading
We build the TCP file and load it for your users, and tell you how to switch it off.
Step 4 of 4
Quoted per change
- Request
- Scoped
- Quote
- Quoted in writing
- Build
- Tested by you
- Live
- Live for your users
Questions about custom TDL
The one buyers ask most is answered first. Type to find the rest.