Expense Lines Realtime-enabled

The detail lines of an expense document. Each line is one amount charged to an expense G/L account (glAccountNumber), with its own dimensions. A nested collection addressed under a parent: expenses({id})/expenseLines. Bank/G/L entries carry their own bankGLEntryLines collection; they used to reuse this one.

What the line captures

expenseDate, merchantName and receiptNo record what was actually bought. None of them affects posting. They are carried so an approver can review the report inside Business Central without going back to your expense system. The detail also survives in history after the staging document is cleared. See Processed Documents.

expenseDate is when the money was spent, which is why it sits on the line and not the header. A report submitted at month end routinely mixes expenses from several weeks.

Line grain: one line per charge

Send one line per amount you want charged to a G/L account, and set the line integrationId to match that grain:

• <entryId>. The expense entry becomes a single line.
• <entryId>-<itemizationId>. One itemized entry is flattened into several lines, for example a hotel bill split into room, meals and parking.

Keeping the itemization id in the key means a re-sent report maps line for line. It also means a line in history can still be traced to the charge it came from.