Nexus Finance — A Real CFO View, Not a Month-End Guess

The Problem

Revenue you can only see at month-end isn't revenue you can manage

A multi-center healthcare business — a pharmacy plus related clinical facilities, run as several "Nexus centres" — generates cash, card, and bank transfer revenue across departments and procedures every single day. Without a live rollup, the CFO's actual financial picture arrived weeks late, reconstructed from receipts and reconciliations, by which point a bad month was already locked in rather than something that could still be steered.

There was a second, quieter problem too: discounts. Front-desk staff need the ability to offer one, but not the unilateral authority to grant one — and without a system for that, "how much did we give away this month, and who approved it?" wasn't a question anyone could answer quickly.

What I Built

A live CFO dashboard, sitting on disciplined books

Nexus Finance is the billing and finance system for the practice — patient and procedure records, transaction entry, doctor management, and reporting — built as a separate companion system to Nexus Reporting (the clinical reporting app), the two talking to each other over a signed service-key API rather than sharing a database. Front-desk staff record transactions and request discounts; a CFO dashboard rolls everything up in real time — net revenue, payment-method split, top procedures by revenue, per-department breakdown — and a formal End-of-Day Closing process locks each day's books rather than leaving the ledger perpetually open.

Nexus Finance CFO dashboard — net revenue, transactions, collections by payment method, daily revenue trend, and per-department breakdown (figures blurred)

The CFO dashboard for one of the centres — figures blurred for confidentiality.

Technical Highlights

Separation between clinical and financial systems, on purpose

Two apps, one signed service API

Nexus Finance and Nexus Reporting are separate codebases and databases, integrated over a bearer-key-authenticated service API — clean separation between clinical and financial systems while patient and billing data still stay linked.

Discounts are governed, not just applied

A discount doesn't just get typed in — it's logged as a request and routed through a Discount Approvals queue, with the aggregate tracked as a percentage of gross directly on the CFO dashboard.

A real end-of-day close

End-of-Day Closing, a Closing History log, and Finalize Closings give the practice a disciplined books-close process — each day's numbers get locked, not left open to quiet edits later.

Multi-tenant by center from day one

Every domain table is scoped by center_id, the same tenancy model shared with Nexus Reporting — multiple physical centres run on one system without data ever crossing between them.

Revenue broken down the way a CFO thinks

Not just a single top-line figure — the dashboard splits revenue by payment method (cash/card/IBFT), by department, and by procedure, so where the money actually comes from is visible at a glance.

Framework-free, Hostinger-deployable

Plain PHP + MySQL, matching the constraints the rest of the practice's systems are built under — no daemons, no long-running processes, deployable on ordinary shared hosting.

Big discounts become a held bill, not a hard wall

A discount above 20% parks the bill for CFO approval. Nothing is charged and nothing enters the transactions table until it's approved and actually paid, so revenue and closing figures never carry a sale that didn't happen.

An AI-written monthly report for the CFO

On the 1st of every month, a cron job aggregates the previous month on the server into a de-identified payload (counts, sums and categories only, no patient details) and Claude turns it into a self-contained report with inline charts, saved as HTML and PDF.

Payouts computed from the books

Performing and ordering doctors are recorded per procedure line. Department share percentages, per-doctor exceptions, a lab revenue split and a flat per-scan CT technician fee produce month-end payout reports without a spreadsheet in sight.

Stack

Under the hood

Backend	Plain PHP API + MySQL, no framework
Integration	Signed service-key API shared with Nexus Reporting (Laravel)
Reporting	Live CFO dashboard — revenue, collections, discounts, per-department and per-procedure breakdowns
Frontend	React + Vite
AI	Claude for the monthly performance report, generated by cron or on demand
Hosting	Hostinger shared hosting

Status

Where it stands

In daily production use at Nexus Diagnostic Centre, and still actively extended: split payments, a laboratory module, held-bill approvals, doctor and technician payouts, a curated referrer list and AI-written monthly reports have all landed since the first release. Every schema change ships as a re-run-safe migration against the live database.

Nexus Finance — a real CFO view, not a month-end guess

Revenue you can only see at month-end isn't revenue you can manage

A live CFO dashboard, sitting on disciplined books

Separation between clinical and financial systems, on purpose

Under the hood

Where it stands

Need real-time financial visibility into your own practice?