AMORTANCE — WHAT AN EXPORT HAS TO CONTAIN
Template · synthetic values · one plan shown

WHY THIS FILE
The review replays your plans against the rules your own
contracts state and compares the result with what your own system
produced. To do that it needs four things per plan: the terms, the
payments actually collected, every change after signing with the
date it takes effect, and the figures your system shows for what
is being checked. Nothing beyond that.
The same thing as rows is in sample-export.csv, beside this file.

REQUIRED
- Terms: amount financed, annual rate, day count, and the
  installment dates and amount as originally scheduled.
- Payments: one row per payment collected, with its date and
  amount. Reversals and partial payments as their own rows.
- Events: one row per change after signing — an adjudication above
  or below estimate, added treatment, a canceled procedure, a
  discount or write-off — with the amount and the date it takes
  effect under the plan agreement.
- Your own results for the figures under review: how each
  collected payment was split between interest and principal, the
  balance the plan shows today, and any repriced installment,
  credit or refund your system quoted — each with the date it was
  computed. Without them a comparison has one side only. They are
  the "result" rows in sample-export.csv.
- A plan identifier that is yours. Anything stable will do.

THE TWO DATES
Every event has the date it takes effect under the agreement and
the date it reached your system. The gap between those two is the
whole question, so both belong in the export. In the event row
of sample-export.csv beside this file, the insurer's decision
takes effect on 2026-03-01 and arrives on 2026-04-23; everything
the review has to say about that plan follows from those seven
weeks.

IF YOU DO NOT STORE THE SECOND DATE
Common, and not a reason to stop. Send what you have and say which
date it is. A created-at or posted-at timestamp usually stands in
for the date received. For the effective date, the clause the plan
agreement points to is enough, even if the system never recorded
it. Where neither exists, the review states the assumption it made
rather than burying it in a number.

USEFUL IF YOU HAVE IT, NOT REQUIRED
- Procedure codes and fees behind the financed amount.
- The estimate the plan was originally written against.
- A statement or ledger entry a patient actually questioned.

NEVER NEEDED
Patient names, contact details, dates of birth, clinical notes,
card or account numbers. Amounts, dates and codes carry the whole
calculation. Anonymized identifiers are preferred, and whatever
you do send is deleted once the review is delivered.

FORMAT
CSV, JSON or a database dump — whatever your system already
emits. The columns in sample-export.csv are one shape that works,
not a requirement. Twenty to fifty plans is the review; one plan
is enough to answer whether any of this applies to you.