# ALIS Online Payments — Scoping Questions for Medtelligent

> Drafted 2026-07-15 (Howard / ACG) for the WS9 roadmap item: getting Cascades of Tucson
> onto ALIS's online payment system (resident/family billing payments).
> Community: cascadestucson.alisonline.com, communityId 622.
> Send to Medtelligent support/account rep; loop in Jeff Bristol (accounting@) on replies.

## Product & availability

1. Is the online payments module available on Cascades of Tucson's current ALIS plan, or is
   it a separate subscription/add-on? What is it officially called on your side?
2. Does it cover both one-time payments and recurring/autopay (ACH and credit/debit card)?
3. Can family members / responsible parties pay without an ALIS login, or does each payer
   need a portal account? How are payer accounts invited and managed?
4. Does it support partial payments, split billing between multiple responsible parties, and
   payment plans?

## Pricing & processing

5. What are the costs: monthly/module fee, per-transaction fees (card vs ACH), and any
   setup fee? Who is the payment processor?
6. Can transaction fees be passed to the payer (surcharge/convenience fee), and is that
   configurable per payment method?
7. What is the settlement flow — how and when do funds land in Cascades' bank account,
   and what does the remittance/reconciliation report look like?

## Compliance & security

8. Is the payment flow fully hosted/tokenized by the processor (i.e., Cascades never touches
   card data)? What PCI DSS responsibility, if any, remains on the community?
9. Does the existing Medtelligent BAA cover the payments module, or is an updated
   agreement needed? (Note: we are completing a BAA inventory — please send the current
   executed BAA on file for Cascades.)
10. Where is payment/payer data stored, and what is the data-retention policy?

## Billing integration & reconciliation

11. Do online payments post automatically against ALIS resident ledgers/invoices, or does
    the business office apply them manually?
12. How do refunds, chargebacks, and failed ACH payments flow back into the ledger?
13. Is payment data available through the ALIS API/exports (we pull staff data via API today
    and are building a leadership KPI dashboard — billing/AR aging would be a Phase 1 source)?
14. Does it interoperate with QuickBooks or Bill.com workflows, or is export/import the path?

## Rollout & support

15. What does implementation look like: timeline, setup steps on the community side, bank
    verification, and any business-office training you provide?
16. What family-facing materials exist (announcement templates, how-to guides) for the
    payer rollout?
17. Is there a sandbox/test mode so accounting can validate posting before go-live?
18. Who is our implementation contact, and what does ongoing support look like for payment
    disputes or processor issues?

## Internal notes (not for the vendor email)

- IT side is expected to be near-zero: staff SSO is live; the payer portal is vendor-hosted.
  Confirm nothing is needed on our identity/network side (Q3, Q8).
- Q9 doubles as the BAA chase — the Medtelligent BAA is unverified (wiki: "BAA required
  before PHI leaves"), and the plan's area 4 BAA inventory needs it regardless.
- Answers feed: WS9 rollout decision, area 4 BAA tracker, KPI dashboard Phase 1 source list.
