AWRA Help Center
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
What is new, release notes, changelog history, status updates, and product change tracking.
Human Resources — employee records, leave, attendance and time, payroll and payslips, and employee self-service.
Delivery management — projects and tasks, Kanban board and my tasks, planning and Gantt, agile sprints, time and budget tracking, and flexibility (labels, checklists, templates).
Support desk — tickets, department queues, categories and assignment, SLA timers and escalation, the public intake portal, and staff self-service (My Tickets).
Android, iOS, mobile workflows, barcode scanning, scanner bridge, and field operations.
APIs, webhooks, sync patterns, QuickBooks, connectors, and external system implementation.
Trust, security, privacy, compliance, uptime, access controls, and procurement review resources.
Pricing, plans, subscriptions, ROI estimates, billing conversations, and commercial review.
AWRA Academy courses, lessons, assessments, and verifiable certificates — learn the platform module by module.
Implementation, onboarding, migration, demos, training, rollout, and customer success guidance.
Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
Buying — requisitions and approvals, RFQs and quotation comparison, purchase orders and receiving, three-way matching, supplier prequalification, and landed cost.
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Money — chart of accounts and journals, expenses, budgets and controls, vendor payments, the payments register, aging reports, and period close.
Asset register — tagging and custody, assignment and location history, condition and verification, maintenance, depreciation schedules, and disposal.
The supply base — supplier records and documents, performance scoring, the vendor portal and collaboration, and vendor-side self-service.
Seeing the business — the report catalog, BI Studio and custom report builder, saved filters and scheduled reports, dashboards, and predictive insights.
Making the system act — approval workflows, rules and triggers, the unified action queue, exception handling, alerts and notifications, and scheduled jobs.
Core product documentation, module explainers, operating concepts, and platform overviews.
Browse Help Sections
Each article is backed by approved public knowledge and links back to the authoritative AWRA resource for deeper context. Tap a section to expand it.
Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.
AWRA Blog
A customer credit limit here genuinely refuses — past the line the invoice is created on hold. What the number never records is which currency it is expressed in, and the exposure it is weighed against is a sum of invoice balances that each carry a currency of their own.
AWRA Blog
In most of the world the inventory costing method is an accounting preference and any defensible one will do. In the United States it can be a commitment with consequences reaching past the ledger — which makes it the one market where "our system supports exactly one method" is a fact a buyer needs before signing rather than after. We support exactly one.
AWRA Blog
The stock module hides the expected quantity from the counter by default. The till displays Expected Cash to the cashier as a tile on the sale screen. Same product, opposite answers to the same control question.
AWRA Blog
A blind count hides the expected quantity. Doing it properly means hiding three figures rather than one, hiding them in the data rather than on the screen, and hiding the same item everywhere else for as long as the session is live.
AWRA Blog
Overriding a customer credit hold here needs the permission to edit invoices — the same grant that lets somebody change one. Three modules away, an equivalent override was deliberately given a permission of its own.
AWRA Blog
From "we need this" to "the supplier is paid" — the eight P2P steps, the control at each, and the leak that opens when any step is skipped.
AWRA Blog
A refund reversed the sale, returned the stock and balanced the drawer perfectly. It also left cash overstated on the balance sheet by the amount refunded, and a matching phantom balance in receivables — for the life of the workspace, in silence.
AWRA Blog
Until 1 October 2026 every allocation went oldest-expiry-first, with no setting and no per-item policy — and a column on the item that looked exactly like one. That column is now a real setting: earliest expiry first by default, or earliest received first, per item, on every issue path. What a dead column does to a reader, and the shelf-life rules a switch cannot replace.
AWRA Blog
A workspace can make its password rules stricter and cannot make them weaker — the minimum length is a floor, and complexity has no off switch. Beside it sits a lockout keyed on the address typed rather than the account found, which is the only way to stop it becoming a directory.
AWRA Blog
Matching an order against a receipt against the supplier's invoice is the standard control over paying for goods. We do two of those three. The third is not weakly implemented — it has no data behind it at all, because what we call an invoice is a document we generated ourselves from our own prices.
AWRA Blog
Three-way matching compares what you ordered, what arrived and what you were billed. We do the first two properly, with tolerances and a payment gate. The third document is one we generate from our own prices — so we call this a two-way match.
AWRA Blog
Four of its six actions contain no language model at all — they are keyword tests and arithmetic. Why that is the right design for automation, and four experiments that test any vendor's "AI-powered" claim in twenty minutes.
AWRA Blog
Between five to nine and a quarter past, five reminder sweeps run — approvals, customers, supplier responses, late deliveries and expiring quotations. Each has its own switch, its own clock and, in one case, a check that runs before either.
AWRA Blog
Splitting a purchase to stay under a tender ceiling is the pattern every auditor looks for first. Our product will not spot it, and the reason is structural rather than a missing report: a procurement request in our system carries no money at all, and its department is free text. There is nothing at the moment of the split to compare against a threshold.
AWRA Blog
The van is a warehouse that drives away; the site is a store with no walls — load-out transfers, nightly variance, job-costed materials, and crew custody.
AWRA Blog
The checkpoint between your transactions and your statements — a list that proves the books balance. What it catches, and the serious errors it never will.
AWRA Blog
AWRA Procurement is the purchasing module of AWRA OpsHub — requests, approvals, RFQs, purchase orders, three-way matching and budget control in one procure-to-pay workflow. What it does and how it fits the suite.
AWRA Blog
The control that stops you paying for goods you never received at prices you never agreed — how the match works, tolerances, and two-way vs four-way variants.
AWRA Blog
An asset is held by a person; consumable stock is held by a place. That asymmetry is why spray gangs, pickups and satellite stores end up modelled as warehouse locations — the workaround, its limits, and when to use a real custodian instead.
AWRA Blog
Measured usage is counted from stock issued through check-outs, which is exactly right for a store-issue operation. For counter-only items we can feed POS sales into the same formula, so the reorder tile fires on what actually moved.
AWRA Blog
Stock cannot go negative here: the issue is refused, per location, before anything is written. That is correct, and it has a price — the pallet standing in your yard that nobody has booked in does not exist, and cannot be sold.
AWRA Blog
One says what left the shelf. The other says who received it and whether they should have. Our batch trace answers the first properly — every movement, every location still holding it, quantities in, out and remaining. There is no patient anywhere in the product, so it stops at the door, and that is a boundary we intend to keep.
AWRA Help Docs
This Dashboard guide helps users read operational cards, trends, alerts, and insight panels without confusing dashboard summaries with final reports.
AWRA Help Docs
This Inventory guide helps users manage item records, warehouses, movements, counts, stock evidence, and inventory reports accurately.
Page 3 of 8 · 176 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
