Appearance
Billing and invoices
Notesflow writes, numbers and keeps invoices for the packages your customers hold, and chases what is unpaid. It does not take payment yet: you record money as it arrives. The design is ADR 0026, in the repository's docs/adr.
Before the first invoice
- Price your packages. In
/admin→ Packages, give each one you sell a counted price: an amount, a currency, per month or per year, per seat or flat. A package without one is never invoiced. The Invoices and Invoicing sections appear once one package has a price. - Say who is invoicing.
/admin→ Invoicing: your company's name, address and tax ID, a footer that says how to pay, the tax name and rate, how many days an invoice is due after it is issued, how many days overdue before the package is put on hold, and the number prefix.
Each month
On the 1st, Notesflow drafts an invoice for each customer and currency for the month just ended. On 1 January it also drafts one for the year just ended, for packages priced per year.
- Each day is billed at the package held at midday UTC, so a change partway through a month is prorated by day, and nothing is billed twice.
- A per-seat price is charged on the peak seats over the days the package was held. A seat is a person with a lasting membership; programs and break-glass access are not seats.
- A workspace that lives on its owner's per-seat package is charged to the owner, for the days it had no package of its own and they owned it.
- A price change applies from the day you make it. Days before it are billed at the old price, even in a month not yet invoiced; a month with both shows two lines.
Drafts wait under /admin → Invoices for you to issue them, unless Issue each period's invoices as soon as they are drafted is ticked. Issuing gives the invoice its number and due date, applies the tax, fixes both parties' details, and sends the customer an invoice-issued notice. An issued invoice never changes. Delete a draft to leave a customer out, then Draft this period again to make it afresh. Running a period that already has a customer's invoice skips that customer.
Money
Record payment against an invoice as money arrives, in parts if need be. When the payments add up, it is paid, and the customer gets a payment-received notice. Void an invoice that was wrong, before any money is paid or anything credited against it; the reason you give is printed on it. Account credit spent on a voided invoice goes back to the customer's balance.
Account credit
Until payments are taken in Notesflow, you add a customer's credit by hand, under Account credit in Invoices: their workspace address or account email, an amount and currency, and a reason they will read. Use it for money received in advance, or as goodwill. Take away removes credit, never more than they hold. The customer gets a credit-changed notice saying how much, why, and what they hold now.
Credit is spent on what the customer owes as soon as there is something to spend it on: at once on their open invoices in that currency, oldest first, and on each invoice as it is issued, before the customer is told what to pay. The invoice shows it as Paid from account credit. What is left stays in the balance, which the table under Account credit lists for everybody holding some.
Correcting an issued invoice
An issued invoice is never edited. Credit it instead, whether it is due or paid: give an amount before tax, or tick Everything not yet credited, and say why. The credit note gets a number of its own (NF-CN-2026-000001 with the default prefix), takes tax off at the invoice's own rate, and is printed as a page of its own. The customer gets a credit-note-issued notice.
- On a due invoice, a credit lowers what is owed. Credited in full, or paid and credited until it adds up, the invoice is settled, and any hold it caused is released.
- On a paid invoice, a credit leaves money owed back to the customer, and its row shows how much to refund. When you have sent it, Refund records it. Notesflow never refunds more than was paid beyond what is owed, nor more than was paid in money, and a refund is how an overpayment is handed back too. Keep as credit puts it into the customer's account credit instead, which is the only way back for credit that was spent on the invoice.
Credit notes on a row lists its credit notes and refunds.
When it is not paid
At the due date, and a week later, the customer gets an invoice-overdue notice. When the grace period has passed, the package is put on hold: it lapses exactly as an ended trial does, and the customer gets a package-held notice. Nothing is deleted, sign-in rules that are on stay on, and nobody is locked out. Recording the payment releases the hold; so does crediting what is left, voiding the invoice, or Release the hold under One customer's tax.
Tax
One rate for the deployment. Under One customer's tax you can give a customer a rate of their own, 0% included, with a note printed on their invoices, such as "Reverse charge: VAT to be accounted for by the recipient". Customers cannot change their own rate.
What your customers see
People whose role holds See invoices and keep billing details (manage_billing, which admins have) find Billing in the workspace's console. Everybody finds their own account's in Settings. They see what they owe, what is to be refunded to them, their account credit and every change to it, every issued invoice and credit note with a printable page (saved as PDF from the browser), and the details invoices are made out to, which they keep up to date themselves. If they give a billing email, invoice notices go there.
Notices
Through the link webhook (see Authentication), each with invoice: { number, total, due, currency, dueAt, workspace? }: invoice-issued, invoice-overdue, package-held, payment-received, credit-note-issued (also with invoice.credit: { number, total }) and refund-sent (also with invoice.refunded). The link opens the customer's billing in the app.