What workflow does
With workflow, you define what happens to a document after someone creates it. Predictiv moves a purchase requisition, a purchase order, a supplier payment, a stock count variance or a cash-up difference through statuses your business defines. At each status, Predictiv checks which actions are allowed, which roles may take them, and what must be true before they can.
You define the rules in configuration, not in code. Statuses, actions, transitions and the conditions on them are set up in the ERP, so a change to your approval policy is a change to a setting.
Why it matters
When an approver does not know a document is pending, purchasing, payments and deliveries are held up. When someone bypasses an approval, your controls are weakened. Predictiv removes both problems with workflow. It routes each document along the same path every time, and notifies the next person as soon as the document is routed to them.
What you can do
- Set thresholds. Use conditions on the document, such as its value, type or organisation, to set whether it needs approval and at which level.
- Separate duties. Access to each transition can be limited by user, role and organisation. The person who raised a document cannot approve it, and nobody can approve their own variance.
- Work from one queue. Predictiv places every pending action in one queue for the person or role responsible, with a priority and a colour you configure. Each entry links straight to the record, on a desktop or a phone.
- Notify and escalate. Predictiv can send a notification at each action, from a template you control, and escalates an item when its service-level timer expires, so work does not stall with one person.
- Approve anywhere. Approvers can approve or reject from the ERP window, from the Predictiv Assistant in chat, on a phone, or in Atrium. Predictiv applies the same transition rules and the same checks on every channel.
- Record every decision. For each transition, Predictiv stores who acted, when, from which status to which, and any comment. The record is part of the document’s history, not a separate log.
Where workflow is used
Predictiv uses workflow in many of its controls. Purchase requisitions and orders are routed for approval in procurement. Supplier payment packs are checked and then released through an approval step in finance. Stock count variances in inventory and cash-up variances in direct store delivery are sent for approval above a threshold, and never to the person who caused them. Maintenance work orders in maintenance use supervisor approval, notifications and escalation.
What makes it different
Many ERPs add approvals as a separate tool, or email the approver a request to log in somewhere else. In Predictiv, workflow is part of the record. The approval step is part of the document itself, the queue is next to the work, and the same rules apply whether someone approves at a desk, in chat or on a phone.
Because the AI assistant uses those same rules, it offers only the actions that are valid for the document’s current status and the person’s role. It cannot approve anything the person could not approve on screen.
How it connects
Workflow uses the platform’s identity, roles and audit trail described under security. Predictiv turns documents uploaded through documents into draft records and routes them through their workflow like any other. People on the move receive notifications and approvals through mobile and offline access and Atrium.