SAP Community - SAP Document and Reporting Compliance

SAP Document and Reporting Compliance, Cloud Edition New Role Collection

2024-03-13T15:44:15.705000+01:00

There is a new role collection for you to assign to your user in SAP BTP, the SAP Document and Reporting Compliance, Cloud Edition – Administrator role collection.

The new role collection includes the roles that give you administrator access to the applications of the cloud edition that are not specific to any process.

The existing role collection (SAP Document and Reporting Compliance, Cloud Edition Administrator) is being deprecated as of March 2024 and we advise you to replace that by the new one (SAP Document and Reporting Compliance, Cloud Edition – Administrator).

Yes, it is only a dash (-) that differs the name of the deprecated and the new role collection, but there are important differences between both of them now.

The SAP Document and Reporting Compliance, Cloud Edition Administrator role collection (deprecated) still exists in SAP BTP and you are still able to assign it to your users but since it is no longer managed by SAP, SAP will not include, to this role collection, new roles that might be necessary for the use of features released as of March 2024.

The new SAP Document and Reporting Compliance, Cloud Edition – Administrator role collection is, as a matter of fact, managed by SAP and SAP will maintain and update the necessary authorizations for you to continue having administrator access to the applications of the cloud edition that are not process-specific.

For having the role collection maintained by SAP with up-to-date authorizations, assign the new SAP Document and Reporting Compliance, Cloud Edition - Administrator role collection to your administrator user as described in Assigning Users to Role Collections.

For checking all roles available for cloud edition users, see Identity and Access Management.

Customer downpayment in S4HC – temporary workaround for Hungary

2024-03-26T19:24:07.031000+01:00

Case: you would like to receive customer downpayments and report them to the Hungarian Tax Authorities (NAV)

Following description contains two parts:

Part 1. End-to-end description of the customer downpayment process, including preparatory steps

Part 2. DRC – Online Invoice registration for Hungary – reporting for DP and Final invoices

Part 1. End-to-end description of the customer downpayment process

Preparation

Create a special FI Accounting document type (eg DP) which will only be used for clearing incoming customer downpayments

Process steps
- Create a sales order with a billing plan (eg. OR) (Role: Internal Sales Rep)

Optional: print downpayment request from the order (standard printout has to be adjusted) (alternatively, use a wordprocessor)
After the customer payment, the date of services rendered has to be updated in the order (administrative process: bank accountant informs SD accountant about the receipt of payment),

Create SD downpayment invoice (FAZ) from the order (Role: Billing clerk)
Clear incoming payment with the special Accounting document type from the preparation step (eg. DP) (Role: AR_ACCOUNTANT, App: Post incoming payments)

Edoc will be generated with the SD billing document number as source document (see Part 2.)

Create SD final invoice – which will contain the respective DP invoice (s) as separate item(s) (with minus sign)
Edoc will be generated with the SD billing document number as source document (see Part 2)
Print SD final invoice (adjustment might have to be made in the standard printout)

Part 2: Steps for the DRC Online Invoice Registration (component: CA-GTF-CSC-EDO-HU):

2.1. Preparation

2.1.1. Activate FI source for the company code, (Role: BPC Expert)

2.1.2. The Accounting document type used for the clearing (eg DP) should be assigned in the eDocument customizing, (Role: BPC Expert)

2.1.3. No special enhancement needed for the Final invoice (for invoices in local currency)

2.2. Process steps

During the downpayment process, eDocs will be automatically created in the following cases:

Clearing incoming downpayment – eDoc for downpayment is created and displayed in the eDoc cockpit (advanceIndicator tag set to “TRUE” on item level)
Posting of the final invoice – eDoc for the final invoice is created and displayed in the eDoc cockpit (containing the DP items with the advanceIndicator tag set to “TRUE”, DP invoice number, clearing date and exchange rate)

Updates on Conhecimento de Transporte Eletrônico and Manifesto Eletrônico de Documentos Fiscais

2024-03-27T20:15:42.857000+01:00

Hi everyone,

The SAP Document and Reporting Compliance, inbound and outbound invoicing options for Brazil team has released updates on Conhecimento de Transporte Eletrônico (CT-e) and Manifesto Eletrônico de Documentos Fiscais (MDF-e). The update complies with SEFAZ CT-e Technical Note 2024.001 1.01 Version (Tax Benefit Inclusion) and MDF-e Technical Note 2024.001 1.01 Version (Closing Event). The new version is planned to be in production on April 8, 2024, according to the tax authority.

Updates on CT-e and MDF-e Technical Note 2024.001 - Version 1.01

Conhecimento de Transporte Eletrônico (CT-e):

The new update on CT-e (model 57) and CT-e OS (model 67) allows you to include the new vICMSDeson (Exempt ICMS Tax) and cBenef (Fiscal Benefit Code) fields in the XML files. These fields will be included in the following ICMS groups: ICMS20, ICMS45, ICMS60, ICMS90, and ICMSOutraUF.

You can implement these updates by following the instructions on the SAP Notes:

SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824
SAP Note 3441171
SAP Note 3445374

You can implement the changes for the SAP Electronic Invoicing for Brazil (SAP NFE) solution following the instructions on SAP Notes:

SAP Note 3426934
SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824

The SEFAZ CT-e Technical Note 2024.001 1.02 Version has been revised, and there will be no impact on the CT-e solution.

Check SAP Knowledge Base Article 2807654 for troubleshooting information and common issues.

Manifesto Eletrônico de Documentos Fiscais (MDF-e):

The update on MDF-e (model 58) allows you to include the indEncPorTerceiro field in the XML files, which has been introduced to the closing event (type 110112). To implement this update, follow the instructions on SAP Note 3437854.

The SEFAZ MDF-e Technical Note 2024.001 1.02 Version has been revised. The XML schema has been updated in our service, and it is not necessary to implement other SAP Notes for this change.

You can implement the changes for the SAP Electronic Invoicing for Brazil (SAP NFE) solution by following the instructions on SAP Note 3431096.

Related blog posts:

For a step-by-step guide on how to use the SAP Document and Reporting Compliance, inbound and outbound invoicing options for Brazil, refer to the following SAP Help Portal pages:

You can sign up for email alerts when new SAP Notes are released or updated in the components listed below; just follow the instructions in the SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-IN
FI-LOC-NFE-BR-OUT
LOD-LH-NFE
SLL-NFE

Use the regulatory change manager tool to find out if a solution to a legal change is planned. Take a look at SAP Knowledge Base Article 3421995 and the regulatory change manager page to understand how to use this tool.

Have you found this blog post useful? If so, choose “Like” (Kudos), share it with your colleagues, and follow me for similar content.

You are welcome to leave your questions and read similar blog posts on the SAP Document and Reporting Compliance SAP Community. Don’t forget to follow the SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) tag and the SAP Document and Reporting Compliance Community to keep up with the latest NF-e news.

Thank you, and until next time,
Thiago

Tags: electronic transportation document, nota técnica, v1.01, 2024/001, inclusão do benefício fiscal, tax benefit inclusion, tax benefit code, código de benefício fiscal, documento fiscal eletrônico, electronic fiscal document, electronic manifest of tax documents, brasil, einvoice, einvoicing, e-invoicing, electronic invoice, electronic invoicing, edocument, edoc, e-document, e-docs, e-doc, e-docs, drc, document compliance, nota fiscal eletrônica, electronic nota fiscal, ct-e outros serviços, ct-e other services.

Generate Custom Legal Certificates in SAP DRC

2024-04-03T15:16:32.123000+02:00

The purpose of withholding tax is to ensure that the government receives tax revenue in a timely manner and to facilitate tax compliance. It is commonly applied to various types of income such as wages, salaries, interest, dividends, royalties, and payments to contractors or freelancers. The rates of withholding tax and the types of income subject to withholding tax vary depending on the tax laws of each jurisdiction.

While SAP provides standard reports for reporting withholding tax, custom requirements may arise for specific needs. This blog focuses on the development of a custom certificate to address such requirements. Developing a custom certificate requires knowledge in DRC extensibility and Adobe Form development.

In this scenario, a custom Adobe form is being created within the system, extending the Thailand 50 BIS certificate.

Go to t-code SFP to create the Adobe Form. The form can be developed using the default interface SOMU_DEFAULT_INTERFACE, with XFA2 chosen as the layout technology.

Once the form layout is created, save and activate it.
Then, navigate to Define Compliance Application and initiate the creation of a new report definition. For this example, an existing report definition is duplicated. Provide a name for the new report definition and specify a package for its storage.

Create custom report definition

Save it in local package

After creating a new report definition, Add a new document according to the specified requirements. In this instance, a PDF document is presented as an example.

Add new legal document

Create it as a PDF

Provide details for the document such as the document name, file name, code page, etc.

Document Details

Select a schema for this document, which defines the format and structure of the document. Various options for creating a schema are available, including using XSD, JSON, or ABAP dictionary. For this particular example, the schema is generated using the ABAP dictionary. Alternatively, an existing schema can also be utilized.

Create Schema

Enter the Custom Form Details

After finalizing the schema, proceed to the Mapping section. The structure of the document, based on the schema, will be displayed, allowing for mapping according to the requirements. Data can be mapped from various sources such as CDS, tables, class methods, or system fields.

Perform Mapping

Save and Activate the report definition.

Save and Activate

Now the schema needs to be downloaded in order to perform mapping in the Adobe form. Select the "Export Schema" option and then choose "Export as Simplified XSD". Ensure that the report definition is in editable mode before attempting to download the schema.

Download XSD as shown

The layout for the Adobe form can be created using the Adobe LiveCycle Designer (ALD). Develop a custom layout, and if there's a requirement for a fixed company logo, watermark, or signature, it can be directly incorporated. For dynamic company logo, watermark, or signature needs, include an image field in the Adobe Form. The value of this field can be manipulated during form generation

Create Custom Layout

In this example, an already developed Thailand 50 BIS form has been downloaded. It contains existing bindings. To remove these bindings, navigate to the data view, right-click, and select "Delete Data Connection". During deletion, you have the option to retain or delete the existing bindings. In this instance, the existing bindings are kept intact while mapping new fields in the form.

Delete Data Connection

Do not remove existing binding

To establish a new data connection, right-click in the Data View and select "New Data Connection". Upload the previously downloaded schema from the steps above and utilize it for mapping the new fields.

Create New Data Connection

Choose XML schema

Upload the earlier downloaded schema

Next, proceed with the new mapping process as demonstrated below. The newly added fields from the schema will be displayed, allowing them to be mapped within the form layout.

Perform Mapping

After completing the layout, upload it in transaction code SFP. Change the existing custom form and select "Upload Layout". This action will replace the existing layout with the new one.
Save and Activate the Form.

Now create a new report category , for this example exisiting report category is copied . Enter the Report category name and save it designated package .

Create New Report category

Maintain the report activity details by assigning the already developed report definition to this report category. Enter additional information such as description, phase, submission mode, valid form, and validity period.

Add new activity

Save and Activate the report category

Activity details

The Custom legal certificate generation involves several steps related to working with Adobe Forms and Report Definitions:

Develop Custom Adobe Form: Design and create a personalized Adobe form tailored to specific needs or requirements.
Create a New Report Definition: Create a new definition for a report, outlining its structure, content, and parameters.
Create Schema for the Document: Develop a schema outlining the structure and format of the document to ensure consistency and compatibility.
Download the Schema: Retrieve the schema for integration purposes.
Perform Mapping In Form: Map data fields or elements within the Adobe form to corresponding elements in the schema or report definition.
Create a New Report Category: Create a new category to classify or organize reports based on specific criteria or characteristics.
Assign Report Definition to the Report Category: Link the newly created report definition with the designated report category for generation of custom output.

Overall, these steps involve the creation, customization, and organization of Adobe forms and report definitions to effectively manage data and generate custom report within DRC framework.

Summary:

Summary

Thank you for reading!

Drop a like or comment below if you found the above steps useful and do let me know in the comments section if you are looking for any other specific use case of US report extensibility.

Government SEFAZ Technical Notes with Optional Events

2024-04-05T22:17:12.404000+02:00

Hello,

In recent years, the Secretaria da Fazenda (SEFAZ) has published several technical notes containing optional events. This means that taxpayers are not obligated to issue these events, and it is up to each company to decide whether to use them.

Since these events are optional, SAP considers the events as new features and not mandatory legal changes. Therefore, optional technical notes will not appear in the regulatory change manager (RCM) tool.

You can check the following technical notes with optional events published by SEFAZ:

Nota Técnica NF-e 2020.007 – Evento Ator Interessado na NF-e (NF-e Intestered Actor)
Nota Técnica NF-e 2021.001 – Evento Comprovante de Entrega na NF-e (NF-e Delivery Confirmation)
Nota Técnica NF-e 2023.005 – Evento Insucesso de Entrega na NF-e (NF-e Delivery Failure)
Nota Técnica CT-e 2019.001 – Evento Comprovante de Entrega no CT-e (CT-e Delivery Confirmation)
Nota Técnica CT-e 2023.002 – Evento Insucesso de Entrega no CT-e (CT-e Delivery Failure)

SAP is still analyzing the demand for each technical note. Any updates will be published on the SAP Roadmap Explorer for SAP Document and Reporting Compliance, inbound and outbound options for Brazil.

Thank you,

Cláudia Wada

Disclaimer: This blog, or any related comment, SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed at any time for any reason without notice. This blog is not a commitment, promise or legal obligation to deliver any material, code or functionality. This blog is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP Document and Reporting Compliance Brazil: Atualizações no CT-e MDF-e

2024-04-08T20:00:31.977000+02:00

(English version here)

Olá pessoal,

O time de SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil entregou semanas atrás as atualizações nas soluções de Conhecimento de Transporte Eletrônico (CT-e) e Manifesto Eletrônico de Documentos Fiscais (MDF-e). As mudanças atendem à Nota Técnica 2024.001 versão 1.01 (Inclusão do Benefício Fiscal) de CT-e e à Nota Técnica 2024.001 versão 1.01 (Evento de Encerramento) de MDF-e da SEFAZ.

Nota Técnica 2024.001 versão 1.01 para CT-e e MDF-e

Conhecimento de Transporte Eletrônico (CT-e):

A nova atualização do CT-e (modelo 57) e CT-e OS (modelo 67) permite incluir os novos campos vICMSDeson (valor do ICMS desonerado) e cBenef (Código do Benefício Fiscal) nos arquivos XML. Esses campos serão incluídos nos seguintes grupos de ICMS: ICMS20, ICMS45, ICMS60, ICMS90 e ICMSOutraUF.

Você pode implementar as mudanças seguindo as instruções nas seguintes SAP Notes:

SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824
SAP Note 3441171
SAP Note 3445374

Você pode implementar as mudanças na solução SAP Electronic Invoicing for Brazil (SAP NFE) seguindo as instruções nas SAP Notes:

SAP Note 3426934
SAP Note 3444678
SAP Note 3444679
SAP Note 3444823
SAP Note 3444824

A Nota Técnica 2024.001 Versão 1.02 de CT-e foi revisada e não haverá impacto na solução de Conhecimento de Transporte Eletrônico (CT-e).

Consulte o SAP Knowledge Base Article 2807654 para obter informações sobre resolução de problemas.

Manifesto Eletrônico de Documentos Fiscais (MDF-e):

A atualização no MDF-e (modelo 58) permite incluir nos arquivos XML o campo indEncPorTerceiro, que foi introduzido no evento de encerramento (tipo 110112). Para implementar esta atualização, siga as instruções na SAP Note 3437854.

A Nota Técnica 2024.001 Versão 1.02 de MDF-e foi revisada. O schema XML foi atualizado em nosso serviço, não sendo necessária a implementação de outras SAP Notes para esta alteração.

Você pode implementar as mudanças na solução SAP Electronic Invoicing for Brazil (SAP NFE) seguindo as instruções na SAP Note 3431096.

Blog posts relacionados:

Para obter um passo a passo sobre como usar o SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil, consulte as seguintes páginas do portal SAP Help:

Você pode receber alerta por email quando novas SAP Notes forem lançadas ou atualizadas nos componentes listados abaixo; basta seguir as instruções do SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-IN
FI-LOC-NFE-BR-OUT
LOD-LH-NFE
SLL-NFE

Acesse o gerenciador de modificações legais para ter uma noção do que está planejado para ser suportado. Consulte o SAP Knowledge Base Article 3421995 e a página “regulatory change manager” para entender como usar esta ferramenta.

Gostou desse post? Dê um Like (Kudos) e compartilhe o conteúdo com seus colegas. Sinta-se à vontade para deixar suas perguntas ou ler posts semelhantes no SAP Community do SAP Document and Reporting Compliance.

Para acompanhar as últimas notícias da NF-e, siga a tag SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) e a comunidade SAP Document and Reporting Compliance.

Obrigado e até a próxima,
Thiago

Colombia Production Number Range Retrieval from DIAN

2024-04-08T22:26:50.550000+02:00

This guide provides clear steps for accessing Ranges from DIAN to Colombia in Production systems. Its primary focus is to assist customers going live with the SAP Document and Reporting Compliance-Colombia solution.

Prerequisites:

Complete the Habilitation test process. The habilitation test process for the Colombia e-invoice ensures compliance with the e-invoicing requirements before a taxpayer is enabled as an authorized issuer of electronic invoices. The taxpayer must perform a series of tests to verify the software's correct functioning and compliance with the e-invoicing requirements. The tests include the generation, transmission, validation, and consultation of electronic invoices, credit notes, and debit notes.
After the successful Habilitation tests, manually request the production number ranges for Invoices and Contingency Invoices in the DIAN portal.
You have deployed the iflow for the Query Ranges in the production tenant.
SOAMANGER configuration is completed.
You must have the authorization to run the transaction ‘EDOC_CO_RANGES’ or report EDOC_CO21_QUERY_RANGES.
You must know the Company Code and Software ID for running the transaction EDOC_CO_RANGES.

Note: You can get the Software ID from the DIAN portal.

7. The necessary configuration in EDOSOASERV is maintained and transported to the production system.

Important Notes:

The logical port name in the SOAMANGER for the proxy object CO_EDO_CO21_QUERY_RANGES_V2_0 must match the logical port name maintained in the view EDOSOASERV for the SOA service name CO_GET_RANGES.
The production ranges are only retrieved from DIAN for Invoices and Contingency invoices. In DIAN, only the ranges for invoices and contingency invoices are maintained.
For all document types, such as Credit Notes and Debit Notes, you must choose the number ranges according to your business requirements and maintain them manually in SNRO.

Number Range Retrieval Steps:

Execute transaction EDOC_CO_RANGES or follow the path in SPRO, Cross-Application Componentsà General Application Functionsà Document and Reporting Complianceà Country/Region-Specific SettingsàColombiaà Electronic Document Processingà Get Number Ranges for Invoices from Tax Authority
Enter Company Code and Software ID

Example:

3. Press the Execute button.

4. A successful execution will create necessary configuration entries in SNRO and the view EDOCORANGESV. You can also view retrieved ranges in the report execution.

Example:

5. The retrieved ranges are stored in

SNRO Against the object EDOC_CO and Company code used in the report execution.

The transaction EDOC_CO_RANGES will find the next available Number Range No. and adds it to the SNRO.

This means that screenshot 2 above shows that the range retrieved from DIAN is the number three position.

b. EDOCORANGESV - You use this Customizing view to enter the number ranges and their attributes to be used to create eDocuments.

Example:

Next Steps After Range Retrieval from DIAN:

Maintain Ranges for Credit notes and Debit notes manually

Go to SNRO and define number ranges for Credit and Debit Notes according to your business requirements.

2. Maintain Ranges for Credit and Debit Notes in EDOCORANGESV.

Example:

Assign Number Ranges to eDocument Types

In this Customizing activity, you assign number ranges to the eDocument types for Colombia.

The Variable Key field enables the use of different number ranges for the same eDocument types. A use case is, for example, if you want to use different number ranges for different organizational entities like branches, business places, or plants.

If the number range overlaps for Colombia eInvoice and Colombia eInvoice Contingency document types, you can define the range numbers used for the contingency process in the columns From Number – Contingency and To Number – Contingency.

For example, DIAN authorizes the number range from 100000 to 105000, but the numbers between 100000 and 100800 are to be used for contingency documents.

SAP Document and Reporting Compliance Brazil: Dashboard do Usage Analytics

2024-04-09T21:55:23.727000+02:00

(English version here)

Olá pessoal,

Lançamos uma nova funcionalidade que permite que você verifique sua utilização do SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil fornecendo informações mais precisas sobre o consumo.

Esse novo recurso só está disponível a partir do ano de 2024 para os IDs de métrica CY140 (faturamento de saída) e CY141 (faturamento de entrada). Para saber qual é o seu ID de métrica, verifique no SAP LUI (License Utilization Information) no app “SAP for Me”. Mais informações sobre SAP LUI estão descritas abaixo.

Você acessa o dashboard do Usage Analytics no painel de navegação esquerdo do SAP BTP Cockpit, como mostrado na imagem a seguir:

No dashboard do Usage Analytics, você pode encontrar informações sobre o produto "SAP Document and Reporting Compliance, opção de emissão de fatura de entrada e de faturamento de saída para o Brasil" (inbound and outbound invoicing options for Brazil).

Para processos de saída (outbound), temos dois grupos de classificação, chamados Grupo A e Grupo B, como mostrado na imagem a seguir:

Para exibir todas as Usages na tela, deixe o filtro Service em branco. Nem todas as classificações estão sendo exibidas nesta imagem.

Grupo A: Classifica cada documento processado (definição de métrica) por tipo e ação. O Grupo A é composto pelos documentos abaixo.

Documentos processados (NF-e, CT-e, NFS-e, MDF-e e NF3-e)
Documentos de eventos processados (CC-e, cancelamento, inutilização, etc.)
Arquivos de documentos exibidos/baixados*
Arquivos de eventos exibidos/baixados*
Documentos reenviados para aprovação (NF-e, CT-e, NFS-e, MDF-e e NF3-e)

*Somente quando o mesmo arquivo XML for baixado pela segunda vez. Isso evita o mau consumo.

Acesse o Cloud (SaaS) Application Usage & SAP Business Technology Platform para verificar a lista completa de classificação do Grupo A.

Grupo B: Classifica cada documento processado (definição métrica) conforme o tipo de ambiente:

Documentos processados em ambiente produtivo.
Documentos processados em ambiente de homologação.

A soma dos documentos exibidos no Grupo A deve ser igual à soma dos documentos exibidos no Grupo B. O número total de documentos é exibido em Total documents from group A or B.

Considerando o exemplo da imagem anterior, a soma do Grupo A é 1317 e a soma do Grupo B também é 1317.

Para processos de fatura de entrada, também temos dois grupos de classificação, chamados Grupo A e Grupo B, como mostrado na imagem a seguir:

Para exibir todas as utilizações na tela, deixe o filtro Service em branco. Nem todas as classificações podem ser exibidas nesta imagem.

Grupo A: Classifica cada documento processado (definição de métrica) por tipo e ação. O grupo A é composto pelos seguintes tipos de documentos:

Documentos processados (NF-e, CT-e)
Documentos de evento processados (CC-e, cancelamento, etc.)
Arquivos de documentos baixados da SEFAZ (NF-e, CT-e)
Arquivos de eventos baixados da SEFAZ (CC-e, cancelamento, etc.)

Acesse o Cloud (SaaS) Application Usage e o SAP Business Technology Platform para verificar a lista completa de classificação do Grupo A.

Grupo B: Classifica cada documento processado (definição métrica) conforme o tipo de ambiente:

Documentos processados em ambiente produtivo.
Documentos processados em ambiente de homologação.

A soma dos documentos exibidos no Grupo A deve ser igual à soma dos documentos exibidos no Grupo B. O número total de documentos é exibido em Total document from group A or B.

Considerando o exemplo da imagem anterior, a soma do Grupo A é 202 e a soma do Grupo B também é 202.

Se você encontrar discrepâncias, certifique-se de que não haja codificação personalizada que chame o serviço em nuvem duas vezes ou crie um efeito de loop.

Principais opções da análise de utilização

Capability: no dashboard Usage Analytics, você pode usar o menu suspenso Capability para filtrar a utilização do serviço selecionando os recursos do SAP BTP (aplicativo, automação ou integração).
Service: nessa lista suspensa, você pode usá-la para filtrar o uso de cada plano de serviços na subconta da sua empresa. Por exemplo, você pode filtrar a utilização de dados da solução “opção de emissão de fatura de entrada e de faturamento de saída para o Brasil” (inbound and outbound invoicing options for Brazil).
Metric: você pode selecionar uma das métricas (documentos exibidos, baixados, reenviados para aprovação ou processados). Você pode utilizar o menu suspenso Metric para evitar exibir todos os documentos ao mesmo tempo.
Period: em relação ao intervalo de tempo selecionado no campo Period, esteja ciente de que as informações apresentadas são do ano 2024 em diante e somente após a instalação das seguintes SAP Notes.

Instalação

Você pode implementar essas modificações seguindo as instruções nas SAP Notes.

As SAP Notes são necessárias para fornecer os dados utilizados em métricas e para corresponder à quantidade do Grupo B aos dados de consumo no rótulo Total document from group A or B. A instalação das SAP Notes não tem impacto nos processos de cálculo da fatura atuais.

Outbound (faturamento de saída): SAP Note 3111469
Inbound (fatura de entrada): SAP Note 3399269

License Utilization Information (LUI)

O aplicativo License Utilization Information (LUI) fornece detalhes sobre a titularidade da licença e sobre a utilização do software. Para receber os resultados, uma medição do sistema é realizada em cada sistema relevante.

O dashboard Usage Analytics pode ser usado em conjunto com a LUI selecionando o mesmo período para gerar análises sobre como a solução SAP Document and Reporting Compliance está sendo usada. O painel do LUI deve mostrar o mesmo valor na coluna Measured e no Total document from group A or B do Usage Analytics.

A aplicação LUI pode ser acessada por meio do SAP for Me. Verifique o License Utilization Information para obter detalhes sobre como utilizá-las e acessá-las.

Data da contabilização

A data da métrica pode não representar a data da ação do usuário. Por exemplo, podem existir discrepâncias em que um documento processado no fim de um mês aparece no consumo do mês seguinte, devido ao processo assíncrono da contabilização. O momento em que um usuário realiza uma ação e quando essa ação é refletida em nossas métricas pode nem sempre se alinhar perfeitamente, especialmente na transição entre os dias.

Você pode entrar em contato com seu executivo de contas se tiver perguntas sobre os valores ou se precisar de mais ajuda. Verifique a SAP Note 2626344.

Você pode receber alerta por email quando novas SAP Notes forem lançadas ou atualizadas nos componentes listados abaixo; basta seguir as instruções do SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-IN
FI-LOC-NFE-BR-OUT
LOD-LH-NFE

Para acompanhar as últimas notícias da NF-e, siga a tag SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) e a comunidade SAP Document and Reporting Compliance.

Obrigado e até a próxima,
Bruno Eltz e Thiago Cezimbra

Tags: brasil, einvoice, einvoicing, e-invoicing, electronic invoice, electronic invoicing, edocument, edoc, e-document, e-docs, e-doc, e-docs, drc, document compliance, nota fiscal eletrônica, electronic nota fiscal

Navigating Tax Requirements in the Digital Era: Learn How SAP Helps You Revolutionizing Compliance

2024-04-11T20:41:17.436000+02:00

In today's rapidly changing business environment, taxation stands as a crucial aspect for enterprises worldwide. As businesses adapt to digitalization, they face various trends that are changing tax compliance. These trends include new business models and governments' digital initiatives, which are transforming the tax landscape. Authorities are getting involved in business transactions, disrupting established processes, and taking control of the invoicing flow between suppliers and buyers. This gives them the data they need to prevent tax evasion, audit taxpayers automatically or even pre-fill tax returns. Additionally, sustainability measures and climate change regulations are also affecting tax regulations. Amidst these shifts, SAP serves as a strategic partner, providing peace of mind to navigate these complexities efficiently. By understanding the changing tax landscape, businesses can use SAP's solutions to streamline compliance processes and automate tasks, taking advantage of the emerging opportunities.

SAP offers solutions tailored to address modern tax challenges. SAP S/4HANA Cloud provides transparency and compliance on a global scale, enabling businesses to embed tax requirements in their processes. Through localized solutions that offer standardized – but flexible – business processes, SAP provides a complete suite of solutions that facilitates efficient tax management, from e-invoicing to statutory reporting and tax compliance overall. With SAP's technologies and expertise, businesses can achieve greater accuracy and agility in tax compliance, paving the way for sustainable growth and competitive advantage.

To help tax professionals to prepare for and become a valuable member of a tax transformation project, SAP introduces "Unlocking Tax Transformation with SAP," a learning course designed to equip professionals with the knowledge needed to navigate today's tax landscape and learn new capabilities that can be leveraged as part of SAP S/4HANA-enabled transformations to simplify tax compliance. Integrated with SAP's solutions, this course offers practical strategies for you to learn about the different tax types, global developments, their business relevance, and the importance of technology with a focus on SAP S/4HANA and SAP solutions for global tax management. The course starts April 30 and enrollment is now open. By enrolling in this course, tax professionals can gain valuable insights into industry best practices and leverage SAP's latest innovations to optimize their tax processes.

In a time of rapid change, SAP stands as a reliable partner, supporting businesses in their journey towards tax compliance and growth. Join us as we uncover the evolving landscape of taxation and explore opportunities for transformation. Through collaboration with SAP and a commitment to continuous learning, businesses can navigate the complexities of taxation with confidence and achieve their long-term objectives.

Register now, don't miss this learning opportunity!

Did You Set Up Your Cloud Edition Before April 26, 2023? Your Attention Is Needed!

2024-04-12T21:23:35.747000+02:00

When setting up your system, you create a service instance for the SAP Document and Reporting Compliance, cloud edition to connect with your business system. For that, you have followed the steps described in the Creating a Service Instance for the Cloud Edition.

All service instances created before April 26, 2023, were delivered with a direct communication with the component part of SAP Document and Reporting Compliance, cloud edition. However, starting from April 2023, as part of our product evolution, we introduced an API layer aimed at unifying and simplifying the process of exchanging electronic documents and submitting reports across different scenarios.

What does this mean? If you have onboarded SAP Document and Reporting Compliance, cloud edition prior to April 26, 2023, you need to recreate the service instance to be able to leverage the latest API layer. This is a prerequisite to use any scenario published and supported by SAP Document and Reporting Compliance, cloud edition after April 26, 2023.

Creating two process instances within the same subaccount is not possible. Hence, you are presented with two alternatives:

Establishing a new subaccount along with a new service instance.
Deleting the current service instance and re-creating it.

Create new subaccount and new service instance

For creating a new subaccount and service instance, you follow the steps described in the Initial Setup page on the SAP Help Portal. Additionally, follow the integration steps specific to your scenario.

Delete current service instance and recreate it

For deleting the current service instance, follow the steps described in Deleting Service Instances. For recreating it, the steps vary depending on the authentication type you use. Consider the following:

When using OAuth 2.0 Client Authentication or SSL Client Certificate Authentication, perform all steps as described under Integration for your scenario.
When using User Provided SSL Client Certificate Authentication, perform all steps described under Integration for your scenario, except the PSE configuration in the STRUST as you will use the same certificate.

If you use the same subaccount for Peppol, you don’t need to set it up again as long as you create a new service binding using the same certificate you were using before. That is because, for the Peppol Exchange process, the host has not been changed with the addition of the new API.

It’s just a few steps and you’ll be setup for the future - if you need to connect multiple back-end systems to SAP Document and Reporting Compliance, cloud edition, or exchange documents and reports with different countries/regions, you can use the same process instance to incorporate both OAuth (EHP8 for SAP ERP 6.0 – SP 23 and higher) and certificate-based (EHP8 for SAP ERP 6.0 – SP 22 and lower) authentications. In that case, you can create three service bindings to accommodate all configurations:

Peppol
Others - oAuth
Others - Certificate

Remember that the combination of OAuth and certificate-based authentication is only necessary if the backend systems are running on multiple versions of the back-end systems. Otherwise, you can reuse the oAuth authentication between your backend systems.

We hope you find this information useful. You can leave a comment on this blog or follow us for more information about SAP Document and Reporting Compliance here in SAP Community.

Introducing the market standard of electronic invoicing for the United States

2024-04-15T22:05:00.484000+02:00

Hi everyone,

As a brief introduction to the Community at large, I have been working at SAP for over 16 years in localization product management for Latin America and the United States. In my journey through the areas of financials, logistics and human capital management, I supported the launch of varied solutions ranging from electronic invoicing to tax calculation and reporting. Certainly, electronic invoicing has been one of my favorite topics at the core of my heart for its business criticality and technical challenges to the parties involved.

Two years ago, I had the privilege to join a task force to participate in a market pilot program intended to become the standard for electronic invoicing in the United Stated.

Unlike most countries where there is a government mandate, electronic invoicing in the United States is a private sector business-driven initiative. Currently, there is a wide fragmentation of standards for electronic invoicing with over 55 formats and variants, hindering companies from adopting and scaling digitalization across the Business-to-Business (B2B) space.

What benefits does electronic invoicing bring to the B2B space?

From my product management experience, I have witnessed American, European and Asian companies adopting electronic invoicing with clear return on their investments:

Seamless communication and exchange of electronic documents between business partners regardless of the IT systems and platforms used
Time savings (reduction of rework from error-prone manual processes and handling of exceptions) and cost savings (significant reduction in paper use, mailing and handling costs)
Digital archiving, easy data access and audit-ready document traceability
Business dispute mitigation by securing the terms and conditions included in the electronic documents, thus contributing to the optimization and transparency of the supply chain.

How is the exchange of electronic documents going to be enabled in the United States?

The benefits that I listed above are going to be achieved thanks to a modern exchange framework for electronic documents called the four-corner network model (see image below). This ensures a seamless, resilient and secure invoice transmission process, regardless of the underlying technology used for processing electronic invoices. Imagine a network where you can connect once and reach anyone anytime following a common open standard. This network and its standard are going to be governed by Digital Business Networks Alliance (also know as "DBNAlliance").

This model contains four types of participants – the supplier (or sender), two access points known as service providers, and the buyer (or receiver).

A supplier sends invoice information to its access point provider. The access point connects to the Exchange Framework and searches for the buyer’s access point. Once located, the supplier’s access point packages the invoice into the exchange data standard, and securely sends the invoice to the buyer’s access point. The buyer’s access point pushes the invoice data into the buyer’s accounts payable system for approval and payment processing.

Background about DBNAlliance (“Digital Business Networks Alliance, Inc.”)

As a result of a collaborative initiative between the US Federal Reserve and a coalition of companies from the private sector, a Market Pilot Program was launched in 2021 to assess and test a proof of concept for the exchange of electronic invoices, similarly to the Open Peppol network. Upon successful completion in 2023, the Digital Business Networks Alliance, Inc. (also known as “DBNAlliance”) was created as the legal oversight entity of the Exchange Framework based on a set of open standards, policies and security mechanisms for the network, intended to accelerate the adoption of electronic invoicing, making digital business transactions the norm, not the exception.

Like modular legos, DBNAlliance has the flexibility and potential to add more functionality blocks like e-remittances and e-payments, thus contributing to a seamless flow in the Order-to-Cash and Procurement-to-Pay processes.

By enabling the exchange of electronic documents between different IT systems and platforms, DBNAlliance offers a straightforward and accessible means for companies of all sizes to implement e-invoicing with their business partners without the need for them to adopt any specific provider or portal.

Localization as a key differentiator for SAP customers

SAP localization is often recognized for its competitive edge by enabling companies to run their business on a global scale with confidence while staying compliant to local requirements. Follow this link for more details on how customers succeed using localized solutions from SAP.

As a founding member of the DBNAlliance network, SAP is currently evaluating plans to develop an Access Point solution. More news to come, stay tuned to my next blog!

If you are interested:

To join our early adoption program, please, reach out!
To leave me a feedback or question, please use the comments section below.

SAP Document and Reporting Compliance - 'Colombia' - Contingency Process

2024-04-17T18:04:21.615000+02:00

This blog offers insights into the contingency process feature within the SAP DRC Colombia solution and details the steps required for setting it up.

Occasionally, users encounter difficulties submitting eDocuments to the Colombian tax authorities (DIAN) owing to technical glitches within the system or communication errors. These issues may arise from the electronic bill issuer's end or from DIAN itself, resulting in the unsuccessful submission of eDocuments.

The different types of contingencies are distinguished based on the '<InvoiceTypeCode>' tag. The value 03 represents contingency due to technical issues on the electronic bill issuer's side, and 04 represents contingency due to technical issues on DIAN.

DIAN Contingency - Tipo - 04

Technological problems generated by DIAN for the prior validation of electronic invoicing. Electronic billers can set up this contingency process when one of the following error messages are received from DIAN.

Error Handling: If an error (specifically mentioned in section 12.2.1) is detected when transmitting an electronic sales invoice, the invoice must be re-transmitted to DIAN 20 seconds after the error is detected. If the error persists after three attempts (one minute after the first attempt), the invoice should be issued directly to the buyer without prior validation from DIAN.
Error Documentation: Providers must maintain records of the errors encountered as specified in section 12.2.1.
Figure 1.1 - Possible error codes during DIAN Contingency
Follow the link to DIAN documentation for more information.
Invoice Generation with Errors: In case of persistent technological issues, invoices should be issued with an InvoiceTypeCode of 04, maintaining the same prefix and number, and should be re-signed and delivered without DIAN’s validation response.
Monitoring DIAN Services: Providers should monitor DIAN’s electronic billing web services 30 minutes after an error is first reported to check if the service has been restored. Monitoring should continue until the service is fully operational.
Post-Recovery Actions: Once the DIAN service is active again, providers should generate, transmit, and issue electronic documents normally.
Reporting Timeline: Electronic billers have 48 hours to report to DIAN any invoices issued due to technological issues once they verify that DIAN's services are operational.

Figure 1.2 - Provides context about the steps to be followed in case of DIAN Contingency

Electronic Bill Issuer Contingency - Tipo -03

Technological problems at electronic bill issuer system. If a technical problem prevents you from sending eDocuments to DIAN, you define in Customizing that all eDocuments are created in contingency mode.

The steps outline procedures for electronic billers to follow during technological issues in the issuer system:

Issuing Invoices During Contingency: If there are technological problems, billers should issue sales invoices manually or through electronic systems, using either booklet or paper formats.
Communication of Issues: Billers must draft a letter detailing the technological issue or its resolution, signed by the company’s legal representative. This letter should be sent to a specified email address, with certain required details in the subject, attachment, and body of the email.
Post-Issue Procedures: Once the technological issue is resolved, billers should resume normal operations of generating, transmitting, issuing, and receiving electronic documents.
Documentation and Notification: During the contingency period, information from manually issued invoices must be transcribed into an electronic transmission document. Notifications of acceptance or rejection from DIAN (the tax authority) will follow within 48 hours of resolving the issue.
Specific Documents Without Contingency Plans: CreditNote, DebitNote, and ApplicationResponse documents should not use contingency numbering but instead follow the established numbering by the biller.

For further information about this type of contingency, please refer to the DIAN documentation link.

Figure 1.3- Provides information about the contingency due to Electronic biller's system issues

SDC Colombia Contingency Process setup:

When an eDocument submitted from edoc cockpit and if it results in one of the below statuses, then the documents are must be processed in DIAN contingency mode (InvoiceTypeCode - 04) / Electronic Bill Issuer contingency mode (InvoiceTypeCode - 03) :

Communication Exception Status in EDOC Cockpit

This situation occurs when there is a communication issue at DIAN, and the document does not reach its system. You can perform the following steps to complete the process:

Validate if the error messages received from DIAN is one of the following

If you are not able to see the error code in the application log or interface log in the cockpit, you must check it in the CPI logs; here is an example screenshot-

If you receive the message "Time out" while transmitting electronic documents, it is a declared delay in the DIAN system, you should attempt again after two minutes, if the error persist attempt four times more each two minutes, if the problem persist in spite of the five attempts, it is declare the contingency type 04, you should keep the evidence of the delay in the DIAN services.

Steps to be followed for DIAN Contingency mode:

Select the eDocument with the status 'Communication Exception' and choose the 'Switch to Contingency' action
Choose Yes in the next dialog box.
The status changes to 'Switched to DIAN Contingency'
Send an electronic invoice to the customer without validations from DIAN
Select eDocument and choose Customer-->Send to Customer option
1. The system allows sending email to customer in this situation; you can confirm this in the History section
2. Once the technological issues are resolved on DIANs side you must submit the edocument again and DIAN performs the validations, Approves and Rejects the edocuments.

The resubmitted document must have the InvoiceTypeCode 04. The History section of the edocument can show this.

Sending to DIAN requested

There is a technical issue in the electronic invoice issuer system, and the eDocument cannot be sent to DIAN. If the issue cannot be resolved quickly, you can switch the eDocument to contingency. After that, you manually reverse/cancel the source document related to this eDocument in the source application.

Note:

If the issue is related to data and can be resolved easily, switching to the contingency mode is unnecessary. Correct the data and resubmit the data again.
You must have prenumbered forms approved by DIAN

Steps to be followed for Contingency at the invoice issuer's System:

Once you identify the technological issues in the system that cannot be solved quickly, follow the steps to create eDocuments in contingency mode (Electronic bill issuer contingency - 03)

Choose the eDocument with the status 'Sending to DIAN Requested' and select 'Switch to Contingency' action
Choose Yes in the next dialog.
Status of the eDocument changes to 'Switched to Contingency'
Cancel the Invoice
Perform the configuration to allow the creation of the eDocuments in contingency mode
In the source applications, you create new documents for the eDocument you have switched to contingency. Before posting the documents, you enter the number of the prenumbered document you used for the contingency documents:
1. For FI documents, you enter the number of the prenumbered form in the Reference Number field of the new source document.
2. For SD documents, you enter the number of the prenumbered form in the Reference field of the new source document when you are creating the sales order (VA01 transaction)
3. Example:
The newly created eDocument will be seen in the 'Colombia eInvoice Contingency' process in cockpit
Once the technological issues are resolved, submit the eDocuments
1. Note: The InvoiceTypeCode will be 03.
Reverse the contingency configuration to allow the creation of the eDocuments normally
After reversal, the configuration appears as below:

In summary, effectively managing the contingency processes within the SAP DRC Colombia solution is crucial for maintaining compliance with DIAN regulations during technological disruptions. This blog has explored the necessary steps and considerations for setting up and navigating through contingency modes, whether the challenges arise from the electronic bill issuer's end or directly from DIAN.

Understanding the differentiation between 'InvoiceTypeCode' 03 and 04 helps in pinpointing the origin of the issue and deciding the appropriate response strategy. The outlined procedures ensure that, even in the face of technological difficulties, businesses can continue their operations by issuing invoices in contingency modes and maintaining necessary documentation for compliance and verification.

As technology evolves and challenges emerge, staying informed and prepared to handle such issues with the appropriate contingency plans will safeguard the integrity of electronic document transactions and support uninterrupted business operations.

Revolutionizing Taxation: Navigating VAT in the Digital Age (ViDA)

2024-04-19T15:40:04.736000+02:00

Tax regulation is a shifting terrain, constantly evolving with technological advancement and changing business needs. Once, VAT reporting had the luxury of time; now, the demand is for real-time precision. Increasing digitalization in tax administration is reshaping conventional practices. One upcoming challenge is VAT in the Digital Age (ViDA), a directive proposed by the European Commission on December 8, 2022. Designed to modernize the VAT system of the European Union (EU) with its 27 member states, it eliminates tax fraud while embracing digitalization. With the growth of the platform economy and the existing globalized economy the significance for collecting indirect taxes, like VAT, has become more prominent for all tax authorities. Stay updated with SAP's analysis of how these changes impact their solutions, through the regulatory change manager.

Powering Progress: European Commission's Strategy for a Unified, Digital, and Efficient VAT System

European Commission's Strategy: Transformative Legislative Proposals under three pillars:

1. E-invoicing and E-reporting: as of January 1, 2028

The first pillar is mandating VAT-based e-invoicing within the European Union and real-time digital reporting.

2. Platform Economy: as of January 1, 2025

The second pillar harmonizes the framework to charge VAT for the Platform Economy. All platform operators in passenger transport and short-term accommodation sectors will become responsible for VAT collection and reporting.

3. Single VAT Registration: as of January 1, 2025

The third pillar is the VAT registration process where businesses need to register just once to cater to customers across the EU. Using a single portal, businesses can comply with all VAT reporting obligations using a single sign-on.

Embracing the Future: Navigating the Transformative Shifts of ViDA with SAP

SAP is analyzing the impacts of these changes associated with ViDA.

To help you stay on top of the changes that will come with the ViDA initiative, SAP will be publishing further blogs detailing SAP solutions that will be impacted. In the meantime, get to know how SAP solution can help to unlock your tax transformation by attending FREE OpenSAP course (Unlocking Tax Transformation with SAP).

To make sure you don't miss any comments on this blog, subscribe to it! Click on the tick at the beginning of the article (above the publication date) and then select 'Subscribe' in the drop-down menu (log in to the SAP Community is required).

We will also be hosting webinars in the coming months, focusing on ViDA updates and the implications they have on your SAP system. Do not miss the webinar on ViDA hosted by USF on April, 24.

Stay tuned to our calendar of events on localization topics.

¿Cómo resolver el timbrado del proceso de anticipo de clientes en México?

2024-04-22T16:49:58.395000+02:00

Debido a que el best practice de SAP (5XU-Document and reporting compliance) no contempla el timbrado de anticipos de clientes utilizando la funcionalidad estándar de Solicitudes de anticipos y anticipos (esto es, utilizando CME de anticipos), entonces hay que ver otras opciones.

Primero debemos de tener en consideración los puntos que el SAT solicita para cumplir con este escenario y brevemente esto nos dice el SAT:

1. Emisión de la factura electrónica por el valor del anticipo. Al momento de recibir el pago del cliente hay que emitir esta factura.

2. Emisión de la factura electrónica por el valor total de la operación. Una vez que se ha levantado un pedido de venta y se entrega la mercancía, entonces se emite una factura por la venta del producto/servicio, y se indica aquí el UUID del anticipo relacionado.

3. Emisión de la factura electrónica de tipo “Egreso”. Debido a que hay un anticipo relacionado hay que informar el importe que se está aplicando del anticipo para que ahora el cliente ya solo pague el resto del valor total de la operación. En este paso se indica el UUID de la factura del producto/servicio entregado como CFDI relacionado.

Para mayor detalle del escenario mira el PDF de este link-> Caso_uso_Anticipo.pdf (sat.gob.mx).

Ahora teniendo claro el requerimiento, en seguida te detallo la solución que incluso SAP nos pone en los documentos del test script del Best practice de AR J59 de México, aunque como no se detalla ahí el proceso a cumplir con respecto a la generación de CFDIs, muchas veces no es claro al leerlo, pero aquí lo desgloso para mejor comprensión. Agrego que si revisas el J59 para USA verás las diferencias, pues para USA si se sugiere utilizar el proceso estándar de solicitud de anticipo o anticipo (CME).

J59 para USA, sugiere uso de Down payment request (CME):

J59 para MX, sugiere uso de Factura normal:

Pasos creación de anticipos con timbrado para México

Explicación de estos pasos:

1a) Se registra factura en el cliente por concepto de anticipo (FB70 / Create outgoing invoice / Factura desde SD)

Se manda a timbrar y aquí generamos nuestro primer UUID.

La contrapartida del cliente puede ser cualquier cuenta (balance o resultados, pues va a ser cancelada inmediatamente en el paso 2)

1b) Después de recibir el pago por extracto de cuenta bancario, se realiza la aplicación de esta cobranza a la factura recién creada de anticipo. (F-28 ó Post Incoming Payments)

El cliente se compensa en esta aplicación de cobranza contra la factura de anticipo.

Es importante notar que esta aplicación de cobranza no debe timbrarse con un complemento de pago, por lo que, si utilizarás el tipo de documento estándar DZ, habrá que ir al Cockpit del edocument para cancelar o borrar este documento y así no puedas timbrarlo, o bien puedes crear una nueva clase de documento la cual no estará en la configuración del eDocument, por tal motivo no saldrá en el Cockpit para timbrarla.

2) Se registra una nota de crédito inmediatamente después de registrar la factura y compensarla con el pago.

De esta manera le decimos al sistema que el cliente tiene un saldo a favor en su cuenta, es decir este es el importe del anticipo que quedará vivo hasta emitir la factura de la mercadería o servicio.

En este momento esta nota de crédito no debe ser timbrada, quedará ahí pendiente del timbrado hasta que emitamos la factura de la mercadería o servicio.

Además, en este punto la cuenta contrapartida o puente estará saldada, no tendrá ningún efecto.

3a) En el momento que ya entregues la mercadería o servicio, podrás generar la factura de dicha mercadería o servicio.

Esta factura debe contener el UUID del anticipo como CFDI relacionado. Para indicar este UUID relacionado, te recomiendo utilizar los textos de cabecera del documento contable o bien los textos en el documento de SD.

Usualmente el timbrado en el cockpit del edocument, no lee el UUID relacionado por lo que necesitarás solicitar ayuda para hacer esta pequeña adecuación en el código ABAP.

Habiendo hecho el ajuste para leer el UUID del anticipo relacionado, podrás ir al Cockpit del edocument y timbrar esta factura para obtener tu segundo UUID en este proceso.

3b) Ahora es momento de hacer el tercer timbrado, y es facturar la nota de crédito, la cual se genera como una factura tipo Egreso, pero antes de hacer el timbrado también es necesario indicar el UUID de la factura de la mercadería o servicio del paso 3a como un CFDI relacionado.

Igualmente te recomiendo hacer uso de estos textos de cabecera para indicar ahí el UUID relacionado.

Habiendo hecho esto y la adecuación al código para leer y pintar en el PDF/ XML a generar el UUID relacionado, podrás ir al cockpit del edocument y timbrar este último documento de este proceso.

Y finalmente para cerrar este proceso, los siguientes pasos ya dependerán de la situación, en un determinado caso podrás ir a compensar la nota de crédito con la factura de la mercadería o servicio, o tal vez esperar a un pago restante para compensar la factura completa.

En cualquier caso, ya son procesos manejables por las transacciones o aplicaciones estándar de SAP.

Espero esta información sea de tu interés y te ayude en tu actual o próximo proyecto.

Y si ya habías aplicado esta solución comenta o si tienes otra también.

Frase anónima "Lo mejor del día es despertar preocupado porque se te hizo tarde y darte cuenta de que es sábado."

New Reporting Activities for Withholding Tax Declarations in SAP Document and Reporting Compliance

2024-04-28T03:35:20.716000+02:00

As businesses expand globally, they face a complex web of regulatory compliance requirements. One of the most important obligations for enterprises is to meet their statutory reporting requirements accurately and on time. To help organizations with this challenge, SAP Document and Reporting Compliance provides a range of features and functionalities that enable customers to generate accurate and compliant statutory reports. Recently, SAP has introduced two new reporting activities for the Withholding Tax statutory reports, namely "Review Withholding Tax Items" and "Clear Withholding Tax Items" in the Run Statutory Reports app. In this blog, we will take a closer look at the withholding tax procedure and how SAP's solution simplifies this process for businesses.

Spoiler

Withholding Tax procedure

Navigating tax regulations can be daunting. The SAP Document and Reporting Compliance and Run Statutory Reports app simplify compliance with withholding tax declaration mandates. It provides a range of reporting functions for precise and streamlined withholding tax declarations, including the generation of tax certificates, the creation of tax reports, and the submission of tax declarations. Utilizing this app helps businesses remain up-to-date with tax laws and circumvent possible fines or penalties.

How do withholding reporting activities work?

Spoiler

SAP Document and Reporting Compliance, Withholding Statutory Report activities

Manage Withholding Tax Items "MWTI"

The MWTI activity allows business users to exclude one or more tax items from reporting periods by changing the tax reporting date. The app retrieves documents based on parameters from the statutory reporting task or the filter values provided in the MWTI activity screen, depending on the Withholding Tax Reporting Date field.

As a business configuration expert user you should ensure you completed the Setting Up the Withholding Tax Legal Form Report.
If the withholding tax reporting date is unavailable, you can run the Migration Report for Withholding Tax Reporting Date app to update the source documents.
To correct tax reporting errors, you can exclude documents, post Credit Memos/Delta postings, report documents later, change the withholding tax reporting date, or run a correction for statutory reports.

Once all the withholding tax items have been included or excluded as required, mark the activity status as COMPLETED.

Updatable documents cannot be revised after the reporting period has been closed. However, you can submit the correct documents by reversing the reporting period, posting a credit memo, or generating the withholding tax advanced compliance report in a correction run.Reviewing Withholding Tax Items.

After completing the activity, you can perform new reporting activities to review the withholding tax items available in the period and clear them for preparing the Withholding Tax Report.

The primary objective of the two newly introduced activities is to streamline the procedure of submitting legal forms for withholding tax items in order to guarantee adherence to the local tax laws and regulations. The accompanying flowchart for scrutinizing and authorizing the withholding tax is presented beneath, which takes you through every step and shows in reverse case if needed.

Spoiler

Review and Clear Withholding Tax flowchart

Review Withholding Tax Items "RWTI"

The RWTI reporting activity enables business users to review and finalize the list of withholding tax items for the reporting period.

Spoiler

Review Withholding Tax Items "RWTI"

As a business user, you can select the Run ID for a single company code and reporting dates and review the withholding tax items to ensure that the correct documents have been included in the reporting period.

If the withholding tax items for that Run ID are accurate, you can set it to "READY FOR CLEARING" status.

As a business configuration expert user, you should ensure the activation of the new reporting activity RWTI.
These withholding tax items will be the source the Clear Withholding Tax Items activity to create a clearing document, and the source for the Prepare Withholding Tax Report activity to generate the legal form

Clear Withholding Tax Items "CWTI"

The CWTI reporting activity allows business users to generate a clearing document for the withholding tax items before reporting the legal form

Spoiler

Clear Withholding Tax Items "CWTI"

As a business user, you can process the clearing and the payment of withholding tax to the tax authority for the Run ID that was updated as " READY FOR CLEARING" in the RWTI activity.

As a business configuration expert user you should ensure the activation of the new reporting activity CWTI, and you created a supplier corresponding to your tax authority in the business partner master data and Assigned Tax Authority and Accounting Document described in Making Additional Settings for Withholding Tax Legal Form.
As abusiness user, the new activity supports clearing only for the reporting entity's leading company code.
You should not post documents with varying recipient types at the line level. If a document contains line items with different recipient types, then the CWTI activity clears the entire document amount. This might lead to an inconsistency between the amount cleared and the amount reported in the legal form. The legal form only includes line items with the recipient type for the legal form.
Once the clearing document has been successfully generated, the report Run ID should be updated to " CLEARED " status in the RWTI activity.

Generate Withholding Tax Legal Form

Following the previously completed activities, and using the Run Statutory Reports app, you can generate the legal Withholding Tax report and perform further actions, such as view, analyze, and download the report output.

When the RWTI activity is active, the legal form is produced based on the withholding tax items generated in a report with a Run ID that has a " READY FOR CLEARING" or "CLEARED" status.
If the CWTI activity is active, it is essential to ensure that the withholding tax has been paid to the tax authority in compliance with local regulations.

Conclusion,

To ensure compliance when submitting the Withholding Tax legal form in Egypt, it is crucial to complete all necessary settings and include the appropriate documents within the reporting period. The Run Statutory Reports app offers reporting activities such as Manage, Review, and Clear Withholding Tax Items, which aid customers in fulfilling the withholding tax declaration requirements. These activities enable business professionals like GL Accountants, Tax Consultants, or AP Managers to manage withholding tax items effectively, ensuring they can include or exclude items, review and finalize the list, and clear the items for the remittance document submitted to the tax authority.

Taxpayers must comply with the tax authority's regulations by providing details of the remittance document, serving as evidence of tax payment within the reporting period, when filing the Withholding Tax legal form. Essentially, companies are required to declare and remit the withholding tax prior to submitting the legal form. For an in-depth guide on this procedure, the SAP Help Portal serves as a valuable resource.

Releases

The two new activities have been enabled in Egypt's local version of SAP Document and Reporting Compliance in the following release that support SAP Customers and Businesses operating in Egypt who are required to file the Withholding Tax Form 11 and Form 41.

The upcoming release is for the Oman local version in SAP S/4HANA Cloud Public Edition 2408.

Quick Demo

Spoiler

How SAP's solution simplifies the withholding tax reporting process for business in SAP Document and Reporting Compliance

Thank you for taking the time to read. I eagerly await your feedback and am available for any further larifications you may require.

デジタルインボイス・グローバル税務申告の対応について～SAP Document and Reporting Compliance概要～

2024-05-01T11:09:58.802000+02:00

【はじめに】

本ブログでは、日本や世界各国におけるや税務申告への対応を行っている担当者様に向けて、SAPソリューションでできることについてご紹介します。

デジタルインボイスへの対応については各社ご関心をお持ちのトピックかと思いますが、各国の仕様がばらばらであったり、ルールが改正されたり、全容を把握するのが難しいテーマかと思います。そのため、国内でデジタルインボイスに対応されようとしているお客様も、海外の子会社のデジタルインボイス要件に対応しようとしているお客様も、何にどう取り組めばよいのか、よくわからないことがあるのではないでしょうか。また、導入する仕組みも国によってばらばらということになると、現地の状況を本社が確認するのはとても困難です。このような状況ですと、対応の遅れによるコンプライアンスリスクが懸念されることはもちろん、M&Aにより海外で法人を買収し、ビジネス基盤を拡大したいという場合の足かせになることもあり、事業展開の阻害要因にもなりえます。

また、海外子会社が現地パッケージを採用し、各国ごとに異なるシステムの運用を行うことになると、メンテナンス業務の複雑化による対応工数・コストの増加を招く懸念があります。また、業務システムとインボイス送信・電子申告用のシステムが別々だと、データ連携時の仕組みの構築やメンテナンス負荷がかかることはもちろん、業務データと送信データの整合性の担保にかかわる対応コストがかかることも想定されます。

今回は、そのようなお悩みを抱えている業務担当者様およびIT担当者様に向けて弊社デジタルインボイスおよび法定レポート対応機能であるSAP Document and Reporting Complianceについてご紹介いたします。

【SAP Document and Reporting Compliance概要】

SAP Document and Reporting Complianceは、デジタルインボイスの送受信や税務当局への法定レポートの提出をサポートするソリューションです。特徴として、SAP S/4HANAに統合された製品であるため、業務伝票が生成されたタイミングでリアルタイムかつ自動で送信用データが生成される仕組みになっており、それをそのため、業務データとデジタルインボイスや申告用データとの間に一貫性が担保されているのが特徴です。また、2024年4月現在で55か国、500シナリオのSAP標準コンテンツを用意しており、パートナー企業様が提供しているコンテンツを組み合わせてお使いいただくことも可能で、世界各国でビジネスを行っているお客様のグローバルな法要件を一つのプラットフォームで管理することができます。一つのシステムで各国の税務要件を管理できることでシステムの保守性が向上し、ITの担当者の負荷の軽減にもつながります。

【SAP Document and Reporting Complianceアーキテクチャ】

本ソリューションのアーキテクチャは大まかには上記の図の通りです。左側がERP本体、そして生成された送信データを連携するのが中央の領域です。SAP Document and Reporting Complianceと呼んでいる範囲は、左と真ん中の領域を合わせた部分です。右側の紫で表しているのは、デジタルインボイスの連携先となるPeppolネットワークや各国の税務当局のポータルサイトです。

オレンジで表しているERPは業務伝票からデジタルインボイスや電子申告用データの生成や、法定レポートを出力する機能を有しており、青や緑のSAP Buisness Tecnology Platformと呼ばれる機能によって生成されたデータを各種ネットワークおよびポータルに連携することができるようになっています。

ここまで、SAP Document and Reporting Complianceの概要を見ていきました。
それでは、ここからSAP Document and Reporting Complianceの機能のイメージを見ていきましょう。
今回は、デジタルインボイスや法定レポートの提出状況を確認できる画面をご紹介します。

【デジタルインボイスで使用する画面のイメージ】

下図は、各国のデジタルインボイスの送受信の状況を確認できる画面です。画面左側では、各国ごとにツリー構造でデジタルインボイスのシナリオおよび数が表示されています。シナリオを選択すると右部に詳細データを表示できますが、ここでは、日本のデジタルインボイスのみを表示しています。一行ごとに、一件のデジタルインボイスを表しています。ステータスが緑色になっている場合は問題なく送受信が行われていることを表します。もし、各電子伝票の送受信でエラーが発生している場合は、緑ではなく赤いアイコンが表示されます。各電子伝票をクリックすると元となっている会計伝票を参照していただくことができます。

【法定レポート提出に使用する画面のイメージ】

また、各国の法定レポートの提出状況をダッシュボード形式で確認することもできます。下の画面では、今月の日本本社と子会社のある国の法定レポートの提出進捗を確認しています。左のダッシュボードを見ると、各国で求められているレポートの数およびその提出が「完了」しているか、あるいは「期日超過」「期日間近」「期日が後」なのかを把握でき、本社の担当者はどの国に対するサポートを優先するべきかを直感的に判断することができます。また、ダッシュボード内の6の数字は「期日超過」「期日間近」のレポートの総数を表しており、優先的な対応が必要となるレポートがどのくらいあるかを確認することが出ます。レポート進捗をクリックすると、画面が遷移し、各国の法定レポートの提出を行うにあたっての処理タスクを確認できます。

下図が、各種法定レポート提出にあたって必要となるタスクの進捗を確認する画面です。今回は、日本で2024年3月から4月に提出対象となっている各種法定レポートのタスク処理状況を確認します。提出期限からどのくらい遅れているのか、レポートを提出のために必要なアクションがどのくらい残っているのかを確認をすることができるようになっています。対象のレポートの行をクリックすると、レポートのデータ生成実行などレポート提出に必要なタスク処理を行うことができます。

【おわりに】

ここまでブログを読んでいただき、ありがとうございました。各国のデジタルインボイスや法定帳票の提出を行うために、SAP Document and Reporting Complianceをお使いいただくことで、ERPに内包された機能を使って効率的に導入および業務運営を行うことができます。もし、ご興味を持っていただけましたら、弊社営業およびこちらの公式ホームページからお問い合わせをいただけますと幸いです。

NF3-e Technical Note 2024.001: New Fields Added to Electronic Nota Fiscal for Electrical Energy

2024-05-08T17:22:26.898000+02:00

(Versão em português aqui)

Hi everyone,

The SAP Document and Reporting Compliance, outbound invoicing option for Brazil team has released updates on the mapping for XML files in the Electronic Nota Fiscal for Electrical Energy (NF3-e).

NF3-e Technical Note 2024.001

This release complies with the SEFAZ NF3-e Technical Note 2024.001. The new update on NF3-e allows you to create electronic notas fiscais for electrical energy (model 66) with the following fields using EDOC_BR_ISU_EE_MAP_FILL_AUTH BAdI.

ICMS60 group: The vICMSDeson (Exempt ICMS) and cBenef (Tax Benefit Code for RBC) fields were added to the XML file layout, and both are optional.
ICMS90 group: The vICMSDeson (Exempt ICMS) and cBenef (Tax Benefit Code for RBC) fields were also added to the XML file layout, and both are optional too. The pFCP (Tax Rate for FCP Deferral) and vFCP (FCP Value) fields were added for the Fundo de Combate à Pobreza (FCP), and both are optional in the XML file layout.

The XML schema and mapping have been updated in our service, and it is not necessary to implement SAP Notes for this change in your backend system. For more details on this update, read SAP Note 3460797.

NF3-e Nota Técnica 2024.001: novos campos na nota fiscal eletrônica de energia elétrica

2024-05-08T17:37:20.211000+02:00

(English version here)

Olá pessoal,

O time de SAP Document and Reporting Compliance, opção de emissão de fatura de saída para o Brasil entregou atualizações no mapeamento de arquivos XML de nota fiscal eletrônica de energia elétrica (NF3-e).

Nota Técnica 2024.001 de NF3-e

Esta versão está conforme a Nota Técnica 2024.001 de NF3-e da SEFAZ. A nova atualização de NF3-e permite criar notas fiscais eletrônicas de energia elétrica (modelo 66) com os seguintes campos utilizando a BAdI EDOC_BR_ISU_EE_MAP_FILL_AUTH.

Grupo ICMS60: foram adicionados ao layout do arquivo XML os campos vICMSDeson (Valor do ICMS desonerado) e cBenef (Código de Benefício Fiscal), ambos opcionais.
Grupo ICMS90: os campos vICMSDeson (Valor do ICMS desonerado) e cBenef (Código de Benefício Fiscal) também foram adicionados ao layout do arquivo XML, sendo ambos opcionais. Os campos pFCP (Percentual relativo ao FCP) e vFCP (Valor relativo ao FCP) foram adicionados para o Fundo de Combate à Pobreza (FCP), e ambos são opcionais no layout do arquivo XML.

O XML Schema e o mapeamento foram atualizados em nosso serviço, não sendo necessária a implementação de SAP Notes para esta alteração em seu sistema. Para mais detalhes sobre esta atualização, leia a SAP Note 3460797.

Blog posts relacionados:

Dashboard do Usage Analytics

Para obter um passo a passo sobre como usar a solução de nota fiscal eletrônica de energia elétrica (NF3-e), consulte as seguintes páginas do portal SAP Help:

Você pode receber alerta por email quando novas SAP Notes forem lançadas ou atualizadas nos componentes listados abaixo; basta seguir as instruções do SAP Knowledge Base Article 2171560.

CA-GTF-CSC-EDO-BR-OU
CA-GTF-CSC-EDO-BR
FI-LOC-NFE-BR-OUT
LOD-LH-NFE

Acesse o gerenciador de modificações legais para ter uma noção do que está planejado para ser suportado. Consulte o SAP Knowledge Base Article 3421995 e a página Regulatory Change Manager para entender como usar esta ferramenta.

Gostou desse post? Dê um “like” (kudos) e compartilhe o conteúdo com seus colegas. Sinta-se à vontade para deixar suas perguntas no SAP Community e ler posts semelhantes no blogging space do SAP Document and Reporting Compliance.

Para acompanhar as últimas notícias da NF-e, siga a tag SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica) e a comunidade SAP Document and Reporting Compliance.

Obrigado e até a próxima,
Thiago

Adapting to technical annex 1.9 for Colombia: Updates for SAP S/4HANA and SAP ERP

2024-05-08T21:54:18.119000+02:00

Hello everyone,

According with the new regulation, companies in Colombia are required to adapt to the changes detailed in resolution 000165 and technical annex version 1.9. In this blog post, we will cover the following topics available for SAP S/4HANA and SAP ERP:

Rounding removal
Healthy taxes
Foreign currency in export invoices
Emission and signing date of electronic documents
Period of time for credit and debit notes
CUFE algorithm

Rounding removal
The system does not send the <RoundingAmount> tag in the XML file for invoices anymore as rounding for values related with taxes is disabled. This means the following validations rules from DIAN are eliminated: FAS18, FAX18, CAS18, CAX18, DAS18, DAX18.

Healthy taxes
The system allows you to display information of the taxes for ultra-processed edible goods, liquor consumption, ultra-processed sugary drinks, and plastic products. To do so, you create a new condition type or tax code related to the tax and add this to the Define Fix Values (/AIF/V_FFIX) Customizing activity. See the steps on the post implementation instructions of SAP Note 3420596.

Foreign currency in export invoices
Electronic documents for export invoices must be reported in Colombian pesos. If you want to use the PDF generated by the system in a foreign currency, you inform the <Interoperability> tag group of the UBLExtension and calculate the values. This tag group is optional and does not have validation rules in the system.

With the new tags, you can implement the BAdI: Enhancements for eDocument (EDOC_ADAPTOR). Check the attachments section of SAP Note 3426328 for an implementation example.

Be aware that when you convert the currency in the BAdI, you must also recalculate the CUFE.

Emission and signing date of electronic documents
The emission date of the electronic documents must be equal to the signing date of these electronic documents. To support different time zones, we added a new parameter in the CPI where the system converts an alternative time zone to the Colombian one, avoiding the documents to be signed in different times.

To avoid this inconsistency, update your Cloud Platform Integration (CPI) to version 2.0.13.

Period of time for credit and debit notes
You can use the <Notes> XML tags from the BAdI: Enhancements for eDocument (EDOC_ADAPTOR) to inform the period of time you want to report credit or debit notes.

CUFE algorithm
When you submit a credit or debit note, the @schemeName attribute of the <UUID> tag in the XML file must be filled in. You can implement the BAdI: Enhancements for eDocument (EDOC_ADAPTOR) with the respective CUFE algorithm.

SAP Notes relevant to this legal requirement
You can implement the following SAP Notes to update your solution:

SAP Note 3420596 - Technical annex 1.9 for Colombia: Rounding removal and healthy taxes
SAP Note 3426328 - Technical annex 1.9 for Colombia: Foreign currency proxy changes
SAP Note 3459015 - Technical annex 1.9 for Colombia: Foreign currency proxy changes - Part 2

Did you like this post? Give it kudos and share the content with your colleagues, and feel free to leave a feedback, comment or question in the space below.

Regards,
Aleshane Ghisleri
#SAPGoGlobal #SAPLocalization

Adapting to technical annex 1.9 for Colombia: Updates for SAP S/4HANA Cloud

2024-05-09T15:07:51.289000+02:00

Hello everyone,

Rounding removal
Healthy taxes
Foreign currency in export invoices
Emission and signing date of electronic documents
Period of time for credit and debit notes

Rounding removal
The system does not send the <RoundingAmount> tag in the XML file for invoices anymore as rounding for values related with taxes is disabled. This means the following validations rules from DIAN are eliminated: FAS18, FAX18, CAS18, CAX18, DAS18, DAX18.

Healthy taxes
The system allows you to display information of the taxes for ultra-processed edible goods, liquor consumption, ultra-processed sugary drinks, and plastic products. To do so, you create a new condition type or tax code related to the tax and add this to the Configure Value Mapping app. See Configuring Replace Fix Values Using Value Mapping (FIX_VALUE_REPLACER).

The system automatically calculates taxes for ultra-processed edible goods. For liquor consumption, ultra-processed sugary drinks, and plastic products, you implement the BAdI: Adapt Invoice XML (EDOC_CO_ADAPT_XML_INVOICE), the BAdI: Adapt Credit Note XML (EDOC_CO_ADAPT_XML_CREDIT_NOTE) or the BAdI: Adapt Debit Note XML (EDOC_CO_ADAPT_XML_DEBIT_NOTE). See App Extensibility: eDocument Cockpit or Manage Electronic Documents.

With the new tags, you can implement the BAdI: Adapt Invoice XML (EDOC_CO_ADAPT_XML_INVOICE), the BAdI: Adapt Credit Note XML (EDOC_CO_ADAPT_XML_CREDIT_NOTE) or the BAdI: Adapt Debit Note XML (EDOC_CO_ADAPT_XML_DEBIT_NOTE).

Be aware that when you convert the currency in the BAdI, you must also recalculate the CUFE.

To avoid this inconsistency, update your Cloud Platform Integration (CPI) to version 2.0.13.

Period of time for credit and debit notes
You can use the <Notes> XML tags from the BAdI: Adapt Credit Note XML (EDOC_CO_ADAPT_XML_CREDIT_NOTE) or the BAdI: Adapt Debit Note XML (EDOC_CO_ADAPT_XML_DEBIT_NOTE) to inform the period of time you want to report credit or debit notes.

CUFE algorithm
When you submit a credit or debit note, the @schemeName attribute of the <UUID> tag in the XML file must be filled in. You can implement the BAdI: Adapt Credit Note XML (EDOC_CO_ADAPT_XML_CREDIT_NOTE) or the BAdI: Adapt Debit Note XML (EDOC_CO_ADAPT_XML_DEBIT_NOTE) with the respective CUFE algorithm.

These changes are already available in your system and will be delivered as default with SAP S/4HANA Cloud 2408.

Did you like this post? Give it a Like and share the content with your colleagues, and feel free to leave a feedback, comment or question in the space below.

Regards,
Aleshane Ghisleri
#SAPGoGlobal #SAPLocalization

SAP Community - SAP Document and Reporting Compliance

SAP Document and Reporting Compliance, Cloud Edition New Role Collection

Customer downpayment in S4HC – temporary workaround for Hungary

Updates on Conhecimento de Transporte Eletrônico and Manifesto Eletrônico de Documentos Fiscais

Generate Custom Legal Certificates in SAP DRC

Summary:

Government SEFAZ Technical Notes with Optional Events

SAP Document and Reporting Compliance Brazil: Atualizações no CT-e MDF-e

Colombia Production Number Range Retrieval from DIAN

Prerequisites:

Important Notes:

Number Range Retrieval Steps:

Next Steps After Range Retrieval from DIAN:

Maintain Ranges for Credit notes and Debit notes manually

Assign Number Ranges to eDocument Types

SAP Document and Reporting Compliance Brazil: Dashboard do Usage Analytics

Navigating Tax Requirements in the Digital Era: Learn How SAP Helps You Revolutionizing Compliance

Register now, don't miss this learning opportunity!

Did You Set Up Your Cloud Edition Before April 26, 2023? Your Attention Is Needed!

Introducing the market standard of electronic invoicing for the United States

SAP Document and Reporting Compliance - 'Colombia' - Contingency Process

DIAN Contingency - Tipo - 04

Electronic Bill Issuer Contingency - Tipo -03

SDC Colombia Contingency Process setup:

Communication Exception Status in EDOC Cockpit

Steps to be followed for DIAN Contingency mode:

Sending to DIAN requested

Steps to be followed for Contingency at the invoice issuer's System:

Revolutionizing Taxation: Navigating VAT in the Digital Age (ViDA)

¿Cómo resolver el timbrado del proceso de anticipo de clientes en México?

New Reporting Activities for Withholding Tax Declarations in SAP Document and Reporting Compliance

デジタルインボイス・グローバル税務申告の対応について ～SAP Document and Reporting Compliance概要～

【はじめに】

【SAP Document and Reporting Compliance概要】

【SAP Document and Reporting Complianceアーキテクチャ】

【デジタルインボイスで使用する画面のイメージ】

【法定レポート提出に使用する画面のイメージ】

【おわりに】

NF3-e Technical Note 2024.001: New Fields Added to Electronic Nota Fiscal for Electrical Energy

NF3-e Nota Técnica 2024.001: novos campos na nota fiscal eletrônica de energia elétrica

Adapting to technical annex 1.9 for Colombia: Updates for SAP S/4HANA and SAP ERP

Adapting to technical annex 1.9 for Colombia: Updates for SAP S/4HANA Cloud

デジタルインボイス・グローバル税務申告の対応について～SAP Document and Reporting Compliance概要～