> 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/other-important-notes.md).

# Other Important Notes

<mark style="color:purple;">**Settlement currency:**</mark> Transactions are always processed in the country’s local currency (i.e. Indonesian Rupiah, Singapore Dollars, Malaysian Ringgit, Thai Baht, Philippine Peso, or New Taiwan Dollars). Payouts to partners are always made in USD at the exchange rate used by the bank (or non-bank payment service provider where applicable) when the exchange from local currency to USD is made, less the international transfer fee specified in the Partner’s agreement with Coda.

<mark style="color:purple;">**Deferment of payment:**</mark> To minimize the remittance fees that partners bear, if a payment is less than US$100, Coda will, *unless the partner instructs Coda otherwise in writing*, defer making it until the current month’s payment and deferred payments from prior months total US$100 or more.

<mark style="color:purple;">**Settlement bank account:**</mark> The payee bank account must be a corporate account in the name of the partner. Personal bank accounts will not be accepted.

<mark style="color:purple;">**Accessing transaction data:**</mark> Finance contacts at Partners can access transaction records in two ways:

* <mark style="color:purple;">**Automatically via Email/SFTP/Webhook:**</mark> Coda will send the sales report (daily/weekly/monthly) basis and deliver this to one of the options available now. For more detailed information, please refer to this [Transaction Report Delivery Option](broken://spaces/SEdQy23klcHCaJcfBCmP) document.<br>
* <mark style="color:purple;">**Manually (i.e. “self-serve”):**</mark> Transaction data can be manually generated by any user that has Finance access in the [Publisher Portal](https://portal.codapayments.com/) anytime by visiting the <mark style="color:purple;">**Transactions**</mark> tab.

  * The user can select the filters such as payment channels and date range as desired
  * Then press “Show results”
  * Finally, the user can click “Export CSV” or “Email CSV” to extract the transaction data in CSV format. For the Email CSV function, if you don’t receive the CSV within a few minutes, please check your spam/junk folder.
  * This process is illustrated below:

  <div data-full-width="true"><figure><img src="broken://files/QqoYIyj6kIBdQhfwbYUG" alt=""><figcaption></figcaption></figure></div>

<div data-full-width="true"><figure><img src="broken://files/1iuvf87pVMA7uTdZ3lOJ" alt=""><figcaption></figcaption></figure></div>


---

# 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/other-important-notes.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.