Jurnal Transaction

Overview

Jurnal Transaction endpoint returns journal transaction records for the requested date range. Each transaction includes its transaction ID, transaction number, transaction date, total debit, total credit, and the user who created the record. The response also provides detailed account entries associated with each transaction.

Each detail record contains account information, reference number, description, debit and credit amounts, key rate, creator, and transaction type. This endpoint is commonly used to review accounting jurnal entries and track debit and credit transactions within a specified period.

Request Endpoint

• Method: POST
• Path: {{base_url}}/api/reports/jurnal-transaction

Payload Construction and Schema Definition

The request payload is submitted as form-data fields.

Request Body Fields

Field	Type	Required	Description
start_date	string (date)	Yes	Start date (YYYY-MM-DD) for the report.
end_date	string (date)	Yes	End date (YYYY-MM-DD) for the report.
account_id	string	No	Account filter. Use all for all accounts.

Response Body Fields

Field	Type	Always present	Description
error	boolean	Yes	Indicates whether the request failed. false means success.
status	string	Yes	Status string. On success the example returns "ok".
message	string	Yes	Human-readable message. Often empty on success.
data	array of object	Yes (on success)	Array of jurnal-transaction object.

Response data Fields

Field	Type	Description	Example
transaction_id	string	Unique identifier of the jurnal transaction.	INV/2025-07-01/gusadivillas-20250103-...
transaction_no	string	Jurnal transaction number.	INV/2025-07-01/gusadivillas-20250103-...
transaction_date	string	Date of the jurnal transaction.	2025-07-01
total_debit	number	Total debit amount of the transaction.	10000
total_credit	number	Total credit amount of the transaction.	10000
created_by	string	User who created the transaction.	gusadi
detail	array of object	List of account entries associated with the transaction (see below).	[ ... ]

Response data.detail Fields

Field	Type	Description	Example
account_id	string	Account identifier associated with the transaction.	1.1.04.01
account_name	string	Account code and account name.	1.1.04.01 - Saleable Supplies
reference_no	string	Reference number of the transaction entry.	gusadivillas-20250103-...
description	string	Description of the transaction entry.	Nasi Goreng
debit	number	Debit amount of the account entry.	0
credit	number	Credit amount of the account entry.	10000
key_rate	number	Rate value associated with the transaction entry.	0
created_by	string	User who created the transaction entry.	gusadi
transaction_type	string	Type of transaction associated with the account entry.	POS

Expected System Responses

The system responds with HTTP 200 OK.

{
    "error": false,
    "status": "ok",
    "message": "",
    "data": [
        {
            "transaction_id": "INV/2025-07-01/gusadivillas-20250103",
            "transaction_no": "INV/2025-07-01/gusadivillas-20250103",
            "transaction_date": "2025-07-01",
            "total_debit": 10000,
            "total_credit": 10000,
            "created_by": "gusadi",
            "detail": [
                {
                    "account_id": "1.1.04.01",
                    "account_name": "1.1.04.01 - Saleable Supplies",
                    "reference_no": "gusadivillas-20250103",
                    "description": "Nasi Goreng",
                    "debit": 0,
                    "credit": 10000,
                    "key_rate": 0,
                    "created_by": "gusadi",
                    "transaction_type": "POS"
                }
            ]
        }
    ]
}