Tin Roofs of Surabaya
by Adit WijayaIn Surabaya in the late 1940s, a kretek factory clerk finds her dead brother’s name on a payroll list weeks after his burial.
Once the jobs are clear and the accounts are open, the next temptation is to automate everything and call the system finished. That sounds efficient. It also creates a very common problem: money starts moving on schedule, but no one is checking whether it is moving to the right place in the right amount.
Automation is useful, but it is not judgment. It is a way to carry out decisions you have already made. If the decisions are sound, automation reduces friction. If the decisions are sloppy, automation repeats the sloppiness very reliably.
That is why this chapter is about the first draft. Your money system does not need a perfect machine on day one. It needs a sensible sequence that handles the obvious moves automatically and leaves a few points where a human being still looks up and asks, “Does this still make sense?”
For Maya, that matters a lot. She is paid twice a month, on the 15th and the last day of the month, with $2,150 take-home each paycheck. Her system already has a shape. Bills Checking holds bill money and a $500 buffer. Spending Checking is for everyday life. Sinking Funds Savings holds the monthly set-asides for irregular costs. What she needs now is a repeatable payday flow so the plan happens before convenience, forgetfulness, or wishful thinking take over.
A good rule is simple: automate the parts of the plan that are supposed to happen almost every time in almost the same way.
That usually includes four things:
It usually does not include every flexible category, every extra debt payment, or every spending decision that changes with the month.
Think of automation as handling the first pass. It gets the paycheck sorted into the right buckets. It protects the essentials. It moves the predictable pieces into place. Then it stops. It does not need to decide whether this is the month to spend more on restaurants, replace shoes, or send extra money to a credit card. Those are human decisions, not machine decisions.
For Maya, the fixed pattern is already mostly known:
That means the first draft of automation can be built around those repeated moves. What should happen automatically is not mysterious. On payday, Maya needs her money sorted fast enough that rent, utilities, insurance, and daily spending do not compete in one account.
Notice what this chapter is not doing. It is not asking Maya to automate every category separately. She does not need a transfer for groceries, another for coffee, another for gas, another for personal spending, and another for every future goal she may add later. That turns a simple system into a wiring diagram. The point is clarity, not complexity.
The order matters because automation should protect the most important jobs first. If the sequence is sloppy, money can be available in the wrong place for a few days, which is often enough to create mistakes.
A practical sequence looks like this:
For Maya, the cleanest first draft is to have her paycheck deposited into Bills Checking, then use automatic transfers out of that account. There are other workable setups, including split direct deposit through payroll, but the logic is the same. The money lands in a controlled place, then gets assigned.
Here is how Maya’s end-of-month paycheck can flow:
Then her bills can draft on schedule from Bills Checking:
Her 15th paycheck follows the same shape:
That is the first draft. It is not fancy, but it does the essential work. By the time Maya starts buying groceries or paying for lunch, the money for those choices has already been separated from rent and utilities. Bills are not waiting in the same pool as takeout and rideshares.
This is exactly what automation is for. It handles the repetitive sorting before mood and memory interfere.
Automation works best when it moves money toward its job, not when it tries to replace every later judgment call.
If Maya’s employer allows split direct deposit, she could send part of each paycheck directly to Spending Checking and part to Sinking Funds Savings, with the rest going to Bills Checking. For example, each paycheck could be split this way from the start:
That is perfectly workable if payroll makes it easy and reliable. But it is not required. Many people find it simpler to let the paycheck land in one place and schedule transfers themselves. The best method is the one that is easy to understand and easy to verify.
Autopay has a reputation for being automatically wise. It is not. Autopay is wonderful when the account balance is ready for it. It is dangerous when the timing is fragile and no one is watching.
Maya is finally in a position to use autopay well because earlier chapters did the setup work. She sorted bills by timing in Sort Bills by Timing. She set a realistic spending floor in Set a Floor for Daily Life. She created sinking funds in Build Sinking Funds First. She chose a $500 working buffer in Choose Your Buffer Target. She separated accounts in Open the Right Accounts. Now autopay can serve the plan instead of exposing every weakness in it.
For Maya, the best candidates for autopay are the recurring bills with known due dates and expected amounts:
Electric is also a recurring bill, though the amount varies somewhat. That does not disqualify it. It just means Maya should know that the bill may be closer to $95 some months and closer to $140 in others. That is one reason her buffer stays in Bills Checking. The buffer is not there for drama. It is there for ordinary variation.
There are two practical rules here.
First, autopay from the account built for bills. Maya’s recurring bills should draw from Bills Checking, not from Spending Checking and not from whatever account happens to have cash at the moment. The account structure only helps if each account is allowed to do its job.
Second, do not autopay from a category that changes week to week. Groceries, coffee, transit top-ups, and small personal spending belong in Spending Checking because they require active trade-offs during the month. If Maya automates a stream of flexible purchases, she loses the very visibility that is supposed to help her stay on track.
This is the line many people need: fixed bills can usually be automated; flexible life still needs a person.
Some people hear “manual” and think “failure.” It is not failure. It is oversight.
A money system should remove unnecessary decisions, not all decisions. There are still moments when someone has to notice reality. Income can change. Utility bills can drift up. A subscription can renew at a higher price. A transfer that worked in March can be too aggressive in August. Automation will not raise its hand and say, “This setup is getting tight.”
That is why Maya needs a few built-in review points.
The first is right after payday. Not a long meeting. Just a quick check that the paycheck arrived, the transfers happened, and Bills Checking still sits above the $500 buffer floor after the planned obligations are accounted for.
The second is before the next cluster of bills. For Maya, that matters especially in the first half of the month because rent, electric, and internet all lean on the end-of-month paycheck. If electric comes in at the high end, or if a transfer failed, she wants to know before the due date, not after.
The third is at her monthly money date from Choose Your Money Date. That is where she can decide whether the first draft still fits. Maybe the $400 spending amount is realistic and steady. Maybe it is consistently too low in one half of the month and too high in the other. Maybe one sinking fund category needs a larger contribution. Maybe the buffer should stay at $500 a little longer before any extra debt payment is considered. Automation cannot make those judgments. It can only carry out the current settings.
Here is what Maya is not reviewing every few days:
Those decisions have already been made. The review points are for checking execution and adjusting the plan when reality changes, not for reopening every settled question.
A useful test is this: if skipping the action would create a late fee, missed obligation, or predictable future scramble, automate it if possible. If the action depends on changing priorities or trade-offs, review it manually.
It helps to see the whole pattern in one place.
Maya’s monthly income is $4,300 total, split into two paychecks of $2,150. Her first-draft automation can look like this:
Across a full month, that means:
What remains for active choice is exactly what should remain for active choice: how Maya uses her everyday spending money, whether she needs to shift within that spending amount, and whether any extra money beyond the first draft should go to a goal, debt, or buffer growth.
That is the point. The plan handles the predictable work first. Human attention is saved for the trade-offs that are actually trade-offs.
There is also a psychological benefit here, though it comes from structure, not motivation. When Maya opens Spending Checking and sees the amount available for daily life, she no longer has to mentally subtract rent, internet, and insurance from a mixed account balance. The account itself is doing part of the thinking. That is what a good system should do.
If the first draft turns out to need adjustment, that is normal. Maybe a bill due date shifts. Maybe Maya decides to split direct deposit later because it feels cleaner. Maybe she raises the sinking-fund transfer after seeing a larger annual car expense. None of that means the system failed. It means the first draft did its job by making the moving parts visible.
Before the next payday, write down three things: where the paycheck will land, which fixed transfers should happen automatically, and which bills are safe to put on autopay from the correct account. Then write down the two or three moments when you will still review the system by hand. The goal is not to automate everything. The goal is to automate the parts that should not need a debate every month.
This book turns a steady paycheck into a system that covers bills, builds reserves, and leaves room for real life. Rachel Torres walks through one money decision at a time, using simple examples to show how to route income, stop drift, an…
In Surabaya in the late 1940s, a kretek factory clerk finds her dead brother’s name on a payroll list weeks after his burial.
In the cliff town of San Jerónimo, Rosa Varela keeps the lighthouse lit with a trade everyone understands: a memory for a flame.
In a damp, overbuilt Newcastle a public service called Proxy lets people rent out their bodies for remote work, care visits and difficult conversations.
When a retired language teacher is found dead in a narrow lane behind Kanda Station, former police detective Mariko Arai is asked to make sense of the papers he left behind: old…
Sign in to leave a comment.