Tax invoicing in Latin America
In Mexico every invoice has to be authorised by the tax authority, and our ERP doesn't do it.
- What we do
- We connect your ERP to each country's e-invoicing, alongside a local provider, certified by the tax authority where the law requires one: CFDI in Mexico, DTE in Chile, DIAN e-invoicing in Colombia, NF-e in Brazil. Each country is a project of its own.
- How we do it
- In each country, we first look at how the subsidiary invoices today and what that country's tax authority requires of each invoice. Then we write which field of your ERP goes to each field of the e-invoice, connect the system to the local provider and test until the invoices pass validation. Finally we switch on the daily check of the rejected invoices.
- What you receive
- One connection per country and a daily check of the rejected invoices.
- What changes for you
- No invoice is redone by hand on a provider's portal, outside the ERP. Rejected invoices are not discovered when a customer complains: the daily check shows them, with the reason.
- What we need from you
- Access to the subsidiary's ERP, one person from its administration, samples of the invoices it issues and, in each country, the details and certificates that the tax authority and the local provider ask of the company.
- Who it is for
- The subsidiary's head of administration
- How you buy it
- One project per country, plus a recurring fee.
Example use cases
These are examples: they do not describe a real client.
An agricultural machinery maker whose Mexican subsidiary invoices outside the group's system
The situation
The Mexican subsidiary sells with the group's ERP, but that system cannot issue the CFDI. So every invoice is redone by hand on a provider's portal: the same data, typed twice. When the provider rejects one, someone fixes it right there, and the invoice in the group's system no longer matches the one the customer received.
What we do
We connect the ERP to a provider authorised by the Mexican tax authority: each invoice leaves the system, the provider stamps it, and the stamped CFDI comes back into the system, attached to the sale's record. The daily check shows the rejected ones and the reason, and administration corrects them in the same system.
A textile group with subsidiaries in Chile and Brazil
The situation
The Chilean subsidiary issues the DTE with one tool and the Brazilian one the NF-e with another, each outside the group's system. At head office no one sees which invoices have been rejected, or why, and each subsidiary has its own way of sorting it out.
What we do
We run two separate projects, one per country. In Chile, the group's system is connected to the local provider to issue the DTE; in Brazil, alongside the local provider, the NF-e leaves the system signed with the subsidiary's digital certificate and is authorised by its state's SEFAZ. Each country has its daily check of rejections, and head office sees them.
Frequently asked questions
Why is each country a separate project?
Because each country has its own e-invoice, its own tax authority and its own rules: what works in Mexico does not work in Chile. Each connection has its own scope and price in writing, and you can start with a single country.
Do we have to change the group's ERP?
No. We connect it to each country's local provider, and the subsidiary invoices from the system it already uses.
What happens to a rejected invoice?
The daily check shows it with the reason for the rejection, and your administration corrects it in the ERP and sends it again, without leaving it.