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.
Com o Despacho 351/2021.XXII publicado dia 11 de novembro de 2021, ATCUD será opcional em 2022 e obrigatório a partir de janeiro de 2023.

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.

 

SAP Notes lançadas e atualizadas em 2022

Agora você já pode consultar a nota coletiva 3154599 que lhe dará toda a informação relevante para a implementação da solução, inclusive nos diversos módulos (SD, FI, FI-CA, Settlement Management, etc.). Veja também a documentação incluída. Esta nota será atualizada sempre que for liberada a solução de um novo módulo.

 

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.
With Despacho 351/2021.XXII published on November 11, 2021, ATCUD will be optional in 2022 and mandatory as of January 2023.

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.

 

New and Updated SAP Notes Released in 2022

The Collective Note 3154599 has been released with all the information you need to know about the solution implementation for ATCUD in different modules. You can also check the product documentation for more information.
This SAP Note will be updated every time there’s a new solution release for the different modules. Stay tuned!

 

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

      60 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 António Santos
      António Santos

      Olá Marta,

      têm alguma novidade sobre este tema?

      Obrigado

      Cumprimentos

      António Santos

      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 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

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Luis

      Relativamente às questões:

      1 - A comunicação não necessita de um broker, mas o processo automático será feito via SAP Cloud Integration.

      2 - Todos os NR que hoje em dia são certificados mais os recibos necessitam ter uma nova série.

      Obrigado, Marta

       

      Author's profile photo Marcelo Pollak
      Marcelo Pollak

      Olá Marta

       

      Gostaria de ver se eu entendi corretamente: a solução do Web Service estará disponível apenas no SAP Cloud?

      Nesse caso, pra quem tem apenas um ERP ou S/4 on premise, teria que pegar o certificado manualmente?

       

      Obrigado, Att

      Marcelo

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Luis

      Quem quiser a solução automatizada, terá de ver junto do seu account/parceiro como obter a licença para o serviço da Cloud.

      Não lhe sei dar pormenores sobre este assunto.

      Cumprs, Marta

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Marcelo

      A comunicação manual não tem custos associados.

      Apenas quem quiser ter o processo automatizado de comunicar e receber o Código de Validação é que necessita ter o SAP Cloud Integration.

      Cumprs, Marta

      Author's profile photo Susana Gonzalez
      Susana Gonzalez

      Hello

      Thanks so much for your sharing this information. Do you know in witch table ATCUD is storage?

      Susana

      Author's profile photo Marta Pereira
      Marta Pereira

      Dear Susana

      This will be a new table that SAP will deliver in the note planned to be released on middle of November.

      Regards, Marta

       

      Author's profile photo Catarina Alves
      Catarina Alves

      Boa tarde Marta,

      Envio de seguida algumas questões relativas ao ATCUD:

      1. Será necessário criar de novos intervalos para 2022 para todos os documentos certificados? só os certificados? tais como Documentos de expedição SD, Documentos de Facturação SD e Documentos de FI e documentos de Auto-Facturação de fornecedores de forma a serem cumpridas as regras de acordo uma nova definição de série.
      2. Caso se opte pela Comunicação manual no portal como vai funcionar? vai ser uma solução semelhante à que existe para a comunicação das guias à AT via Rmini_SAFT? através de um ficheiro que extraímos do SAP e integramos no site da AT, a qual nos devolve posteriormente um ficheiro com os Códigos os quais subsequentemente são integrados em SAP?
      3. A solução com webservice implica sempre a aquisição de uma licença ou haverá outra solução alternativa?
      4. Empresas que tenham anos fiscais diferente do ano em que momento devem ser comunicadas as séries?
      5. Haverá algum programa de suporte da SAP que ajude na identificação dos novos intervalos de numeração a serem criados?
      6. No caso de já não existir na NRIV codificações disponíveis para criar novos intervalos de numeração para o objeto RV_BELEG como devemos proceder?

      Muito obrigada pela ajuda

      Catarina Alves

       

       

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Catarina

      Seguem as respostas às tuas questões:

      1 - Devem ser criados novo NR/Séries para todos os documentos assinados digitalmente e para os recibos.

      Quanto à auto-faturação a propria AT ainda não publicou os requisitos, por isso ainda não temos orientações sobre a criação ou não de novos NR já para 2022.

      2 - O processo manual será mesmo manual, sem qualquer tipo de webservice. Ou seja a empresa vai manualmente ao portal da AT com as séries e depois tem de ir à APP/transação colocar para cada série o Código de Validação dado pela AT

      3 - Será sempre através do SAP Cloud Integration

      4 - Devem comunicar antes de 01.01.2022 e depois os documentos anuais (por exemplo de FI) tornar a comunicar antes do novo ano fiscal da empresa (por exemplo se o ano fiscal for 01.04.2022 a 31.03.2023, deverão comunicar novamente as series antes de dia 01.04.2022 com uma nova série)

      5 - Ao criarem novas séries, desde que estas cumpras as regras de 4 caracteres e o 1º caracter corresponder ao módulo de onde provem o documento, estes serão sempre automaticamente incorporados no framework (APP/transação) com status Inicial

      6 - Os 2 caracteres usados para a criação de novos NR, podem tefr caracteres especiais, nordicos, chineses, etc. Apenas na criação da série não podem ser usados caracteres especiais, tal como descrito pela AT.

      Espero ter ajudado, Marta

       

      Author's profile photo Soumyakanti Giri
      Soumyakanti Giri

      Hi Marta,

      Thank you for the information in the blog till now.

      Is the ATCUD solution that is being created by SAP for all documents classes as mentioned by Portuguese Authorities - invoices (Sales Invoice), movement of goods (delivery documents), offer and order (working documents)?

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Soumyakanti

      You need to have ATCUD in all digitally signed documents (Invoices, Credit and Debit Memos, Deliveries, Working Documents and others that are digitally signed), plus the receipts.

      Regards, Marta

      Author's profile photo Soumyakanti Giri
      Soumyakanti Giri

      Hi Marta,

       

      Thank you for the help. I also have a doubt regarding document series identifier.

      After reading the replies I understood that a new series identifier has to be sent to Portugal AT each time a new number range is communicated.The number range we maintain is in the standard table RV_BELEG.

      Can you clarify a little on what the series identifier relates to in SAP terms in the system.

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Soumyakanti

      The Series is a concept that we created in SAP for Portuguese Digital Signature to follow portuguese TAx Authorities rules.

      This is a new field (since 2011) used in tables SIPT_NUMBR_BKPF; SIPT_NUMBR_VBRK, SIPT_NUMBR_LIKP and others.

      We use then the series in the Legal Number of the documents (invoices, Credit and Debit memos, Deliveries and so on).

      Imagine that your internal Invoice in SD from Doc Type F2 is the number 100056.

      When you print the document and when you report this invoice in SAF-T you give it the number

      F2 1/100056

      where 1 is the series that you indicate in table SIPT_NUMBR_VBRK for the NR associated to doc type F2.

      Now is this series that need to follow the rules, and because of that new NR are necessary for the documents that are digitally signed.

      Hope that this could clarify your doubts.

      Regards, Marta

       

      Author's profile photo Marcelo Pollak
      Marcelo Pollak

      Olá Marta

      Já tem a decisão sobre a possível prorrogação do prazo?

      Obrigado, att

      Marcelo

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Marcelo

      Uma vez que o Orçamento de Estado não foi aprovado, e ainda não saiu nenhuma lei a dar o adiamento do requisito, as datas que temos são 1 Jan 2022.

      No entanto ainda pode sair alguma lei a dar o adiamento do prazo.

      Na SAP continuamos a trabalhar para que tudo seja entregue nas datas planeadas de modo as os clientes poderem ter a solução antes de 1 Jan 2022.

      Cumprs, Marta

      Author's profile photo Barbara Botelho
      Barbara Botelho

      Olá Marta,

      Atualmente utilizamos Rmini_SAFT para comunicar as guias de transporte. Temos algumas dúvidas com relação ao processo.

      Para o Rmini_SAFT como e em que momento o ATCUD e QrCode são criados?

       

      Obrigada,

      Author's profile photo Teodoro López
      Teodoro López

      Good morning Marta,

      Up to now, there are specific settings and tables for the digital signature in Portugal for RE.

      Is SAP taking into account for the new solution the Real Estate component?. I am quite concerned about this issue..

      Thank you for your feedback.

      Best Regards,

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Teodoro

      The solution for RE-FX is planned to be delivered in 2 phases:

      Phase 1 - the generic framework of the communication in middle of november

      Phase 2 - notes specific for RE-FX planned delivery date 30.11.2021

      Regards, Marta

      Author's profile photo Claudia Kurose
      Claudia Kurose

      Olá...

      será que o Governo Português vai prorrogar essa solicitação? Vi que a SAP tem previsão de disponibilizar algo no fim de Novembro para meio de Dezembro... vai ficar muito em cima...

       

      Há outra alternativa para o ATCUD se não houver solução SAP até Jan/22 e a lei não prorrogar?

      Obrigada!

       

       

      Author's profile photo Claudia Kurose
      Claudia Kurose

      Olá..

      se a SAP não lançar uma solução até fim de Dez/21 e a lei não for prorrogada... há alguma outra alternativa quanto ao ATCUD?

      Vi que s SNOTEs poderão ser disponibilizadas do fim de Novembro para meio de Dezembro, mas entendo que depende do Governo português nas diretrizes do requerimento.

      Grata

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá Claudia

      A SAP irá entregar a solução antes do final do ano.

      Em relação a um possivel adiamento, isso depende exclusivamente de ser ou não aprovada uma alteração à portaria 195/202 em que a data seja alterada de 01.01.2022 para 01.01.2023.

      Cumprs, Marta

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

      Olá,

      relativamente ao formato dos novos números de série a criar, os valores a utilizar para o primeiro caracter já têm valores finais?

      Confirmam-se os valores abaixo?

      Documentos gerados via módulo FI/FICA: F

      Documentos faturação gerados via módulo SD: B

      Documentos transporte (Guias remessa): D

       

      Aguardo feedback

      Obrigado

      Cumprimentos

       

       

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá António

      O primeiro caracter para cada um dos módulos será o seguinte:

      FI - F

      SD - B

      FICA - K

      Deliveries - D

      Receipts FI - P

      Receipts FICA - Q

      Cumprs, Marta

       

       

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

      Olá Marta,

      Obrigado pelo feedback,no entanto no seguimento da resposta da Marta ficamos com as seguintes dúvidas:

      1. Todos os recibos (FI/FICA) devem ter ATCUD ou só os recibos certificados que são os de IVA de Caixa?
      2. Caso todos os recibos devam ter ATCUD e QR Code, estes devem ser certificados?

      Obrigado

      Cumprimentos

      Author's profile photo Marta Pereira
      Marta Pereira

      Olá António

      Segundo a AT são todos os recibos impressos que devem conter o QR Code e o ATCUD.

      Cumprs,

      Marta

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Dear Customers

      Today it was released the Despacho 351/2021.XXII were the ATCUD it will be mandatory only in 2023.

      In 2022 the ATCUD will be optional.

      Even so in the next days/weeks we will deliver the solution as planned and that you can start implementing and testing with time.

      Best Regards, Marta

      https://info.portaldasfinancas.gov.pt/pt/informacao_fiscal/legislacao/Despachos_SEAF/Documents/Despacho_SEAAF_351_2021_XXII.pdf

      Author's profile photo Luis Mendes
      Luis Mendes

      Hello Marta, thank you for the information.

      Author's profile photo Claudia Kurose
      Claudia Kurose

      Thank you for the information.

      Author's profile photo Barbara Botelho
      Barbara Botelho

      Hello Marta, thank you.

      Is this also valid for qrcode?

      Thanks

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Barbara

      QR Code is still mandatory in 2022.

      Regards, Marta

       

       

      Author's profile photo Nicola Poisa
      Nicola Poisa

      Hi Marta,

      In the last digits of QR Code  there is included also the ATCUD...( if I remember well).

      What we need to transfer  to QR Code if ATCUD is not active?   XXXX?

      thank you.

      Nicola

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Nicola

      you should populate it with 0 (zero).

      Like in Saf-t.

      regards, Marta

      Author's profile photo Yannick Ragot-Mercier
      Yannick Ragot-Mercier

      Hello.. in this case, which is minimum number of 0000 should we key to populate QR code ?

      thanks

      Author's profile photo Arun Kumar
      Arun Kumar

      Hello Marta,

      What are all the mandatory documents we should have QR code to comply?

      Do we have to do any config/notes implementation apart from the notes specified in blog to have QR code in SAFT?

      Thanks in advance.

      Regards,

      Arun,

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi Arun

      The QR Code should be printed in all the documents digitally signed, plus the receipts.

      QR Code is not populated in SAF-T file, and this is the reason why we don´t have any solution for that.

      QR Code solution is only for Layouts.

      Regards, Marta

      Author's profile photo APO Support
      APO Support

      Hi

      As per the latest communication from SAP regarding H field ATCUD in QR code, the solution for TAX authority value will come by mid December,2021.

      Please provide confirmation on this and if there is any update on this

       

      Thank you

      Author's profile photo Marta Pereira
      Marta Pereira

      Dear all

      Please consider the following information about planned dates/release for the solution

      On Premise Solution

      Module Component Portaria 195/2020 and Despacho 412/2020 (ATCUD) - On Premise Planned Delivery Date
      SD XX-CSC_PT-LO Central Framework 31/01/2022
      Validation Code for Communication of Series Deliveries 28/02/2022
      Validation Code for Communication of Series Settlement Management 28/02/2022
      ATCUD Print Layout Deliveries 28/02/2022
      MM XX-CSC-PT-LO Validation Code for Communication of Series - SelfBilling To be provided
      SD XX-CSC-PT-BIL Validation Code for  Series of SD Invoices 15/03/2022
      Validation Code for  Series of FI Invoices 31/03/2022
      ATCUD for FI Invoice Adobe Print Layout 31/03/2022
      ATCUD Validation Code for Series of Payment Receipts To be provided
      ATCUD for VAT on Cash Receipt Adobe Layout To be provided
      RE-FX RE-FX-LC-PT ATCUD Validation Code for communication of series - RE-FX 31/03/2022
      SAF-T communication - RE-FX 31/03/2022
      SAF-T XX-CSC-PT-LO ATCUD SAF-T Communication - Deliveries 28/02/2022
      ATCUD SAF-T Communication - Settlement Management 28/02/2022
      FI-LOC-SAF-PT Monthly SAF-T to report ATCUD 15/04/2022
      Monthly Self-billing SAF-T to report ATCUD To be provided
      FI-LOC-SAF-PT Monthly SAF-T to report ATCUD for Payment Receipts To be provided
      XX-CSC-PT-FICA Monthly SAF-T to report ATCUD for FICA, IS-U (incl 3rd Party Billing, Self-Billing), Convergent Invoicing 31/03/2022
      FICA/IS-U/CI XX-CSC-PT-FICA ATCUD Validation Code for Series in FICA, IS-U, Convergent Invoicing 31/03/2022
      ATCUD for (non-SAP) Print Layouts 31/03/2022
      ATCUD Validation Code for Series for Self-Billing in IS-U To be provided
      ATCUD Validation Code for Series for FICA Payment Receipts and VOC Receipts To be provided
      CRM CRM-LOC ATCUD SAF-T Communication - CRM To be provided
      Validation Code for Communication of Series - CRM To be provided

       

      Cloud Solution

      Release Portaria 195/2020 and Despacho 412/2020 (ATCUD) - Cloud Planned Delivery Date
      S4HANA CL 2111 e-invoice: ATCUD 30/11/2021
      S4HANA CL 2202 Central Framework 26/01/2022
      ATCUD Print Layout Deliveries 26/01/2022
      Validation Code for Communication of Series - Deliveries 26/01/2022
      ATCUD Validation Code for series of SD invoices 26/01/2022
      ATCUD in SD print Adobe Layouts 26/01/2022
      Monthly SAF-T ACR  to report ATCUD 26/01/2022
      S4HANA CL 2203 Validation Code for Communication of SD Invoices & Settlement Management 16/03/2022
      Webservice Central Framework (Automatic Communication - require CPI) 16/03/2022
      ATCUD Validation Code for Series of Payment Receipts 16/03/2022
      ATCUD SAF-T Communication Deliveries 26/03/2022
      S4HANA CL 2205 Monthly SAF-T ACR  to report ATCUD for Payment Receipts 18/05/2022
      S4HANA CL 2206 ATCUD Validation Code for series of FI invoices 15/06/2022
      Not yet a date Validation Code for Communication of Series - SelfBilling To be provided
      Monthly SAF-T ACR  to report ATCUD for Settlement Management To be provided
      Self-Billing SAF-T ACR to report ATCUD To be provided

      Best Regards, Marta

      Author's profile photo Luis Silva
      Luis Silva

      Hi.

       

      Can you confirm:

      Premise Solution - is manual range certification

      Cloud Solution - automatic range certification (online)

      ?

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Caros clientes

      As datas planeadas de entrega atualizadas, assim como o status das entregas

       

      Dear Customers

      The planned dates updated and status of the deliveries

      Regards

      Marta

      On Premise Solution

      Module Component Portaria 195/2020 and Despacho 412/2020 (ATCUD) - On Premise Planned Delivery Date Status of Delivery
      SD XX-CSC_PT-LO Central Framework 31/01/2022
      Validation Code for Communication of Series Deliveries 28/02/2022
      Validation Code for Communication of Series Settlement Management 28/02/2022
      ATCUD Print Layout Deliveries 28/02/2022
      MM XX-CSC-PT-LO Validation Code for Communication of Series - SelfBilling To be provided
      SD XX-CSC-PT-BIL Validation Code for  Series of SD Invoices 15/03/2022
      Validation Code for  Series of FI Invoices 31/03/2022
      ATCUD for FI Invoice Adobe Print Layout 31/03/2022
      ATCUD for SD Invoice Adobe Print Layout 31/03/2022
      ATCUD Validation Code for Series of Payment Receipts To be provided
      ATCUD for VAT on Cash Receipt Adobe Layout To be provided
      RE-FX RE-FX-LC-PT ATCUD Validation Code for communication of series - RE-FX 31/03/2022
      SAF-T communication - RE-FX 31/03/2022
      SAF-T XX-CSC-PT-LO ATCUD SAF-T Communication - Deliveries 28/02/2022
      ATCUD SAF-T Communication - Settlement Management 28/02/2022
      FI-LOC-SAF-PT Monthly SAF-T to report ATCUD 15/04/2022
      Monthly Self-billing SAF-T to report ATCUD To be provided
      Monthly SAF-T to report ATCUD for Payment Receipts To be provided
      XX-CSC-PT-FICA Monthly SAF-T to report ATCUD for FICA, IS-U (incl 3rd Party Billing, Self-Billing), Convergent Invoicing 31/03/2022
      FICA/IS-U/CI XX-CSC-PT-FICA ATCUD Validation Code for Series in FICA, IS-U, Convergent Invoicing 31/03/2022
      ATCUD for (non-SAP) Print Layouts 31/03/2022
      ATCUD Validation Code for Series for Self-Billing in IS-U To be provided
      ATCUD Validation Code for Series for FICA Payment Receipts and VOC Receipts To be provided
      CRM CRM-LOC ATCUD SAF-T Communication - CRM 15/09/2022
      Validation Code for Communication of Series - CRM 12/09/2022

       

      Cloud Solution

      Release Portaria 195/2020 and Despacho 412/2020 (ATCUD) - Cloud Planned Delivery Date Status of Delivery
      S4HANA CL 2111 e-invoice: ATCUD 30/11/2021
      S4HANA CL 2203 Central Framework 26/01/2022 Delivered
      ATCUD Print Layout Deliveries 26/01/2022 Delivered
      Validation Code for Communication of Series - Deliveries 16/03/2022
      ATCUD in SD print Adobe Layouts To be provided
      Monthly SAF-T ACR  to report ATCUD To be provided
      Validation Code for Communication of SD Invoices To be provided
      Webservice Central Framework (Automatic Communication - require CPI) 16/03/2022
      ATCUD SAF-T Communication Deliveries 16/03/2022
      S4HANA CL 2208 Monthly SAF-T ACR  to report ATCUD for Payment Receipts 27/07/2022
      ATCUD Validation Code for series of SD invoices 27/07/2022
      ATCUD Validation Code for series of FI invoices 27/07/2022
      ATCUD Validation Code for Series of Payment Receipts 27/07/2022
      Validation Code for Communication Settlement Management 27/07/2022
      Monthly SAF-T ACR  to report ATCUD for Settlement Management 27/07/2022
      Not yet a date Validation Code for Communication of Series - SelfBilling To be provided
      Self-Billing SAF-T ACR to report ATCUD To be provided

       

      Author's profile photo Pugal KP
      Pugal KP

      Hi Marta,

      'm working on QR code development for SD Billing. I've to develop QR code both in Smartform and Sapscript. Based on Technical specification received from Tax authorities there are few fields such as Document type, Document status, Document date, Unique identification of the document, Total taxes, Total amount of the document with taxes need to be picked up from SAF - T(PT) table.  We come across a table  - FIEUD_SDINV_H were it suits to pick up the values.

      But the issues is  before triggering output for this SD invoice, This table needs to be filled. This table in executed through T code - FIEU_SAFT by users and not automatically once Billing doc., got generated. Different users will trigger Billing in Different time. It would be really difficult to manage with the above said table.

       

      The question is ....

      1, As per the Technical specification, Can we have any other SAF - T(PT) table were we can refer. can you please share.

      2, What are the scanning apps can we use while testing the developed QR code ?  what are the scanning app recommended from Tax authorities ? Is there any simulator link is available were we can use it for testing. Your recommendation please.

      Thanks  & Regards,

      Pugal.

       

       

       

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Caros clientes / Dear Customers

       

      PT: Como pre-requisitos OP para as notas do ATCUD, será necessário terem em atenção a implementação de todas as notas referidas nas collective notes abaixo:

       

      EN: As pre-requirements for the implementation of ATCUD in OP, please consider the implementation of all the notes indicated in collective notes below:

      2375055 Despacho 8632/2014: Collective SAP Note for Despacho 8632/2014 Portugal Related to Digital Signature in FI and SD in S/4HANA
      2268552 Despacho 8632/2014: Collective SAP Note for Despacho 8632/2014 Portugal Related to Digital Signature in FI and SD

       

      PT: Relativamente às novas datas de entrega da solução temos:

      EN: Related with the new deliverie dates of the solution we have:

       

      On Premise Solution:

      Module Component Portaria 195/2020 and Despacho 412/2020 (ATCUD) - On Premise Planned Delivery Date Status of Delivery
      SD XX-CSC_PT-LO Central Framework 31/01/2022 Delivered
      Validation Code for Communication of Series Deliveries 31/03/2022
      Validation Code for Communication of Series Settlement Management 31/03/2022
      ATCUD Print Layout Deliveries 31/03/2022
      MM XX-CSC-PT-LO Validation Code for Communication of Series - SelfBilling To be provided
      SD XX-CSC-PT-BIL Validation Code for  Series of SD Invoices 31/03/2022
      Validation Code for  Series of FI Invoices 31/03/2022
      ATCUD for FI Invoice Adobe Print Layout 31/03/2022
      ATCUD for SD Invoice Adobe Print Layout 31/03/2022
      ATCUD Validation Code for Series of Payment Receipts To be provided
      ATCUD for VAT on Cash Receipt Adobe Layout To be provided
      RE-FX RE-FX-LC-PT ATCUD Validation Code for communication of series - RE-FX 31/03/2022
      SAF-T communication - RE-FX 31/03/2022
      SAF-T XX-CSC-PT-LO ATCUD SAF-T Communication - Deliveries 31/03/2022
      ATCUD SAF-T Communication - Settlement Management 31/03/2022
      FI-LOC-SAF-PT Monthly SAF-T to report ATCUD 15/04/2022
      Monthly Self-billing SAF-T to report ATCUD To be provided
      Monthly SAF-T to report ATCUD for Payment Receipts To be provided
      XX-CSC-PT-FICA Monthly SAF-T to report ATCUD for FICA, IS-U (incl 3rd Party Billing, Self-Billing), Convergent Invoicing 31/03/2022
      FICA/IS-U/CI XX-CSC-PT-FICA ATCUD Validation Code for Series in FICA, IS-U, Convergent Invoicing 31/03/2022
      ATCUD for (non-SAP) Print Layouts 31/03/2022
      ATCUD Validation Code for Series for Self-Billing in IS-U To be provided
      ATCUD Validation Code for Series for FICA Payment Receipts and VOC Receipts To be provided
      CRM CRM-LOC ATCUD SAF-T Communication - CRM 15/09/2022
      Validation Code for Communication of Series - CRM 12/09/2022
      OIL XX-CSC_PT-LO Validation Code for Communication of Series - Deliveries OIL 25/05/2022

       

      Cloud Edition

      Release Portaria 195/2020 and Despacho 412/2020 (ATCUD) - Cloud Planned Delivery Date Status of Delivery
      S4HANA CL 2111 e-invoice: ATCUD 30/11/2021
      S4HANA CL 2203 Central Framework 26/01/2022 Delivered
      ATCUD Print Layout Deliveries 26/01/2022 Delivered
      Validation Code for Communication of Series - Deliveries 16/03/2022
      ATCUD in SD print Adobe Layouts To be provided
      Monthly SAF-T ACR  to report ATCUD To be provided
      Validation Code for Communication of SD Invoices To be provided
      Webservice Central Framework (Automatic Communication - require CPI) 16/03/2022
      ATCUD SAF-T Communication Deliveries 16/03/2022
      S4HANA CL 2208 Monthly SAF-T ACR  to report ATCUD for Payment Receipts 27/07/2022
      ATCUD Validation Code for series of SD invoices 27/07/2022
      ATCUD Validation Code for series of FI invoices 27/07/2022
      ATCUD Validation Code for Series of Payment Receipts 27/07/2022
      Validation Code for Communication Settlement Management 27/07/2022
      Monthly SAF-T ACR  to report ATCUD for Settlement Management 27/07/2022
      Not yet a date Validation Code for Communication of Series - SelfBilling To be provided
      Self-Billing SAF-T ACR to report ATCUD To be provided

       

      Cumprs/ Best Regards

      Marta Pereira

      Author's profile photo Project Team_1
      Project Team_1

      Hello Marta Pereira,

      Any updates on the status on the delivery of the planned notes for the on Premise ATCUD code solution?

      Thanks in advance for your feedback.

      Best regards,

      JPB

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi JPB

      Just published the dates and the collective number note for ATCUD.

      Regards,

      Marta

       

      Author's profile photo Marta Pereira
      Marta Pereira

      Caros clientes / Dear Customers

       

      PT: Como pre-requisitos OP para as notas do ATCUD, será necessário terem em atenção a implementação de todas as notas referidas nas collective notes abaixo:

       

      EN: As pre-requirements for the implementation of ATCUD in OP, please consider the implementation of all the notes indicated in collective notes below:

      2375055 Despacho 8632/2014: Collective SAP Note for Despacho 8632/2014 Portugal Related to Digital Signature in FI and SD in S/4HANA
      2268552 Despacho 8632/2014: Collective SAP Note for Despacho 8632/2014 Portugal Related to Digital Signature in FI and SD

       

      PT: Foi criada uma nota coletiva para a solução do ATCUD. Por favor verifiquem a mesma, uma vez que detalha todos os passos e as notas das várias soluções/componentes.

      EN: A collective note was released to ATCUD solution. Please check the note, because it has all the steps and details for the notes released to each one of the solutions/components

       

      NOTA COLETIVA ATCUD - 3154599 - Collective Note : Portugal ATCUD Legal Change

       

      On Premise Solution:

      Module Component Portaria 195/2020 and Despacho 412/2020 (ATCUD) - On Premise Planned Delivery Date Status of Delivery
      SD XX-CSC_PT-LO Central Framework 31/01/2022 Delivered
      Validation Code for Communication of Series Deliveries 31/03/2022 Delivered
      Validation Code for Communication of Series Settlement Management 14/04/2022
      ATCUD Print Layout Deliveries 31/03/2022 Delivered
      MM XX-CSC-PT-LO Validation Code for Communication of Series - SelfBilling To be provided
      SD XX-CSC-PT-BIL Validation Code for  Series of SD Invoices 01/04/2022 Delivered
      Validation Code for  Series of FI Invoices 14/04/2022
      ATCUD for FI Invoice Adobe Print Layout 14/04/2022
      ATCUD for SD Invoice Adobe Print Layout 01/04/2022 Delivered
      ATCUD Validation Code for Series of Payment Receipts To be provided
      ATCUD for VAT on Cash Receipt Adobe Layout To be provided
      RE-FX RE-FX-LC-PT ATCUD Validation Code for communication of series - RE-FX 31/03/2022 Delivered
      SAF-T communication - RE-FX 31/03/2022 Delivered
      SAF-T XX-CSC-PT-LO ATCUD SAF-T Communication - Deliveries 31/03/2022 Delivered
      ATCUD SAF-T Communication - Settlement Management 14/04/2022
      FI-LOC-SAF-PT Monthly SAF-T to report ATCUD 15/04/2022
      Monthly Self-billing SAF-T to report ATCUD To be provided
      Monthly SAF-T to report ATCUD for Payment Receipts 30/04/2022
      XX-CSC-PT-FICA Monthly SAF-T to report ATCUD for FICA, IS-U (incl 3rd Party Billing, Self-Billing), Convergent Invoicing 14/04/2022
      FICA/IS-U/CI XX-CSC-PT-FICA ATCUD Validation Code for Series in FICA, IS-U, Convergent Invoicing 14/04/2022
      ATCUD for (non-SAP) Print Layouts 14/04/2022
      ATCUD Validation Code for Series for Self-Billing in IS-U To be provided
      ATCUD Validation Code for Series for FICA Payment Receipts and VOC Receipts To be provided
      CRM CRM-LOC ATCUD SAF-T Communication - CRM 15/09/2022
      Validation Code for Communication of Series - CRM 12/09/2022
      OIL XX-CSC_PT-LO Validation Code for Communication of Series - Deliveries OIL 25/05/2022

       

      Cloud Edition

      Release Portaria 195/2020 and Despacho 412/2020 (ATCUD) - Cloud Planned Delivery Date Status of Delivery
      S4HANA CL 2111 e-invoice: ATCUD 30/11/2021 Delivered
      S4HANA CL 2203 Central Framework 26/01/2022 Delivered
      ATCUD Print Layout Deliveries 26/01/2022 Delivered
      Validation Code for Communication of Series - Deliveries 16/03/2022 Delivered
      ATCUD in SD print Adobe Layouts To be provided
      Monthly SAF-T ACR  to report ATCUD 26/01/2022 Delivered
      Validation Code for Communication of SD Invoices To be provided
      Webservice Central Framework (Automatic Communication - require CPI) 14/03/2022 Delivered
      ATCUD SAF-T Communication Deliveries 16/03/2022
      S4HANA CL 2208 Monthly SAF-T ACR  to report ATCUD for Payment Receipts 18/05/2022
      ATCUD Validation Code for series of SD invoices 27/07/2022
      ATCUD Validation Code for series of FI invoices 27/07/2022
      ATCUD Validation Code for Series of Payment Receipts 27/07/2022
      Validation Code for Communication Settlement Management 27/07/2022
      Monthly SAF-T ACR  to report ATCUD for Settlement Management 27/07/2022
      Not yet a date Validation Code for Communication of Series - SelfBilling To be provided
      Self-Billing SAF-T ACR to report ATCUD To be provided

       

      Cumprs/ Best Regards

      Marta Pereira

      Author's profile photo Project Team_1
      Project Team_1

      Hello Marta Pereira,

      I have some questions about the mapping of the series with the FI number ranges which is required for the ATCUD set up!

      In the pdf attachment of oss note 3164607 the following sentence was written :

      "In FI, the combination of internal code and series must be unique per company code and fiscal year"

      Do I understand that cross PT company codes we can reuse the same serie code? If not, then we could have an issue as we have only 4 char for the serie code and the last two positions we must already indicate the fiscal year. In our system we have 3 PT company codes which are assigned to 239 number ranges. Only 6 number ranges are relevant for Digital signature!

      Can you please advise on how we should proceed on the mapping of the serie codes to our FI number ranges for those 3 PT company codes?

      Thanks in advance for your help.

      Best regards,

      JPB

      Author's profile photo Marta Pereira
      Marta Pereira

      Hi JPB

      The unique series is per Company Code/NIF and type os SAF-T document (Invoices, credit memos, etc).

      You also only communicate the FI documents relevants for digital signature + Receipts.

      The vendor, accounting and other type of documents that are not relevants for digital signature, except the receipts, should not be communicated for ATCUD.

       

      Regards,

      Marta