Mexico Postpones the New CFDI Cancellation Process

September 7, 2018 Ramon Frias

After a meeting with the Confederation of Chambers of Commerce and Tourism (CONCANACO), the Mexican Tax Administration (SAT) decided to postpone for two months the new process of Cancellation of the CFDI (https://www.sat.gob.mx/noticias/54244/se-prorroga-al-1-de-noviembre-de-2018-la-operacion-del-nuevo-proceso-de-cancelacion-de-facturas). The petition of postponement was based on the fact that a lot of taxpayers were not ready from the technological standpoint, to initiate the new process of cancellation that requires both the use of the fiscal inbox and the approval of the customer. Originally scheduled to take effect on September 1, 2018, this new process will instead become mandatory on November 1. This is the third time this new system is postponed. The official postponement will be made in the Federation Official Diary in the coming days.

About the Author

Ramon Frias

As Tax Counsel, Ramon is licensed to practice law in the Dominican Republic and is a member of the Dominican Bar Association. He has a Certificate Degree from Harvard University as well as a JD from the Universidad Autonoma de Santo Domingo.Ramon has written many essays about tax administration, and for one of them won the first prize in the international essays contest sponsored by the Inter American Center of Tax Administrations (CIAT). Prior to joining Sovos Compliance, Ramon worked for more than 10 years in the Department of Revenue of the Dominican Republic where he served as Deputy Director. He is proficient in French and Spanish.

More Content by Ramon Frias
Previous Article
IRS Releases Publication 1220 for Tax Year 2018

The IRS recently published a new version of Publication 1220 for tax year 2018.

Next Article
Mexico Postpones the New CFDI Cancellation Process

The Mexican Tax Administration (SAT) decided to postpone for two months the new process of Cancellation of ...

×

Regulatory Analysis News - Delivered Weekly

Company
Thank you for subscribing!
Error - something went wrong!