---
title: "Should OCR come before DeepSeek when extracting rows from scanned invoices?"  
description: "Should OCR come before DeepSeek when extracting rows from scanned invoices?"  
author: "Ida Holm"  
published: 2026-10-21  
updated: 2026-10-21  
canonical: https://www.mindstick.com/forum/162597/should-ocr-come-before-deepseek-when-extracting-rows-from-scanned-invoices  
category: "Document Extraction"  
tags: ["DeepSeek", "OCR", "Document processing"]  
reading_time: 1 minute  

---

# Should OCR come before DeepSeek when extracting rows from scanned invoices?

I’m putting together a workflow to extract line items from scanned invoices: product descriptions, quantities, and totals. Some scans are clean, while others have skewed pages or faint text. I’m unsure whether to send the document straight to a DeepSeek model or run OCR first and pass along the recognized text.

For anyone who has tested invoice extraction, did separating OCR from the language model make the results easier to check? I’d also be interested in how you preserve row boundaries so the model doesn’t accidentally combine neighboring items.


---

Original Source: https://www.mindstick.com/forum/162597/should-ocr-come-before-deepseek-when-extracting-rows-from-scanned-invoices

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.