This article is about a problem that looks solved until the moment it isn't.
Search "fill pdf form programmatically" and you'll find dozens of tutorials. PyPDF2. pdfrw. iTextSharp. PDFBox. They all get you to a filled PDF by the end of the article. None of them tell you what happens when you hit a PDF generated by a fund's legal document platform — or a custodian's proprietary forms engine — or a 12-year-old LaTeX template that a compliance officer refuses to update because it passed regulatory review in 2013.
We hit all three. This is the story of what broke, why it broke, and how we built a pipeline that doesn't break — along with a map of every place in that pipeline where an outside contributor could have meaningful impact right now.
What this article is: A technical deep-dive into programmatic PDF form filling, using PDFFillr's open-source pipeline as the primary reference. Every code sample is real, running in production, and drawn from our TypeScript SDK and core engine. GitHub repo and contribution guide are linked at the end.
The problem space: AIF subscription documents as the extreme case
