Overview

In accounting software, journals are used to record all the financial transactions of a company. Each transaction in a journal is represented by a separate journal entry. These entries are used to create the general ledger, which is then used to create the financial statements of a business.

When a company records all their transactions in a single journal, it can become large and difficult to maintain and track. This is why large companies often use multiple journals (also known as subjournals) to categorize and manage journal entries.

Such journals can be divided into two categories:

  • Special journals: journals used to record specific types of transactions; for example, a purchases journal, a sales journal, or a cash management journal.
  • General journals: journals used to record transactions that fall outside the scope of the special journals.

Multiple journals or subjournals are used in the following Codat integrations:

🚧

When pushing journal entries to an accounting platform that doesn’t support multiple journals (multi-book accounting), the entries will be linked to the platform-generic journal. The Journals data type will only include one object.

Data model

Field

Type

Description

id

string

Journal ID.

journalCode

string

Native journal number or code.

name

string

Journal name.
The maximum length for a journal name is 256 characters. All characters above that number will be truncated.

type

string

The type of the journal.

parentId

string

Parent journal ID.
If the journal is a parent journal, this value is not present.

hasChildren

boolean

If the journal has child journals, this value is true. If it doesn’t, it is false.

createdDate

string
See date

Journal creation date.

status

string

Possible statuses:

  • `Unknown`
  • `Active`
  • `Archived`

modifiedDate

string
See date

The last time Codat modified the record.

sourceModifiedDate

string
See date

The last time the journal was modified on the source platform.

journalRef

Reference type

See journalRef.

Journal reference

Codat uses the journalRef object to link journal entries to the relevant journal in accounting integrations.

This reference enables Codat to push journal entries to the integrations that require the journal to be specified.

Field

Type

Description

id

string

Journal ID.

name

string

Journal name.

Example data

//Journals object
{
    "id": "string", -- journal
    "journalCode": "string", -- number or code for the journal
    "name": "string", -- journal name
    "type": "string", -- journal type
    "parentId": "string", -- journal parent of the journal (if journal is the parent, this would not be mapped)
    "hasChildren": true, -- if a journal has children, the journal is parent of those children journals
    "createdDate": "date",
    "status": "unknown|active|archived",
    "modifiedDate": "datetime",
    "sourceModifiedDate": "datetime"
}
//journalRef object
{
    "id": "string",
    "name": "string"
}


Did this page help you?