From the Statement Line to the Receipt Behind It
Every figure on a financial statement is the sum of things that happened. Click one and AWRA walks you down: the account’s lines for the same dates, the posting each line belongs to, and the invoice, bill, till sale or payment that made it. That walk only works because every event now posts once, in balance, as one document.
The finance manager of an Eldoret agro-dealer is asked by her director why September’s transport cost is KES 1.21 million when the plan said 960,000. She knows the answer is in the ledger. Until now, finding it meant exporting the general ledger, filtering a spreadsheet to one account and one month, and then searching the system for each reference one at a time. Now she clicks the number.
Four steps down from a figure
-
The statement line
On the income statement, balance sheet, cash-flow statement or trial balance, an account’s name is a link. It carries the statement’s own dates with it.
-
The account’s lines for those dates
Every line posted to that account in the range, oldest first, with the opening balance before the range, a running balance that carries across pages, and the total debits and credits. The total on the statement is the total of the lines listed.
-
The posting
Each line belongs to one posting. Its page shows every line in it, on every account, so you see both sides of the event: the transport cost and the bank or payable it came from. It also shows any files attached, and whether it reverses or was reversed by another posting.
-
The document
The posting links to what made it: the supplier bill, the invoice, the till sale, the payment, the asset, the bank statement line. One click from the ledger to the paper.
| A posting made by | Opens |
|---|---|
| A customer invoice, credit note or receivable write-off | The invoice |
| A customer payment | The invoice it settled |
| A supplier bill | The bill |
| A supplier payment | The bill it paid, or the purchase order where there is no bill |
| A till sale, return or payment | The till sale |
| A bank statement line | The bank reconciliation for that account |
| A stock adjustment or a transfer shortfall | The adjustment or the transfer |
| A service delivery confirmed on a purchase order | The purchase order |
| An asset | The asset |
| A manual journal | The journal, with its approval history |
The walk runs the other way too. An invoice, a supplier bill, a till sale, an expense and an asset each show a ledger postings panel: what that document put on the books, line by line, with a link to each posting. That is the answer to “did this invoice actually reach the ledger, and where?” without leaving the invoice.
A number you cannot follow down is a number you have to take on trust. The point of the drill is that nobody has to.
Why the walk needs one posting per event
A trail from a figure to a receipt is only as good as the step in the middle. If a sale writes five separate ledger lines that merely share a reference, the trail forks, and a line that failed to write leaves the other four behind with nothing to say they belonged together. So every automatic posting — a sale, a bill, a receipt, payroll, depreciation, a stock movement — is now one posting: a single document that holds all its lines, written together or not at all.
- It always balances. Debits must equal credits. Rounding drift of up to half a cent a line, which converting foreign amounts line by line produces, is absorbed on the largest line and noted on the posting; anything larger is refused.
- It cannot post twice. Each event carries a key. If the same sale or payment is sent again — a retried request, a double click, a webhook that arrives twice — the first posting is returned and nothing new is written.
- Once posted, it does not change. Its date, total, source and number are frozen, and a posted posting cannot be deleted. A manual journal is corrected by a linked reversal; a document is corrected the way its own module corrects it, with a credit note or a reversal of its own.
- It knows what made it. Every posting carries the module, the document type and the document it came from, which is what the drill’s last step reads.
What happened to the older lines
Ledger lines written before postings existed were gathered into postings too, grouped by what most likely wrote them together. Where an old group never balanced, it was still gathered, so nothing is left floating, but it is marked as an older group that did not balance and its numbers were left exactly as they were. Correcting history is an accountant’s journal, not a migration’s guess.
Files on the posting, not in a drawer
A posting can carry attachments: the schedule behind an accrual, the board minute behind a write-off, the supplier’s statement behind a correction. Anyone who can create journals can attach a file to a posting from its page; the file is kept in private storage and served only to people allowed to see the accounts, and every attachment is written to the audit log. When the auditor drills to the posting, the evidence is next to it.
Checks that read the postings
Because every line now belongs to a posting, AWRA can check the ledger as a whole. The Reconciliation screen under Accounting runs these on demand:
Ledger integrity checks
- Ledger lines that belong to no posting.
- Postings whose debits and credits differ.
- Accounts Receivable against the open customer documents, and Accounts Payable against open supplier bills and unbilled receipts.
- Settled payments that never posted.
- Bank statement lines not yet explained, by age.
- Lines missing a department, branch, project or cost centre on an account that requires one.
- Journals to a sensitive account that only one person signed.
Each check says how many and how much, so “the control account agrees with the documents” becomes a line you read rather than a reconciliation you rebuild. The tagging rules and how to set them up are in the Department, Branch & Project Tags guide; the ledger itself in the General Ledger guide and on the general ledger page.
The same checks feed the reconciliation workspace, which puts every area that has to tie out for a month on one screen — cash drawers, payments, receivables, purchase-order receiving, stock value, bank and QuickBooks — each with its difference and a reviewer’s sign-off. An area in exception is signed off only with a note saying why. See the Reconciliation Workspace guide.
What AWRA OpsHub does today
- Drill-down from the income statement, balance sheet, cash flow and trial balance to the account’s lines for the same dates, with opening and running balances.
- A page per posting showing every line, its source document, its attachments and any reversal.
- A link from each posting to the document that made it, across sales, purchasing, the till, payments, banking, stock and assets.
- A ledger postings panel on invoices, supplier bills, till sales, expenses and assets.
- One balanced posting per event, written in one step, refused if it does not balance, and never posted twice for the same event.
- Attachments on any posting, privately stored and audited.
- Ledger integrity checks for loose lines, unbalanced postings, control accounts, unposted payments, unexplained bank lines, missing tags and one-signature journals on sensitive accounts.
- A reconciliation workspace that sets cash drawers, payments, receivables, purchase-order receiving, stock value, bank and QuickBooks side by side for a month, each with its difference, a link to the items behind it and a reviewer’s sign-off.
- A posting’s page in the AWRA mobile app, opened from a journal entry or a write-off, with every line and the document it came from.
More we can add to your workspace
- The walk from a statement figure in the mobile app, from the income statement line down to the posting, as it runs on the web.
- Comparative columns on the account view, this period beside the same period last year, line by line.
- Journal import from a spreadsheet, so an opening balance or a payroll journal prepared elsewhere arrives as one posting with its file attached.
Where we point you to a specialist
- The drill shows what was posted and where it came from. Whether the posting was the right accounting for the event is your accountant’s judgement, and the trail is there to make that judgement quicker, not to replace it.
Spreadsheet journal import is small and usually the first thing a finance team asks for after go-live; comparative columns on the account view build on the same drill the web already runs.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsThree questions to ask of any ledger
Click the transport line on last month’s income statement. Where do you land?
A good answer sounds like
The account’s lines for last month, adding up to the figure.
What it tells you
A figure that leads to an export is a figure you rebuild every time someone asks.
What happens if the same payment is posted twice?
A good answer sounds like
The second attempt returns the first posting.
What it tells you
A ledger that trusts every request to arrive once will one day double a payment.
Can you show me every line that belongs to no posting?
A good answer sounds like
A check that says none, or how many.
What it tells you
Loose lines are where a trial balance stops balancing and nobody can say why.
Our position
Start every variance question at the statement and click down, not at an export. Attach the evidence to the posting when you make it, not when the auditor asks. And read the integrity checks before you close the month: if the control accounts disagree with the documents, you want to know before the statements are certified, not after.
The general ledger in AWRA
A ledger that writes itself from your documents, one balanced posting per event, and a trail from every figure to the paper behind it.
Read the feature pageFrequently asked questions
Can I drill down from a financial statement to the source document in AWRA OpsHub?
Yes. Account names on the income statement, balance sheet, cash-flow statement and trial balance open that account’s lines for the same dates. Each line opens its posting, and the posting opens the invoice, bill, till sale, payment, asset or other document that made it.
What does one balanced posting per event mean?
Every automatic entry, such as a sale, a supplier bill, a payment or depreciation, is written as a single posting holding all its lines. It must balance, it is written in one step, and the same event cannot post twice.
Can I attach a document to a journal or posting?
Yes. Anyone who can create journals can attach files to a posting from its page. Files are kept in private storage, served only to people who may see the accounts, and each attachment is recorded in the audit log.
Can a posted entry be edited or deleted?
No. Once posted, its date, total, source and number are frozen and it cannot be deleted. A manual journal is corrected by a linked reversal, and a document by its own correction, such as a credit note.
