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

WHY THIS FILE
The review replays your contracts against the terms your own
paper states and compares the result with what your own system
produced. To do that it needs four things per contract: the terms,
the payments actually collected, every change after the sale 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-dealer.csv, beside
this file.

REQUIRED
- Terms: amount financed, annual rate, day count, and the payment
  dates and amount as originally scheduled.
- Payments: one row per payment collected, with its date and
  amount. Reversals, partial payments and NSF as their own rows.
- Events: one row per change after the sale — a deferral, a
  canceled service contract or GAP policy, a total loss, a
  trade-in, a repossession — with the amount and the date it
  takes effect under the contract.
- Your own results for the figures under review: how each
  collected payment was split between interest and principal, the
  balance the contract shows today, and any payoff 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-dealer.csv.
- A contract identifier that is yours. Anything stable will do.

THE TWO DATES
Every event has the date it takes effect under the contract and
the date the money or the paperwork reached you. The gap between
those two is the whole question, so both belong in the export. In
the event rows of sample-export-dealer.csv beside this file, the
service contract is canceled on 2026-08-07 and the administrator's
check arrives on 2026-08-28; which of the two the refund is
credited as of decides the balance.

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 posted-at or check-received timestamp usually stands
in for the date received. For the effective date, the clause the
contract 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
- The itemized amount financed: cash price, fees, ancillary
  products, negative equity rolled in.
- The waiver or service contract terms the example turns on.
- A payoff quote or statement a customer actually questioned.

NEVER NEEDED
Borrower names, contact details, dates of birth, social security
or driver's license numbers, card or account numbers. Amounts,
dates and terms 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-dealer.csv are one shape that
works, not a requirement. Twenty to fifty contracts is the review;
one contract is enough to answer whether any of this applies to
you.