Available now · paid calculation review
Check 20–50 patient payment plans against their contracts.
Launch terms
$1,500
Fixed, for the first three platforms
Bring disputed plans or recurring manual corrections.
See where your figures follow the contract and what needs correcting.
Scope
One contract type, usually your platform's default terms, and an agreed
set of changes to check.
Your input
One export: orders, terms, payments, changes and current results, with
non-identifying plan IDs. No integration work.
Delivery
10 business days from the agreed start date, once the export and
contract rules are complete.
Launch terms. In return for this rate, I ask for a 30-minute feedback call
after delivery to shape the engine. Later reviews are quoted per scope.
We confirm your fee and start date in writing before you book.
A report your team can act on
- Compare: exported and recalculated balances, schedules, interest,
fees and refunds for every plan, within the agreed scope.
- Explain: the event, input or contract rule behind each difference.
- Act: confirmed matches, corrections to make and unresolved rules or missing data.
Use the findings to fix your current engine and add test cases.
The review stands on its own.
Reviewed by Evgenii Agafonov,
founder of Amortance. I have worked in consumer lending since 2022 as a developer
and tech lead, on loan origination pipelines and microloans. I build Amortance
and carry out the reviews; you work directly with me.
Email your platform and one difficult case.
I will reply with a scope, data checklist, fixed fee and start date.
Sample report · the same refund dispute
Correction: apply the contract's effective date.
Finding: the export refunds $533.31;
the selected contract requires $636.23.
Difference: $102.92.
Cause: interest on the cancelled procedure remains in past periods.
Action: apply the cancellation from the plan's start, as this contract
requires, and replay the plan.
If a contract leaves the effective date unspecified, the report
records an open question pending agreement.
Check this example →
The downloads cover this same plan: three checks, one per event — April, May, October. In each row, exported_amount is your system's figure after the event, recomputed_amount the same figure under the contract, difference the gap between them. Two checks match; the third is this refund. The "before" payment from the first block is not there: the review checks the result of an event, not the change itself.