Most organizations run one order through five tools. Here is the same order run through one: 200 bags of cement, from the request on site to the line on the report — nine stages, every record linked to the one before it.
None of these tools is wrong on its own. The cost is in the gaps between them, where someone has to carry the information across by hand, and where the numbers start to disagree.
| Stage | Usually lives in | In AWRA |
|---|---|---|
| Request | A WhatsApp message or a phone call | A request against the item master |
| Approval | A reply-all, if anyone can find it | A stamped decision on the request |
| Procurement | Three PDFs and a spreadsheet | An RFQ, compared quotes and a PO |
| Receiving | A paper delivery note in a drawer | A receipt against the PO, signed |
| Inventory | Stock_Count_FINAL_v3.xlsx | A live count per warehouse and bin |
| Sales / POS | A till, a receipt book, a second sheet | An invoice or POS sale off the same shelf |
| Payments | A bank statement and a phone | A payment matched to its order |
| Accounting | Month-end re-keying from exports | Journals written as the work happens |
| Reporting | A board slide nobody can reproduce | Reports read from the same records |
Each stage shows who does it, what AWRA records, and the record it links back to. That last line is the whole argument: it is what turns nine screens into one audit trail.
Site B asks for 200 bags of cement in AWRA instead of a chat. The item comes from the item master, so the request names the same product stores and finance will see later.
A manager with approval rights approves it in AWRA. The decision is stamped on the request itself with who made it and when, and workflow rules can notify the next person the moment it lands.
Three suppliers quote against one RFQ, through the vendor portal or entered by the buyer, and are compared side by side on price, lead time and terms. The winning quotation is approved and becomes the purchase order.
Stores receive the delivery against PO-0311 — on the web, or on the Android app at the loading bay with no signal — record what arrived, and can capture a signature from whoever handed it over.
Stock rises when the receipt posts, at the warehouse and bin it was put away in. Procurement, sales and finance all read this one count, and reorder alerts watch it from here on.
The same bags are invoiced to a contractor or sold at the counter. Each sale takes them off the same shelf, so the count stays true while the queue keeps moving.
The supplier is paid against the order and the receipt. Customers pay by card, cash or M-Pesa, and each receipt settles the invoice it belongs to.
Receipts, sales and payments each write their own double-entry journal as they happen. The ledger is a result of the work, not a separate round of data entry at month end.
Reports, scheduled digests and Awra Intelligence read the same records: cement nearing a stock-out, a supplier whose deliveries run late, a customer slow to pay.
A connected flow is only worth trusting if it refuses the shortcuts. These three are not reports you read afterwards — they are refusals at the moment someone tries.
A purchase order in AWRA is always raised from a quotation, and the quotation has to be approved first. There is no standalone form that skips the RFQ, so every PO can be traced back to the quotes it beat and the request that started it.
Nobody can bypass it. It is a property of how a PO is created.When stores record a receipt against a purchase order, AWRA compares it with what is still outstanding on that order. An over-receipt is refused, on by default with zero tolerance, so surplus stock cannot quietly enter the count.
The tolerance is a workspace setting, so the rule is a decision rather than an accident.Before a supplier payment goes out, AWRA checks it against the order and what was received. A discrepancy holds the payment. It can still be released, but only by someone holding the override permission, and only with a written reason that stays on the record.
Override is a separate permission from paying, so the person who pays is not automatically the person who can excuse a mismatch.Approval itself is controlled by permission: only people whose role carries approval rights can approve a request. Budgets are checked when an RFQ is approved and an overspend is flagged to the approver. See budget controls and audit trail integrity.
In most organizations accounting is the last stage and the slowest one, because it starts by re-typing everything the other eight stages already did.
In AWRA, the events that move money post their own double-entry journal at the moment they happen. Each journal names the document that created it, so a figure in the general ledger is one click from the receipt, invoice or payment behind it.
Finance still reviews, reconciles and closes. What goes away is the month-end round of exporting from operations and keying it back in — the step where most of the disagreement between stores and finance is born.
An audit trail is only useful if it answers the questions people actually ask. Because every record links back to the one before it, each of these is a click rather than an investigation.
Open PR-0142: the approver and timestamp are on the request.
RFQ-0087 holds all three quotes and the comparison that awarded it.
GRN-0219 sits against PO-0311 line by line, and PAY-0098 was checked against both.
Every movement out of WH-01 / A-04 names the sale or transfer that caused it.
PAY-0098 links to the PO and the receipt it was matched against.
Every journal names the document that posted it, one click back to the source.
Everyone works in the same system, but not on the same screens. Roles and permissions decide who can raise, approve, buy, receive, sell and pay, so the record is shared while the authority is not.
| Role | Request | Approval | Procurement | Receiving | Inventory | Sales / POS | Payments | Accounting | Reporting & AI |
|---|---|---|---|---|---|---|---|---|---|
| Site supervisorRaises the request | |||||||||
| ApproverApproves or rejects it | |||||||||
| BuyerRuns the RFQ and issues the PO | |||||||||
| StorekeeperReceives, puts away, counts | |||||||||
| Cashier & salesInvoices and sells from stock | |||||||||
| FinancePays suppliers, reconciles, closes | |||||||||
| ManagementReads the reports and the signals |
Scroll the table sideways to see every stage.
Cement is one example. The same pattern — each step created from the one before, ending in the ledger or the report — runs through people, spend, projects and assets.
Hours and leave feed the payroll run, the run is paid through the payments register, and the payment posts to the ledger.
Explore people & payrollA claim is approved by someone with approval rights — never its own author — then paid and posted.
Explore expensesHours and purchases booked to a project are measured against its budget as they land.
Explore projectsEquipment received as stock becomes a tracked asset with a custodian and a place on the fixed asset register.
Explore assetsNo. It is an illustrative example, and the record numbers are made up. The stages, the links between records and the three refusals are how AWRA actually behaves.
Three refusals built into the chain. A purchase order can only be raised from an approved quotation. A receipt larger than what is outstanding on the order is refused. And a supplier payment that does not match the order and receipt is held until someone with the override permission releases it with a written reason.
No. Most organizations start with inventory or procurement and switch on sales, finance or HR later. The records link up as each module is turned on, and nothing has to be re-entered when it is.
Posting does. Goods receipts, customer invoices, POS sales, customer and supplier payments, approved expenses and payroll payments each write a double-entry journal when they happen. Finance still reviews, reconciles and closes; what goes away is re-keying the same events from exports.
AWRA can sync to QuickBooks, and the sync health view shows what went through, what failed and why, so the two do not drift apart unnoticed.
The Android app keeps working. Receipts, counts and adjustments queue on the device and sync when the connection returns, and anything that conflicts is raised for a person to settle rather than overwritten.
Yes. Book a demo and we will walk your own request-to-report flow through AWRA, with your items, approvers and warehouses.
Bring one real order — your items, your approvers, your warehouses — and we will walk it through every stage on this page with you.
