Procure-to-pay
A controlled path from request to payment. Requisition, purchase order, goods receipt, supplier invoice — and no payment until the three agree.
What it does
Requisition and approval
Spend is requested and approved against limits before a commitment is made.
Purchase orders
An approved requisition becomes an order to a vendor, with the commitment visible.
Goods receipt
What arrived is recorded, including short or damaged deliveries, rather than assumed to match the order.
Three-way match
Order, receipt and invoice are matched before payment. A mismatch stops the payment rather than flagging it afterwards.
Vendor management
Vendors are approved records with their own history, not free-text on an invoice.
Withholding at invoice
Qualifying invoices carry withholding tax at the point they are raised.
How it works
The sequence an operator actually follows, not a feature list rearranged into steps.
- 1
Someone requisitions; an approver within limit approves it.
- 2
A purchase order is issued to an approved vendor.
- 3
Goods or services are received and the receipt recorded.
- 4
The invoice arrives, is matched against order and receipt, and only then becomes payable.
What the database guarantees
These hold whether or not the interface remembers to check.
- Approval limits are enforced in the database, not by hiding a button.
- An invoice that fails three-way match cannot proceed to payment.
What it does not do yet
You will ask this in an evaluation, so here it is without being asked.
- No supplier portal — vendors do not log in to submit invoices.
- No punch-out or catalogue integration.
Works with
These share the same database, so nothing is re-keyed between them.
Double-entry accounting
A real ledger, with immutable postings
Ghana VAT & withholding
Levies, VAT and WHT, applied at source
Facilities & maintenance
Assets, PPM, SLAs, statutory compliance
Leases & tenancies
Ghana-specific agreements and lifecycle
Commercial leasing & CAM
Service charge, apportionment, reconciliation