The invoice, and the proof it was paid.
Send an invoice with your reference, due date and files on it. Every payment lands against it, from any rail, so the invoice stays the one record of what was billed, paid and still owed.
One record, from sent to paid
This is the invoice as your team sees it. Every payment, every confirmation and every change is written onto the invoice itself, not into a spreadsheet beside it.
Try it Step through the invoice's life.
Invoice · NWL-0142
Halden Studio
Design retainer, October
- Your reference
- PO-4471
- Due
- Nov 15
- Files
- invoice-0142.pdf · Retainer agreement
Total$4,800.00
$0.00 received$4,800.00 left
Payments
None yet.
History
- Oct 15Created by Maya Chen
- Oct 15Sent to Halden Studio
Everything on the invoice
What your customer needs to pay it, and what you need to close it out.
-
Your reference
Your PO or invoice number on the invoice, so it reads the same in Mezzanine as in your books.
-
A due date
Your customer sees when it is due, and your team sees which invoices are past it.
-
Files and agreements
The invoice PDF and the contract behind it, attached to the invoice and scanned before anyone opens them.
-
Every payment against it
By bank or by stablecoin, each payment is recorded on the invoice with the rail it came in on.
Close the month from the invoice
- Each bank transfer carries a reference that ties the money to this invoice, beside your own PO number.
- Who confirmed each payment, and when, is on the invoice, and so is any payment that was rejected and why.
- Settled for less? Void the remaining balance. What was paid stays on record.
- The paperwork finds the payment. Link the invoice PDF to it in Company Files, and either one leads to the other.
Your customer's side
One page to pay from.
They open the invoice, see the total and the files, and pay by ACH, wire or stablecoins on the network they use. No workspace to join.
See what they see