01
Patient and invoice
minimal financial context
Collections for private clinics
Manage patient balances without touching the medical record
Certeza organizes invoice, balance, authorized contact, and payment; coordinates respectful reminders; and keeps promises, payments, and disputes visible to administration.
Your medical system keeps scheduling and clinical records. Your bank or gateway processes funds. Certeza uses only minimal financial data and does not manage claim denials, medical billing records, or insurer receivables.
- no diagnosis or treatment
- Minimal data
- coordinated channels
- 4+
- of medical software
- No replacement
Certeza key points
02
Balance and due date
clearly bounded follow-up
03
Promises and payments
history for administration
04
Disputes and exceptions
cases outside automation
Direct patient receivables
Respectful financial follow-up without turning clinical data into collection data
This vertical is designed for balances paid directly by patients, not institutional receivables from insurers or health-system payers.
01
01
Receivables by invoice and payer
Relate internal identifier, invoice, generic financial charge, due date, balance, and authorized contact without importing diagnosis or treatment.
02
02
Preventive and overdue reminders
Configure follow-up by due date, balance, response, and clinic-approved rules using clear and respectful language.
03
03
Coordinated multichannel outreach
WhatsApp, SMS, email, calls, and tasks follow authorized channels, timing, frequency, privacy, and do-not-contact requests.
04
04
Promises and partial payments
Record promised date, amount, partial payments, and next steps without inferring medical conditions or offering unapproved terms.
05
05
Reconciliation with human review
Match reference, invoice, amount, and date. Ambiguous, duplicate, or reversed payments remain in review before receivables update.
06
06
Disputes and privacy by design
A payment or dispute stops the related flow; roles, minimization, traceability, and retention protect the financial information used.
How it works
From direct balances to applied payments or visible exceptions
The pilot starts with a financial sample that excludes medical history, diagnosis, test results, and clinical notes.
- 01
Define a strict data allowlist
Use only internal identifier, invoice, balance, due date, authorized contact, reference, payment, and dispute status needed by the workflow.
- 02
Test payments and edge cases
Validate partial payments, multiple invoices, authorized payers, duplicates, reversals, disputes, and do-not-contact requests.
- 03
Approve messages and privacy controls
The clinic defines tone, channels, timing, frequency, prohibited fields, access, retention, exclusions, and human escalation.
- 04
Certeza coordinates follow-up
The platform runs reminders, records responses and promises, and stops outreach after payment, dispute, or an authorized instruction.
- 05
Reconcile and measure
Reliable payments follow the agreed process; ambiguous cases remain in review and the clinic keeps its system as the primary source.
On top of your current operation
Connect only the financial information the workflow needs
A pilot can start with a controlled file. Any API is assessed for scope, permissions, and its ability to exclude clinical information.
1Allowlisted Excel or CSV
2Medical, accounting, or billing software
3Bank, gateway, and references
4WhatsApp, SMS, email, and calls
Operational outcome
More clarity on balances and payments with less data exposure
We measure manual work, unapplied payments, promises, and correct stops; we do not promise recovery or institutional insurer collections.
The clinic protects care; Certeza organizes financial follow-up.
- Balances prioritized by invoice, due date, and approved rules.
- Promises, partial payments, responses, and next steps remain visible.
- Reliable payments are reconciled and exceptions isolated.
- No diagnosis, medical record, or clinical billing detail in the flow.
Questions from clinics
What must be clear before starting a pilot
Financial collections and reconciliation for private clinics without turning Certeza into medical software or insurer revenue-cycle tooling.
Direct patient receivables
01Which receivables can Certeza manage?
Direct balances paid by patients or authorized payers to private clinics, medical centers, dental practices, labs, or aesthetic medicine. The first stage excludes institutional insurer and public-payer receivables.
02Does Certeza receive medical records or diagnoses?
No. The flow excludes medical history, diagnosis, treatment, test results, images, and clinical notes. Collection only needs an internal identifier, invoice, balance, due date, authorized contact, payment, and dispute status.
03Does it replace medical software?
No. Medical software keeps scheduling, care, clinical records, and official billing. Certeza receives minimal financial information and returns contacts, promises, payments, or exceptions.
04Does Certeza receive or process money?
No. The clinic's bank or gateway processes funds. Certeza can expose the existing payment link and match references to invoices; uncertain matches remain in review.
05Does it manage insurer denials or institutional claims?
Not in this vertical. Those workflows require submission, audit, denial management, medical billing records, and institutional payment reconciliation. We do not mix them with direct patient balance reminders.
06How does a privacy-first pilot start?
We review the process without patient data, define the allowlist, roles, retention, and messages, and then test a limited sample. The clinic validates authorization, exclusions, and criteria before outreach.
Assessment for private clinics
Let's review direct receivables without requesting clinical information
Tell us monthly volume, current software, and payment sources. Do not include names, diagnoses, or patient information.