Invoices, without the spreadsheet detour
We shipped a first-class invoice creation flow so you can bill business and individual customers directly, with payment terms and notes attached at the source.
For a long time, getting an invoice out the door meant leaving the product. Teams were exporting line items into a spreadsheet, pasting them into a template, then re-keying the same data back in to mark things paid. That round trip was the single most common complaint we heard from finance leads — and the one most likely to introduce errors right at the moment money is changing hands.
So we built invoice creation into the core product Create an Invoice.
Why this, why now
The shape of the problem was unusually clean. Customers already had their counterparties, their line items, and their payment expectations in the system. What was missing was a way to assemble those into a billable document without bouncing through a third tool. Every workaround we saw — Google Sheets, a PDF generator, a side instance of someone's old invoicing app — was solving the same handful of fields: who is being billed, on what terms, and with what notes attached.
A feature that maps that cleanly to existing data is a feature that should live in the product, not next to it.
What it unlocks
The new flow supports both business and individual customers, with payment terms and free-form notes as part of the invoice itself Create an Invoice. That last part matters more than it sounds: notes are where the real-world context lives — the PO number the buyer's AP team needs, the reference to a signed SOW, the "net 30 from delivery, not issue" caveat that turns a disputed invoice into a paid one.
By putting terms and notes on the invoice at creation time, we make them part of the record rather than something that has to be reconstructed later from email threads. That's the unlock. Not just "you can make an invoice now," but "the invoice you make carries the context it needs to actually get paid."
What's next
Creation is the foundation, not the finish line. The same data model that backs this flow is what we'll build sending, reminders, and reconciliation on top of. If you want the step-by-step walkthrough, the help-center article has it; this post is just the why. Try it on your next bill and tell us where it falls short — that's how the next iteration gets shaped.