Sage 300 - Integration Features and Requirements

Integration Requirements

Listed below are the requirements for integration with Martus via the Sage 300 API. 

• WebScreens must be enabled within Sage 300 and the URL provided to Martus. 
• The Sage 300 company ID must be provided to Martus.   
• The Martus IP addresses listed in the Guide to Support Tools must be whitelisted.

Integration Features

Current Features

• Sync accounts and dimensions from Sage 300 each weeknight via AutoUpdate and ad hoc.

• Sync GL transactions from Sage 300 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 300. 
• Martus' Cash Flow Forecasting is available for Sage 300 integrations at the Premium subscription level.
• Martus honors 12 reporting periods for Sage 300. 
• Martus will recognize any Adjustment entries posted in period 14 on the Transaction Report honoring the date they were posted and closing entries, transactions posted in period 15, will not be included in Martus.
  
  

Dimension Support

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 whatever segments Sage 300 uses up to the Martus maximum of 8 dimensions.  Account mapping can vary with segment order. A line dimension in Martus must be reserved for Sage 300 account mapping.

Martus supports adding custom, Martus-only dimensions. Account mappings for the custom dimension are also supported.

Budget Management between Sage 300 and Martus

• Sage 300 does not support pulling budgets from Sage 300 into Martus. At the time of implementation, any budgets that already exist in Sage 300 and are wanted in Martus  must be exported from Sage 300 and imported into Martus individually. 
• Sage 300 does not support pushing budgets from Martus to Sage 300. Any budgets that are needed in Sage 300 must be exported from Martus and imported into Sage 300. 

Features Not Yet Supported

• Syncing of balance sheet accounts, along with the standard Balance Sheet and Cash Flow Forecast reports
• Multi-currency
• Multi-entity & Consolidation

Unavailable Features - Not Supported by the Capabilities of Sage 300

• Display of attachments associated with transaction detail
• Display of Vendor Name column in transaction detail
• Statistical accounts
• Pull a budget from Sage 300 into Martus
• Push a budget from Martus to Sage 300

Other Notes

• Optional fields in Sage 300 cannot be supported as dimensions within Martus 
• Martus also provides a file-based integration with Sage 300