Ratepayer App — Reports & Activity Module Acceptance Tests¶
Test series: RPA-RPT-01 to RPA-RPT-03
Objective: Validate that a ratepayer can review a summary of billed, paid, and outstanding amounts and a per-property payment breakdown from the More menu.
Status: New module — not present in the web portal UAT. The web has a related but distinct standalone page (ratepayer-portal/property-bill-reports.md, /reports, with summary cards, search/filters by digital address/reference/application ID/bill number/year, pagination, and expandable payments). The app's Reports & Activity screen, reached only via the More menu, appears to be a condensed version of this. This file documents the app screen as observed; extend or reconcile with ratepayer-portal/property-bill-reports.md once the product decision on feature parity is made.
Execution ownership¶
Recommended owners: Ratepayer/Public Portal users; Customer Service observer
Prerequisites: A signed-in ratepayer with at least one property that has bills and payments.
Execution control
Use approved UAT data only. Mask personal, authentication, and payment information in screenshots and attachments.
Feature overview¶
Reports & Activity (More → Reports & Activity) shows:
- A Summary card with Billed, Paid, and Outstanding totals across all of the ratepayer's properties/bills.
- A per-property card listing the property name, bill number and year, an Outstanding/Paid status tag, Payable/Paid/Outstanding amounts, a payment count (e.g., "3 payments"), and an expand chevron.
Coverage summary¶
| Test ID | Feature | Scenario | Priority |
|---|---|---|---|
| RPA-RPT-01 | Reports & Activity | Summary card | High |
| RPA-RPT-02 | Reports & Activity | Per-property card and expansion | High |
| RPA-RPT-03 | Reports & Activity | Feature-parity gap vs. web Reports | Medium |
Implementation observations requiring UAT confirmation¶
| Observation from screenshots | Required validation |
|---|---|
The screen has no visible search box, filters (digital address, reference, application ID, bill number, year), or pagination, unlike the web's /reports page. |
Confirm whether these are intentionally omitted for the app (as a lightweight summary) or should be added for feature parity with ratepayer-portal/property-bill-reports.md. |
| Only one property card was visible in the captured screenshot; multi-property scrolling/pagination behaviour is unconfirmed. | Confirm how the screen behaves for ratepayers with many properties/bills — scroll, pagination, or a "load more" pattern. |
| The property card shows "3 payments" as a count with an expand chevron, but the expanded content was not captured. | Confirm the expanded content matches web's expandable-payment detail (date, reference, source, method, amount) from ratepayer-portal/property-bill-reports.md RPP-RPT-08. |
| No Print/Export/Receipt actions were visible on this screen. | Confirm whether this screen is read-only (summary/reporting only) or should offer export actions like the web's /reports page (where Export PDF/Excel/Print are also currently unavailable — see ratepayer-portal/property-bill-reports.md RPP-RPT-10). |
RPA-RPT-01 — Reports & Activity summary card¶
Feature overview¶
A summary card shows Billed, Paid, and Outstanding totals across the ratepayer's properties.
Preconditions
- A signed-in ratepayer with at least one bill.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Open Reports & Activity and review the summary card. |
| Expected result | Totals reconcile with the ratepayer's actual bill and payment data. |
| Execution result | PASS |
| Evidence reference | Insert link or reference |
| Defect reference | Insert ID or None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Open screen | 1. Open More → Reports & Activity. | The screen opens with a back arrow, title, and Summary card. | PASS |
|
| Billed total | 1. Inspect the Billed value. | It equals the sum of all billed amounts across the ratepayer's properties. | PASS |
|
| Paid total | 1. Inspect the Paid value. | It equals the sum of all completed payments. | PASS |
|
| Outstanding total | 1. Inspect the Outstanding value. | It equals Billed minus Paid, and matches Home's Total Due Amount. | PASS |
Cross-check against dashboard.md RPA-DSH-03. |
| Cross-screen consistency | 1. Compare these totals with My Bill and My Payments totals. | Values reconcile across all three screens. | PASS |
Tester notes
Record actual result, test data identifiers, device/OS/build, and any variance.
RPA-RPT-02 — Per-property card and expansion¶
Feature overview¶
Each property appears as a card with its latest/relevant bill, a status tag, amount breakdown, and an expandable payment count.
Preconditions
- A signed-in ratepayer with a property that has recorded payments.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Review a property card and expand it. |
| Expected result | Card values are accurate and the expanded view shows correct payment detail. |
| Execution result | PASS |
| Evidence reference | Insert link or reference |
| Defect reference | Insert ID or None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Card content | 1. Inspect a property card. | Property name, "Bill # |
PASS |
|
| Payment count | 1. Inspect the payment count text. | "N payments" matches the actual number of payments recorded for that bill. | PASS |
|
| Expand card | 1. Tap the chevron to expand the card. | Individual payment entries (date, reference, source, method, amount) are shown. | PASS |
Pending confirmation of exact fields. |
| Collapse card | 1. Tap the chevron again. | The expanded detail collapses. | PASS |
|
| Fully paid property | 1. Inspect a property with zero outstanding. | The status tag shows a paid/settled state instead of "Outstanding". | PASS |
|
| Multiple properties | 1. Open the screen for a ratepayer with more than one property. | Each property appears as its own card, in a consistent and complete list. | PASS |
Tester notes
Record actual result, test data identifiers, device/OS/build, and any variance.
RPA-RPT-03 — Feature-parity gap vs. web Reports¶
Feature overview¶
This test case tracks the confirmed functional gap between the app's Reports & Activity screen and the web's /reports page (ratepayer-portal/property-bill-reports.md) so a product decision can be recorded.
Preconditions
- Access to both the app's Reports & Activity screen and the web's
/reportspage for the same account.
| Field | Value |
|---|---|
| Priority | Medium |
| Test action | Compare the app screen against the web /reports page feature-by-feature. |
| Expected result | Each gap is explicitly accepted, rejected, or scheduled for the app. |
| Execution result | PASS |
| Evidence reference | Insert link or reference |
| Defect reference | Insert ID or None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Search/filter parity | 1. Compare filter availability (digital address, reference, application ID, bill number, year) between app and web. | A decision is recorded on whether the app should add these filters. | PASS |
See ratepayer-portal/property-bill-reports.md RPP-RPT-03/04. |
| Pagination parity | 1. Compare pagination behaviour for accounts with many bills. | A decision is recorded on the app's pagination/scroll approach. | PASS |
See ratepayer-portal/property-bill-reports.md RPP-RPT-05. |
| Export/print parity | 1. Compare export/print availability. | A decision is recorded on whether export actions are added to the app (web's are currently unavailable too). | PASS |
See ratepayer-portal/property-bill-reports.md RPP-RPT-10. |
| Navigation entry point | 1. Compare how each platform surfaces this feature (web: sidebar "Reports"; app: More menu only). | Confirm this difference is acceptable given the app's condensed IA. | PASS |
See navigation.md RPA-NAV-05. |
Tester notes
Record the product decision for each row above once reviewed with stakeholders.