Banking Data Layout

Banking data in graphiteConnect is validated by graphiteConnect before it appears in the API. All bank accounts provided by a supplier are returned as an array of JSON objects under the Banking_Account_Object answer key.

Banking_Account_Object

The Banking_Account_Object key holds the complete list of bank accounts for a supplier. Each object in the array represents a single bank account and contains the account details.

{
  "Banking_Account_Object": [
    {
      "_id": "7a3c1f2e89b04d5a6e91c2f8",
      "Bank_Name": "First National Bank",
      "Bank_Account_Number": "123456789",
      "Bank_Routing_Number": "021000021",
      "Bank_Account_Type": "Checking"
    },
    {
      "_id": "2b4d6f8a0c1e3g5i7k9m1o3q",
      "Bank_Name": "City Credit Union",
      "Bank_Account_Number": "987654321",
      "Bank_Routing_Number": "311079269",
      "Bank_Account_Type": "Savings"
    }
  ]
}

The _id field in each bank account object is the internal graphiteConnect identifier for that account instance.

No-Formatting Fields

Banking fields may include variants suffixed with _No_Formatting. These fields return the same data value with all formatting characters removed — for example, no hyphens (-), periods (.), or other characters used for human readability.

Example:

• Bank_Routing_Number: "02-1000-021" (formatted for display)
• Bank_Routing_Number_No_Formatting: "021000021" (raw digits only)

Use the _No_Formatting variants when your ERP system requires unformatted numeric strings for processing.

ERP-Selected Bank Accounts

Many customers with ERP integration configure graphiteConnect to allow suppliers to select which bank accounts should be synced to the ERP for payment processing. These selected accounts appear within the ERP_Record group alongside other ERP integration fields, rather than (or in addition to) the full Banking_Account_Object list.

In practice:

• Banking_Account_Object → all bank accounts provided by the supplier
• ERP_Record → contains a subset of bank accounts specifically chosen for ERP payment synchronization

When building your ERP integration, use the bank accounts within ERP_Record for payment data synchronization, and refer to Banking_Account_Object for a complete view of all supplier banking information.

Related Documentation

• ERP Record — ERP_Record group field definitions including selected bank accounts
• Company Data Layout — Overview of the full profile data structure
• Location Data Layout — Structure of location data