OCR for KYC: building document verification that actually works
Manual KYC onboarding is slow, expensive and error-prone. Automating it with OCR sounds simple until you hit real documents: glare, skew, dozens of ID formats, and a compliance team that will not accept 85% accuracy. Here is what it actually takes to build document verification that holds up in production.
Everything below comes from building exactly that pipeline as KYC automation for a FinTech, on the document AI stack described here.
The real problem is not “reading text”
Off-the-shelf OCR reads characters. KYC needs something harder: find the right document, locate the right fields, extract them accurately, and know when it is unsure. That is a pipeline, not a single API call.
A production pipeline we built for a money-transfer platform had four stages:
- Document detection and classification. Before extracting anything, you have to know what you are looking at. We trained a lightweight YOLOv8 classifier across multiple identity-document types, optimized for low-compute and edge deployment (70% less compute than standard solutions).
- Field and layout extraction. With the document type known, PaddleOCR extracts the specific fields that matter, using layout rather than blind full-page OCR.
- Face match. Pairing OCR with facial recognition (DeepFace) verifies the person matches the document.
- Confidence scoring. Every field carries a confidence score, so low-confidence extractions route to a human instead of silently passing.
The result: 98% field-detection accuracy across document types, and roughly EUR 40,000 per year in operating cost removed by automating onboarding that used to be manual.
Lessons that matter in production
- Curate your own dataset. We labeled 5,000+ real documents for the specific types the client processed. Generic models plateau; a targeted dataset is what gets you from 85% to 98%.
- Design for low compute. A lighter model (YOLOv8n) that runs at the edge often beats a heavier one that needs a GPU cluster, especially when data cannot leave the environment for privacy reasons.
- Never auto-pass low confidence. The point of confidence scoring is to catch the 2% that need a human, which is exactly the 2% that would otherwise become a compliance incident.
The takeaway
KYC OCR is not a model, it is a pipeline: detect, classify, extract, verify, score. Build it that way, curate real data, and keep a human on the uncertain cases, and you get automation your compliance team will actually sign off on.
Tools referenced
EpochC builds KYC automation and OCR / document AI pipelines that ship to production. See the KYC case study — €40,000 a year removed at 98% field accuracy — or the intelligent document processing guide.
Related: intelligent document automation · custom KYC vs Sumsub and Onfido · intelligent document processing explained · document workflow automation costs · Google Document AI vs a custom pipeline · text classification for document AI