AWRA OpsHub Search
Advanced Certificate on pass

Reconciliation Workflows

Match bank and payment records, resolve exceptions, and check source documents.

3 lessons 40 min 5-question assessment 80% to pass
Take the assessment

What you’ll learn

  • Connect finance reports to source modules, controls, and operational decisions
  • Review accounting, tax, budget, payment, reconciliation, and close evidence
  • Identify finance exceptions before they distort reports or manager decisions
  • Prepare finance records for audit, period close, and executive review

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Reading 12 min

Match records

Reconciliation Workflows focuses on bank matching, payment matching, reconciliation exceptions, source documents, and review routines. In AWRA, finance control works best when operational activity, accounting records, tax treatment, approvals, attachments, and reports stay connected.

The practical goal is trust. Finance users should know where a number came from, which source module created it, who reviewed it, and what evidence supports the balance, tax, payment, budget, or close decision.

In practice, finance imports the month’s bank statement under Bank Reconciliation, lets Match the obvious ones clear the lines with a single candidate, matches the rest from the suggestions, posts and matches the bank charges nobody recorded, and completes the reconciliation once the difference is zero — which locks the lines it cleared.

Reconciliation path

1

Import

A statement is uploaded (CSV, OFX or MT940), or arrives from the M-Pesa feed or the statement inbox.

2

Match

Statement lines are matched to ledger entries with the same amount and direction.

3

Exception

Lines with no entry are posted and matched, or ignored if they never belong in the books.

4

Resolve

The statement balance is checked against the books and any difference traced.

5

Approve

The reconciliation is completed at a zero difference and its lines lock.

Finance model

  • Finance reports should trace back to source records and review decisions.
  • Tax, budget, and accounting setup choices affect many downstream reports.
  • Attachments and review notes make balances defensible during audit or close.
  • Exceptions should be owned before they become reporting noise.
02
Lesson 2 of 3 Workshop 14 min

Resolve reconciliation exceptions

The operating routine is to import the statement, match lines to ledger entries, post and match unrecorded bank charges, confirm any payment-run bank lines, and complete the reconciliation at a zero difference. This keeps finance work from becoming a spreadsheet-only exercise disconnected from AWRA source activity.

Before acting, check bank date, payment date, amount, reference, customer or vendor, source document, unmatched status, and reviewer. These checks protect report accuracy, cash visibility, tax treatment, procurement decisions, and audit readiness.

A strong finance user can explain the next action from the record itself, whether the action is reviewing a ledger line, chasing a receivable, reconciling a payment, approving a budget, or closing a period.

Reconciliation exception guide

Finance signal Review Action
Unmatched deposit Suggestions with the same amount within ten days Match the right entry
Bank charge not in the books Statement line date and amount Post & match to the charges account
Supplier payment missing Payment-run bank lines awaiting confirmation Confirm the line on the run
Difference left over Entries in the books not yet on a statement Trace the date or account

Finance decisions

  • Finance action should follow the current balance, source module, and control state.
  • High-impact edits, deletes, overrides, and close decisions need clear reasons.
  • Operational context helps finance teams interpret margins, cash, and aging.
  • Reports are more useful when exceptions have owners and next actions.
03
Lesson 3 of 3 Practice 14 min

Prepare review evidence

Finance closure should leave proof. Useful evidence includes bank record, payment record, match decision, unmatched explanation, source document, attachment proof, and reviewer signoff, connected to the exact account, transaction, report, payment, tax setting, budget, reconciliation, or close item.

Managers should review patterns such as unmatched payments, aged balances, failed sync, suspicious adjustments, tax setup gaps, budget overruns, and unresolved period-close blockers.

In practice, closure means reconciliation exceptions are matched, explained, corrected, or assigned for follow-up.

Reconciliation close checklist

External records are imported
Matches are reviewed
Unmatched items are explained
Source proof is linked
Reviewer signoff is recorded

Financial proof

  • Finance work is complete only when the balance and evidence can be defended.
  • Close routines should surface unresolved risk instead of hiding it.
  • Audit packs and exports should preserve source context, not just report totals.
  • Good finance governance protects cash, tax, margins, budgets, and trust.

Finished the material?

Take the 5-question assessment and earn your certificate — 80% to pass.

Take the assessment

More in this path

Point of Sale Fundamentals

Open course

Asset Tracking Essentials

Open course

Vendor Portal Foundations

Open course

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