Scheduled Processing

CBS performs background processing that can change account balances, interest records, account status, loan information, and asset values. Operators review the results through account details, transaction history, journals, and reports.

This chapter explains those effects and how to verify them. The operations team manages the processing schedule and any required recovery. Confirm the applicable processing window, holiday treatment, and period cutoff with that team before reconciling the results.

Before Reviewing a Processing Period#

Confirm the business date or period, the affected product/account population, and the expected result with the bank's operations team. Make sure you are comparing the same office scope and dates in each screen or report.

An interest accrual, an interest payment, a tax deduction, and a transfer to a settlement account represent different events. Their dates and amounts need not appear as one combined transaction. Check the relevant event and account before concluding that an amount is missing or duplicated.

Deposit and Savings Processing#

The result depends on the product, account, and bank configuration. Do not use a rate, inactivity duration, tax percentage, or execution time from an example as a universal CBS default.

Verify Interest, Maturity, or Rollover#

1. Open the account and confirm its product, status, relevant dates, and payment or rollover instructions.
2. Review the account's transaction history for the expected interest, tax, transfer, or settlement event.
3. Where a receiving account is involved, review that account's corresponding entry as well.
4. Generate the relevant report: deposit interest accrual, interest due/payment, deposit maturity, placement, or disbursement, according to the event being checked.
5. Compare account and report references with the accounting entries for the same period.
6. Record any missing, unexpected, or duplicate-looking result before asking the operations/support team to investigate.

Do not initiate a manual settlement simply because a scheduled result is not yet visible. First establish whether the original process is pending, completed, or failed, and whether another office or period was selected in the report.

Dormant Savings Accounts#

Dormancy detection and dormant charging are separate processes. Becoming dormant is a status change; a subsequent charge or closure is an additional event with its own effect on the balance.

A dormant account can have later fee or closure activity. Review its recorded balance, applicable fees, linked facilities, and status history before deciding whether reactivation or another account-servicing action is appropriate. The current balance alone does not explain an earlier charge or closure.

Review a Dormant Account#

1. Find the account and confirm whether its current status is dormant, active, or closed.
2. Review the status history and transaction history to distinguish the dormancy date from later charges or closure.
3. Compare the account with Laporan Rekening Dormant for the relevant scope.
4. If the customer needs the account reactivated, follow the reactivation and authorization workflow in Deposit Accounts. Viewing or editing the customer record does not reactivate the account.
5. After authorization, verify the account status and any subsequent transaction eligibility.

If a charge appears unexpected, retain its date, amount, account reference, and associated history. The investigation should include the configured fee and balance used by the process, rather than only the customer's current balance.

Loan Processing#

Loan processing covers overdue penalties, collectibility and accrual, accrual-journal posting, accrual reversal, and automatic debit where used by the bank.

Authorized administrators can review Konfigurasi Autodebit in Pengaturan Pinjaman; see Loan Products and Origination. The setting records whether automatic debit is enabled. Verify actual collections through the account histories below.

Enlarge Screenshot

The displayed settings are an environment example. An enabled switch does not confirm that a collection has completed.

The loan's Rekening Angsuran is the savings account used to fund installment repayment. It is distinct from Rekening Pencairan, the account designated to receive disbursement. Both regular repayment and scheduled automatic debit use the configured installment debit account. Depositing money into that account makes funds available; it does not by itself prove that a loan repayment has been collected. Verify the resulting debit and installment history together.

Verify Penalties, Collectibility, and Accrual#

1. Open the active loan and review its installment schedule, due dates, repayment history, and unpaid amounts.
2. Check the current penalty and collectibility information against the effective account/product settings and recorded repayments.
3. Compare the account with Laporan NPL, Tunggakan, dan Kolektibilitas, Laporan Nominatif Pinjaman, and Laporan Akrual Kredit as relevant.
4. Trace any related journal entry and its accounting date.
5. Escalate a discrepancy with the loan reference, installment number, period, repayment reference, and observed result.

Do not replace a missing scheduled outcome with a manual financial adjustment before checking whether processing is still outstanding. A repayment entered after the relevant cutoff can also require the operations team to establish which processing period it affects.

Verify an Automatic-Debit Repayment#

1. Open the loan and identify its Rekening Angsuran and installments due for collection.
2. Review the installment history to establish whether the expected repayment has been recorded.
3. Review the linked savings account for the corresponding debit. Match the amount and reference with the repayment result.
4. Check the remaining installment balance and any penalty amount after collection.
5. If either side is missing or the amounts differ, record the references and contact the operations/support team before taking an alternative payment.

Sufficient funds in the installment account do not establish that collection has completed. Resolving an uncertain automatic debit before taking another payment helps prevent duplicate collection. For operator-initiated payments and their outcomes, see Loan Servicing and Problem Loans.

Fixed-Asset Depreciation#

Depreciation processing considers active inventory, elapsed months since the applicable start/latest depreciation date, and the recorded residual-value floor. It creates depreciation records and accounting entries, and can mark an asset fully depreciated when the floor is reached.

A processing result can cover multiple elapsed months. Review its period and total amount together rather than assuming that every month appears as a separate history row. Use Fixed Assets for the depreciation review procedure.

For a period-end review, compare the asset register, depreciation report, asset history, and journals. Exact amounts should be reconciled to the approved depreciation schedule before the bank relies on the output for closing.

Reconcile a Period#

1. Confirm the period and list of processes expected to have completed with the operations team.
2. Review exceptions in the affected account or inventory populations.
3. Generate the relevant operational reports after the expected processing window.
4. Review associated journals and their approval/posting state. Journal posting has a separate operator workflow described in Accounting.
5. Compare the report totals, account histories, and ledger totals using the same date and office scope.
6. Record unresolved differences and their owner before the bank's period-close decision.

A useful escalation includes the process concerned, business date/period, account or inventory reference, expected and observed result, report code, journal/voucher reference, and the time of the check. Share customer details only through the bank's authorized support channel. The operations/support team can establish whether processing is outstanding, completed, or requires recovery.

Related: Reports and Operational History.