ISP supports importing transaction splits for contributions and expenses via the API.
To utilize this functionality:
- Submit Splits First – Split transactions must be submitted before the parent transaction
- Unique Identifier Required – Each split transaction must include a UniqueIdentifier
- Reference Splits in Items – The parent transaction must include the associated split identifier or identifiers in the Items section
- Matching Transaction Types Required – The Transaction Type on the parent transaction and all associated splits must match
Transaction splits follow the same import model used by Deposit Batches.
Submitting Splits
Example of a split expense transaction. Multiple splits are supported.
{
“Company”: “Dave’s Pizza Parties”,
“EntityType”: “Company”,
“Line1”: “156 Pepperoni Blvd”,
“City”: “The Lakes”,
“State”: “NV”,
“ZipCode”: “88901”,
“Transactions”: [
{
“Amount”: “162.55”,
“UniqueIdentifier”: “pizza-5226”,
“Date”: “2020-01-07”,
“NoteForInternal”: “”,
“NoteForCompliance”: “Pizza”,
“ReportingCode”: “007”,
“TransactionType”: “Expense”
}
]
}
Submitting the Parent Transaction
After submitting the split transaction, submit the parent transaction and include the split identifier in the Items section.
{
“Company”: “Citibank”,
“EntityType”: “Company”,
“Line1”: “200 Wall Street “,
“City”: “The Lakes”,
“State”: “NV”,
“ZipCode”: “88901”,
“Transactions”: [
{
“Amount”: “162.55”,
“Date”: “2020-01-07”,
“NoteForInternal”: “”,
“NoteForCompliance”: “Credit Card Payment”,
“ReportingCode”: “007”,
“TransactionType”: “Expense”,
“Items”: [
“pizza-5226”
]
}
]
}
This same structure can be used for other Transaction Types, including Accrued Expense and Monetary Contribution. To associate multiple splits with a transaction, include multiple UniqueIdentifier values in the Items section.
