Code invoice line items with GL accounts
Code an invoice line by reviewing or changing its GL Account field in the unified line-item workspace.
Who can do this
You need company:invoice:edit to change an editable GL Account field.
Before you start
- Open an editable invoice.
- Make sure the invoice line uses a segment and field set that includes GL Account.
Line sections, field order, and available account values come from your company schema and ERP data. A field may also be derived or locked by a relationship.
Code a line in the workspace
- Open Invoices, then select the invoice you want to code.
- Find the line in the stacked line-item workspace. Do not look for segment tabs because the configured sections appear one below another.
- In Review view, find GL Account under the line's section label. In Table view, scroll horizontally if GL Account is one of the configured columns.
- Select the GL Account field and choose an available account.
- Compare the selected account with the source document and any matching context on the line.
Code a line in the full editor
- Select the pencil action for the line. Its accessible label is
Edit {segment noun}. - Find GL Account in the
Edit {segment noun}dialog. - Choose an available account, then select Done.
If the field is locked, read the lock explanation. A derived value can be visible without being editable, which means changing a related source field may be the correct fix.
To apply one account to several eligible lines, select the lines and use Set field. See Edit and bulk-update invoice lines for the full bulk flow.
What you should see
The chosen account appears in GL Account, then the invoice saves and validation runs again. The display value follows your company's configured account format.
If something goes wrong
- If GL Account does not appear in Table view, switch to Review view or open the full line editor.
- If the account you need is unavailable, check the line's other relationship fields and confirm that the account is available in your ERP data.
- If GL Account is locked, do not try to replace the derived value. Read the lock explanation and review the related match or source field instead.