> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/billing/understand-your-billing-documents/invoice-fields-mapping.md). # Invoice fields mapping Your Marketplace invoice includes various details that are pulled from the platform and displayed on the invoice. This topic provides information on all such fields, helping you understand where the information comes from and how it corresponds to your invoice PDF. If you want to learn about the structure of your Marketplace invoices and statements, see the [Billing invoices](/modules-and-features/billing/understand-your-billing-documents.md#billing-invoices) and [Billing statements](/modules-and-features/billing/understand-your-billing-documents.md#billing-statements) sections, respectively. {% hint style="info" %} To see a larger version of the images on this page, select the image. To download a sample PDF, see [Billing invoices](/modules-and-features/billing/understand-your-billing-documents.md#billing-invoices). {% endhint %}

Invoice PDF Field	Invoice Location	Platform UI
PO No.	Invoice header	Mapped from the Additional Client ID in your agreement details.
External Document No.	Invoice header	Mapped from the agreement ID.
Your Reference	Invoice header	Mapped from the statement ID.
Agreement	Invoice line item details	Mapped from the agreement details page.
Product	Invoice line item details	Mapped from the agreement details page.
Licensee	Invoice line item details	Mapped from the agreement details page.
Subscription	Invoice line item details	Mapped from the subscription details page.
Client ID/Vendor ID	Invoice line item details	Mapped from the Details tab on the subscription details page.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.platform.softwareone.com/modules-and-features/billing/understand-your-billing-documents/invoice-fields-mapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.