Turn messy school payment exports into accountant-ready CSVs.
BursarBridge helps private-school and microschool finance admins convert tuition, fee, and payment exports into QuickBooks/Xero-ready files with exceptions explained before month-end close.
Export preflight
17 rows will fail import
Tuition export
Payment method and fee category aligned
Family payments
Duplicate payer names across siblings
Refunds
Missing account mapping for credit rows
QuickBooks CSV
Clean rows exported with memo fields
Who this is for
The school office manager who becomes the human adapter between tuition payments and accounting.
You work at a small private school, microschool, after-school program, or independent K-12 operation. Tuition, deposits, fees, refunds, discounts, and payment-plan records come out of one system, but the accountant expects another shape.
The day-in-the-life pain is specific: a payment export looks fine until QuickBooks rejects rows, a column changed after an app update, siblings share payer names, refunds need special accounts, and the month-end question becomes “who understands this spreadsheet?”
Narrow buyer
Bursars, school business managers, and finance admins at small schools that cannot justify a full finance-system migration.
Paid problem
Manual re-keying and broken accounting imports slow close, introduce errors, and make payment reporting depend on one person.
Validation offer
Join the waitlist for a redacted 48-hour export preflight: cleaned CSV, exception list, and mapping memo.
Product workflow
A file-based control layer before an integration project.
The first version does not replace the school payment system or accounting software. It makes the handoff safer, documented, and repeatable using the files the bursar already exports.
Input
Upload a redacted tuition, fee, or payment export plus the QuickBooks, Xero, or accountant CSV template you need to produce.
Checks
BursarBridge maps columns, finds missing student IDs, duplicate payer names, odd dates, split fees, stale categories, and rows likely to fail import.
Output
You receive an accounting-ready CSV, exception list, mapping memo, reconciliation note, and repeatable rules for the next fee batch.
Features tied to the evidence
QuickBooks/Xero export preflight
Turn ad-hoc school-payment exports into stable import files without asking the school to replace its payment portal or SIS.
Exception list before close
See which rows need a human: missing family names, duplicate students, unknown fee codes, refunds, split payments, and date mismatches.
Mapping memory
Keep a versioned record of how export columns become accounts, classes, payment methods, fee categories, and memo fields.
Accountant-ready reconciliation note
Give the bookkeeper or accountant a short explanation of totals, skipped rows, transformations, and open questions.
Concierge-first privacy workflow
Early users can mask names and upload samples for a 48-hour review before any persistent sync or integration is promised.
Public evidence
The test is small: will bursars ask for a redacted export preflight?
GitHub · school bursar exports
A school-payment issue says bursars need stable QuickBooks/Xero/CSV exports because ad-hoc columns break pipelines, causing manual re-keying and failed downstream imports.
GitHub · school fee management
A school backend issue names missing structured fee billing, payment tracking, and financial reporting as a gap beyond basic transaction records.
GitHub · financial ecosystem
A related school operations issue asks for payment processing, invoicing, financial reporting, and integration with school operations instead of isolated transaction models.
These sources do not prove demand. They justify one focused validation page for a narrow buyer, with a concrete artifact: a payment export that must become an accounting import without manual re-keying.
Objections
Not a new school ERP. A safer accounting handoff.
Why not use the school system export?
That is the source of the pain. The export may exist, but if columns change or accounting fields are missing, the bursar still becomes the human adapter.
Why not buy a full school ERP?
Small schools often need a clean accounting handoff now, not a multi-month migration across admissions, SIS, billing, and reporting.
What about student privacy?
The first offer is redacted and file-based. Names can be masked, sample rows can be limited, and the output focuses on mapping and exceptions.
Will schools pay for this?
The landing page tests that exact question: will bursars share a redacted export and ask for a repeatable preflight packet?
Early waitlist offer
Get one redacted payment export turned into an accountant-ready packet.
Early users get a concierge review and a short interview. Demand is validated if school finance admins join, share a redacted export, and ask for the same preflight before the next close.