Starting Light: Your Billing at a Glance

• How many active student accounts does your office bill in a typical term? Options: Under 1,000, 1,000–5,000, 5,001–15,000, 15,000–30,000, Over 30,000
• Tell me how your current term billing cycle runs from SIS record to student statement, step by step.
• Which systems hold the canonical records we need to integrate with for billing, financial aid, and student accounts? Options: Primary student information system, Financial aid system, General ledger/ERP, Learning management records, Other
• Who on your team owns billing rule changes, and who is the day-to-day operator for running statement cycles? Options: Bursar, Student accounts director, Financial aid lead, IT/system admin, Hybrid team, Other
• On average, how many student-facing billing adjustments, appeals, or manual overrides do you process each billing cycle? Options: Fewer than 50, 50–200, 200–800, 800–2,000, Over 2,000
• When a billing cycle completes, what specific artifact do you use to validate accuracy, for example an audit report, sample student statements, or a reconciliation file? Options: Audit report, Sample statements, Reconciliation file, Manual checklist, Ad hoc reviews

Where Errors First Surface in Your Billing Flow

• If a single recurring billing error could be eliminated, which one would reduce calls and complaints the most? Options: Incorrect tuition charge, Missing aid posting, Wrong residency or fee assessed, Duplicate charges, Payment plan miscalculation
• Walk me through the last time that error happened, starting with how it was created and ending with how it was resolved.
• How often do billing exceptions lead to formal student appeals or escalation to the dean or financial aid for resolution? Options: Almost every cycle, Several times a cycle, Occasionally, Rarely
• Who typically discovers billing errors first, and how long on average before the root cause is identified and fixed? Options: Student, Frontline cashier, Financial aid, Bursar team, Other
• What downstream cost or risk do billing mistakes create for you, for example additional staff hours, increased delinquency, or regulatory exposure? Options: Staff overtime and rework, Higher delinquency and cash impact, Compliance reviews or sanctions, Loss of student trust and complaints, Other
• Which single discovery about your billing accuracy would make you stop a vendor evaluation immediately? Options: Inability to handle your refund rules, No secure integration with your SIS, Cannot calculate Title IV refunds correctly, Lack of payment plan flexibility, Unclear 1098-T reporting path

Sponsor and Third-Party Billing, Unpacked

• How confident are you that your current process bills third-party sponsors correctly every time? Options: Very confident, Mostly confident, Sometimes confident, Not confident
• Describe the types of sponsors you bill and the typical invoicing cadence for each, for example employers, military, or international sponsors. Options: Employers, Military, State agencies, International sponsors, Private foundations, Other
• What specific exception patterns do sponsors create, for example retroactive adjustments, partial payments, or approvals tied to course enrollment? Options: Retroactive adjustments, Partial or staged payments, Enrollment-dependent approvals, Sponsor denials after invoicing, Other
• When sponsor invoices are unpaid or reversed, how does that show up in your receivables and collections workflows? Options: Increased past-due balances, Manual reconciliation tasks, Write-offs, Student account holds, Other
• What manual steps would have to stop today for your sponsor billing to be considered scalable and reliable? Options: Manual invoice creation, Email-based approvals, Spreadsheet reconciliations, Phone-based collections, Other
• Do you have a single decisive sponsor scenario that has failed in production and would be unacceptable for a new platform to reproduce? Options: Yes, multiple failed scenarios, Yes, one critical scenario, No, not yet
• Which integration endpoint must be perfect for sponsor billing to succeed, the SIS enrollment feed, sponsor approval workflow, or your AR ledger? Options: SIS enrollment feed, Sponsor approval workflow, Accounts receivable ledger, Payment gateway

Title IV Refunds and Compliance, Head-On

• If you could guarantee one compliance outcome about Title IV refunds, which would change the most for your office? Options: Accurate refund calculations every time, Faster refund disbursements, Clear audit trails and documentation, Fewer corrective actions
• Walk me through how you calculate a Title IV refund today, including where you pull charges, aid, and withdrawal dates from.
• When a refund calculation is audited, which artifacts do you expect to produce, for example calculation logs, student enrollment snapshots, or communications? Options: Calculation logs, Enrollment snapshots, Disbursement receipts, Student communications, Other
• How often have you needed to issue post-disbursement corrections for Title IV errors in the last 12 months? Options: None, 1–2 times, 3–5 times, More than 5 times
• Who ultimately signs off that your refund process is compliant, and how long does it take from discovery to remediation? Options: Bursar, Financial aid director, Compliance officer, General counsel, Other
• What single missing capability in a vendor solution would cause you to halt an implementation because of compliance risk? Options: No Title IV calculation engine, No immutable audit trail, No configurable enrollment snapshots, No secure data transfer

Payment Plans, Delinquency, and Student Experience

• How do your current payment plans affect collection rates and receivables aging? Options: Improve collections, Neutral, Worsen delinquency, Mixed results
• Describe the typical payment plan lifecycle from student enrollment to default or completion and who intervenes at each stage.
• Which payment plan features matter most to you, for example variable installment schedules, auto-debit, late fee rules, or guarantor support? Options: Variable schedules, Auto-debit, Late fee rules, Guarantor support, Grace periods, Other
• When a student misses a payment, what is your current escalation path and how many manual touches does that require? Options: Automated reminders then collections, Multiple manual calls/emails, Immediate hold on records, Outsourced collections
• What measurable improvement in delinquency would justify a change in vendor or process, percent-wise? Options: 10% improvement, 20% improvement, 30% improvement, Any measurable improvement
• If the payment plan module could not integrate with your auto-debit processor, would that stop the project or be an acceptable workaround? Options: Stop the project, Workaround acceptable short term, Unsure

Data, Integrations, and What Could Break Deployment

• If one integration were the single critical path, which would it be, and why would failure there sink the timeline? Options: SIS enrollment feed, Financial aid posting feed, Payment gateway, General ledger export, Other
• Which of your systems already provide APIs or scheduled extracts we can consume for billing and refunds? Options: SIS provides API, SIS provides scheduled extract, Financial aid provides API, Financial aid extract, No APIs/extracts available
• Who owns the credentials and access for those endpoints, and how quickly can you provide test credentials and a sandbox environment? Options: IT owns and can provide within 2 weeks, Business system owner, needs approval, Not sure who owns access, Credentials not available
• How clean is the data we must migrate for billing rules, historic transactions, and student balances, for example percentage clean and common errors? Options: Over 95% clean, 80–95% clean, 60–80% clean, Under 60% clean
• Do you have any technical constraints that would block nightly integration runs or a parallel billing validation window? Options: No constraints, Limited maintenance windows, Strict change control requiring approvals, Sandbox access only during business hours
• Which single integration gap would cause you to pause the project until resolved? Options: No enrollment feed, No aid posting feed, No secure file transfer, No payment gateway access

People, Process, and Acceptance Criteria

• Who are the minimum decision makers and approvers we must satisfy to reach acceptance for core billing, refunds, and 1098-T? Options: Bursar, Financial aid director, CFO, Compliance officer, IT lead, Other
• Describe the test cases you require for acceptance, for example full-term sample bills, Title IV refund scenarios, sponsor invoices, and 1098-T samples. Options: Full-term sample bills, Title IV refund cases, Sponsor invoice flows, 1098-T generated examples, Payment plan enrollments, Other
• How long is your typical acceptance window for a deployment phase and what are your fixed calendar constraints, for example start of term or audit deadlines? Options: 2 weeks, 4 weeks, 6–8 weeks, Depends on term/calendar
• What training model works best for your staff and students, instructor-led sessions, recorded modules, or train-the-trainer? Options: Instructor-led, Recorded modules, Train-the-trainer, Combination
• If acceptance testing reveals a reproducible issue that affects billing totals by more than 0.5%, would you pause go-live until fixed, accept with a remediation plan, or seek financial remedy? Options: Pause go-live, Accept with remediation plan, Seek financial remedy, Unsure

Competitive Landscape and Your Alternatives

• Which options are you actively evaluating right now, including staying with your incumbent, buying another vendor solution, or building internally? Options: Keep incumbent, Buy another vendor, Build internally, Hybrid approach
• What evidence would need to exist for you to decide to stay with your current approach rather than change vendors? Options: Clear cost advantage, No integration risk, Proven audit record, Internal roadmap to fix issues, Other
• Has anyone on your team proposed an internal rewrite or workaround to avoid an outside vendor, and if so what scope was suggested? Options: Yes, full rebuild, Yes, partial patchwork, No internal proposal, Unsure
• What procurement or governance hurdle from your side would be the hardest to clear and most likely to delay a decision? Options: Board-level approval, Budget cycle timing, Security review, Legal contract cycle, Other
• If a pilot proves your top hypothesis about reduced errors or faster refunds, who could sign an order and in what timeline to accelerate the deal? Options: Bursar, CFO, Procurement, VP of finance, Other

Non-Starters and Next Steps

• Which single procurement or technical condition would make this project a non-starter for you right now? Options: No API access, Unacceptable security posture, Cannot support Title IV refunds, No support for sponsor invoicing, Other
• What would a successful pilot look like in concrete terms, including scope, target metrics, and duration? Options: Scope: term billing sample; Metrics: 0 errors in 100 statements; Duration: 4 weeks, Scope: payment plans; Metrics: reduced delinquency 10%; Duration: 6 weeks, Scope: sponsor billing; Metrics: invoice accuracy 99%; Duration: 4–6 weeks, Other
• How soon can you make test credentials, sample enrollment snapshots, and a few representative student accounts available for an initial parallel run? Options: Within 1 week, Within 2 weeks, 2–4 weeks, Longer than 4 weeks
• Which timeline milestone would accelerate a decision if hit, for example a compliant Title IV pilot result or a clean sponsor reconciliation? Options: Compliant Title IV pilot, Clean sponsor reconciliation, Payment plan delinquency improvement, Accurate 1098-T generation
• Who else should we bring into the next conversation to either unblock access or accelerate signoff, and can they join within the next two weeks? Options: IT integration lead, Financial aid director, CFO or budget owner, Procurement or legal, Other

• Solution Experience Session

• Confirm the current state and its cost
• You confirm the demonstrated term billing flow eliminates the manual exception rework described in Discovery.
• Provide a representative extract of one term's billing dataset including typical exceptions and one sample sponsor file for the seller to use in a parallel run.
• You confirm the payment plan and delinquency handling shown will reduce manual follow-ups and improve receivables metrics.
• Proof, term billing scenario end-to-end
• Seller to run a parallel billing cycle using the provided dataset and deliver a results report comparing outputs and highlighting exceptions within five business days.
• Proof, payment plan enrollment and delinquency handling
• Seller to draft an integration dependency checklist and proposed acceptance criteria for billing, payment plans, sponsor invoicing, and Title IV calculations.
• You confirm the Title IV refund calculation shown meets your audit and compliance needs or identify the remaining gaps.
• Proof, third-party sponsor invoicing
• You agree on the integration boundaries and the specific evidence required for acceptance testing.
• Identify the buying committee members and confirm the decision timeline so evidence delivery aligns with your procurement milestones.
• Proof, Title IV refund calculation and audit trail
• Integration and data boundary check
• Validate outcomes with a direct question

• Solution Experience Session
• Solution Experience Deck
• Solution Brief — Tuition Billing Experience

• meeting
• slides
• document

• Configure Term Billing Rules
• Migrate Student and Financial Records
• Integrate with SIS and Financial Aid Systems
• Setup Payment Gateway and Merchant Account
• Deploy Student Self-Service Payment Portal
• Configure Payment Plans and Auto-Draft Schedules
• Implement Third-Party and Sponsor Billing Workflows
• Configure Refund Calculation and Disbursement
• Enable Cashiering and On‑Campus Payments
• Configure 1098-T Tax Document Generation
• Activate Receivables Management and Aging Controls
• Set Up Automated Billing and Payment Communications
• Run Parallel Billing Cycle Validation and Go‑Live Support
• Train Bursar and Student Accounts Staff

Configure Term Billing Rules

• 1. Which term-level charge templates (for example: tuition per-credit template, flat-term tuition, mandatory fee bundles, housing) should be configured as billable artifacts? Options: Tuition per-credit, Flat-term tuition, Mandatory fees bundle, Housing/meal plan, Other (describe)
• 2. How many distinct billing rule sets do you require for a single academic term (examples: full-time, part-time, pro-rated, residency-adjusted)? Options: 1, 2-3, 4-6, 7 or more
• 3. Do you need automatic proration rules for mid-term add/drop and retroactive adjustments tied to your SIS add/drop dates? Options: Yes, No
• 4. List the exact SIS fields (for example: enrollment status, credit hours, residency code, program code) that must feed term billing calculations.
• 5. Specify any term billing cadence exceptions you run today (examples: split-term billing, monthly split within a term, date-based holdbacks for financial aid). Options: Split-term billing, Monthly installments within term, Date-based holdbacks, None, Other (describe)
• 6. Identify the allowable time window between your final SIS roster freeze and production bill generation (hours). Options: Less than 4 hours, 4-24 hours, 24-72 hours, More than 72 hours

Migrate Student and Financial Records

• 7. How many student records (active + historical) do you plan to migrate and which SIS ID field will be the primary key for matching? Options: Less than 5,000, 5,000-25,000, 25,000-100,000, More than 100,000
• 8. Which financial record types need migration (examples: historical invoices, payments, adjustments, payment plans, third-party invoices)? Options: Invoices, Payments, Adjustments/credits, Payment plan enrollment, Third-party invoices, Other (describe)
• 9. What is the minimum acceptable migration accuracy for critical fields (for example: student ID match rate, invoice line-level accuracy) expressed as a percentage? Options: 95%, 97%, 99%, Customer-defined
• 10. Provide the primary export formats available from your current system for student and ledger exports (for example: CSV, fixed-width, XML, direct DB export). Options: CSV / Excel, Database export (SQL dump), XML / XSD, API export, Other (describe)
• 11. What acceptance criteria will confirm migration completeness and be used to sign off migration work (examples: % record match, sample ledger reconciliation, zero critical mismatches)? Options: % student record match, Line-item invoice reconciliation, Payment total comparison, Sample audit checklist
• 12. Identify any legal or compliance constraints on student data migration (examples: state residency data, FERPA restrictions, PII masking requirements). Options: FERPA/PII masking required, State data residency restrictions, None, Other (describe)

Integrate with SIS and Financial Aid Systems

• 13. Which SIS and financial aid endpoints do you require integrated at go-live (examples: SIS roster API, ledger push, financial aid award feed, disbursement notice)? Options: SIS roster/API, Student ledger push, Financial aid award feed, Disbursement notifications, Other (describe)
• 14. How frequently must integrations run for each feed (examples: real-time, hourly, nightly batch) for roster, aid posting, and payments? Options: Real-time / webhook, Every 15 minutes, Hourly, Nightly batch
• 15. Do any of your SIS or financial aid feeds require field-level transformations (examples: aid-to-ledger mapping, award term normalization)? Options: Yes, mapping required, No transformations needed, Need analysis to determine
• 16. List the exact SIS field names we should map for billing and aid (examples: student_id, term_code, credit_hours, aid_type, award_amount).
• 17. Identify the owner and contact for your SIS integration work and whether we will get API credentials or SFTP access for each endpoint. Options: Provide API credentials, Provide SFTP access, Provide DB read-only export, TBD
• 18. Estimate allowable lag between financial aid disbursement posting in your SIS and the platform receiving the award (hours) to meet your receivables policy. Options: <4 hours, 4-24 hours, 24+ hours

Setup Payment Gateway and Merchant Account

• 19. Which payment methods must be enabled at launch (examples: card, ACH/ACH debit, campus cash, wire)? Options: Card, ACH debit, ACH credit, Campus cash / ID card, Wire transfer, Other (describe)
• 20. Do you already have a merchant account or MID that will be used for tuition processing, or is a new merchant onboarding required? Options: Existing merchant account available, Require new merchant onboarding, Need advice to determine
• 21. Which fraud or card acceptance rules must be applied at gateway level (examples: AVS checks, CVV requirement, velocity limits)? Options: AVS required, CVV required, Velocity limits, 3D Secure, None
• 22. Provide your settlement expectations for card and ACH (daily, weekly) and any reconciliation file format required by your finance team. Options: Daily settlement, Weekly settlement, Custom schedule
• 23. Indicate whether you require PCI scope reduction assistance or will retain full PCI responsibilities for on-campus card capture. Options: Need PCI scope reduction, Retain full PCI scope, Unsure, need guidance
• 24. Identify any transaction volume or peak-season limits for gateway throughput we should plan for (transactions per hour/day). Options: Less than 500 tx/day, 500-5,000 tx/day, 5,000-25,000 tx/day, More than 25,000 tx/day

Deploy Student Self-Service Payment Portal

• 25. Which student-facing features must be available at go-live (examples: view bill by term, enroll in payment plan, download 1098-T, authorize third-party payers)? Options: View bills by term, Payment plan enrollment, Download 1098-T, Third-party payer portal, Make one-time payment, Other (describe)
• 26. Do you require single sign-on (SSO) integration with your campus identity provider and which protocol (examples: SAML, OIDC)? Options: SAML, OIDC, CAS, No SSO required
• 27. What language and accessibility requirements must the portal meet (examples: bilingual UI, WCAG 2.1 AA)? Options: English only, Bilingual, WCAG 2.1 AA, Other (describe)
• 28. List the billing and payment documents students must be able to download from the portal (examples: statement PDF, payment receipts, payment plan agreement).
• 29. Specify preferred branding elements for the portal (examples: logo, color hex codes, portal name) and whether you will provide assets. Options: We will provide assets, We need a default template, Require brand review cycle
• 30. Indicate whether you want staged feature rollout (for example, billing-only then payment) or full feature launch at go-live. Options: Staged rollout, Full feature launch

Configure Payment Plans and Auto-Draft Schedules

• 31. How many distinct payment plan templates do you offer (examples: 3-installment, 6-installment, monthly auto-draft)? Options: 1, 2-3, 4-6, 7 or more
• 32. Which auto-draft methods are used for plans (examples: ACH debit, card on file) and which require signed authorization? Options: ACH debit, Card on file, Both, Other (describe)
• 33. Describe your delinquency policy for payment plans including grace periods, late fees, and financial aid hold rules that affect enrollments.
• 34. Do you require proration or payment plan mid-cycle adjustments when aid posts after enrollment in a plan? Options: Yes, automatic adjustment, Manual adjustment by staff, No
• 35. Which communication triggers should be tied to plan events (examples: upcoming draft, failed draft, plan completion)? Options: Upcoming draft, Failed draft, Plan completion, Missed payment reminders, Other (describe)
• 36. Identify thresholds for automated collections escalation tied to aging buckets (for example: escalate at 60 days past due). Options: 30 days, 60 days, 90 days, Custom

Implement Third-Party and Sponsor Billing Workflows

• 37. Which sponsor types do you bill at launch (examples: employer tuition assistance, VA/military, international sponsors, state agencies)? Options: Employer tuition assistance, VA/military, International sponsors, State agencies, Other (describe)
• 38. What invoice formats are required by your sponsors (examples: PDF invoice, EDI, XML with PO reference) and which delivery methods are used? Options: PDF by email, EDI, XML via SFTP, Portal access, Other (describe)
• 39. Do sponsor agreements require conditional billing rules (examples: cap per term, percent coverage, billing only after Roster verification)? Options: Yes, conditional rules, No, flat coverage
• 40. List the fields your sponsor invoices must include for reconciliation (examples: sponsor PO number, student ID, term code, charge breakdown).
• 41. Specify any sponsor invoicing cadence requirements (examples: monthly, term-end, triggered after a course completion event). Options: Monthly, Term-end, Event-triggered, Other (describe)
• 42. Indicate who owns sponsor dispute resolution and the SLA for sponsor invoice disputes (days to respond). Options: We own disputes, You own disputes, Shared ownership

Configure Refund Calculation and Disbursement

• 43. Which refund calculation methods should the platform support at launch (examples: Title IV refund worksheet, pro rata term refund, manual override)? Options: Title IV refund calculation, Pro rata term refund, Manual overrides, Other (describe)
• 44. Do you need automated Title IV return of funds calculations based on institutional attendance records and disbursement dates? Options: Yes, No
• 45. Which refund disbursement methods do you require (examples: ACH to student, check, refund to card, campus account credit)? Options: ACH to student, Check, Refund to card on file, Campus account credit, Other (describe)
• 46. List the refund hold rules you apply today (examples: unresolved financial aid, unresolved enrollment hold, list of business units requiring manual approval).
• 47. What reconciliation evidence do you require after refunds (examples: per-term refund summary, payment method totals, bank return file match)? Options: Per-term refund summary, Payment method totals, Bank return file match, Other (describe)
• 48. Indicate any regulatory or institutional thresholds that require manual review before refund release (examples: refunds over $X, Title IV special cases). Options: Refunds over $500 require review, Refunds over $1,000 require review, No threshold, Custom threshold

Enable Cashiering and On‑Campus Payments

• 49. Which on-campus payment capture methods must be supported at go-live (examples: cash window, campus card kiosk, cashiering POS)? Options: Cash window, Campus card kiosk, Cashiering POS, Check intake, Other (describe)
• 50. Do you require real-time posting from cashiering terminals into the student ledger and which field maps must be preserved (example: tender type, receipt number)? Options: Yes, real-time posting, No, batch posting daily, TBD
• 51. Specify reconciliation cadence for on-campus receipts and whether daily vault balancing reports are required. Options: Daily reconciliation, Weekly reconciliation, Monthly reconciliation
• 52. List any payment acceptance constraints at physical locations (examples: cash-only windows, no card acceptance at satellite locations).
• 53. Identify whether cashiering staff require a separate UI and which till/receipt numbering conventions must be preserved. Options: Separate UI required, Use same portal with cashier role, Other (describe)
• 54. Do you need integration with campus ID card systems for campus cash application and refunds? Options: Yes, No

Configure 1098-T Tax Document Generation

• 55. Which 1098-T box population rules do you follow for box 1 and box 2 reporting (examples: payments received method, amounts billed method)? Options: Payments received method (box 1), Amounts billed method (box 2), Custom institutional policy
• 56. Do you require TIN/SSN validation and masking rules for student records when generating 1098-T forms? Options: Yes, validate and mask, Mask only, No
• 57. List the months or term cutoffs you use to determine calendar-year tax reporting boundaries for 1098-T generation.
• 58. Which delivery methods do you want for 1098-T (examples: secure portal download, print-and-mail, bulk file for third-party tax vendor)? Options: Secure portal download, Print-and-mail, Bulk file export, Other (describe)
• 59. What acceptance criteria will confirm correct 1098-T generation (examples: sample of X students validated against ledger, zero mismatches for box totals)? Options: Sample audit of X students, Zero critical mismatches, Box totals match ledger totals
• 60. Identify any institutional carve-outs for 1098-T (examples: non-reportable scholarships, employer-paid tuition) that must be coded into generation rules.

• Order Form / Subscription Agreement
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Data Processing Agreement (DPA)
• Integration & Data Transfer Addendum
• Milestone Schedule & Acceptance Criteria
• Change Order Agreement

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate Review (around day 90)
• Ongoing Success Review, Quarterly

• Log agreed enhancement requests into the backlog with required evidence and expected review date.
• Restate acceptance criteria and documented targets
• Produce a documented acceptance decision against each Solution Scope criterion and capture the buyer signatory for the record.
• Confirm the incumbent system is formally decommissioned or retained read-only and data archiving completed or scheduled.
• Define remediation deliverables and verification timeline for any unmet criteria to achieve final acceptance.
• Publish the acceptance record listing pass/fail status per criterion and include the named buyer signatory or documented buyer approval.
• If applicable, create a remediation plan with milestones and verification tests for each failed acceptance criterion.
• Submit incumbent decommission checklist showing data archived, access removed, and contract renewal actions completed or escalated.
• KPI trend review
• Confirm that billing error rate and payment plan delinquency rate remain within agreed bounds or have a remediation plan with dates.
• Ensure user adoption and integration error counts demonstrate stable operations or have named actions to correct trends.
• Prioritize enhancement requests for the next release window and confirm next review cadence.
• Publish a quarterly success summary with KPI trends, open incidents, and agreed enhancement priorities.
• Create or update mitigation plans for any KPI trending off-target, with milestone dates for correction.
• Re-confirm success criteria and ownership
• Confirm that initial billing runs and key integrations completed without critical failures.
• Agree owners and resolution dates for all open incidents through a short remediation plan.
• Validate that training completion and portal access are sufficient to proceed to KPI measurement.
• Publish a go-live validation report that lists run results, open incidents, and remediation owners.
• Execute priority bug fixes and configuration updates identified during triage within 7 days.
• Provide a snapshot of portal access counts and staff training completion for the first 14 days.
• Present first KPI results
• Determine whether billing error rate and payment plan delinquency rate are trending toward Solution Scope targets or require remediation.
• Agree a prioritized corrective action list with target dates to address the top 3 metric gaps.
• Confirm readiness status and evidence required for the acceptance gate at day 90.
• Deliver a corrective action tracker listing each remediation, its rationale, and target completion date.
• Run targeted parallel billing validation for the identified exception scenarios and report results before the acceptance gate.
• Produce a data extract demonstrating 1098-T generation samples and reconciliation steps used for accuracy verification.
• Deployment and migration validation
• Ongoing incidents and compliance questions
• Root-cause diagnosis for gaps
• Present outcome data per criterion
• Corrective action agreement
• Document pass/fail per criterion and formal acceptance decision
• Enhancement and backlog triage
• Early adoption and usage signals
• Confirm timeline to acceptance gate
• Open issues and incident triage
• Incumbent system wind-down review
• Action tracking and next steps
• Agree remediation items and resolution timeline
• Immediate remediation actions