> For the complete documentation index, see [llms.txt](https://docs.buildertek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildertek.com/contractor-invoice.md).

# Contractor Invoice

Once the Purchase Order has been approved by the vendor, the next step is to create a Contractor Invoice (CI).

The Contractor Invoice serves as the financial record used to request payment for completed work, delivered materials, or project milestones. BuilderTek allows Contractor Invoices to remain directly connected to the Purchase Order, ensuring that all pricing, quantities, and scope items remain aligned throughout the procurement and payment process.

While Contractor Invoices can be created through multiple areas within BuilderTek, the most common workflow is to create them directly from the Purchase Order.

BuilderTek supports three different methods for creating Contractor Invoices, allowing organizations to select the process that best matches their operational workflow:

* Create Contractor Invoice by Progress
* Request Invoice with Actual Quantities
* Create Complete Contractor Invoice

Each option is designed for a different stage of project execution and payment management.

<br>


---

# 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.buildertek.com/contractor-invoice.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.