ePalkat API: journalentries

JournalEntry API Method (journalentry)

The JournalEntry (journalentry) method returns accounting journal entry rows from ePalkat payroll.
The method supports filtering by payroll period (periodnumber), date range (startdate/enddate), split logic (split parameters), and pagination (maxrecords, skiprecords).

Authentication

• Basic Authentication required

• Header:
  Authorization: Basic base64(username:password)

• Typical headers:

  • Accept: application/json

  • Content-Type: application/json (POST)

Endpoints

hree calling methods:

• POST JSON:
  https://<host>:<port>/journalentry

• GET JSON:
  https://<host>:<port>/journalentry?parameters

• REST GET JSON (reports):
  https://<host>:<port>/reports/journalentry?parameters

Note: The examples use lowercase /journalentry.
Your actual host, port, or path may differ — these are sample endpoints.

Request Parameters

All parameters are optional unless stated otherwise.

• periodnumber (int) — Payroll period number.
  Recommended primary filter (typically required in reporting scenarios).

• OR:

• startdate (string[20]) — Start date filter.
  Format depends on environment (typically ISO-style).

• enddate (string[20]) — End date filter.

Split Parameters (advanced)

These control how accounting rows are grouped or split.
Supported values depend on system configuration.

• costcentersplit (string[20]) — Cost center split logic

• projectsplit (string[20]) — Project split logic

• dimension3split (string[20]) — Dimension 3 split logic

• dimension4split (string[20]) — Dimension 4 split logic

• dimension5split (string[20]) — Dimension 5 split logic

• employeesplit (string[20]) — Employee-based split logic

Filtering Parameters (Parameters as they are used in system User Interface)

• payrollgroup (string) — Payroll group filter (max 120 chars)

• firstemployee (string) — First employee identifier (range start, max 20 chars)

• lastemployee (string) — Last employee identifier (range end, max 20 chars)

• project (string) — Project filter (max 120 chars)

• healthinsurancepercent (string) — Health insurance percentage override (max 20 chars)

• sortorder (string) — Sorting order (max 20 chars)

  • 1 — Account
    Sort by accounting account number

  • 2 — Cost center
    Sort by cost center

  • 3 — Project
    Sort by project

  • 4 — Employee
    Sort by employee number

  • 5 — Group
    Sort by payroll group

Pagination

• maxrecords (int) — Maximum number of rows returned

• skiprecords (int) — Number of rows skipped (offset)

Response Structure

A successful response contains a top-level object journalentry_response, including:

• journalentry — Array of journal entry rows

• skippedrecords — Number of skipped rows

• resultcomplete —

  • 1 = all results returned

  • 0 = more results available

In error scenarios, additional error fields may be included (see below).

JournalEntry Fields (journalentry)

Each journalentry[] item may contain the following fields:

• id (string) — Record ID

• sid (string) — Internal identifier (system-specific)

• companyid (int) — Company identifier

• accountnumber (string) — Account number

• accountname (string) — Account name

• amount (int) — Entry amount (signed value)

• creditamount (int) — Credit amount

• debetamount (int) — Debit amount

• year (int) — Fiscal year

• period (int) — Fiscal period

• paytype (string) — Payroll type identifier (system-specific)

• employee (int) — Employee number

• description (string) — Entry description

• vouchertitle (string) — Voucher title

• costunitstring (string) — Cost allocation string (environment-specific)

• dimensions (string) — Dimension structure (format depends on setup)

• costcentername (string) — Cost center name (if available)

• sorting1 (string) — Sorting field 1 (reporting use)

• sorting2 (string) — Sorting field 2 (reporting use)

• vatcode (string) — VAT code

• vatamount (int) — VAT amount

• vatrate (int) — VAT rate

• ---

• Error Fields (if present)

• If the API returns an error, the response may include:

• ErrorNumber (int) — Error code

• ErrorPosition (string[255]) — Error location or processing stage

• ErrorRecordID (string[255]) — Related record ID (if available)

• ErrorDescription (string[255]) — Error description

• ErrorRecomendation (string[255]) — Suggested resolution

• ---

• Usage Tips

• Always start with a periodnumber filter and refine with date filters if needed.

• Use pagination (maxrecords + skiprecords) for large datasets and monitor resultcomplete.

• Supported values for split parameters depend on implementation and configuration.
  If not documented in your environment, confirm them with your system provider or integration settings.r