> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/product/ledger/added-funds-in-the-ledger.md).
# Added Funds in the Ledger
Added funds are funds that are manually added to collective accounts by fiscal hosts when they process manual bank transfers and checks. Added fund related transactions are potentially different from contribution related transactions:
1. They are initiated by a fiscal host admin and not by a contributor.
2. They are created in response to manual data entry (and not automated interaction with a payment processor system).
3. Can be manually dated by the fiscal host admin to reflect when the funds actually arrived. In such cases the “Transaction Date” will show the date (and time) the transaction itself was created in the ledger and and the “Effective date” will show the date entered by the fiscal host admin.
Added funds transaction groups typically look like contributions in the ledger where instead of a pair of CONTRIBUTION transactions there will be a pair of ADDED\_FUNDS transactions.
---
# 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.opencollective.com/help/product/ledger/added-funds-in-the-ledger.md?ask=&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.
