Administration Topics

API Integrations

Microsoft Dynamics 365 Business Central Features & Requirements


Overview of Integration Features

The integration includes these features:

  • Sync accounts and dimensions from the accounting system – each weeknight via the nightly automated sync and ad hoc.
  • Sync GL transactions from the accounting system each weeknight. The nightly sync updates the current and previous two full months. Ad hoc sync is available to allow the manual sync any desired range of months.
  • Drilldown in Martus from standard financial summary reports to see transaction detail.
  • Display of attachments associated with transaction detail for Purchase Invoices.
  • Ability to pull existing budgets from the accounting system.
  • Export of budget from Martus in a format optimized for import into the accounting system.
  • Display of vendor name on transaction detail.


Business Central Configuration

Business Central must be configured with the Business Central API v2.0.


Multiple Entities

Typically, any given Dynamics Business Central company file only includes a single entity. Accordingly, a multi-entity Dynamics Business Central customer would need multiple Martus instances.  Martus does not presently provide consolidation of multiple Martus instances. 


Authorization

Martus supports and prefers service-to-service authorization.


Overlays

The following overlays have been implemented and are supported:

  • Wiise
  • Tangicloud FUNDamentals
  • Sylogist Mission

Additional overlays will be considered for support upon request.


Dimension Setup

As with any Martus configuration, the Implementation Consultant works with the customer to identify the dimensions that are important to budgeting and reporting.  (GL accounts are not considered dimensions, within Martus.) Martus can support whichever Business Central dimensions that the customer uses, up to the standard Martus maximum of eight. Dimension values must have names (not just numbers). If they do not have names, they will not be synced into Martus. With overlays such as Tangicloud FUNDamentals and Sylogist Mission, Martus also supports dimensions such as Fund that are defined within the overlay and treats those like any other dimension within Martus. 


GL Account Setup

GL accounts must be categorized in Business Central as Income or Expense, or they would not be synced into Martus. Additionally, balance sheet accounts must be categorized as Assets, Liabilities, and Equity. Accounts categorized as Cost of Goods Sold are classified in Martus as Expense accounts with the subtype of CostOfGoods.


Syncing Martus to Business Central

Martus will sync daily all GL accounts and dimensions, as well as actuals for the current and two previous full months, as is standard for Martus API Integrations.


Year-End Closing Entries

Martus requires that the description on these entries contain the text “[MARTUS IGNORES]” so that they will not be included in the summary activity for the last month of the fiscal year or included in the transaction detail drilldown. 


Global Dimensions

Martus requires that all the Global Dimensions be identified in Martus. For the Sylogist overlay, the Fund must not be included in the Global Dimensions. 


Pulling Budgets from Business Central

Martus supports pulling existing budgets from Business Central. This feature requires that the Global Dimensions be identified within the Martus configuration.


Pushing Budgets into Business Central

The Business Central API does not support this, as of this writing. Therefore, to move a budget into Business Central, export from Martus, reformat as necessary, and import into Business Central.


Statistical Accounts

Not yet supported.


Multicurrency

Not yet supported.