Skip to main content

Automate purchase requisitions: from informal requests to a traceable approval process

Capture requirements using a form, route approvals by amount threshold and cost centre, and send Purchasing a complete purchase order with approval history.
Industry: Finance
Department: Finance

Why purchase requests sent by email or word of mouth get lost

A colleague needs new hardware; a team needs a software licence. Requests arrive by email, Teams message or hallway conversation, sometimes with a cost centre and sometimes without. A manager receives the approval request in their inbox, while someone checks the budget on the phone in passing.

Purchasing then places orders with incomplete information. Later, it is difficult to establish who approved what and when. An internal audit or year-end closing triggers a search through old email threads.

The underlying issue is usually a missing workflow: nobody has defined the information a request must contain or who is authorised to decide above each amount threshold.

How swoox.io digitises purchase requisitions

With swoox.io, every purchase requisition starts with a structured form. Need, cost centre and amount are mandatory fields, so all essential information is available from the start. The process validates the entries and routes the request according to fixed rules: below the threshold, one approval is enough; above it, a second person must also approve. Every decision is logged. Finally, Purchasing receives a complete purchase order with its approval history.

Technically, the workflow is a BPMN 2.0 process that business teams can read and adapt themselves. Amount thresholds, approval levels and form fields are configured without development. ERP or controlling systems are connected via interfaces during implementation.

What is the agent allowed to do?

Platform Level
The role- and permission system defines who can submit requests, who can approve them and who can change the process. Requesting and approving remain separate responsibilities.
Process Level
The BPMN process is an explicit graph. The amount threshold is visible as a gateway, so everyone can see when the second approval level applies.
Agent Level
Whenever money is involved, a person makes the decision. Approval is a dedicated process step with an input form, deadline and log.
If AI agents are added later—for example, to pre-qualify requests—they work within the same control framework. The process defines what an agent may do and where a person must decide.

The purchase requisition process, step by step

(Example workflow – each process is unique)

  1. An employee submits a request through the purchase requisition form, including cost centre, amount and justification.
  2. The process checks that the information is complete and starts the workflow.
  3. A gateway routes the request according to the amount threshold and cost centre.
  4. The responsible manager receives the request in their approval screen. A person makes the decision because the budget is affected.
  5. If the amount exceeds the threshold, a second approval level starts automatically.
  6. Once approved, swoox.io creates the purchase order from a template.
  7. Purchasing receives the order with the complete approval history.
  8. Every step is documented in the process log.

Results: complete requests, verifiable approvals

  • Requests arrive complete, eliminating follow-up questions.
  • Approvals follow defined levels.
  • Who approved what and when can be verified at any time.
  • Purchasing orders only on the basis of checked and approved requests.
  • Covering colleagues can see open cases and continue working immediately.
  • Business teams can adjust amount thresholds and forms themselves.

Why swoox.io for SMEs?

swoox.io runs on-premises or as PaaS in the EU, with SSO/MFA and a role- and permission system that even a small IT team can manage. Process data stays in your own environment, and your organisation chooses the operating model.

The same foundation supports further workflows such as leave requests, invoice approvals or onboarding. Business teams model them with low-code on BPMN 2.0; IT operates the platform.

If AI is added later, swoox.io is not tied to a single provider. Models such as ChatGPT, Claude or Llama can be integrated without changing the process.

Frequently asked questions about purchase requisitions

What is a purchase requisition?
A purchase requisition is an internal request to Purchasing, including the cost centre, amount and justification. It is the starting point of procurement: the need is submitted and approved first, and Purchasing places the order afterwards.
Does swoox.io replace our ERP?
No. Ordering and posting remain the responsibility of your ERP. swoox.io manages the workflow leading up to them, documents every approval and retrieves cost centres and budgets from your system via an interface. The integration is configured during implementation.
Can business teams adapt the approval process themselves?
Yes. Amount thresholds, approval levels and form fields are modelled in BPMN 2.0 and can be adjusted without programming skills. The permission system defines who is allowed to make changes.
What happens if an approval is delayed?
The request remains visible as an open process step. You can define deadlines and delegation rules so that no request gets overlooked.
Can the process be operated in compliance with the GDPR?
Yes. You can run swoox.io on-premises or as PaaS in the EU, depending on your operating model. Access is controlled by the role- and permission system, and personal data remains in your own environment.
Get to know swoox.io

We’d be happy to show you how easy and flexible process automation with swoox.io can be.
Or you can try it out for yourself.