> 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/expenses.md). # Expenses ## Overview An Expense Record in BuilderTek is used to capture and manage project-related expenses in one centralized place. An expense can include one or multiple cost lines and can be associated with a specific project, budget, vendor, payment method, and other relevant details. ![](/files/03cbe42812a5cde072f40f1c088ea6b8fcff59f5) Expense Records can be created independently from the Expenses module or directly from a Project. Creating an expense from the Project is the recommended approach, as it automatically associates the expense with the correct project from the beginning. Once created, the expense can also be connected to a budget or utilized through the Funding workflow when required. ### What You Can Manage Through an Expense Record An Expense Record can be used to: * Record project-related expenses * Add multiple expense lines under one record * Associate expenses with a specific project * Add expenses to a project budget * Record vendor and payment information * Track individual cost lines and amounts * Utilize reserved project funds against expenses --- # 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.buildertek.com/expenses.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.