Built for the Coretax era

Your books agree with the tax office. Every month.

The tax office already holds your tax invoices, withholding slips, and bank movements before you file. KLOPT compares your books against that data every month and shows you the gap now — not after the letter arrives.

Book a demo Try the interface

Data stored in Indonesia Flat price, any number of users Accounting and tax reports at once

This is KLOPT’s real interface with sample figures. Click the left-hand menu — seven screens are live.

0 checks

Run automatically every month: output VAT, input VAT, service withholding, and payroll tax

0 set of books

Not two systems to reconcile. The accounting and tax reports are read from the same journal

0 stray rounding

Money is never stored as a computer floating-point number. How it rounds comes from the tax rule itself

Rp0–30m

A tax consultant’s monthly fee. That is what we are priced against, not a cheap accounting subscription

What changed

It used to be hard to gather the numbers. Now it is hard to prove they agree.

Your numbers are already with the tax office. What they check is no longer whether your report is complete, but whether it agrees with the data they already hold.

They already have your data

Tax invoices, withholding slips, and bank movements reach Coretax before your return does. Your report becomes a comparison, not new information.

Gaps show up on a screen

A gap used to surface only during a field audit. Now it takes one comparison on a desk.

Checking once a year is too late

A gap found eleven months later means hunting for documents nobody remembers, in files that have moved warehouse.

The four things compared every month

So you do not need tidier accounting software

You need books that know, every day, how far they differ from the tax office’s data — and can explain every rupiah of that difference with a document and a statute. That is what KLOPT does.

See how it works

The core difference

One set of books, two reports. Nothing to reconcile.

Every company really has two versions of profit: the accounting one and the tax one. They genuinely differ, and should. The only question is how that difference is managed.

Nothing is entered twice. A transaction is recorded once. The system decides which report sees it: both, accounting only, or tax only.
Nothing needs matching. Two figures read from the same row cannot disagree. All that is left is explaining the adjustments you meant to make.
Fiscal adjustments are not December work. They attach to the account and the transaction from the start, and the working papers collect themselves through the year.
Change one transaction and both reports change. Immediately. There is no second step to forget.

The full explanation

All from the same journal July 2026

Sale of VAT-able goods Both

Enters the accounting and tax reports identically.

Entertainment expense without the required list Accounting only

Recognised as a cost in the accounts, but cannot reduce tax.

Extra depreciation under the tax rules Tax only

Appears only in the tax calculation, because the method differs.

Deposit interest Accounting only

Already taxed at source, so it is left out of the corporate tax base.

The four rows above come from one set of books. Nothing is typed twice, so nothing can disagree.

How it works

Type it once. The system makes the rest.

One correctly recorded sales invoice immediately produces the journal entry, the e-invoice line, the tax matching line, the receivables ageing, and the audit working paper. Without a single figure retyped.

Record one transaction

Pick the customer, enter the items, set the date. VAT status and payment terms already sit on the customer record, so your staff are never asked a tax question.

The journal entry forms itself

Debits and credits are assembled by the system from the transaction itself, guaranteed to balance, and posted to both the accounting and tax reports.

The tax obligation forms with it

This month’s e-invoice line, output VAT, any withholding exposure, and whether you under- or over-paid this month. All calculated, none typed.

At each month end, the figures are matched

The same four checks a tax auditor uses run automatically. Each gap is matched to an explanation, and anything left over is clearly flagged.

Working papers are ready before they are asked for

When you prepare the annual return, or when a query letter arrives, the file is already complete. Every figure traces back to its original document.

What is inside

Ten modules, one set of books

What normally takes three separate systems — accounting, inventory, and tax — sits in one place.

Sales

Quotes, orders, delivery notes, invoices. A customer’s VAT status lives on their record, so the VAT follows automatically.

Purchasing

Vendor bills arrive with input VAT attached. The system works out which ones are subject to withholding from the transaction type.

Inventory & production

Stock by warehouse, cost of goods, bills of materials, and the value still sitting in production.

Cash & bank

Receive money, pay bills, transfer between accounts, match bank statements, and count physical cash with a printable record.

Fixed assets

One asset, two depreciation calculations: one for the accounts, one for tax. The gap becomes an automatic fiscal adjustment.

Payroll & employee tax

Salaries, allowances, social security, and employee tax. Every figure on a payslip traces back to its component.

General ledger

Journals that cannot be deleted or edited, a chart of accounts with tax treatment, recurring entries, and monthly close.

Financial reports

Balance sheet, P&L, cash flow, worksheet, and notes. The accounting version and the tax version sit side by side.

Tax centre

Automatic monthly matching, fiscal adjustments with their statutes, working papers, and a risk score before you file.

Access & control

16 permissions across 7 roles, approval flows, a record of who changed what, and imports checked row by row.

See inside each module

Tax matching

Checked every month, not every March

The same four checks a tax auditor uses run automatically at each month end. Gaps are matched against explanations in your own data. Whatever is left is written down plainly as unexplained.

Output VAT against revenue in the books
Input VAT against purchases and expenses
Withholding slips against service costs
Employee tax against salary costs

See the details

July 2026 matching results 3 of 4 clean

Output VAT vs revenue Rp83.000.000 Explained

Input VAT vs purchases Rp146.000.000 Rp6.5m left

Withholding vs service costs None Matched

Employee tax vs salary Rp13.500.000 Explained

Rp6,500,000 has no explanation yet. The system does not guess and does not force the numbers to agree. It raises the question now, eleven months before someone else does.

The AI prepares the work — it does not decide the tax

Two marks run through the whole app. Ink for figures a person has approved. Pencil for anything from the AI: grey, dashed, and always erasable.

Always a suggestion

AI output never goes straight into the ledger. It appears as a suggestion awaiting approval, and if rejected leaves no trace at all.

Statutes are looked up, not written

A statutory reference is not a sentence the AI wrote; it is pulled from the rule list in the system. So the AI cannot cite an article that does not exist.

Forbidden from computing tax

This ban lives in the code structure, not just in an internal policy. If anyone calls the AI from a tax calculation, the build fails.

Example AI suggestion — nothing is changed yet

“The Rp6,500,000 input-VAT gap looks like a pattern in three vendor invoices whose invoice date falls in a different month from their booking date. Likely: BILL-2026-0341, BILL-2026-0352, BILL-2026-0377.”

PMK 18/2021 art. 65 3 source documents How the AI works

Where we sit

There is a wide gap between accounting software and a tax consultant

Accounting software records but does not guarantee the tax figures agree. A consultant guarantees but does not sit inside your daily bookkeeping. KLOPT stands between them.

What you need	Ordinary accounting software	Tax consultant	KLOPT
Daily bookkeeping & financial statements	Yes	Not their job	Yes, in full
Tax report alongside the accounting report	Usually a separate module, or missing	Built by hand each year	Automatic, from the same books
Monthly tax matching	No — a spreadsheet job	Yes, but billed by the hour	Runs itself at each month end
Working papers ready for audit	None	Built when needed	Collected through the year
Journals cannot be quietly edited	Partly	Depends on the client’s files	Cannot be deleted, and every change shows
The legal basis is attached to the figure	None	In the consultant’s head	Pulled from a dated rule list
Monthly cost	Rp150–500k	Rp5–30m	Flat, any number of users

This compares product types, not specific brands. Capabilities change over time — check for yourself before deciding.

Trustworthy

Not because we promise, but because the system refuses

A rule guarded only by application code will eventually be broken. So KLOPT’s bookkeeping rules are guarded by the database. Wrong code is rejected, not forgiven.

Security & data

Journals cannot be edited

There is no delete or edit. Corrections go through a reversing entry linked to the original.

Each entry is locked to the one before it

If one figure is changed mid-year, the lock breaks and it shows on the next check.

Companies are separated by the database

Not by application code. One wrong line cannot leak another company’s data.

Servers in Indonesia

Including backup and disaster-recovery locations.

Questions

What people ask most

Ordinary accounting software is good at recording. But there is one question it cannot answer: why does the revenue on your annual return differ from the total tax base on your invoices for the year?

There, matching those figures stays a March spreadsheet job. In KLOPT it runs by itself every month, from the same data.

No. The AI is forbidden from touching tax calculations, and that ban is built into the code structure. If someone tries, the build fails.

The AI does what machines are good at: reading PDF invoices, suggesting accounts, flagging odd transactions. The result is always a suggestion. You can reject it, and rejecting it leaves nothing in the ledger.

You are, as always. That is exactly why it is built this way: every tax figure comes from a rule list with effective dates. A 15 March transaction uses the rule in force on 15 March, not today’s rule.

Every judgement is labelled honestly: certain, conditional, or grey. A system that claims everything is certain loses your trust the moment one case is wrong.

One company with a year of history usually takes two to three weeks. Week one: import customers, vendors, items, and opening balances. Week two: run alongside the old books. Then switch.

Do not switch mid-period. The cleanest point is the start of a month. If that date is only days away, wait for the next one.

In Indonesia. Separation between companies is enforced by the database, not by application code. A single mistyped line cannot leak another company’s data, because the database itself refuses.

The full explanation is on the security page.

Another question? Send it to us — answered by a person, not a bot.

Next step

See your books the way a tax auditor sees them

Forty minutes with our team. We load sample data from your industry, run the last four months of checks, then show which gap is most likely to be questioned first.

Book a demo See pricing

No credit card. No commitment. We prepare the sample data.