Reports and Operational History

Use Laporan to request reports, monitor their generation, and download completed files. Reports are organized by the operational area they describe. Most report pages retain a history of generation requests, so requesting a report and downloading a finished report are separate actions.

The navigation groups are Laporan Deposit, Laporan Pinjaman, Laporan Customer Service, Laporan Akunting, and Laporan Administratif. Teller reports are included under Laporan Deposit; accrual and fixed-asset reports appear under Laporan Akunting.

Enlarge Screenshot

Scroll through the catalogue to reach further report groups.

Use account and transaction histories to investigate individual events, and reports to review a defined population or period. A request log can help support teams trace an application request, but it should not be treated as the authoritative customer ledger or a substitute for a transaction's authorization history.

Before You Begin#

Confirm the reporting period, office/cash-office scope, account or product filters, and required format. Access and available reports depend on your role and the institution's configuration.

Choose the same dates and scope when comparing reports. A month-end balance, a range of transactions, and the current status of accounts answer different questions even when they refer to the same customers.

Generate a Report#

1. Open the appropriate report under Laporan.
2. Choose Generate to open Generate Laporan.
3. Complete the filters shown by that report. Depending on the report, these may include a date, date range, month, office, cash office, customer, product, teller, COA, or asset type. Do not assume that filters from one report are available on another.
4. Select Format from the options offered. Standard dialogs can offer PDF - Landscape, PDF - Portrait, XLSX, and CSV; some reports provide a narrower list.
5. Choose Generate and review any validation message.
6. Return to the report list and locate the request using its report code, requested time, status, or format.
7. Wait for the request to finish, then download the completed output.

Generation creates a report request; it does not establish that a usable file already exists. If the list has not updated, refresh or reopen the report list and inspect the request before generating another copy.

Example: Generate a Savings-Balance Report#

Enlarge Screenshot

Laporan Saldo Tabungan: select the office scope and output format before requesting a report.

1. Open Laporan → Laporan Deposit → Laporan Saldo Tabungan and choose Generate.
2. Review Kantor and Kantor Kas, which initially follow the available default office context. Choose the required scope from the options available to you.
3. If you change Kantor, review Kantor Kas again: it resets to Semua Kantor Kas. Selecting Semua Kantor disables the individual cash-office selector.
4. Select PDF - Landscape, XLSX - Landscape, or CSV under Format.
5. Choose Generate to request the report, or Batal to leave without a request.
6. Follow the request's status in the report list and download it when it is ready.

This report dialog has no date or historical “as of” field. Use a report with the appropriate period control when you need a historical reporting date, and confirm its cutoff before comparing totals.

Understand Generation Status#

The list displays Kode Laporan, Nama File, Format, Status, Diminta, Selesai, and download information.

The status filter may use the English terms In Progress, Finished, and Error while the row badge uses Diproses, Berhasil, and Gagal.

Download a Completed Report#

1. Find the request with Berhasil status.
2. Select its download action.
3. In Download Laporan, confirm the selected Report ID and download the file.
4. Open the result and check the title, reporting period, scope, format, and totals before using it.

The download icon is disabled for unfinished or failed requests. If a finished request cannot be downloaded, retain its report code and requested/completed times for support investigation.

Choose the Appropriate Report#

Use this catalogue to find the report that matches your task. Select a format offered by the report's own Generate Laporan dialog.

Additional report pages cover mapped profit/loss data and financial position, other assets and liabilities, immediate liabilities, deferred interest and penalty income, provision amortization, agent fees, and non-core funding. Use the filters and format choices offered by the specific page.

Fixed-Asset Register Period Behavior#

Daftar Aset Tetap, Inventaris dan Aset Tidak Berwujud uses a month selection. Future months are disallowed. The current month is limited to today in WIB; a past month ends on the final day of that month. The report's office and inventory status follow current conditions, so a historical month is not a full historical snapshot of asset placement/status. Use the inventory histories for that investigation.

Configure Report COA Mappings#

Some report pages provide Setting COA. This editor defines the report's row structure and maps those rows to accounting accounts. Changing a report mapping does not change the ledger's chart of accounts.

Before changing a structure, confirm the intended presentation and account mapping with the responsible accounting/reporting owner.

Enlarge Screenshot

Setting COA on Laporan Posisi Keuangan. An empty structure can be started with Tambah COA.

1. Open an applicable report, such as Laporan Posisi Keuangan, and choose Setting COA.
2. Review the hierarchy and the columns LABEL, EKSTERNAL COA, INTERNAL COA, and AKSI.
3. Use Tambah COA to create a parent row, or the + action beside an existing row to add a child beneath it.
4. Enter the required Label. Enter Eksternal COA and select Internal COA according to the approved mapping; the form permits these account fields to be empty.
5. Choose Tambah to add the row to the editor. Repeat for additional rows, or edit the existing row fields directly.
6. Review the entire affected branch. Removing a parent with its delete action also removes its child rows from the edited structure.
7. Choose Simpan to save the structure and check for Setting COA berhasil disimpan. Row additions and edits are not saved until this step.
8. Generate a new report and reconcile it to the ledger after the mapping is saved.

If a conflict prevents saving, preserve a record of the intended changes, then choose Buang perubahan dan muat ulang to load the current structure. Reconcile and reapply the changes before saving again.

The editor supports one internal COA per row. Setting COA is available only on applicable report pages; it is not shown on Laporan Neraca or the asset-register page.

Inspect Operational Request History#

Laporan Log History provides a dedicated search of application request history.

1. Enter Tanggal Mulai and Tanggal Selesai. The end date cannot be after today or before the start date.
2. Select Requester when narrowing the search to a particular requester.
3. Choose Cari Data.
4. Review the returned rows, including Trace ID, Waktu, Kode User, Nama User, HTTP Verb, Tujuan, URL Path, Response Code, and Traffic Data.
5. If an export is needed, use the page's generation action after searching. When its report is ready, use Download.

Changing the dates or requester invalidates the current search result for generation/download; search again with the new selection. This page automatically updates status while its report is pending. If its last report fails or the file is unavailable, the page prompts you to generate again.

Use a Trace ID when referring a technical problem to support. The request's response code helps locate a failed call, but a successful response alone does not establish a transaction's final accounting or authorization state. Verify that state in the transaction/account record.

Reconcile a Report Discrepancy#

First confirm the date, office, product/account filters, generation time, and format. Then compare the source record's status: an unapproved transaction, an unfinished processing run, or a report generated before a change can explain a difference. For mapped reports, review the applicable COA structure as well.

If the difference remains, record the report code, filters, relevant transaction/account references, expected total, and observed total. Keep the original file as evidence. Avoid altering source transactions merely to make a report total match.

Related: Accounting · Fixed Assets · Scheduled Processing.