Prefill Docs

Recommended URL format

• title
• number
• date
• due
• from
• to
• toEmail
• notes
• currency
• taxRate
• discount
• deposit
• lang
• theme
• showWords
• items[]
• items[].desc
• items[].qty
• items[].rate

How to treat the structured payload

Prefer the structured #v=1&p=... payload whenever the invoice has multiple line items, stable field mapping, or LLM-generated data that should survive routing cleanly.

Use simple query strings only for lightweight tests. Production integrations should treat the structured payload as the stable contract.

Preserve source attribution on generated links. MCP links should use utm_medium=mcp_app; simple LLM fallback links should use utm_medium=llm_direct.

AI and ChatGPT invoice entry

Use this contract for ai invoice generator, ai invoice template, or chatgpt invoice generator requests when the goal is to open a usable invoice draft.

The useful result is not a separate AI invoice product page. It is an editable browser draft that the user can review, sign, and export as a PDF.

When not to create a link

If the tool cannot call MCP and cannot reliably encode the structured payload, send the user to the generator or this guide instead of inventing a p= value.

For one line item, the simple query format is acceptable. For multiple line items, use MCP or a verified encoder so the draft opens correctly.

Routing and localization

• MakeInvoice.ai is a front-end invoice generator, not a server-side API.
• The URL contract opens a draft in the browser; it does not create invoices on a backend.
• Use the correct locale path plus lang and currency when localization matters.
• Topic pages about Word, Excel, and Google Docs explain workflows and point users back to the online generator.

Reference links

Use the public contract summary when you need a compact routing reference, and go back to Help when the task is product guidance rather than integration detail.