Sage 300 - Integration Features and Requirements (IN BETA!)

Modified on Wed, Apr 8 at 11:31 AM

More information coming soon!


The Sage 300 integration with Martus requires that WebScreens is enabled. Accounts must have a dimension that will be used for reverse mapping. Account mapping can vary with segment order.


Integration Features

Current Features 

  • Sync accounts and dimensions from Sage 300– each weeknight, via AutoUpdate and ad hoc, using the Martus EZ Connector
  • 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. 
  • Integration with both the ProvideX and SQL Server database versions of Sage 300.

Features Not Yet Supported

  • Pull a budget from Sage 300
  • View transaction attachments in Sage 300
  • Push a budget from Martus to Sage 300
  • Statistical accounts
  • Standard Balance Sheet report


Dimension Support

Martus can support whatever segments Sage 300 uses up to the Martus maximum of 8.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article