Integration specification - D365 Business Central /NAV


Preliminary Booking



Pay Ref to ERP

Text on account coding row

Invoice image

PO matching support

2 way matching

Yes, journal









Master Data

Master data is initially transferred as a full load of all configured registers/tables. After the initial load only changes of the used information is collected.

Functions exists to preform full master data synchronization if needed.

Tables from which information is exported

  • Currency
  • Vendor
  • G/L Account
  • Payments (Vendor Ledger Entry)
  • Dimensions (Dimension and Dimension Value). If applicable.
  • Accounting Periods
  • Purchase Orders and Receipts. If applicable.
  • Company Information
  • VAT Product Groups
  • Job and Job Task. If applicable.


On every execution of the integration module (WFconnector) the integration ask MediusGO if any new postings. Each booking is inserted to Business Central and a receipt is confirmed back. In case of failure of the booking an errormessage is receipted.

Posting of a preliminary booking is always done by generating lines, that are directly posted to the General Ledger as a journal booking.

Posting of a final booking is performed to BC/NAV as a posting of a Purchase Invoice / Credit Memo. (Purchase Journal is not supported). At final booking the invoice is transferred and recorded fully.


Purchase Orders

New and changed Purchase Orders and deliveries is transferred on every exexcution to MediusGo. 

Support for 2 way matching exists. Possibility to configure for export orders with Net amount (with discounts deducted) exists.

Even bookings with attached JobNo and JobTaskNo is supported, as well as possibility to set JobLineType if required.

Charge Items can also be supported with 2 different settings “Even” or “Amount”.



Best Practice based on several hundreds of companies using the integration is to use “Final booking Only” . However if preliminary booking is required a method for this exists.


The integration supports deferral with even spread with from and to period. If You enter i.e Jan 12th to April 11th as date range the amount on the deferral row will be spread equally in Jan, Feb, March, and April with one fourh of the amount. 

The text on the deferral rows in Business Central are default text set by BC and cannot be affected from the integration/Workflow.

The VAT Prod Posting Group is used in Postings to Business Central, this means that each cost row should have a corresponding VAT row from MediusGo. This is supported via the Taxes and Fees module in MediusGo, which have to be setup. There is also functionality for the Swedish market to use the “simplified VAT” module to collect all VAT on one VAT line.


Support for cancelation and possibilty to handle credit notes exists. Further bookings with reversed VAT is also supported as well as You can have quantity on cost invoices.

Assets can also be handled via the integration but may require special setup / modifications. 



Architecture and Execution

The integration with Business Central / NAV follows Medius standard Architecture for integration. The described functionality is tested with a non-modified installation of Business Central. Different combinations of configuration may affect the integrations functionality and can require minor modifications or changes. 

The integration requires an installation of an app from App Source in Business Central (for On Prem installation a runtime package or FOB is provided for the customer to install). The app is currently available on the SE, DK, UK and US regions in AppStore. The App/FOB is not modifying any objects in BusinessCentral, but it adds a number of tables (listed below). Any modification in the standard objects in BusinessCentral may affect the functionality of the integration.

After installation of the App/FOB in Business Central/NAV a setup screen needs to be completed and the access must be granted.

The added tables are in version 18 of the App the following. The app is constantly updated to support new versions of both Business Central and MediusGo, as well as new functionality in the integration can apply.

A screenshot of a computer

Description automatically generated


The integration is using the SOAP API and the logon method is following Oauth2 for “MS Cloud” installations and via WebServiceKey for OnPrem installations. For Cloud installation a ”grant consent” operation is performed and for OnPrem the WebServiceKey is requiring a user licence. Any licence need in the ERP have to be clarified with Your ERP supplier and is not included in the integration as such.

Technically there is a integration client (WFConnector) that is installed on Medius dedicated integration server for “MS Cloud” installations. For OnPrem installations the client is often installed on the BusinessCentral/NAV server. The integration is often configured to be executed every 10 or 15 minutes between 07:00 – 22:00 every day of the week. The configuration, error messages, log file handling and more is controlled via the Medius Integration portal and all changes is logged to an audit trail. Only authorized Medius staff have access to perform changes. Changes and Updates of the integration is performed via the integration portal.