AWRA OpsHub Search
Tie & agree

Four things
that have to
agree.

Reconciliation is not a monthly ritual here. Four pairs are computed from live records every time you open the screen, both sides shown, and the difference between them printed rather than buried.

What reconciles
  • 01 Stock against the ledger
  • 02 Purchase orders against payables
  • 03 Debits against credits
  • 04 Payments register against the ledger
The worksheet

Both sides, and the gap.

A reconciliation that shows you only the answer is asking to be trusted. Each of these shows what was compared, what each side said, and what is left over.

01

Stock against the ledger

Agrees
Stock on hand, valued
4,182,600
Inventory ledger account
4,182,600

Both sides are valued at weighted average, because that is what POS cost of goods posts at. Value the stock side at buying price instead and you report a variance that is only a difference of basis — a number that looks like a problem and is not.

02

Purchase orders against payables

Variance named
Open purchase orders
1,246,900
Accounts payable ledger
1,198,400
Left over 48,500

Every purchase order that is neither paid nor cancelled, against what the payables account says you owe. A gap here is usually a receipt posted without its invoice, or an invoice entered against no order.

03

Debits against credits

Agrees
Total debits
18,904,250
Total credits
18,904,250

The internal-consistency test for double entry, run across every journal entry rather than a sample. Both halves are written on every posting, so the totals must match exactly; an imbalance means a journal was written incomplete.

04

Payments register against the ledger

Agrees
Settled payments out
2,640,100
Bank and cash ledger
2,640,100

Money actually leaving on the payment rails, against what the bank and cash accounts say left. Settled, pending and failed are counted separately, and the settled figure is split by what it was for and by how it was paid.

The leak check

Money that moved
without a posting.

A total that agrees can still hide a gap, because two errors can cancel. So there is a second, narrower test on the one rail whose posting contract we own: a settled project payout is expected to carry its own settlement journal — debit payable, credit bank — keyed by the payment reference.

Any settled payout with no matching journal is listed by name. Money that left without reaching the ledger is the failure that costs most and shows least, because nothing on any screen looks wrong until someone goes looking.

Settled payouts · journal match
PYT-2026-00841 182,400 ✓ posted
PYT-2026-00844 96,750 ✓ posted
PYT-2026-00849 240,000 ▲ no journal
PYT-2026-00852 58,200 ✓ posted
Scope

This reconciles your records to your ledger.

That is the half that catches posting errors, unposted settlements and stock that drifted from its account — the errors made inside the system, which are the ones a system can reasonably be asked to find.

More we can add to your workspace

Bank and mobile-money statement feeds

Settlement files from the card acquirer, the mobile-money provider and the bank pulled into the Payments Register, so collections match invoices without anyone re-keying a statement at month end. It is a well-defined build on rails that already exist, and we will scope it with a written specification, a timeline and a price.

Talk to us about it
Questions

Asked at month end.

What does the reconciliation screen actually compare?
Four pairs. Stock on hand against the inventory ledger account, open purchase orders against accounts payable, total debits against total credits, and settled payments in the register against the bank and cash ledger accounts. Each pair shows both sides and the difference between them.
Does it import my bank statement?
Not today. What reconciles here is your own records against your own ledger, which is the half that catches posting errors and unposted settlements. Pulling bank statement feeds and mobile-money settlement files into the Payments Register so collections match invoices without re-keying is something we can build for your workspace on a written specification.
Why value stock at weighted average rather than buying price?
Because the ledger side does. POS cost of goods posts at weighted average, so valuing the stock side at buying price would report a variance that is only a difference of basis — a number that looks like a problem and is not. Both sides use the same basis so a difference means something.
What is the debits-equals-credits check for?
It is the internal-consistency test for double entry. Every posting writes both halves, so the totals must match exactly; any imbalance means a journal was written incomplete. It runs across every journal entry rather than a sample.
How do I know a payment actually reached the ledger?
A settled project payout is expected to carry its own settlement journal — debit payable, credit bank — keyed by the payment reference. The screen lists any settled payout with no matching journal, so money that moved without a posting is named rather than quietly absent.
How often does it run?
Every time you open it. The figures are computed from live records rather than a nightly snapshot, so what you see is the position now.

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