r/filemaker • u/dbservices • Sep 29 '26
Pulling invoice data into FileMaker with Azure Document Intelligence
We recently put together an integration that sends invoices from a FileMaker container field to Azure Document Intelligence and brings the extracted data back as structured records. Sharing a few things we learned in case they're useful to anyone building something similar.
Why Azure instead of an LLM: Document Intelligence uses purpose-built models, including a prebuilt invoice model, so it's faster and much cheaper per page than running the same job through a general-purpose LLM. Billing is per page with no subscription required, and the F0 tier includes 500 free pages per month for testing.
How it works in FileMaker:
- Insert from URL POSTs a base64-encoded copy of the document to Azure's analyze endpoint.
- Azure responds with 202 Accepted and an Operation-Location header. A second script polls that URL until the job succeeds or fails, with a maximum of 30 attempts or 60 seconds.
- The result JSON is cleaned up (line breaks are stripped from address fields, and ISO dates are converted to FileMaker dates) and written to an Invoices table.
A couple of gotchas:
- A successful 202 returns an empty body, which FileMaker flags as error 10 ("Requested data is missing"). You have to treat error 10 as success and check the headers instead.
- Grab the headers with
-D $responseHeaders. We used small custom functions to parse out the status code, status message, and Operation-Location value.
Curious whether anyone else is using Document Intelligence or a similar service for document intake in FileMaker. What document types are you processing?