← All articles

·6 min read

Coretax Taxpayer Ledger Reconciliation: How SMEs Find and Fix Misallocated Tax Payments

Paying your taxes every month is not the same as having them recorded correctly. This guide gives SME owners and their admin a simple monthly routine to check the Coretax taxpayer ledger and fix wrong payments before they turn into penalty notices.

  • coretax
  • taxpayer ledger
  • pemindahbukuan
  • deposit pajak
  • tax payments
  • tax compliance
  • reconciliation
  • sme
Coretax Taxpayer Ledger Reconciliation: How SMEs Find and Fix Misallocated Tax Payments

Most SME owners we talk to treat taxes as a payment task: generate the billing code, pay it, save the receipt, done. The problem is that a payment can reach the state treasury and still be recorded against the wrong tax type, the wrong period or even the wrong taxpayer ID. Nothing warns you when it happens. Months later a tax bill (STP) arrives with interest for a liability you are sure you paid. A simple monthly Coretax taxpayer ledger reconciliation catches these mistakes while they are still cheap and easy to fix.

This post explains what the ledger shows, which mistakes to look for, a routine your admin or accountant can follow in under an hour, and how to correct problems with Pemindahbukuan, Deposit Pajak or an amended return.

What the Coretax taxpayer ledger actually shows

Since Coretax went live in January 2025, every taxpayer has a Buku Besar Wajib Pajak (taxpayer ledger). Think of it as a bank statement between your company and the Directorate General of Taxes (DJP). It records two sides:

  • Liabilities: amounts you owe, created when you file a return (SPT) or when the DJP issues a tax bill (STP) or assessment (SKP).
  • Payments and credits: every payment identified by its NTPN (the state receipt number on your payment proof), plus any balance in your Deposit Pajak.

For each tax type and period, the ledger shows whether the liability is fully paid, underpaid or overpaid. Under the old system you rarely saw how the DJP matched your payments. Coretax makes it visible, which is good news only if somebody actually looks.

The mistakes that hide in the ledger

These are the patterns we see most often in small companies. None of them are dramatic, which is exactly why they go unnoticed.

Wrong tax type

The admin creates a billing code with the wrong tax account and payment type code (KAP/KJS), for example paying PPh 23 withholding as PPh 21. The money arrives, but one tax looks overpaid and the other looks unpaid.

Wrong period

March payroll tax is paid with the period set to February. February now shows an overpayment and March shows an outstanding balance, even though the total is correct.

Double payment or overpayment

A payment seems to fail at the bank, so the admin pays again with a new billing code. Both go through. Or the amount was rounded up. The extra money sits in the ledger doing nothing.

Liability without a matching payment

The return was filed but the payment was forgotten, or it was paid under another ID, such as a branch or the owner's personal NIK-based tax number. The ledger shows an open debt that will eventually become an STP.

A monthly Coretax taxpayer ledger reconciliation routine

Monthly taxes are generally due by the 15th and monthly returns by the 20th of the following month. That makes the 21st to the 25th a good window: everything for the previous month should already be in the ledger.

  1. Collect your own records. Bank statements for the tax account, payment proofs (BPN) with NTPN numbers, and the amounts due according to the returns you filed.
  2. Open the ledger in Coretax. Filter by the period you are checking. Menu names have changed a few times since launch, so ask your accountant where to find it if you cannot see it.
  3. Match line by line. For every payment, check the NTPN, amount, tax type, period and taxpayer ID against the ledger.
  4. Check the balance per tax type. Each liability should show as settled. Anything showing underpaid or overpaid gets flagged.
  5. Write down every difference and decide on a fix (see the next section). Do not leave it for next month.

A simple spreadsheet is enough. Use these columns: tax type, period, amount due per return, amount paid, payment date, NTPN, ledger status and notes. For a small company with four to eight tax payments a month, this takes 30 to 60 minutes once the habit is set. The first month takes longer because you will probably find older issues.

Example: a small catering company in Surabaya paid Rp 4,200,000 PPh 21 for March but selected February as the period. The ledger showed Rp 4.2 million overpaid for February and Rp 4.2 million outstanding for March. Caught in April, this needs one correction request. Caught a year later, it arrives as an STP with interest, and fixing it means letters, a visit to the tax office and an accountant's time.

Fixing mismatches: Pemindahbukuan, Deposit Pajak or an amended return

Pemindahbukuan (Pbk)

Pemindahbukuan is a request to move a payment you already made to the correct tax type, period or taxpayer ID. You submit it in Coretax using the NTPN of the original payment. Once the DJP approves it, you receive proof of the transfer and the ledger is updated. In general the corrected payment keeps its original payment date, so it does not count as late as long as the original payment was on time. One important limit: if the payment has already been credited in a return, you usually need to amend that return first.

Deposit Pajak

Deposit Pajak is a balance in your ledger that can later be used to pay any tax. Overpayments and double payments can be moved into it through Pemindahbukuan instead of sitting stranded under the wrong code. Some companies also pay into the deposit in advance and let Coretax use it when returns are filed. That is convenient, but you still need to check the ledger to confirm the balance was applied to the right liabilities.

Amended return (pembetulan SPT)

If the payment was right but the return was wrong, such as a mistyped amount, the fix is to amend the return rather than move money.

When to bring in a tax consultant: large amounts, periods older than a year, an STP that has already been issued, or payments made before the move to Coretax that were not migrated correctly. These cases have more rules and deadlines, and a mistake in the correction can make things worse.

Making the routine stick

The routine fails when it depends on one person remembering it. Put it in a shared calendar with a fixed date, give one person responsibility and have the owner glance at the summary: how many items matched and how many are open. Keep every NTPN and approval proof in one shared folder named by period so you can answer any question from the tax office in minutes.

Start this month: pick the last three months, match them against the ledger and see what turns up. If you would rather not do it by hand every month, CodeWorks can build a simple internal tool that pulls your bank and payment data together and flags differences automatically. Contact us for a short call and we will tell you honestly whether a tool is worth it for your volume or whether a good spreadsheet is enough.