Searchable text, a spreadsheet and an API payload are different products. An archive needs readable text with page references. A finance workflow needs named fields, typed amounts, repeating rows and rules that stop a bad value before export. The destination tells you whether plain OCR is enough or whether you also need layout analysis and review.
Start with the file itself. A digital PDF may already contain reliable text even when copy and paste looks messy. An image-only PDF needs recognition, while a mixed packet may need a different path on each page. Running every file through visual OCR can replace clean embedded text with a less certain reading.
Keep the schema as small as the job allows. An invoice needs supplier, document, tax, line-item and total fields. A bank statement needs transaction rows and balance checks. Capturing every visible word creates more noise for the reviewer and the next system.