Electronic reporting (ER) destinations

You can configure a destination for each Electronic reporting (ER) format configuration and its output component (a folder or a file). Users who have appropriate access rights can also modify destination settings at runtime. This topic explains ER destination management, the types of destinations that are supported, and security considerations.

ER format configurations usually contain at least one output component: a file. Typically, configurations contain multiple file output components of different types (for example, XML, TXT, XLSX, DOCX, or PDF) that are grouped into either a single folder or multiple folders. ER destination management lets you preconfigure what occurs when each component is run. By default, when a configuration is run, a dialog box appears that lets you save or open the file. The same behavior also occurs when you import an ER configuration and don't configure any specific destinations for it. After a destination is created for a main output component, that destination overrides the default behavior, and the folder or file is sent according to the destination's settings.

Availability and general prerequisites

The functionality for ER destinations isn't available in Microsoft Dynamics AX 7.0 (February 2016). Therefore, you must install Microsoft Dynamics 365 for Operations version 1611 (November 2016) or later to use the following destination types:

Alternatively, you can install one of the following prerequisites. However, be aware that these alternatives provide a more limited ER destination experience.

There is also a Print destination type. To use it, you must install Microsoft Dynamics 365 Finance version 10.0.9 (April 2020).

Overview

You can set up destinations only for ER configurations that have been imported into the current Finance instance, and for the formats that are available on the Electronic reporting configurations page. The functionality for ER destination management is available at Organization administration > Electronic reporting > Electronic reporting destination.

Default behavior

The default behavior for an ER format configuration depends on the execution type that you specify when an ER format starts.

In the Intrastat Report dialog box, on the Run in the background FastTab, if you set the Batch processing option to No, an ER format is run immediately in interactive mode. When this execution is successfully completed, a generated outbound document is made available for download.

If you set the Batch processing option to Yes, an ER format is run in batch mode. The appropriate batch job is created, based on the parameters that you specify on the Run in the background tab of the ER parameters dialog box.

Note

The job description is initiated to inform you about the run of an ER format mapping. It also contains the name of the executed ER component.

Running an ER format

You can find information about this job in several places:

  • Go to Common > Inquiries > Batch jobs > My batch jobs to check the status of the scheduled job.

  • Go to Organization administration > Electronic reporting > Electronic reporting jobs to check the status of the scheduled job and the execution results of the completed job. When job execution is successfully completed, select Show files on the Electronic reporting jobs page to get a generated outbound document.

    Note

    This document is stored as an attachment of the current job record and is controlled by the Document management framework. The document type that is used to store ER artifacts of this type is configured in the ER parameters.

  • On the Electronic reporting jobs page, select Show files to view the list of any errors and warnings that were generated during job execution.

    Reviewing the ER jobs list

User-configured behavior

On the Electronic reporting destination page, you can override the default behavior for a configuration. Imported configurations aren't shown on this page until you select New and then, in the Reference field, select a configuration to create destination settings for.

Selecting a configuration in the Reference field

After you create a reference, you can create a file destination for each Folder or File output component of the referenced ER format.

Creating a file destination

Next, in the Destination settings dialog box, you can enable and disable individual destinations for the file destination. The Settings button is used to control all the destinations for a selected file destination. In the Destination settings dialog box, you can control each destination separately by setting the Enabled option for it.

In versions of Finance before version 10.0.9, you can create one file destination for each output component of the same format, such as a folder or a file that is selected in the File Name field. However, in version 10.0.9 and later, you can create multiple file destinations for each output component of the same format.

For example, you can use this capability to configure file destinations for a file component that is used to generate an outbound document in Excel format. One destination (Archive) can be configured to store the original Excel file in the ER jobs archive, and another destination (Email) can be configured to simultaneously convert the Excel file to PDF format and send the PDF file by email.

Configuring multiple destinations for a single format element

Destination types

The following destinations are currently supported for ER formats. You can disable or enable all types at the same time. In this way, you can either do nothing or send the component to all configured destinations.

Applicability

You can set up destinations only for ER configurations that have been imported, and for the formats that are available on the Electronic reporting configurations page.

Note

Configured destinations are company-specific. If you plan to use an ER format in different companies of the current Finance instance, you must configure destinations for that ER format for each of those companies.

When you configure file destinations for a selected format, you configure them for the whole format.

Configuration link

At the same time, you might have multiple versions of the format that have been imported into the current Finance instance. You can view them if you select the Configuration link that is offered when you select the Reference field.

Configuration versions

By default, configured destinations are applied only when you run an ER format version that has a status of either Completed or Shared. However, you must sometimes use configured destinations when the draft version of an ER format is run. For example, you modify a draft version of your format, and you want to use configured destinations to test how generated output will be delivered. Follow these steps to apply destinations for an ER format when the draft version is run.

  1. Go to Organization administration > Electronic reporting > Configurations.
  2. On the Configurations page, on the Action Pane, on the Configurations tab, in the Advanced settings group, select User parameters.
  3. Set the Use destinations for draft status option to Yes.

Use destinations for draft status option

To use the draft version of an ER format, you must mark the ER format accordingly.

  1. Go to Organization administration > Electronic reporting > Configurations.
  2. On the Configurations page, on the Action Pane, on the Configurations tab, in the Advanced settings group, select User parameters.
  3. Set the Run setting option to Yes.

Run setting option

After you complete this setup, the Run draft option becomes available for ER formats that you modify. Set this option to Yes to start to use the draft version of the format when the format is run.

Run draft option

Destination failure handling

Usually, an ER format is run within the scope of a specific business process. However, the delivery of an outbound document that is generated during execution of an ER format must sometimes be considered part of that business process. In this case, if delivery of a generated outbound document to a configured destination is unsuccessful, execution of the business process must be canceled. To configure the appropriate ER destination, select the Stop processing on failure option.

For example, you configure vendor payment processing so that the ISO20022 Credit Transfer ER format is run to generate the payment file and supplementary documents (for example, the covering letter and control report). If a payment should be considered successfully processed only if the covering letter is successfully delivered by email, you must select the Stop processing on failure check box for the CoveringLetter component in the appropriate file destination, as shown in the following illustration. In this case, the status of the payment that is selected for processing will be changed from None to Sent only when the covering letter that is generated is successfully accepted for delivery by an email provider that is configured in the Finance instance.

Configuring process handling for file destination failure

If you clear the Stop processing on failure check box for the CoveringLetter component in the destination, a payment will be considered successfully processed even if the covering letter isn't successfully delivered by email. The status of the payment will be changed from None to Sent even if the covering letter can't be sent because, for example, the email address of the recipient or sender is missing or incorrect.

Output conversion to PDF

You can use the PDF conversion option to convert output in Microsoft Office format (Excel/Word) to PDF format.

Make PDF conversion available

To make the PDF conversion option available in the current Finance instance, open the Feature management workspace, and turn on the Convert Electronic Reporting outbound documents from Microsoft Office formats to PDF feature.

Turning on the PDF conversion of outbound documents feature in Feature management

Applicability

The PDF conversion option can be turned on only for file components that are used to generate output in Microsoft Office Excel or Word format (Excel file). When this option is turned on, output that is generated in Office format is automatically converted to PDF format.

Limitations

Note

This feature is a preview feature and is subject to the terms of use that are described in Supplemental Terms of Use for Microsoft Dynamics 365 Previews.

Note

The PDF conversion option is only available for cloud deployments.

The produced PDF is limited to a maximum number of 300 pages.

In Microsoft Dynamics 365 Finance version 10.0.9 (April 2020) only landscape page orientation is supported in the PDF document that is produced from an Excel output. With the release of Dynamics 365 Finance version 10.0.10 (May 2020), you can specify page orientation in the PDF document that is produced from an Excel output while you configure an ER destination.

Only the common system fonts of the Window operating system are used for the conversion of an output that contains no embedded fonts.

Use the PDF conversion option

To turn on PDF conversion for a file destination, select the Convert to PDF check box.

Turning on PDF conversion for a file destination

Select a page orientation for PDF conversion

If you generate an ER configuration in Excel format and want to convert it to PDF format, you can specify the page orientation of the PDF. When you select the Convert to PDF check box to turn on PDF conversion for a file destination that produces an output file in Excel format, the Page orientation field becomes available on the PDF conversion settings FastTab. In the Page orientation field, select the preferred orientation.

Selecting a page orientation for PDF conversion

Note

To have the option to select the PDF page orientation, you must install Microsoft Dynamics 365 Finance version 10.0.10 (May 2020) or later.

The selected page orientation is applied to all ER configurations that are generated in Excel format and then converted to PDF format.

If a converted PDF is created from an ER configuration in Word format, the page orientation of the PDF is taken from the Word document.

Security considerations

Two types of privileges and duties are used for ER destinations. One type controls a user's overall ability to maintain the destinations that are configured for a legal entity (that is, it controls access to the Electronic reporting destinations page). The other type controls an application user's ability to override, at runtime, the destination settings that an ER developer or ER functional consultant has configured.

Role (AOT name) Role name Duty (AOT name) Duty name
ERDeveloper Electronic reporting developer ERFormatDestinationConfigure Configure electronic reporting format destination
ERFunctionalConsultant Electronic reporting functional consultant ERFormatDestinationConfigure Configure electronic reporting format destination
PaymAccountsPayablePaymentsClerk Accounts payable payments clerk ERFormatDestinationRuntimeConfigure Configure electronic reporting format destination during runtime
PaymAccountsReceivablePaymentsClerk Accounts receivable payments clerk ERFormatDestinationRuntimeConfigure Configure electronic reporting format destination during runtime

Note

Two privileges are used in the preceding duties. These privileges have the same names as the corresponding duties: ERFormatDestinationConfigure and ERFormatDestinationRuntimeConfigure.

Frequently asked questions

I have imported electronic configurations, and I see them on the Electronic reporting configurations page. But why don't I see them on the Electronic reporting destinations page?

Make sure that you select New and then select a configuration in the Reference field. The Electronic reporting destinations page shows only configurations that destinations have been configured for.

Is there any way to define which Microsoft Azure Storage account and Azure Blob storage are used?

No. The default Microsoft Azure Blob storage that is defined and used for the document management system is used.

What is the purpose of the File destination in the destination settings? What does that setting do?

The File destination is used to control a dialog box. If you enable this destination, or if no destination is defined for a configuration, an open or save dialog box appears after an output file is created.

Can you give an example of the formula that refers to a vendor account that I can send email to?

The formula is specific to the ER configuration. For example, if you use the ISO 20022 Credit Transfer configuration, you can use '$PaymentsForCoveringLetter'.Creditor.Identification.SourceID or model.Payments.Creditor.Identification.SourceID to get an associated vendor account.

One of my format configurations contains multiple files that are grouped into one folder (for example, Folder1 contains File1, File2, and File3). How do I set up destinations so that Folder1.zip isn't created at all, File1 is sent by email, File2 is sent to SharePoint, and I can open File3 immediately after the configuration is run?

Your format must first be available in the ER configurations. If this prerequisite is met, open the Electronic reporting destination page, and create a new reference to the configuration. You must then have four file destinations, one for each output component. Create the first file destination, give it a name such as Folder, and select a file name that represents a folder in your configuration. Then select Settings, and make sure that all the destinations are disabled. For this file destination, the folder won't be created. By default, because of hierarchical dependencies between files and parent folders, the files will behave in the same way. In other words, they won't be sent anywhere. To override that default behavior, you must create three more file destinations, one for each file. In the destination settings for each, you must enable the destination that the file should be sent to.

Additional resources

Electronic reporting (ER) overview