Skip to content

INDUSTRY FIELD GUIDE

Dealer-arranged finance contract data for AI testing

A dealership worksheet may describe a proposed deal while a finance company’s acceptance refers to a later contract.

By Fiund · Updated 2026-11-05

NAICS 522220 · Sales Financing

A dealership worksheet may describe a proposed deal while a finance company’s acceptance refers to a later contract. CFPB’s auto finance pilot and consumer materials distinguish relevant parts of the dealer-arranged financing process. An evaluation can test document lineage using invented parties and amounts. CFPB auto finance data pilot · CFPB financing routes

Prepare a practice sale packet with a preliminary worksheet, a revised installment contract, and an acceptance record tied to the revised contract. Give a second case an acceptance notice from an earlier deal with a similar reference. Ask which contract can be matched and what evidence remains missing. Include a trade-in figure only as a document-matching field.

Leave real applications, signatures, lender buy rates, vehicle IDs, and credit decisions out of the sample. Clear dealership and finance-company rights separately before discussing production records.

Describe a sales financing dataset

Original Fiund exercise

Finance acceptance attaches to a contract revision, not a preliminary worksheet

A practice sale packet has invented deal aliases and arbitrary figures. It contains no signatures, credit applications, vehicle IDs or actual lender terms.

Fictional records supplied to the evaluator
RecordSourceWhat it records
DF1Worksheet W1Deal D-A, preliminary version: practice total 200 and trade-in field 20. Marked proposal only.
DF2Contract C2 and acceptance A2Revised D-A/C2: practice total 190, trade-in 25. A2 explicitly accepts D-A/C2, not W1.
DF3Second packetDeal D-B/C1 has an acceptance referring to older D-B0/C1. No D-B-to-D-B0 revision relationship supplied.

Question for the model

Which D-A document has a matched acceptance, and does the second packet establish acceptance for D-B/C1?

Show the reference answer and checks

DF2 explicitly matches A2 to D-A/C2. DF1's proposal has different figures and is not the accepted document named in A2. DF3's acceptance points to D-B0, while the packet asks about D-B; the similar contract suffix does not establish a revision relationship. Flag the second packet's deal-identity gap rather than transferring acceptance. The task identifies documentary links without assessing finance suitability or a consumer decision.

  • Summarizing accepted figures from the earlier proposal instead of the named contract.
  • Matching by a contract suffix while ignoring a conflicting deal reference.

Fields to preserve

Deal alias and document class
Separates proposals from contracts.
Contract revision and acceptance target
Establishes the exact match.
Practice figures and unresolved relationship
Exposes mismatched versions without guessing.

Test another case

Add an explicit D-B0-to-D-B conversion record that excludes acceptance carryover. Require the identity link to be recognized while acceptance remains unconfirmed.

Use independently written fictional packets. Exclude credit decisions, lender buy rates, applications, signatures and actual dealership records.

Download this fictional example and answer key (JSON)

Discuss a contribution

Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.

Primary sources and further reading