> 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/cut-off-dates.md).

# Cut-off Dates

The table below illustrates the timeline for transactions that occurred in January depending on Payment Channel's settlement period:

| Payment channel's settlement period | Cut-off date for submitting invoice | Payment sent by Coda to Partner |
| ----------------------------------- | ----------------------------------- | ------------------------------- |
| 30 days                             | 24th February                       | End of February                 |
| 60 days                             | 24th March                          | End of March                    |
| 90 days                             | 24th April                          | End of April                    |

Invoices received after the 25th of each month will be included in the subsequent month's payment schedule.


---

# 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/cut-off-dates.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.