WORKED EXAMPLE · FICTIONAL DATA
Before you chase a renewal, check the records.
A member may have paid without the payment being matched to the right invoice. A useful AI workflow helps your team find the evidence, separate the exceptions and review the next step.
A membership report you can trace.
All records and amounts are invented. We ran read-only MCP calls locally against sample responses, then calculated this report. The video and screenshots replay those saved results. No AI model or live Wild Apricot account was used.
35-second walkthrough · Fictional sample records · No messages sent or records changed. The written walkthrough below contains the same information.
01 / Ask a specific question.
“Show active members by level. Reconcile October renewal invoices into paid, outstanding and needs-review groups. Recommend the next follow-up for a person to review. Do not send messages or change records.”
02 / Check the source records.
The sample contains 12 contacts, 12 invoices and 7 recorded payments. We retrieved all pages and checked the payment allocations for the 8 nonvoid renewal invoices dated October 1–12, 2026. Event invoices, new applications, voided renewals and September invoices stay outside this report.
Five sample members meet the active definition: 2 Professional, 2 Community and 1 Student. Active membership status and payment evidence are checked separately.
03 / Eight invoices. Three different next steps.
3 paid invoices
Their recorded amounts agree with linked payment allocations. No payment request is proposed for these invoices.
3 outstanding invoices · $260 remaining
These have an unpaid balance without a sample-data exception. Staff should check current records and native reminders before drafting a follow-up.
2 exceptions · hold the follow-up
One contact has an unallocated $120 payment. Another invoice’s paid flag conflicts with its recorded amount. These invented exceptions show why a report needs human review.
Across the 8 invoices: $750 invoiced = $250 recorded paid + $500 remaining. Of that remaining amount, $240 belongs to the two cases held for review. The separate unallocated $120 is not automatically credited to an invoice. All amounts are USD.
Saved demonstration result, October 12, 2026. The numbers above provide a readable alternative to this screenshot.
04 / Give staff a decision they can check.
Before any follow-up, confirm the organization, reporting dates and complete source retrieval. Resolve ambiguous payments, recheck current invoice balances, and review native renewal reminders, previous outreach and bundle recipients. Only then approve a message or record change.
This demonstration sent 0 messages and changed 0 records. Recorded invoice settlement is different from money reaching a bank account or a member authorizing recurring payments.
How this example was verified
The actual MCP client and server completed 13 local calls using injected sample responses: account selection, four contact pages, four invoice pages, three payment pages and allocation checks. Read-only access, pagination and the expected report totals were checked. No external network requests were made.
This is a reproducible sample, not evidence of customer results, time saved or a live AI session. The deliberately inconsistent sample invoice does not establish a defect in Wild Apricot. A real workflow must be tested against its own account and reporting rules.
What does your team still reconcile by hand?
Tell us the report you need, where the numbers come from and what staff do next. We’ll scope the source checks, output and human review around your existing Wild Apricot process.