The Sage Intacct integration syncs approved bills and payments including any bill attachments and in-line tax information). It also includes a Master Data Sync, where you can sync Vendors and Account Codes from Sage Intacct to Procurify.
Sage Intacct for syncing Bills & Payments
Setting up Sage Intacct with Procurify
First, you'll need to retrieve your Sage Intacct Company ID and configure your account for the integration:
In Sage Intacct:
1. Find your Sage Company ID and (optionally) your Location ID, Location ID is only needed if you're not connecting to the Top Level of Sage Intacct
Company ID: Company → Setup → Company
Optionally: Location ID (also called the Entity ID): Company → Setup → Entities
These will be used in the Setup process in Procurify later.
2. Enable Web Services if not enabled:
Company → Admin → Subscriptions, scroll down and toggle Web Services on.
3. Authorize Procurify as a sender
Company → Setup → Company → Security. Click Edit, scroll to Web Services Authorizations, and add a row:
Sender ID: Procurify
Description: Connection to Procurify
Status: Active
Then Save.
4. (Optional) Create a role, if you don't have an Admin role
Company → Admin → Roles. Create a role named "Procurify Role" with the description "Role for Procurify connection". Make sure all Subscriptions are selected, and that within each Subscription all Permissions are selected.
5. Create a Web Service User.
Company → Admin → Web Services users. Create a user with:
User type: Business
Admin privileges: Full
Role: an existing Admin role, or the Procurify Role created from Step 4.
Intacct emails the User ID and password to the address on the user. You will enter those in Procurify during the setup Process.
Choosing your connection scope
Top Level or a Single Entity
The Location ID field at link time decides the scope of the connection. It is optional, and it cannot be changed later without disconnecting and re-linking.
Leave it empty to connect at Top Level. Use this for multi-entity organizations. You will be able to choose to post Bills to the Top Level, or to different Entities based on the Location mapping set later.
Enter an entity's Location ID only when all data should be scoped to that specific Entity including any vendors and account codes data as well as bill syncs.
In Procurify:
1. Navigate to Settings → Integrations.
2. Select Set up under Sage Intacct and follow the setup steps.
3. Enter your Company ID, and your Location ID (For the Entity) only if you are connecting to a single entity.
4. Enter the Web Services user ID and password that Intacct emailed you.
Setting up Master Data sync (Vendor List and Account Code):
Navigate to Settings → Integrations.
Click View below Sage Intacct.
On the Vendor and Account Code tabs, toggle Start Scheduled Sync to ON
All new vendors will be created/synced as Preferred Vendors
All account codes created/synced via this method will require manual linking to departments. For how to link account codes to departments, see:
You have successfully connected Sage Intacct.
Bill Sync
How the entity is determined
In Intacct, entities are a type of location, and every location belongs to exactly one entity.
On a Top Level connection, by default the Location on the bill's first line determines which entity the bill is created in. A Location field mapping is therefore required.
Bills can optionally be synced to the Top level using this toggle found under Sage's integration settings for Bills.
On a connection scoped to one entity, no location is needed. Intacct stamps the entity's internal root location automatically. A Location mapping is still optional if you want more granular locations.
Advanced Custom Field Mapping
Complex mapping scenarios to support mapping to User Defined Dimensions or Intacct Custom Fields
In Intacct, User defined dimensions can be discovered in top level entity, under Platform Services → Objects
In Intacct, Custom fields can be discovered in Platform Services → Custom fields
Procurify advanced custom field mapping
Sage object definition (Platform Services → Objects)
The values between Procurify and Sage Intacct need to match exactly, if you require the ID to be in Procurify as well, Procurify custom field choices can be setup as "ID--Value" specifically for default dimensions in Sage but not for Sage UDDs or custom fields.
💡Required dimensions for GL account
If a General Ledger account is configured to require a dimension, and that dimension is a user defined dimension, there are a few caveats to making sure it’s properly configured. If a dimension is configured to be required, it’s generally recommended to also require a mapped Procurify custom field to be required, to avoid errors when syncing.
Required dimensions for an account can be checked under that account settings, in General Ledger → General Ledger Accounts menu. Note that if a dimension is marked as required, its name might be different from the actual object name. This is because we believe that once required, and used, object names become immutable, and do not react to a name change in Platform Services → Objects settings. A new Object must be created instead.
Make sure that these two object settings are enabled for the target Object
How Payment Sync Works: Procurify to Sage Intacct
To ensure your payment records sync successfully from Procurify to Sage Intacct, the system relies on a direct match between General Ledger (GL) account codes.
If these codes do not match exactly between both platforms, the integration will be unable to identify the correct destination for the payment data, leading to sync errors.
Configuration Requirements
The sync logic applies to both standard Financial Accounts and External Payment methods. Follow the mapping guidelines below to ensure a seamless connection.
1. Standard Financial Accounts
For payments tied to a standard Financial Account, Procurify looks for a match based on the following fields:
In Procurify: The GL Account Code defined on the specific Financial Account.
In Sage Intacct: The GL Account listed within the Checking Account details (found under the Accounting Information section).
2. External Payment Methods
If you are using External payment methods (configured via Settings > Manage Bank & Credit Card Accounts), the same matching logic is required:
In Procurify: The GL Code entered in the Add Account form.
In Sage Intacct: The corresponding GL Account assigned to that bank or credit card account.
Comparison Table: Mapping Logic
Payment Type in Procurify | Procurify Field to Match | Intacct Field to Match |
Financial Account | GL Account Code | Checking Account > GL Account |
External Payment Method | GL Code (in Add Account form) | Bank/Credit Card > GL Account |
Note: Ensure there are no leading or trailing spaces in the GL code strings in either system, as this can prevent a successful match.
Frequently Asked Questions
Can we map the Location ID?
Yes, for all default dimension fields can be setup as "ID--Value" to map to the correct corresponding value in Sage.
Are there any restrictions on which account codes can be moved over from Sage to Procurify?
No. When the Account Code sync is enabled, all account codes will sync over to Procurify in one-hour intervals and be automatically applied to all departments available within the domain during the sync. For more information, see Syncing Chart of Accounts to Procurify (Master Data Sync).
If I add additional locations and departments after my account codes have synced to Procurify, will they automatically be applied to All Departments?
No. You must manually apply account codes to newly added locations and departments. Account codes can also be linked in bulk.
What Account Code value is being sent from Procurify to Sage Intaact?
Procurify only sends the Account Code (not the Account Description) and uses the Account Code to match the Account (item level) in Sage on the Bill line item.
Troubleshooting
Error Message: Custom field with Location-ID #: Tracking Category cannot be found
This error occurs when the Location Name is not an exact match in Procurify and Sage Intaact. Ensure that the Location name is an exact match.
Error Message: Custom field with Procurify ID custom-#: Tracking Category not found.
This error occurs when Custom Field is not an exact match in Procurify and Sage Intaact. Ensure the Custom Field is an exact match.
Error Message: Bill with Procurify ID #: Error when attempting operation: The Account number # is associated to [Account name]. Enter an account number on line item # in transaction # that's not associated with any bank account, and try again. Error code BL03002112
This occurs when an accounts are made available for syncing. Ensure to unassign applicable account codes manually.
Additional Information:
Once connected, custom field mapping options will be available on the Sage Integration set-up page (Settings → Integrations→ Sage Intacct Setup)
Ensure you correctly toggle the tax setting to sync over tax details as needed