The case for deterministic PDF filling

AI can read almost any document now. The harder question is what writes the answer back — and for anything an auditor might ever look at, that write step should not be a language model. A document workflow has two halves Most real document automation is a loop: read data out of one document, then write it into another. Read a scanned invoice, write the numbers into your ledger. Read an onboarding packet, write the values into a W-9. Read a claim, write an ACORD form. The read half is having its moment. Vision-language models are genuinely good at pulling structured data out of messy, never-before-seen documents, and a wave of strong APIs — Extend, Reducto, LlamaParse, the hyperscalers’ document-AI services — have made it a solved-enough problem. If you need to understand an arbitrary PDF, reach for one of those. The write half is a different problem with a different failure mode — and it’s the half people are quietly bolting an LLM onto because it’s adjacent.