Patch Pay reads the invoices your suppliers email, proposes the coding and sends each one to the person who approves it. Approved bills post to QuickBooks and become payment drafts in Revolut. A person releases every payment.
An invoice is always in one named stage, with one named person. Nothing moves to the next stage without the check that belongs to it.
By email, to a forwarding address that belongs to one company. A document can also be added by hand.
Supplier, amounts, dates and period are read from the document. Coding is proposed from the supplier’s earlier bills.
By the person who answers for that supplier, inside their own limit. Larger amounts go to a second approver.
Released from Final review, the bill is created in QuickBooks with its coding and the document attached.
Open bills become payment drafts in Revolut, merged per supplier. Somebody sends them at the bank.
Each invoice reaches one person, with the reason it needs them: a new supplier, an amount outside the usual range, a possible duplicate, a month that is already closed. An approver sees their own invoices and nothing else.
A bill from a known supplier, inside its usual range and with nothing flagged, can be approved by a rule. A rule never releases a payment, and a flagged invoice always goes to a person.
The controlsPatch Pay connects to Revolut Business with permission to read and to write drafts. It never asks for permission to pay, so no setting, rule or mistake in Patch Pay can move money. A person opens Revolut and sends each draft.
The checks that matter are not settings somebody remembers to switch on. They run on every invoice.
Finance teams where one or two people run the payables inbox and several others approve. Patch Pay takes the reading, the chasing and the retyping, and leaves the decisions where they were.
A person reads every request. Nothing is created until one is approved: then the company is set up and its first admin gets an invitation with a sign-in link.