Invoicing System

Coople issues invoices to companies across Switzerland and the UK, and the two markets had grown two different ways of doing it. In Switzerland, back-office staff matched bank statements to invoices by hand. In the UK, a third-party provider chased outstanding debt and reported partial payments back in Excel, which fed a second Excel, which was uploaded to the finance system every night. Nobody had a live, trustworthy view of who owed what.

I led design on the new invoicing system: company settings (VAT, markup, and payment terms per customer), invoice creation and editing, credit notes, and the payment and debt-tracking views the back office depends on. We started by talking to the teams in Switzerland and the UK to map out how they actually worked today. From there I built a working prototype and tested it directly with the people who'd use it, refining the flow across several rounds. Also, I sat with engineering while they mapped the whole domain as commands, events, and read models, so the interface would speak the same language as the system underneath it.

The result is one invoicing engine that behaves consistently in both markets, with statuses and settings that adapt to how each one actually works rather than forcing a single template onto both.