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).

Potential Future Features

• Pull existing budget from Sage 100 
• Display vendor/customer name on Transaction Detail 
• Integration with the versions of Sage 100 that use an SQL database 

Unavailable features 

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

Description of the Integration 

The Martus Connector for Sage 100 is an application that is installed on the Sage 100 Server. It communicates with a Sage 

100 Company via a Sage ProvideX ODBC Connection. 

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

The 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 updates the Martus database with those results. (Note that automation of these periodic calls is not included in the initial beta version of the Connector.) Implementation and Upgrades for the Martus Connector for Sage 100 Martus provides a Martus Connector for Sage 100 that makes an ODBC connection to the Sage 100 Providex database. At the time of implementation, it is the customer/partner responsibility to install and configure this 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.

Implementation and Upgrades for the Martus Connector for Sage 100 

Martus provides the Martus EZ Connector for Sage 100 that makes an ODBC connection to the Sage 100 Providex database. At the time of implementation, it is the customer/partner responsibility to install and configure this 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.