Holofin
Category
Fintech
Automation
Use cases
KYC
KYB
Workflow automation
Document processing infrastructure for regulated backoffices. Classifies, splits and extracts the hardest financial documents, every value traced to its source.
Holofin is intelligent document processing for regulated backoffices. It classifies, splits and extracts the hardest financial documents, bank statements, tax filings, payslips, IDs, using vision models trained on layout rather than templates, so degraded scans and mixed uploads read the same as clean exports.
Reading a financial PDF is a specialist job, and it should stay one. Native or scanned, multi-column, tables that wrap across pages, a watermark printed over the holder's name: these are the documents that break general-purpose OCR. Holofin is built only for them. Forest is built for what happens to the answer: which case it lands in, who is allowed to act on it, and what a regulator sees a year later.
An extracted figure is worth nothing until someone is allowed to act on it. Holofin returns each value with its bounding box and the verdict of every validation rule. Forest gives that value a case, an owner, an approval limit and a log line, and applies the same limits whether the reviewer is a person or an AI agent. Neither side has to build the other's half badly.
A reviewer should open one page, not the whole file. When a statement fails to close, Holofin names the rule, the page and the amount. Forest routes on that failed rule instead of on a status, so the right person reads one line, and the correction they make is recorded against the figure. The trail runs from the pixel on the page to the decision, and it still holds when someone asks about it two years later.
Frequently asked questions
What does Holofin actually do, and is it just OCR?
OCR gives you text. Holofin gives you fields: it splits a mixed upload into its documents, extracts each value into your schema, checks it against your rules, and shows where on the page it came from. The last two are what OCR never does.
How do Holofin and Forest connect?
Holofin is one supplier inside a Forest workflow, alongside the identity and registry providers already in the stack. Forest hands Holofin the documents, Holofin returns validated data at record level, and Forest's inbox, gates and permissions take it from there.
Does Holofin need a template for each bank or document type?
No. Its models are trained on document layout, not on templates, so a new bank's format or a degraded scan reads without setup. New document types are added from a handful of validated examples.
What happens in Forest when a document fails a Holofin check?
Holofin names the rule, the page and the amount: for example, credits on page 12 miss the closing balance by 4.80 euros. Forest routes the case on that failed rule, so the reviewer opens one page instead of the whole file, and their correction is logged with who, when, before and after.
Can a reviewer in Forest see where a figure came from?
Yes. Every value Holofin returns carries its bounding box on the source page and its correction history, and both stay attached to the record in Forest, so an examiner can follow a figure from the pixel it was read from to the decision made on it.
Do you have more questions?
Book time with a Forest expert.