Get started with Electronic invoicing for Costa Rica

This article provides information to help you get started with Electronic invoicing for Costa Rica. It guides you through the configuration steps that are country/region-dependent in Microsoft Dynamics 365 Finance or Microsoft Dynamics 365 Supply Chain Management. These steps complement the steps that are described in Electronic invoicing setup. For the last-mile integration with the Costa Rican Tax Authorities, Microsoft partners with Edicom.

After you configure Electronic invoicing, you can generate, digitally sign, and submit the XML files of electronic invoices to the Edicom authorized certification provider (PAC) according to the regulatory requirements in Costa Rica.

Prerequisites

Before you begin the procedures in this article, complete the following prerequisites:

1. Ensure that the settings for the Costa Rican legal entity are in place. For more information, see Set up legal entity and tax information for Costa Rica.

2. Configure electronic invoice parameters for Costa Rica.

3. Gain familiarity with and understanding of Electronic invoicing as it's described in Electronic Invoicing service overview.

4. Complete the common part of Electronic Invoicing service configuration as it's described in Electronic invoicing configuration.

5. Enable the following features in Feature management:

   • Electronic invoicing integration
   • Electronic invoicing integration resubmit document from failed action
   • Execute update actions for submitted documents

6. Make sure that the following Electronic reporting (ER) format configurations are imported. For more information, see: Import Electronic reporting (ER) configurations from Dataverse, Import Electronic reporting (ER) configurations.

   • Inventory e-invoice (CR)
   • Inventory Credit Note (CRI)
   • Inventory Debit Note (CRI)
   • Inventory Export e-Invoice (CRI)
   • Project e-invoice (CR)
   • Project Credit Note (CRI)
   • Project Debit Note (CRI)
   • Project Export e-Invoice (CRI)
   • Purchase e-invoice (CRI)
   • Payment Receipt (CRI)
   • Customer invoice context model
   • Edicom source file response import format
   • Edicom Response Processing LATAM
   • Edicom Response Processing CR
   • Edicom response error log import

   Note

   These formats are based on the corresponding LATAM format configurations that use the Invoice model LATAM and Invoice model mapping LATAM configurations. All other required configurations are automatically imported.

Country/region-specific configuration for Electronic invoicing for Costa Rica

The Costa Rica electronic invoice (CRI) "E-Invoicing for Costa Rica: ISV last-mile connector with Edicom" feature represents an outbound flow for issuing the following sales documents:

Some parameters of the feature are published with default values. Before you deploy the Electronic invoicing feature to the service environment, add a feature that is based on the Microsoft-provided feature, and complete the common parameters on the Feature parameters tab. Review the default values, and update them as required, so that they better reflect your business operations.

Edicom Interactions for Costa Rica

For Costa Rica, the base flow includes at least three core interactions with Edicom:

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. The feature setup for all document types reuses these parameters. Edicom supplies these values during the company's onboarding process.

Costa Rica Electronic Invoice (CR) Edicom integration for Costa Rica

1. Import the latest version of the Costa Rica Electronic Invoice (CR) 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, you see a page that displays 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.3	Completed
   Payment Receipt (CRI)	296.152.5	Completed	CR
   Purchase e-invoice (CRI)	296.152.14	Completed	CR
   Inventory Credit Note (CRI)	296.152.55.41	Completed	CR
   Inventory Debit Note (CRI)	296.152.55.41	Completed	CR
   Inventory e-invoice (CR)	296.152.55.46	Completed	CR
   Inventory Export e-Invoice (CRI)	296.152.55.29	Completed	CR
   Project Credit Note (CRI)	296.152.27.22	Completed	CR
   Project Debit Note (CRI)	296.152.27.21	Completed	CR
   Project e-invoice (CR)	296.152.27.22	Completed	CR
   Project Export e-Invoice (CRI)	296.152.27.6	Completed	CR

   Note

   The version numbers might 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. For more information, see 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 are used across the different actions in the setups, so you only need to configure them once in this section.

   Tip

   The following table provides example values for each feature parameter, so you can understand the type of data that you should enter 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	EdiwinCosta RicaToken
   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 is always created as a Draft version. Regardless of whether you make changes, you must complete, publish, and deploy the feature as described in Complete and deploy a Globalization feature.

Outbound flow pipeline

The Costa Rica Electronic Invoice (CR) feature includes 10 electronic invoice formats for Costa Rica. Each format requires its own setup and configuration. The formats are:

• Inventory e-invoice (CRI)
• Inventory Credit Note (CRI)
• Inventory Debit Note (CRI)
• Inventory Export e-Invoice (CRI)
• Payment Receipt (CRI)
• Project e-invoice (CRI)
• Project Credit Note (CRI)
• Project Debit Note (CRI)
• Project Export e-Invoice (CRI)
• Purchase e-invoice (CRI)

The following sections provide guidance on the general configuration steps that apply to all 10 formats. They also explain specific considerations and requirements for each individual format, so you can ensure that each one is configured correctly according to its unique needs.

Electronic invoice feature

Setups-View

After you import the feature, the second screenshot shows five tabs: Versions, Configurations, Feature parameters, Setups, and Tags. Select the Setups tab, then select View. This action opens the Feature version setup page:

Feature version setup

This page allows you to review and configure the details of the feature setup for Costa Rica. On the left side of this page, you see four sections: Processing pipeline, Applicability rules, Variables, and Parameters.

Processing pipeline

The Setup Actions and Parameters section contain 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 associated with the selected processing action. These parameters allow for fine-tuning of the selected step’s behavior. Each entry includes a parameter name, description, data type, and value, enabling you to configure processing logic according to your business requirements.

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 value to the exact name of the feature format you're configuring.
  • For example:
    • Inventory e-invoice (CR) → Configuration: Inventory e-invoice (CR)
    • Inventory Credit Note (CRI) → Configuration: Inventory Credit Note (CRI)
    • Inventory Debit Note (CRI) → Configuration: Inventory Debit Note (CRI)
    • Inventory Export e-Invoice (CRI) → Configuration: Inventory Export e-Invoice (CRI)
    • Project e-invoice (CR) → Configuration: Project e-invoice (CR)
    • Project Credit Note (CRI) → Configuration: Project Credit Note (CRI)
    • Project Debit Note (CRI) → Configuration: Project Debit Note (CRI)
    • Project Export e-Invoice (CRI) → Configuration: Project Export e-Invoice (CRI)
    • Payment Receipt (CRI) → Configuration: Payment Receipt (CRI)
    • Purchase e-invoice (CRI) → Configuration: Purchase e-invoice (CRI)
• Configuration Integration Point:
  • Configuration Integration Point:
    • InvoiceCustomer — Inventory e-invoice (CRI), Inventory Debit Note (CRI), Inventory Credit Note (CRI), Inventory Export e-Invoice (CRI)
    • InvoiceProject — Project e-invoice (CRI), Project Debit Note (CRI), Project Credit Note (CRI), Project Export e-Invoice (CRI)
    • CustomerPrepayment — Payment Receipt (CRI)
    • EInvoiceVendor — Purchase e-invoice (CRI)

Integrate with Edicom parameters

Get signed XML from Edicom parameters

Get invoice status from Edicom parameters

Process response parameters

• If the status response indicates successful submission to the Costa Rican Tax Authorities (MH), the pipeline completes automatically.

Applicability rules and feature setup scope

You must correctly configure applicability rules to provide context, so that the Electronic Invoicing service can find the exact Electronic Invoicing Globalization feature to run. The system provides these applicability rules out of the box by checking the legal entity’s International Organization for Standardization (ISO) country/region code.

Applicability rules for Costa Rican electronic invoice formats

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

Inventory e-invoice (CRI)

Inventory Credit Note (CRI)

Inventory Debit Note (CRI)

Inventory Export e-Invoice (CRI)

Project e-invoice (CRI)

Project Credit Note (CRI)

Project Debit Note (CRI)

Project Export e-Invoice (CRI)

Payment Receipt (CRI)

Purchase e-invoice (CRI)

Variables

The outbound data flow actions for the Costa Rican feature use the following variables. The system provides these variables.

• BusinessDocumentDataModel – The Business Document Data model variable that Finance or Supply Chain Management sends. The system transforms this variable into the format required for submission.
• SignedXML – The signed XML variable that the system sends back to Finance or Supply Chain Management. This variable contains the base64-encoded response body from the Get Signed XML from Edicom step. The response types use this variable to save the signed XML that the system gets from Edicom as an attachment to the invoice journal. The system also uses this variable to generate printable reports through QR codes.

After you import the Electronic invoicing for Costa Rica feature that includes the default feature setup, follow the steps in the next section to configure 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 Costa Rica.

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. Make sure that you import the country/region-specific ER configurations for the document context and electronic document model mapping that are required for Costa Rica. For more information, see 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 in accordance with step 1.

The Electronic Document Parameters page in Dynamics 365 Finance. Shows on the left-hand navigation pane, you can see the following options:

• Electronic Document

• Features

• Electronic Invoicing

• Integration Channels

For the Electronic Document option on the right-hand side, the section labeled Electronic Reporting is displayed.

Within Electronic Reporting, a grid is presented which lists the electronic document configurations. This grid includes important 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 is essential for determining 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, select New to create a response type that you get from the back end, and enter the following values:

      • In the Response type field, enter SignedXML (the default value). (See the Variables section of this article.)
      • In the Description field, enter any meaningful name. Alternatively, leave the field 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. In this way, you can run a subset of the actions in the processing pipeline in a loop to continuously pull updated statuses and other information for the submitted documents from the tax authority. In the standard view, you should see a table similar to the following:

   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 that you get from Edicom. The system stores this signed XML as an attachment to the corresponding invoice journal. You can use it later to generate printable invoices through QR codes.

Issue electronic invoices

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

To check the results of a submission, 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 Costa Rica, after you submit the invoice, the submission status is set to Pending update actions execution. The response body is probably empty for the signed XML and the call to get the invoice status. An empty response body indicates that the XML isn't available immediately after submission. To address the pending status, use a function named Execute update actions. This function resumes the pipeline from the action that is marked as an update action. It then runs all subsequent actions in the pipeline in a loop. The status should change to Executing again. Then, after a few seconds, it reverts to Pending update actions execution.

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

As a result of the completed outbound flow, the signed XML is attached to the invoice journal as EdicomSourceFile.

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

More resources

• Electronic Invoicing service overview

• Get started with Electronic invoicing service administration

• Setting 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 Additional Countries/Regions | Dynamics 365 Fast Track TechTalk | Jun 23, 2025

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