Skip to Content
Product Information
Author's profile photo Ailane Kuhn

ATCUD para Portugal: Prepare-se para o novo requisito legal da Portaria 195/2020

(Scroll down for the English version)

Olá,

 

Como já deve saber, o governo português publicou a Portaria 195/2020 e, juntamente com o código QR, introduziu o Código de Documento Único (ATCUD) como um novo requisito legal, vigente a partir de 1º de janeiro de 2022.

As empresas precisam obter um novo código de validação de série e usá-lo para gerar o ATCUD, sendo este um código único atribuído a documentos fiscais relevantes, como faturas e notas de crédito.

O ATCUD é reportado no ficheiro (SAF-T) e incluido no código QR. Ele deverá também ser incluido nos documentos impressos e eletrônicos.

Para mais informações sobre a solução de código QR, veja o blog post Código QR e ATCUD para Portugal: Fique por dentro das últimas atualizações da Portaria 195/2020.

 

A solução SAP

Um framework centralizado para gerir as séries e os códigos de validação AT por módulo será disponibilizado, suportando a comunicação manual e eletrônica.

Essa solução está planejada para estar disponível em duas fases:

  • Fase 1: Âmbito reduzido (serviços web não incluídos). Está planejado para ser disponibilizado em meados de novembro de 2021.
  • Fase 2: Funcionalidade relacionada aos serviços web. Está prevista para ser disponibilizada em meados de dezembro de 2021.

 

Os pré-requisitos

Existem algumas atividades de preparação que podem ajudar a acelerar as etapas de implementação assim que a solução estiver disponível:

Implementação de SAP Notes

Certifique-se de que implementou as SAP Notes relacionadas ao Despacho 8632/2014:

Comunicação com as autoridades fiscais

Pode utilizar os serviços da Web para comunicar automaticamente com as autoridades fiscais. Para esta comunicação, é necessário integrar o seu sistema com SAP Cloud Integration.

Para mais informações, consulte a SAP Note 2903776 ou entre em contato com seu gestor de conta SAP.

Atividades de configuração

Certifique-se de atualizar as configurações necessárias:

    • Crie novos intervalos de numeração e defina as respectivas séries únicas para assinatura digital. A nova nomenclatura deve seguir os requisitos legais (não são permitidos caracteres especiais). Para mais informações sobre as atividades de customizing, veja Customizing for Digital Signature of Invoices. Aguarde também as novas instruções que serão publicadas em breve.
    • Atribua os novos intervalos de numeração aos respectivos tipos de documento SAF-T.
    • Adapte os seus layouts de impressão para incluir o ATCUD nos formulários.

Poderá utilizar os intervalos de numeração e séries atuais enquanto prepara os novos intervalos de numeração. Após 1 de janeiro de 2022, deverá utilizar os novos intervalos de numeração.

 

Fique atento às notícias mais recentes

Fique atento! Pretendemos atualizar este blog regularmente.

Também pode verificar mais informações no grupo SAP Jam SAP Portugal Collaboration Forum. Se ainda não for membro deste grupo, envie sua solicitação de convite para o seguinte e-mail: marta.pereira@sap.com.

Fique à vontade para deixar seus comentários abaixo se tiver alguma dúvida ou sugestões para uma publicação futura. E não se esqueça de seguir a tag do SAP S/4HANA aqui na SAP Community para ficar atento às notícias mais recentes.

Até à próxima,

Ailane Kuhn

#SAPGoGlobal #SAPLocalization

 

 

***

 

 

ATCUD for Portugal: Get ready for the new legal requirement on Portaria 195/2020

 

Hi everyone,

As you might be aware, the Portuguese government published Portaria 195/2020 and, together with the QR code, introduced AT-Validation Code (ATCUD) as a new legal requirement, effective as of January 1, 2022.

Companies need to obtain a validation code for their series and then use it to generate the ATCUD, which is a unique document code assigned to relevant documents, such as invoices and credit memos.

You must include the ATCUD on printed documents and in electronic invoices and also report the ATCUD via the Standard Audit File for Tax Purposes (SAF-T). It must also be included in the QR code.

For more information about the QR code solution, see QR Code and ATCUD for Portugal: Stay Tuned to the Latest Updates on Portaria 195/2020.

 

The SAP solution

A centralized framework to manage the Series and AT-Validation Codes across modules will be provided, supporting both the manual and the automatic communication.

This solution is planned to be available in two phases:

  • Phase 1: Reduced scope (web services not included), planned to be available not earlier than mid November 2021.
  • Phase 2: Web service-related functionality, planned to be available not earlier than mid December 2021.

 

The prerequisites

There are some preparation activities that could help you to speed up the implementation steps once the solution is available:

SAP Notes implementation

Make sure you have the SAP Notes related to Despacho 8632/2014 implemented:

Communication with the tax authorities

You can use webservices to communicate with the tax authorities automatically. For this communication, you need to integrate your system with SAP Cloud Integration.

For more information, see SAP Note 2903776 or contact your account executive.

Configuration activities

Make sure you maintain the required configuration settings:

    • Create new number ranges and define their unique series for Digital Signature. The new nomenclature should follow the legal requirements (special characters aren’t allowed). For more information about the Customizing activities, see Customizing for Digital Signature of Invoices. Further instructions will be published soon.
    • Assign the new number ranges to the respective SAF-T document types.
    • Adapt your print layouts to include the ATCUD in the forms.

Note that you can use the current number ranges and series while defining the new number ranges. After January 1, 2022, you must use the new number ranges.

 

Stay tuned to the latest news

Stay tuned! We plan to update this blog post regularly.

You can also check out the SAP Jam group Portugal SAP Collaboration Forum. If you are not a member of this SAP Jam group yet, please send your invitation request to the following email: marta.pereira@sap.com           .

Feel free to leave your comments below if you have any questions or suggestions for an upcoming post. And don’t forget to follow the SAP S/4HANA tag here on SAP Community to stay tuned to the latest news.

 

See you next time,

Ailane Kuhn

#SAPGoGlobal #SAPLocalization

Assigned tags

      15 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Robbert Van Sprang
      Robbert Van Sprang

      Hello Ailane and Marta,

       

      Many thanks for this new blog about ATCUD. Good to know that a solution is being worked on.

       

      I have a question in the meantime. The blog mentions the following configuration:

       

      Configuration activities

      Make sure you maintain the required configuration settings:

        • Create new number ranges and define their unique series for Digital Signature. The new nomenclature should follow the legal requirements (special characters aren’t allowed). For more information about the Customizing activities, see Customizing for Digital Signature of Invoices. Further instructions will be published soon.
        • Assign the new number ranges to the respective SAF-T document types

       

      We have been using digital signatures already for many years, so all related configuration for digital signatures is already in place in our system. Can you let me know what configuration we must take care of specifically related to ATCUD? This is not clear to me yet.

       

      Thank you in advance for clarifying,

      • Robbert
      Author's profile photo Marta Pereira
      Marta Pereira

      Dear Robbert

      The process should be more or less the following:

      1 - You can use your old NR/Series until the end of the year or you can decide the moment when you want to start using the new NR/Series.

      2 - You need to create the new NR and the respective new series following the instructions.

      3 - You need to decide when you want to start using this new NR/Series and on that moment you should communicate to TA those new NR/Series (manually or in a automatic way using webservice).

      4 a)- If the process is automatic, the solution will pick the new NR/series and communicate them to TA and store the returned validation code delivered by TA.

      4b) - if the process is manual, you need to go to TA portal, communicate the NR/series, and update manually the system with the returned validation code

      5 - After that (and assuming that the customization of the documents/series/NR are already updated and digital signature activated), you can start using the new NR.

      Hope that this summary can help you to better understand the future solution.

      Best Regards, Marta

       

       

      Author's profile photo António Oliveira
      António Oliveira

      Hi Marta,

      about the need for new number ranges, on Portaria 195/2020, Article 7º, we have:

      "Regime transitório
      1 — Os sujeitos passivos, utilizadores de programas informáticos de faturação ou outros meios
      eletrónicos, relativamente às séries que pretendam manter em utilização, dando continuidade à
      respetiva numeração sequencial, devem, durante o mês de dezembro de 2020, comunicar os
      elementos referidos no n.º 1 do artigo 2.º, sendo o elemento referido na alínea c) substituído pelo
      último número utilizado, nessa série, no momento da comunicação."

      So, for SD documents, I see no need to create new number ranges.

      About FI invoices, because we have the same range number for each year, I think that the best way is to use for each year a different serie number (could be the same of the year), and on an annual basis, comunicate the serie for the new year, and after finish and post all documents of last year, close the corresponding serie.

      I see on the blog and SAP Jam several doubts about this question, related no the need of new number ranges, but I'm not agree with that need, based on Artilce 7º of Portaria 195/2020.

      It's very important to all customers clarify this question!

       

      Thanks,

      António Oliveira

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi António

      In the past we never had any specific rules for the series. The customers could decide if they want to use always the same (for example 1) for all the types of documents/NR, or some customers use 1 character, other 2 or 3.

      Now with Portaria 195/2020, we need to define some rules for the series, to follow the rule of having a unique series per SAF-T document type (FT, NC,….).

      For that and to guarantee the unique series by document type, we will implement some validations to the series, like for example the 1st letter of the series defines the module from where the document is originated.

      Another validation will be that there is no possibility for repeat the series for the same document type (the example for this case is the year dependent NR, that according with the new rules you need to have the following

      DR - 2020– 100 - 199 – F001

      DR – 2021 – 100 – 199 – F002

      This means that for 2 different years will not be possible to repeat the series F001

      Because of this rule of unique series by SAFT doc type, we need to create new series, and according with point 1.9 of Despacho 8632/2014, when there is a need for technical reasons to change the series, it is necessary to create a new series (in our case also a new NR).

      “1.9 - Se por uma questão técnica ou operacional, a utilização de uma série for descontinuada, a aplicação deve inibir a sua utilização, não podendo, de forma alguma, apagar qualquer informação relativa à mesma”

      This means that you need to create a new NR, even if it is the continuity of the previous NR. You can cut the old NR and create a new one using the remaining numbers available

      Example

      Old NR – 10000 – 19999 – Serie 1 – last number used 10095

      You can create a new NR where: New NR - 10100 – 19999 – Series B001

      Regards, Marta

      Author's profile photo António Oliveira
      António Oliveira

      Dear Marta,

      In fact, we have the mention of “Identificador da série do documento” as need to communicate on both:

      . Portaria 195 2020 -  Article 2º a)

      . Comunicacao_de_Series_Documentais_Manual_de_Integracao_de_SW_Aspetos_Especificos, 2.1.2 – XML structure to register series.

       

      We start to use the “serie” because of the digital signature legal requirement. However, the “serie” was always a part of a combination of the pair “System document type” “Serie”.

      For each (unique) pair of this combination, we should assigned one specific (and always different) number range to get the corresponding digital signature. Is in this logic that we have customizing tables SIPT_NUMBR_SD, SIPT_NUMBR_FI and SIPT_NUMBR_OBD.

       

      Even, on Despacho 8632/2014, the relevant to identify the document is this pair “System document type” “Serie”, followed by “/” and number range, and have something like “F2 2/2064123456”.

       

      So, in my opinion, the TA intention is maintain (or not misrepresent) this logic.

       

      As example for a specific Sales Organization, we have the following real entries on table SIPT_NUMBR_SD:

      Doc. Type   Serie   Number Range    (SAFT Doc. Type)

      F2                     2        2064nnnnnn                  FT

      IV                      2        2066nnnnnn                  FT

      RE                    2        2068nnnnnn                  NC

       

      In fact, if we see “Identificador da série do documento” only as “Serie” we cannot communicate this tree different Series/Document types, because we can only communicate the “Serie” once for a specific number range and SAFT document type.

       

      But, if we maintain the logic of the pair, as used always for digital signature, and without misrepresent the logic and TA intention we can communicate the following:

       

      1. Identificador da Série: F2_2 (respect the rules for the “Identificador da Serie” construction; note that on this rule we have [._-] as separator; and I ask: separator of what?...)

      TipoDoc: FT

      NumInicialSeq: 2064123456 (for instance)

      DataInicioPrevUtiliz: 01-01-2022

       

      1. Identificador da Série: IV_2

      TipoDoc: FT

      NumInicialSeq: 2066123456

      DataInicioPrevUtiliz: 01-01-2022

       

      1. Identificador da Série: RE_2

      TipoDoc: NC

      NumInicialSeq: 2068123456

      DataInicioPrevUtiliz: 01-01-2022

       

      Note: you said on your post that "to follow the rule of having a unique series per SAF-T document type". I think that Portaria 195/2020 don´t have that rule, as you also refer on sentence "there is no possibility for repeat the series for the same document type" (but we can have different series (assigned to different system document types) for one specific SAFT document type. Example: we have the standard document types F2 and IV related to SAFT document type FT and we must have these entries on digital signatures customize tables)

       

      In this way, we need no need to create new number ranges and, in my opinion, does not collide with the legal requirement purposes.

       

      This approach is much simpler for customers and if it has not yet been approached with the authorities, should be.

       

      I hope with this my point of view contribute for a simpler solution either for customers, but also for SAP.

       

       

      Thanks,

      António Oliveira

      Author's profile photo KANNAN A
      KANNAN A

      Hi,

       

      Thanks for the information about ATCUD code. Could you please clarify below points,

      • If the process is manual, we can get ATCUD code from TA and use it to print ATCUD code in invoice output. In this case, we no need to wait for SAP notes as we are running short on time due to our internal processes.
      • If the process is automatic to get ATCUD code, then we need webservice and wait for SAP notes to be implemented.
      • Is the ATCUD code same for each invoice types and is it going to be static or it is dynamic or incremental like invoice numbers.?

      Thanks in advance.

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Kannan A

      Answering to your question:

      1 - Portuguese Tax Authorities will release a portal to allow customers to communicate the series manually. Unfortunaly they still have not date for that manual portal.

      The issue if you don´t use the SAP solution to store the ATCUD code, is that you will not be able to report it in SAF-T and when creating documents you will probably get some error messages, because SAP is expecting to have that information in SAP delivered internal tables.

      2 - Yes, if you decide to go for Webservice automatic communication, you will have to wait for the full solution from SAP.

      3 - The ATCUD is a concatenation between the validation code returned by Tax Authorties for each series communicated plus the internal document number.

      So this means for example for doc Type F2 with the number range F2 (doc nr 100 to 199) and Series B001, when communicated you will get for example the validation code AB3TR6I8.

      When concatenated this code with the documents you will get a unique combination for each document:

      AB3TR6I8-100

      AB3TR6I8-101

      ....

      AB3TR6I8-199

      Hope that my explanations could help you.

      Best Regards, Marta

      Author's profile photo Barbara Botelho
      Barbara Botelho

      Olá,

      Temos algumas dúvidas sobre as guias de transporte. As guias de transporte também devem ser impressas com o QRCode? Como será o processo para as guias de transporte?

      Obrigada.

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Barbara

      Sim, as guias de remessa terão de ter também o QR Code impresso, assim como o ATCUD.

      Existe a nota coletiva para logistica relativamente ao QR Code 3008107.

      Cumprs, Marta

      Author's profile photo António Santos
      António Santos

      Boa tarde,

      relativamente à comunicação de guias de remessas via webservice à AT, o ATCUD também deverá ser comunicado ou é exclusivo para o SAF-T?

      Obrigado

      Cumprimentos

      Author's profile photo Marta Pereira
      Marta Pereira

      Oá António,

      Vou tentar verificar essa informação junto da AT, uma vez que a documentação do ATCUD não faz referencia à comunicação das guias de transporte.

      Cumprs, Marta

      Author's profile photo Daniel Cunha
      Daniel Cunha

      Olá Marta Pereira

       

      Tendo em conta reuniões da AHRESP com o governo no sentido de adiar mais 1 ano a implementação do ATCUD (englobado no OE2022), existem novidades nesse sentido?

      https://www.jornaldenegocios.pt/empresas/detalhe/oe2022-proposta-falha-no-essencial-diz-ahresp

      Pelo que entendi não existe ainda uma solução da SAP para implementar o ATCUD.

       

       

      Obrigado,

      Daniel Cunha.

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Daniel

      Até aprovação do OE 2022, mantemos as datas de entrega da solução (meio de Novembro a parte do framework e meio de dezembro a parte de webservice).

      O OE será votado na generalidade na proxima semana dia 27. Nessa altura esperamos ter mais noticias sobre o adiamento ou não do ATCUD para 2023.

      Cumprs, Marta

       

       

      Author's profile photo Barbara Botelho
      Barbara Botelho

      Olá Marta,

      Atualmente utilizamos o mini saft para certificar as guias de remessas. Com o processo do ATCUD e QR Code, como ficam essas certificações através do mini saft? O mini saft ainda pode ser utilizado?

      Obrigada.

      Author's profile photo Luis Mendes
      Luis Mendes

      Olá Marta, muito obrigado pelas informações.

      Tenho duas questões:

      1. Quanto à comunicação com a AT, será necessária a contratação de um Broker (ex. Generix, SAP Cloud Integration, Saphety, etc) ou será possível se comunicar direto do ECC pelo SOA MANAGER como já é feito hoje para documentos de delivery?
      2. Quanto ao range de numeração, ambos, SD e FI devem ter novos ranges? Isso vale apenas para billing documents?

      Agradeço antecipadamente.

      Luis Mendes