Project and billing references in Tally reports
Tally & TDL Development for Bengaluru Businesses
For service businesses reconciling customer invoices and receipts against project or contract references held elsewhere.
Tally & TDL customisation · Bengaluru
Project and billing references in Tally reports
Check native references and reporting first. If necessary, scope one TDL field or report that makes an agreed project identifier visible without replacing your accounting controls. Compatibility is assessed against your installed release and add-ons.
What we scope together
- A reference-field specification and a sample project-wise report.
- Acceptance cases for missing references, amended records and receipt allocation.
What affects cost: Existing reference quality, report grouping, historical backfill and testing across installed add-ons.
From review to handover
How the Tally & TDL customisation pilot works.
Check the installed setup
Review your TallyPrime release, licence, company structure, reports and installed add-ons. Try the native reporting or configuration route before specifying TDL.
Specify one change
Agree the field, report or document layout and its source data. Record the expected result for a normal record, a missing reference and an amended record.
Test and control the release
Test the agreed change in an authorised test company with your installed add-ons. Document the installation, backup, rollback and acceptance steps before a production release.
Before the review
What to prepare.
- The exact TallyPrime release and a list of installed TDLs or add-ons.
- A redacted current report or document and an annotated example of the output you need.
- Sample vouchers or references showing a normal record and a correction, plus the report owner.
Remove identifying customer, staff and financial details from initial samples. We agree authorised access and the test environment separately.
Cost and timing
Start with one agreed outcome.
A diagnostic typically takes 2–5 business days after the required samples and access are available. A focused pilot is usually planned over 1–3 weeks, with release following owner sign-off.
These are scoping estimates. We confirm the quote, dependencies and delivery dates after review. Licences, connector or app fees, historical clean-up, additional companies and ongoing maintenance are identified separately.
For this workflow: Existing reference quality, report grouping, historical backfill and testing across installed add-ons.
Inspect the method
Examples and preparation guides.
Our downloadable pack contains synthetic job-work, receipt-exception and source-event examples. Use them to understand the checking method before we work with your approved samples. They are offline demonstrations, and compatibility is established in the agreed test environment.
For the agency’s Shopify credential and independent profile, visit The Night Marketer’s Shopify Select Partner profile.
Questions before you enquire.
What does the first Tally & TDL customisation pilot cover for Bengaluru?
Check native references and reporting first. If necessary, scope one TDL field or report that makes an agreed project identifier visible without replacing your accounting controls. Compatibility is assessed against your installed release and add-ons.
Can you confirm compatibility before reviewing our Tally installation?
Compatibility must be assessed against the exact release, company structure and installed add-ons. We scope that review and test the agreed change before confirming its release conditions.
Do we need TDL if Tally already has a similar report?
We check native configuration and reports first. Custom development is appropriate when an agreed requirement remains unmet, such as a specific reference field, grouping rule or print layout.
Review a first milestone before payment.
Agree a small deliverable, fee and acceptance checks in writing. Review the work, pay after acceptance and decide whether to continue. Remote delivery in English, led by Raghav with The Night Marketer.