Configure edoc D365 BC invoice cockpit

In this topic you get to know how to set up edoc invoice cockpit for your organization.

In the first step, you configure the fields and the behavior of edoc invoice cockpit. You can decide whether your users work on processes manually or whether you use the job queue entries for automated processing.

You can open the setup dialog by opening the search in Dynamics 365 Business Central and searching for "edoc invoice cockpit setup". Click on edoc invoice cockpit Setup to get started with the configuration.

Configure the fields

In the edoc invoice cockpit Setup dialog, you define the basic functions for the edoc invoice cockpit in the General section.

• invoice cockpit active: Use this slider to specify whether edoc invoice cockpit can be used in Microsoft Dynamics 365 Business Central.

• Use web service for data import: Use the slider to specify whether data is to be imported using the REST API (OData, web service) or using SQL tables (LinkedObject). If you activate the function, data is imported via the REST API. For more information about the web service see: Configure web services for edoc invoice cockpit (cloud)

• Auto posting invoices: Use this slider to specify whether your users can post purchase invoices or G/L journal lines in Microsoft Dynamics 365 Business Central after they have been created. The following options are possible by activating:

  • Create and post processes manually: Your users can create and post purchase invoices with one click at edoc invoice cockpit > Processing > Create and post purchase invoices.

  • Create and post process automatically: The corresponding job is automatically created and posted by a job queue entry. For more information see: Configure job queue entries for edoc invoice cockpit

• Documenttype cost acc.: Select the document type for invoices without order reference. You have the following options:

  • Posting journal: The invoice is created in the General journal You must then use a journal template and enter the batch name.

  • Purchase invoice: The invoice is created under Purchase invoice.

• Treat commercial invoice as cost invoice: Use the slider to specify whether special logic should be applied to invoices for goods so that invoices for goods are treated as invoices without order reference. You always need this option if you manage financial accounting in Dynamics 365 Business Central with edoc D365 BC invoice cockpit in one instance, while all other relevant edoc D365 BC invoice cockpit modules such as Purchase, Inventory, etc. have been implemented in another ERP system.

• Posting date: Define the logic for determining the posting date by selecting the appropriate combination:

  • Workflow completion date: The edoc invoice workflow completion date is used as the posting date in Dynamics 365 Business Central.

  • Document date: The edoc invoice document date is used as the posting date in Dynamics 365 Business Central. If the field is empty, the edoc invoice workflow completion date is used as the posting date in Dynamics 365 Business Central.

  • Performance date: The edoc invoice service date is used as the posting date in Dynamics 365 Business Central. If the field is empty, the edoc invoice workflow completion date is used as the posting date in Dynamics 365 Business Central.

• Activate log: Use this slider to activate whether processes are logged in edoc invoice cockpit.

• Log type: Select the level of detail for the log:

  • Errors only: Only erroneous processes are logged.

  • Information: Both errors and information messages are logged.

  • Debug: All messages relating to processes are logged, e.g. errors and all informational messages.

• Log lifespan in days: Define the logging duration in days. The log entries are deleted after the specified duration. If you enter the value 0, the log entries are never deleted. You cannot delete the log entries manually. The log entries are only deleted by job queue entries.

• Journal template name: Select an entry from the master data to define the journal template name for the general journal lines. You must specify the entry Posting journal under Documenttype cost acc. in order to use the template.

• Journal batch name: Select an entry from the master data for the general journal lines. You must select the entry Posting journal under Documenttype cost acc. and enter a journal template name.

• Fixed asset G/L journal template name: Select an entry from the master data to define the journal template name for the fixed asset G/L journal lines. You must specify the entry Posting journal under Documenttype cost acc. in order to use the template.

• Fixed asset G/L journal batch name: Select an entry from the master data for the fixed asset G/L journal lines. You must select the entry Posting journal under Documenttype cost acc. and enter an fixed asset G/L journal template name.

• Overwrite description with posting text: Use this slider to specify whether the description in newly created lines (purchase invoice and G/L journal) may be overwritten by the posting text from edoc invoice.

• Show tiles in cockpit: Use this slider to specify whether the edoc invoice cockpit view in the FactBox should display edoc Purchase Invoice Overview information in tiles instead of per line.

• Company: Enter the abbreviation of the company that you have defined in edoc invoice. With the abbreviation, you ensure that the data of the purchasing records are separated per company.

• Open document after creation: Use this slider to specify whether a Microsoft Dynamics 365 Business Central document (purchase invoice or G/L journal) that was created with Create purchase invoices or Create and post purchase invoices should be opened directly.

• Distribute charge (item) manually: Specify whether your users must manually distribute the value in Charge (Item) to different item lines.

• Purchase order no. for commercial invoice without purchase order reference: Define a dummy purchase invoice no. for goods invoice items without order reference. The field is required if goods invoice items must be entered in edoc invoice without order reference, but the purchase order number has been set up as a mandatory field.

• edoc invoice app company currency code: Enter the company currency code from edoc invoice if the company currency code is available in edoc invoice. In Microsoft Dynamics 365 Business Central, however, the company currency code is displayed as an empty currency code. When importing the transactional data from edoc invoice, the system checks whether the value in the Currency field of the currency code matches the value in the edoc invoice app company currency code field. If the value matches, the value is replaced with an empty value during data import.

• Export posted purchase documents starting from: Enter a date from which the posted purchase receipt lines and posted purchase return shipment lines are exported.

• Export posted purchase documents with uninvoiced quantity: Use this slider to specify whether only the posted purchase receipt lines and posted purchase shipment lines that have not yet been fully invoiced are exported.

• Expert mode: Use this slider to specify whether a person can edit and save entries in the list, e.g. in the edoc invoice cockpit view. By default, users cannot edit the list and entries. However, if an entry needs to be corrected manually, you can temporarily use the expert mode.

In the Dimensions section of the edoc invoice cockpit Setup dialog, you can define up to eight dimensions. The values of the dimensions can be filled with dimension values from edoc invoice when creating purchase invoices or G/L journal lines or existing dimension values can be overwritten with the dimension values from edoc invoice.

You can enter the dimension code for the dimension values 1-8 from edoc invoice in the fields for dimension codes 1-8.

Once you have configured the fields and the software behavior, connect to the ECM system to display the corresponding purchase invoice.

Configure the field mapping

In some cases, edoc invoice is customized and configured so that default fields in edoc invoice can contain other information: For example, the approval policy code is stored in the field for the cost center so that the release steps and workflow completion can be performed smoothly.

Instead, another standard field is created in edoc invoice for the cost center information. Since edoc invoice cockpit expects certain information in its own default field, which may be checked, the edoc invoice cockpit default field must be assigned to the new field in edoc invoice in the edoc Invoice Cockpit Field Mapping list.

When importing data, the information is transferred according to the list. You can open the edoc Invoice Cockpit Field Mapping list in the edoc invoice cockpit Setup dialog by clicking on Field Mapping.

Map the corresponding fields in the edoc invoice cockpit Field Mapping list:

• Table ID: Select the edoc invoice cockpit table whose fields need to be mapped.

• Table name: The name is automatically displayed based on the Table ID field.

• Target field ID: Select the edoc invoice cockpit field that should receive data.

• Target field name: The name is automatically displayed based on the Target field ID field.

• Target field type: The data type is automatically displayed based on the Target field ID field.

• Source field ID: Select the edoc invoice cockpit field that contains the correct data for the Target field ID.

• Source Field Name: The name is automatically displayed based on the Source field ID field.

• Source field type: The data type is automatically displayed based on the Source field ID field.

• Active: Use the slider to activate or deactivate the current mapping. When activating, various checks are performed, e.g. for duplicates, whether all relevant fields are filled, etc.

Publish the edoc web services (cloud)

In the edoc invoice cockpit Setup dialog, you will find the Publish edoc web services function in the menu.

This function is used to automatically create and publish edoc web services, e.g. for data import and data export.

You can also publish the web services manually. For more information see here.