Consumer Credit
Consumer Duty evidence, vintage performance and one agreed contribution number.
Lending businesses usually have the data and no way to stand behind it. Risk, finance and marketing each hold a version of the truth, the bureau data sits in exports, and Consumer Duty evidence gets assembled by hand as the deadline approaches. We give you one timeline per customer and the history to trend it.
The numbers that matter here
What we'd connect here
Whatever it is and however it exposes itself — API, database, nightly file, or a spreadsheet somebody maintains by hand. We only ever need read access, with personal data excluded.
What we do about it
Where it hurts
- Risk, finance and marketing each have their own version of the truth
- Consumer Duty evidence assembled by hand, close to the deadline
- Systems hold today's position and no history, so there is no trend to report
- Decisioning data locked inside bureau exports
What Acta builds
- Application-to-funded-to-collections single timeline per customer
- Consumer Duty outcome reporting, with a full audit trail behind every number
- History rebuilt so vintage cohorts and roll rates exist at all
- Affordability and arrears views the credit committee can act on
What you get
One number for net new contribution — agreed by risk, finance and growth.
Live in months rather than years, from £5k a month, on your own Google environment — handed over to you, or run by us.
Inside a consumer credit engagement
A lender usually arrives with the data spread across an origination platform, a decisioning engine fed by bureau data, a servicing system and a collections dialler, with marketing spend sitting in a fourth place again. Each team trusts its own extract, so the approval rate risk quotes, the funded volume finance books and the acquisition cost growth defends never quite reconcile — and the monthly contribution number is rebuilt by hand every board cycle from whichever version won the argument that month.
We land the events behind all of it — application, decision, funding, payment, contact, arrears status — in your own BigQuery, recorded once with the time each happened, and rebuild the loan-book position back as far as the data allows. That history is usually the unlock: vintage cohorts and roll rates that never existed become reportable, and the leaks show themselves. A typical one is a channel with a healthy approval rate and quietly worse vintage loss than the book average, which no departmental report was ever built to catch because origination and collections are measured by different people.
Once it is live the credit committee works from cohorts that are current rather than a month old, Consumer Duty outcome reporting regenerates itself with a full audit trail behind every figure, and risk, finance and growth argue about what to do rather than about whose number is right. The affordability and arrears views update on the same definitions the board pack uses, so the decision and the evidence for it come from one place.
Common questions
How do you produce Consumer Duty evidence from our data?
We land every event — application, decision, funding, contact, payment — in your own BigQuery as an immutable history, then build outcome reporting on top with a full audit trail behind each number. The evidence regenerates itself rather than being assembled by hand as the deadline approaches.
Can you rebuild vintage cohorts and roll rates if our system only holds today's position?
Yes. Most lending systems store the current balance and no history, so cohorts and roll rates do not exist to report. We reconstruct the position over time from the events, so vintage loss, roll rates and arrears trends become reportable — usually further back than you expect.
How much does it cost for a consumer credit lender, and how fast?
Solving one area — usually risk or collections reporting — is £60k a year, billed at £5k a month, in your own Google environment. You see a real number within the first week, and the reporting behind it lands over the following two to three months.
Which consumer credit systems do you connect to?
Whatever you already run — it makes no difference whether a system exposes an API, a database view, a nightly file or a spreadsheet somebody maintains by hand. In consumer credit that usually means: Loan management system; Decision engine; Bureau feeds (Experian, Equifax, TransUnion); Open banking provider; Direct debit and card payments; Collections dialler; In-house SQL Server. We only ever need read access with personal data excluded, and the layer is built in your own Google environment rather than ours.
Other sectors
Bring one decision your data should be helping you make.
30 minutes, no deck. We'll tell you on the call whether we're the right partner, and exactly what we'd ship in the first 30 days.