Sage Intacct - Integration Features and Requirements

Each instance of Martus is connected to a single Sage Intacct company, with a unique set of dimensions and Chart of Accounts. If your Sage Intacct configuration is distributed, each Sage Intact company is independent, so you’d have a separate Martus instance for each Sage Intacct company.

Supported Dimensions

Sage Intacct dimensions supported by Martus are:

• Entity / Location
• Department
• Class
• Item
• Project
• Employee
• Customer
• Vendor
• Warehouse
• UDDs. We do recommend that UDDs are created with an additional custom field so that you can use the “name” field for short ID codes, and a custom field for a fully descriptive name, even though Sage Intacct allows UDDs to only have the name field.
  
  

Private Dimensions

Martus supports private (entity-level) dimension values for projects and warehouses for both reporting and budgeting.

Dimension Restrictions

Martus can define dimension restrictions so that line item dimensions are restricted by sheet dimension values on the basis of dimension relationships within Sage Intacct. Note that this feature is dependent on the specifics of the Sage Intacct and Martus configurations. It is not available for all dimensions and in all cases.

General Requirements

• Budgets and GL accounts must be at the top level.

• Budgetable monthly reporting periods must exist for all years for which Martus will be reporting and budgeting.

Support for Non-Standard Accounting Periods

Martus supports non-standard accounting periods with a fixed number of weeks per month (sometimes called “5-4-4”). Martus also supports definition of a week-beginning day to match the customer’s organizational requirement. This is set at time of implementation and can only be modified with a reimplementation. One basic calendar structure is allowed per Martus instance.

For non-standard reporting periods with a fixed number of weeks in each quarter (“5-4-4”), here are the conditions that we support:

• Fiscal year can start in any month
• Week beginning day is client-specific
• Calendar can start on or before the beginning of the fiscal year (FY starting in any month)
• or Calendar can start after the beginning of the fiscal year (limited to fiscal years that start in a month other than January)
• or Calendar can have fixed beginning and ending dates (limited to January 1 and December 31), which also results in additional short weeks
  
  

Please let your implementation consultant know if you have any questions about whether your organization fits within this structure.

Requirements for Encumbrances

Martus’ reporting is based on Open and Pending POs and PRs. To be cleared out of the Martus reports of total encumbered, the POs must be converted to payables.

Alternate or Additional Book IDs 

Each instance of Martus is configured to use either the Accrual or the Cash book in Sage Intacct. Martus can also be configured to layer on additional books; the internal book ID is required for this. Refer to the Knowledge Base article Identifying the Internal Book ID: Sage Intacct Integrations for instructions about finding the internal book ID.

Display of Attachments

Martus supports the display of attachments located within Sage Intacct for AP Bills (for an instance configured to use the Accrual book), AP Payments (for an instance configured to use the Cash book), GL journal transactions, and Credit Card transactions.

• Support for Custom Attachment Location for AP Bills. Martus can also be configured to use a custom location for AP Bill attachments for integrations with Concur, Bill.com, AvidXchange, and Beanworks. Note that Martus supports only one attachment location for AP Bills (either the native Sage Intacct location or the custom location).  
• Support for Custom Attachment Location for Credit Card Transactions. Martus can also be configured to use a custom location for CC Transaction attachments for integrations with Divvy, Ramp, and other third party providers. Note that Martus supports only one attachment location for CC Transactions (either the native Sage Intacct location or the custom location).

Support for the Multi-Entity Console Setting “Restrict Users to Top Level”

This setting within Martus is defined at implementation and affects the Martus process that updates budgets within Sage Intacct. Let your implementation consultant know if you are restricting users to the top level.