Product Information
ATCUD para Portugal: Prepare-se para o novo requisito legal da Portaria 195/2020
(Scroll down for the English version)
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
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:
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,
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
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
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
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:
…
TipoDoc: FT
NumInicialSeq: 2064123456 (for instance)
DataInicioPrevUtiliz: 01-01-2022
…
TipoDoc: FT
NumInicialSeq: 2066123456
DataInicioPrevUtiliz: 01-01-2022
…
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
Hi,
Thanks for the information about ATCUD code. Could you please clarify below points,
Thanks in advance.
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
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.
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
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
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
Olá Marta,
têm alguma novidade sobre este tema?
Obrigado
Cumprimentos
António Santos
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.
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
Olá Marta, muito obrigado pelas informações.
Tenho duas questões:
Agradeço antecipadamente.
Luis Mendes
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
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
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
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
Hello
Thanks so much for your sharing this information. Do you know in witch table ATCUD is storage?
Susana
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
Boa tarde Marta,
Envio de seguida algumas questões relativas ao ATCUD:
Muito obrigada pela ajuda
Catarina Alves
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
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)?
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
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.
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
Olá Marta
Já tem a decisão sobre a possível prorrogação do prazo?
Obrigado, att
Marcelo
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
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,
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,
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
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!
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
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
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
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
Olá Marta,
Obrigado pelo feedback,no entanto no seguimento da resposta da Marta ficamos com as seguintes dúvidas:
Obrigado
Cumprimentos
Olá António
Segundo a AT são todos os recibos impressos que devem conter o QR Code e o ATCUD.
Cumprs,
Marta
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
Hello Marta, thank you for the information.
Thank you for the information.
Hello Marta, thank you.
Is this also valid for qrcode?
Thanks
Hi Barbara
QR Code is still mandatory in 2022.
Regards, Marta
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
Hi Nicola
you should populate it with 0 (zero).
Like in Saf-t.
regards, Marta
Hello.. in this case, which is minimum number of 0000 should we key to populate QR code ?
thanks
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,
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
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
Dear all
Please consider the following information about planned dates/release for the solution
On Premise Solution
Cloud Solution
Best Regards, Marta
Hi.
Can you confirm:
Premise Solution - is manual range certification
Cloud Solution - automatic range certification (online)
?
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
Cloud Solution
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.
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:
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:
Cloud Edition
Cumprs/ Best Regards
Marta Pereira
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
Hi JPB
Just published the dates and the collective number note for ATCUD.
Regards,
Marta
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:
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:
Cloud Edition
Cumprs/ Best Regards
Marta Pereira
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
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
Hello Marta,
Thanks for the reply.
There is one piece that I am still missing about the ATCUD code set up! It's about the final logic of the ATCUD code generation that will be used on the printing of the invoices and on the QR code.
Currently the method "GET_ATCUD" was delivered by SAP with a temporary solution by setting it by default to '0'.
"METHOD get_atcud.
"temporary solution definat by tax authority
atcud = '0'.
ENDMETHOD."
Does SAP has already the final logic to generate the ATCUD code? If yes, which ossnote should we implement?
Thanks in advance for your quick reply.
Best regards,
JPB
Hi JPB
Please implement all the notes related with ATCUD for your module.
3154599 - Collective Note : Portugal ATCUD Legal Change
Example:
There are notes specific for the standard layouts delivered by SAP. There you will have that information.
Regards
Marta
Hello,
I’m trying to define the series for ATCUD in the system and I receive the message:
ATCUD naming convention for series not enabled yet
Nº mensaje: SIPT049
Diagnosis
You tried to create a new series that adheres to the naming conventions
required for ATCUD, for example, starting with F.
System Response
The system doesn't allow you to create the series because the new naming
convention hasn't been enabled for the corresponding application area
yet.
I thought that by implementing the notes I could already create the series here, but that's not the case.
Can you help me?
Regards,
Mayte.
Hi Mayte
Are you creating the new series for FI documents (FI invoices, FI debit or credit memos)? For FI the series should start with F
But if you intend to create documents from SD (invoices, credit or debit memos, ...) then the series should start with B.
Also the series should have 4 characters, were the 1st one is the letter from the module from were the document is issued.
Hope that this help you to clarify your doubts.
Regards, Marta
Yes, I think we have something wrong implemented because also I have a dump when I try to display SIPT_NUMBR_FI_V2 table.
Categoría Error de programación ABAP
Err.tmpo.ejec. SYNTAX_ERROR
Programa ABAP SAPLSIPTCUST2
Anwendungskomponente FI-LOC
Fecha y hora 30.05.2022 10:28:58
Any idea? Had someone this dump?
I solved the dump. I had not implemented the corrections of the 3170039 note.
Hello Marta Pereira,
We are doing some testing regarding the new ATCUD for the Deliveries.
In our test we notice that:
Maybe we have some OSS notes that are not implemented in our system that are causing these issues.
Is there in any OSS Note a Detail Guideline manual on how to perform the customizing of this functionality?
Thanks in advance for your help.
Best regards,
Carlos Silva
Hi Carlos
If you are facing this issue, were Series is always 01 please create one incident, because there is a problem.
It´s not supposed to be like that.
Component XX-CSC-PT-LO
Regards
Marta
Hi Marta,
This issue was solved implementing the OSS Note 2823903
Thanks and Best Regards,
Carlos Silva
Hello Marta,
In the table SIPT_BKPF the invoice number that is showing the system is DP F269/2600000003.
In the SAFT appears in this way. Is it correct?
<InvoiceNo>DP F269/2600000003</InvoiceNo>
<ATCUD>12345678-2600000003</ATCUD>
Regards,
Mayte.
Hello Maria Teresa,
can I ask you in which part of the customizing have you filled the value "12345678" (I think corresponding to the Validation Code)?
Also, how do you create the ATCUD with the SAFT functionality? I refer to the tag <ATCUD>12345678-2600000003</ATCUD>.
It is available in some standard table?
Thank you so much,
Federica
Hi,
you can execute transaction GLO_PT_SVC for customizing the validation code.
ATCUD in SAFT funcionality, you have when you implement the OSS notes included in 3154599 - Collective Note : Portugal ATCUD Legal Change for SAFT.
Hope it helps.
Mayte.
Hi Frederica
You don´t have in any table the ATCUD.
We use the validation code plus the internal document number on line. This means ATCUS is created in the moment when is used (printing, saf-t, qr code)
Regards
Marta
Hi Maria Teresa
Yes, you are correct
Regards,
Marta
Thanks Marta! i think I'm ready !
Mayte.
Hi Marta Pereira ,
we have a question about de naming convention of FI series:
In the document PT_ATCUD_FI_IMG_Documentation.pdf (note 3170039 ) in the "Naming Conventions for Series IDs (ATCUD)" part are the following examples:
BA19 (B = SD billing, A1 = number range, 9 = year-independent)
FZ1A (F = FI, Z1 = number range, A = 2022)
FZ1B (F = FI, Z1 = number range, B = 2023)
FZ1C (F = FI, Z1 = number range, C = 2024)
but there isn't an example of FI year independent range. We understand that works like the SD range:
FZ29 (F = FI, Z2 = number range, 9 = year-independent)
but we apreciate if you can confirm that point.
Thanks!!
Hi Agustín
The only character that is mandatory is the letter that correspond to the module.
The example that we gave was always considering the independent year as a 9, but you don´t need to follow the same as the example
But if you want to follow is like you mentioned before FZ29 but it could also be for example FZ2A ou FZ20. You can decide.
Regards
Marta
Thanks Marta for your time,
the key point is not the last character, but rather that in year-independent FI ranges, it is not necessary to declare new series every year. From your answer I think it is clear that it is so.
regards
Hi Agustín
You are right. The independent year NR only needs to be communicated one time, independent of the module from were is billing.
Regards
Marta
Hi Marta,
We already implemented the SAFT OSS notes reported in the collective note for ATCUD, however when I generate the SAFT file for accounting, I don't see any specific tag for ATCUD.
This feature it's not yet available?
Thank you.
Regards,
Isabel
Hi Isabel
Accounting SAFT don´t have ATCUD field.
ATCUD is only for the tags related with source documents - 4.1; 4.2; 4.3 and 4.4
Regards
Marta
Hi Marta,
After finishing the delivery series in SIPT_NUMBR_OBD_V using ATCUD report FINISH. How to define a new delivery series for the same delivery document. An error is being thrown 'there is already entry for the same company code.' in SPRO settings.
Thank you,
Soumyakanti.
Hi Soumyakanti
Is no possible, because it´s like you had already communicated the new NR with that series to Tax Authorities.
This is the way to guarantee that the same NR/Series is not communicated twice.
We have the same validations in Quality as we have in Productive.
In this case you need to create a new NR (you can do the splitting of the finished one)
Regards
Marta
Hi Marta,
Thank you for the quick response. We have entered a new number range. However, it is giving error by only considering the document type and not both. The document type and company code will always remain the same, hence an error should not come based on that but rather the number range number.
I can see the note which says 'deleting is allowed' after finishing. So can we delete the old entry from the table or there is provision to archive it?
Thank you,
Soumyakanti.
Hi Marta,
Are there any notes that talk about the correct/best way obtain validation code for TEST systems for SAP ATCUD manual solution e.g. insert dummy in table or request test user IDs for portal, etc.
Thank you,
Soumyakanti.