AWRA OpsHub Search

AWRA Help Center

Copy link
Finance Controls Reports
01 Finance, Accounting & Reports Module Guides 02 Report Export Step-by-Step Workflows 03 QBO Sync Check Step-by-Step Workflows

Payments Register

One place to see money in and money out — customer receipts, POS takings, and payments to vendors — across sales, POS and procurement, without opening each module in turn.

AWRA records payments where the work happens: a customer pays an invoice in Sales, a shift takes cash in POS, a vendor is paid from a purchase order in Procurement. The Payments Register is the cross-module view that merges those streams so finance can reconcile without hopping between screens. You reach it from Reports → System Reports.

Three Views, Deliberately Separate

ViewWhereWhat it holds
Money InSales → Customers → PaymentsCustomer and sales receipts — the sales payment ledger, including online collections.
Money OutVendor PaymentsPayments to vendors: manual records, M-Pesa B2C/B2B, and card or online settlements.
Payments RegisterReports → System ReportsThe merged register — customer payments, POS payments, and procurement payments together.

The register is a reconciliation view, not a fourth ledger. Nothing is entered here; it reads what the modules recorded.

Paying A Vendor

A vendor payment can be raised from the purchase order or from Vendor Payments directly. A purchase order's paid figure is the sum of its successful vendor payments — a queued or failed attempt does not reduce what is owed. Bank and cash payments recorded on the purchase order page are mirrored into the vendor payments ledger automatically, so the same settlement does not have to be entered twice and does not show up as two payments.

M-Pesa And Card Payments Settle Asynchronously

This trips people up more than anything else on this page. When you send an M-Pesa payment, the row is created as pending as soon as the request is accepted for processing — that is an acknowledgement that the instruction was queued, not confirmation that money moved. It stays pending until the provider's result callback arrives, which can be seconds or minutes later, and it can still come back failed.

  • Do not re-send a pending payment. Refresh and wait for the result before trying again.
  • Once any payment against a document succeeds, leftover pending attempts on it are cancelled, so a document does not carry ghost rows forever.
  • A payment that fails at the provider is recorded as failed with the reason — see Failed Payment.

Operational Payments Are Not Your Subscription

Everything on this page is your organization's own money — what customers pay you and what you pay suppliers and staff. What you pay for AWRA itself is separate and lives under Billing.

Reconciling

If a total does not agree with your bank, check in this order: pending provider payments that never resolved, payments recorded against the wrong document, and multi-currency rows. AWRA never converts and adds currencies together in one figure — see Currency & Billing. Payroll payments also land in the register: see Payroll.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide