Before we wrote a single line of StewardTrack's finance module, we spent time with church treasurers — in their homes, in their sacristies, at their kitchen tables where they spread out their ledgers and binders. Here is what we learned.
Lesson 1: The Treasurer Is Almost Never a Professional Accountant
In the vast majority of Filipino churches we visited, the treasurer was a dedicated lay volunteer — a retired teacher, a small business owner, a nurse who was good with numbers. They had given years of service to their church and were doing their best with the tools available.
This shaped everything about how we designed the finance module. We could not assume accounting knowledge. We could not use jargon without explanation. The chart of accounts needed to be intuitive. The reports needed to be readable by someone who had never seen a balance sheet.
Lesson 2: The Biggest Fear Is Making an Undetectable Mistake
When we asked treasurers what kept them up at night, the answer was almost always: "What if I made a mistake and nobody catches it?" Not fraud — most treasurers were deeply ethical people. Just honest errors. A wrong sum. A misfiled receipt. An encoding mistake.
This is why the audit trail was non-negotiable for us. Every transaction logged. Every change recorded. Not as surveillance, but as a safety net. When something looks wrong, you can trace it back and find where it went off.
Lesson 3: Inter-Fund Confusion Is Universal
Almost every church we visited had some version of the same problem: money from the building fund had been used for operational expenses at some point, and now nobody was quite sure of the actual building fund balance. Or missions giving had been mixed with general offerings.
This is why Ministry Funds with dedicated tracking are a core feature, not an add-on. The system should make it physically difficult to mix funds accidentally.
Lesson 4: Year-End Is Dreaded
We asked one treasurer in Zamboanga how long year-end reporting took her. "Three weekends," she said. "My husband knows not to make plans in January."
That answer stayed with us. Three weekends. For something that should take a few hours if the data is clean and organized throughout the year. Every feature we built was designed with that treasurer in mind.
