Raise a payment request
Ask the business to pay a vendor, a contractor, or someone specific.
Use a payment request when you already know who gets paid and how much — a supplier invoice, a reimbursement, a bill that needs settling.
Opening the form
Raise a request on Spend home, or + New on the Spend list, opens the picker at /payment-requests/new. It offers three choices; pick Request a payment.
Under the picker sits your own recent requests, so you can open the last one instead of starting again.
Per line
The form asks plain questions instead of showing field labels.
| Question | Required? | Notes |
|---|---|---|
| What is this payment for? | Yes | The purpose. Up to 255 characters. |
| How much? | Yes | The amount. A currency chip sits beside the question — see below. |
| Who gets paid? | No | The beneficiary account name. |
| Their account number or IBAN | No | Up to 34 characters. |
| Their bank | No | Picked from the bank directory, shown with the bank’s logo. |
| Anything the approver should know? | No | A note on this line only. |
Add another payment adds a line. Each line is reviewed, approved, declined and posted independently — a request with three lines can end with two paid and one declined. The running total sits in the footer beside the submit button.
While a line has no beneficiary yet, a strip of chips appears above it — up to five people you have paid on your own past payment requests, deduped by account and bank, most recent first. Account numbers are shown masked. Tapping one fills the name, account number and bank in a single tap. Nothing extra is stored to make this work; it is read from your own request history.
Currency
The chip beside How much? shows the currency the request will be raised in. It defaults to your business's own currency, and opens the same currency picker the document forms use — any currency, with live rates. Whatever you choose is stamped on every line of the request.
On the whole request
| Section | Required? | Notes |
|---|---|---|
| Project | No | Ties the spend to a project. If you have no project access, the card says so rather than showing an empty picker. |
| A note for your approvers | No | Context that helps it get approved faster. |
| Attachments | No | Invoices, quotes, receipts — anything that backs the request up. |
Purpose and amount are the only required fields. Everything else can be left to the approver or filled in later.
An invoice attached now is one question fewer later.
If anything is missing the footer says Please fix the highlighted fields and the offending fields are marked. Otherwise the request is created and you land straight on its request page.
Reusing a past request
On a wide screen a rail of Your recent payment requests sits beside the form — the last six, each with its number, total and status. Use again copies that request's lines into the form you are filling in, ready to edit. The same is available from an existing request as Duplicate as new.
What happens next
| Stage | What it means |
|---|---|
| Awaiting review | Submitted. Waiting for a reviewer. |
| Awaiting approval | Reviewed. Waiting for the approver(s). |
| Approved | Cleared. It can now be posted as a payment, or converted. |
| Paid | Posted — recorded against the ledger. |
| Converted | Turned into an Expense or a Bill instead. |
An approved payment request has two possible endings — post it, which records the payment, or convert it into an Expense or a Bill that Purchases then settles.
Open it from Spend home or from the list. The request page shows a stage marker — "Stage 2 of 4 — approval ahead" — rather than a roster of names. If it has been sitting too long, Remind approvers nudges whoever it is waiting on.
Related
- The request page — what you see once it is raised
- Approve a request — how the decision is made
- Post a payment — the ledger moment
- Convert a request — turning it into an Expense or a Bill
- Spend — the whole module