The request page
Everything one Spend request carries — the header, the lines, the stage, the conversation, and the actions available on it.
Every request — payment, requisition or advance — opens on the same page at /payment-requests/{id}. It is where the request is read, discussed, decided, and settled.
The header
The title reads the workflow and the request number — Payment Request #PR-000315 — with the current status beside it, and underneath: who raised it, the date, and the total.
The actions on the right change with the request's state and your rights:
| Action | Appears when | Who |
|---|---|---|
| Approve · Decline | The request is awaiting review or approval | Administrators and Super Administrators |
| Post payment | The request is approved | Administrators and Super Administrators |
| Convert | The request is approved and is not an advance | Administrators and Super Administrators |
| Retire | It is an advance that has not been fully retired | Anyone who can open the request |
| Share | Always | Anyone who can open the request |
| More (⋯) | Always | Anyone who can open the request |
| Item | Notes |
|---|---|
| Remind approvers | Hidden once the request is declined, paid, converted or retired — there is nobody left to chase. |
| New request | Opens the raise picker. |
| Duplicate as new | Opens the same workflow’s form with this request’s lines already filled in. |
| Export PDF · Export Excel | The request as a document or a spreadsheet. |
| Prints the PDF. | |
| Delete | Administrators only, and confirmed first. Permanent. |
The lines
The main card lists what was asked for. Its title follows the workflow — Payments, Items requested or Advance — and each line shows its own status badge, because decisions happen per line.
| Workflow | Each line shows |
|---|---|
| Payment Request | The purpose, then the beneficiary, bank and account number underneath (or the line note if there are no bank details), then the amount. |
| Requisition | The description, then quantity, priority and the required-by date. No amount — a requisition is not priced. |
| Advance | The purpose and the amount. There is only ever one line. |
The card foots with the number of lines and the request total.
Payout details
A payment request also carries a Payout details card — each beneficiary with their bank's logo, account number and amount, so the person posting can see where the money is meant to go without opening the lines again.
The transfer itself happens in your bank. Post payment is what records it against your ledger. See Post a payment.
The conversation
Below the lines sits an always-open thread. Anyone who can open the request can post to it — questions, context, the reason behind a decision.
- Enter sends, Shift + Enter starts a new line.
- Your own messages sit on the right; everyone else's on the left, with their name and the time.
- Approving or declining also writes the decision note into this thread, so the record of why lives beside the request rather than in somebody's inbox.
The rail
| Card | Shows |
|---|---|
| Where it is | The stage marker and a Remind approvers button. |
| Summary | Requested by, date, total, and the project if one was linked. |
| Retirement | Advances only — advance, retired, returned, balance, and the deadline. |
| Converted to | Once converted — the document type, its number, when, and by whom. |
| Attachments | Whatever was attached when the request was raised. |
The stage marker
Progress is shown as a stage, not as a list of people: Stage 3 of 4 — paid ahead. The stages differ by workflow.
| Workflow | Stages |
|---|---|
| Payment Request | Raised → Review → Approval → Paid |
| Requisition | Raised → Review → Approval → Converted |
| Advance | Raised → Review → Approval → Collected → Retired |
Where your approval rules require more than one approver, a second line appears underneath — Approval · 1 of 2 recorded — so the requester can see the request is moving even though it is not yet approved.
The stage marker deliberately never names who a request is waiting on. Chasing an individual is what Remind approvers is for, and that emails the whole active approval team rather than singling anyone out.
If the request cannot be opened
A request id that does not exist, or one that belongs to another business, shows Request not found — it may have been deleted, or you may not have access, with a way back to the list. A request from another business is never confirmed to exist.
Related
- Share a request — sending it to someone without an account
- Approve a request — the decision, thresholds and reminders
- Post a payment · Convert a request · Retire an advance
- Track requests — finding a request in the first place