> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/finance-and-cash.md).

# Finance & Cash

Manage non-stock invoices, prepayment invoicing, contra balances, and cash flow visibility in Bevica.

Use this section to manage day-to-day finance processes and cash visibility in Bevica.

### Summary

* Post and review non-stock transactions for sales and purchasing.
* Control prepayment invoicing when you need deposits or staged billing.
* Use contra processing to net off balances when a trading partner is both customer and vendor.
* Get cash flow context and training links for forecasting and analysis.

### Next steps

* If you post charges without items, start with [Non-Stock Sales Invoices and Credit Memos](https://kb.bevica.com/documentation/guides/finance-and-cash/non-stock_sales_invoices_and_credit_memos.md).
* For non-stock supplier charges, use [Non-Stock Purchase Invoices and Credit Memos](https://kb.bevica.com/documentation/guides/finance-and-cash/non-stock_purchase_invoices_and_credit_memos.md).
* If you see finance-only differences, check [Finance Only Price Discrepancies](https://kb.bevica.com/documentation/guides/finance-and-cash/finance_only_price_discrepancies.md).
* If you invoice deposits, set up and run [Prepayment Invoicing](https://kb.bevica.com/documentation/guides/finance-and-cash/prepayment_invoicing.md).
* If you need netting, configure and run [Contra Balances](https://kb.bevica.com/documentation/guides/finance-and-cash/contra_balances.md).
* For forecasting and analysis, review [Cash Flow Overview](https://kb.bevica.com/documentation/guides/finance-and-cash/cash_flow_overview.md).


---

# 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://kb.bevica.com/documentation/guides/finance-and-cash.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.
