Food Brigade Accounting System
Role & duration: Software Engineer / IT Consultant (December 2024) for Program Brigade Pangan, Kementerian Pertanian Indonesia.
TL;DR
- Problem: Farmer groups receiving programme funds had no structured way to record and report how the money was used.
- Solution: A web-based double-entry accounting system covering the full cycle, from daily journal entries to the three core financial statements.
- Constraint: One month, starting with no accounting background.
- Tech Stack: Laravel, MySQL, Bootstrap.
Context & Problem
Farmer groups (kelompok tani) in the Food Brigade Program receive programme financing for food security activities. Funds like these have to be accounted for, line by line, to the programme and to auditors. The groups needed a tool that produces proper books without asking farmers to become accountants.
Constraint
- One-month deadline. The system had to be usable within the programme’s timeline.
- No accounting background. I had built financial reporting before, but never a general-purpose accounting system with its own books.
- Non-specialist users. The people entering transactions are farmer group administrators, not finance staff.
Decision & Trade-off
Learn the domain before writing the schema. I spent the first week on double-entry fundamentals: how journals post to the ledger, how the trial balance proves the books, and how the statements are derived from it. An accounting schema built on a half-understood model looks plausible and still produces wrong statements. That week was the cheapest insurance in the project.
Statements are derived, never typed in. Users record transactions once, in the journal. The ledger, trial balance, income statement, balance sheet, and cash flow statement are all produced from those entries, so the reports cannot drift away from the underlying records.
What I Built
- Daily journal for recording each transaction as balanced debit and credit entries.
- General ledger that posts journal entries per account.
- Trial balance to check the books before reporting.
- Financial statements: income statement (laba rugi), balance sheet (neraca), and cash flow statement (arus kas).
Why It Matters
Accounting software is unforgiving: a report that is almost right is wrong. This project shows I can take an unfamiliar, rule-heavy domain, learn it properly, and turn it into software that produces correct numbers on a deadline.
It is the same discipline behind the financial reporting I built for the ICARE and YESS programmes, where reports had to match the World Bank and IFAD Interim Financial Report formats and hold up in audits.