Statement ZenWhy I built Statement Zen
A decade automating finance systems. Statement reconciliation was the worst of them.
Statement Zen isn't a startup idea I dreamed up on a whiteboard. It's the productised version of the last and ugliest system I automated for two real Australian clients over 12 years.
The 12-year backstory
For over a decade, I was embedded with two large Australian groups as their automation operator. Not a vendor selling a product — actually inside the business, week after week, fixing things.
We automated the crap out of their finance stack — AP processing, accruals, intercompany reconciliations, payment runs, fuel cost allocation, internal reporting, payroll feeds, inventory movements, GST returns. If it ran on a schedule and humans hated doing it, we automated it.
One process refused to die: vendor statement reconciliation. Every month, the AP team would print statements, line them up against the AP ledger, and chase discrepancies for two full weeks. Duplicates. Missing credits. Pricing variances. Statements that didn't balance. Vendors that hadn't emailed yet. It was the kind of work that nobody ever finished — they just stopped when the month ended.
We tried scripts. We tried better Excel templates. We tried OCR tools that existed at the time. Nothing held up across enough vendors and statement formats. Until the AI tooling caught up around 2023.
Then everything clicked. We rebuilt their statement reconciliation using a custom OCR pipeline (vision-language model fine-tuned for financial documents), a layered matching engine that handles the edge cases AP teams know about and SaaS vendors don't, and a workflow built around the way real AP managers actually work — not the one product designers imagine.
Both clients — each with around 200 active vendors — went from a two-week monthly ordeal to a half-day exercise. A 95% time reduction. The AP teams stopped dreading month-end.
That was the moment I knew it was a product, not a custom build. Every AP team has the same problem. Most don't even know what's possible because the tools they've seen (DocParser, Textract, generic AI) don't come close to handling real-world statement chaos. So I packaged it.
That's Statement Zen. It's not a fresh idea. It's a decade of pattern recognition shipped as software.
What makes this different from the other AP tools
- No mandatory ERP integration. Email-first workflow — forward your AP export and your vendor statements, get a reconciliation back. No IT project, no integration cycle, no "we'll get to it next quarter."
- A custom OCR stack tuned for finance documents. Most AP tools rent generic OCR from AWS or Google. We built our own — a vision-language model fine-tuned on real vendor statements, with deterministic fallbacks for the cases the AI gets wrong. It's more accurate AND cheaper to run.
- Edge-case handling that comes from doing it for real. Multi-page statements that don't balance to themselves. Foreign currency vendors. Credit notes booked the wrong month. Statements where the closing balance is on page 4 but the line items stop on page 2. We've seen all of it because we lived it.
- Custom integrations on the house, for founding partners. Don't see your ERP listed? We'll build the integration ourselves, free, for the first 15 founding partners. Most tools won't do that because they can't afford to. We can — because the integration work is exactly what I've been doing for 12 years.
What we stand for
Three principles. They show up in every line of code and every customer conversation.
Pick the worst problem
I didn't build Statement Zen because vendor statements were trendy. I built it because it was the single hardest AP process I'd ever automated — the one that resisted a clean fix for years. If we cracked it for two clients with ~200 vendors each, we can crack it for you.
Earn the time back
Both clients went from a two-week monthly ordeal to a half-day exercise — a 95% reduction. That's not a marketing claim. That's the bar. If Statement Zen doesn't move the needle that much for you, we haven't earned the spot.
Build it like a CFO would
WAF-protected, post-quantum encryption, SOC 2 Type II in progress, Australian-onshore data. I've watched too many CFOs get burned by SaaS founders who treat security as a sales objection. We treat it as the floor.
Built in Australia, for AP teams that already exist
Statement Zen is an Australian company, built for Australian, New Zealand, US, and UK finance teams. Data stays onshore (Sydney region). Support comes from the people who built the product. We understand the ERP landscape your business actually runs on — because we've been inside it for a decade.
Want to be one of the first 15 founding partners?
Pro plan free for life. Custom ERP integration on the house. 15 min/week of founder time for 60 days. In exchange: a case study, a review, a video testimonial, and 60 days of honest feedback while we iterate.