Error on Invoice Post
We're working on an integration that includes processing invoices and we're receiving an error when testing the Invoice POST. Any guidance would be much appreciated.

Request Body:
{
"vendor_id": 2,
"amount": 29.0100,
"description": "Invoice description",
"invoice_number": "793149-20200819",
"payment_details": {
"remit_to": {
"address_id": 8
},
"payment_method": "Check"
},
"invoice_date": "2020-08-19 00:00:00",
"post_date": "2020-11-04 13:07:12",
"distributions": [
{
"distribution_splits": [
{
"ui_project_id": "1100",
"transaction_code_values": [
{
"name": "Spendable/Non-Spendable",
"value": "Spendable",
"id": 233
}
],
"amount": 29.0100,
"percent": 100,
"account_class": "Unrestricted Net Assets"
}
],
"amount": 29.0100,
"description": "Distribution description",
"account_number": "01-5000-00",
"type_code": "Debit",
"custom_fields": []
},
{
"distribution_splits": [
{
"ui_project_id": "1100",
"transaction_code_values": [
{
"name": "Spendable/Non-Spendable",
"value": "Spendable",
"id": 233
}
],
"amount": 29.0100,
"percent": 100,
"account_class": "Unrestricted Net Assets"
}
],
"amount": 29.0100,
"description": "Distribution description",
"account_number": "01-2000-00",
"type_code": "Credit",
"custom_fields": []
}
]
}

Request Body:
{
"vendor_id": 2,
"amount": 29.0100,
"description": "Invoice description",
"invoice_number": "793149-20200819",
"payment_details": {
"remit_to": {
"address_id": 8
},
"payment_method": "Check"
},
"invoice_date": "2020-08-19 00:00:00",
"post_date": "2020-11-04 13:07:12",
"distributions": [
{
"distribution_splits": [
{
"ui_project_id": "1100",
"transaction_code_values": [
{
"name": "Spendable/Non-Spendable",
"value": "Spendable",
"id": 233
}
],
"amount": 29.0100,
"percent": 100,
"account_class": "Unrestricted Net Assets"
}
],
"amount": 29.0100,
"description": "Distribution description",
"account_number": "01-5000-00",
"type_code": "Debit",
"custom_fields": []
},
{
"distribution_splits": [
{
"ui_project_id": "1100",
"transaction_code_values": [
{
"name": "Spendable/Non-Spendable",
"value": "Spendable",
"id": 233
}
],
"amount": 29.0100,
"percent": 100,
"account_class": "Unrestricted Net Assets"
}
],
"amount": 29.0100,
"description": "Distribution description",
"account_number": "01-2000-00",
"type_code": "Credit",
"custom_fields": []
}
]
}
0
Comments
-
Hi Zachary,
My name is Eddie Barker and I'm one of the product managers for Financial Edge NXT. I looked at this and then had one of my engineers take a deeper look (because your payload looks right). Since it looks like you're testing this on our sample database, there's another transaction code that is being used in this database. We added that to your payload, and it validates and posts the invoice. Here's the updated payload with the "Grants" section added:
From the looks of it, it seems like we'll need to address this longer-term in the software, but this should be an easy addition that lets you move forward. In a nutshell, if you have setup your database to use one of the five transaction codes, you should provide for that in your payload.
{
"vendor_id": 2,
"amount": 29.0100,
"description": "Invoice description",
"invoice_number": "793149-20200819",
"payment_details": {
"remit_to": {
"address_id": 8
},
"payment_method": "Check"
},
"invoice_date": "2020-08-19 00:00:00",
"post_date": "2020-11-04 13:07:12",
"distributions": [
{
"distribution_splits": [
{
"ui_project_id": "1100",
"transaction_code_values": [
{
"name": "Grants",
"value": "None"
},
{
"name": "Spendable/Non-Spendable",
"value": "Spendable",
"id": 233
}
],
"amount": 29.0100,
"percent": 100,
"account_class": "Unrestricted Net Assets"
}
],
"amount": 29.0100,
"description": "Distribution description",
"account_number": "01-5000-00",
"type_code": "Debit",
"custom_fields": []
},
{
"distribution_splits": [
{
"ui_project_id": "1100",
"transaction_code_values": [
{
"name": "Grants",
"value": "None"
},
{
"name": "Spendable/Non-Spendable",
"value": "Spendable",
"id": 233
}
],
"amount": 29.0100,
"percent": 100,
"account_class": "Unrestricted Net Assets"
}
],
"amount": 29.0100,
"description": "Distribution description",
"account_number": "01-2000-00",
"type_code": "Credit",
"custom_fields": []
}
]
}
If this doesn't work for you, feel free to reply to this post, and we'll go from there, probably outside the Community.
Thanks!
Eddie Barker
0
Categories
- All Categories
- 6 Blackbaud Community Help
- 213 bbcon®
- 1.4K Blackbaud Altru®
- 401 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 655 Blackbaud Grantmaking™
- 576 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 939 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.6K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 248 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 241 Member Lounge (Just for Fun)
- 34 Blackbaud Community Challenges
- 34 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 791 Community News
- 2.9K Jobs Board
- 53 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
