ERP Record

The typical graphiteConnect implementation includes a section of internal-use data called the ERP Record. Graphite consolidates the majority of the relevant information about an entity into this section to make integrating with an ERP system easier.

Most API workflow documentation references ERP_Record as the starting point for synchronization. This page defines the fields in that group.

Field Reference

Field	Description
`ERP_Record`	The group key for all ERP records. An array holding one or more ERP record instances.
`_id`	The unique identifier for this `ERP_Record` instance. Also known as the instance ID, used in the acknowledge API call to target a specific record.
`ERP_ID`	The identifier for this supplier within the ERP system. This value is passed back to graphiteConnect after the first successful synchronization. If empty, the integration should create a new supplier in the ERP system.
`Integration_ERP_Status`	A Graphite-managed field indicating whether the last synchronization was successful. Automatically updated by the acknowledge API call.
`Integration_ERP_ON`	A flag allowing managers to enable or disable ERP integration for each individual ERP record.

ERP_Record in the Integration Workflow

When fetching a supplier profile, your integration should:

Find the ERP_Record array in the profile data.
For each ERP record instance, check ERP_ID:
- Empty → create a new vendor record in the ERP and write the new ID back using PATCH /profile/{publicId}.
- Populated → update the existing vendor record in the ERP.
Acknowledge each instance using its _id value as the instanceId parameter in POST /changes/acknowledge.

Ready To Transact Fields

The ERP_Record group also contains the following answer keys related to the Ready To Transact feature:

Field	Description
`ERP_Ready_To_Transaction`	Set to `"y"` if the company is ready for transactions, or `"n"` if transactions should be blocked.
`ERP_Ready_To_Transaction_Reason`	A plain English explanation of why transactions are blocked (e.g., `"Contract open for review"`).

Selected Bank Accounts

When a supplier selects bank accounts for ERP synchronization, those selected accounts appear as a subset within the ERP_Record group. All bank accounts for a supplier are available under the Banking_Account_Object group; the ERP_Record subset contains only those chosen for payment processing.

See Banking Data Layout and Ready To Transact for related documentation.