Purchase request approval: Finance first, Management above 5,000
A purchase request's amount decides its path: Finance reviews the quote, 5,000 and over also needs Management, with the quote required as evidence.
Updated · 7 min read
In short
- A purchase request today is usually a quote forwarded in an email or a chat message, approved with a reply and no attached proof once the thread scrolls away.
- DueReason's payment template reads the amount on the request and routes it by itself: nothing under 100 needs a person, 100 to 4,999 needs Finance, 5,000 and over adds Management after Finance.
- The quote or invoice is required evidence on the Finance step, not an attachment someone might forget to forward, and the person who filed the request can never be the one who approves it.
- Once decided, the request produces a signed, verifiable record naming the amount, the payee and who approved it - something a forwarded email thread never does.
A purchase - a vendor quote, a software renewal, a one-off order - usually gets approved the way it gets asked: a message to whoever signs off on spending, a quote attached or pasted in, a reply that says go ahead. The record of that approval is whatever is left in the thread once it scrolls past, and the amount that actually needed a second sign-off is whatever the approver remembered to check, not a rule anyone wrote down.
The amount decides the path, automatically
DueReason's payment template (action key payment, in core/src/approval-templates.ts) reads the amount field on the request and picks the workflow for it:
| Amount | Steps |
|---|---|
| Under 100 | Auto-approved, no person involved |
| 100 to 4,999 | Finance reviews, with the invoice as required evidence |
| 5,000 and over | Finance reviews with the invoice, then Management approves with a written reason |
Nobody has to remember which quotes are "big enough" to escalate - the request names the amount, and the template's conditions pick the workflow for it the same way on every request, not just the ones someone happens to flag.
The quote is evidence, not an attachment someone might skip
The request carries the amount, currency, payee, an optional IBAN, a purpose and an invoice URL; on the 100-and-over workflows, Finance's step requires document evidence, so the request cannot be approved without the quote or invoice attached to it. That is the difference between "I'm pretty sure someone looked at the quote" and a decision record that still has the quote attached to it next quarter.
Segregation of duties, not just a second opinion
Whoever files the purchase request is never one of the people who can approve it, on every request DueReason handles, not only payments. Finance and, above the threshold, Management are answering someone else's request every time - the rule the discount exception and expense/policy exception templates also enforce, not a payments-specific exception.
The away rule
A Finance or Management step that needs exactly one approver can be reassigned to someone else in that same group for a single open request, if the usual approver is away - an owner, admin, or another eligible approver does the reassignment. Nothing about the 5,000-and-over workflow needing two separate steps changes who has to sign off; it only changes who has to be available to do it, and a stand-in is always a real person in the right group, never a rule that skips the step.
The record once it is decided
A decided purchase request produces a signed grant bound to the exact amount, payee and purpose that were approved, and the request can produce a record - JSON or CSV - at any point, including while it is still pending. DueReason never moves the money itself: it records who approved what and why, and issues the signed grant once Finance (and, above the threshold, Management) have answered; actually paying the invoice still happens in whatever banking or payment tool your organization already uses. A recurring purchase - the same vendor, amount and purpose on a schedule - can be filed automatically on a cadence instead of re-typed every time, through the same workflow's recurring-request setting.
What this does not do
DueReason has no accounting-system connector that creates the purchase itself, and no built-in way to turn an approved request straight into a bill in Xero or QuickBooks - a worked example wires that up with a webhook and a no-code tool instead of a native integration, reading the same amount, payee and invoice fields off the approved request.
Questions
- Can I change the 100 and 5,000 thresholds?
- The thresholds are set on the payment workflow's conditions when it is installed for your organization - editing them is a change to the workflow, not a field on the request form itself.
- What happens if Finance approves but forgot to attach the quote?
- It cannot happen: the 100-and-over workflows require document evidence on the Finance step, so the request has nothing to approve without a quote or invoice attached to it.
- Does DueReason actually pay the invoice once it is approved?
- No. It records the decision and issues a signed grant once the required approvers have answered. Moving the money, and creating the accounting entry, still happens in your own payment and accounting tools.
Give purchase requests a threshold, evidence and a record
Create an account, install the payment template, and let the amount on each request decide whether Finance alone or Finance plus Management signs off - with the quote attached and a record you can still produce later.
Create your accountSources
This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.