01
Payer and student
each obligation keeps its context
Collections and reconciliation for private education
Recover tuition and reconcile payments without replacing your academic software
Certeza organizes receivables by payer, student, charge, and invoice; coordinates authorized reminders; and gives your team a clear view of promises, payments, and exceptions.
Your academic system and payment gateway keep running. Certeza adds a specialized collections and reconciliation layer without holding funds or managing grades, enrollment, or attendance.
- collections and reconciliation
- One workflow
- coordinated channels
- 4+
- of academic software
- No replacement
Certeza key points
02
Enrollment, tuition, services
charges and periods remain separate
03
Promises and partial payments
visible follow-up for finance teams
04
Payments and exceptions
ambiguous cases go to review
Education receivables
School collections need context, control, and respectful communication
Certeza turns scattered balances into a traceable operation without trying to become another academic system.
01
01
Receivables by payer and student
Relate an adult payer to one or more students, charges, periods, due dates, and invoices so every contact has the right context.
02
02
Preventive and overdue collections
Configure pre-due reminders and overdue sequences based on aging, balance, response, and rules approved by the institution.
03
03
Coordinated multichannel outreach
WhatsApp, SMS, email, calls, and internal tasks form one sequence instead of isolated messages lost between administration and finance.
04
04
Promises, agreements, and partial payments
Record promised dates, partial payments, agreements, notes, and next steps so the team knows what was kept and what needs attention.
05
05
Reconciliation with exception review
Match references, invoices, amounts, and receipts when the data supports a reliable result; ambiguous cases remain in a review queue.
06
06
Minimal data and auditable management
Collections target the adult payer, minimize student data, and preserve rules, templates, activity, and permissions for internal review.
How it works
From current receivables to measurable follow-up
Implementation starts with a controlled sample and keeps the academic or accounting system as the primary source.
- 01
Connect the available information
Start with an export, Excel, CSV, or an assessed API containing payers, students, charges, invoices, due dates, balances, and payments.
- 02
Validate relationships and exceptions
Test families with multiple students, payments covering several charges, partial payments, duplicates, reversals, and missing references.
- 03
Approve rules and messages
The institution defines segments, authorized channels, timing, frequency, tone, templates, exclusions, and cases that need its team.
- 04
Run coordinated collections
Certeza activates reminders and follow-up, records responses and promises, and stops the flow when payment is confirmed.
- 05
Reconcile and measure
The team reviews applied payments, exceptions, promises, contacted accounts, and period results without scattered manual reports.
Your current operation
Certeza adapts to the data your institution already has
We do not advertise native integrations before validating them. A pilot can start with files and move to an API when the system, subscription, and permissions allow it.
1Excel and CSV
2Academic or accounting software
3The institution's bank or gateway
4WhatsApp, SMS, email, and calls
Operational outcome
A verifiable history for every obligation, contact, and payment
The pilot aims to reduce manual follow-up and unidentified payments without inventing recovery rates or disrupting academic operations.
Less scattered information. More clarity for finance, leadership, and collections.
- Receivables segmented by payer, student, charge, and due date.
- Promises, partial payments, responses, and next steps stay visible.
- Reliable payments are applied and ambiguous cases are isolated for review.
- Contact rules and traceability remain under the institution's control.
Questions from schools and kindergartens
What must be clear before starting a pilot
A specialized finance layer for institutions that want better collections without replacing academic operations.
Private education
01What is Certeza for a school or kindergarten?
Certeza is a platform and specialized operation for preventive collections, overdue follow-up, and payment reconciliation. It works on top of the information the institution already manages and makes obligations, contacts, responses, promises, payments, and exceptions visible. It is not grading, attendance, academic enrollment, or e-invoicing software; nor is it a payment gateway, financial institution, or legal collection firm.
02Do we need to replace our academic software?
No. The academic or accounting system remains the primary source. A pilot can begin with an Excel or CSV export and an agreed update cycle. If a suitable API exists, scope, permissions, fields, and security are assessed before a connection is promised. Certeza uses only the data needed to manage receivables and return results to the operation.
03How are payers, students, and charges related?
The model preserves the relationship between the adult payer, one or more students, and each obligation. Enrollment, tuition, transportation, meals, and other charges remain separate by period, due date, balance, and invoice. Implementation tests families with multiple students, partial payments, and payments covering several obligations before automating the workflow.
04Does Certeza receive or process the money?
The institution's financial provider or payment gateway processes the funds. Certeza can facilitate access to the existing payment link and relate references, invoices, amounts, movements, or receipts when the data source allows it. Certeza does not hold or disburse funds. An uncertain match is never applied automatically; it goes to the team's review queue.
05Does Certeza contact students?
No. Outreach targets the authorized adult payer through channels approved by the institution. Implementation minimizes student data, avoids disclosing debt to minors or third parties, and configures timing, frequency, exclusions, and do-not-contact requests. The institution remains responsible for documenting authorizations and defining the rules that apply to its community.
06How does a pilot start and how is pricing set?
We start with a process assessment, a data sample, and a controlled segment. Relationships, rules, templates, payment sources, and success criteria are validated before outreach begins. Pricing follows the number of payers, obligation volume, channels, frequency, integrations, and support required; we do not publish a generic fee that hides meaningful operational differences.
Education receivables assessment
Let's review how your institution collects and reconciles today
Tell us your community size, current system, and where manual work concentrates. We will respond with concrete questions to assess a pilot.