From lender request to the right document—faster, safer, and easier to track.
FundingDriver helps automotive finance teams interpret lender funding requests, locate the requested deal-jacket evidence, protect exceptions that require human judgment, and keep the workflow organized through funding.
Funding request detected
“Need proof of insurance and signed VSC.”
The engine is certified. The integration phase begins now.
Phase 5 completed simulator and installed-Windows certification. Phase 6 begins with authorized read-only/shadow connections first, human-authorized actions later, and bounded automation only after real-world evidence supports it.
Understand the request
Translate lender funding messages into clear document and action requirements.
Find the evidence
Identify the correct purchase-deal documents while excluding trade, internal, blank, unsafe, or unrelated pages.
Keep the deal moving
Track what was found, what needs Human Review, what was returned, and what happens next.
One funding request. One controlled workflow.
FundingDriver is designed to sit between the systems dealership finance teams already use—not replace them.
Detect
Observe an authorized lender funding-status or message event.
Understand
Separate routine document requests, monitor-only events, no-action states, and Human Review cases.
Retrieve & find
Retrieve the exact authorized deal jacket and identify only the pages that satisfy the request.
Review
If judgment is required, stop the governed action and make the reason visible.
Prepare, verify & monitor
Create an exact package revision; later authorized returns require independent receipt verification. Only explicit governed FUNDED closes monitoring.
Connect carefully. Read first. Write later.
FundingDriver is beginning authorization and capability discovery for the systems dealership funding teams already use.
RouteOne
Initial target: read-only funding status and lender request/message data. Later document return requires approved authorization and safe reconciliation.
CUDL / SmartFund
Initial target: read-only FUND DELAY, FUNDING, FUNDED and active-delay identity. Document return and delay-handled remain separately governed.
CDK
Initial target: exact store/deal deal-jacket retrieval with source revision and hash evidence. No fuzzy fallback to another deal.
Axcessa / CIT
Governed funding-note workflows where an approved interface exists. Any write begins as human-authorized and idempotent.
FundingDriver is independent. Third-party names are descriptive only; no affiliation or endorsement is implied unless separately announced.
Fail closed when identity, evidence, or destination is uncertain.
Current controls include MFA-capable authentication, role/store scoping, Argon2 password hashing, session revocation, AES-GCM protected security fields, Windows DPAPI master-key protection, immutable package revisions, hash-chained security events, and idempotent restart/reconciliation behavior.
Certified safety boundaries
- Human Review cannot be bypassed
- Trade/internal documents excluded from lender return
- Wrong store/deal/platform fails closed
- Partial packages never imply completion
- Only explicit FUNDED closes monitoring
Phase 6 security work
FundingDriver does not currently claim SOC 2 Type II, ISO 27001, or blanket GLBA compliance.
One funding standard across every rooftop.
Standardize common lender-request handling without removing Finance Manager accountability.
For leadership
- Consistent handling across stores
- Store-scoped access and evidence
- Standard Human Review reasons
- Visibility into found, missing, returned, and monitored work
- Comparable pilot metrics
For Finance Managers
- Less hunting through portals and deal jackets
- Clearer answer to what the lender needs
- Fewer duplicate or wrong-document submissions
- Defined handoff when judgment is required
- Less repetitive trailing-document follow-up
Prove it on real deals before you let it change anything.
FundingDriver observes authorized activity and records what it would do while the dealership team continues the real workflow normally.
Shadow mode can
- Observe authorized statuses and requests
- Interpret the request
- Retrieve authorized deal-jacket evidence
- Identify requested documents
- Flag Human Review
- Prepare a non-submitted package suggestion
- Measure accuracy and workflow agreement
Shadow mode cannot
- Upload documents to a lender
- Post a live CIT note
- Mark CUDL delay handled
- Change lender or DMS records
- Override Human Review
- Close a deal without governed FUNDED status
Evidence decides what gets promoted.
Questions teams ask first.
Are RouteOne, CUDL, CDK, or Axcessa integrations live today?
Not yet. Phase 6 begins with authorization and read-only/shadow integrations. An integration will be labeled live only after it is actually authorized and enabled.
When will FundingDriver use real customer data?
Only after authorization, credential, store/deal isolation, document-security, retention/deletion, and shadow-mode controls are in place. The first use should be a small read-only lab.
Does FundingDriver automatically upload documents?
Not in the current rollout. Shadow mode performs no production writes. Later capabilities may move to human-authorized return, then narrowly bounded automation after evidence and approval.
What happens when a request requires judgment?
FundingDriver routes it to Human Review. Recontracts, rate/buydown issues, identity corrections, mileage mismatches, notary problems, customer interviews, and other governed exceptions remain human.
Can FundingDriver send trade documents?
Trade/internal/accounting documents are hard-excluded from lender-return workflows in the certified safety model.
What closes the funding workflow?
Only an explicit governed lender FUNDED status. A successful document return does not equal funded.
Does FundingDriver replace existing dealership systems?
No. FundingDriver is designed as an orchestration layer around the systems dealerships already use.
Start the conversation.
We are beginning controlled integration and shadow-pilot conversations with dealerships, dealer groups, and technology partners.
Do not include SSNs, driver-license numbers, deal jackets, credit applications, bank statements, tax documents, or other customer/deal information.
Observe first. Compare. Then earn the right to act.
Our preferred first live-data deployment is a tightly controlled shadow pilot with production writes technically disabled.