Flexible & Health Savings Account Admin
Multi-stakeholder benefits decisions where employer groups, brokers, and members must align on coverage and cost.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome Discovery
Align on desired outcomes, current benefits programs, participation and engagement goals, compliance constraints, and key stakeholders.
Discovery Questions
A quick snapshot of your benefits landscape
- Tell me about the account types you offer today and the approximate number of active participants in each (HSA, FSA, HRA, commuter)
- Describe how your annual enrollment cadence works, including any midyear eligibility events
- Share which payroll connectivity approach you currently use for benefits deductions
- Which of these account administration activities are handled in-house versus outsourced
- How do new hires typically get set up for accounts, and how long until they can access their funds
Where employees actually get stuck
- If participation and engagement don't improve this year, which business outcome would be most affected for your team or finance partners
- Identify the top three participant friction points you hear about most from employees
- How often does your team receive participant tickets that require manual substantiation or paper documentation
- Give a recent example of a participant issue that required cross-team escalation and tell me why it escalated
- Which single operational failure would make you pause supplier selection or an implementation immediately
Compliance risks that carry real consequences
- Describe a situation where a compliance lapse or audit finding changed how you thought about your vendor choices
- List the IRS or regulatory requirements you consider nonnegotiable for any admin platform
- Does your benefits team run internal audits or compliance checks on plan data, and how often
- Who in your organization must sign off on plan design changes, compliance exceptions, or audit responses
- Would an inability to provide audit-ready reports within 30 days rule a vendor out of consideration
Payroll and integrations, where timelines break
- Pinpoint the single integration failure that has caused the longest delay in prior benefit rollouts
- Select the payroll systems or payroll delivery methods you must support for a successful integration
- Who owns the payroll connection at your company and who do we need to contact to validate access
- Identify which participant data fields must be present in the first feed for activation
- Are there any contractual or security rules from your payroll vendor that could block exchanging participant files
Who decides and how success gets measured
- Name the one executive or committee whose buy-in would accelerate a signed agreement
- Outline the top three metrics your team uses to evaluate benefits vendor performance
- Rank these outcomes by priority for the next 12 months
- Suppose a pilot reaches your target adoption numbers, describe any internal approvals that would still be required before full rollout
- Would achieving your numeric pilot goals remove procurement or budget obstacles and allow signing within your desired timeline
Operational readiness and the data reality
- Pinpoint the single data quality issue that would stop a launch if it remains unresolved
- Estimate how complete and clean your employee roster and eligibility data are today
- Does your team have a dedicated technical lead and at least one resource available to support integration and testing
- Provide the typical timeline your IT team needs to approve API credentials or file exchange access
- Name any regulatory approvals, union agreements, or legal reviews that could materially delay an implementation
Alternatives on the table and why they might win
- Share the other solutions you are actively evaluating, including your incumbent and any internal build options
- Select the single reason you might prefer to stay with your current provider
- Would anyone on your team advocate for an in-house solution instead of a vendor, and who would that be
- Are there contract terms or legacy data constraints from your incumbent that would keep you from switching even if the new platform met your targets
- Why would your benefits broker or consultant recommend staying with the current approach rather than moving to a new partner
Acceptance criteria that will make procurement sign
- List the single measurable outcome that would allow you to commit to a vendor within 30 days of pilot completion
- Set numeric targets for the following, if applicable: participation lift, time to activate, reconciliation error rate
- Suppose the platform cannot meet one of your top three metrics during pilot, describe the threshold or contingency that would still allow a go/no-go decision
- Rate how flexible you are on commercial terms if the solution delivers above-target operational results
- Confirm whether procurement or finance has pre-set deal-size limits that require executive approval
Timeline, blockers, and clear next steps
- When is your target launch date for a new benefits administrator, and is that date fixed
- Estimate how long your legal and data security review process usually takes for a new vendor
- Summarize any internal initiatives or technology projects that could block implementation during your desired window
- Flag the single person or committee that will raise the final objection if the project stalls
- Specify the next action you want from the seller after this discovery to move toward a decision
-
Solution Experience
Walk through how the platform delivers targeted outcomes using the buyer's payroll, enrollment, and participant-service scenarios.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost
- You confirm the demonstrated payroll integration removes the manual upload and reconciliation steps you described.
- Provide a representative payroll file, the current enrollment export, and a list of 3 participant service scenarios to test before the session.
- Walk through payroll-to-account scenario with your data
- You confirm the participant workflows shown reduce support handling time and map to the adoption improvements you need.
- Identify a pilot cohort and define 2 success metrics and their measurement windows for the pilot.
- Prove participant-service scenario
- Run the provided sample payroll and enrollment scenarios in a test environment and deliver the scenario runbook, results, and a recording before the follow-up session.
- You agree on a concrete set of evidence items and acceptance criteria required before a deployment decision.
- Provide plan rules for contribution limits and eligibility exceptions to validate compliance controls against your design.
- Show compliance and eligibility controls against your plan rules
- Validate the future state
- Agree on remaining evidence and next steps
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define account types, banking and payroll integrations, participant features, compliance controls, reporting, responsibilities, and measurable acceptance criteria.
Scope Configuration
- Configure plan designs and IRS contribution limits
- Provision participant accounts and enrollment
- Integrate payroll for pre-tax contributions
- Issue and activate healthcare debit cards
- Enable mobile app and web access
- Deploy auto-substantiation for point-of-sale expenses
- Set up HSA investment portal and custodial options
- Manage claims submission, adjudication, and reimbursements
- Establish custodial banking and funds settlement
- Run non-discrimination testing and compliance monitoring
- Migrate participant and payroll data from prior provider
- Activate employer admin portal and reporting dashboards
- Configure real-time eligibility verification
- Operate participant customer service and dispute resolution
Scope Questions
Configure plan designs and IRS contribution limits
- Which account types will you offer at launch (select all that apply: health savings account HSA, flexible spending account FSA, health reimbursement arrangement HRA, dependent care account, commuter)?
- How many plan variations (distinct benefit designs) do you require for the initial go-live (for example: single HSA plan, dual HSA/FSA option across employee classes)?
- Who on your benefits team owns plan design decisions and will sign off on IRS limit configurations?
- When configuring HSA limits do you require automatic annual updates tied to IRS published limits or manual annual adjustment by your admin team?
- Provide the eligibility classes that affect plan enrollment (for example: full-time hourly, salaried exempt, part-time 20+ hours, union employees) and indicate which account types each class may elect.
- Select which IRS-related compliance artifacts must be generated for your plans: contribution limit audit report, annual Form 5500 inputs, participant year-end statements, or other.
Provision participant accounts and enrollment
- How will employees enroll: through single-sign-on from your HRIS, a separate enrollment portal, or paper forms to be uploaded?
- Approximately how many participant accounts must be provisioned at go-live (headcount or estimated active participants)?
- Describe the data fields required for account provisioning (for example: legal name, SSN last 4, date of birth, hire date, eligibility status) and indicate any fields that are currently missing from your source feed.
- Which enrollment events should trigger account provisioning or changes (new hire enrollment, life event, rehire, QLE documentation)?
- Are there multi-company or multi-division hierarchies that require separate employer IDs for accounts and reporting?
- Do you expect we should handle participant welcome communications and initial enrollment confirmations or will you provide those messages?
Integrate payroll for pre-tax contributions
- Which payroll provider or system will supply contribution files and ongoing payroll feeds? (name your current payroll system or indicate if using a payroll bureau)
- Which payroll file formats and transport methods will be used for sending contribution files or receiving payroll confirmations (for example NACHA ACH file, CSV payline export, SFTP delivery, API endpoint)?
- How often do you process payroll contributions that need to flow to the accounts (each payroll run frequency e.g., weekly, biweekly, semi-monthly, monthly)?
- Identify the primary payroll contact who can provision API keys, SFTP access, or scheduled file transfers for initial integration and ongoing troubleshooting.
- Which payroll deduction fields must map to account types (for example: pre-tax HSA elective amount, pretax FSA contribution code, employer HRA funding code)?
- What defines successful payroll integration acceptance for your payroll team (for example: two consecutive payroll cycles processed with zero contribution reconciliation exceptions)?
Issue and activate healthcare debit cards
- How many physical debit cards should be issued at launch and how many participants should receive virtual cards only?
- Which card activation methods do you require: phone IVR, mobile app activation, web activation, or employer pre-activated distribution?
- List any card controls you require at go-live (for example: MCC blocking for non-medical merchants, single-merchant exclusion, per-transaction limits, ATM restrictions).
- Who will own card dispute escalation within your HR or finance teams and what is the expected SLA for initial dispute acknowledgement?
- Are you expecting cardholder funding to be real-time at point-of-sale or batched settlement from employer-funded accounts?
- Specify the acceptance criteria for card issuance and activation (for example: X% of distributed cards activated within 14 days and no more than Y% returned undelivered).
Enable mobile app and web access
- Which authentication methods must be supported for participant access (for example: SSO via SAML/OAuth, email/password, biometric unlock on mobile)?
- What participant features are mandatory in the mobile app at launch (balance view, transaction history, receipt upload, claims submission, investment portal access)?
- Describe any corporate branding or text changes required in the portal and whether you will provide brand assets (logo, color hex codes, copy) prior to configuration.
- When do you expect mobile app store provisioning and what is your timeline requirement for iOS and Android availability?
- Identify required accessibility standards or corporate policies the portal must meet (for example: WCAG 2.1 AA, mobile accessibility guidelines).
- Are push notifications and transactional SMS messages required for card activity and claims updates, and do you have an SMS consent policy to share?
Deploy auto-substantiation for point-of-sale expenses
- Which merchant categories or point-of-sale data sources should be prioritized for auto-substantiation (for example: pharmacies, urgent care, dental offices, eligible medical merchant category codes MCCs)?
- How do you want the platform to handle transactions missing merchant category codes or with ambiguous MCC assignments?
- Provide any existing rules your plan uses for auto-adjudicating transactions (for example: threshold amounts auto-approved, recurring prescriptions auto-approved).
- Which participant communications are required when a transaction is auto-substantiated versus when manual receipt is requested?
- Specify the acceptance test for auto-substantiation accuracy (for example: 95% correct auto-approval rate on sampled pharmacy transactions across 30 days).
- Who will own exception adjudication for transactions that fail auto-substantiation and what turnaround time do you expect?
Set up HSA investment portal and custodial options
- Which investment features must be available at launch (for example: self-directed brokerage, employer default investment menu, automatic sweep to investments at a balance threshold)?
- Do you have a preferred custodian or do you require a vendor-agnostic integration that supports multiple custodians?
- List acceptable investment account minimums and any participant eligibility rules for investing (for example: minimum HSA balance $1,000, enrolled employees only).
- How should investment reporting be delivered to participants and to your finance team (daily NAV feeds, quarterly statements, API access)?
- Identify the custodian onboarding documents we should expect from your side (W9, organizational resolution, custody agreement) and whether they are already available.
- Are employer HSA matching or employer-directed investment contributions planned and how frequently should they post?
Manage claims submission, adjudication, and reimbursements
- Which claims submission channels do you want enabled at go-live (mobile receipt upload, web claims form, mail-in paper claims, vendor EDI)?
- What adjudication SLA do you require for typical FSA claims and for escalated HRA reimbursements (for example: 3 business days for standard claims)?
- Describe your desired reimbursement methods for approved claims (direct deposit ACH to employee bank, reimbursement to payroll, check mailed).
- Are subrogation or coordination-of-benefits workflows required for claims adjudication and do you have existing vendors to integrate for COB?
- Provide any required document retention periods or evidence rules for substantiation (for example: retain receipts for 6 years per IRS documentation expectations).
- Who on your compliance or benefits team will review adjudication exception reports and what is the expected review cadence?
Establish custodial banking and funds settlement
- Which bank relationship will be used for custodial accounts or do you require us to provision a new custodial bank account?
- Which settlement method do you require for employer funding and participant reimbursements (ACH debit/credit, wire transfers, same-day ACH)?
- Identify the bank account and routing data fields we will need from your treasury team and whether micro-deposit verification is permitted.
- Specify the expected reconciliation tolerance between payroll remittances and custodial settlements (for example: net variance less than 0.5% per cycle).
- Are there required fund float rules for your organization (for example: employer holds float for X days before settlement) or fiduciary constraints to observe?
- Who is the treasury contact for bank onboarding and ACH authorization (name and role)?
Run non-discrimination testing and compliance monitoring
- Which nondiscrimination tests do you require at go-live and on what cadence (for example: IRC Section 125 eligibility testing for FSAs annually)?
- How should failed nondiscrimination test results be remediated and who on your team approves remediation options (for example: corrective contributions, participant refund)?
- Provide the compliance monitoring reports you need for HR and finance (for example: eligibility exception report, contribution limit violations, substantiation failure rates).
- Are you subject to any additional regulatory regimes that affect plan operation (for example: state-level mandates, collective bargaining agreements)?
- Identify the frequency you want compliance checks run (daily transaction scanning, weekly summaries, monthly audit reports).
- Who will be the designated compliance owner for receiving exception alerts and taking corrective action?
-
Mutual Commit
Finalize commercial and legal terms, SLAs, data security and privacy obligations, implementation milestones, and mutual responsibilities.
Agreement Modules
- Order Form / Subscription Agreement
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Data Processing Agreement (DPA)
- HIPAA Business Associate Addendum (BAA)
- Go-Live Acceptance Certificate
- Roles & Responsibilities and Escalation Matrix
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Capture concrete readiness facts — payroll provider, system owners, data sources, timelines, and testing contacts required before execution.
Pre-Deployment Questions
Environment and site access
- Production payroll topology the deployment must integrate with (select the category) — this tells us whether we need single or multi-feed sequencing.
- Are production or sandbox test environments available for each system the platform will connect to (payroll, HRIS/roster, bank)? If yes, list each environment name and the date it will be accessible to the deployment team (so we can schedule integration testing).
Data and configuration
- Who is the authoritative source of participant eligibility and contribution data (system name and owning team) — this is the source of truth we will reconcile against.
- Has the field-mapping approach for payroll → platform data been decided (who will own mapping and validation)?
- Which of these data transfer methods will be required (select all that apply) — this determines connectors and security patterns.
People and ownership
- Provide the named primary owner (name, role, phone or email) we should contact for each workstream: payroll, HRIS/benefits, IT/security, and banking/finance (so tasks and approvals have clear assignees).
- Who will serve as the buyer's primary testing/contact lead for participant-facing acceptance testing (name and preferred contact) — this person will coordinate pilot sign-ups and UAT feedback.
- Are there executive, legal, or procurement approvers whose sign-off is required before go-live? If yes, list the approver role and the specific decision criterion they approve (commercial, legal/contract, compliance, other).
Timing and constraints
- List any recurring blackout windows or payroll processing cutoffs when configuration or cutover changes are prohibited (for example: pay-period freeze, month-end, fiscal close) — this prevents scheduling conflicts.
- Target go-live window or hard deadline the deployment must meet (select the best option) — the deployment schedule will use this to set milestones.
-
Integration & Configuration
Lock integration credentials, API endpoints, field mappings, bank account and card provisioning details, and environment access the deployment team will use.
Configuration Details
ENVIRONMENTS & ENDPOINTS
- Environment canonical name (enter the exact environment name the deployment build will use; examples: 'prod-us-east-1' or 'sandbox-us-east-1'; Default: 'prod-us-east-1')
- Platform API base URL the build will call (format: https://api.example.com — enter production or sandbox base URL exactly)
- Environment region (Default: US - East)
AUTHENTICATION & ACCESS
- Authentication method for API integrations (Default: OAuth2 Client Credentials)
- Integration client identifier (enter the non-secret client_id or integration user name the build will reference; do NOT paste secrets)
- Secret exchange channel for sensitive credentials (how will the deployment team retrieve the secret at kickoff? Default: your secrets manager)
FIELD MAPPINGS & DATA MODEL
- Canonical source system for participant/master data (select the single source the build will ingest; Default: Payroll provider)
- Participant data mapping endpoint or file location (enter exact URL, S3 path, or file path the build will pull; formats: https://..., s3://bucket/path, or /path/to/file)
- Source field name for employee identifier (enter the exact source field name that maps to platform 'participant_id')
- Source field name for payroll deduction amount (enter the exact source field name that maps to platform 'pre_tax_deduction')
BANKING & CARD PROVISIONING
- Primary funding account type (Default: ACH operational account)
- Non-secret bank account identifier the platform will reference (enter account nickname, virtual account ID, or bank-provided reference label; DO NOT paste account numbers or routing numbers)
- Card provisioning method (Default: Issuer-hosted tokenized provisioning)
- Card program identifier or BIN mapping key (enter the non-secret program ID or 'N/A' if not applicable)
-
Deployment
Execute rollout with pilots, testing, training, cutover sequencing, owners, and escalation paths.
-
-
Success
Confirm adoption and compliance targets, conduct recurring service reviews, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live health check (week 1-4)
- First measurement review (week 4-10)
- Acceptance gate and formal acceptance (around day 90)
- Ongoing quarterly success review
Issues & Enhancements
- Close any remaining compliance exceptions and confirm remediation evidence in the shared channel.
- Implement payroll reconciliation fixes to address missing or mis-mapped deduction records.
- Launch targeted participant communications or training to improve enrollment and contribution setup rates.
- Restate acceptance criteria and numeric targets
- Produce a documented pass/fail decision for each acceptance criterion listed in Solution Scope.
- Agree remediation actions and a timeline to resolve any failed criteria, with verification checkpoints.
- If replacing an incumbent, confirm the legacy system's decommission or retained-read-only status and data migration completion.
- Publish the acceptance decision record with pass/fail results and any remediation plans.
- Schedule remediation verification checkpoints prior to final acceptance closeout if criteria failed.
- Complete archival or migration steps for legacy system data and confirm access status of retired system if incumbent is decommissioned.
- Quarterly metrics trends
- Confirm the solution remains on track against participant adoption and auto-substantiation targets in Solution Scope.
- Ensure open issues are being actively worked and remediation is progressing or completed.
- Agree prioritized enhancement requests and concrete actions for the next quarter.
- Update the shared dashboard with the latest quarterly metrics and circulate for async review.
- Assign owners and target dates for the top three enhancement requests to be addressed next quarter.
- Confirm success criteria and owners
- All deployment validation checks completed and documented with owners for unresolved items.
- Early adoption signals captured and classified as healthy or requiring remediation.
- Issue tracker populated with owners and dates for all high-priority blockers.
- Publish the hypercare issue tracker with owners and target resolution dates.
- Provide a one-page status of payroll feed confirmations and card provisioning counts for the first 7 days.
- Execute the agreed immediate remediation tasks and report status before the first measurement meeting.
- Identify root causes for any metric shortfalls and document specific remediation actions with deadlines.
- Confirm timeline and readiness criteria for the acceptance gate meeting.
- Present first-period outcome data
- Determine if participant adoption rate and payroll contribution setup completion rate are trending toward Solution Scope targets.
- Publish the measurement dataset and dashboard used in the meeting for ongoing tracking.
- Service performance review
- Review transaction integrity metrics
- Present outcome data against each criterion
- Deployment and data migration validation
- Early onboarding and usage signals
- Root-cause analysis for gaps
- Open issues burn-down
- Document pass/fail per criterion and record decision
- Agree corrective actions, owners, and dates
- Blockers and open issues triage
- Enhancement requests and backlog status
- Agree remediation plan for any failed criteria
- Agree immediate remediation actions
- Incumbent system wind-down verification (if applicable)
- Confirm acceptance gate timeline
- Agree next-quarter actions and checkpoints