Get started with electronic invoicing for Paraguay

This article helps you set up electronic invoicing for Paraguay. It lists configuration steps that depend on the country or region in Microsoft Dynamics 365 Finance and Microsoft Dynamics 365 Supply Chain Management. These steps supplement Electronic invoicing setup. For last mile integration with the Paraguayan tax authority, Microsoft partners with Edicom.

After you set up electronic invoicing, generate, digitally sign, and submit XML invoice files to the Edicom authorized certification provider (PAC) according to the regulatory requirements in Paraguay.

Prerequisites

Before you start, make sure you meet these prerequisites.

1. Set up the Paraguayan legal entity. Learn more in Set up a legal entity and tax information for Paraguay.

2. Review the Electronic invoicing overview.

3. Complete the common Electronic invoicing service configuration described in Electronic invoicing configuration.

4. Enable the following features in Feature management:

   • Electronic invoicing integration

   • Electronic invoicing integration resubmits document from failed action

   • Execute upda1. Import the following Electronic reporting (ER) format configurations. Learn more in Import Electronic reporting (ER) configurations from Dataverse and Import Electronic reporting (ER) configurations.reporting-import-ger-configurations.md).

   • Customer invoice context model

   • Edicom response error log import

   • Edicom Response Processing LATAM

   • Edicom source file response import format

   • Inventory-PY

   • PackingSlip (PY)

   • Project e-invoice (PY)

   Note

   These formats build on the corresponding LATAM format configurations, which use the Invoice model LATAM and Invoice model mapping LATAM configurations. The system imports all other required configurations automatically.

Configure the electronic invoicing feature

The "Paraguay Electronic Invoice (PY) Edicom integration for Paraguay" feature is an outbound flow that issues the following sales documents.

The feature publishes some parameters with default values. Before you deploy the electronic invoicing feature to the service environment, add a feature that's based on the Microsoft-provided feature and complete the common parameters on the Feature parameters tab. Review the default values and update them as needed so they reflect your business operations.

Edicom interactions for Paraguay

Paraguay has three core interactions with Edicom in the base flow:

1. Invoice submission
2. Signed XML retrieval
3. Status retrieval of the submitted invoice

Each of these interactions requires common parameters, such as Edicom connection details and the authentication token provided by Edicom. These parameters are reused across the feature setup for all document types. Edicom supplies these values during the company's onboarding process.

Paraguay electronic invoice (PY) Edicom integration

To integrate Edicom for Paraguay electronic invoices, follow these steps:

1. Import the latest version of the Paraguay Electronic Invoice (PY) Globalization feature as described in Import features from the repository. The following illustrations show what the feature looks like after you import it from Dataverse.

   

   If you go to the Configuration tab, as shown in the previous screenshot, there's a page displaying information similar to the following table:

   Name	Version	Status	Country/region code
   Edicom Response Processing LATAM	13.2.5	Completed
   Edicom response error log import	13.1	Completed
   Inventory (PY)	296.140.32.25	Completed	PY
   PackingSlip (PY)	296.140.32.31	Completed	PY
   Project e-invoice (PY)	296.140.19	Completed	PY

   Note

   The version numbers can change if the formats are updated. The table is for illustrative purposes only.

2. Create a copy of the imported Globalization feature, and select your configuration provider. Learn more in Create a Globalization feature.

3. On the Versions tab, confirm that the Draft version is selected.

4. On the Feature parameters tab, specify values for the following connection and integration parameters that are required for interoperation with Edicom's API.
   These parameters are general purpose and apply to all actions, so configure them once here.

   Tip

   The following table provides example values for each feature parameter, so you can understand the type of data that should be entered for each one. These values are illustrative only and were provided by Edicom to Microsoft for testing purposes. When you're onboarded, Edicom provides you with your own unique values to use in your configuration.

   Parameter	Description	Data type	Value
   EdicomApplication	Application	String	<ID_PROVIDED_EDICOM>
   EdicomDomain	Domain	String	<ID_PROVIDED_EDICOM>
   EdicomGetStatusSchema	Get status schema name	String	IN_DOCUMENT_STATUS_MICROSOFT_UY
   EdicomGroup	Group	String	<GROUP_ID>
   EdicomSignedXMLSchema	Signed XML schema name	String	EDIWIN-SOURCE-FILE_XML_CFE_ADENDA_<ID_PROVIDED_EDICOM>
   EdicomSubmitInvoiceDestination	Destination name	String	<ID_PROVIDED_EDICOM>_EDIWIN
   EdicomSubmitInvoiceSchema	Submit invoice schema name	String	OUTBOUND_DOCUMENT_MICROSOFT_UY
   EdicomToken	Auth token	Secret name	EdiwinParaguayToken
   EdicomWebServiceURL	Web service URL	String	https://ipaasgw.edicomgroup.com

   Tip

   When configuring the feature parameters for Edicom integration, follow these steps:

   • Select Application, and enter the service ID number you obtained from Edicom.
   • Select Domain, and enter the same service ID number.
   • Select Get status schema name, and enter the provided schema name.
   • Select Group, and enter the group code you received.
   • Select Signed XML schema name, and enter the appropriate schema name.
   • Select Destination name, and enter the service ID number concatenated with "_EDIWIN". For example, if your service ID is 123456, enter 123456_EDIWIN.
   • Select Submit invoice schema name, and enter the schema name.
   • Select Auth token, and choose the name of the secret you created for the token.
   • Select Web service URL, and verify the web address is correct.

5. The copy of the feature always starts in a Draft version. Regardless of whether you made changes, you must complete, publish, and deploy the feature as described in Complete and deploy a Globalization feature.

Outbound flow pipeline

There are three electronic invoice formats for Paraguay included in the Paraguay Electronic Invoice (PY) feature. Each format requires its own setup and configuration. The formats are:

• Inventory (PY)
• PackingSlip (PY)
• Project e-invoice (PY)

The following sections provide general configuration steps that apply to all formats. They also explain specific considerations for each format.

Electronic invoice feature

Setups view

After you import the feature, you see five tabs: Versions, Configuration, Feature parameters, Setups, and Tags. Select Setups, then select View to open the Feature version setup page.

Feature version setup

Use this page to review and set up the feature for Paraguay. The page has four sections: Processing pipeline, Applicability rules, Variables, and Parameters.

Processing pipeline

The Set up Actions and Parameters section is divided into two distinct grids:

Top right – processing pipeline

The Processing pipeline grid is similar to the following table:

Bottom right – parameters

The lower grid shows the parameters for the selected processing action. These parameters fine-tune the step's behavior. Each entry lists a name, description, data type, and value so you can set processing logic for business needs.

Transform document parameters

Linking the correct format in Transform document parameters

When configuring the Transform document action in the processing pipeline, ensure the following:

• Configuration: Set this to the exact name of the feature format you're configuring.

  • For example:
    • Project e-Invoice (PY) → Configuration: Project e-Invoice (PY)
    • Inventory e-Invoice (PY) → Configuration: Inventory (PY)
    • e-Packing Slip (PY) → Configuration: PackingSlip (PY)

• Configuration Integration Point:

  • Use InvoiceCustomer for inventory formats (Inventory (PY), PackingSlip (PY)).
  • Use InvoiceProject for project formats (Project e-Invoice (PY)).

Integrate with Edicom parameters

Get signed XML from Edicom parameters

Get invoice status from Edicom parameters

Process response parameters

Terminate pipeline parameters

Applicability rules and feature setup scope

Configure applicability rules so the service can find the correct Electronic Invoicing Globalization feature. These applicability rules are provided out of the box by checking the legal entity’s International Organization for Standardization (ISO) country/region code.

Applicability rules for Paraguayan electronic invoice formats

The following applicability rules for each electronic invoice format for Paraguay. Replace <Legal Entity ID> with the actual ID of your legal entity.

Inventory PY

Packing slip PY

Project PY

Variables

The following variables are used in the outbound data flow actions of the Paraguayan feature. (These variables are provided out of the box.)

• BusinessDocumentDataModel – The Business Document Data model variable that is received from Finance or Supply Chain Management and transformed into the format that is required for submission.
• SignedXML – The signed XML variable that is sent back to Finance or Supply Chain Management. This variable contains the base64-encoded response body from the Get Signed XML from Edicom step. It's used in the response types to save the signed XML that is obtained from Edicom as an attachment to the invoice journal. It's also used to generate printable reports through QR codes.

After you import the Electronic invoicing for Paraguay feature with the default setup, follow the next steps to set up electronic documents.

Setups > Application setup

To configure the mapping between Dynamics 365 Finance source tables and electronic document formats, go to the Setups tab within the Electronic invoice feature section, and then select Application Setup. This step lets you define how data from Finance is linked to the correct electronic invoice formats for Paraguay.

The following grid defines the link between the source table in Dynamics 365 Finance, the document context model, and the mapping configuration used for electronic invoicing:

Configure electronic document parameters

To configure electronic document parameters, follow these steps:

1. Import the Paraguay-specific ER configurations for the document context and electronic document model mapping. Learn more in Set up Electronic document parameters.
2. Go to Organization administration > Setup > Electronic document parameters.
3. In the Electronic document section, add records for the Customer Invoice journal and Project invoice table names.
4. For each table name, set the Document context and Electronic document model mapping fields as in step 1.

On the Electronic Document Parameters page in Dynamics 365 Finance, the navigation pane shows the following options:

• Electronic Document

• Features

• Electronic Invoicing

• Integration Channels

For the Electronic Document option, the Electronic Reporting section appears.

Within Electronic Reporting, the grid lists the electronic document configurations. It includes associations between:

• The source table name

• The document context model and context

• The electronic document model mapping

• The final mapping name used for generating the electronic invoice.

This configuration controls how Dynamics 365 Finance maps internal data models to external electronic formats for submission to tax authorities or service providers.

Configure the grid as follows:

1. Save your changes, and close the page.

2. For each table name, follow these steps:

   1. Select Response types, then select New to create a response type from the back end, and enter these values:

      • In the Response type field, enter SignedXML (default). See the Variables section.
      • In the Description field, enter a meaningful name, or leave it blank.
      • In the Submission status field, select Pending.
      • In the Model mapping field, select Edicom source file response format.

   2. Repeat the preceding step, but set the Submission status field to Pending update actions execution. This setting lets you loop a subset of pipeline actions to pull updated statuses and other information for submitted documents from the tax authority.

   Response type	Description	Submission status	Data entity name	Model mapping
   SignedXML	Signed XML obtained from EDICOM	Pending		Edicom source file response import format
   SignedXML	Signed XML obtained from EDICOM	Pending update actions execution		Edicom source file response import format

   Note

   The response includes the signed XML obtained from Edicom. The system stores this signed XML as an attachment to the corresponding invoice journal. The system uses it to generate printable invoices with QR codes.

Issue electronic invoices

After you complete the required configuration steps, generate and submit electronic invoices for posted invoices. Go to Organization administration > Periodic > Electronic documents > Submit electronic documents. For more information, see Submit electronic documents.

Check submission results. Go to Organization administration > Periodic > Electronic documents > Electronic document submission log, and select the required document type. For more information, see Work with Electronic document submission log.

For Paraguay, after you submit the invoice, the submission status changes to Pending update actions execution. The response body might be empty for the signed XML and for the call that gets the invoice status. An empty response body indicates the XML isn't available immediately after submission. To address the pending status, use the Execute update actions function. This function resumes the pipeline from the action that's marked as an update action. It then runs subsequent actions in a loop. The status changes to Executing, and after a few seconds reverts to Pending update actions execution.

When you review the submission details, you see that the steps run again. This time, the signed XML is received.

After the outbound flow completes, the signed XML is attached to the invoice journal as EdicomSourceFile.

For Paraguay, the Process response action completes the pipeline after a few minutes.

More resources

• Electronic invoicing service overview

• Get started with electronic invoicing service administration

• Set up electronic invoicing

• Electronic invoicing service independent software vendor (ISV) last mile connector

• Dynamics 365 Country/Region expansion: localizations for LATAM Countries/Regions | June 27, 2024

• Dynamics 365 Country/Region expansion: localizations for LATAM Countries/Regions | Dynamics 365 FastTrack Tech Talks (youtube.com)

• Finance Localization for LATAM: Update on more Countries/Regions | Dynamics 365 Fast Track TechTalk | Jun 23, 2025

• Finance Localization for LATAM: Update on more Countries/Regions | Dynamics 365 Fast Track TechTalk (youtube.com)