On this page
- Begin with accreditation and the contracting entity
- Describe your environment before asking for compatibility
- Compare evidence in a simple worksheet
- Test the ordinary case and the awkward case
- Understand the support boundary
- Read the commercial assumptions
- Common questions
- Make the shortlist useful to your finance team
Use a shortlist that records evidence and unanswered questions. Avoid ranking providers on an invented score or assuming the lowest advertised fee represents the full implementation cost.
Begin with accreditation and the contracting entity
Check the current Ministry of Finance register and record the provider’s exact legal name. Make sure the business named in the contract corresponds to the accredited service being offered.
A reseller or software implementer may support the project without being the ASP. Keep that relationship explicit so that your staff know who supplies the accredited service and who configures the business software.
Describe your environment before asking for compatibility
Record the TallyPrime edition and installed build, the deployment method, legal entities, user arrangement and existing custom modules. Identify whether a native connection, an additional connector or a proposed integration is involved.
“Works with Tally” is not a complete answer. Ask what version and workflow the statement covers, who maintains the connection and how changes are handled.
Compare evidence in a simple worksheet
| Assessment area | Evidence to request | Possible open item |
|---|---|---|
| Accreditation | Current official listing and exact legal entity | Contracting name unclear |
| Connection | Supported version and documented method | Connector still requires development |
| Transaction fit | Demonstration using relevant scenarios | One of your credit-note or reference cases not tested |
| Status handling | Where users see acknowledgement and errors | Responsibility for a stuck transaction unclear |
| Records and access | Export/retrieval terms and record responsibilities | Exit data format not confirmed |
| Support | Escalation route and service terms | Implementer and provider roles overlap |
| Cost | Itemised setup, recurring and usage charges | Transaction assumptions not stated |
| Exit | Notice, transition and access arrangements | Contract termination consequences unclear |
This is a requirements worksheet, not a government accreditation test. Your business chooses the weight of each requirement and decides what evidence is sufficient.
Test the ordinary case and the awkward case
A standard invoice shows that one path can work. Your business also needs to understand the exceptions that occur in its normal operations.
Choose representative scenarios with the relevant accountant or reviewer. Consider document references, discounts, returns and the fields your customers ask to receive. Confirm which information appears only on the printout and which information actually travels in the structured message.
Do not assume a proposed future feature is ready because it appears on a roadmap. Record the exact limitation and decide whether it affects your implementation date.
Understand the support boundary
When something fails, does your user contact the software implementer or the ASP first? Who checks source-data issues? Who investigates provider-side transmission? Who communicates the resolution back to accounts?
Agree this process before daily invoicing begins. It is especially important when a third-party connector sits between the accounting system and the provider.
Read the commercial assumptions
Ask how charges change with companies, users, documents or connectors. Clarify onboarding fees, recurring costs and what happens at renewal. Confirm what the implementation provider charges separately for cleanup, mapping, testing and training.
Do not turn “no additional software feature charge” into a statement that every service in the project is free.
Common questions
Should every Tally user choose the same ASP?
Not on the basis of a generic recommendation alone. The actual connection and business requirements should be checked. The business remains responsible for its appointment and contract decisions.
Can BlackCat help with a provider we have already selected?
We can review the technical and data requirements. That review must establish feasibility and scope before we confirm an integration or implementation commitment.
Make the shortlist useful to your finance team
Use the worksheet to identify evidence, decisions and unresolved questions. Then connect it with the e-invoicing implementation plan and data-preparation work.
For assistance, see ASP selection and onboarding support, contact BlackCat or message us on WhatsApp.
Official references
Ministry of Finance: eInvoicing programme and current legislation ↗Ministry of Finance: accredited provider register ↗TallyHelp: UAE release notes ↗TallyHelp: UAE capabilities and limitations ↗Reviewed 18 November 2026. Product capabilities, commercial terms and official guidance should be rechecked before implementation.