Skip to content
KLOPT
Product Tax engine Two books AI Demo Pricing Security About Contact
Book a demo Sign in to the app
About KLOPT

We are building one thing, and building it right

Nobody has yet put accounting and tax checking into one system for the Indonesian market. Not because nobody thought of it, but because doing it right means making hard decisions early, before any customer is there to demand them.

Thesis

Why now

For twenty years, accounting software was valuable because it could gather the numbers. The data was scattered, and whoever could bring it together won.

Coretax ended that era. Tax invoices, withholding slips, and bank movements now reach the tax office before your return does. The numbers are no longer scattered. They are already gathered, on the other side of the desk.

What has value now is not gathering but proving the figures agree: making sure what you report can be explained against what they already hold — every month, with documents and statutes.

The product formula
1 The feature coverage of an established accounting package
2 The usability of a modern product
3 Tax depth nobody else has yet
4 AI you can defend, not AI as decoration
Principles

Eight things we do not negotiate

A principle that bends under deadline pressure is not a principle, it is a preference. These are the ones we genuinely do not bend, and the price we pay to keep them.

01

Type it once

One correctly recorded transaction produces the journal entry, the invoice, the withholding slip, the return data, and the working paper. All automatic.

02

Tax work runs by itself

Tax matching runs automatically every month, not as a year-end project.

03

Numbers always come from a repeatable calculation

Checkable, re-runnable, and defensible to an auditor. The AI never computes tax.

04

AI only makes suggestions

Always cited, always rejectable, and never posted straight to the ledger.

05

Usable by non-accountants

Business language on the surface, debits and credits underneath. Those who need the entries can open them; those who do not are not made to.

06

A tamper-proof record

Entries can only be added, corrections go through reversals, and each entry is locked to the one before it. That applies to us too.

07

Flat price, any number of users

Per-user pricing punishes you for giving access to people who should have it.

08

Honest when things are not certain

Every tax judgement is labelled certain, conditional, or grey. A system that fakes certainty loses trust on the first case it gets wrong.

Roadmap

Tax depth first, feature breadth later

We are not trying to win a feature-list comparison. We are trying to be the only system that can answer an auditor. The order of work follows from that.

Foundation

Done

Two-report ledger, database-locked rules, company separation, the entry chain, the design system, and the tax rule engine skeleton.

Core financial

Done

Sales, purchasing, cash & bank, inventory, dual-book fixed assets, financial statements, data migration, AI extraction v1.

Automatic tax matching

In progress

Payroll tax, withholding and slips, VAT, monthly return data, and a tax-rule assistant.

Tax matching

In progress

Automatic monthly matching, fiscal adjustments, the corporate return with its working papers, a risk dashboard, and material for query responses.

Channels & integration

Planned

Direct submission to tax systems, auditor-method flow tests, a consultant and firm portal, a B2B API.

Premium

Planned

Model-based risk scoring, transfer-pricing documentation, multi-entity group consolidation.

One thing we deliberately keep slow

No tax figure enters the system without a checked legal basis and a worked example validated by a tax practitioner. This slows us down, and that is the point. A wrong tax rule is not a bug you fix next week. It becomes a return that has already been filed.

How we work

What you can expect from us

We say no

If your feature request would make the product broader but shallower, we will say so, and say why. A roadmap that follows every request ends up with no direction.

A tax practitioner is part of the team

Not a freelancer consulted now and then. Whoever owns the tax rule list and the chart of accounts is part of the product, not an add-on service.

We show what is unfinished

This page states the roadmap plainly, including what is not done. You deserve to know what you are buying today, not what we promise next year.

“A rule guarded only by code will eventually be broken. What must be right is locked into the database.”
04 Correctness principleKLOPT internal engineering doctrine
“A system that fakes certainty loses trust on the first case it gets wrong, and never gets it back.”
08 Eighth product principleThe KLOPT master plan
Next step

We are looking for design partners

If you are a mid-market VAT-registered company or a tax consultant willing to show us your real work, messy parts included, we would like to talk. Design partners help set our build order.

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