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

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 · ‎2022 Aug 10

Bom dia JB

Penso que a informação que pretende está em

https://api.sap.com/package/SAPS4HANAIntegrationwithPortugalTaxAuthority/overview

Cumprs,

Marta

former_member774751 · ‎2022 Aug 10

Hi Marta:

Thank you very much for your answer and the link.

I have been reviewing the documents generated by the AT and unless I am mistaken, the only existing option to report a serie identifier in a test way is doing it by web service.

The problem is that I have not seen the way to do it under manual registration. I don´t know whether it´s possible or not….

If anyone is in the same situation, I would appreciate the advice.

Thank you in advance.

Regards,

cepsa-sga-sap-oss-notes · ‎2022 Aug 10

Dear Marta,

do we have any news about ATCUD for selfbilling documents?

Best Regards

Alejandro.

micaelmesquita · ‎2022 Aug 17

Boa tarde,

Estou a ter problemas (em ambiente de testes) com as operações de cancelar e finalizar séries, mas o registo e a consulta está bom. Mais alguém com esse problema?

Cumprimentos.

cepsa-sga-sap-oss-notes · ‎2022 Aug 18

Também temos problemas, porque o comprimento do ambiente ATCUD para teste é maior do que o esperado, portanto, para SAP não é válido

former_member234717 · ‎2022 Aug 24

Hello Marta,

I have some concerns about the maintenance of the series validation code via trans GLO_PT_SVC.

In our production system we have a set up with 3 company codes in Portugal but all are belonging to the same legal entity.

Now when I maintain in FI the series by number range for the 3 company codes, see below:

CoCd No Year Signature Doc. Type Series

PT1 16 2023 X DG F16A
PT1 18 2023 X DR F18A
PT2 16 2023 X DG F16A
PT2 18 2023 X DR F18A

I only get one record for the series identifier in the maintenance table list via trans GLO_PT_SVC!

F16A

F18A

But that means that the same validation code will be used for the 3 company codes in which they are using different number ranges for document type DR & DG! Would this cause issues with the local tax authority?

I tried by putting different series for the other company codes but that doesn't work as well.

Please advise.

Thanks in advance for your feedback.

Best regards,

JPB

former_member713824 · ‎2022 Aug 24

Hi JPB

It isn´t supposed to have 3 companies with the same legal entity.

The communication to TA is by NIF, and this is the reason why you can´t report the same NR for 2 companies with the same legal entity.

The only approach that I see is to create different document types per company with different NR/Series.

PT1 DG 16 FXX1

PT1 DR 18 FXX1

PT2 DH 17 FXX2

PT2 DS 19 FXX2

....

But you need to test it, because like I said our solution is according with the rules that you should have only one company code per NIF.

Also please let me also advise you about the accounting saf-t file. With this solution this will only work if you have a unique CC with all the information of accounting.

Regards

Marta

former_member234717 · ‎2022 Aug 24

Hello Marta,

But we have the same issue for SD billing documents!

For the 3 company codes we have 3 different number range codes and numbers in SD set up with a different serie code but still only one record is displayed in the maintenance table list via trans GLO_PT_SVC.

Please advise on this part.

Thanks in advance for your feedback.

Best regards,

JPB

former_member234717 · ‎2022 Aug 25

Hello Marta,

After some further investigation I found the reason why in both cases it was not displayed in the maintenance table via trans GLO_PT_SVC!

The SAF-T document type mapping was not mapped with the new different series of the other PT company codes (with same VAT n°).

Now we can maintain the validtion codes for each of those number ranges.

But still we need to test in depth in quality system to see if there are no other constraints with this organizational set up!

Best regards,

JPB

claudia_kurose · ‎2022 Aug 30

Hello,

I have same doubt. In AT website I can only see manual registration to the Production system, but looks series in test mode must be as AA as I have reading in some place.

The test environment is valid to developers (as I also understood) only.

So, how to test as user the manual communication with AT?

And, after that, is there a guide about what should be customized in SAP to have the series validation working?

Thank you.

Claudia Kurose

cristiana_masu · ‎2022 Sep 05

Hello,

Could you please help me clarify the following?

For year dependent NR in FI, there is no need to create new number ranges, but it is enough to create and register a new series each year?

For example:

NR Year From To Serie

DR 2021 100 - 199 1

DR 2022 100 - 199 F001

DR 2023 100 - 199 F002

DR 2024 100 - 199 F003

Thank you.

Best regards,

Cristiana

former_member785060 · ‎2022 Sep 05

Hello Marta,

Currently in our system we have the following SD number ranges valid for Portugal (table SIPT_NUMBR_SD):

Billing type          Number range   Series

ZF2                        E6                         1

ZF1                        E7                         1

ZCDN                    E8                          1

ZL2                        E9                          1

ZSDR                     EA                         1

ZEXI                      EB                         1

ZEDR                   EC                         1

ZG2                       EE                          1

ZCCN                   EF                          1

ZECR                     EG                         1

ZSCR                    EH                         1

ZPF                       EJ                          1

Each billing type has its own number range, and the series is always 1. The NR are valid since 2015 and all are marked relevant for digital signature (except ZPF) – digital signature is implemented in our system for a really long time. Our client does not have webservices, we will go with the manual solution.

The SAFT invoice type – SD invoice is:

FT: ZF2, ZF1,ZEXI

NC: ZSCR, ZG2, ZECR

ND: ZSDR, ZEDR

In this context, we are unclear if:

new SD number ranges should be created

the Series should be changed and made unique, eg:

Billing type          Number range   Series

ZF2                        E6                         1

ZF1                        E7                         2

ZCDN                    E8                          3

Thank you,

Maria

rainer_sinn2 · ‎2022 Sep 06

Hello Marta,

When creating the new number ranges for deliveries in SIPT_NUMBR_OBD_V it is necessary to delete existing entries when you want to create new entries with the same delivery type. In this case a warning comes up with following text:

It's not recommended to switch off or on the digital signature generation.
Stopping the digital signature is not a legal procedure.

I think that the deletion is necessary to continue but the message sounds strange.
Can you confirm that this is the correct way?

Best regards
Rainer

JSilva · ‎2022 Sep 08

Bom dia Marta,

Estive a rever o tópico e tenho uma dúvida, na resposta "3 - Será sempre através do SAP Cloud Integration", queres dizer que em SAP ECC não temos forma de criar o WebService , nem podemos usar um sistema PO para o fazer, é isso? ou queres dizer que a solução suportada pela SAP é só através SAP Clould Integration?

Obrigado,

Jorge Silva

former_member719805 · ‎2022 Sep 16

Hi Marta,

Could you please explain us in which segment of Invoice Idoc will be the ATCUD information?

Is there any Sap Note the explains it?

Thank you in advance.

Best Regards.

Raquel.

former_member466830 · ‎2022 Sep 22

Hi Marta,

Could you please explain us, where we can update the user/ password in SAP, and also where we can request the certicate keypair for test and production?

Thank you.

Regards,

Isabel

former_member234717 · ‎2022 Sep 27

Hi Marta,

A pratical question about the ATCUD code related to billing documents to be printed and/or submitted through IDOC for E-invoicing !

I understood that the first part of the ATCUD code is the validation code and the second part the document number.

What if the official invoice number is not the billing document number but the accounting document number, which number should we use in the ATCUD code? Taken into account that SD billing documents of credit notes are in the same SD billing document number range as the normal invoices but when released to accounting there is a split of FI document type between invoices and credit notes with a different number range!

Please advise if the document number must be the one that was communicated to the authorities by serie (billing doc n°) or it must always be the official invoice document n° (accounting doc n°) ?

Thanks in advance for your quick reply.

Best regards,

JPB

yannickmercier · ‎2022 Sep 27

dear all..

stupid question :

I understood that ATCUD number is Serial number / internal invoice number (VBRK-VBELN) .

I understood that Serial number can be asked to AT for a range, and re use from year to year, as long as we do not change range rof numbering.

So, unless I missed something, we can use same serial number for our full invoice range until the end of range (in our case, in some years.. )

here is my stupid question :

so.. why shall we need a webservice to get serial number from AT ? at least, we request once a time every 10 years and that's it..

I missed something ?

last question : what will apped to electronic signature ? (SIPT_VBRK-SIGNATURE) ? shall we continu or is this over ?

thanks for your answer.

lpisco · ‎2022 Sep 30

Hi all,

Collective Note : Portugal ATCUD Legal Change (3154599) does not include a Self-Billing MM solution, using the series identifier 'S' does not enable the series in GLO_PT_SVC validation cockpit. Self-Billing MM implementation itself defines '1','2' or '3' for the series maintenance in SIPT_NUMBR_MM_V’ (note 1550481).

Please let us know when the solution will be available.

es0230 · ‎2022 Oct 03

Hi

we are facing the same issue in deliveries customizing setup. Do you know how we should do it?

Best regards

Marcos Alonso

former_member724869 · ‎2022 Oct 03

Hi,

Did someone resolve this error? we're getting the same error when trying to add a FI number range series

ATCUD naming convention for series not enabled yet

EAS28 · ‎2022 Oct 03

Boa tarde marta_pereira,

O documento não certificou.

Fiz a parametrização para 2023, já que em 2022 não é possível não consigo mais fazer actualizar em 2022, pois está em uso.

Exemplo:

SIPT_NUMBR_FI_V

19 2023 1900000000 1999999999 DR Fatura de clien F193 01.01.2023

SIPT_NUMBR_FI_V2

XPTO 19 2023 F193 Fatura

GLO_PT_SVC

F193 Fatura (FT) FI 1900000000 30.09.2022 Ativo (A) Atualização manual (PF) AT1234XXXX

Poderia me dar uma dica do que está a faltar,

Cordialmente,

Eloisa Silva

former_member713824 · ‎2022 Oct 03

Hi Teodoro

It was supposed to have the manual test portal delivered by TA.

Maybe you can open one question in e-balcão to TA asking when this will be available.

Regards, Marta

former_member713824 · ‎2022 Oct 03

Hi Claudia

If the communication is manual, there is no validation from SAP side if you are introducing the Validation Code in a correct way.

The only validation that we can have in this situation are the ones that are available in the law (for example more than 8 characters, the letters A,E,I,O and U are not accepted and only the special characters defined by law are accepted

Regards,Marta

former_member713824 · ‎2022 Oct 03

Hi Alejandro

We are working in the solution and we are planning to deliver it in middle of November.

Regards,

Marta

former_member713824 · ‎2022 Oct 03

Boa tarde

Podem por favor abrir incidente para esta situação?

Obrigado,

Marta

former_member713824 · ‎2022 Oct 03

Hi Maria

You need to have unique series per type of document.

To obtain that and guarantee that you need to create new NR and a unique series to each one of that NR.

For example for ZFI E7 1

you need to create for example a new combination: ZFI XX BXX1

Regards,

Marta

former_member713824 · ‎2022 Oct 03

Hi Raquel

We did not deliver any solution for IDOC.

Regards,

Marta

former_member713824 · ‎2022 Oct 03

Hi Isabel

I that information is explained in the notes for automatic communication.

Regards,

Marta

former_member713824 · ‎2022 Oct 03

Hi JBP

This is not according with the best practices from SAP and from digital signature.

The number of the invoice should be the SD number and not the accounting document number.

Or are you talking about a specific scenario beside the traditional ones using VF01?

Regards,Marta

former_member713824 · ‎2022 Oct 03

Hi y.ragot-mercier

You don´t need to use the automatic communication, and this is the reason why we offer both solutions.

In your case you only have a few NR to communicate the series, and for that you can use the manual communication, but there are customers with lot´s of documents to report and in that case the automatic communication makes sense.

Also for customers in this situation with many documents in Year dependent can make sense the automatization.

Regards,

Marta

former_member713824 · ‎2022 Oct 03

Hi Luis

Selfbilling solution was still not released.

We are planning to release it in middle of November.

Regards,

Marta

former_member713824 · ‎2022 Oct 03

Olá Eloisa

O processo de certificação é igual ao que tem sido até agora. Terão de fazer a entrada na SIPT_NUMBR_FI_V e SIPT_NUMBR_FI_V2

Se a vossa data de inicio de utilização do documento é 01.01.2023, só a partir dessa data o sistema valida se leva ATCUD ou não.

Cumpr,

Marta

former_member234717 · ‎2022 Oct 04

Hello Marta,

For all countries which are active on our production system it's always the accounting document number and not the billing document n° which is the official invoice number to the customer! For country Portugal when billing documents are released to accounting there is a split by FI document type between invoices and credit notes with a different FI number range!

Example:
Document type 'RV' invoice with FI doc n° 1121300463 (=billing doc 0976006666) and document type 'ZY' credit note with FI doc n° 9121300008 (=billing doc 0976006826).

ATCUD code set up:
one validation code '1234' which is linked to the billing doc n° range 976000000 - 978999999 in table GLO_PT_SVC

but on the printed documents and E-inv. the following data is taken:
Invoice => ATCUD code '1234'-1121300463
Credit note => ATCUD code '1234'-9121300008

Is this set up allowed?

Thanks in advance for your advice.

Best regards,

JPB

EAS28 · ‎2022 Oct 04

Bom dia Marta,

Crie um documento em FI com data de lançamento futura 01.01.2023 e não certificou. O sistema não irá reconhecer essa data por ser lançamento futuro?

Cordialmente

Eloisa Silva

vseverino · ‎2022 Oct 04

Hello Marta,

quick question, are there any instructions for executing the SAFT report after all notes for ACTUD have been applied?

Regards,

Venecia

former_member713824 · ‎2022 Oct 04

Hi Venecia

The field ATCUD is in the file since 2016 but it was populated with zero.

After the communication of the series to TA that field should be populated with ATCUD information, but we had already released the notes to update the information of that field.

Regards,

Marta

former_member713824 · ‎2022 Oct 04

Boa tarde Eloisa

Tem o novo intervalo de numeração/serie com a flag de assinatura digital?

Se sim não há motivo nenhum para os docs não serem assinados.

Verificou a tabela SIPT_BKPF e viu se o doc está na tabela?

Cumprs,

Marta

former_member234717 · ‎2022 Oct 04

Hello Marta,

Another way to solve the validation code issue on the SD number ranges if FI number ranges are the official invoice numbers to the customer, is to switch off the digital signature flag in configuration table "Record Number Ranges for Digital Signature of Billing Documents (SD)"!

Instead we switch the digital sign flag on the FI document type "RV" in config table "Record Number Ranges for Digital Signature of Invoices (FI) ".

With this set up the validation codes are only set at FI level and are in sync with the official invoice numbering to the customer as well as in the SAF-T extractions.

Please advice on this proposal.

Thanks in advance for your feedback.

Best regards,

JPB

former_member817342 · ‎2022 Oct 05

Hi Marta, Rainer, All

We are facing the same issue as above regarding the delivery number ranges set up. I cannot find any comment/confirmation on the process. Can you please confirm how to proceed?

I have additional question. Currently out SIPT_NUMBR_V table has the following entry:

No. Del.Type Signature Series CoCode

51 XF Outbound Delivery X 1 PO

52 XLF DeliveryCustCons X 1 PO

53 XR Returns delivery X 1 PO

54 XLO Delivery w/o ref. P X 1 PO

55 XLCC ICY Delivery X 1 PO

56 XL Returns (pur.ord) X 1 PO

57 XB Delivery for Subcon. X 1 PO

X means that there are marked for Digital Signature

However when editing the existing number range and assigning new Series the system does not give any warning or error and allows to save the changes. Is it normal ? or do we miss any set up in our system?

51 XF Outbound Delivery X D511 PO

Thank you in advance and best regards

Barbara

jagadeesh_arumugam · ‎2022 Oct 06

Hello Marta,

After we Run the transaction GLO_PT_SVC, there is no option to perform 'WS Registration'.

I am not sure if it's because of missing Web service configuration.

Can you please share the information how to setup webservice configuration to communicate with Portugal tax authority?

PS: We are using SAP ECC System not S/4 HANA.

Thanks & Regards,

Jagadeesh

jagadeesh_arumugam · ‎2022 Oct 06

Hello Marta,

Please ignore the above request.
I have got the required information, If it doesn't work I will come back to you.

Thanks,

Jagadeesh

EAS28 · ‎2022 Oct 06

Bom dia Marta,

Consegui avançar com um intervalo que não tinha sido utilizado. A principio tudo correu bem.

Obrigada pela atenção.

Eloisa Silva

former_member234717 · ‎2022 Oct 06

Hello Marta,

Another point to be clarified! When adding new number ranges in table SIPT_NUMBR_SD_V. I am not able to fill in the start date as the field is grey and thus not editable!

How the system will know that it should use the new number range (example P2) from 01.01.2023 if there is no start date?

Example:

Z2 0976000000 0978999999 PT2 ZF4 Invoice 1 26.10.2017

P2 0984000000 0984999999 PT2 ZF4 Invoice BP20

Thanks in advance for your reply.

Best regards,

JPB

former_member613011 · ‎2022 Oct 07

HI , i have the same issue . Could you please share how did you solve it ?

jagadeesh_arumugam · ‎2022 Oct 07

Hi Leston,

It's not solved yet.

We realized the SOAMANAGER settings are not configured and it could be a reason.

We are working on establishing the connection first by referring the link below.

https://api.sap.com/integrationflow/com.sap.GS.Portugal.ManageSeriesRegistration

I will update you if it helps.

Best Regards,
Jagadeesh

former_member613011 · ‎2022 Oct 07

HI Jagadeesh ,

thanks a lot for your feedback . I'm gona check wiht my basys team which manage connections about it also .

regards

former_member824622 · ‎2022 Oct 10

Ola Marta,

I would like an advice on my company situation. We are running on SAP 4/HANA 1610 (101) and i understand approx 50% of the SAP notes to apply for ATCUD implementation are not compliant for this version. We cannot upgrade to 102 or 103 before Jan 1st 2023 due to time constraint.

What is your advice for us to proceed and be compliant with Portugal regulation under our current SAP version ?

Regards,
Thomas

former_member613011 · ‎2022 Oct 10

HI Martha ,

We do have doubts /concerns about Foregin Company codes scenarios we have currenlty running in production system because it seems not be working in our test system where we are implementing a bunch of notes related the ATCUD implementation .

Currently we do have next foreign Companies Scenarios :

Scenario A)

C.code : A913 – Spanish - S.org: A913 -Spain

Delivering goods / sellings from PT with PT Reg number since years from a Portuguese plant ( 905A ) which belongs to another Portuguese C.code of our gruop (A905) , this is done just assigning the Portuguese plant in the s.agreemnt / sales order

So in this case system generates :

A.1- "F1" invoice type from C.code A913 - S.Org:A913 with VBRK-LANDTX= PT to our external customer , and this invoice is currently being digitally signed as it's set in the customizing for Foreign C.codes we do have in our production system

A.2-“IV” intercompany invoice from Portuguese C.code A905 -S.org:A905 with PI01- intercompany price condition to internal customer A913 which is also digitally signed as it set in the customizing

we are using the standard SAP intercompany Billing functionality for this scenario

Scenario B)

Germany C.Code :A118 . S.Org :A118 in Germany

+which is selling services ( Billing order releated , no deliveries ) in Portugal with PT vat Reg number . In this case , the plant code is 118A in Germany , therefore the Sales orders contains Tax departure country VBAK-LANDTX =PT

So in this case system generates :

B.1- F1 invoice from C.Code A118 with VBRK-LANDTX= PT which is digitally signed as it's set in the customizing for Foreign C.codes we do have in our production system

So , in none of those scenario the company codes have not neither a plant in Portugal nor a Portuguese Sales org as it was not really mandatory . Beside of this , we don’t have Plants Abroad activated as we don’t really need neither .

Currenlty we are implementing all the notes related to the ATCUD changes following the 3154599 collective note and doing some tests we 've found that the Billing documents are not digitally signed for the foreign c.codes , in fact , the Billing documents are not added to SIPT_VBRK . Only those Billing documents for Portugues companies are still signed .

Checking the notes about this topic I’ve found and checked the following note and related ones , 3000350 - Despacho 404/2020-XXII: Digital Signature for all entities with a VAT registration in Portugal (SAP APPL) where is included the document Portugal Digital Signature - Plants Abroad Solution (SD Only) .

After reading such document I understand that the ONLY WAY to set up the foreign companies is MANDATORY to have the 3 conditions below :

+using Portuguese Sales Org and assign it in SIPT_CCODE_SD_VC

+using Portuguese plant and assign it in SIPT_FC_SD_WRK_V

+Plant Abroad activated

Is this really correct ? Are all those 3 points mandatory or there is any set up as the current one we have in our Production system where we could still cover such scenarios described ?

Sorry for such a long explanation and thanks in advance

former_member713824 · ‎2022 Oct 10

Hi JPB

As soon as you communicate the new series to TA and when you start using the new NR in your document (when you configure the ZF4 to use the NR P2 with the new series, the system will use the new series.

Regards,

Marta

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