Skip to content
TechFabric
AutoFabric

Automate the deal without losing the audit trail

The vehicle finance lifecycle, run by agents that have to ask permission and leave a record.

A vehicle loan is a long process with a regulator waiting at the end of it, and it does not finish when the deal funds. AutoFabric runs the stages that eat the calendar across the whole lifecycle, from origination and refinance through repossession, remarketing, transport and claims.

Agents do the work and an Open Policy Agent policy engine decides what each one is allowed to do, with TILA, ECOA and FCRA checked on every action instead of sampled in a quarterly review.

It reaches into DealerTrack, RouteOne, CDK and the credit bureaus because that is where the deals already are, not because integration counts look good on a slide. Every decision keeps its lineage, so when an examiner asks in month nine why a deal went the way it did, the answer is a record rather than a reconstruction.

Built for auto lenders, dealer groups, credit unions and captive finance companies.

The work got automated. The evidence did not.

Vehicle finance has been automating for twenty years and most lenders have the screens to prove it. What tends to be missing is the part a regulator asks about, and it shows up in three ways.

The deal waits on a document

Proof of income, proof of insurance, a signature on the right page. Somebody chases each one by phone and email while the file sits at ninety percent for four days, and the applicant takes an approval somewhere else in the meantime.

Compliance is a sample, taken afterwards

Disclosure accuracy and adverse action timing get reviewed quarterly, on a slice of files. A control that runs after the fact is a report, and a report cannot stop the deal it is describing.

The decision cannot be reproduced

An examiner asks why an application was declined in March. The answer gets assembled from a CRM note, a bureau pull nobody kept, and a loan officer who has since left.

One cause sits underneath all three. The process runs across DealerTrack, RouteOne, CDK and a spreadsheet, none of which shares a record with the others, so the control and the evidence both get added at the end instead of produced along the way.

The shift

Three ways to run a loan file

The outcome is the same funded deal. What differs is what you can prove about it nine months later.

Loan officers and a queue

Defensible, and capped by headcount

Application
Officer picks it up
Manual pulls and calls
Stipulations chased
Funded, eventually

Scripts driving the same screens

Faster, until a screen changes

Application
Bot fills the forms
Exception falls out
Person picks up the exception
Funded, with a gap in the record

Governed agents on one record

Fast, and the evidence is a by-product

Application
Agent works the file
Policy allows or refuses each step
Person decides what policy reserves for a person
Funded, with the trail attached

What gets installed

Six parts, running in your own Databricks workspace. Lenders usually start with one stage of the lifecycle instead of all six, and origination is the common first one.

An agent for each stage of the lifecycle

Origination, refinance, repossession, remarketing, transport and claims are separate agents with separate scopes. Not one assistant asked to understand the whole business.

A policy engine that can say no

Open Policy Agent decides what an agent may do before it does it. Changing a rule is a policy edit, and a refusal is recorded the same way an approval is.

Regulation checked on every action

TILA, ECOA and FCRA run against each step as it happens. That is what turns a quarterly sample into a control, because a check that runs before an action can stop it.

The systems the deals already live in

DealerTrack, RouteOne, CDK and DealerSocket over the Model Context Protocol, so an agent reads and writes where the deal already is instead of where a migration would like it to be.

Bureau, valuation and auction data

Experian, TransUnion and Equifax for credit, NADA Guides and Black Book for value, Manheim and ADESA for disposition. What a decision needs, pulled at the moment the decision is made.

Decision lineage, because the runtime keeps it

What an agent was asked, what it read, which policy allowed it and who approved it are recorded by Temporal as the work runs. In month nine, answering an examiner is a query somebody runs in an afternoon.

For lending operations

Give the file to an agent, keep the decision with a person.

The goal was never an unattended loan factory. It is that the work nobody should be doing by hand stops being done by hand, and that the judgement calls reach a person already assembled, with the rule that applies and the evidence behind it attached.

  1. 01

    Take the application

    Credit pulled, VIN decoded and the vehicle valued as the application arrives, so the file is already complete when somebody opens it.

  2. 02

    Work the stipulations

    Documents requested, received, read and matched against what the lender actually asked for. The applicant hears from the process on the day and not the following week.

  3. 03

    Structure and submit

    Deal structures built against live lender programs and submitted through DealerTrack or RouteOne, with the disclosure checks already run against them.

  4. 04

    Hand over the decision

    Where policy reserves a call for a person, the file arrives carrying the reason, the rule and the record, so the call takes minutes.

What is in it

  • Origination agent
  • Refinance agent
  • Repossession agent
  • Remarketing and auction agent
  • Transport and relocation agent
  • Claims and insurance agent
  • Policy governance on Open Policy Agent
  • Compliance engine for TILA, ECOA and FCRA
  • Credit bureau, VIN decode and valuation integration
  • Decision lineage

What changes for the team

The file moves while the judgement stays put.

Days come out of the cycle

The time a file spends waiting on a document is the time an applicant spends shopping the rate somewhere else.

Controls that run before the fact

A check able to refuse an action is worth more than a report describing one after it funded.

An answer ready for the examiner

Lineage is produced by running the process, so a request for a file from last March is a query and not a project.