Dynamics Community Forum Thread Details

How to link General Ledger Entries to Customer/Vendor/Contact via Business Central API?

Hi everyone,

We are integrating with Microsoft Dynamics 365 Business Central using the standard API v2.0.

We currently import generalLedgerEntries from the standard endpoint: /api/v2.0/companies({companyId})/generalLedgerEntries

We would like to link individual general ledger entries to the related customer, vendor, or contact in Business Central.

However, the standard generalLedgerEntry API resource only seems to expose fields such as:

id
entryNumber
postingDate
documentNumber
documentType
accountId
accountNumber
description
debitAmount
creditAmount
lastModifiedDateTime

It does not appear to expose fields such as:

Source Type
Source No.
Customer No.
Vendor No.
Customer Id
Vendor Id
Contact Id

Because of this, we cannot reliably determine whether a G/L entry belongs to a customer or vendor, or link it to the related contact.

I understand that the underlying G/L Entry table in Business Central may contain fields like Source Type and Source No., which could potentially be used to link to customers or vendors. But these fields do not seem to be available in the standard API v2.0 generalLedgerEntries resource.

My questions are:

Is there any standard Business Central API endpoint that allows us to reliably link a generalLedgerEntry to its related customer/vendor/contact WITHOUT creating a custom AL APPI query?

Any guidance, examples, or recommended approaches would be appreciated.

Thanks!

Categories:

Dynamics 365 Business Central

Hello,

No, the standard API v2.0 generalLedgerEntries endpoint does not expose Source Type, Source No., Customer Id, Vendor Id, or Contact Id; Microsoft’s v2.0 resource only gives the G/L account-related fields and navigation to account/attachments/dimensions, so you cannot reliably link each G/L entry to a customer/vendor/contact from that endpoint alone. Microsoft does show other reporting/analytics G/L entry resources that include sourceType / sourceNo, but that is not the same standard API v2.0 resource, so for a clean production integration the usual approach is to create a small custom API page/query over G/L Entry exposing Source Type and Source No. and then map Customer / Vendor from there; contact linkage may still need extra logic because the G/L Entry does not always directly represent a contact.

Regards,
Oussama Sabbouh

Quick Links

Leaderboard > Small and medium business | Business Central, NAV, RMS