Manager approval always. Finance approval only when the number warrants it.
A real approval chain, not a form that emails somebody. An employee submits what they want to buy, from whom, for how much, and why. Their manager decides first. If the amount hits your finance threshold, a second approval routes to finance, genuinely sequential, not a copied-in email. Once it clears, procurement is told to raise the PO and the requester gets the green light. Rejections come back with the reason so they can revise instead of re-asking.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Where employees submit a purchase for approval: requester, department, item, quantity, vendor, amount, justification, optional quote. Publishing it auto-creates the Purchase Requests response sheet, the single system of record.
Emails the requester the outcome, with the reason and next steps.
Logs the request and walks it through the chain (manager first, then finance on high-value spend) before notifying procurement and emailing the requester the decision.
You connect your own accounts. Swap any app that offers an alternative at install.
Posts the manager and finance approval requests (with the secure review link) and notifies your procurement channel when a request is approved. Swap for Microsoft Teams, Google Chat, Telegram or Discord.
Emails the requester the decision on their purchase request. Swap for Microsoft Outlook or Brevo.
The Purchase Request Form captures the requester, department, item, quantity, vendor, amount, business justification, and an optional quote, and opens a request record the instant it's submitted. Nothing lives in a DM. Every request starts on the same row it'll finish on.
An approval message goes to the requester's manager in Slack with the full request (item, vendor, amount, justification, quote) and a secure link. Approve or Reject. A rejection here is recorded on the row and the requester is emailed the reason, so the loop closes immediately rather than after a week of silence.
If the amount is at or above the finance_threshold you set at install, a second approval routes to finance for sign-off. Below the threshold, the manager's approval is enough and the request moves straight on. That's the whole governance model in one setting: small spend moves fast, large spend gets a second pair of eyes.
Once fully approved, the request posts to your procurement channel so a PO can be raised, the row is stamped approved, and the requester is emailed the green light. Any rejection (manager or finance) is emailed back with the reason attached, so the next version is better rather than identical.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
