Academy / Week 4 / Forms & Payments Implementation / Provider Selection in Payment Write-backs

Provider Selection in Payment Write-backs

Lesson 15.7⏱ ~7 minWeek 4

πŸ’‘ Why This Matters

Provider selection is an optional field in Weave but is often mandatory in the PMS. Getting this wrong means the PMS ledger doesn't show which provider performed the procedure β€” a real billing problem for offices. This lesson explains why it matters and how to handle it.

🎯 What You'll Learn

  • Why provider selection matters: PMS ledgers need to track which provider generated which revenue
  • When provider selection is mandatory vs optional: Weave = optional, but some PMS vendors = required
  • The two failure scenarios: PMS mandates a provider value, OR office staff need it for their internal ledger
  • How to handle the mandatory provider scenario in write-back implementation
  • What happens when provider is missing: the invoice is created but the PMS ledger doesn't show provider details
  • How offices escalate this as a support issue when their PMS ledger is incomplete

β–Ά Watch Video

Open in Google Drive πŸ’‘ Open in Drive for AI-powered transcript search

πŸ“‹ Lesson Summary

When creating a payment invoice in Weave, provider is an optional selection. However, some PMS vendors mandate a provider value in their payment API. Additionally, even when not technically mandated, offices often need the provider in their PMS ledger for financial reporting β€” tracking which provider's procedures generated which revenue. When provider is missing from a write-back, the PMS creates the payment record but without provider attribution. Offices then escalate this as a bug. The solution in the integration code: always attempt to pass a provider value; if Weave doesn't have one, look up a default provider for the office.

🏷 Key Concepts

Provider SelectionOptional vs Mandatory FieldsPMS Ledger AttributionInvoice Provider FieldFinancial ReportingDefault Provider LookupProvider Compensation TrackingWrite-back Field Requirements

⭐ Key Takeaways

01Always check whether the PMS mandates a provider in the payment API β€” failing to do so causes hard-to-debug PMS errors
02Even when not mandatory, missing provider attribution causes real problems for office billing workflows
03Implement a default provider fallback: if no provider is selected in Weave, look up the office's default provider
04This is a common support escalation pattern β€” if an office reports missing provider details in their PMS ledger, check the write-back provider field
05Document whether a PMS requires provider in the payment feasibility doc before implementation