Who it's for · business & teams
Bill on any rail. Pay on any rail.
One client wants an IBAN and a PO number. One sends USDT and asks for nothing. One pays half now and the rest when it ships. All three land in the same book, and nothing leaves it without the signatures you set.
- 01
Fifteen tabs, Friday evening
Two bank logins, an exchange, the invoicing tool that cannot see either of them, and the spreadsheet where the three are supposed to meet. It balances somewhere around Saturday.
- 02
The third message about one invoice
It went out four weeks ago. You think part of it came back, but that transfer might have been the other client. So you ask again, and hope you are not asking twice.
- 03
Thirty payouts, one at a time
Different amounts, half on a bank and half on chain. Copy, paste, check the last four characters, send. Then do it again, twenty-nine times, and hope nobody was missed.
What is out, what came back in halves
Everything owed to you on one page, with the ones that repeat pulled out at the top and a filter for the ones that only came back in part.
A real capture from a seeded studio. INV-0007 was paid in halves, so the row says so and the total still counts the rest as owed.
One invoice, whichever rail they use
Line items, a due date, a public link and a PDF with your details on it. A pay link for stablecoins, or bank details with a reference. A crypto payment for the right amount is matched on chain and booked as income while you are doing something else.
Half now, the rest when it ships
Record any amount up to what is left. The invoice turns partially paid, the list says paid 6,000 of 12,000, and the public page and the reminders start speaking in the balance due. Overpayment is refused rather than absorbed. Closing one early writes the remainder off, and the write-off lands in the log.
The chasing happens without you
A sent invoice with an email on it chases itself: three days before the due date, on the day, then three and seven days after. Each one goes once and carries the pay link. Clients get an unsubscribe link, and you can turn the whole thing off for one invoice from its row.
The ones that repeat, repeat
Turn a sent invoice into a weekly or monthly schedule and each cycle goes out on its own. If your monthly invoice allowance runs out the schedule pauses itself and tells you, then sends one catch-up when you resume. Never a backlog burst at the client.
Money out is the half that gets a spreadsheet of its own.
Which is where the mistakes live: the payee typed twice, the one that went out before anyone agreed to it, the bill nobody remembers approving.
Thirty payouts are one card, and one signature short
A payout run is one row in the queue with its total, not thirty things to check off. The rule reads the total, so splitting a payment into small rows does not slip under it.
Four contractors, 9,400 USDT, one card. The studio's rule asks for two signatures over 2,000, so it sits at one of two until somebody else signs.
Thirty people, one run
Add rows by hand or paste a CSV of payee, amount and note, up to 200 of them. Broken lines are shown rather than dropped. The run appears as one card you can expand, and Sign batch approves every row in a single action.
A second yes, on your rule
Pick the amount above which a payment needs another signature, and how many. Whoever proposes it never counts toward their own quorum. Lock sends to your address book if you want. Everything waiting sits on one page until it is signed or rejected.
Bills you accept, paid together
Invoices other people send you arrive in Incoming. Accept them into the space, tick the ones due, and Pay selected pays them as one run from an account you choose. Each closes itself when its payment executes. A bill above your threshold cannot be quietly marked paid instead.
What someone else paid for
Anyone who can write to the space submits a claim with a receipt, or without one and it is labelled so. Only people who can approve payments see the queue, and nobody decides their own, whatever their role. Reimburse selected pays the approved ones as one run, each booked with the category and project the claim carried.
Half of one invoice in, four contractors out
Nothing arranged. One rule set when the space was made: anything over 2,000 needs two signatures.
Sam signed, and all four went out as one run.
The half-paid invoice still shows what is owed and keeps chasing it. The print run closed itself the moment its payment executed.
Which project actually made money
Label a transaction, an invoice or a bill with a project and it lands in the same line. Paying either one books the money into its project without being asked twice.
Kestrel app is 6,200 in the red while the retainer carries the studio. That is the sentence a spreadsheet takes a weekend to produce.
Four numbers a Monday needs
Days from issue to payment over the last 90. Months of runway at the current burn, or the word profitable when there is none. What the active schedules bill every month. What is still owed to you and by you, side by side.
A bookkeeper who cannot move money
The accountant seat reads the whole picture and handles the paperwork: invoices, pay links, contacts, documents, and recording money that came in. It cannot post a transaction, propose a payment, pay a bill or touch the team. Everything it does lands in the log.
Accounts that are not everyone's business
Restrict an account and it disappears for everyone except the people you name, along with its balance and its operations. Their reports, net worth, goals and calendar quietly cover only what they can see, and say so.
The log that answers the awkward question
Every action with the old value beside the new one. Bulk work folds into one counted row and anything the system did is labelled. Filter by area and date, and the write-offs and signatures are in there with everything else.
- Rows per payout run
- 200, by hand or pasted as CSV
- Approval check
- On the run's total, never row by row
- Quorum
- The proposer never counts toward their own
- Invoice statuses
- draft, sent, partially paid, paid, void
- Auto-reminders
- 3 days before, on the day, 3 and 7 days after, once each
- Overpayment
- Refused, payments cap at the balance due
- Claims
- Submitted by any writer, decided only by an approver, never the author
- Roles
- Owner, admin, member, viewer, accountant, plus 12 per-member toggles
- Export
- CSV per report block, a monthly PDF, FIFO capital gains by year
Is this accounting software?
No. It is the ledger and the controls around it: what happened, who signed off, and what it exports to. Your accountant still does the accounts, with much better inputs.
Can I give my bookkeeper access without giving them the money?
Yes, that is what the accountant seat is. They read everything and keep the paperwork straight, including recording payments that came in. They cannot post a transaction, propose or approve a payment, pay a bill, or change accounts, team or settings.
Does a big payout dodge the rule if I split it into small rows?
No. The rule is checked on the run's total, so four rows of 2,350 need the same signatures one row of 9,400 would.
What happens if a client pays half?
Record it and the invoice turns partially paid: the list shows what is paid of what is owed, and the public page and the reminders start speaking in the balance due. Auto-tracked bank arrivals record their own partial payments.
Does everyone on the team need their own subscription?
No. The subscription belongs to one person and covers every space they own, so a business space runs on the owner's plan.
How do I keep business and personal apart?
Separate spaces. Connect each one's accounts, and move a stray transaction between them when it lands in the wrong place. Net worth still adds up across both.
Put both directions in one book.
One rule, one run, one log.