What they have in common
One set of approval rules, not three
A voucher, a purchase order and a grant payment are different documents with the same question behind them: who is allowed to say yes to this amount? You define that once. Every request type obeys it, so finance does not maintain three sets of limits that drift apart.
Limits that hold when nobody is watching
Amount thresholds, departmental scope and separation of duties are enforced as the request moves, not checked afterwards. Somebody who submits a request cannot approve it, and an amount above a limit routes upward on its own.
The same audit trail at the end
Whatever was spent and whoever approved it lands on one tamper-evident trail — the same one your auditors, your board and your donors are shown. No module keeps its own private history.
What each one adds
Each is bought and switched on separately. Everything above is true of all of them.
Novorit Payables
Money going out to a supplier, a staff member, or a bank.
Payment vouchers from submission through finance validation to sanction, with a bank-ready instruction at the end and the payment evidence — reference, value date, receipt — recorded against the voucher afterwards.
Explore Payables →Novorit Procurement
Money committed before it is spent.
Purchase orders with their vendors, line items and delivery terms, reviewed by the department head and issued to the supplier from one record — so a commitment is visible long before the invoice arrives.
Explore Procurement →Novorit Grants
Money that came with somebody else's rules attached.
Restricted funds tied to their grant and budget line, burn tracked against each donor's restrictions, and a donor-ready report produced in the grant's own currency — from the same approvals finance already runs.
Explore Grants →