Requests move, but accountability does not.
Approvals sit across email and chat, with no dependable queue, owner, rejection reason or history.
Procurement, purchasing & inventory systems
Follow every purchase from need to receipt, payment and stock.
We design connected procurement systems for mission-led and commercial organisations: purchase requests, budget checks, vendors, quotations, approvals, purchase orders, goods or service acceptance, invoices, payments, inventory and audit trails.
What breaks today
A purchase loses control when each team sees only one part.
Email, spreadsheets and accounting tools can each hold a fragment without showing the full commitment, the current exception or who needs to act next.
The budget is checked after the decision.
Backdated requests and late purchase orders make it difficult to see committed spend before cash leaves.
Receipt, invoice and stock do not share one reference.
Teams reconcile goods, services, bills, payments, assets and stock by hand because the chain breaks after the PO.
See it working
Three screens your teams would use every week.
A procurement system earns its place when a requester, an approver and the stores team each open it and see the same purchase, at the stage it has actually reached.
PRClassroom kits · samplePR-0142 · programme: education · site: sample
Purchase request raised, budget head linkedSubmitted
3 vendor quotations comparedRecorded
Lowest quote not chosen, reason requiredHuman decision
Goods receipt: 180 of 200 kits acceptedPartial
One reference from need to stock. Quotes, approvals, purchase order and receipt on the same chain.
5 purchase requests in your rangeDue
1 request missing a quotationWaiting
2 purchase orders ready to issueReady
1 invoice above PO valueCheck
A queue with reasons. Every rejection and exception is recorded, not lost in chat.
142classroom kits in stock at the sample warehouse
- Opening
- 40
- Goods in
- 180, PO-linked
- Goods out
- 78 distributed to sites
- Last count
- Verified by stores lead
Receipt is not the end. Goods in, goods out and the closing balance trace back to the purchase.
Illustrative screens with sample data. Not a live partner record.
Request-to-reconciliation
One traceable chain, with the right control at each handoff.
The exact policy differs by organisation. The underlying records and decisions repeat.
- Need and purchase request
- Budget, policy and sourcing route
- Vendor, quotations and selection
- Approval and purchase order
- Receipt or service acceptance
- Invoice, payment and reconciliation
For physical goods, the chain continues into stock, warehouse or asset custody. For services, acceptance can be a milestone, timesheet or completion confirmation.
Configurable controls
Make policy executable without hard-coding today’s org chart.
Thresholds, roles, states and documents should be configurable so the workflow can change without rebuilding the application.
Request and budget context
Purpose, entity, programme, project, grant or cost centre, budget head, quantity, dates, delivery location and supporting evidence.
Vendor and quotation governance
Controlled vendor onboarding and changes, compliance documents, categories, prices, lead times, quotation comparison and selection rationale.
Approval matrix and segregation
Role-, department- and value-based routes, delegated authority, no self-approval, rejection reasons, resubmission and a visible decision history.
PO and commitment control
Numbering, terms, advances, credit periods, amendments, versions, partial fulfilment, committed value, remaining balance and formal closure.
Goods and services
Use one control model without pretending every purchase is the same.
The request, sourcing, approval and commitment records can be shared. Acceptance evidence must follow what was actually bought.
Two paths after the PO.
A clean design branches at fulfilment, then rejoins for invoice validation and payment.
Physical goods
Quantity and quality checks, goods receipt note, batch or serial details where needed, returns, warehouse/location, stock or asset update.
Services and milestones
Deliverable, milestone, period or timesheet confirmation, accountable service owner, exceptions and evidence of acceptance.
Invoice control
Match the invoice to the approved PO and receipt or acceptance, including partial invoices, advances, taxes and balance checks.
Accounting handoff
Send validated records to the authorised finance process or tools such as Zoho Books, Zoho Expense or Tally, with reconciliation status.
Inventory, warehouse & assets
Receipt is not the end of the process.
When the organisation buys physical goods, purchasing must connect to custody, movement, valuation and reconciliation.
Item and location masters
Categories, SKUs, variants, units of measure, preferred vendors, warehouses, locations, reorder rules and responsible users.
Goods-in and stock book
PO-linked receipts, grading or quality, accepted and rejected quantity, opening stock, goods in, goods out and closing balance.
Transfers and adjustments
Warehouse transfers, packaging or unit conversion, wastage, returns, stock-taking differences and authorised corrections.
Operational reporting
Pending approvals, cycle time, committed versus actual spend, open POs, receipt variance, stock position, ageing, reorder and vendor performance.
How a project runs
What you get at each stage.
Every procurement system follows the same ImpactOS stages and sign-off points, so you always know what is being decided, by whom, and what you will have at the end of it.
- 01
Listen
We trace one real purchase from need to payment and stock with the people who handle it.
You getA map of the request-to-reconciliation chain and where context is lost - 02
Scope
Policy, thresholds and roles first, then the records behind requests, orders, receipts and stock.
You getA locked data model, an honest estimate and a plain list of what would be new for us✓ Scope agreed - 03
Deliver
One purchase route first, tested with real requesters, approvers and stores.
You getA working first release, migrated vendor and item masters with a transformation log, and training in context✓ Design locked✓ Tested - 04
Close
We track whether purchases move through the system, not just logins.
You getHandover, documentation and 30 to 60 days of hypercare after go-live✓ In use - 05
Learn
A retrospective on what worked and what the next release should be.
You getA roadmap for inventory, assets or the accounting hand-off in sequence
Procurement sits inside our finance and operations work. See the five-stage transformation pathway →
Our track record
We haven’t published a procurement case study yet.
What we can show is the adjacent work this builds on: connected operations, approvals and project delivery. We’ll tell you on the first call which parts would be new for us.
Connected operations10+tools connected into one record
Admissions, payments and refunds, learning, Zoom and WhatsApp through one system for The/Nudge Institute.
Read the case study ↗ Project delivery · Zoho ProjectsAria CFO Services
Operational work moved into a shared, accountable system.
Read the case study ↗ Said plainlyWhy we name our limits
Why we tell you up front what we haven’t built before, instead of finding out halfway through.
Read the essay →Adding AI
When the purchase chain is clean, AI can take on the chasing.
Our own products plug into a procurement system once requests, approvals and receipts share one reference. People keep every decision about what is bought and paid for.
DozAI · Run
Missing documents
Document completeness is one of the missions we are shaping: chase every missing quotation, bill or receipt note and hand unclear cases to your team.
Explore DozAI → FundZola · AccountSpend against grants
AI suggests the grant and programme head for each bill from your allocation matrix; you confirm before it reaches your books.
Explore FundZola → Claude · coachingAI for operations teams
Claude coaching for leaders, and AI agents on your own data, with a person still in charge of every decision.
Explore AI for nonprofits →Not sure where AI belongs in purchasing yet?Start with AI for nonprofits →
Questions
What teams usually ask first.
If yours isn’t here, bring it to the first call. We’d rather answer it honestly than have it surface halfway through a build.
Have you built procurement systems before?
Procurement is our newest area and builds on our finance and operations work. On the first call we’ll tell you which parts we’ve built before and which would be new for us. Why we name our limits →
Can one system handle goods and services?
Yes. Requests, sourcing, approvals and purchase orders share one model; acceptance branches into goods receipt or service confirmation, then rejoins for invoice and payment.
Do you replace Zoho Books or Tally?
No. The accounting system stays the source of truth for the books. We send validated records to it with reconciliation status.
Can approval limits change without a rebuild?
Yes. Thresholds, roles, delegated authority and states are configured, not hard-coded.
What will it cost to run, not just to build?
Cost follows records, roles, integrations, migration and support. We show expected running costs, including licences, up front. Eligible nonprofits can access subsidised delivery through the Built for Impact Programme.
Will AI approve purchases?
No. AI can chase documents or suggest tags. A named person approves every request, order and payment.
Design before software
Clarify the operating model first.
The useful first step is usually a real transaction traced across people, decisions, records and tools.
Interactive field guide
Budget, allocation, spend and utilisation
See how money moves across fundraising, grants, programmes and finance.
Open the chapter →Technology assessmentEvaluate what you already use
Decide what to retain, repair, connect, replace or retire.
Read on edzola.com ↗Data architectureOvercome data silos deliberately
Connect authoritative records without forcing every job into one tool.
Read on edzola.com ↗Connected verticals
Procurement sits at several organisational handoffs.
The right connections depend on what is being bought, how it is funded and who will use or hold it.
Trace one real purchase from request to reconciliation.
Bring a PR form, approval chain, PO, receiving problem or stock tracker. We will map where context is lost and identify the first useful system change.