Invoicing and getting paid
Payment methods, building an invoice, sending it, reminders, and multiple currencies.
1 min read
We never hold your money
The client pays you directly. An invoice here is a document and a record, and the payment button on it opens your payment link on somebody else's site.
We take no cut of it, ever.
Payment methods
Add at least one before you can send an invoice: a payment link, or bank details.
A payment link is checked against a list of known providers, by exact host. That is the one field in this product where a wrong URL costs real money, and an allowlist is the only shape that fails safely.
Bank details are structured fields rather than a paragraph, and a bare run of 13–19 digits is refused as a card number. The provider on an existing method cannot be changed. Turning a link method into a bank method in place would leave fields behind rules that no longer fit, so switching means adding one.
One method is the default; ticking a new one demotes the old one rather than refusing.
Building an invoice
From scratch, or from an approved timesheet week, which writes one line per worked day and links each entry.
An entry that has already been billed cannot be billed twice: that is a database rule, not a check somebody remembered to write. Already-billed entries are skipped rather than refused.