Integration Requirements & Permission Settings - Sage Intacct

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 are:

• Entity / Location
• Department
• Class
• Item
• Project
• Employee
• Customer
• Vendor
• 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 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 starts in any month
• Week beginning day is client-specific
• Calendar has fixed beginning and ending dates (limited to January 1 and December 31)
• Calendar starts before the beginning of the fiscal year (FY starting in any month)
• Calendar starts after the beginning of the fiscal year (limited to fiscal years that start in a month other than January)

Please let your implementation contact 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 theCash 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. 

With the Advanced and Advanced Plus subscriptions, 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, Concur, AvidXchange, Beanworks, or Bill.com).
• 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. Note that Martus supports only one attachment location for CC Transactions (either the native Sage Intacct location or Divvy).

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 implementer know if you are restricting users to the top level.

Martus User

• The Martus user must be a Web Services User with the user type “Business” and the permissions noted below.
• Martus Solutions must be defined as a white-listed sender.
• Detailed instructions about how to set up this user are provided in the document Connecting to Sage Intacct.

Sage Intacct Permissions Needed

• Your Sage Intacct environment may not be configured for all the modules below.
• Any dimension name that is customized in your Sage Intacct will appear in your permissions list with the customized name. For example, if you call the class dimension “Restriction”, you will see “Restriction” not “Class” in the list of permissions.
• Any Permission Name that is listed in more than one module should be enabled in both modules.
• if there are any dimensions that you do not use at all (for example, Project), you do not need to grant permission for that dimension to the Martus web service user.
  
  

Module Permission Name Access

• Company Module: List and view to all utilized dimensions
  • Departments List|View
    
  • Entities List|View
  • Locations List|View
  • Class List|View
  • Employees List|View
  • Reporting Periods List|View
  • Attachment Folders List|View
  • Attachments List|View
• General Ledger Module:
  • Journal Entries List|View
  • Statistical Journal Entries List|View
  • Adjusting Journal Entries List|View
  • Statistical Adjusting Journal Entries List|View
  • User-Defined Journal Entries List|View
  • GAAP Adjusting Entries List|View
  • Tax Adjusting Entries List|View
  • User-Defined Books List|View
  • Accounts List|View
  • Statistical Accounts List|View
  • Budgets List|View|Add|Edit|Delete
    
  • Journals List|View
  • Statistical Journals List|View
  • Adj Journals List|View
  • Statistical Adj Journals List|View
  • User-Defined Journals List|View
  • GAAP Adjustment Journals List|View
  • Recurring Journal Entries List|View
  • Recurring Statistical Journal Entries List|View
  • Reporting Periods List|View
  • Trial Balance Run
    
    • Note: The Martus web services user does not need access to open/close books, approve journal entries, view account groups, or anything to do with templates, or revenuerecognition.
      
• Accounts Payable Module:
  • Vendors List|View
  • Bills List|View
  • Adjustments List|View
  • Recurring Bills List|View
  • Payment requests List|View (required if Martus is linked to the Cash book)
  • Posted payments List|View (required if Martus is linked to the Cash book)
• Purchasing Module:
  • Vendors List View
  • Vendors List|View
• Accounts Receivable 
  • Customers List|View
  • Projects List|View
• Cash Management 
  • Credit Card Transactions List|View
  • Credit Card Charges and Other Fees List|View
• Projects 
  • Customers List|View
  • Projects List|View
  • Items List|View
  • Employees List|View
• Order Entry 
  • Customers List|View
  • Items List|View
• Additional Dimension 
  • All UDDs List|View

Once you’ve assigned permissions to that user, you can export the list of permissions from your environment and compare it to the list above.