PRC.01Standard
Purchase orders
Pending, Approved, Partial, Received, Closed, Cancelled — with received quantity tracked per line, so a part-delivered order says exactly which lines are still outstanding instead of sitting at “open”.
Procurement, RFQ and vendor portal software
Purchase orders, partial receipts, a two-stage payment approval, and a vendor portal that vendors run themselves — with the checks that stop an order being overpaid.
Procurement modules
- Standard
- Configurable
- Custom scope
PRC.02Standard
Goods receiving
Receipts record the delivery note number, vehicle, driver and transporter, and carry backorder quantity per line. Stock moves on the receipt, not on the order.
PRC.03Standard
Purchase payments
A two-stage chain: Submitted → Manager Approved → Approved, each stage stamped with who and when. Withholding tax, the vendor bank and IBAN snapshot, and the uploaded transfer receipt all travel with the payment.
PRC.04Standard
Vendors
Categorised by the fields they supply, with certificates on file and an approval state per application. Approving or rejecting one sends the vendor a templated email you can edit yourself.
PRC.05Configurable
Vendor portal
A separate application on its own login, deliberately isolated from staff sessions. Vendors register themselves, pick the categories they want to be invited for, and upload their certificates.
PRC.06Custom scope
RFQs & bidding
Publish a request for quotation with a deadline and target cities or countries; eligible vendors are found by explicit invite, category match or location. Vendors bid in the portal, and every recipient is tracked — emailed, failed, or opened.
PRC.07Standard
Procurement requests
Any quotation line flagged as needing procurement surfaces here as a buy request, showing live whether a purchase order has been raised against it yet.
Procure to pay, without paying twice
Purchasing goes wrong in predictable places: an order is paid twice because two people approved separately, goods arrive in part and nobody knows what is outstanding, and vendor details live in an inbox. The Procurement workspace is built around those failure points.
Purchase orders track received quantity line by line. Stock moves when goods are received, not when the order is placed. A payment passes through two recorded approval stages, and the final stage checks the balance still owed on the order before it clears. Vendors register themselves in a separate portal on its own login, upload their certificates, and bid on your requests for quotation — and you can see who was emailed, who opened it and who bid.
Common questions
Do vendors log in to the same system as our staff?
No. The vendor portal is a separate application on its own login, isolated from staff sessions. Vendors can register, upload certificates and bid on RFQs, but cannot reach any internal record.
How are RFQ recipients chosen?
Eligible vendors are found by explicit invite, by category match, or by location (target cities or countries). Every recipient is tracked as emailed, failed or opened, and you can compare bids when the deadline passes.
Who approves a purchase payment?
Approval authority comes from the organisation chart — the direct and operational manager recorded on the employee — not from a powerful role. Each stage records who approved and when.
See it running on your own documents
Tell us what your company does and which modules you would actually use. We will walk you through the system handling your work — not a slide deck.