Super — Connect Beam & Member Verification¶

Manual test plan for connecting a company to the Beam super clearing house, the Beam settings page, auto-sync, and Member Verification (MVR). Read How testing works first.

Beam UAT only

Use the Beam UAT (test) environment. Never register a real business or send a real payment. Connecting opens Beam's hosted onboarding portal — confirm it is the UAT portal before entering anything.

You will need: a test company with business bank details set; a second test company without bank details; an accountant login that manages a client (to test per-company scoping); and a developer on hand for the 🔧 cases.

A. Connecting a company to Beam (Integrations)¶

A1 — Beam card shows the correct connection status¶

Steps 1. Log in and go to Settings → Integrations. 2. Look at the Beam card's status badge.

✅ Pass if the badge shows Connected · N (with the number of registered companies) when at least one company is connected, Setup incomplete · N when a company is mid-onboarding, or Not Connected when none are. The count reflects all your companies, not just the active one.

❌ Fail if the status/count is wrong for the companies you have connected — 🟠 Major.

A2 — "Connect" opens the company picker¶

Steps 1. On the Beam card, click Connect (or Connect another if you already have one connected). 2. Observe the dialog.

✅ Pass if a company picker dialog opens listing your companies. Already-connected companies are shown as Connected (green, not selectable); mid-onboarding ones show Setup in progress (also not selectable). Connectable companies are listed first, then alphabetically.

❌ Fail if an already-connected company can be selected again, or the list is empty when you have connectable companies — 🟠 Major.

A3 — A company without bank details is blocked with guidance¶

Steps 1. In the picker, look at a company that has no business bank details. 2. Try to select it and click Continue to Beam.

✅ Pass if the row shows an amber "Add business bank details before connecting" note, and continuing shows an error and sends you to Settings → Business → Bank details (rather than opening Beam).

❌ Fail if you are allowed to proceed to Beam onboarding with no bank details — 🔴 Blocker (Beam registration will fail or be invalid).

A4 — Connecting opens the Beam onboarding portal¶

Steps 1. Pick a company with bank details and click Continue to Beam.

✅ Pass if a success toast appears and the Beam UAT onboarding portal opens in a new tab. The company's status becomes Setup incomplete until onboarding finishes.

❌ Fail if nothing opens, or you see an error even though bank details exist — 🟠 Major. (If the portal is briefly unavailable you should get a clear "onboarding portal temporarily unavailable" message, not a silent failure.)

Steps 1. Ask a developer to make Beam report unhealthy (unreachable). 2. Open Settings → Integrations.

✅ Pass if a "Beam is currently unreachable" banner shows and the Connect button is disabled.

❌ Fail if you can still start onboarding while Beam is unreachable, or no banner appears — 🟠 Major.

A6 — Connect a second, different company (multi-company isolation)¶

Steps 1. With one company already connected, click Connect another, pick a different company, and connect it.

✅ Pass if the second company connects independently and both appear under "Connected for" with their own names. Each company's Beam connection is separate.

❌ Fail if connecting the second company changes or overwrites the first company's connection, or one company shows another company's details — 🔴 Blocker (tenant isolation).

A7 — Accountant connecting for a client (locked scope)¶

Steps 1. Log in as an accountant working inside a client company. 2. Connect Beam.

✅ Pass if the picker step is skipped and Beam connects for the locked client company directly (no chance to pick the wrong company).

❌ Fail if the accountant can accidentally connect Beam for the wrong company — 🔴 Blocker.

B. Beam settings page¶

B1 — Company picker scopes everything on the page¶

Steps 1. With two or more companies connected, go to Settings → Integrations → Beam → Settings. 2. Use the company picker at the top to switch between companies.

✅ Pass if switching the company re-loads the status badge, participant details, and auto-sync settings for the selected company — not the globally active one. It defaults to your active company if that one is connected, otherwise the first connected company.

❌ Fail if switching the picker shows another company's data or doesn't re-scope — 🔴 Blocker (per-company isolation).

B2 — Refresh participant details¶

Steps 1. On the Beam settings page, click Refresh.

✅ Pass if the participant details reload (spinner while loading) and the button is disabled during the refresh.

❌ Fail if refresh does nothing or errors — 🟠 Major.

B3 — Re-register / re-accept¶

Steps 1. Click Re-register.

✅ Pass if it re-opens the Beam onboarding portal in a new tab (same bank-details and health guards as A3/A5 apply). If the selected company has no bank details, it is blocked with the same guidance.

❌ Fail if re-register ignores the bank-details/health guards — 🟠 Major.

B4 — Disconnect Beam (Danger Zone)¶

Steps 1. In the Danger Zone, click Disconnect Beam, then confirm.

✅ Pass if a confirm dialog appears, the company is disconnected with a toast, and the page re-defaults to another connected company (or routes back to Integrations if none remain). The copy explains the Beam-side registration is preserved.

❌ Fail if it disconnects without confirming, or disconnects a different company than the one selected — 🔴 Blocker.

B5 — Reconnect after disconnect¶

Steps 1. After B4, reconnect the same company from Integrations.

✅ Pass if the company reconnects and returns to Connected without having to redo full onboarding.

❌ Fail if reconnection fails or forces full re-onboarding unexpectedly — 🟠 Major.

B6 — Participant sections render read-only¶

Steps 1. View the Organisation / Contact / Address / Direct-Debit / Employers & Funds sections.

✅ Pass if they display read-only, with account numbers masked, and empty sub-cards show "—" or an empty state (no crash).

❌ Fail if an unmasked account number is shown, or a section crashes on missing data — 🔴 Blocker (masking) / 🟠 Major (crash).

Steps 1. Ask a developer to make the participant fetch fail. 2. Open the Beam settings page.

✅ Pass if a banner notes the data may be stale with a Retry button that refetches.

❌ Fail if stale data is shown as if current with no warning — 🟠 Major.

C. Auto-sync settings¶

C1 — Toggle auto-sync topics and save¶

Steps 1. On the Beam settings page, find the Auto-Sync card. 2. Tick/untick topic checkboxes.

✅ Pass if the Save Auto-Sync Settings button appears only when you've changed something; saving shows a success toast. Checkboxes re-initialise when you switch company (auto-sync is per-company).

❌ Fail if Save saves the wrong company's topics, or changes aren't reflected after reload — 🟠 Major.

C2 — Auto-sync topics gate which Beam notifications are fetched 🔧 Needs developer setup¶

Steps 1. Turn off a topic (e.g. Exceptions) and save. 2. Ask a developer to send a Beam notification of that type.

✅ Pass if the disabled topic's notifications are not ingested/shown for that company.

❌ Fail if disabled topics are still processed — 🟠 Major.

D. Beam onboarding callback¶

D1 — Returning from Beam confirms registration¶

Steps 1. Complete Beam onboarding so it redirects back to the /settings/integrations/beam/callback page.

✅ Pass if the page shows a loading→success state and a success toast, and the company's status becomes Registered/Connected. A Back to Integrations button is shown.

❌ Fail if a completed onboarding is not recognised (stuck loading, or shows error) — 🟠 Major.

D2 — Callback with a bad/missing id¶

Steps 1. Open the callback URL with no subscription id (ask a developer for the URL shape, or remove the id parameter).

✅ Pass if a clear error "No subscription ID" is shown with Back to Integrations — no crash.

❌ Fail if the page crashes or silently succeeds — 🟠 Major.

E. Member Verification (MVR) — on an employee's Super tab¶

E1 — "Verify Super" sends a verification for an APRA fund¶

Steps 1. Open Payroll → Employees → [an employee with an APRA fund] → Super tab. 2. Click Verify Super.

✅ Pass if a request is sent, the status row updates (Pending) and a success toast "…sent to fund successfully" appears (or a clear "failed validation — see the activity timeline" message if the fund details are invalid).

❌ Fail if the button does nothing, or a fund with valid details reports a system error — 🟠 Major.

E2 — Verify is hidden/locked when it should be¶

Steps 1. Check the Super tab for: an SMSF employee; an employee missing fund data (no ABN/USI); an employee already Verified; and one Pending within the last 24 hours.

✅ Pass if the button is hidden for SMSF, disabled (locked) when fund data is missing, locked permanently once Verified, and locked while a verification is Pending inside the 24-hour fund window. Hovering shows the lock reason.

❌ Fail if you can fire a verification in any of those locked states (e.g. re-verify an already-Verified member, or spam within 24h) — 🟠 Major.

E3 — "Re-send verification" after the 24-hour SLA lapses¶

Steps 1. On an employee whose verification has been Pending for more than 24 hours, look at the button.

✅ Pass if the label changes to "Re-send verification" and the button is enabled again.

❌ Fail if it stays locked forever after 24h, or lets you re-send before 24h — 🟠 Major.

E4 — "Check for response" on a pending verification¶

Steps 1. On a Pending MVR row in the activity timeline, click Check for response.

✅ Pass if it either updates the status ("Verification status updated.") or tells you the fund hasn't replied yet ("No response from the fund yet. They have 24 hours to reply.").

❌ Fail if it errors or never updates a fund that has responded — 🟠 Major.

E5 — Fund response is applied 🔧 Needs developer setup¶

Steps 1. Ask a developer to simulate a Beam member-verification response (MVOR) for the employee (Verified, and separately a Warning/Failed). 2. Refresh the Super tab.

✅ Pass if the status badge updates to Verified / Warning / Failed accordingly, the "Last checked" time updates, and any fund message (summary/severity/error code) is shown verbatim in the timeline.

❌ Fail if the response isn't applied, or applies to the wrong employee — 🔴 Blocker.

E6 — ERR165 "fund can't accept Payday Super" card 🔧 Needs developer setup¶

Steps 1. Ask a developer to return an ERR165 / not-MIGv3-compliant verification result.

✅ Pass if a dedicated "Fund can't accept Payday Super contributions" card is shown (instead of a generic error).

❌ Fail if ERR165 shows as a generic failure with no guidance — 🟠 Major.

E7 — Member number auto-captured from a fund message 🔧 Needs developer setup¶

Steps 1. Ask a developer to send a Beam member-response carrying a new membership number (code SUPER.GEN.CNTRBTN.1). 2. Re-open the employee's Super details.

✅ Pass if the employee's membership number is filled in automatically from the fund's message.

❌ Fail if the number isn't captured (future contributions for this member would keep failing) — 🔴 Blocker.

E8 — Copy process ID¶

Steps 1. On an MVR timeline row, click the copy icon next to the process id.

✅ Pass if the id is copied to the clipboard (a check icon confirms briefly).

❌ Fail if nothing is copied — 🟡 Minor.

E9 — "Learn more" link¶

Steps 1. Expand About member verification and click Learn more….

✅ Pass if the FAQ expands and the link opens the member-verification guide in a new tab.

❌ Fail if the link is broken — 🟡 Minor.