Administration Topics
API Integrations - General Documentation
Martus Features by Integration - Integration Feature Matrix
Martus Features by Integration - Integration Feature Matrix
Martus features for each integration are listed below.
Martus Features | Sage Intacct | QuickBooks Online | QuickBooks Desktop | NetSuite |
| Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes |
| Yes | No | No | No |
| Yes | Yes | Yes | Yes |
| Yes | No | No | No |
| Yes | No | Yes | No |
| Yes | No | No | No |
| Yes | Yes | No | No |
| Yes | One company file per Martus instance | One company file per Martus instance. | Yes (with NetSuite OneWorld) |
| Yes | No | No | Yes |
Supported Dimensions | Class | Class | Class | Location |
Customer | Customer/Project | Customer/Job | Department | |
Department | Location | Items | Class | |
Employee | Department (only in Martus) | Department (only in Martus) | Custom Dimensions | |
Entity / Location | (such as Program | |||
Item | and Grant) | |||
Project | ||||
UDDs | ||||
Vendor | ||||
Warehouse |
Martus Features | Sage 100 | Financial Edge NXT | Business Central | Acumatica |
| Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes |
| No | No | Yes | Yes |
| No | No | Yes | No |
| Yes | Yes | Yes | No |
| No | No | No | No |
| Yes | Yes | Yes | No |
| Yes | Yes* | No | No |
| No | No | No | No |
| No | No | Yes, via MEM | No |
| No | No | No | No |
Supported Dimensions | Each sub-account from Sage 100 is a separate dimension in Martus | Fund | Martus can support whatever Business Central dimensions the customer uses, up to the Martus maximum of 8. | Company |
Department | Branch | |||
Cost Center | Project | |||
Other Account Segments | Additional available on request. | |||
Project | ||||
Grant | ||||
T-Codes |
Martus Features | Xero |
| Yes |
| Yes |
| Yes |
| Yes |
| No |
| No |
| No |
| No |
| No |
| No |
Supported Dimensions | Martus can support whatever Xero tracking categories the customer uses, up to the Martus maximum of 8. |
Integration Documents
*FE NXT stat accounts can be supported but the accounts have to be designated in FE NXT as 'Transfer' accounts.
Provider Non-Standard Reporting Periods
Provider Non-Standard Reporting Periods
Martus will allow the use of non-standard reporting periods for all integrations. We can support 4-4-5 type configurations, but not 13 reporting periods per year.
- The client instance requires a client-level flag to be turned on on the client record.
- Setup > Calendar requires the Fiscal Year Beginning Month and Week Ending Day be defined.
Financial Calendar Tab
Users will manually enter calendar dates based on the structure they would like to follow. Additional calendars can be imported by Martus Support if they are provided.
These are the guidelines for new calendars:
- Start/End dates must honor the day of the week indicated on Setup > Calendar > Last Closed Month > Fiscal Year.
- The start day will auto-populate based on the ending day of the year prior.
- The ending day will auto-populate based on the start day of the year following.
- Deleting a calendar will cause the button to Add a year to appear.
- Users are warned if the Start/End dates do not honor the beginning/ending day. Note: This means Martus cannot support starting every year on July 1st no matter the day or ending on Dec 31 no matter the day.
- Missing dates between months will cause an error.