Draft Journal Entries

Number of draft entries successfully created

Details of all created draft journal entries

List of draft journal entries

Total number of matching drafts

Current page number

Items per page

Total number of pages

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 together with currency. That field names the currency the draft was entered in (EUR in the example), while this number is in DKK, so the pair reads as EUR 7,450 — about seven times what the draft is actually for. originalAmount is the figure that belongs beside currency.

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

The deprecated v1 create takes a request field of the same name carrying the figure the draft is entered in, so a EUR draft sent as amount: 1000 is returned with amount: 7450 — the request field and this one are in different currencies under one name.

How large this draft is, in the currency it was entered in — the currency currency 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 currency. amount is the same draft in your company base currency: on that EUR draft this field reads 1000 and amount 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. This is not the currency amount is in; originalAmount is the figure in this currency.

Journal type

Every line of the draft — the field to read. 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 v2 draft reads back through the field it was written with. The deprecated v1 create still takes splitEntries, so a v1 client sends these lines back under that name.

Always "DRAFT" for draft journal entries

Creation timestamp

Last update timestamp

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

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

What one unit of currency 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. amount 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 exchangeRate was captured for. Null whenever exchangeRate is.

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 together with currency. That field names the currency the draft was entered in (EUR in the example), while this number is in DKK, so the pair reads as EUR 7,450 — about seven times what the draft is actually for. originalAmount is the figure that belongs beside currency.

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

The deprecated v1 create takes a request field of the same name carrying the figure the draft is entered in, so a EUR draft sent as amount: 1000 is returned with amount: 7450 — the request field and this one are in different currencies under one name.

How large this draft is, in the currency it was entered in — the currency currency 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 currency. amount is the same draft in your company base currency: on that EUR draft this field reads 1000 and amount 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. This is not the currency amount is in; originalAmount is the figure in this currency.

Journal type

Every line of the draft — the field to read. 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 v2 draft reads back through the field it was written with. The deprecated v1 create still takes splitEntries, so a v1 client sends these lines back under that name.

Always "DRAFT" for draft journal entries

Creation timestamp

Last update timestamp

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

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

What one unit of currency 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. amount 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 exchangeRate was captured for. Null whenever exchangeRate is.

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

Transaction type

Status of the journal entry

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 for legacy entries.

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 exchangeRate 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 * exchangeRate 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.

Date the exchangeRate was captured for. Null whenever exchangeRate is.

Description of the journal entry

Reference number

Your own system's id for this entry, when set. Not unique — several entries may share one id.

The other half of the accountId pair, when the entry has a second non-VAT line. Same caveat: it is one line, not a summary of every line other than accountId.

Every line of the entry, including VAT lines the platform derived. This is the complete picture: accountId, contraAccountId, amount, currency and vatCodeId above all describe one line, or two, and nothing about the rest. Debits and credits balance across the array on functionalAmount. The order is stable for a given entry — normally the order the lines were posted in — but match lines by account rather than by position, and use vatSourceLineIndex to link a VAT line to its source.

Customer ID if applicable

Supplier ID if applicable

VAT/Tax code on the line accountId names, if it has one. Lines can carry different codes — read lines[].vatCodeId for the per-line codes.

Tag IDs attached to the entry as a whole. Per-line dimensions are on lines[].tagIds.

Document IDs attached to the entry