Workday’s financial model defines ledger accounts within the scope of an account set. While the Journal_Entry_Line data currently includes the Ledger_Account_ID, it does not include the corresponding Account_Set_ID. These two values are required together to uniquely identify a ledger account within a Workday tenant.

Using the Get_Journals SOAP endpoint, we confirmed that Workday returns this relationship in the following structure:

<wd:Ledger_Account_Reference>
<wd:ID wd:type="Ledger_Account_ID" wd:parent_type="Account_Set_ID" wd:parent_id="Corporate">6000</wd:ID>
</wd:Ledger_Account_Reference>

In this example, the parent_id value "Corporate" represents the Account Set Name. This value is globally unique and is essential for joining journal entry lines to the appropriate ledger accounts.

While the current connector implementation includes an integration ID for Ledger_Account, we are unable to reliably use it due to the structure of Workday’s Get_Ledger_Accounts API. Without the account set context, it is impossible to resolve the correct account across potentially ambiguous IDs.

We are requesting that the Account_Set_ID (the value of parent_id shown above) be added to each Journal_Entry_Line record returned by the connector. This is necessary to ensure accurate mapping between journal entries and ledger accounts which is absolutely crucial to our business's use of this connector