AWRA Blog
The ID You Look Up and the Name You Send
The schema call identifies a table's key column by an opaque identifier. The write call wants its human name. A connector missing the translation fails on every table anybody has ever tidied.
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.
APIs, webhooks, sync patterns, QuickBooks, connectors, and external system implementation.
AWRA Blog
The schema call identifies a table's key column by an opaque identifier. The write call wants its human name. A connector missing the translation fails on every table anybody has ever tidied.
AWRA Blog
Real-time fiscalisation moves the tax authority from something you report to afterwards into something standing between you and your own invoice. That is an operations change before it is a tax change.
AWRA Blog
A Mailchimp API key ends with the name of the server your account lives on. The credential carries its own routing — so a key with the suffix missing is not a credential at all.
AWRA Blog
A supplier in your workspace and a supplier in QuickBooks are decided to be the same supplier by the display name, matched exactly, on every run. Everything downstream hangs off that one comparison — including what happens the day somebody renames one.
AWRA Blog
On a Discord webhook the sender name is a value in the message body, chosen per message, with nothing checking it. Which makes the name in that channel a claim rather than a fact.
AWRA Blog
A revenue authority identifies your invoice by a number you choose. Three kinds of document were each choosing from their own sequence — two documents claiming one filing, invisible from inside.
AWRA Blog
The password on an M-Pesa request is not stored anywhere. It is built fresh for every call out of three pieces — one of which is the current time — which makes your server clock part of getting paid.
AWRA Blog
A workflow can be built with a wait in the middle — do this, pause three days, then do that. The pause works. Everything before it runs, the run is marked paused, and the log names the date it will continue. Nothing in the product ever comes back to it.
AWRA Blog
Almost nobody writes the plain-text version of a transactional email, and almost every spam filter notices. This connector builds one from the HTML — three characters of code, a measurable difference.
AWRA Blog
The response to a payment request is two identifiers and a suggestion to ask the customer for their PIN. Everything that matters arrives later, from a party that signs nothing.
AWRA Blog
"Sync" does more work on integrations pages than any other word in software marketing. Ours pushes vendors, items and purchase orders out on a button and reads nothing back — including a note on where our own connector copy overstates it.
AWRA Blog
When a message is handed to a mail or messaging provider, the provider hands back an identifier — its receipt for what it just accepted. There is a place to keep that identifier and nothing puts anything in it, so our record of a message and theirs cannot be joined.
AWRA Blog
There is a real API and there is no developer portal. How tokens are issued, why a token carries the user's permissions rather than its own, what the API is genuinely good for — and why continuous two-way sync is not a shape it supports.
AWRA Blog
Send a contract naming a role the template does not define and everything succeeds — the document is created, the email goes out, and there is nothing for the recipient to sign.
AWRA Blog
One Microsoft sign-in button serves a corporate directory account and a personal one, and the profile it returns is the same shape for both. Knowing which way that decision went tells you what the button can enforce.
AWRA Blog
An automation platform learns what a payload looks like from one sample and builds every mapping against it, which makes a field that is sometimes absent worse than a field that is always empty.
AWRA Blog
Two mechanisms stop a request being processed twice, and they disagree about almost everything — including whether an identical second request is a duplicate or a legitimate new one. Both are right for where they sit.
AWRA Blog
Three SMS providers, one missing sender name, three behaviours: one omits the field, one substitutes a default, one refuses to send. A connector that assumed any of them would break on the other two.
AWRA Blog
The same email address has to be sent four different ways depending on what the destination column was declared as. Guess wrong and the whole record is refused.
AWRA Blog
The accounting sync keeps a proper log — what it moved, when it started, how long it took, what went wrong. There is a column for who started it, and a defined way to read that column, and nothing has ever written to it.
AWRA Blog
Telegram puts the bot token in the request path rather than a header. Every proxy and access log along the route sees credentials the other providers keep out of the URL — worth knowing before you route alerts through it.
AWRA Blog
An inbound webhook endpoint has no login and no workspace in its address. One header decides which of thousands of workspaces an event belongs to, and where that decision is made is the whole security model.
AWRA Blog
Our stock transfer has a button marked Approve. It is a synonym for Dispatch, in the web application and the API alike, and the stock leaves the source in the same instant. There is no approved-and-waiting state, because there is no approved state at all.
AWRA Blog
A customer pays once. The provider tells you three times, or eleven minutes late, or not at all. Four failure modes, how each is caught, and the one that leaves nothing behind — plus why the retry only runs when somebody presses it.
Page 4 of 9 · 199 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.