TIBCO Scribe® Online Connector For Sage Intacct

Use the TIBCO Scribe® Online Connector For Sage Intacct to integrate sales and financial data.

Possible use cases for the Sage Intacct Connector include:

• Integrate sales invoices from a proprietary operational system to Sage Intacct Order Entry.
• Update customer information when changes are entered in your CRM application.
• Import payments from an online banking system and match to Sage Intacct posted invoices.
• Create a project when a new opportunity is marked Closed-Won in your CRM system.
• Import data into Sage Intacct from spreadsheets containing records such as customers, vendors, or items.
• Customize a Quote-to-Cash integration between your CRM and Sage Intacct.
• Create and maintain a local data warehouse of Sage Intacct data.
• Synchronize customers from Sage Intacct to a local, custom database for marketing.
• Connect HubSpot CRM data with Sage Intacct customer data.
• Synchronize data between ConnectWise PSA and Sage Intacct with pre-built, customizable templates.

Connector Specifications

This Connector supports the latest version of the Sage Intacct API.

	Supported
Agent Types
On Premise	X
Cloud	X
Replication Services
Source
Target
Integration Services
Source	X
Target	X
Migration Services
Source
Target
Maps
Integration	X
Request-Reply	X
Message

Supported Entities

The Sage Intacct Connector supports the following entities. Click a linked entity name for additional information when using that entity in TIBCO Scribe® Online. For a list of additional operations by entity see Special Operations.

Standard Operations

Entity	Query	Create	Update	Delete	Upsert
ARPayment	X	X	X	X	X
ARPaymentBatch	X	X	X	X	X
Bill	X	X	X	X	X
BillLineItem	X	X	X	X	X
Class	X	X	X	X	X
Contact	X	X	X	X	X
Customer	X	X	X	X	X
Department	X	X	X	X	X
EExpenses	X	X	X	X	X
EExpensesItem	X	X	X	X	X
Employee	X	X	X	X	X
GLAccount	X	X	X	X	X
GLEntry	X	X	X	X	X
GLEntry30	X	X	X	X	X
ICItem	X	X	X	X	X
Invoice	X	X	X	X	X
Item	X	X	X	X	X
Location	X	X	X	X	X
POTransaction	X	X	X	X	X
POTransactionItem	X	X	X	X	X
Project	X	X	X	X	X
ProjectResources	X	X	X	X	X
ProjectStatus	X	X	X	X	X
ProjectType	X	X	X	X	X
SOPriceList	X	X	X	X	X
SOPriceListEntry	X	X	X	X	X
SOTransaction	X	X	X	X	X
SOTransactionItem	X	X	X	X	X
Task	X	X	X	X	X
TaskResources	X	X	X	X	X
Timesheet	X	X	X	X	X
TimesheetEntry	X	X	X	X	X
Vendor	X	X	X	X	X
Warehouse	X	X	X	X	X

Special Operations

Entity	Operations
	-CreateWith -UpdateWith -Add

Setup Considerations

• The Web Services subscription must be enabled in your Sage Intacct Company.
• Sage Intacct Trial accounts are not supported with this Connector. Contact your Sage Intacct representative for a Demo or a production account instead.

API Usage Limits

Sage Intacct is limited to two concurrent operations at any given time. Other operations are queued until a slot is free or until the connection times out. Any one of the following actions also makes a Connection to the Sage Intacct API and may exceed the limit of two operations at the same time:

• Running another Solution that connects to Sage Intacct using the same account.
• Debugging a Map that connects to Sage Intacct.
• Creating more than one Sage Intacct Connection using the same account.
• Selecting OK on the Edit Connection dialog for your Sage Intacct Connection.
• Testing the Sage Intacct Connection.
• Refreshing metadata for Sage Intacct.
• Retrieving metadata for a new Map that connects to Sage Intacct.

Some options to prevent your Sage Intacct Solutions from failing include: 

• Pausing Sage Intacct Solutions when you need to do other work that connects to Sage Intacct.
• Using a single Solution that contains all of your Sage Intacct Maps, so they never execute at the same time.
• Scheduling Solutions to run at staggered intervals to prevent them from trying to access the API at the same time.

Selecting An Agent Type For Sage Intacct

Refer to TIBCO Scribe® Online Agents for information on available Agent types and how to select the best Agent for your Solution.

Connecting To Sage Intacct

1. Select More > Connections from the menu.
2. From the Connections page select Add to open the Add a New Connection dialog.
3. Select the Connector from the drop-down list in the Connection Type field, and then enter the following information for this Connection:
   • Name — This can be any meaningful name, up to 25 characters.
   • Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
   • Company ID — Enter your Sage Intacct company ID.
   • Location ID — Optional field. Limits the entities returned to the selected Location.
   • UserID — Enter your Sage Intacct User ID.
   • Password — Enter your Sage Intacct Password.
   • POTransaction Types — Optional field. To include custom fields associated with Purchases in your metadata, enter a comma separated list of any PO Transaction definitions associated with those fields.
   • SOTransaction Types — Optional field. To include custom fields associated with Sales Orders in your metadata, enter a comma separated list of the SO Transaction definitions associated with those fields.
   • Custom Object Types — Optional field. To include custom objects or entities in the metadata returned from Sage Intacct enter a comma separated list of those entity names.
4. Select Test to ensure that the Agent can connect to your database. Be sure to test the Connection against all Agents that use this Connection. See Testing Connections.
5. Select OK/Save to save the Connection.

Metadata Notes

• Parent/Child relationships are not supported.
• Hierarchical relationships, such as grandparent, parent, grandchild relationships are not supported. See Hierarchical Data for examples.
• Datetimes stored in the Sage Intacct database use the Pacific time zone.
• Data in Sage Intacct is case sensitive.

Naming

Connection metadata must have unique entity, relationship, and field names. If your Connection metadata has duplicate names, review the source system to determine if the duplicates can be renamed.

Retry Logic

• Timeout exceptions are caught and retried.
• Connector retries three times.

Sage Intacct Connector As IS Source

Consider the following when using the Sage Intacct Connector as an Integration Solution source.

Filtering

When a datetime is configured on the Query Block on the Block Properties Net Change Tab to query for new and updated records, that configuration is treated as an additional filter. The Net Change datetime filter is applied as an AND after any other filters specified on the Block Properties Filter Tab. TIBCO Scribe® Online builds a query combining both the Net Change filter and the filters on the Filter tab. See Net Change And Filters for an example.

Some Connectors for TIBCO Scribe® Online only support one filter. For those Connectors you can use either Net Change or one filter on the Filter tab, not both.

TIBCO Scribe® Online API Considerations

To create connections with the TIBCO Scribe® Online API, the Sage Intacct Connector requires the following information:

Connector Name	Intacct
Connector ID	C4A1656F-D1CB-4EB5-BD5B-5B5486568A02

TIBCO Scribe® Online Connection Properties

In addition, this Connector uses the Connection properties shown in the following table.

Name	Data Type	Required	Secured	Usage
CompanyID	String	Yes	No
LocationID	String	No	No
UserID	String	Yes	No
POTransactionTypes	String	No	No	Comma separated list.
SOTransactionTypes	String	No	No	Comma separated list.
CustomObjectTypes	String	No	No	Comma separated list.
UserPassword	String	Yes	Yes

More Information

For additional information on this Connector, refer to the Knowledge Base and Discussions in the TIBCO Community.