Invoicing and getting paid

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.

A monthly-rate engagement gets a clear refusal rather than an invented per-hour figure.

You can also add lines by hand, a discount, a tax percentage, a PO number, payment terms and notes, and reorder the lines.

Numbers

Assigned when you send, from your own counter. Drafts have no number. A cancelled invoice keeps its number, and the sequence has no gaps: that is a property of how it is assigned rather than a promise.

You can set a number by hand on a draft. Auto-assign can never collide with one you chose.

Sending

Sending freezes the document: the payment details, the exchange rate and every figure are snapshotted as they are at that moment. Changing your payment link afterwards cannot rewrite an invoice somebody is about to pay.

A sent invoice is read-only. If it is wrong, Revise reopens it, which is the same state the client's "request changes" produces.

Currencies

Any of the six the platform supports, and by default the currency the engagement was agreed in. A courtesy estimate in the client's currency sits beside the total, at the rate frozen when it was sent.

If we have no fresh rate, sending is refused rather than freezing a stale one into the document.

Getting paid

The client marks it paid, and you confirm it, or dispute it, which returns it to you to revise and resend.

Only a confirmed invoice counts as paid anywhere. Marking paid is the client's claim; confirming is yours.

Reminders

An unpaid invoice generates reminders on a widening schedule, and the last one says it is the last. You can also send one by hand, with a wait between them.

They stop the moment the client marks it paid: chasing somebody who has just said they paid is worse than saying nothing. If they dispute it back, the remaining reminders resume, because you have just been told the money never came.

Money and PDFs

Every invoice downloads as a PDF and exports as CSV. `/me/invoices` also carries your own figures: what you billed, what you received, and approved hours you have not invoiced yet.

Currencies are never added together. Two currencies are two numbers.