Invoices people stop asking about

Research

I read four months of support tickets tagged billing and sorted them by the question behind them. Three questions covered most of them: what changed since last month, why a credit was missing, and how to get the data into a spreadsheet. I then sat in on six month-end calls with finance teams at customer companies, watching them reconcile our invoice against their own records.

The pattern was the same each time. People were not confused by the numbers; they were confused by where the numbers lived. Usage was on one page, credits on another and the PDF on a third.

I also asked the support team to forward every billing ticket to a shared channel for two weeks, so the engineers saw the questions as they arrived rather than in a summary at the end.

Decisions

We rebuilt the invoice as one page with three parts: a summary that names what changed, a line for every product with its own usage chart, and credits shown inside the line they apply to. Exports became a single button with a date range, CSV or the accounting format the customer already used.

If a finance team needs to ask us what a line means, the line is wrong, not the finance team.

I kept the old table available behind a toggle for the first two months, so nobody lost a workflow overnight.

Shipping

We released to twenty customers first, then to everyone over three weeks. Support tracked the billing tag weekly. By the third month-end, invoice questions were down 38% and exports had more than doubled, mostly from customers who had never used them before. Closing a month went from eleven working days to two.

The biggest surprise was who used the new export. Account managers started sending it to customers before renewals, which nobody had planned for, so we added a share link in the next release.