ATCUD para Portugal: Prepare-se para o novo requis... - Page 2

AilaneKuhn · ‎2021 Sep 22

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

- SAP ERP: 2268552
- SAP S/4HANA: 2375055

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.

Guia de solução de problemas e perguntas frequentes

Consulte o SAP Knowledge Base Article 3274103 para um guia de solução de problemas e respostas a perguntas frequentes para ajudar você no processo de implementação da solução.

Fique atento às notícias mais recentes

Fique atento! Pretendemos atualizar este blog regularmente.

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

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

Até à próxima,

Ailane Kuhn

#SAPGoGlobal #SAPLocalization

***

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

Hi everyone,

As you might be aware, the Portuguese government published Portaria 195/2020 and, together with the QR code, introduced AT-Validation Code (ATCUD) as a new legal requirement.
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:

- SAP ERP: 2268552
- SAP S/4HANA: 2375055

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!

Troubleshooting Guide and FAQ

Check the SAP Knowledge Base Article 3274103 for a troubleshooting guide and answers to frequently asked questions to help you in the implementation process.

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

former_member713824 · ‎2021 Dec 15

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
RE-FX	RE-FX-LC-PT	SAF-T communication - RE-FX	31/03/2022
SAF-T	XX-CSC-PT-LO	ATCUD SAF-T Communication - Deliveries	28/02/2022
	XX-CSC-PT-LO	ATCUD SAF-T Communication - Settlement Management	28/02/2022
	FI-LOC-SAF-PT	Monthly SAF-T to report ATCUD	15/04/2022
	FI-LOC-SAF-PT	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
CRM	CRM-LOC	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

former_member773383 · ‎2022 Jan 03

Hi.

Can you confirm:

Premise Solution - is manual range certification

Cloud Solution - automatic range certification (online)

?

former_member713824 · ‎2022 Feb 09

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
RE-FX	RE-FX-LC-PT	SAF-T communication - RE-FX	31/03/2022
SAF-T	XX-CSC-PT-LO	ATCUD SAF-T Communication - Deliveries	28/02/2022
	XX-CSC-PT-LO	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
CRM	CRM-LOC	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
Not yet a date	Self-Billing SAF-T ACR to report ATCUD	To be provided

former_member791216 · ‎2022 Feb 21

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.

former_member713824 · ‎2022 Mar 16

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
RE-FX	RE-FX-LC-PT	SAF-T communication - RE-FX	31/03/2022
SAF-T	XX-CSC-PT-LO	ATCUD SAF-T Communication - Deliveries	31/03/2022
	XX-CSC-PT-LO	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
CRM	CRM-LOC	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
Not yet a date	Self-Billing SAF-T ACR to report ATCUD	To be provided

Cumprs/ Best Regards

Marta Pereira

former_member234717 · ‎2022 Mar 31

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

former_member713824 · ‎2022 Apr 01

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
RE-FX	RE-FX-LC-PT	SAF-T communication - RE-FX	31/03/2022	Delivered
SAF-T	XX-CSC-PT-LO	ATCUD SAF-T Communication - Deliveries	31/03/2022	Delivered
	XX-CSC-PT-LO	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
CRM	CRM-LOC	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
Not yet a date	Self-Billing SAF-T ACR to report ATCUD	To be provided

Cumprs/ Best Regards

Marta Pereira

former_member713824 · ‎2022 Apr 01

Hi JPB

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

Regards,

Marta

former_member234717 · ‎2022 Apr 12

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

former_member713824 · ‎2022 May 18

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

Mayte_Cosme · ‎2022 May 30

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.

former_member713824 · ‎2022 May 30

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

Mayte_Cosme · ‎2022 May 30

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?

cacsilva · ‎2022 May 31

Hello Marta Pereira,

We are doing some testing regarding the new ATCUD for the Deliveries.

In our test we notice that:

The new series ex:"D001" set up in table SIPT_NUMBR_OBD is not used by the web Service.
- In the SIPT_LIKP the Reference was set up to LF D001/1300000153 and on the Web Service Table WSPT_LIKP was LF 1/1300000153

We notice that the SAP Standard method that builds the string to populate the QRCode in the deliveries is still using the default value "0".

A minor display issue when consulting the table WSPT_LIKP with Tx SE16 the last field is not displayed ex: it appears: LF 1/130000015 instead of the full LF 1/1300000153 the value is there because we can see the full reference number in tx WSPT_MONI

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

Mayte_Cosme · ‎2022 Jun 02

I solved the dump. I had not implemented the corrections of the 3170039 note.

Mayte_Cosme · ‎2022 Jun 02

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?

Regards,

Mayte.

former_member267368 · ‎2022 Jun 08

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

Mayte_Cosme · ‎2022 Jun 08

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.

former_member713824 · ‎2022 Jun 08

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

former_member713824 · ‎2022 Jun 08

Hi Maria Teresa

Yes, you are correct

Regards,

Marta

former_member713824 · ‎2022 Jun 08

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

Mayte_Cosme · ‎2022 Jun 08

Thanks Marta! i think I'm ready !

Mayte.

r_daneel · ‎2022 Jun 08

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

former_member466830 · ‎2022 Jun 21

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

former_member713824 · ‎2022 Jun 21

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

former_member713824 · ‎2022 Jun 21

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

r_daneel · ‎2022 Jun 21

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

former_member773897 · ‎2022 Jun 22

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.

former_member713824 · ‎2022 Jun 22

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

former_member773897 · ‎2022 Jun 22

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.

former_member713824 · ‎2022 Jun 22

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

former_member773897 · ‎2022 Jun 22

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.

former_member234717 · ‎2022 Jul 05

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

cacsilva · ‎2022 Jul 05

Hi Marta,

This issue was solved implementing the OSS Note 2823903

Thanks and Best Regards,

Carlos Silva

former_member713824 · ‎2022 Jul 05

Hi JPB

Please implement all the notes related with ATCUD for your module.

3154599 - Collective Note : Portugal ATCUD Legal Change

Example:

3114759	Digital Signature Portugal: ATCUD - Print Programs for Layout SIPT_INV
3134492	DS PT: QR Code correction and ATCUD SD/FI Layouts - OP
3153031	Digital Signature Portugal: ATCUD SD and FI - Mapping for QR Code

3140877

Portugal ATCUD Legal Change: Code Changes for SD Deliveries

There are notes specific for the standard layouts delivered by SAP. There you will have that information.

Regards

Marta

micaelmesquita · ‎2022 Jul 11

Bom dia Marta,

A integração via Cloud ainda se mantêm? A SAP vai disponibilizar alguma alternativa (sem falar da manual)?

Atentamente,

Micael Mesquita

former_member812679 · ‎2022 Jul 13

Olá Marta, bom dia,

A solução standard recomenda o uso do SAP Cloud Integration para comunicação com a AT.

Existe alguma documentação que suporte o setup dessa integração.

Muito obrigado

JB

former_member719805 · ‎2022 Jul 19

SIPT_NUMBR_SD_V2 Syntax Error

We are implementing note 3163798 - Digital Signature Portugal: ATCUD SD and FI Maintenance Views and it gives us the following syntax error:

Include LSIPTCUST2F00
Field "SIPT_NUMBR_SD_V2-<KEYFIELD>" is unknown. It is neither in one of
the specified tables nor defined by a "DATA" statement. "DATA"
statement.

Code: SELECT SINGLE FOR UPDATE * FROM SIPT_NUMBR_SD WHERE
NRRANGENR = SIPT_NUMBR_SD_V2-NRRANGENR AND
LEAD_DOCTYPE = SIPT_NUMBR_SD_V2-<keyfield> .

View SIPT_NUMBR_SD_V2 has been generated with report NOTE_3151456. We realize that the filed LEAD_DOCTYPE doesn’t exist.

Do you know how can we solve it?

Thank you in advance.
Raquel

The maintenance view SIPT_NUMBR_SD_V2 fields are:

MANDT
NRRANGENR
SERIES
BUKRS
INVOICE_TYPE

Please, can someone compare with the one in your system? Thank you

former_member267368 · ‎2022 Jul 20

Hello Maria Teresa,

thank you for your suggestion, we have implemented all the notes and we are customizing the table SIPT_NUMBR_FI_V2 following the SAP guide, but, opening it with SM30, the field "Edit" --> "New Entry" is grey, so it is not possible for us to update the table.

Do you have any suggestion to me it editable?

Thank you,

Federica

nogueirapa · ‎2022 Jul 20

Hello Elena,

you can't add new entries in this view, you can only change them.

You will have entries to maintain as soon as you have added entries in SIPT_NUMBR_FI_V view that match the requirements for the FI series.

I hope this is clear enough.

BR

former_member267368 · ‎2022 Jul 21

Hi Paula,

thank you so much!!

Trying to add the entries in the table SIPT_NUMBR_FI_V with the series F000 the error message is:

ATCUD naming convention for series not enabled yet

Message no. 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.

Shoul we inizialize the new series number for ATCUD somewhere in the customizing?

Thanks a lot,

Federica

former_member799835 · ‎2022 Jul 28

Ola Marta, bom dia,

Consegue nos dar algum feedback sff.

Precisamos de encontrar alguma documentação que suporte a integração com a AT via CPI.

Obrigado

JB

former_member816491 · ‎2022 Aug 09

Hi Team,

Even after implementing the suggested notes 3151456 - Digital Signature Portugal: ATCUD SD and FI - Prerequisite Objects Maint. View for ATCUD we are unable to find the configuration path as suggested by SAP to enable the ATCUD.

Assign a SAF-T Document Type to each number range in Customizing for Sales and Distribution under Billing -->Billing Documents--> Country-Specific Features--> Country-Specific Features for Portugal-->Digital Signature--> "Assign SAF-T Document Types to Number Ranges (SD) (SIPT_NUMBR_SD_V2 view)".

Could you please let me know if there are any other SAP note to be implemented to get the customizing path enabled (or) table (or) transaction to get use of SIPT_NUMBR_SD_V2 for ATCUD number range on invoice.

Please find the attached screenshot of the configuration path that is currently shown in system.

Configuration Path

Thanks & Regards,

Ganesh Kumar.V

former_member713824 · ‎2022 Aug 09

Hi Ganesh

The collective note have the notes that you need to implement by module.

Please confirm that you have implemented all the notes for the SD module.

Regards

Marta

former_member774751 · ‎2022 Aug 09

Dear Marta:

We are going to implement the ATCUD solution for Portugal but we have some conceptual doubts related to the series communication process/managing to the Portugal tax authority and how testing it.

How can be test the ATCUD development (in a test environment) when reporting the series identifiers in a manual way (through Portugal Tax authority portal)?

Is it possible reporting a serie identifier in a test way for manual registration (not web service) trough Portugal tax authority portal?

If it´s possible; must it have a special code?

If it´s not possible; how should it be tested?

Thank you in advance.

Best Regards,

João_Terenas · ‎2022 Aug 09

Hi,

we are facing the same issue for deliveries it is not possible to create a new entry for a new number range for the same delivery type/company, but according to SAP's June 9 presentation of the new settings to be made for a delivery type/company that already exists in the SIPT_NUMBR_OBD_V table, it was only necessary to copy the entry and assign a new interval and a new series.

We have already opened a message in SAP and we are awaiting for a reply.

It makes no sense that we need to create new types of deliveries to define new numbering ranges

for existing processes and for existing remittance/company types in the SIPT_NUMBR_OBD table.



Thanks in advance,

Best regards

Catarina Alves

former_member816491 · ‎2022 Aug 10

Hi Marta,

You mean the collective note 3164607 - Digital Signature Portugal: Activation of ATCUD Series for SD Billing to be checked and implement all the notes mentioned in this?

I have implemented below 6 notes so far...

3163798 Digital Signature Portugal: ATCUD SD and FI - Maintenance Views

3151456 Digital Signature Portugal: ATCUD SD and FI - Prerequisite Objects Maint. View

3153032 Digital Signature Portugal: ATCUD SD and FI - Prerequisite Objects Search Help

3146767 Digital Signature Portugal: ATCUD SD and FI - Prerequisite Objects Utility Classes

3149338 Digital Signature Portugal: ATCUD SD Invoices – Validations

3136989 - Portugal ATCUD Legal Change : Framework DDIC Objects - SAP ONE Support Launchpad

Please check and let me know what all other notes that need to be implemented along with these notes.

Thanks & Regards,
Ganesh Kumar.V

former_member713824 · ‎2022 Aug 10

Hi Ganesh

If after the implementation of the notes you still don´t have the path for the customization visible, please open one incident so that the development team can see what is missing in your system.

Component: XX-CSC-PT-BIL

Regards

Marta

former_member713824 · ‎2022 Aug 10

Hi Teodoro

Tax Authorities provide 2 portals, one for development and another one for productive communication.

Also they provide a "manual" communication environment

You have the link for the TA portal below, were you have all the information provided by them, and the links for the different communications.

https://info.portaldasfinancas.gov.pt/pt/apoio_contribuinte/Faturacao/Comunicacao_Series_ATCUD/Pagin...

Hope that this information is relevant and that could help you.

Regards,

Marta

former_member713824 · ‎2022 Aug 10

Hi Raquel

In this case is better for you to open one incident so that developers can see what is the issue with your implementation.

Component: XX-CSC-PT-BIL

Regards,

Marta

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