Too ordinary for anyone to mention

Today marks exactly 1 month since I arrived in Jakarta. I landed on 30 July and I am here until 26 September to renew my working visa. Between appointments I meet people and we talk about screens. Of everything I have learned in this month, the parts that mattered most appear in no manual. Not left out, exactly — nobody thinks of them as the sort of thing you would write down.

The first one was our own PDF invoice. I printed it and showed it to V, the accountant here in Jakarta who has tested KAZENA Books with her firm's real data more than 20 times. She picked the sheet up, went quiet for a moment, and said it could not go out like this. Nothing to do with the numbers. The top is empty, is how she put it.

She meant the KOP: the band across the top of a document carrying the company name, the address, the phone number and the NPWP. Here that band is simply expected, and a sheet without one is not always treated as a proper document. All our PDF had at the top was 1 small logo in the left corner. We had carried over the habits of a Japanese invoice and assumed a logo was enough.

Why nobody had mentioned it before is the thing I have thought about most this month. V was not holding anything back. To her, a KOP is about as remarkable as ink on paper — not the sort of thing you explain. And on our side, you cannot ask about what you do not know. Until that first sheet was printed and lying on a desk, the question had not occurred to anyone.

She taught me a second thing the same day: the company stamp that goes beside the signature. A document with only a signature looks unfinished, she said. Our PDF did have a signature block, but it was not tall enough to leave room for a stamp. Press one and it either lands across the letters or spills out of the frame. The field existed; it just could not be used.

We talked about the duty stamp as well. Certain documents require a 10,000 rupiah stamp, and an electronic version is in use now. Which documents need one depends on the nature of the document, so I will not make claims about it here. What I can say is that our template had nowhere to put it. It was not that we did not know the rule; we knew it, and left no space on the page.

The idea of what counts as evidence was different too. We had built as though every payment produces a receipt. In practice here, the image of a transfer confirmation travels as the evidence itself. If there is no place to attach an image to a transaction, that image stays inside somebody's phone. Whatever has no home in the software gets lost in the actual work.

A word about handwritten paper. At the warung near the office, receipts are written by hand as a matter of course. Thousands are separated with dots, some people write K for a thousand and others write rb, and item names are abbreviated in ways only the shop can read. After nasi padang one lunchtime I ran the slip I was handed through our own reader on the spot. Half of it came out; half did not. I had never seen what a thing built on clean test images does in front of paper like that.

Here is what we changed. Three documents — the invoice, the receipt, the withholding slip. A KOP band now sits at the top, with the company name, address and NPWP pulled from the settings. The signature block is taller, with clearance so a stamp does not land on the letters. There is a defined place for the duty stamp. And a transaction can carry an attached image, so the transfer confirmation has somewhere to live. Four changes in all. None of them was hard to build. The hard part was learning that they were needed.

E looked at the new template too. He lives in a small town some way outside Jakarta and sees slightly different paper than I do. What he said was that the address has to be allowed to run to 2 lines. Addresses in his town run long, from the RT/RW through the kelurahan and the kecamatan. My frame was 1 line tall and quietly cut off whatever did not fit. If I had only ever looked at addresses in this city, we would have shipped it that way.

The design mistake underneath all of this is easy to state. A document is not finished at the moment we generate it. After that it passes across a client's accounting desk, a tax counter, and an archive shelf some years later. What we had built was paper that looked correct on screen. What was needed was paper that survives the desks that come after. Both come out of the same software the same way, and they are not the same thing.

What I have learned in this month is only what I happened to bump into. I learned it by printing something and showing it to someone, or by going out to eat. Not one item on the list came from research. So saying these were things I could not learn through a screen is probably wrong. It is not that I could not learn them. I never asked.

One caution. I am not a tax accountant. Which documents require a duty stamp, and what has to appear on an invoice, depend on the nature of the document and the shape of the transaction, and the rules change over time. What I have written here is what I was taught locally and what we changed in our own software because of it. Please confirm the formats you actually need with a professional.

A request, then. Print something KAZENA produces, and if it does not look like the paper you actually use, tell me where the difference is. The top is empty — a short sentence, and a month of my assumptions came apart. The things you think are too obvious to mention are exactly the things we do not know.