Title: Has anyone successfully created Engagement Manager trial balance accounts through the API? We’re getting HTTP 500
Hi everyone,
We’re building an integration that pulls a trial balance from QuickBooks Online and prepares it in Engagement Manager. API authentication and read operations are working: we can retrieve the client, engagement, trial balance views, grouping schedules, and accounts. We’re stuck at POST /external/v1/trialbalance/account/add.
We’ve tried a single-account create in two separate synthetic audit engagements. Both returned HTTP 500. Neither created an account, as confirmed by an immediate API read-back. We did not retry either request.
Our request follows the structure in the Engagement Manager API reference. Here is the October test, with the engagement ID and grouping schedule keys replaced by placeholders:
{
"engagementId": "<synthetic engagement ID>",
"accountNumber": "1010",
"description": "Checking",
"grpCodeSubcodes": [
{
"groupingScheduleKey": "<Account Classification schedule key>",
"codeText": "CA",
"subcodeText": "CASH"
},
{
"groupingScheduleKey": "<Title IV Financial schedule key>",
"codeText": "CA",
"subcodeText": "CASH"
},
{
"groupingScheduleKey": "<Data Analysis schedule key>",
"codeText": "1000",
"subcodeText": "1010"
}
],
"wpRef": ""
}
Before the request, we verified that the engagement was not finalized, its trial balance was empty, and those grouping codes and subcodes existed in the engagement’s schedules. We’re using the API-key and bearer-token headers required by the documentation. Importing accounts and groupings through the spreadsheet UI has worked in one of these test engagements.
Has anyone gotten account/add working? In particular:
- Does the endpoint require fields or a sequence of calls that the published example doesn’t show?
- Should grouping assignments be omitted when first creating the account and added in a later update?
- Is account creation followed by balance updates the intended API path for a full trial-balance import, or is there another supported approach?
- Have others seen HTTP 500 instead of a validation error for this endpoint?
The Thomson Reuters error IDs are cbbe79a1-9bbd-46c9-812e-a747d6a0af93 (September 30) and 955d3af4-969b-4fae-916c-9906e56ff226 (October 1). We can provide additional sanitized request details if helpful. We won’t post credentials or tokens.
Thanks for any examples or pointers.