Approvals by amount
The customer asks: Purchase orders or transfers over an amount need approval
- Verdict: Ready, with limits (1)
- Door: Configure · area: Documents and print › Approvals
- Recipe: Approvals by workflow, with a nightly export
- Sample: S11 — price-change approvals with a nightly export
- Checked: carried 2026-10-16 · not re-run
What you build
A workflow on the document, with an approval step by amount. Configuration only.
Limits
- Who may edit a record in a workflow state is checked in the browser only: follow the four safeguards in chapter 13a.
Tell the customer
Documents over the amount wait for the approver before they can be submitted.
What next
- Tell the customer the 1 limit above, and write it into the proposal.
- Follow the recipe: Approvals by workflow, with a nightly export.
- Copy the sample: S11 — price-change approvals with a nightly export, and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
- Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.
Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.
Related needs
- The approver must give a reason when rejecting a purchase order, and it is kept on the document — Ready, with limits (4)
- An e-mail at each approval step with the purchase order's PDF attached, and the uploaded CSV — Ready, with limits (4)
- Each store's purchase orders or transfers are approved by that store's manager — Ready, with limits (1)
- Fields cannot be changed once the document is approved — Ready, with limits (1)
Start a project shortlist with this need · Put it in your blueprint · Every need