Schemas

First day of the fiscal year, inclusive (YYYY-MM-DD)

Last day of the fiscal year, inclusive (YYYY-MM-DD)

Whether the year is still open for posting

The company's base (functional) currency, ISO 4217. Every figure a report labels a base-currency total is denominated in this.

The fiscal year containing today. Null when no accounting year covers today — a company mid-setup, or one whose years stop short of the current date.

Unique identifier for the company, uuidv7 based

Company name

Primary email address

Street address

The company's accounting configuration: base currency and the fiscal year covering today.

VAT / company registration number, as registered

Billing email address

City

Postal code

Country code (ISO 3166-1 alpha-2)

Phone number

Preferred language code

Contact person first name

Contact person last name

Name of the rate limit tier

Time-to-live in milliseconds for this rate limit tier (0 means no time limit)

Maximum number of requests allowed within the TTL window (-1 means unlimited)

Available rate limit tiers for this API key

Expiration date and time of the API key

List of IP addresses allowed to use this API key

List of scopes granted to this API key

The unique identifier of the account

Name of the account

Account type number

Public account id that the account maps to

Type of ledger account. Only BALANCE_SHEET and PROFIT_AND_LOSS accounts can be used in journal entries.

The side a journal-entry line on this account pre-selects: debit or credit. This is the Debit/Credit choice on the account form. It does not decide how a balance is reported; accountClassification does.

IDs of the dimensions this account requires: every journal entry line posting to the account must carry a value from each of them, or the entry is refused with JOURNAL_TAG_REQUIRED_DIMENSION_MISSING. Empty when the account requires none. This is the account setting as stored: a dimension that has since been deactivated stays listed and is not enforced until it is active again, so match the ids against the dimensions list, which returns active dimensions only.

Account classification (ASSET, LIABILITY, EQUITY, REVENUE, EXPENSE)

Control account type. ACCOUNTS_RECEIVABLE requires customerId on journal entries, ACCOUNTS_PAYABLE requires vendorId. Null for regular accounts.

VAT code applied by default to journal-entry lines on this account, or null

First account number of the range (inclusive)

Last account number of the range (inclusive)

The unique identifier of the account

Name of the account

Account type number

Public account id that the account maps to

Type of ledger account. Only BALANCE_SHEET and PROFIT_AND_LOSS accounts can be used in journal entries.

The side a journal-entry line on this account pre-selects: debit or credit. This is the Debit/Credit choice on the account form. It does not decide how a balance is reported; accountClassification does.

IDs of the dimensions this account requires: every journal entry line posting to the account must carry a value from each of them, or the entry is refused with JOURNAL_TAG_REQUIRED_DIMENSION_MISSING. Empty when the account requires none. This is the account setting as stored: a dimension that has since been deactivated stays listed and is not enforced until it is active again, so match the ids against the dimensions list, which returns active dimensions only.

The currency the account is kept in (ISO 4217). A balance-sheet account may be kept in a foreign currency; every other account is kept in the company's base currency.

Free-form tags for grouping accounts

When the account was created

When the account was last changed

Account classification (ASSET, LIABILITY, EQUITY, REVENUE, EXPENSE)

Control account type. ACCOUNTS_RECEIVABLE requires customerId on journal entries, ACCOUNTS_PAYABLE requires vendorId. Null for regular accounts.

VAT code applied by default to journal-entry lines on this account, or null

The account number this account reports under. When set, publicAccountId follows it.

For a TOTAL_FROM account: the first account number it sums from, up to the account's own number

For a TOTAL_INTERVALS account: the account-number ranges it sums

When the account was deactivated, or null while it is active

Name of the account

Account number, unique within the company

Kind of account. Only BALANCE_SHEET and PROFIT_AND_LOSS accounts take postings; HEADING, HEADING_BREAK, TOTAL_FROM and TOTAL_INTERVALS structure the chart.

Classification of a postable account; required whenever the request sets ledgerType to BALANCE_SHEET or PROFIT_AND_LOSS. Decides which statement the account belongs to and which side a journal-entry line on it pre-selects. It cannot be cleared.

Marks a control account. Lines on an ACCOUNTS_RECEIVABLE account need a customerId, lines on an ACCOUNTS_PAYABLE account a supplierId. The classification must fit: receivable is an ASSET, payable a LIABILITY. Null clears it.

The side a journal-entry line on this account pre-selects: debit or credit. Omitted on create, it follows accountClassification (ASSET and EXPENSE pre-select debit, the rest credit); an account with no classification, which only a heading or total account can be, pre-selects debit. It cannot be cleared.

VAT code applied by default to journal-entry lines on this account. Null clears it.

Currency the account is kept in, as an ISO 4217 code. Applies to a BALANCE_SHEET account only; every other account is kept in the company's base currency and the field is ignored. Moving an account off BALANCE_SHEET resets it to the base currency.

Free-form tags for grouping accounts (at most 25, each at most 50 characters)

The account number this account reports under. When set, publicAccountId reports it instead of accountNumber. Null clears it.

For a TOTAL_FROM account: the first account number to sum from; the total runs up to the account's own number. Required whenever the request sets ledgerType to TOTAL_FROM.

For a TOTAL_INTERVALS account: the account-number ranges to sum (at most 50). Required whenever the request sets ledgerType to TOTAL_INTERVALS.

Classification of a postable account; required whenever the request sets ledgerType to BALANCE_SHEET or PROFIT_AND_LOSS. Decides which statement the account belongs to and which side a journal-entry line on it pre-selects. It cannot be cleared.

Marks a control account. Lines on an ACCOUNTS_RECEIVABLE account need a customerId, lines on an ACCOUNTS_PAYABLE account a supplierId. The classification must fit: receivable is an ASSET, payable a LIABILITY. Null clears it.

The side a journal-entry line on this account pre-selects: debit or credit. Omitted on create, it follows accountClassification (ASSET and EXPENSE pre-select debit, the rest credit); an account with no classification, which only a heading or total account can be, pre-selects debit. It cannot be cleared.

VAT code applied by default to journal-entry lines on this account. Null clears it.

Currency the account is kept in, as an ISO 4217 code. Applies to a BALANCE_SHEET account only; every other account is kept in the company's base currency and the field is ignored. Moving an account off BALANCE_SHEET resets it to the base currency.

Free-form tags for grouping accounts (at most 25, each at most 50 characters)

The account number this account reports under. When set, publicAccountId reports it instead of accountNumber. Null clears it.

For a TOTAL_FROM account: the first account number to sum from; the total runs up to the account's own number. Required whenever the request sets ledgerType to TOTAL_FROM.

For a TOTAL_INTERVALS account: the account-number ranges to sum (at most 50). Required whenever the request sets ledgerType to TOTAL_INTERVALS.

Name of the account

Account number, unique within the company

Kind of account. Setting a postable type requires accountClassification in the same request; setting TOTAL_FROM requires totalFrom, and TOTAL_INTERVALS requires intervals.

The extract items — one object per extract (momsindberetning, erhvervsselvangivelse, udbytteindberetning, e-indkomst, skattekonto, lønsum, …). Each item is stored as received.

The delivering system, e.g. 'revibot'.

The sender's own id for this batch. Folded into the idempotency claim, so an x-api-idempotency-key reused across two DIFFERENT batches is refused (422) instead of silently replaying the first batch's response.

Number of extract items stored.

Number of extract items stored.

Distinct CVRs in this batch that are not clients of the firm, as digits only. Their items are stored all the same; a CVR listed here usually means the firm's client list is missing that client.

Items whose cvr was missing or not a registration number. They are stored without a subject.

The id of the firm's own record of the client when it keeps one, else the client's company id. Key a sync on companyNumber and productionUnitNumber together: a client the firm first knows through its company id takes the record's id once the firm records it.

The CVR (Danish company registration number), digits only. Name the client by it when delivering data about it.

The P-number of the office the client is, 10 digits, when the client is one office of a company; null for the whole company. Offices of one company share a companyNumber and differ here.

The firm's own client number, when it keeps one.

True while the client keeps its books in LedgerBee; false again once it stops.

When the client was added to the firm, or the firm's record of it or the client's own company last changed, whichever is later.

Clients on this page, sorted by name.

Total clients matching the query.

Clients per page.

Cursor for the next page; pass it as cursor. null on the last page, and on every page of a sort that cannot page by cursor — hasMore then says whether another page follows by page number.

Whether more rows follow this page.

The unique identifier of the customer group

Customer group number

Name of the customer group

The ledger account ID associated with this customer group. Present with the customers-read scope; omitted for checkout-only keys.

The ledger account number associated with this customer group

The ledger account name associated with this customer group

Key-value metadata attached to the customer group

The unique identifier of the department

Name of the department

Whether this is the default department for the customer

Whether the department is active

Purchase order number

EAN number for e-invoicing

Street address

City

Postal code

Two-letter country code (ISO 3166-1 alpha-2)

The unique identifier of the contact

Name of the contact

Whether this is the default contact for the customer

Email address

Phone number

The unique identifier of the customer

Customer number

Customer type

Name of the customer

VAT zone classification

Customer group ID

Whether the customer is active

Billing relationship. self = this customer is billed directly. parent_pays = the parent customer (set via parentCustomerId) is billed instead.

Whether to attach a zip of per-child detail PDFs when sending consolidated invoices. Only relevant for parent customers in single_invoice mode.

Whether this customer's portal users may fill in their own billing details (VAT number, street, postal code, city), both on the portal's Company settings page and during checkout, instead of only confirming a read-only copy of the record. Country and customer type stay operator-owned either way, which is what keeps them inside the VAT regime the operator assigned.

Customer group number

Customer group name

Email address

Phone number

Street address

City

Postal code

Two-letter country code (ISO 3166-1 alpha-2)

VAT registration number

Website URL

External system identifier for tracking the customer across other systems

EAN number for e-invoicing. Absent when the customer has none.

Credit limit

Opening balance in the company base currency (signed: positive = the customer owes us)

Payment terms in days

Payment term type

Default currency code

Parent customer ID. When set, this customer is a child in a parent-child billing relationship. Set together with billingRelationship to change how this customer is billed.

Consolidation mode for a parent customer. single_invoice = all child subscriptions are consolidated onto one parent invoice on billingDay. per_child_invoice = each child receives its own invoice. Only meaningful on parent customers.

Day of month (1-28) when the parent consolidated invoice is generated. Required for single_invoice consolidation mode.

Parent single invoice PDF template override

Key-value metadata attached to the customer

Customers on this page

Total customers matching the query

Items per page

Cursor for the next page; pass it as cursor. null on the last page, and on every page of a sort that cannot page by cursor — hasMore then says whether another page follows by page number.

Whether more rows follow this page.

Specifies whether the customer is a business or a private person

Customer name

VAT zone classification

Customer group ID

Two-letter country code

The currency this customer is invoiced in, ISO 4217 alpha-3.

Unique customer number. Omit it, or send an empty value, to have the next number assigned from the company customer sequence; the assigned number comes back on the response.

Email address

Phone number

Street address

City

Postal code

VAT registration number

Website URL

External system identifier for tracking the customer across other systems

EAN number for e-invoicing. Digits only.

Additional notes

Credit limit

Opening balance in the company base currency, seeding receivables that predate LedgerBee. Signed: positive = the customer owes us, negative = a credit position.

Payment terms in days

Payment term type

Whether the customer is active

Parent customer ID. Set when creating this customer as a child in a parent-child billing relationship. Must be combined with billingRelationship = parent_pays to route billing to the parent. Send null to create a standalone customer.

Billing relationship. self (default) = this customer is billed directly. parent_pays = the parent customer (set via parentCustomerId) is billed instead.

Consolidation mode (parent customers only). single_invoice = all child subscriptions consolidated onto one invoice on billingDay. per_child_invoice = each child receives its own invoice.

Day of month (1-28) for the parent consolidated invoice. Required for single_invoice consolidation.

Whether to attach a zip of per-child detail PDFs when sending consolidated invoices

Whether this customer's portal users may fill in their own billing details (VAT number, street, postal code, city), both on the portal's Company settings page and during checkout, instead of only confirming a read-only copy of the record. Country and customer type stay operator-owned either way, which is what keeps them inside the VAT regime the operator assigned.

Parent single invoice PDF template override. Send null to clear.

Key-value metadata to attach to the customer. At most 50 entries; keys up to 128 characters, string values up to 500 characters.

The unique identifier of the created customer

Customer number

The subscription to move onto the new billing arrangement: the id GET /v1/subscriptions returns, the same stable id every subscription endpoint takes.

Customer type

Unique customer number

Customer name

VAT zone classification

Customer group ID

Email address. Send null or empty string to clear.

Phone number

Street address

City

Postal code

Two-letter country code

VAT registration number

Website URL

External system identifier for tracking the customer across other systems

EAN number for e-invoicing. Digits only. Send null or empty string to clear.

Additional notes

Credit limit

Opening balance in the company base currency, seeding receivables that predate LedgerBee. Signed: positive = the customer owes us, negative = a credit position.

Payment terms in days

Payment term type

The currency this customer is invoiced in, ISO 4217 alpha-3. Omit it, or send a blank one, to leave the stored currency alone.

Whether the customer is active

Parent customer ID. Send null to detach from parent. Changing this field on a customer with active subscriptions will transition those subscriptions to the parent's billing day with a clean cut at today's date: advance-billed subscriptions receive a credit note for the remaining days of the current period, and arrears-billed subscriptions are invoiced up to the transition date. When transitioning, subscriptionTransitions must list every active subscription on this customer as explicit acknowledgement that they will be migrated.

Billing relationship. Change to parent_pays together with parentCustomerId to route billing to the parent.

Consolidation mode (parent customers only). Send null to clear.

Day of month (1-28) for the parent consolidated invoice. Send null to clear.

Whether to attach a zip of per-child detail PDFs when sending consolidated invoices

Whether this customer's portal users may fill in their own billing details (VAT number, street, postal code, city), both on the portal's Company settings page and during checkout, instead of only confirming a read-only copy of the record. Country and customer type stay operator-owned either way, which is what keeps them inside the VAT regime the operator assigned.

Parent single invoice PDF template override. Send null to clear.

Subscription transitions — required when changing parentCustomerId, billingRelationship, or consolidationMode on a customer with active subscriptions, and when changing billingDay or consolidationMode on a single_invoice parent (then it must cover every child customer's subscriptions). Lists every active subscription as explicit acknowledgement that each one is migrated to the new billing arrangement with a clean cut at today's date. Entries for subscriptions that need no transition are accepted and ignored.

Key-value metadata. When provided, REPLACES the customer metadata wholesale — send the complete desired map; an empty object clears all entries. Omit the field to leave metadata unchanged. At most 50 entries; keys up to 128 characters, string values up to 500 characters.

The unique identifier of the customer

Customer number

DELETED when the customer had no history and is gone. DEACTIVATED when bookings, invoices or subscriptions kept it: it stays readable with isActive: false, so its history is intact.

Unique identifier of the dimension value

Display name of the dimension value

Parent dimension value ID for hierarchical structures. Null for root-level values. Use this to create nested structures like "Sales > Europe > Denmark".

Child dimension values (nested structure). Only populated in list responses.

Unique identifier of the dimension category

Display name of the dimension category

When true, only one value from this dimension can be assigned to a journal entry (mutually exclusive). When false, multiple values can be assigned (additive tags). Example: A "Department" dimension is typically unique (one department per entry), while a "Tags" dimension might allow multiple values.

Available dimension values within this category, organized as a hierarchical tree. Root values have parentId as null, nested values reference their parent.

IDs of the accounts that require this dimension: every journal entry line posting to one of them must carry a value from this dimension, or the entry is refused with JOURNAL_TAG_REQUIRED_DIMENSION_MISSING. Empty when no account requires it.

Unique identifier of the dimension value

Name of the value

Parent value id for hierarchical dimensions. Absent on root values. Rebuild the tree client-side.

Dimension values as a FLAT page ordered by name; use parentId to rebuild hierarchy

Total number of values in this dimension

Current page number (1-indexed)

Maximum number of items per page

Total number of pages available

The dimension value this share is allocated to

Name of the target dimension value

Share of the amount, in percent with up to six decimal places. All shares sum to exactly 100.

Display order of the allocation row (0-based)

Unique identifier of the distribution key

Display name

True for a one-document split created inline on a draft. Ad-hoc keys are excluded from listings unless includeAdHoc=true, and their lifecycle is system-managed.

False once the key is archived (a posted ad-hoc key archives automatically)

The allocations, in display order. Percentages sum to exactly 100.

Distribution keys, ordered by name

Total number of keys matching the query

Current page number (1-indexed)

Maximum number of items per page

Total number of pages available

The dimension value to allocate to. Must belong to this dimension.

Share in percent, up to six decimal places. All allocations must sum to exactly 100.

Display order of the allocation row (0-based)

Allocations that must sum to exactly 100%. Between 2 and 100 entries.

Display name. Required for a reusable key; omit it on an ad-hoc key, which names itself from its allocations server-side.

True to create a one-document split. Ad-hoc keys are hidden from listings by default and their lifecycle is system-managed: archived when the document they are applied to posts, deleted with the draft that owned them, and swept if left orphaned. Reference the returned id from a draft’s tagIds to apply the split.

Display name for the dimension category. Must be unique within your company. Choose a descriptive name that clearly indicates the categorization purpose.

Whether only one value from this dimension can be assigned to a journal entry. Set to true for mutually exclusive categories (e.g., Department - an entry belongs to exactly one department). Set to false for additive tags (e.g., Tags - an entry can have multiple tags). This constraint is enforced when assigning dimension values to journal entries, and it is fixed once the category is created.

Unique identifier of the created/updated dimension category

Display name of the dimension category

Whether only one value from this dimension can be assigned per journal entry

IDs of the accounts that require this dimension on every line posting to them. Empty when no account requires it.

New display name for the dimension category. Must be unique within your company. Changing the name does not affect existing dimension value assignments.

ID of the dimension category this value belongs to. The category must exist and belong to your company.

Display name for the dimension value. Must be unique within the dimension category. Choose descriptive names that will be clear when selecting values in the UI.

Parent dimension value ID for creating hierarchical structures. Leave null or omit for root-level values. The parent must exist within the same dimension category. Example: Create "Europe" first, then create "Denmark" with parentId set to Europe's ID.

Unique identifier of the created/updated dimension value

Display name of the dimension value

ID of the dimension category this value belongs to

Name of the dimension category this value belongs to

Whether the parent category enforces single selection

Parent dimension value ID, if this is a nested value

New display name for the dimension value. Must be unique within the dimension category. Changing the name does not affect existing journal entry assignments.

New parent dimension value ID. Set to null to move to root level. The parent must exist within the same dimension category and cannot create circular references (e.g., A cannot be parent of B if B is already an ancestor of A).

Filename with extension

Base64-encoded file content. Note: Base64 encoding adds ~33% overhead. Individual files should not exceed 10MB before encoding.

MIME type of the file

Transaction type for this line (debit or credit)

Amount for this line (must be non-negative)

Account ID for this line (UUID). Optional for drafts — empty lines (type + amount with no account) are persisted as placeholders and must be completed in the platform UI before booking. Cannot be a heading or total account when provided.

VAT/Tax code ID for this line (UUID)

Optional per-line memo (max 500 characters). Persisted on the draft line and carried onto the booked ledger transaction when the draft is booked.

Dimension tag IDs to attach to this specific line. Per-line tagIds MUST come from single-select (dimension) categories — multi-select tags belong at the entry-level tagIds instead.

Primary account ID (UUID). Cannot be a heading or total account. For typed entries (supplier_invoice, customer_invoice, etc.), must have appropriate account classification.

Date of the journal entry in YYYY-MM-DD format

Contra account ID (UUID). Optional for drafts — partial drafts (primary line only) are allowed and must be completed in the platform UI before booking. Cannot be a heading or total account.

Entry type determines the journal type and enforces account classification rules. Account classification requirements: supplier_invoice: account=EXPENSE|ASSET, contraAccount=LIABILITY; supplier_payment: account=LIABILITY, contraAccount=ASSET; customer_invoice: account=ASSET, contraAccount=REVENUE; customer_payment: account=ASSET, contraAccount=ASSET; journal: no restrictions. Legacy values "invoice" and "payment" map to supplier types.

Transaction type (debit or credit)

Description of the journal entry

Reference number or identifier

Customer ID (UUID) for customer-related entries

Supplier ID (UUID). Required for supplier_invoice / supplier_payment entry types, and for any posting that touches an accounts-payable control account.

Tag/Dimension IDs to attach to the journal entry

VAT/Tax code ID (UUID). Applied to the primary account unless split entries are used.

File attachments (base64-encoded). Maximum 10 attachments per entry. Total request size limit is 15MB.

The draft amount in the currency it is entered in, the one originalCurrency names (zero or more). Ignored when splitEntries is sent: the draft then stores the sum of the debit lines. Required unless the deprecated amount is sent instead.

ISO 4217 alpha-3 code of the currency the draft is entered in. Omitted under both names, the draft is in your company base currency.

Split entry lines for multi-account drafts. Each line may omit accountId to act as a placeholder; the draft is persisted with NULL on those lines and the user completes them in the platform UI. Booking still requires every line to carry a real account and the entry to balance.

Your own system's id for this draft. Carried onto the booked journal entry. Not unique — several drafts/entries may share one id. Filter the list endpoint by externalSystemId.

Array of draft journal entries to create (1-100 entries per batch)

Which side of the entry this line sits on

Account this line posts to. Absent on a placeholder line — one persisted with an amount and a side but no account yet, which must be completed before the draft can be booked.

Amount for this line in the draft's own currency, the one originalCurrency names. Absent on a line persisted without one, which must be completed before the draft can be booked — reported as absent rather than as 0, so an unfinished line is never mistaken for a zero-value one.

VAT/Tax code ID

Per-line memo

Tag/Dimension IDs attached to this line. Per-line dimensions override the entry-level tagIds on this specific ledger transaction.

Account ID

Transaction type (debit or credit)

Amount for this line in transaction currency

VAT/Tax code ID

Per-line memo

Tag/Dimension IDs attached to this line. Per-line dimensions override the entry-level tagIds on this specific ledger transaction.

Draft journal entry ID

Date in YYYY-MM-DD format

How large this draft is, in your company base currency — the one your company reports in. A draft entered as EUR 1,000 by a company reporting in DKK is 7450 here.

Do not display this number beside originalCurrency. That field names the currency the draft was entered in (EUR in the example), while this number is in DKK. originalAmount is the figure that belongs beside originalCurrency.

Reads 0 on a draft that holds no figure in this currency. The minBaseCurrencyAmount and maxBaseCurrencyAmount list filters run on this field, so a draft reading 0 here is excluded whenever either filter is applied.

How large this draft is, in the currency it was entered in — the currency originalCurrency names, and the one lines[].amount uses. A draft entered as EUR 1,000 is 1000 here, whatever your company reports in.

This is the figure to display beside originalCurrency. baseCurrencyAmount is the same draft in your company base currency: on that EUR draft this field reads 1000 and baseCurrencyAmount reads 7450. Reads 0 on a draft that carries no amount yet.

The currency this draft was entered in — EUR for a supplier invoice received in EUR. originalAmount and lines[].amount are in this currency; baseCurrencyAmount is in your company base currency, which is this one only when the draft was entered in it.

Journal type

ID of the journal category the draft is in. Set it with journalCategoryId on the v2 draft create and on PATCH /v2/draft-journal-entries/{id}. Booking the draft keeps it on the journal entry. List the categories with GET /v1/journal-categories. Null when the draft has no category.

Every line of the draft. Always present, an empty array included, so a client never has to distinguish absent from empty. The name matches the lines the v2 draft endpoints take, so a draft reads back through the field it was written with.

Always "DRAFT" for draft journal entries

Creation timestamp

Last update timestamp

Document date (date on the invoice/voucher). Null when not set.

Due date stated on the draft (YYYY-MM-DD). Null when none was stated; booking a customer or supplier invoice then calculates one from the payment term.

What one unit of originalCurrency is worth in your company base currency. 7.45 on a EUR draft of a company reporting in DKK means 1 EUR buys 7.45 DKK.

This is the rate the draft is converted at, not a factor between the two amounts on this response. baseCurrencyAmount is built from the draft lines rather than from originalAmount, so multiplying originalAmount by this rate does not reliably reproduce it — on a draft whose sides disagree the two figures differ with no rate involved at all. A draft already entered in your own currency carries 1. Null only while a foreign-currency draft has no rate yet — booking gives it one.

Date the originalCurrencyToBaseCurrencyExchangeRate was captured for. Null whenever that rate is.

Description

Reference number

Your own system's id for this draft, when set. Not unique. null when unset or cleared.

Transaction type (debit or credit)

Primary account ID

Contra account ID

Customer ID

Supplier ID

VAT/Tax code ID

Tag/Dimension IDs

Document IDs attached to the draft

Number of draft entries successfully created

Details of all created draft journal entries

List of draft journal entries

Total number of matching drafts

Items per page

Cursor for the next page; pass it as cursor. null on the last page, and on every page of a sort that cannot page by cursor — hasMore then says whether another page follows by page number.

Whether more rows follow this page.

Account this line posts to

Which side of the entry this line sits on

Amount posted to the account, in that account's own currency (accountCurrency). For an account operating in the company base currency this equals functionalAmount.

The account's operating currency — the currency accountAmount is denominated in.

Amount posted, converted to the company's base currency. This is the figure to sum when comparing or aggregating across accounts — summing accountAmount across accounts of different currencies would add unlike units.

True when this line is VAT that the platform derived from another line, rather than a line you posted. Derived VAT lines are included so the lines of an entry balance; vatSourceLineIndex points at the line they came from.

This line's amount in the entry's originalCurrency — the third currency layer, alongside accountAmount (the account currency) and functionalAmount (the company base). On an entry posted in the base currency all three agree. Do not sum this to get the entry total. It is absent on a derived VAT line — the platform computes VAT in base currency and stores no document figure for it — so the sum falls short by the VAT whenever a line is VAT-coded. Use the entry-level originalAmount for the document total, or sum functionalAmount for the base-currency total. Also absent on historical lines that stored no document amount.

Index into this same lines array of the line this VAT was derived from. Set only when isVatLine is true, and omitted in the rare case where the source line is not part of this entry.

VAT/Tax code in effect for this line. A VAT line derived within this entry stores no code of its own — the code belongs to the line it was derived from — so this reports that source line's code. A VAT line derived from a line in a different entry carries its own code and is reported directly. Absent on a line with no VAT.

Per-line memo, separate from the entry-level description

Dimension tag IDs attached to this specific line

The account the note is about.

What the note says. Each value has an en + da translation in the web app.

Unique identifier of the created journal entry

Entry number assigned to the journal entry

Date of the journal entry

Amount of the line accountId names, in that line's account currency (currency). On a two-line entry this is the entry total. On a wider entry it is one line of several — sum lines[].functionalAmount on either side for the total.

Currency amount is denominated in — the operating currency of that first line's account.

Journal type

ID of the journal category the entry is in. A draft booked with a category keeps it. List the categories with GET /v1/journal-categories. Null when the entry has no category.

Transaction type

Status of the journal entry

The id of the entry that reverses this one, or null when no reversal made in LedgerBee points at it. A reversed entry keeps its status, so this field is what says it no longer counts: it and its reversal cancel each other out. A reversal imported from e-conomic cancels its entry through opposite amounts and is not linked, so the entry it cancels reads null here.

On a reversal, the id of the entry it reverses; null on every other entry. The entry named here names this one in its reversedByEntryId.

One non-VAT line of the entry, paired with contraAccountId as a two-line summary. On a two-line entry the pair describes the whole entry. On a wider one it describes two of its lines and nothing about the rest — read lines for the full picture. Which two are picked is not part of this contract and differs by endpoint (a read takes them in posting order; the draft-booking response takes a debit and a credit), so do not infer a line's position from it.

Timestamp when the entry was created

Document date (date on the invoice/voucher). Null when the entry was booked without one; its VAT period then follows date.

Due date of the customer or supplier invoice this entry books (YYYY-MM-DD). Null on every other entry type, on a credit note booked without one, and on an invoice posted through this API without a reference (no invoice is registered for it).

What you posted, in the currency you posted it in — the document figure, before any conversion. Distinct from amount, which is denominated in the ACCOUNT currency (currency): a EUR entry against DKK accounts reports originalAmount: 200 / originalCurrency: "EUR" and amount: 1492.24 / currency: "DKK". Null on historical entries that stored no document amount.

The currency the entry was posted in: what originalAmount is denominated in, and what originalCurrencyToBaseCurrencyExchangeRate converts FROM. Present independently of originalAmount — an entry can name a currency and store no document amount, which is the historical shape, and the currency still says what its rate converts from. Null only on an entry that names no currency at all.

Rate converting originalCurrency to the company base currency — 7.45 on a EUR entry of a DKK-based company means 1 EUR = 7.45 DKK, so originalAmount * originalCurrencyToBaseCurrencyExchangeRate is the base-currency total that lines[].functionalAmount sums to. Reported whether you supplied it on create or the platform resolved it, which is what lets you compute the difference against the rate your own settlement later used. 1 on an entry posted in the base currency, since that is the conversion that was applied and stored. Null only on historical entries that stored no rate at all.