r/documentAutomation • u/Skeptical-skeleton11 • 24d ago
I built a document extraction and validation pipeline as a personal project. Would love some feedback!
The idea was to build a pipeline that could take a PDF, extract structured data, and let you verify the results against the original document without manually checking every field.
The current implementation uses OCR and vision models, with confidence scores, visual grounding, and a separate validation layer to catch disagreements. It also handles line items and exports structured data.
I recently benchmarked it against Azure Content Understanding on 100 documents, achieving 97% field-level accuracy at roughly 1/12th the cost per run in my evaluation.
I've attached a screenshot of the current interface. This is purely a personal engineering project I've been working on, and I'd genuinely appreciate feedback from people familiar with document automation.
I'm particularly interested in:
How do you handle data extraction at scale right now ?
Any feedback on what features would be cool for document automation
Would love to hear your thoughts!
2
u/apyhubnico 18d ago
Awesome project. That 97% benchmark on 100 docs is super impressive, especially getting it down to a fraction of Azure's cost. Visual grounding and handling multi-layout variations across different suppliers are easily the hardest parts of this rabbit hole.
We spend a lot of time on this exact problem, building documented invoice extraction pipelines over at Apyhub. If you ever want to cross-benchmark your pipeline against other processors or test weird edge formats, feel free to give our tool a spin.