Document extraction is not the same as accepted data
Read the guide →Guide preview
Separate reading a document from accepting its fields into a working system.
Choose a method
Match the method to the input.
Distinguish the document, the fields and the work that an existing tool can already do.
Distinguish the document, the fields and the work that an existing tool can already do.
5 practical guides
Choose the question closest to yours.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Choose a parsing method from the documents you receive
Read the guide →Guide preview
Choose from a representative sample—not from an accuracy slogan or one tidy PDF.
Template or AI parsing: compare the maintenance and review burden
Read the guide →Guide preview
Changing the extraction method moves work; it does not remove the need to define correct output.
When an existing Power Query PDF import may be enough
Read the guide →Guide preview
For occasional supported PDF-table work, test the tool you already have before adding a subscription.
Check the input before blaming the parser
Read the guide →Guide preview
Input quality, document meaning and extraction rules can fail independently.
Choose what must survive extraction.
Start with one representative document and write the fields you actually need. A text PDF, a scan and an email body are not interchangeable inputs. Check the supported route before comparing subscriptions.
If an existing import produces an adequate, reviewable table for occasional work, keep it. Move to a dedicated parser only when repeated input or a necessary handoff creates a requirement it can address.
Start with the method decision →