AWRA OpsHub Search
Intermediate Certificate on pass

Track: Accounts Payable

For Accounts Payable: supplier bills, the three-way match, debit notes, payment runs, withholding, and bank reconciliation.

3 lessons 45 min 5-question assessment 70% to pass

What you’ll learn

  • Explain the specialized operational responsibilities behind the track: accounts payable track
  • Configure role-specific options, interface views, and default permissions settings
  • Handle day-to-day workflow exceptions, supervisor escalations, and system inputs
  • Provide audit-ready task history reports and compliance evidence records

Course content

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

Match purchase orders

Track: Accounts Payable focuses on accounts payable operations, capturing supplier bills against purchase orders, offsetting debit notes, and paying approved bills through payment runs. In AWRA, role-based tracks deliver target training, operational boundaries, and verification tools tailored to specific job profiles.

The primary objective is role clarity and procedural control. Users must understand their dashboard widgets, access boundaries, and daily checklist items.

In practice, an AP specialist captures a supplier’s invoice against its purchase order, checks the three-way match, adds the bill to a payment run, and once a second person has approved the run, uploads the bank file and confirms the lines when the bank statement shows them paid.

Accounts payable path

1

Match

Capture the supplier bill against its purchase order and check the three-way match.

2

Verify

Approve the bill; a duplicate invoice number or a bill above the order total is refused.

3

Pay

Add approved bills to a payment run that a second person approves before anything is paid.

4

Close

Confirm bank lines once the statement shows them paid, then reconcile the bank account.

Role model

  • Dashboards display widgets matching user roles.
  • Action permissions enforce segregation of duties.
  • Daily checklists ensure consistent operations.
  • Always escalate exception tasks through system workflows.
02
Lesson 2 of 3 Workshop 15 min

Verify supplier bills

The operating routine is to capture supplier bills, check the three-way match, apply open debit notes, build payment runs for a second approver, and confirm bank lines from the statement. This keeps user inputs accurate and ensures that exceptions are caught and resolved before daily close.

Before submitting values or approvals, check the supplier’s invoice number, the order’s received quantities, the bill total against the order total, open debit notes, withholding on the bill, and the supplier’s bank or M-Pesa details. These safety rules prevent transaction errors and protect ledger balances.

A supervisor or team administrator can adjust role dashboards, override blocks, or review audit trails from the console.

AP verification matrix

Signal Check Action
Billing mismatch found The match shows a discrepancy between order, receipt and bill Reject the bill with a reason and ask the supplier to correct it
Goods sent back Received quantity and the order’s returns so far Approve the supplier return so a debit note is raised, and let the payment run offset it
Payment run approved Bank lines are under Awaiting bank Upload the bank file, then confirm each line only when the statement shows it paid
Reconciliation completed Statement and books agree with a zero difference Complete the bank reconciliation so the cleared lines lock

Role decisions

  • Process role tasks according to department policies.
  • Audit input values using automated validation tools.
  • Escalate high-value exceptions to supervisor queue.
  • Confirm daily shift balances match physical audits.
03
Lesson 3 of 3 Practice 14 min

Pay through payment runs

Role transactions and daily audits must leave proof. Useful evidence includes the supplier’s attached invoice, the three-way match on the order, debit notes applied, the approved payment run, and the completed bank reconciliation, which is required for audit logs reviews and system status reports.

Management should review role productivity: task completion times, exception frequencies, and data correction rates indicate training or layout needs.

In practice, closure means bills are approved and matched, payment runs are completed, bank lines are confirmed from the statement, and the bank account is reconciled.

Accounts payable checklist

Bill matches its order and receipt
Supplier invoice number is captured
Open debit notes are offset
Payment run approved by a second person
Bank lines confirmed and reconciled

Oversight validation

  • Confirm task completion matches registry records.
  • Verify security signatures are logged on overrides.
  • Validate daily close counts match bank deposits.
  • Ensure exception notes are saved to transaction records.

Finished the material?

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

Take the assessment

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