Bank G/L Entry Lines Realtime-enabled
GETPOSTPATCHDELETETable: EONE Transaction Line
The distribution lines of a bank / G/L entry. Each line books one amount to a G/L account (glAccountNumber), with its own dimensions. A nested collection addressed under a parent: bankGLEntries({id})/bankGLEntryLines.
lineNumber is stamped for you. description falls back to the header description when left blank. There are no resolver fields. The account is given directly as glAccountNumber.The lines are the distribution, not the counterparty
Send one line per account you want the amount booked to. The offsetting entry is not a line: it comes from the header's balancingAccountType and balancingAccountNumber, and process writes it as a single balancing journal line after the distribution lines. So a bank fee split across two departments is two lines here and one credit to the bank account, not three lines.
A positive amount debits the account and the balancing account takes the credit. Send a negative amount to reverse that, which is how interest received and other credits to a G/L account are booked.
Renamed from expenseLines
Earlier versions published this collection as expenseLines, because bank/G/L entries reused the expense line page. That made the collection answer to the Expenses feature switch while its header answered to another, so the endpoint was refused on every line POST unless a company happened to have both features on. The lines now have their own page and their own route, on the same Bank / G/L entries switch as the header.
Two consequences for an existing map: the nested route becomes bankGLEntries({id})/bankGLEntryLines, and the parent-reference columns are bankGLEntryId and bankGLEntryIntegrationId rather than expenseId and expenseIntegrationId. The expense-report fields that came with the borrowed page (expenseDate, merchantName, receiptNo) are gone; none of them ever affected how a bank/G/L entry posted.