The variance, to the rupiah
Every rupiah that reached the bank and did not match an order, split by cause: fees, refunds in transit, settlement lag, and the ones nobody can explain. The unexplained ones are named, not averaged away.
Send three exports. In five working days you get back a written report of what does not reconcile, what it costs you a month, and what I would fix first.
Not a demo. Not a call. Your data, your period, your real differences — reconciled and priced. If the answer is "nothing is wrong", you keep the report and we stop there. That happens more often than you would expect.
Every rupiah that reached the bank and did not match an order, split by cause: fees, refunds in transit, settlement lag, and the ones nobody can explain. The unexplained ones are named, not averaged away.
The variance, annualised, expressed in your margin. Not "data quality issues" — a figure your partner can argue with.
Questions your data cannot answer yet, ranked by what they would be worth if you could. This is usually the most valuable page in the report.
One recommendation, with the reasoning. Often something you can do yourself this week with no software at all.
A fixed scope and a fixed price for the build, so you can compare it against doing nothing. Credited in full if you go ahead.
The full report, yours to forward to a partner, an accountant or whoever makes you feel stupid about the numbers. No exclusivity, no follow-up sequence.
If transactions live in someone's head or in a notebook, there is nothing to reconcile and the audit becomes research. That is a different engagement and a worse one. Wait until you are recording.
Then hire one. You will get more out of a full-time hire than from a five-day report, and I will say so on the call rather than take the money.
If what you need is a screen, not an answer, this is the wrong product. The build is designed for the answer first.
If a discrepancy has never once caused an awkward conversation, fixing it has no value and you will not use the report.
Bank transfer or QRIS. Invoice on request, PKP-ready.
What to send
Any three. If you have them in the wrong format, send them anyway — that is part of what the audit tells you.
Start by email. Tell me the period, attach the three exports, and say whether to use your real names. You will have a start date and a delivery date within one business day.
I reply within one business day (Jakarta, UTC+7).
Credited in full against the Rp 7.500.000 build if you continue within 30 days of delivery. It is arithmetic, not a discount: you are not paying twice for the same month of analysis. If you do not continue, you keep the report and the credit simply expires.
Then the report says so, in writing, and you have spent 2.5 million to avoid a 7.5 million mistake. This happens. Several of the audits I have described in my own outreach were run precisely because I suspected the answer might be "nothing is wrong" — that is a legitimate outcome, not a failure.
No. The report is yours. I use anonymised, aggregate patterns when I write case studies, and only with written permission naming what may be published. Blank the names yourself if you prefer — see the email template above.
Five working days from the moment I have all three. If they are in formats I cannot read, I will tell you on day one and the clock does not start until it is readable. I would rather say that than miss a date quietly.
No. The audit is complete on its own. It has an end, six pages, and a recommendation you may act on by yourself. The build is a separate decision you make afterwards with the information in front of you.
No. The whole flow is email. I will ask for the period and the exports, then deliver. If you want a call afterwards to walk through it, fine — but it is not a condition of the audit.