Screen 8 of 14
The same payment, from both sides
On the left is the practice’s own ledger, the screen the front desk already looks at every day. On the right is everything NextRev did to put the new line on it.
Nothing on this page is real. No family exists, no money moved, and no ledger was written.
The practice’s own screen
In Ortho2
The Alvarez family’s ledger, drawn as plain text. This is the practice’s own software, and the front desk works in it exactly as it did before.
The Alvarez plan is a mock plan built for this walkthrough, so every figure in the ledger below is MODELLED.
Alvarez, Maria Responsible party for Sofia Alvarez, Horizon City Orthodontics
| Entry | Amount |
|---|---|
| 5 August 2026 Payment plan, Alvarez family 16 instalments, taken on the 5th of each month | $3,200.00 |
| October 5, 2026 Payment received just posted Written back by NextRev. Nobody at the desk retyped it. | $200.00 |
The instalment count moved by exactly one. It read 16 before the payment. It reads 15 now. The balance fell by one instalment, nothing else on the ledger changed, and nobody at the desk typed a figure.
Beside the instalment the family pays one more line, plus a $5.95 technology fee on each payment, paid to NextRev. It is not on this ledger, because the practice never sees it and never handles it.
Drawn, not a screenshot. Ortho2 is the practice’s existing software. It has no part in this walkthrough, and nothing here is said on its behalf.
The same few minutes, on our side
What NextRev did
Five steps, in order, while the front desk carried on with the next patient.
Read the plan out of Ortho2.
Sent the family the link to pay.
The charge was approved on TRX.
The receipt was written back into Ortho2.
The instalment closed.
The first step and the fourth step are the two ends of one job. The plan is read where the practice already keeps it, and the receipt is written back to the same place, so there is no second list to reconcile at the end of the day.
Steps one to three are shown from the inside on screen 6, the front desk and on screen 7, the family’s phone.
Staff never leave Ortho2.
The plan was made in Ortho2, the receipt landed in Ortho2, and the instalment closed in Ortho2. There is no second screen for the front desk to learn and no day-end list to type up.
Two of those five steps are proven in testing
Taking the payment and writing the receipt back into Ortho2 have both run, end to end, in our own testing. MEASURED
The receipt landed in the practice ledger and the instalment count moved by one, which is the same pair of things the left column shows.
Proven in testing means what it says: our own run, on a test database, with a test card, against a test gateway. No family has paid through it and no practice is running it yet. The rest of this walkthrough is a drawing of a finished product, and this screen is the one place where a claim is a measurement.
Why this matters
Without the writeback the payment still happens, and the practice’s own ledger never learns of it, so the family’s balance stays exactly where it was. Every month after that the ledger is wrong, and the family is asked again for money it has already paid.
That is why the fourth step above is the one we treat as the product, and why this screen exists at all.