Invoice & document formats
Branded, bilingual invoice layouts that carry exactly the fields your customers and the Tax Authority expect — plus delivery notes, quotations, statements and LPOs in the same house style.
In-house TDL developers
When standard TallyPrime does ninety percent of what you need, the last ten percent is a customisation project — not a reason to change software.
The usual story runs like this: a business outgrows the standard invoice format, or needs an approval step before a purchase order goes out, or wants a report the built-in four hundred do not quite produce. Someone concludes Tally cannot do it and starts pricing an ERP replacement.
Almost always, it can do it. Tally exposes a proper extension language, TDL, and a business system that already holds your history and that your accountant already knows is worth extending rather than replacing. Replacement is the expensive answer to a question that usually has a cheap one.
The reason it gets recommended anyway is that most Tally resellers cannot write TDL. They can sell you a licence and install it. Development is a different capability, and it is the one we built the business on.
Customisation is written in Tally Definition Language and loaded alongside the standard product. Done properly, it extends behaviour through documented extension points rather than overwriting core code — which is precisely why a well-written customisation survives a version upgrade and a badly written one does not.
That distinction is why some businesses are stranded on an old TallyPrime release, unable to update because an inherited customisation would break. It is a fixable position, and usually cheaper to fix than to live with.

Branded, bilingual invoice layouts that carry exactly the fields your customers and the Tax Authority expect — plus delivery notes, quotations, statements and LPOs in the same house style.
The report your management actually asks for every month, built once and available on demand: margin by salesperson, ageing by project, stock movement by branch, commission calculations.
Controls Tally does not enforce by default — credit limit blocks, purchase order approval thresholds, discount authorisation, restrictions on editing posted vouchers.
Vehicle numbers on delivery notes, project codes on expenses, warranty dates on stock items, serial tracking on serialised goods — captured in Tally rather than a side spreadsheet.
Sector-specific behaviour built onto standard Tally: contracting retention and progress billing, trading multi-currency landed costs, restaurant recipe consumption, workshop job cards.
Two-way data flow with e-commerce platforms, POS terminals, payroll and attendance systems, banking files and custom applications, so nothing is keyed in twice.
Customisation goes wrong when nobody agreed what "done" means. We settle that first.
We watch the process as it runs today and write down exactly what the customisation must do, including the edge cases people forget.
A written scope with a fixed price and timeline. If we think the requirement can be met by standard Tally configuration instead, we say so.
Developed against a copy of your data, then tested with your team on real scenarios before it goes near your live company.
Installed, documented, your team trained on it, and the TDL source handed to you. You own what you paid for.
Inherited a customisation you cannot maintain? Bring it to us. We will read the TDL, document what it does, and tell you plainly whether it is worth keeping or cheaper to rewrite. Being locked to a vendor because nobody else can read the code is not an acceptable position for your business to be in. Ask for a code review.
Tell us what Tally will not do today and what you need instead. We come back with a written scope, a fixed price and a timeline — or an honest note that standard configuration can already handle it.
TDL — Tally Definition Language — is the programming language Tally exposes for extending the product. It is how custom invoice formats, extra reports, new data fields, validation rules and integrations get built. TDL customisations sit on top of standard Tally, so the underlying product keeps behaving normally and keeps receiving updates.
Not if it is written properly. Well-built TDL uses documented extension points rather than overwriting core behaviour, so it survives version upgrades. Poorly written customisation — and we see plenty inherited from other vendors — does break, which is why some businesses are stuck on old TallyPrime versions and afraid to update. We can usually rewrite those cleanly.
Yes, and it is a common request. We review the existing TDL, document what it does, tell you honestly whether it is worth keeping or rewriting, and take on maintenance either way. You should not be locked to a vendor because nobody else can read the code.
Yes. Tally can exchange data with external systems through XML and its integration interfaces. Typical projects push e-commerce or POS sales into Tally as vouchers, pull stock and price data out to a website, or sync payroll and attendance from a separate system. As a Tally Integrator this is core work for us rather than an outsourced extra.
A custom invoice or report format is usually a few days. A departmental approval workflow or an industry module runs two to six weeks. A full system integration depends mostly on the other system's interface. Every project gets a written scope, a fixed price and a timeline before any code is written.
Yes. You own the deliverable and you get the TDL source. We hold no hostage code. If you ever move to another partner, everything needed to maintain what we built goes with you.
Yes. Bilingual Arabic and English invoice formats are one of the most common customisations we build in Oman, and we test the layout on your actual printer before go-live - Arabic rendering on thermal and dot-matrix printers is where these usually go wrong. The format carries exactly the fields your customers and the Tax Authority expect.
It depends on scope, and we quote a fixed price before any code is written. As a rough guide: a custom invoice or report format is a few days of work, a departmental approval workflow or an industry module runs two to six weeks, and a full system integration depends mostly on the other system's interface. We will also tell you when standard Tally configuration can meet the requirement at no development cost.
Yes. Tally exchanges data with external systems through XML and its integration interfaces. Typical projects push online orders into Tally as sales vouchers and pull stock levels and prices out to the website, so the shop is not selling what the warehouse no longer has. As a Tally Integrator this is in-house work for us.
Customisation requires TDL development skill, which is a different capability from reselling licences - most Tally resellers in Oman can sell and install, but not develop. Ample Technology holds Tally Integrator status alongside Gold Partner and has in-house TDL developers. If a supplier tells you Tally cannot do something, it is worth getting a second opinion from someone who can write TDL.
No. You receive the TDL source for everything we build, so another developer can pick it up. We also take over customisations written by other vendors - we read the existing code, document what it does, and tell you honestly whether it is worth keeping or cheaper to rewrite.
Most 'Tally cannot do this' problems turn out to be a few days of TDL work. A short conversation will tell you which kind you have.