Sage 100 Integration Requirements & Features

Integration Requirements

Multiple Entities 

A Sage 100 company includes a single entity. Accordingly, a multi-entity Sage 100 customer would need multiple Martus instances. 

Dimension Setup and the Sage 100 Segmented Account 

Martus dimensionalizes the segmented Sage 100 account, naturalizing the GL account segment and treating the remaining segments as dimensions. At the time of implementation, Martus works with the customer/partner to configure the dimension(s) that are important to budgeting and reporting. 

Integration Features

Current Features 

• Sync accounts and dimensions from Sage 100 – each weeknight via AutoUpdate and ad hoc. 
• Sync GL transactions from Sage 100 each weeknight; per standard Martus functionality, the nightly sync (AutoUpdate) updates the current and previous two full months. Ad hoc sync is available to allow the customer to sync any desired range of months. 
• Drilldown in Martus from standard financial summary reports to see transaction details. 
• Export of budget from Martus in a format optimized for import into Sage 100. 
• Support for statistical accounts (based on the non-financial accounts in Sage 100).
• Integration with both the ProvideX and SQL Server database versions of Sage 100.
• Pull existing budgets from Sage 100 (use of this feature is limited to Martus staffers only; this is usually done at the time of implementation and does not need to be done again).

Potential Future Features

• Display vendor/customer name on Transaction Detail

Unavailable Features - Not Supported by the Capabilities of Sage 100

• Display of attachments associated with transaction detail 
• Push (upload) of budget from Martus to Sage 100 
• Multi-currency support 

Description of the Integration 

Update requests are generated in the Martus application by such activities as the nightly Auto Update or an ad hoc sync request. These requests are stored in the Martus cloud.

The Martus EZ Connector for Sage 100 is an additional application provided by Martus that is installed on the Sage 100 Server. 

• For the Standard and Advanced versions of Sage 100, the EZ Connector makes an ODBC connection to the Sage 100 ProvideX database. 
• For the Premium version of Sage 100, the EZ Connector makes a direction connection to the Sage 100 SQL Server database. 

The EZ Connector periodically calls the Martus cloud to see if there are any pending requests, responds to those requests by querying Sage 100, and returns the results to the Martus cloud. The Martus application then updates the Martus database with those results.

Implementation and Upgrades for the Martus EZ Connector for Sage 100 

At the time of implementation, it is the customer/partner responsibility to install and configure the EZ Connector on the server where Sage 100 is installed. In case of updates to this connector, the customer/partner is responsible for installing the updated version provided by Martus and (when necessary) updating any configuration settings within the Martus EZ Connector.