# Component: Partner Invoice Table

**Available from:** Release 112

The **Partner Invoices Table** component allows **partner users** to view invoices associated with their **partner organisation** in the Partner Portal. Partners can download a specific invoice as a PDF, giving them a single, self-service view of invoices they are eligible to access.

This component is designed for B2B SaaS businesses running a partner/reseller model and lives in the **Partner portal** section.

**Note:** This component is very similar to the existing [**Invoice Table**](https://docs.limio.com/components/~/revisions/g7aG4cxkhvGrL0S9BdOp/component-library/self-service-components/component-invoices-table) component, but it's designed for **partner users** and does **not** include the ability to **pay invoices** (download/view only).

{% embed url="<https://69c2cf3a42a094f3cd354b8d-kmqmmfobmx.chromatic.com/?path=/story/shop-components-partner-portal-partner-invoice-table--default&full=1&shortcuts=false&singleStory=true&embed=true>" %}

#### **Props**

| Prop name               | Type   |        Default | Behaviour    |
| ----------------------- | ------ | -------------: | ------------ |
| Invoice date header     | String | `Invoice date` | Column label |
| Due date header         | String |     `Due date` | Column label |
| Reference header        | String |    `Reference` | Column label |
| Price header            | String |        `Price` | Column label |
| Balance header          | String |      `Balance` | Column label |
| Download invoice header | String |       `Export` | Column label |


---

# Agent Instructions: 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:

```
GET https://docs.limio.com/components/component-library/partner-portal-components/component-partner-invoice-table.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.