On this page
BlackCat helps Tally users review data quality and map agreed information for a supported UAE e-invoicing setup.
Review the records in manageable groups
| Record group | Examples of information to review |
|---|---|
| Your companies | Legal identity, address, registration information and applicable tax identifiers |
| Customers and suppliers | Consistent names, addresses, identifier type and relevant electronic-address information |
| Stock items and services | Meaningful descriptions, units, classifications and agreed tax treatment |
| Transaction settings | Document types, references, discounts, charges and applicable supporting information |
| Custom fields | Whether required business references have supported structured-message destinations |
These are preparation categories, not a substitute for the current mandatory-field specification. Which fields are required depends on the applicable transaction and rules.
Separate data cleanup from data mapping
Cleanup resolves the quality of a record: for example, a duplicate customer or incomplete address. Mapping defines where an approved value belongs in Tally and in the supported exchange format.
A cleaned spreadsheet can still be mapped incorrectly. A correct mapping can still transmit poor source data. Both need attention, and the business should approve identifiers and accounting classifications.
A practical preparation workflow
- Agree the company, master and transaction scope.
- Export or review the relevant records through an agreed process.
- Identify gaps, duplicates and decisions requiring approval.
- Confirm source documents and approved values.
- Apply changes in a controlled way and test representative outputs.
- Record unresolved exceptions and assign ongoing ownership.
For larger changes, connect the work with Excel imports and migration. For electronic exchange, validate the outcome with the intended ASP onboarding and e-invoicing implementation process.
Make the handover useful
Agree what the project will produce: corrected records, a mapping record, an exception list and examples showing the tested output, as applicable to the scope. Identify who maintains these fields after go-live. Without an owner, the same gaps can return as new customers and items are added.
Frequently asked questions
Can BlackCat verify every customer’s legal and tax information?
We can review the agreed records and identify missing or inconsistent information. Your business and counterparties remain responsible for supplying and approving the correct underlying details. No universal third-party verification is promised.
Should every Tax Group member use the group TIN?
Do not assume so. Official FTA guidance says members must independently comply using their own applicable individual TIN. Confirm the entity information for onboarding; do not manufacture identifiers or assume a separate VAT TRN exists for every member.
Can we leave custom project references only on the printout?
That depends on your customer’s needs and applicable requirements. If the information must travel in the structured message, confirm its supported field and mapping. Printing it alone does not establish that it is exchanged.
How is this service priced?
Request a quote based on companies, records, issues, mapping requirements and the agreed correction responsibility. A data-cleanup project should not be hidden inside an undefined onboarding fee.
Fix the source before repeating the error
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.