How we build and check documents
Every document on this site is built from a fixed template in our code — not generated on the fly. Here is how they are made and what we check before one goes live.
Last updated 2026-07-26
Documents are templates, not AI output
Each document has a definition in our codebase that decides exactly which fields exist and how the finished file is laid out. Nothing about your document's wording or structure is invented at the moment you use it. The same input always produces the same file.
What you see is what downloads
The live preview and the downloaded file are produced from the same document object by the same code. That is a deliberate design choice: it means the preview cannot drift away from the file you actually get. On top of that, an automated check downloads the real file and compares its text against what the preview shows, and our build fails if the two do not match.
Money is calculated in whole cents
Totals, tax and line amounts are computed using integer minor units (cents), not decimal floating point. This avoids the rounding drift that makes a total end in an unexpected cent. Rounding is half-up, the convention used on invoices, so a hand check matches the printed total.
Tax rates are yours, not ours
We do not ship a built-in sales tax rate. Sales tax varies by state and locality and changes over time, so you enter the rate and the label yourself, and we do the arithmetic. Confirm your current rate with your state or local tax authority.
What we deliberately do not do
We do not apply law to your facts. Our documents record what you tell us; they do not determine your rights, what you are owed, or whether something is lawful. Documents that would require that kind of judgment are not published on this site. Where a document touches an area where rules vary — final pay and unused leave, for example — it points you to your HR team and your state labor office instead of stating an answer.
Corrections
If you find something wrong in a document, tell us at contact@myformzip.com and we will look at it. Fixes ship as code changes, so a correction applies to everyone the next time they use the document.