Update a Line Entry

PUT

line-entries

{line_entry_id}

Authorizations

Authorization

string

headerrequired

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

teal-instance-id

string

required

The Teal instance ID

modified-by

string | null

An optional identifier for audit logging.

Path Parameters

line_entry_id

string

required

The line entry ID

Query Parameters

expand

enum<string>[] | null

Comma-separated list of Line Entry expand paths.

Available options:

transaction,

ledger,

journal_entry

Body

application/json

description

string | null

An arbitrary string on the object, useful for displaying to the user or for categorization.

ledger_id

string | null

The ID of the Line Entry's Ledger. Can be null in some cases for Instances using QuickBooks as their accounting package.

tag_ids

string[] | null

A list of IDs of the Tag objects associated with the Line Entry.

Response

201 - application/json

amount

number

required

The value of the line entry in decimal dollar cents.

debit_credit

enum<string>

required

Indicates if the amount is a credit or debit.

Available options:

debit,

credit

ledger_id

string

required

The ID of the Line Entry's Ledger. Can be null in some cases for Instances using QuickBooks as their accounting package.

string | null

required

The unique ID of the object. Can be null in some cases for Instances using QuickBooks as their accounting package.

datetime

string

required

The datetime the Line Entry was created in UTC time.

editable

boolean

required

Indicates if the Line Entry can be manually added or removed from a Ledger, as dictated by the editable property on the Ledger.

journal_entry_id

string | null

required

The ID of the associated Journal Entry. Can be null in some cases for Instances using QuickBooks as their accounting package.

journal_entry_description

string

required

An arbitrary string on the object, useful for displaying to users.

ledger_name

string

required

The name of the Line Entry's Ledger.

description

string | null

An arbitrary string on the object, useful for displaying to the user or for categorization.

If the Line Entry is identified as a transfer between accounts, the ID of the Line Entry in the opposing Ledger.

Related guide: Auto-categorization

transaction_id

string | null

The ID of the associated Transaction, if one exists.

journal_entry

object | null

Expandable. The associated Journal Entry object.

ledger

object | null

Expandable. The associated Ledger object.

ledger.id

string

required

The unique ID of the object.

ledger.debit_credit

enum<string>

required

Indicates if the ledger is a credit or debit ledger.

Required if financial_account_type is not specified.

Available options:

debit,

credit

ledger.editable

boolean

required

Whether line entries can be manually added or removed from the Ledger. Set to false if you control the source of truth for the Ledger and want to restrict user changes, for example, if the Ledger is for a bank account or a payments account you control (i.e. you are a neobank or using a Banking as a Service platform).

ledger.is_required

boolean

required

Indicates that the ledger is one of the four system ledgers required for teal to work. In the default chart of accounts, these are named one of: Transfers Between Accounts, Opening Balance Retained Earnings, Uncategorized Cash Inflow, Uncategorized Cash Outflow. You can update the names of these to fit your needs.

ledger.name

string

required

The name of the ledger. Teal does not enforce any other conventions or patterns on naming schemes; however, we recommend you use concise, descriptive names, especially for financial account ledgers.

ledger.parent_id

string | null

required

If the Ledger is a child Ledger, the ID of the parent Ledger object.

ledger.report_cash_flow

boolean

required

Whether Teal includes this ledger in the cash flow report.

Required if financial_account_type is not specified.

ledger.sort_code

string

required

Determines the display order in reports, ordered digit by digit, starting from the leftmost position. For example, 20010 will come before 3050.

Teal does not enforce any other conventions or patterns on sort codes. However, it is recommended to adopt a common convention such as starting all ledgers of the same type with the same number (assets start with 1, liabilities start with 2, etc.). The default CoA templates provided by Teal follow best practices for sort code numbering.

ledger.sub_type

enum<string>

required

Indicates similar characteristics and accounting treatment for a group of ledgers within a type.

Required if financial_account_type is not specified.

Available options:

current_assets,

non-current_assets,

transfers_between_accounts,

uncategorized_assets,

current_liabilities,

non-current_liabilities,

equity,

operating_revenues,

other_income,

cost_of_goods_sold,

operating_expenses,

other_expenses

ledger.type

enum<string>

required

Indicates the purpose and location of the funds and value recorded in the Ledger and which report it is included in: asset, liability and equity ledgers are displayed on the balance sheet; revenue and expenses are displayed on the income statement.

    Required if `financial_account_type` is not specified.

Available options:

asset,

liability,

equity,

revenue,

expense

ledger.financial_account_type

enum<string> | null

If specified, indicates that the ledger represents a real-world financial account.

If provided when creating a new Ledger object, you do not need to provide debit_credit, type, sub_type, or report_cash_flow values as we will provide default values.

Available options:

bank_account,

credit_card,

payments,

payroll,

loan,

prepaid_card,

accounts_receivable,

accounts_payable

ledger.parent

any | null

Expandable. If the ledger is a child ledger, the parent Ledger object.

API overview

Teal API Endpoints

API Migration

Update a Line Entry

Authorizations

Headers

Path Parameters

Query Parameters

Body

Response