> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/general-information/coda-portal/finance-guide/reconciliation-invoicing-and-settlement/preparing-a-partner-invoice-to-coda.md).

# Preparing a Partner Invoice to Coda

Here are some tips to ensure the invoice that you send to Coda is correct (in cases where the Partner is obligated to send an invoice to Coda):

* The invoice should be prepared only after the Partner has reviewed the Sales Report sent by Coda and has verified that the data is correct.
* The amount specified on the invoice shall be for the value of transactions processed during the Transaction Period, net of Coda’s fees. Taking Indonesia carrier billing as an example, if Rp. 1.000.000 was processed in a transaction month (exclusive of VAT) and Coda’s fee is 30%, so the amount that should be specified on the invoice is Rp. 700.000.
* The Partner can use any format for the invoice desired, so long as it includes the following information: (1) the payment channel(s) for which the invoice applies, (2) the Transaction Period, and (3) the net amount.
* A sample invoice can be found in [Appendix A](broken://pages/pWEQ0pDRKLBt9YIDEs3O).


---

# 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://docs.coda.co/general-information/coda-portal/finance-guide/reconciliation-invoicing-and-settlement/preparing-a-partner-invoice-to-coda.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.