These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Veterinary Practice Mgmt
- Features
- Billing and Reporting
Billing and Reporting
Bill completed services from limited visit information and reconcile patient-scope payments.
OverviewConfirmed Payments×
Veterinary Practice Mgmt · Billing and Reporting
New
Confirmed Payments
Payments
| Id | Patient | Received at | Amount | Reference | Status | |
|---|---|---|---|---|---|---|
| IDD-833 | PTN-63361 | 10 Oct | 490 | RFR-300 | Confirmed | |
| IDD-552 | PTN-46033 | 02 Oct | 950 | RFR-491 | Confirmed | |
| IDD-966 | PTN-71434 | 08 Oct | 860 | RFR-546 | Confirmed | |
| IDD-146 | PTN-90824 | 05 Oct | 440 | RFR-733 | Confirmed | |
| IDD-564 | PTN-83720 | 01 Oct | 390 | RFR-979 | Confirmed |
6 of 6 records
IDD-833Payments · PYM-95315
ConfirmedPatientPTN-63361
Received at10 Oct
Amount490
ReferenceRFR-300
What you can do
Connect the service charge to completed care
The service charge links service description and amount to encounter, with status Draft, Approved, Invoiced or Voided. Payments hold patient, received date, amount and reference with status Pending, Confirmed or Refunded. The billing workflow validates a charge for completed care, checks the service description and USD amount, advances it through Approved to Invoiced, and ingests a confirmed patient payment.
For a rehearsal, bill the vaccination service recorded during Milo’s Completed encounter. Select that encounter and confirm the service description and amount. Check the resulting charge alongside the payment for the corresponding patient. A draft charge or pending payment remains distinguishable from an invoiced service and confirmed money.
How the work is organized
- Billing projection. The workflow reads only encounter identity, patient identity, visit type and status for its billing decision. Clinical notes and observations stay outside that read scope. Billing Staff can understand the service without reading the clinical narrative.
- Charge outcome. The workflow validates the submitted charge and advances it through Approved to Invoiced. Billing Staff checks the resulting service amount and patient context. Completed clinical care remains the prerequisite for submission.
- Reconciliation scope. Follow the charge’s encounter to its patient, then compare Invoiced charge amounts with Confirmed payments for the agreed reporting scope. Use the patient comparison to investigate recorded charges and receipts in the agreed scope.
What to agree during setup
Agree how service descriptions and USD amounts are entered and checked. Configure external accounting and payment processing with their responsible owners before relying on the handoff. A local invoiced state must be reconciled with any external ledger before treating the external posting as complete.
Define the date scope used for reconciliation. Each payment carries received date, while encounter dates are available through the charge’s reference. Explain the encounter-date boundary used for the charge side of the comparison. Retain Pending and Refunded payments as distinct outcomes when interpreting totals.
Configure Billing Staff access around the minimal billing projection. The role’s ability to view encounter billing context must not expose clinical notes or observations through a direct record request. Test the actual access with an ordinary Billing Staff account before wider use.
Check the handoff on an actual case
Submit Milo’s valid service charge for the Completed encounter and inspect the move through Approved to Invoiced. Confirm that its encounter resolves to the intended patient and that the workflow records the confirmed payment in that patient scope. Reconcile the recorded amounts using the agreed date interpretation.
Repeat against an encounter still awaiting review and verify that it cannot be treated as completed care for billing. Submit a charge missing service description or a valid USD amount and inspect the rejection. Then attempt to read clinical notes as Billing Staff, confirming that the workflow’s restricted read scope remains effective.
Before acting on a reconciliation difference, inspect the service charges and confirmed payment references behind it. Check that the encounter resolves to the intended patient and that both sides use the agreed reporting scope. Retain unresolved amounts for Billing Staff to investigate before claiming that the patient account agrees.
What your team sees
- Charges Awaiting Invoice — Identify Draft or Approved service charges awaiting their billing outcome.
- Confirmed Payments — Inspect confirmed patient payments with amount, date and reference.
Follow the work through
Rehearse billing and reconciliation after clinical review. Agree external handoffs through integrations.
What it keeps track of
Data model- Charges
- Service charges raised against an encounter for billing.
- Payments
- Confirmed payments received against a patient account.
- Encounters
- Scheduled and completed visits for a patient with the responsible clinician.
- Patients
- Patient and client records with consent status and assigned clinician.
Who uses it
Permissions- Billing Staff
- , Admin.
- Billing Staff
- Validates service billing and reconciles the patient scope; Admin configures the permitted projection and any external connection.
Set up Veterinary Practice Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.