> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/dashboards/payments-dashboard/invoices-flat-rate-rendering-type.md).

# Invoices (Flat-Rate rendering type)

Invoices with the service bundle activated.

{% hint style="info" %} <mark style="color:blue;">Path: Dashboard > Payments > Purchase</mark>
{% endhint %}

* [Definition](#id-1.14.x-invoices-servicesbundle-definition)
* [Create an invoice](#id-1.14.x-invoices-servicesbundle-createaninvoice)
* [Read an invoice](#id-1.14.x-invoices-servicesbundle-readaninvoice)
* [Update an invoice](#id-1.14.x-invoices-servicesbundle-updateaninvoice)
* [Delete an invoice](#id-1.14.x-invoices-servicesbundle-deleteaninvoice)
* [Related resources](#id-1.14.x-invoices-servicesbundle-relatedresources)

## Definition <a href="#id-1.14.x-invoices-servicesbundle-definition" id="id-1.14.x-invoices-servicesbundle-definition"></a>

Invoices are payment receipts delivered to detail and keep track of payments through the platform.

Platform fee invoices are automatically generated by the platform. Service invoices are not generated by the platform.

<mark style="color:red;background-color:yellow;">**WHO CAN USE THIS FEATURE?**</mark>

**Switch:** All logged-in users

**Non-Switch:** Logged-in askers

**Non-Switch:** Logged-in offerors

## Create an invoice <a href="#id-1.14.x-invoices-servicesbundle-createaninvoice" id="id-1.14.x-invoices-servicesbundle-createaninvoice"></a>

Invoices are automatically generated by the platform when a payment is done. Invoices to offerors are delivered when payouts are made, in other words, when the service has been provided and the payout is manually done by the platform administrator.

## Read an invoice <a href="#id-1.14.x-invoices-servicesbundle-readaninvoice" id="id-1.14.x-invoices-servicesbundle-readaninvoice"></a>

To access invoices, click the invoice icon (figure 1) in the payment section of the user dashboard. The invoice is displayed in a new tab.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/vQzBEv3KVrtFSJEoSVmh/6956092161" alt=""><figcaption><p>figure 1</p></figcaption></figure>

With the service bundle enabled, the invoice displays the service name and not the listing name.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/UituBuGJF4APcC5ngAOs/6956092158" alt=""><figcaption></figcaption></figure>

## Update an invoice <a href="#id-1.14.x-invoices-servicesbundle-updateaninvoice" id="id-1.14.x-invoices-servicesbundle-updateaninvoice"></a>

Invoices cannot be updated.

## Delete an invoice <a href="#id-1.14.x-invoices-servicesbundle-deleteaninvoice" id="id-1.14.x-invoices-servicesbundle-deleteaninvoice"></a>

Invoices cannot be deleted.

## Related resources <a href="#id-1.14.x-invoices-servicesbundle-relatedresources" id="id-1.14.x-invoices-servicesbundle-relatedresources"></a>

**Dashboard:**

* [Payments dashboard](https://features.scnd.com/v2.0/dashboards/payments-dashboard.md)

**Business rules:**

* [Invoice ID](#id-1.14.x-basicsolution-businessrules-invoiceid)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://features.scnd.com/v2.0/dashboards/payments-dashboard/invoices-flat-rate-rendering-type.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
