CFDI Cancellation specifying a cancellation reason

This service allows the request of cancellation for one or several CFDI to SAT. Keep in mind that any cancellation request to SAT does not mean that cancellation will be granted.

Content

• General Features
• Requirements to cancel CFDI
• Integration
  • Cancellation via Webwervice
  • Cancellation via a flat text file
• Cancellation Webservice
  • What do I need?
  • Service Location
  • Method [Cancelar]: offline cancellation
  • Cancellation Request
  • Cancelallation Response
  • Method [CancelarSolicitudFirmada]: Self-signed cancellation request
  • Self-Signed cancellation request
  • Self-Signed cancellation response
  • Method [GetFolioStatusDetail]: Asynchronous Cancellation
  • GetFolioStatusDetail Request
  • GetFolioStatusDetail Response
  • Method [GetTransactionStatusDetail]: batch process query
  • GetTransactionStatusDetail Request
  • GetTransactionStatusDetail Response
• Response Codes from SAT's request for Cancellation
• FAQ

General Features

On the scheme of Digital Fiscal Receipts through the Internet (CFDI), SAT keeps on its central database all the certified receipts from all of the Certification Service Providers for the full taxpayers registry. Because of this centralized model, the cancellation of a CFDI consists of directly requesting to SAT the cancellation of the receipt through Cancellation of the CFDI.

The Cancellation of a CFDI can be requested by the taxpayer directly in SAT's portal for electronic invoicing, or through a PAC (Authorized Certification Provider) such as Sovos. The Fiscal Code of the Federation (CFF) for 2017 had a reform on its article 29-A which enables the recipient's of the CFDI to be informed of the cancellation request and allow them to approve or reject the cancellation requests.

Under this scheme the cancellation process cannot be asynchronous anymore. When there's a cancellation request, a consultation of the CFDI status must be triggered in order to know if the recipient has accepted the cancellation, or if the CFDI fell in any of the scenarios where no cancellation approval was requested to the recipient. The scenarios for this assumption are:

• When the cancellation is performed in the next 24 hours after its issuance.
• When it's a Revenue CFDI (with no relationships)
• When it's a Payroll CFDI (with no relationships)
• When it's a Translation CFDI (with no relationships)
• When it's a CFDI of Retentions and Payment information
• CFDI of residents living abroad for fiscal effects according to rule 2.7.1.26.
• CFDI of Incomes issued in operations with the general public, according to rule 2.7.1.24.
• CFDI of Incomes issued to taxpayers of the RIF (Regimen de Incorporación Fiscal)
• CFDI of Incomes up to an amount of $1,000.00 MXN

SAT can process a cancellation request when meeting the following:

• The cancellation request of the UUID (fiscal folio) must be electronically signed with the Digital Seal Certificate (CSD) of the issuer.
• The UUID (fiscal folio) must belong to the receipt's issuer.
• The reason for the cancellation must be established.
  • When the reason for cancellation is the key 01 "Receipt issued with errors and contains relationship" the CFDI should be related to the fiscal folio of the receipt that substitutes the one being cancelled.

Offline Cancellation (asynchronous)

On this modality the taxpayer request Sovos to perform a cancellation procedure for up to 2,000 folios in a single operation. The result of this operation will be a tracking Identification that can be consulted anytime during the progress of sending the fiscal folios to SAT.

Requirements to cancel a CFDI

To Perform the cancellation of a fiscal folio of a CFDI it is necessary to have the following:

• The fiscal folio (UUID) to be cancelled
• The RFC of the issuer of the receipt or receipts to cancel. This data can be extracted from the CFDI, whether the XML or the printed form (PDF).
• A valid Digital Seal Certificate (CSD) of the RFC of the receipt issuer.

The CSD usually consists of 3 parts:

1. The certificate, which is a file with the extension .CER
2. The private key, which is a file with the extension .KEY
3. The password of the private key

To obtain a Digital Seal Certificate (CSD) from SAT, please review the SAT site to generate a Request for a Digital Seal certificate to issue invoices.

Integration

There are two type of integration to perform cancellation requests via Sovos:

• Cancellation Webservice
• Flat text file through SFTP

In this article we explain the integration via webservice. If you wish to perform a cancellation through a flat text file, it is necessary to create the flat text file as indicated in the following link: Flat text file to cancel indicating the reason for cancellation. This file can be sent through the SFTP or uploading it in the Sovos Reachcore Portal.

For more information, please contact us or your executive account manager.

Cancellation Webservice

On this webservice you can perform the following operations:

• Unplugged cancellation
• Self-Signed cancellation

What do I need?

To use the cancellation webservice, you will need:

• A service contract with Sovos. If you don't have one please send an email to sales-mexico@sovos.com
• Generate an API key on your Sovos Mexico account, this is an identifier that authenticates the user on the platform's webservices. To generate an API key, check this article: Generating an API Key for web services.

Service Location

The URLs where the definition of Webservice (WSDL) is located for each of the environments are:

[Cancelar] Method: Offline cancellation

This method of the Webservice can receive a list of up to 2,000 fiscal folios to cancel. To use this method, the Digital Seal Certificate (CSD) must be registered in Sovos Mexico to be able to sign the cancel request. This is an Offline Cancellation therefore a second request is required to know the status of the cancellation.

Cancelar Request

Cancellation Request example

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cus="http://www.reachcore.com/CFDI/customHeaders" xmlns:urn="urn:reachcore.com:services:api:ws:pacservices:6.0">
   <soapenv:Header>
      <cus:ApiKey>7F3FA21M61.....19E42D72E3</cus:ApiKey>
   </soapenv:Header>
   <soapenv:Body>
      <urn:CancelacionFiscalRequest>
         <urn:RFC>AAA010101AAA</urn:RFC>
         <urn:Folios>
            <urn:CancelFolio>
               <urn:UUID>d6855812-af48-4e8f-b30e-3dcb8bd0b40d</urn:UUID>
               <urn:Reason>02</urn:Reason>
            </urn:CancelFolio>
         </urn:Folios>
      </urn:CancelacionFiscalRequest>
   </soapenv:Body>
</soapenv:Envelope>

Cancellation Reasons Catalogue

Cancellation Response Example

Response Example:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <CancelacionFiscalResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
         <OnError>false</OnError>
         <TrackingId>73cce105-aaa6-44ad-9d4e-01de09898b1c</TrackingId>
      </CancelacionFiscalResponse>
   </s:Body>
</s:Envelope>

Method [CancelarSolicitudFirmada]: Self-signed cancellation

This method is used to request the cancellation of the fiscal folio (or folios) of CFDI. The cancellation request is signed with the CSD that you have registered on the Sovos Mexico portal, however, when it's not possible to register the CSD in the Sovos Mexico portal, the XML of the cancellation request signed with the issuer's CSD can be sent with this webservice method: always abiding to definitions by SAT for cancellation requests. The response to this operation is identical to the one of the method Cancelar.

Self-signed Cancellation Request example:

Request Example:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cus="http://www.reachcore.com/CFDI/customHeaders" xmlns:urn="urn:reachcore.com:services:api:ws:pacservices:6.0">
   <soapenv:Header>
      <cus:ApiKey>7F3FA21M61.....19E42D72E3</cus:ApiKey>
   </soapenv:Header>
   <soapenv:Body>
      <urn:CancelarSolicitudFirmadaRequest>
         <urn:SignedApplication><![CDATA[<Cancelacion Fecha="2022-01-06T20:00:00" RfcEmisor="EKU9003173C9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://cancelacfd.sat.gob.mx"><Folios><Folio UUID="7E57607A-AB62-4E34-90AF-D5FA73221BE1" Motivo="01" FolioSustitucion="48318D72-8AA0-4497-8081-0DA3D8B6BB9D" /></Folios><Folios><Folio UUID="F96052BF-1EF7-48FE-9836-0B2CBD6F7C0D" Motivo="03" /></Folios><Signature xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" /><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><DigestValue>vBJlbXR9xVDB1TxZ77B6DLaRMDg=</DigestValue></Reference></SignedInfo><SignatureValue>hTiPnWZTWGW6Z4emZMvUkVpZ0VechiTvrAxuaSgpqKXlBiyTSN44e1O2uKUcEomlANwOQM5UcQVKuO80HaiiOyC/X5t4c3fefQrP086dD/q8TryV3cSQKP/iRvdEHi/wtL0u0ylhARud4kS1/bDn0q5If4NKox6KLM4O/M4ReMHTUErpVyzXHGMzO7kRONyf7vPDtG46ap+rhu6Ien8DxgZCOHFF7cXy0zTqsKHCMhOoWG95s0HnJ6OVPqOFiqvwIBviWKKtNInN6dH/h1hVYCH8jWoorbK89TSOQLoktkonxvrkl267Tq+wiIwHZnDo6srLTDjkWqbeL9WFjpcjRQ==</SignatureValue><KeyInfo><X509Data><X509IssuerSerial><X509IssuerName>OID.1.2.840.113549.1.9.2=responsable: ACDMA-SAT, OID.2.5.4.45=2.5.4.45, L=COYOACAN, S=CIUDAD DE MEXICO, C=MX, PostalCode=06370, STREET=3ra cerrada de cadiz, E=oscar.martinez@sat.gob.mx, OU=SAT-IES Authority, O=SERVICIO DE ADMINISTRACION TRIBUTARIA, CN=AC UAT</X509IssuerName><X509SerialNumber>292233162870206001759766198444326234574038512436</X509SerialNumber></X509IssuerSerial><X509Certificate>MIIFuzCCA6OgAwIBAgIUMzAwMDEwMDAwMDA0MDAwMDI0MzQwDQYJKoZIhvcNAQELBQAwggErMQ8wDQYDVQQDDAZBQyBVQVQxLjAsBgNVBAoMJVNFUlZJQ0lPIERFIEFETUlOSVNUUkFDSU9OIFRSSUJVVEFSSUExGjAYBgNVBAsMEVNBVC1JRVMgQXV0aG9yaXR5MSgwJgYJKoZIhvcNAQkBFhlvc2Nhci5tYXJ0aW5lekBzYXQuZ29iLm14MR0wGwYDVQQJDBQzcmEgY2VycmFkYSBkZSBjYWRpejEOMAwGA1UEEQwFMDYzNzAxCzAJBgNVBAYTAk1YMRkwFwYDVQQIDBBDSVVEQUQgREUgTUVYSUNPMREwDwYDVQQHDAhDT1lPQUNBTjERMA8GA1UELRMIMi41LjQuNDUxJTAjBgkqhkiG9w0BCQITFnJlc3BvbnNhYmxlOiBBQ0RNQS1TQVQwHhcNMTkwNjE3MTk0NDE0WhcNMjMwNjE3MTk0NDE0WjCB4jEnMCUGA1UEAxMeRVNDVUVMQSBLRU1QRVIgVVJHQVRFIFNBIERFIENWMScwJQYDVQQpEx5FU0NVRUxBIEtFTVBFUiBVUkdBVEUgU0EgREUgQ1YxJzAlBgNVBAoTHkVTQ1VFTEEgS0VNUEVSIFVSR0FURSBTQSBERSBDVjElMCMGA1UELRMcRUtVOTAwMzE3M0M5IC8gWElRQjg5MTExNlFFNDEeMBwGA1UEBRMVIC8gWElRQjg5MTExNk1HUk1aUjA1MR4wHAYDVQQLExVFc2N1ZWxhIEtlbXBlciBVcmdhdGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCN0peKpgfOL75iYRv1fqq+oVYsLPVUR/GibYmGKc9InHFy5lYF6OTYjnIIvmkOdRobbGlCUxORX/tLsl8Ya9gm6Yo7hHnODRBIDup3GISFzB/96R9K/MzYQOcscMIoBDARaycnLvy7FlMvO7/rlVnsSARxZRO8Kz8Zkksj2zpeYpjZIya/369+oGqQk1cTRkHo59JvJ4Tfbk/3iIyf4H/Ini9nBe9cYWo0MnKob7DDt/vsdi5tA8mMtA953LapNyCZIDCRQQlUGNgDqY9/8F5mUvVgkcczsIgGdvf9vMQPSf3jjCiKj7j6ucxl1+FwJWmbvgNmiaUR/0q4m2rm78lFAgMBAAGjHTAbMAwGA1UdEwEB/wQCMAAwCwYDVR0PBAQDAgbAMA0GCSqGSIb3DQEBCwUAA4ICAQBcpj1TjT4jiinIujIdAlFzE6kRwYJCnDG08zSp4kSnShjxADGEXH2chehKMV0FY7c4njA5eDGdA/G2OCTPvF5rpeCZP5Dw504RZkYDl2suRz+wa1sNBVpbnBJEK0fQcN3IftBwsgNFdFhUtCyw3lus1SSJbPxjLHS6FcZZ51YSeIfcNXOAuTqdimusaXq15GrSrCOkM6n2jfj2sMJYM2HXaXJ6rGTEgYmhYdwxWtil6RfZB+fGQ/H9I9WLnl4KTZUS6C9+NLHh4FPDhSk19fpS2S/56aqgFoGAkXAYt9Fy5ECaPcULIfJ1DEbsXKyRdCv3JY89+0MNkOdaDnsemS2o5Gl08zI4iYtt3L40gAZ60NPh31kVLnYNsmvfNxYyKp+AeJtDHyW9w7ftM0Hoi+BuRmcAQSKFV3pk8j51la+jrRBrAUv8blbRcQ5BiZUwJzHFEKIwTsRGoRyEx96sNnB03n6GTwjIGz92SmLdNl95r9rkvp+2m4S6q1lPuXaFg7DGBrXWC8iyqeWE2iobdwIIuXPTMVqQb12m1dAkJVRO5NdHnP/MpqOvOgLqoZBNHGyBg4Gqm4sCJHCxA1c8Elfa2RQTCk0tAzllL4vOnI1GHkGJn65xokGsaU4B4D36xh7eWrfj4/pgWHmtoDAYa8wzSwo2GVCZOs+mtEgOQB91/g==</X509Certificate></X509Data></KeyInfo></Signature></Cancelacion>]]></urn:SignedApplication>
      </urn:CancelarSolicitudFirmadaRequest>
   </soapenv:Body>
</soapenv:Envelope>

Self-signed cancellation response

Response Example:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <CancelarSolicituFirmadaResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
         <OnError>false</OnError>
         <TrackingId>68818c13-ac25-4367-8713-5e6ac7fe8234</TrackingId>
      </CancelarSolicituFirmadaResponse>
   </s:Body>
</s:Envelope>

[GetFolioStatusDetail] Method: Get the Status of a fiscal folio previously sent to be canceled

This method allows to know the status of a UUID previously certified by Sovos and that has a cancellation request whether through our Webservice or via Integration file.

Example of a Fiscal Folio Status Request

Example of a Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cus="http://www.reachcore.com/CFDI/customHeaders" xmlns:urn="urn:reachcore.com:services:api:ws:pacservices:6.0">
   <soapenv:Header>
      <cus:ApiKey>51e9d1097f634f20b....9e405d933f769303391008</cus:ApiKey>
   </soapenv:Header>
   <soapenv:Body>
      <urn:FolioStatusRequest>
         <urn:UUID>3895094A-5681-4363-8C4A-BE15A17200AA</urn:UUID>
      </urn:FolioStatusRequest>
   </soapenv:Body>
</soapenv:Envelope>

Example of Status Request of a Fiscal Folio Response

Response example:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <FolioStatusResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
         <OnError>false</OnError>
         <SatSentRequest>true</SatSentRequest>
         <ResultCode>202</ResultCode>
         <ResultMessage>Petición de cancelación recibida anteriormente.</ResultMessage>
         <UUID>3895094A-5681-4363-8C4A-BE15A17200AA</UUID>
         <UUIDStatus>
            <StatusCode>S - Comprobante obtenido satisfactoriamente.</StatusCode>
            <IsCancellable>Cancelable con aceptación</IsCancellable>
            <State>Cancelado</State>
            <QueryDate>2021-12-27T18:00:00</QueryDate>
         </UUIDStatus>
         <RelatedUUIDs/>
      </FolioStatusResponse>
   </s:Body>
</s:Envelope>

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <FolioStatusResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
         <OnError>false</OnError>
         <Error>
            <Code/>
         </Error>
         <SatSentRequest>true</SatSentRequest>
         <ResultCode>201</ResultCode>
         <ResultMessage>Petición de cancelación recibida</ResultMessage>
         <UUID>74e4b36d-e4b5-4ee2-9e5b-64c5362dd56e</UUID>
         <UUIDStatus>
            <State>SIN ELEMENTOS PARA LLEVAR A CABO LA CONSULTA EN EL SAT</State>
            <QueryDate>0001-01-01T00:00:00</QueryDate>
         </UUIDStatus>
         <RelatedUUIDs/>
      </FolioStatusResponse>
   </s:Body>
</s:Envelope>

[GetTransactionStatusDetail] Method: Result of Batch Status cancellation

This method lets you know the Status of a previously request for cancellation, whether it may have been requested through web service or per integration file.

Example of Result of Batch Status cancellation Request

Request Example:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cus="http://www.reachcore.com/CFDI/customHeaders" xmlns:urn="urn:reachcore.com:services:api:ws:pacservices:6.0">
   <soapenv:Header>
      <cus:ApiKey>51e9d1097f634f20b.......406d9e405d933f769303391008</cus:ApiKey>
   </soapenv:Header>
   <soapenv:Body>
      <urn:TransactionStatusRequest>
         <urn:TrackingId>e6123fb8-723b-4d9a-8ff0-e4a69803e380</urn:TrackingId>
      </urn:TransactionStatusRequest>
   </soapenv:Body>
</soapenv:Envelope>

Example of Result of Batch Status cancellation Response

A batch will be on Finished Status when each of the receipts that were requested to be canceled are shown on one of the following statuses: * Successfully canceled. * Could not be canceled at SAT and the reason correspond with certain codes. These codes are considered as non-retriable on the SAT Response Codes for Cancellation.

Response Example

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <TransactionStatusResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
         <OnError>false</OnError>
         <TotalUUIDs>5</TotalUUIDs>
         <UUIDsSentToSAT>5</UUIDsSentToSAT>
         <UUIDsRejectedSAT>0</UUIDsRejectedSAT>
         <Finished>true</Finished>
         <UUIDs>
            <FolioFiscalDetail>
               <UUID>17ed0948-a4ae-4ebd-b581-522bbc800e73</UUID>
               <RequestSentToSAT>true</RequestSentToSAT>
               <ResultCode>202</ResultCode>
               <ResultMessage>Petición de cancelación recibida anteriormente.</ResultMessage>
               <UUIDStatus>
                  <StatusCode>S - Comprobante obtenido satisfactoriamente.</StatusCode>
                  <IsCancellable>Cancelable sin aceptación</IsCancellable>
                  <State>Cancelado</State>
                  <CancellationStatus>Cancelado sin aceptación</CancellationStatus>
                  <QueryDate>2022-01-31T19:29:27.367</QueryDate>
               </UUIDStatus>
            </FolioFiscalDetail>
            <FolioFiscalDetail>
               <UUID>19d18962-e614-4c7a-8a7c-80bd9e0d2af6</UUID>
               <RequestSentToSAT>true</RequestSentToSAT>
               <ResultCode>202</ResultCode>
               <ResultMessage>Petición de cancelación recibida anteriormente.</ResultMessage>
               <UUIDStatus>
                  <StatusCode>S - Comprobante obtenido satisfactoriamente.</StatusCode>
                  <IsCancellable>Cancelable sin aceptación</IsCancellable>
                  <State>Cancelado</State>
                  <CancellationStatus>Cancelado sin aceptación</CancellationStatus>
                  <QueryDate>2022-01-31T19:29:26.817</QueryDate>
               </UUIDStatus>
            </FolioFiscalDetail>
            <FolioFiscalDetail>
               <UUID>1b640b2d-e218-4230-b309-e25d1c2404c0</UUID>
               <RequestSentToSAT>true</RequestSentToSAT>
               <ResultCode>202</ResultCode>
               <ResultMessage>Petición de cancelación recibida anteriormente.</ResultMessage>
               <UUIDStatus>
                  <StatusCode>S - Comprobante obtenido satisfactoriamente.</StatusCode>
                  <IsCancellable>Cancelable sin aceptación</IsCancellable>
                  <State>Cancelado</State>
                  <CancellationStatus>Cancelado sin aceptación</CancellationStatus>
                  <QueryDate>2022-01-31T19:29:27.083</QueryDate>
               </UUIDStatus>
            </FolioFiscalDetail>
            <FolioFiscalDetail>
               <UUID>1ca30c9c-3a38-47bc-b399-ebd4596516a1</UUID>
               <RequestSentToSAT>true</RequestSentToSAT>
               <ResultCode>201</ResultCode>
               <ResultMessage>Petición de cancelación recibida</ResultMessage>
               <UUIDStatus>
                  <StatusCode>S - Comprobante obtenido satisfactoriamente.</StatusCode>
                  <IsCancellable>Cancelable sin aceptación</IsCancellable>
                  <State>Cancelado</State>
                  <CancellationStatus>Cancelado sin aceptación</CancellationStatus>
                  <QueryDate>2022-01-31T19:29:26.223</QueryDate>
               </UUIDStatus>
            </FolioFiscalDetail>
            <FolioFiscalDetail>
               <UUID>1f82ee83-3860-4e35-81e5-6a24401cb693</UUID>
               <RequestSentToSAT>true</RequestSentToSAT>
               <ResultCode>201</ResultCode>
               <ResultMessage>Petición de cancelación recibida</ResultMessage>
               <UUIDStatus>
                  <StatusCode>S - Comprobante obtenido satisfactoriamente.</StatusCode>
                  <IsCancellable>Cancelable sin aceptación</IsCancellable>
                  <State>Cancelado</State>
                  <CancellationStatus>Cancelado sin aceptación</CancellationStatus>
                  <QueryDate>2022-01-31T19:29:28.197</QueryDate>
               </UUIDStatus>
            </FolioFiscalDetail>
         </UUIDs>
      </TransactionStatusResponse>
   </s:Body>
</s:Envelope>

The cancellation process has two phases: Send the cancellation request to SAT and if Reachcore has information to get the status of the receipts: Ask SAT about the status of the receipts in the batch. The Finished element with value true indicates that the cancellation service has finished the process of sending the cancellation request and the attempts to obtain the status in SAT of the receipts in the batch. While in the cancellation process, a status query to the cancellation batch will look like this:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <TransactionStatusResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
      <OnError>false</OnError>
      <TotalUUIDs>1</TotalUUIDs>
      <UUIDsSentToSAT>0</UUIDsSentToSAT>
      <UUIDsRejectedSAT>1</UUIDsRejectedSAT>
      <Finished>false</Finished>
      <UUIDs>
        <FolioFiscalDetail>
          <UUID>0952bfa9-ae90-4c01-a7a9-ba19698cfcd8</UUID>
          <RequestSentToSAT>true</RequestSentToSAT>
          <ResultCode>201</ResultCode>
          <ResultMessage>Petición de cancelación recibida</ResultMessage>
          <UUIDStatus>
            <State>EN PROCESO DE CONSULTA DE ESTADO EN EL SAT</State>
            <CancellationStatus>DESCONOCIDO</CancellationStatus>
            <QueryDate>0001-01-01T00:00:00</QueryDate>
          </UUIDStatus>
        </FolioFiscalDetail>
      </UUIDs>
    </TransactionStatusResponse>
  </s:Body>
</s:Envelope>

If Sovos Reachcore doesn't have the elements to query the status, the response will look like this:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <TransactionStatusResponse xmlns="urn:reachcore.com:services:api:ws:pacservices:6.0">
      <OnError>false</OnError>
      <TotalUUIDs>1</TotalUUIDs>
      <UUIDsSentToSAT>0</UUIDsSentToSAT>
      <UUIDsRejectedSAT>1</UUIDsRejectedSAT>
      <Finished>false</Finished>
      <UUIDs>
        <FolioFiscalDetail>
          <UUID>054d6de1-5b86-42db-a475-c748f3bbba38</UUID>
          <RequestSentToSAT>true</RequestSentToSAT>
          <ResultCode>201</ResultCode>
          <ResultMessage>Petición de cancelación recibida</ResultMessage>
          <UUIDStatus>
            <State>SIN ELEMENTOS PARA LLEVAR A CABO LA CONSULTA EN EL SAT</State>
            <QueryDate>0001-01-01T00:00:00</QueryDate>
          </UUIDStatus>
        </FolioFiscalDetail>
      </UUIDs>
    </TransactionStatusResponse>
  </s:Body>
</s:Envelope>

SAT Cancellation Response Codes

For each receipt cancellation request, SAT authorizes or rejects specifying an status code. On the following table describes the status codes and what they mean.

For more information or to clarify any doubt related to this implementation guide on the cancellation service, please send an email to MEX-soporte@sovos.com. You can aldo see the FAQ about cancellation on this link: cancellation FAQ.

Frequent Asked Questions

1. What can I do if my RFC has special characters such as &?

Unlike the issuance service where the XML is encapsulated in a CDATA envelope, the RFC on this method travels without this envelope so there should be escape sequences for special characters inside the node RFC.
In the case of the character & we have to use the sequence & so if the RFC is &&&010101000 it should be sent as &&&010101000.

2. Inconsistencies on the CFDI cancellation service when using cancellation reason "01"

Sometimes there are inconsistencies over cancellations using the reason for cancellation 01 (Receipt issued with errors. Receipt has relationship.) where cancellation requests are processed sometimes according to what is established sometimes not. About this, the authority says:

1. CFDIs related to the receipt that you want to cancel must be canceled first. Including the replacement CFDI, using the reason for cancellation 02 (Receipt issued with errors. Receipt has no relationship).
2. Proceed with the cancellation request of the related CFDI, registering the key `02` (Receipt issued with errors. Receipt has no relationship).
3. Once the receipts mentioned in steps 1 and 2 are canceled, a new receipt will be issued with the correct information and the relationship with key 04 replacement of previous CFDI related to the fiscal folio of the receipt being replaced.

Frequently Asked Questions and cancellation scenarios according to the Fiscal Reform of 2022

The following is an extract of the questions and answers published on the PDF named "Frequent questions and cancellation scenarios according to the Fiscal Reform 2022" published on the SAT Portal through the page Updates on Electronic Invoice- Fiscal Reform 2022 on the Related Content section published on December 2021.

1.- If I issued an invoice or CFDI with version 3.3, when I request the cancellation, is it necessary to indicate the reason for cancellation or this just applies to version 4.0?

From January 1st 2022, it will be required to display the reason for cancellation. This applies to every version of the invoice or CFDI.
Legal basis: Article 29-A sixth paragraph of the Fiscal Code of the Federation.

2.- In which cases we should select as a reason for cancellation the option "01" - Receipt issued with errors. Receipt has relationship?

This scenario applies when the generated receipt has an error on the product key, unit value, discount, or any other data; so it should be issued again. In this case, first you replace the invoice, and then request for the cancellation, you will add the invoice folio that will replace the canceled one.

3.- In which cases we should select as a reason for cancellation the option "02" – Receipt issued with non-related errors?

This scenario applies when the generated invoice has an error on the product key, unit value, discount, or any other data and it’s not necessary to relate it with another generated invoice.

4.- In which cases we should select as a reason for cancellation the option "03" – The operation was not performed?

This scenario applies when you generated an invoice for a transaction that was not finished.

5.- In which cases we should select as a reason for cancellation the option "04" – Nominative procedure related to the global invoice?

This scenario applies when a sale is included in the global invoice for procedures with the general public and afterwards, the client requests a nominative invoice, this leads to canceling the global invoice and issuing it again, and then generating the nominative invoice for the client.

6.- I issued an invoice, but now my client is asking to cancel it because it has errors on the description, how should I perform the cancellation of that receipt?

When performing the cancellation request, you should follow these steps:

1. You should issue the receipt with the correct data and register the key "04" (Substitution of Previous CFDI) linking the fiscal folio of the receipt that is being replaced.
2. You can request the cancellation by entering the sat.gob.mx portal in the "Cancellation and recovery of invoices" service, or through the services of a PAC (Authorized Certification Provider).
3. When registering the cancellation request you should select the option "01" (Receipt issued with errors. Receipt has relationship.) and include the fiscal folio of the receipt issued on step 1.
4. When sending the cancellation request you will see if the acceptance of the recipient is needed to perform the cancellation.

Legal basis: Article 29-A sixth paragraph of the Fiscal Code of the Federation

7.- In the event that an invoice has been issued for a sale or the provision of a service which was not carried out, what reason for cancellation should be indicated in the corresponding cancellation request?

The issuer of the invoice must register the code "03" The operation was not carried out in the Reason for cancellation section.
Legal basis: Article 29-A sixth paragraph of the Fiscal Code of the Federation

8.- I issued an invoice with an error on the RFC of my client, it has not been delivered to the client yet. To cancel it, should I first link it to the replacement invoice?

The cancellation request may be made by registering in the reason for cancellation section the code "02" (Receipt issued with errors. Receipt has no relationships.).
Subsequently, the fiscal receipt must be issued with the correct data and register the key "04" (Replacement of previous invoices or CFDI) relating the fiscal folio of the receipt that is replaced.
Legal basis: Article 29-A sixth paragraph of the Fiscal Code of the Federation

9.- My client is asking for the invoice of a product that is related to the global invoice issued on the public general operations for the monthly period, what should I do to issue the requested receipt?

The issuer should ask for the cancellation of the global invoice and register the cancellation reason with code "04" (nominative operation related to the global invoice).
Then, he should issue the fiscal global receipt without considering the receipt for the public general operations that was issued in a nominative way.
Finally, you can generate the nominative invoice requested by your client.