When the Accounts & Inventory Officer role opened up at Help Tech Co. Ltd., there was no chart of accounts, no consistent invoicing process, and no real reconciliation happening in QuickBooks. I had a computer engineering background, not an accounting one. I took the role anyway, and built the company's full accounts payable and receivable system from scratch, under deadline, because the alternative was leaving a growing backlog of financial mess untouched.
Starting from an inherited backlog, not a clean slate
The honest version of this story is not "I set up a pristine system on day one." It is that I inherited a backlog of account and inventory errors that had gone undetected before I took the role, and the first real work was clearing that out: tracing discrepancies back through transaction history until I found the actual root cause, correcting them, and only then building the process that would prevent the same errors going forward.
What "setting up AP/AR from scratch" actually involved
- Structuring how vendor bills and client invoices got entered consistently, instead of ad hoc, so reconciliation was even possible.
- Building the company's full payables and receivables reporting process, so cash position was visible without manually pulling numbers together every time someone asked.
- Managing client and vendor accounts end to end: issuing invoices, processing vendor bills, handling cash transactions, and performing daily reconciliation.
- Redesigning the company's invoice and estimate templates, which are still in use today.
- Designing an inventory management workflow that did not exist before and is now used company-wide.
Reconciliation is a debugging skill, not a math skill
The part of bookkeeping nobody warns you about is that reconciling accounts is much closer to debugging software than doing arithmetic. A number does not match, and the actual work is tracing it backward through the transaction history, one step at a time, until you find where reality diverged from the books. That skill transferred almost directly from the analytical habits I had built as an engineering student, and it is part of why I do not think of accounting, marketing, and automation as unrelated skills.
The reporting instincts I built doing bookkeeping made my marketing numbers sharper later. Once you have traced a discrepancy back through a ledger, you stop trusting a KPI dashboard you cannot explain.
Training colleagues, not just doing the work myself
A system only one person understands is not actually finished. Once the QuickBooks process was working, I trained colleagues on workflows they had previously been unable to complete on their own, because the goal was never to be the only person who could touch the books; it was to leave behind a process the company could actually run without me standing over it. That same instinct now shows up in how I document every automation I build in n8n: a README and a clear handoff, every time.
What this taught me about learning under deadline
I did not read a bookkeeping textbook before taking this role. I learned QuickBooks by using it, under real deadline pressure, with real vendor relationships depending on getting it right. That is the same pattern behind almost everything on my about page: hand me an unfamiliar problem with a real deadline, and I will figure out what it takes.