Every vendor, every approval, on one record.

Between the ERP and the email inbox lives a layer of processes every enterprise runs and no package fits: approvals with real routing logic, vendor onboarding with real compliance steps, budget requests with real accountability. Today that layer is held together by forwarded emails, a shared spreadsheet with a colour code and one person who remembers where the request went. When that person is on leave, the process stops. When audit asks who approved what, the answer is an inbox search.

Workflow & Procurement is that layer, built properly. It is a configurable workflow engine with the back-office objects already in it — approval hierarchies, vendors, purchase orders, contracts, compliance checklists — and an audit record of every action. Trained admins model a new process themselves. The ERP stays the ledger. Workflow & Procurement runs the process the humans actually touch, and records every step of it.

The request sits in an inbox for three days because the approver is travelling. It is forwarded to a deputy who is not sure they are allowed to sign. It is approved in a reply-all that nobody files. Six months later, audit asks who authorised the spend, and the answer is a search through a mailbox that has since been archived. None of this is anyone’s fault; it is what happens when a process with real rules is run on a tool with none.

Workflow & approvals is the Workflow & Procurement module that gives those rules a home. Routing conditions, approval limits, delegations and escalations are configuration, versioned and dated. Every decision lands on an append-only record with actor, timestamp, context and comment. Approvers work from one inbox, on desktop or phone, and the time each request spends with each of them is measured. Approval cycle time, the share of approvals still running over email and the number of requests without an owner are the three numbers your instance reports.

It does when the documents arrive by email, the compliance checklist is a spreadsheet, and the person who knows which certificate is missing is in another building. The same vendor’s insurance certificate expires eleven months later and nobody notices until a PO is blocked — or worse, until it is not. Contracts auto-renew because the renewal date lived in someone’s calendar. The ERP records the postings faithfully and has no idea any of this happened.

Vendor & procurement is the Workflow & Procurement module that puts the whole lifecycle on one record. Vendors submit their own documents through a portal and see where they stand. Compliance checklists are configured to your regime and gate the approval. Certificates carry expiry dates that prompt renewal before they lapse. Purchase requests show the budget line at the moment of decision and post to the ERP only once approved. Contracts carry owners and renewal dates, so a renewal is a decision rather than an accident. Onboarding time, the share of active vendors with current compliance documents and the number of certificates caught before expiry are what your instance reports.