Finance teams + delegated spending
Decide which bills and invoices need signing off and by whom, hold them until everybody named has agreed, and keep the authorisation on the document itself.
Where work breaks apart
Once more than one person can commit money, the authorisation lives in chat, email and a conversation by somebody's desk. Months later — for a board, an auditor or a lender — nobody can show who agreed to a payment, or whether anybody did before it went out.
With invoiso
A bill or invoice a rule names cannot reach the books until everybody named has agreed, so the authorisation happens before the payment run rather than being reconstructed after it. Every request, approval, rejection and override sits on the document's own history with the person and the date.
How it comes together
Name the documents that need signing off — by who filed them, the supplier or customer, the category, how they arrived, or an amount — and name the people who have to agree. Where two rules cover the same document, everybody both rules name is asked.
A bill a rule names cannot be confirmed and an invoice cannot be issued until everybody named has agreed. One rejection sends it back with a reason, and nobody is ever asked to approve their own work.
Every request, decision and override is written to the document's history with the person and the date, so the answer to who approved this is on the record rather than in somebody's inbox.
What makes it work
Open any feature for a closer look at what it does, which plan includes it and the product screen behind it.
Write rules about which documents need signing off and by whom — who filed it, which supplier, which category, how it arrived, over an amount. A document a rule names cannot be confirmed or issued until everybody the rule names has agreed, and one rejection sends it back with a reason. Nobody approves their own work, ever. Where two rules cover the same document, everybody both rules name is asked. A document no rule names needs no approval, so switching this on holds nothing up until you write the first rule — and an owner can put one through without its approvals, with a reason that stays on the record for good.
Explore the featureIncluded on every planRecord full or partial supplier payments, including payments in another currency or against a credit note. Outstanding balances and ageing update from each bill's due date; a bill without a due date remains owed without being marked late.
Explore the featureBusiness and upReview bank details read from each bill, save confirmed accounts to the supplier and export selected unpaid bills as an ISO 20022 payment file. Changes and missing details are flagged before download; invoiso never guesses account details or moves money.
Explore the featureCompleteEvery invoice, bill, contact and product carries its own history: who changed it, when, and whether it was a person, the assistant or a connected app. On Complete each entry also lists the fields that moved and what they were before.
Explore the featureCompleteGive everyone working on the books access to the same records instead of emailing exports around. Remove someone once and their access disappears across the workspace.
Explore the featureIncluded on every planSet how far back the books are complete and nothing can write behind that line — not you, the assistant or an automated run. The boundary moves forward automatically instead of relying on someone to remember.
Explore the featureSee it in invoiso
No. A document no rule names needs no approval, so the switch on its own changes nothing. The first rule you write is what starts holding documents.
No. The person who filed the document and the person who asked for approval are both excluded, even when a rule names them. A rule whose only approver is the person who filed the document is refused rather than passed.
An owner or an administrator can put a document through without its approvals, and has to type a reason. The override and its reason stay on the document's history.
Start at your pace
