I built LedgerSkill because I watched accounting teams drown in CSV reformatting.

I'm Brian. I've spent years working in and alongside small accounting departments — the kind with two or three people doing the work of ten, where every new integration or software change gets weighed against the hours it takes away from closing the books.

Every department I worked with had the same story. Payroll exports, payment processor settlements, bank feeds, credit card statements — each one arrived in a different format, and each one needed to become a journal entry in the GL. Somewhere along the way, someone built a spreadsheet, wrote a macro, or cobbled together a custom script to handle the translation. It worked. Then it became permanent. Then the person who built it left, and nobody understood the code anymore.

The tech debt trap

That's the trap small accounting teams fall into. They can't afford enterprise integrations, so they build static custom code — Excel macros, VBA scripts, manual CSV transformations — to bridge the gap between the data they receive and the journal entries they need to post. It works until it doesn't. A vendor changes their export format. A new GL account gets added. The spreadsheet breaks and nobody knows how to fix it.

I watched this cycle repeat across every team I worked with. Hours lost to debugging brittle formulas. Entire close processes held up because one fragile spreadsheet couldn't handle a new edge case. The "custom solution" that was supposed to save time became the biggest source of month-end stress.

A different approach

LedgerSkill is built on a knowledge graph — a structured representation of accounting recipes that understands double-entry bookkeeping, chart of accounts semantics, and the rules that govern how source data maps to journal entries. Instead of static code that breaks when anything changes, recipes are inspectable, modifiable, and composable.

Combined with AI that actually understands accounting logic, LedgerSkill can handle the translation from any data source — payroll, payment processors, bank feeds, credit card statements — into balanced, import-ready journal entries for any accounting software.

Why I keep building

I know what it's like to be the person in a small department who has to be the accountant, the IT support, and the spreadsheet developer all at once. LedgerSkill exists so you can stop maintaining fragile code and start focusing on the work that actually requires your expertise — judgment, advisory, and getting the books right.

No venture capital. No growth-at-all-costs playbook. Just practical tools from someone who's been in the same seat you're sitting in.