Skip to content
Copy site link for AI

Bank / G/L Entries Realtime-enabled — SmartConnect can trigger on changesRealtime-enabled

GETPOSTPATCHDELETETable: EONE Transaction

eOne/core/v1.0/bankGLEntries

Book a generic bank / G/L journal entry, a party-less document for bank fees, interest, accruals and adjustments. The composable sibling of Expenses: the header names the balancing account (balancingAccountType Bank or G/L + balancingAccountNumber), and each line under bankGLEntries(<id>)/bankGLEntryLines debits a G/L account (with its own dimensions); process writes one journal line per line plus a single balancing line for any remainder. A self-balancing entry whose lines already net to zero needs no balancing account at all. One of the Journal Wrappers.

This endpoint posts new journal entries. To read back posted entries, use the read-only G/L Entries feed instead.

Bound actions

Invoke with POST /bankGLEntries(<id>)/Microsoft.NAV.<action>:

  • validate: runs the posting checks without processing; surfaces any problem into status / errorMessage.
  • process: writes one G/L journal line per line, plus a single balancing line when the lines leave a remainder for the balancing account to take (unposted draft, or posted, per the Setup policy). An entry whose lines already net to zero gets no balancing line.
  • post: processes the entry and posts it, whatever the Setup policy says. Use it when SmartConnect decides that this one entry goes to the ledger now, rather than an administrator putting the whole endpoint on Auto Post. Only the lines this entry just wrote are posted, so other drafts sitting in the same journal batch are left alone, and the approval gate applies exactly as it does to process.
  • reopen: returns a failed entry to Open and clears its error, handing it back to the background job. A entry that hits status = Error is not collected again on its own, so on an Auto endpoint - where by definition nothing calls process - this is how a corrected entry gets moving. It refuses a entry that is pending approval, exactly as the Business Central action does.

process and post return no body. The staged entry deletes itself the moment its journal lines exist, so there is nothing to echo, and the outcome lives on the Processed Documents row the same call wrote. Fetch it by the integrationId you sent the entry with - processedDocuments?$filter=integrationId eq '<your id>' - and read postedDocumentNumber, postedPostingDate, glTransactionNumber and status; after post they are already filled in. validate writes nothing and points back at the staged entry. A rejected call returns the error and leaves the entry in staging, with errorMessage describing the problem, ready to correct and retry. See Journal Wrappers.

Approval is not done through the API. When an endpoint has Requires Approval set and a Business Central approval workflow is enabled for eOne documents, an entry must be Approved before it processes. A licensed user sends it for approval and approves it in Business Central, on the eOne Ledger Documents page (Send Approval Request, then the standard Approve/Reject/Delegate), backed by Approval User Setup. The read-only status (Open → Pending Approval → Approved) and errorMessage fields report where the document is; a failed automatic attempt lands status = Error with the reason in errorMessage.

Self-balancing entries

A journal whose debits and credits already net to zero, the shape a payroll import arrives in, posts as-is: leave balancingAccountType and balancingAccountNumber blank, and process writes exactly one journal line per line and nothing else. The balancing account is only required when the lines leave a remainder for it to take. An entry whose only line is zero is still refused, since there is nothing to post.

Dimensions are per line here, since each G/L distribution can carry its own cost centre. See Dimensions.

What a PATCH may do

Two rules apply to every write, on the header and on its lines and applications alike.

A entry under approval cannot be changed. Once status is Pending Approval or Approved, a PATCH, a line append or a delete is rejected. What the approver signed off on is what posts. Call reopen first if the entry genuinely has to change; that is an explicit act rather than a silent revocation, and it leaves no orphaned approval entry behind.

Deleting is also a setup choice. A DELETE of a staged entry is refused when the endpoint's Allow Manual Delete switch is off on the eOne Integration Setup page. It is on by default, so nothing changes until an administrator turns it off to mark the whole document family integration-owned. The approval rule above holds regardless of the switch.

Correcting a failed entry clears its error. Any successful write to a entry whose status is Error returns it to Open and empties errorMessage, so it becomes visible to the background job again - a line or application write counts, because the failure is usually in a line. The full text of every failed attempt is kept separately and is not lost when the live message is cleared. Awaiting Invoice is left alone: that one heals itself when the invoice posts.

Its own feature switch

This endpoint answers to Bank / G/L entries on the Features tab of eOne Integration Setup, not to Ledger documents. Turn it on in the company you are posting to, or both the header and its lines return an error naming the feature.

The switch was carved out of Ledger documents, so a company already importing bank/G/L entries keeps doing so across the upgrade: the new switch starts at whatever Ledger documents held. See Feature switches.

The child collection is bankGLEntryLines. It was published as expenseLines in earlier versions, because the endpoint reused the expense line page, which meant the collection was refused unless the unrelated Expenses feature also happened to be on. Update the nested route in any map that posts lines under an existing entry.