Walnut — Implementation Playbook (DSO)

Walnut Patient Financing Implementation Playbook

A Strategic Guide for DSO Operators

Prepared for: VPs of Operations, CFOs, Revenue Cycle Leadership Organization Type: Dental Service Organizations (5–50 Locations) Tool Category: Patient Financing / Payment Plans Version: 1.0 | Publication Date: 2026

1. Executive Summary

What Walnut Does

Walnut is a patient financing platform that enables dental practices to offer and manage in-house installment payment plans without routing patients through third-party lenders. The practice sets its own qualification criteria, plan terms, and down payment requirements. Walnut handles the infrastructure: auto-pay scheduling, patient communications, reporting, and collections tracking.

For a DSO, the pitch is different than for a solo practice. The appeal is standardization — deploying a consistent financing offering across all locations, generating portfolio-level data on financing utilization and default rates, and potentially reducing aggregate dependency on external lenders whose discount fees erode per-case margin. A DSO doing $30M+ annually in revenue and routing 15% of that through a 5% lender fee is losing meaningful money on a line item that in-house plans could recapture.

The infrastructure Walnut provides becomes more valuable at scale, where a centralized operations team can monitor plan activity across locations without individual offices managing spreadsheets or calling patients themselves.

Why DSOs Benefit

Expected Timeline: Decision to Full Deployment

• Month 1: Contract, legal review, pilot location selection, configuration
• Month 2: Pilot rollout (2–3 locations), staff training, reporting baseline
• Month 3–4: Portfolio-wide rollout, optimization, integration review

2. Pre-Implementation Checklist

• ☐ Legal review in all operating states: In-house financing may require state-specific disclosures or lender registration; DSO legal counsel must review across your entire footprint before launch
• ☐ Central vs. location-level plan ownership: Decide whether plan approval authority sits at the corporate level, location level, or both
• ☐ PMS landscape across locations: Confirm which PMS systems are in use across your portfolio and what integration Walnut offers for each
• ☐ Payment processor compatibility: Determine if Walnut connects to your existing merchant accounts or requires new processing relationships
• ☐ Bad debt policy: Establish a corporate policy on plan write-off thresholds, collections escalation, and third-party collections engagement
• ☐ Pilot location selection: Choose 2–3 locations with engaged office managers and moderate uninsured patient share for initial rollout
• ☐ Reporting requirements: Define what data finance leadership needs (default rates, average plan size, conversion %, location-level breakdown)
• ☐ BAA and enterprise data security: Confirm enterprise-grade BAA and SOC 2 compliance
• ☐ Training delivery model: Determine whether vendor trains each location directly or DSO trains-the-trainer centrally

3. Implementation Phases

Phase 1: Setup and Configuration (Weeks 1–2)

At the DSO level, configuration is more complex than a single practice. Work with Walnut to define a master set of plan templates — term lengths, minimum treatment amounts, down payment requirements — and determine which settings can be customized at the location level versus locked centrally.

Configure your reporting structure so corporate finance can view aggregated and location-level plan data. This is non-negotiable: if you can't see portfolio-level default rates and plan volumes from a single dashboard, the DSO value proposition breaks down.

Establish your collections escalation protocol: what happens at 30 days past due, 60 days, 90 days. Walnut should automate the early notifications; your team needs a policy for what happens after.

Phase 2: Staff Training and Workflow Integration (Weeks 3–4)

At scale, a train-the-trainer approach is typically more efficient. Identify a financing champion at each pilot location and train them deeply — they then train their location team. Develop a standard patient conversation script that all locations use, ensuring the financing offer is consistent regardless of which team member presents it.

Front desk staff at each location need to know: who approves plans, what documentation is collected, how the auto-pay enrollment works, and where to escalate a patient dispute. These should be documented in a location-level SOP, not improvised.

Phase 3: Full Deployment and Optimization (Month 2+)

After the pilot, review location-level data before rolling out to the full portfolio. Are there locations where the default rate is notably higher? Where case acceptance isn't improving despite plan availability? Those patterns should inform training adjustments or policy tightening before scaling.

Once portfolio-wide, establish a quarterly financing review as part of your revenue cycle cadence. Track average plan size, conversion rate, default rate, and the dollar amount of external lender fees avoided.

4. Integration Considerations

DSOs often operate across multiple PMS platforms — Dentrix, Eaglesoft, Open Dental, Carestack — and Walnut's integration depth will vary. Conduct a PMS compatibility audit before committing:

• For each PMS in your portfolio, confirm whether Walnut writes payments back automatically or requires manual reconciliation
• If multiple PMS systems are in use, some locations may require custom reconciliation workflows
• Evaluate whether Walnut can connect to your centralized reporting or BI infrastructure (data warehouse, Tableau, Power BI)

Payment processing at DSO scale often involves existing merchant relationships with negotiated rates. Determine whether Walnut's processing layer competes with or layers on top of existing agreements.

5. Pricing and ROI Framework

Walnut's pricing at DSO scale is likely negotiated — expect volume-based discounts or a per-location fee structure rather than single-practice pricing. Request enterprise pricing and push for multi-year terms if you're committing to a portfolio rollout.

DSO-level ROI metrics:

At 20 locations averaging $1.5M in annual revenue each, if even 10% of revenue moves through in-house plans and you eliminate a 5% lender fee, the annual saving exceeds $150,000. That math scales quickly.

6. Key Questions to Ask the Vendor

1. Do you have existing DSO clients at our scale — can you provide references?
2. What does your enterprise contract and multi-location pricing look like?
3. How is reporting structured for multi-location organizations — can corporate see all location data in one view?
4. How does your platform handle state-by-state compliance if our locations span multiple states?
5. What is the SLA for support response — do DSOs get a dedicated account manager?
6. How does collections escalation work if a patient defaults — do you have relationships with dental collections agencies?
7. Can plan terms and qualification criteria be locked at the corporate level, preventing individual locations from deviating?
8. What does data portability look like — if we exit, what format is our plan history exported in?
9. How frequently is the platform updated, and how are DSO clients notified of changes?

7. Red Flags and Considerations

• Multi-state compliance complexity: DSOs spanning multiple states face compounding regulatory risk. Walnut must have a robust, state-by-state compliance framework — not just guidance to "consult your attorney."
• Fragmented PMS integration: If half your locations are on one PMS and half on another, expect inconsistent reconciliation workflows and higher admin overhead per location.
• Default rate visibility lag: If you can't see portfolio-wide delinquency data in near real-time, you lose the primary DSO advantage. Confirm reporting latency before committing.
• Staff training at scale: Roll-out fatigue is real. If training materials and playbooks aren't strong, quality will degrade by the time you reach location 15.
• Credit risk absorption: At DSO scale, a 5% default rate on $5M in annual plan volume is $250K in bad debt. Model this explicitly before launch.
• Dependency on auto-pay enrollment: The efficiency gains require patients to enroll in auto-pay; if enrollment rates are low, staff collection burden increases.

8. Avized Verdict

Walnut's DSO value case is plausible but requires disciplined execution. The lender fee recapture math is real, and the standardization argument is legitimate for operations-focused DSOs tired of inconsistent patient financing conversations across locations. However, the platform's enterprise maturity — multi-location reporting depth, state compliance coverage, PMS integration breadth — should be stress-tested during a limited pilot before portfolio commitment.

Best suited for mid-size DSOs (10–30 locations) with a centralized revenue cycle team, significant uninsured patient share, and legal resources to manage multi-state compliance. Proceed cautiously if your portfolio spans more than 5 states or if PMS fragmentation is high.