> 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/coda-portal/finance-guide/reconciliation-invoicing-and-settlement.md). # Reconciliation, Invoicing, and Settlement There are four steps in the payment cycle that finance teams should understand when working with Coda: (1) transactions are processed during a particular month (the “Transaction Period”), and then (2) a sales report is generated by Coda (the “Sales Report” or “S.R.”) and sent by email to the partner, and then (3) an invoice (“the Invoice” or “Inv.”) is sent from Coda to the Partner or from the Partner to Coda, depending on the payment channel (as illustrated below), and then (4) Coda makes payment to the Partner (“Pay”). On the next page, you will find a table illustrating this flow and when each of these steps takes place. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coda.co/coda-portal/finance-guide/reconciliation-invoicing-and-settlement.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.