AWRA OpsHub Search
All role-based solutions

External review

Review the books where the transactions happened.

External accountants and auditors work inside a client’s AWRA workspace to read the ledger, the trial balance and the statements, and to read each entry beside the reference and stock movement that produced it.

Accountants & Auditors operations workflow

Read the ledger, journals, trial balance and statements in the client’s own workspace instead of waiting for an export.

Sample a purchase from request to payment on one chain — quotations, order, receipt, invoice match and payment.

Check whether the audit trail is intact before relying on it.

Why this page exists

Built around the problems this team actually owns.

The page connects role-specific pain points to AWRA workflows and implementation resources, so prospects can inspect fit without guessing which module matters.

1

Client exports arrive late, partial, or reshaped in a spreadsheet.

2

Supporting documents sit in email threads rather than beside the entry.

3

Access is shared through somebody else’s login, so nothing a reviewer does is attributable.

Operating workflows

A practical workflow map for accountants & auditors.

Year-end sampling

Pick entries from the journal by date range and type, then trace each through its reference and stock movement to the operational record behind it.

Three-way match review

Review orders held in discrepancy and every payment override, with the permission, the written reason and the stamp each one carries.

Audit trail check

Run the chain verification and export the audit log as CSV for your working papers.

Before you shortlist us

The same page, without the sales gloss.

Everything above describes what accountants & auditors can do with AWRA. This is where the claims are separated into what is built, what is not yet, and what we have decided is not ours to do.

What a reviewer can reach, and what we would add for one

What AWRA OpsHub does today

  • Roles are built from individual permissions, so a reviewer can hold the ledger, journal and statement views without any permission that creates, approves or pays.
  • The trial balance, income statement and balance sheet read the same journal entries the operation posts, and the journal list filters by date range and entry type.
  • Three-way matching holds a discrepancy status when the order, receipt and invoice disagree. A payment override needs its own permission and a written reason, and leaves a stamp.
  • Audit rows are hash-chained per workspace and have no delete route; a verification run reports an edited, deleted or spliced row, and the log exports as CSV.
  • An invoice that passes a customer’s credit limit is held, and releasing it records who, when and why.
  • A reviewer’s login can carry an access end date, so an engagement closes itself on the day it was agreed rather than waiting for someone to remove the user, with a notice three days ahead.
  • Manual journals can require maker-checker approval — the author cannot approve their own, and a rejection carries its reason. A posted entry can never be deleted in any month; a correction is a reversal that posts the mirror entries and leaves the original in place.
  • Supplier bills are maker-checker too: whoever entered or last edited a bill cannot approve it, unless nobody else active holds that permission.
  • A foreign-currency document posts in base currency at the rate recorded on it, and a payment settled at a different rate books the realised exchange gain or loss — so the ledger a reviewer reads is in one currency, with every conversion traceable to a document.
  • A month-end close checklist records, per month, the automatic checks (unposted or unapproved journals, bank accounts reconciled to month end, depreciation, pending petty cash, a balancing trial balance, unclassified accounts, the previous month closed) and the organization’s own steps, each ticked or skipped with a reason.
  • A direct-method cash-flow statement for any date range, built from the ledger with opening and closing cash, and transfers between the organization’s own cash accounts left out.
  • An auditor evidence pack: one ZIP per date range with every ledger line and posting (who drafted, approved and posted it), the period closes and reopen requests, the close evidence packs, certified statements, the integrity checks and the accounting audit log, each file listed with its SHA-256 — behind a permission of its own.
  • Every statement line drills through to the account’s ledger, then to each posting with its attached files, then to the invoice, bill, payment or asset behind it.
  • Certified statements — trial balance, income statement, balance sheet and cash flow frozen for a period with a checksum, downloadable as PDF or CSV, with what has changed in the live ledger since shown beside them.
  • A tax audit export for up to two years — output and input tax lines with PINs and eTIMS status, credit notes, withholding, VAT returns, every tax rate change with who made it, and the tax accounts reconciled to the documents — with its checksum in the audit log.
  • A reconciliation workspace showing, for a month, whether cash drawers, payments, receivables, receiving, stock value, bank and QuickBooks tie out, and who signed each one off.

More we can add to your workspace

  • One login across several client workspaces. A user belongs to one workspace today, so an accountant with five clients holds five sign-ins.
  • An audit-trail permission of its own for the full log. The accounting audit log already comes in the evidence pack under its own permission; the workspace-wide log sits behind the workspace-settings permission, which is more than a reviewer should hold.
  • A trial balance for any period as a spreadsheet for your working papers. Ledger lines and postings already export as CSV in the evidence pack, and a certified trial balance downloads as PDF or CSV.
  • A date range on the trial balance. The income statement already takes a from and to date and the balance sheet an as-at date; the trial balance is being brought into line.

Where we point you to a specialist

  • We will not give an opinion on the accounts. The system shows what was posted, by whom and from which record; whether the result is fairly stated is your judgement and your signature.
  • We will not tell a client whether a cost is capitalisable, deductible or recoverable. That is the accountant’s call, and software that makes it in a demo is selling a liability.

Multi-workspace sign-in, an audit-trail permission, file exports and period-bounded statements are scope, not ceilings. The permission model, the CSV export the audit log already uses and the statements themselves exist, so each is a written specification and a price.

Before you rely on any system’s audit trail, ask to see a deleted row detected. Ours is tamper-evident rather than tamper-proof: anyone with database access can still delete a row, and the verification run is what shows that it happened.

Modules to inspect

The AWRA surface area this team will use most.

General Ledger Trial Balance Financial Statements Audit Trail Procurement Payments Register Roles & Permissions Document Vault

Metrics to discuss

01
Unresolved match discrepancies
02
Payment overrides
03
Credit hold overrides
04
Audit chain status

Next-best links

Enterprise resources for a serious evaluation.

Use these links for product review, implementation planning, pricing, self-serve help, and sales follow-up.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center