
Picture a European group whose ERP runs every company it owns: orders, warehouse, invoices, accounts. Then it opens a subsidiary in Mexico. The order goes into the group’s system as usual, the warehouse ships it and the invoice is posted. But that invoice is worth nothing to the Mexican customer. In Mexico an invoice counts only once it carries the digital seal of the tax authority, the SAT, added by an authorised provider or by the SAT itself. So someone at the subsidiary opens a provider’s web portal, types the sale in again and downloads the valid invoice from there. When the provider rejects it, they fix it on the portal, and from then on the invoice in the group’s system is not the one the customer received.
Chile, Colombia and Brazil tell the same story with different rules. In all four countries an invoice normally goes through the tax authority, or someone acting for it, before it reaches the customer; Chile, Colombia and Brazil write down exceptions, which come up below. What changes is who checks the invoice, what it carries when it comes back, what the subsidiary must hold before its first invoice, how a wrong invoice is put right, and what happens when the authority’s system does not answer.
This piece follows one invoice through its life, from before it exists to the day it is corrected, and at each stage sets the four countries side by side, as their official texts state them. Then it turns them into what your ERP has to do, and how to connect it country by country so that the subsidiary invoices from the group’s own system.
A warning first: this is not tax advice. Which tax applies to a sale, which regime a subsidiary is under and which duty reaches it is for its tax adviser in each country to say. What follows is the systems side: documents, validations, deadlines and data.
Why «issued» stops meaning what your ERP thinks
An ERP built for Europe often treats an invoice as issued the moment it is posted. It gets its number, its date and its total, and it can be printed or sent. In these four countries that moment is only the start.
In all four, the invoice is an electronic document, an XML file in a format the tax authority sets. What gets printed is a representation of that file. Chile calls it the printed representation; Brazil’s portal says in so many words that the printed document travelling with the goods is not a tax invoice and does not replace one.
In all four, the file carries the electronic signature of whoever issues it, made with a digital certificate. And in all four, someone other than the issuer checks it: an authorised provider in Mexico, the tax authority itself in Chile, Colombia and Brazil. What has to wait for that check depends on the country. In Mexico the invoice counts only once it is stamped. In Brazil it counts only once it is authorised, although in two of the contingency modes described below the goods may travel first. In Colombia it counts only once validated, save the two contingency cases described below. In Chile the DTE goes to the SII first, save a 12-hour case described below, and one that covers goods on the move must already have been received there without rejection before they leave; with no data coverage it may travel unsent, and must reach the SII as soon as the connection returns. The check sends something back that the invoice did not have when it left your system: a seal, a state, a validation document, an authorisation.
The part that matters most for the design of the ERP is what is computed on each side. In Chile, Colombia and Brazil your own system computes the invoice’s identifier before sending it: the folio from a range the tax authority authorised, the CUFE, the 44-digit access key. What comes back is the verdict. In Mexico it is the other way round: the folio is assigned by the SAT and comes back through the provider, with the SAT’s seal, and your system does not have either until the provider answers.
Between posting and a valid invoice, then, there is an answer to wait for, and the answer can be a rejection. Everything else in this piece follows from that.
Before the first invoice: what each subsidiary must hold
No subsidiary can issue its first valid invoice on the day it decides to. Each country asks for something to be in place first, and most of it belongs to the subsidiary, not to the group.
Mexico: a seal certificate and a provider
The Mexican invoice is the Comprobante Fiscal Digital por Internet, the CFDI, whose format is in Annex 20 of the SAT’s yearly tax rules. Before it reaches anyone it carries the issuer’s own seal, made with its seal certificate, the CSD, which the Annex 20 guide says works as the issuer’s signature. The CSD is free and is requested on the SAT’s portal, with a request file made in the SAT’s Certifica application. The SAT’s page for Certifica says that generating that request requires a valid e.firma, the company’s advanced electronic signature, a separate certificate from the CSD. What the ERP needs is the CSD: it has to sit in the system that seals the invoices, and someone has to know where it is.
Then comes the provider. The guide is explicit: the only validation of e-invoices with legal basis and fiscal recognition is the certification done by the authorised certification providers, the PACs. That act is called stamping, timbrado. When the PAC adds the SAT’s digital seal, the guide says, it is the SAT that validates through the PAC. The SAT also stamps invoices itself in its free applications, but to invoice from your own system you need a PAC.
Chile: a certificate, folios and a certified system
In Chile, Article 54 of the VAT law, Decree-Law 825, rewritten by Law 20,727 and amended since, says that invoices, credit and debit notes and the other documents it names, which today include dispatch notes and sales receipts, consist exclusively of electronic documents, save the exceptions the law allows. The tax authority, the Servicio de Impuestos Internos or SII, calls them electronic tax documents, DTEs.
A Chilean ERP does not choose the range of its invoice numbers. It asks for it. According to the SII’s issuing instructions, a person the company has authorised requests the folios with their digital certificate, and the SII hands over a folio authorisation code, the CAF, together with a pair of keys used to generate and verify the electronic stamp. For the documents that give a right to VAT credit, an SII resolution sets that CAFs granted from 1 July 2018 are valid for six months from their authorisation. So the system needs a control of its own: how many folios are left, when the CAF expires and who asks for the next one. A system that runs out of folios cannot invoice until it has more.
The SII offers two routes: its own free system, or software of your own or bought on the market. Software takes a certification before it issues for real: a test set the SII assigns, a simulation set, an information exchange set, printed samples, a declaration of compliance and registration as an electronic issuer.
Colombia: enablement, a numbering range and its technical key
In Colombia the company first has to be enabled as an electronic invoicer by the tax and customs authority, the DIAN. Its resolution gives three options: software developed or acquired by the company, the DIAN’s free service, or a technology provider, which must itself be enabled by the DIAN. In all three the company runs tests, and when they pass, the DIAN changes its status from «registered» to «enabled».
The numbering is authorised by the DIAN too. Once it is authorised, the DIAN generates the technical key of that range, and the authorisation lasts two years. As in Chile, the ERP has to know which range it uses, when it expires and who requests the next one.
Brazil: an ICP-Brasil certificate and a test environment
In Brazil the invoice for goods is the Nota Fiscal Eletrônica, the NF-e. Its signature needs a digital certificate of the ICP-Brasil standard, for a legal entity, of type A1 or A3, identifying the company. For a European group that means a Brazilian certificate of the subsidiary, separate from any certificate the parent company uses, and it has to be in the system that signs.
The national NF-e portal describes two environments: the homologation environment, for tests, where documents have no legal validity and do not count as tax documents, and the production environment.
And the customer master, as the tax authority holds it
Mexico adds a requirement that lands in a place many teams overlook: the customer master. The CFDI 4.0 checks the customer’s data against the SAT’s records. According to the Annex 20 guide, the customer’s tax id, the RFC, has to be in the list of registered RFCs that are not cancelled; the name has to be the one registered with that RFC; the postal code of the tax domicile has to belong to that RFC; the tax regime has to be its current code; and the use the customer will give the invoice has to match that regime.
If your ERP holds the name as the order spells it and the address as the delivery address, that is not enough. For the CFDI, the name and the postal code are those of the tax record, written the same way, and one detail that does not match is an invoice the PAC rejects. These fields are best kept apart from the commercial ones, and checked before the first invoice.
Sending: what has to happen, and in what order
Once everything is in place, each country says in what order an invoice moves, and in some cases how much time it may take.
In Mexico, the CFDI’s date is the local time of the place where it is issued. The yearly tax rules tell the PAC to check that no more than 72 hours pass between an invoice’s generation and its certification, and that the period is not below zero, using the time zone of the postal code written as the place of issue; an invoice that misses that window is not issued at all. Both rules matter for a server in Europe. Its clock is not the invoice’s: the date belongs to the Mexican place of issue and its time zone. And three days is the whole life of an unstamped invoice: one left in a queue behind an error nobody reads has to be generated again.
In Chile the SII is precise about the order. Its questions on sending say that every DTE is sent to the SII before the goods are transported, before it is sent to the customer, and before its printed representation is handed to a customer who does not receive electronic documents. One case gets more time: when goods travel under a general dispatch note that only covers the transport, and are delivered at the customer’s premises with another DTE, the issuer has at most 12 hours from the actual delivery to send that other DTE. The DTE that backs a transfer of goods carries a further condition, set by an SII resolution of 2019: before the goods move, the SII must have received it and not rejected it, so that it sits in the SII’s records and can be checked on sii.cl. With no data coverage, the issuer or the carrier may travel with it unsent, on a device or on paper, and must have it sent and received as soon as the connection returns. And the SII warns that issuing does not mean the SII has received it: the issuer has to check whether the SII took it in, and in what state. The exchange with the customer is by email, to the address the customer has registered with the SII.
In Colombia, Article 616-1 of the Tax Statute requires every electronic sales invoice to be validated before it is issued, and considers it issued only once it has been validated and delivered to the customer. When the DIAN’s own systems prevent the validation, the same article lets the issuer issue and deliver it unvalidated, and it then counts as issued on delivery.
In Brazil, according to the national portal, the NF-e’s legal validity comes from the issuer’s digital signature and from the authorisation of use the tax authority grants, before the taxable event. It is sent to the SEFAZ that authorises it, the tax office of the issuer’s state or a virtual SEFAZ that authorises for it, and, except in two of the contingency modes described below, the goods may not circulate without that authorisation.
What comes back, and why it has to come back into the ERP
Each check returns something, and that something is part of the invoice.
From Mexico, the PAC returns the stamped CFDI. Under the yearly rules, certification is three things: the validation, the assignment of the folio and the SAT’s digital seal. The PAC adds them to the invoice in the digital tax stamp, the Timbre Fiscal Digital, which carries the folio the SAT assigned.
From Chile, the SII returns a state. An SII resolution of 2026 adds validations to the files it receives and sets three possible results: accepted, accepted with objections, or rejected.
From Colombia, the DIAN answers each invoice with an electronic validation document, which reads «Documento validado por la Dian» or «Documento rechazado por la Dian». The invoice goes to the customer together with that validation document, in what the resolution calls the electronic container. Each invoice carries the CUFE, an alphanumeric code the issuer computes from the invoice’s data, the technical key of its numbering range among them; credit and debit notes carry an equivalent, the CUDE.
From Brazil, the SEFAZ returns the authorisation of use. Each NF-e has its 44-digit access key, computed from the NF-e’s own fields; the DANFE, the printed document that travels with the goods, carries that key, and the portal warns that it is not a tax invoice and does not replace one.
The validated XML is the invoice, and it has to come back into the ERP, attached to the record of the sale. If it stays on a provider’s portal, the invoice in your system and the invoice the customer has are two documents again: exactly the problem this piece started from.
After the invoice: the customer has a say
In two of the four countries, what the customer does after receiving the invoice changes what it is worth, and in Mexico the customer has a say when you want to cancel one.
Chile: eight days to claim
Chilean Law 19,983 gives the customer eight calendar days from receiving the invoice to claim against its content, or against goods or services not fully delivered, and the SII counts those days from the invoice’s receipt at the SII. When they pass without a claim, the invoice is taken as accepted: it can be assigned to a third party through the electronic register the SII keeps, and it may carry executory force for collection. The acknowledgement of receipt and the claim exclude each other: a customer who acknowledges can no longer claim, and one who claims can no longer acknowledge.
For the seller’s ERP, the acknowledgement and the claim are information coming back. An invoice under a claim is neither accepted nor collectable, and the system should know it before the accounts team finds out.
Colombia: the RADIAN and three working days
When a Colombian sale is on credit, the invoice can become a credit instrument, registered in the DIAN’s RADIAN. Three events have to be on record for that: the customer acknowledges the invoice, confirms it received the goods or the service, and accepts it, expressly or by silence. Silence counts after three working days from receiving the goods or the service without an objection, under the decree that governs it. From that moment the invoice is closed to notes: no debit or credit note linked to it can be registered.
Mexico: a cancellation the customer must accept
When a Mexican cancellation needs the customer’s acceptance, the SAT notifies the customer in its tax mailbox, the buzón tributario. The yearly rules give the customer three days to answer (three working days, in the SAT’s questions and cancellation scheme); if it does not answer, the SAT takes the cancellation as accepted; the SAT’s frequently asked questions add that this applies to the first request. Some cases need no acceptance, among them invoices issued to residents abroad, invoices to the general public and invoices cancelled very soon after they were issued. For that last case, rule 2.7.1.35 says «within the working day following its issue», while the SAT’s questions and its cancellation scheme speak of 24 hours: a system that uses 24 hours meets both texts.
Putting a wrong invoice right: there is no edit button
In none of the four countries is a validated invoice edited and sent again. Each has its own route, and the ERP has to offer that route, not a «modify» button.
Mexico: cancel, with a reason
A stamped CFDI is not corrected: it is cancelled. Each cancellation carries one of four reasons: an invoice issued with errors, with a related replacement; issued with errors, without one; an operation that did not take place; or a named operation included in a global invoice. In the first case, according to the SAT’s questions, the replacement invoice is issued first and the wrong one is cancelled afterwards, citing the folio of the new one.
The deadline to cancel, according to the SAT’s cancellation scheme, runs to the month in which the annual income tax return for the year the invoice was issued is due. The SAT also reminds issuers that a credit note does not replace the cancellation of an income invoice, and that when an invoice has others related to it, those are cancelled first.
Chile and Colombia: notes
In Chile, the credit and debit notes are DTEs themselves, under the same Article 54 as the invoice, and they take the same path through the SII. In Colombia, credit and debit notes are named as such and numbered consecutively, each with its CUDE; once the invoice is accepted as a credit instrument in the RADIAN, as seen above, no notes linked to it can be registered.
Brazil: twenty-four hours, then a correction letter with limits
According to the national portal, an NF-e can be cancelled only while the taxable event has not yet happened. The taxpayer guidance manual has the SEFAZ check whether the NF-e was authorised more than 24 hours earlier; the authorising SEFAZ may still accept a cancellation after that limit, which it then records as approved out of time. To correct an error without cancelling there is the electronic correction letter, which has limits: it cannot correct what determines the tax, such as the tax base, the rate, the quantity or the value of the operation; it cannot change the sender or the recipient; and it cannot change the date of issue or the date of exit. For the values that determine the tax, the portal points to a complementary NF-e.
When the tax authority does not answer
An authority’s system can be down. Two of the four countries have written rules for it, and they are not the same as a rejection.
Colombia’s resolution separates two situations. If the problem is the DIAN’s, and it cannot validate, the company keeps invoicing electronically, without the validation document, and sends the invoices to the DIAN within 48 hours counted from the day after the service is restored. If the problem is the issuer’s, and it cannot invoice electronically, it invoices on paper and later transcribes those invoices as «type 3 invoices», within 48 hours of the problem being solved.
Annex III of Brazil’s taxpayer guidance manual, its contingency manual, describes three contingency modes, and in none of them does an NF-e count without its authorisation of use. Two serve whenever the NF-e cannot be sent or authorised, whether the fault is the issuer’s or the SEFAZ’s. With the security form, FS-DA, usable even without internet access, the DANFE is printed in at least two copies on that form, whose purchase and use the tax authorities control, never on ordinary paper, and one copy lets the goods travel. With EPEC, the prior issuing event in contingency, the issuer first registers a summary of the NF-e (access key, customer, totals) with the federal revenue service, and then prints the DANFE on ordinary paper. In both, the goods may leave before the authorisation, and the NF-e is sent as soon as the technical problems end, within the deadline the legislation sets; the DANFE that went with the goods is valid only if that NF-e is then authorised.
The third mode, the SVC, is a virtual SEFAZ that the state’s own SEFAZ switches on when its system cannot receive NF-e, and the ERP may use it only once the SVC’s status service answers that the SVC is in operation. There the order is the normal one: the NF-e, marked as issued under the SVC, is sent and authorised, and only then is the DANFE printed on ordinary paper; the NF-e is not sent to the state’s SEFAZ afterwards. Whichever the mode, an NF-e sent before the failure and still unanswered is issued again under a new number, and as soon as normal operation returns the ERP cancels the first, which covered no goods, if it was authorised after all, or voids its number if it was neither authorised nor denied. Each mode has its own rules, and the ERP has to know which ones the subsidiary uses.
A system that treats every missing answer as a rejection, or every rejection as a technical fault, ends up redoing by hand what the rules had already provided for.
Paid later: Mexico’s payment receipts
Mexico has one more rule that reaches beyond the invoicing module. An invoice settled when it is issued carries the payment method PUE, which the yearly rules also allow when the full payment is agreed or expected, and made, by the last day of the month of issue. An income invoice paid later or in instalments is PPD, and then each collection produces a document of its own: a CFDI with a total of zero and the payments complement, the Complemento para recepción de Pagos, one per payment or one a month per customer, issued at the latest on the fifth calendar day of the month after the payment.
For the ERP, this means that collecting an invoice also produces an invoice, stamped like any other. If cash receipts and invoicing are separate modules in your system, something has to join them.
Customers abroad, the general public, and services
A few cases change the fields, not the path.
In Mexico, an invoice to a customer resident abroad who is not in the RFC carries the generic RFC XEXX010101000, regime 616, without tax obligations, and use S01, without tax effects. If the operation carries the foreign trade complement, the customer’s tax id in its own country is required. For sales to the general public, the yearly rules allow a daily, weekly or monthly CFDI with the generic RFC XAXX010101000.
In Chile, the boleta is the document for sales to final consumers, and it is electronic only as well. Which document each sale takes is for the subsidiary’s adviser to say; an ERP that serves both kinds of customer has to issue both.
In Brazil, the NF-e is for goods. Services subject to the municipal service tax have their own electronic invoice, the NFS-e: some municipalities have a model of their own, and there is a national standard that each municipality joins by signing a term of adhesion. The joint act of July 2026 described below also sets, by kind of service, the dates from which the NFS-e is mandatory under the IBS and CBS regulations. If your subsidiary sells services, that is another connection.
What 2026 changed
The rules move, and three changes of this year are worth knowing by name.
In Brazil, the consumption tax reform introduces two new taxes, the IBS and the CBS. Technical note 2025.002-RTC, now in its version 1.53, adds their fields to the NF-e. A joint act of the federal revenue service and the IBS management committee, of December 2025, establishes that in 2026 the calculation of these taxes is informative only, without tax effects, provided the formal obligations are met. Another joint act, of July 2026, makes the NF-e mandatory under the IBS and CBS regulations for taxable events from 3 August 2026; some cases have later dates, imports of goods from 1 January 2027 among them. The acts are amended as the reform advances: read the current ones on the national portal before you plan. For the ERP these are new fields to compute and send on every note; how they are computed is for the subsidiary’s tax adviser to decide.
In Colombia, the technical annex of the electronic sales invoice was adopted in its version 1.9 by Resolution 165 of 1 November 2023. In September 2025, Resolution 227 gathered the DIAN’s tax, customs and exchange rules into one resolution, repealed the texts it compiled and kept version 1.9; the resolution itself says its content corresponds to that of the rules it compiles. A rule quoted to you from Resolution 165 still holds; only its article number has changed.
In Chile, Exempt Resolution 121 of 4 September 2026 adds the validations already mentioned and defines three results, among them «accepted with objections», for an invoice whose critical checks pass and which has minor inconsistencies. Its validations come into force in phases that the SII publishes on its site, so a system has to follow that calendar, not only the resolution.
The local provider: what it does, and where the law asks for one
The options of each country are those listed at the start: a PAC in Mexico, the SII’s free system or certified software in Chile, the DIAN’s free service, your own software or an enabled technology provider in Colombia. In Brazil, the texts we read do not require an intermediary: the NF-e is signed by its issuer, with its certificate, and another accredited company may transmit it with its own; only the certificate that transmitted it can then collect the answer.
The free tools of each authority have their place. But if the invoice is typed into them by hand, outside the ERP, you are back where this piece began. The connection to look for is the one between your ERP and the provider, or the authority, such that the invoice leaves the system, comes back validated and stays attached to the sale.
What your ERP has to do
Put the four countries together, and the changes to an ERP that treats an invoice as issued on posting fit in one paragraph. The invoice gets states (posted, sent, validated or rejected, later cancelled or corrected), each visible next to the sale. Only a validated invoice goes to the customer, save the exceptions described above; in Chile, one already sent to the SII, and goods travel only with a DTE the SII has received without rejecting it, unless there is no data coverage. What comes back is stored with the sale, and it is that file the customer receives. Folio and numbering ranges, the 72-hour window and the certificates are watched by the system itself, with a warning before anything runs out. Corrections follow the route of the country the invoice belongs to, and the system records which one was taken. And a rejection, which comes back with its reason, is never confused with a missing answer, which in Colombia and Brazil follows the contingency rules.
Testing country by country
Each country’s way of testing has been described above: the SII’s certification sets in Chile, the DIAN’s enablement tests in Colombia, the homologation environment in Brazil. In Mexico, validation is the PAC’s, and it is the PAC you ask how to test before stamping real invoices. It is worth using all of them.
The tests that teach most are the ones that fail. Besides a normal invoice, test one with customer data that does not match, a cancellation, a credit note and, where the country provides for it, an invoice in contingency. Each of these has to end up in the ERP with the right state and the reason in sight.
Where to start this week
None of these needs a project to be decided first:
- For each subsidiary, write down which tool issues its invoices today, and who types the data again.
- Collect real invoices from each country, with their XML, a cancellation or a credit note, and a rejection with its reason.
- In Mexico, count how many customers have their tax name, postal code, regime and use complete in the group’s system.
- List the certificates, folios, numbering ranges and enablements, with who holds each one and when it expires.
- Ask each subsidiary’s tax adviser what changes this year, and note the dates.
How we do it
This is the work of our tax invoicing in Latin America. 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.
You get one connection per country and a daily check of the rejected invoices. No invoice is redone by hand on a provider’s portal, outside the ERP, and rejected invoices are not discovered when a customer complains: the daily check shows them, with the reason. Each country is a project of its own, with its scope and price in writing, and you can start with a single one. It is not tax advice: which taxes apply is still for each subsidiary’s adviser to decide. The code, the accounts and the documentation are in your name from the first day.
If you want to see how it would work in your case, start with a free one-hour video call: tell us how each subsidiary invoices today, and we will tell you what we would look at first.
The official texts we cite
- SAT, Annex 20, guide to filling in the CFDI.
- SAT, Resolución Miscelánea Fiscal para 2026, compiled with its third amendment, rules 2.7.1.21, 2.7.1.23, 2.7.1.32, 2.7.1.34, 2.7.1.35, 2.7.1.39, 2.7.2.5 and 2.7.2.9; the binding text is the one published in the Diario Oficial.
- SAT, request for a seal certificate to issue invoices and the Certifica application.
- SAT, the questions and scenarios of cancellation 2026 and the CFDI cancellation scheme.
- Chile, Law 20,727, Decree-Law 825, articles 23 and 54, and Law 19,983, articles 3 and 9.
- SII, the technical issuing instructions, the certification process, the guide to accepting or claiming DTEs, Exempt Resolution 58 of 2017, Exempt Resolution 99 of 2019, Exempt Resolution 121 of 2026, and its questions on sending to the SII and reception.
- Colombia, Tax Statute, article 616-1.
- DIAN, Resolution 165 of 2023 and Resolution 227 of 2025, and Decree 1074 of 2015, article 2.2.2.53.4.
- Portal Nacional da NF-e: its frequently asked questions, the taxpayer guidance manual, version 7.0, with its Annex III (the NF-e contingency manual), and technical note 2025.002-RTC, version 1.53.
- Receita Federal and the IBS management committee, joint acts 1 of 22 December 2025 and 4 of 30 July 2026, published on the Portal Nacional da NF-e.
- Government of Brazil, the NFS-e and its national standard.
What we do about it: Tax invoicing in Latin America