Home

How ClearingHouse catches sync issues before customers do

I haven't really talked about ClearingHouse since I launched it in March.

It doesn't make a lot of money (we're talking double digits), but it's slowly growing! 📈

I think most of that's been driven by SEO. About half of customers are Stripe Connect sellers, and the other half have "custom" Stripe integrations.

Lately, I've been working on improving how I spot sync issues before customers notice them.

Every day, ClearingHouse runs deterministic health checks across payouts, transactions and invoices to find anything that's drifted or never got synced to FreeAgent.

When one of those checks fails, it sends redacted information to an LLM that knows the codebase. It works out why it happened and sends me a Telegram message.

Amp watches for new health issues through my internal MCP and fixes them as they come up, so they're ready for me to review when I get to my desk.

GitHub pull request #130, "Stop rounded net unit prices adding pennies to synced invoices". The description explains the health issue that found it, why it happened, the fix, and a temporary command that corrects affected FreeAgent invoices.

I'm pretty happy with the process I've built for it.

It's niche (FreeAgent is UK-only and focused on SMBs), but if you use FreeAgent and Stripe, take a look at ClearingHouse: clearinghouse.app 👀