> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/administrator-help-guides/fund-management.md).

# Fund Management

Funds are an opt in feature (i.e. they are disabled for organisations by default). If you think your organisation could benefit from using the funds module, please get in touch with Tahua Support.

### What is a Fund

A Fund is a discrete pool of money set aside for distribution to applicants — think restricted donor fund or grant pot, not a program category or a label. It has its own balance: a total amount available for distribution, the amount already paid out, and the remaining available amount, calculated automatically.

Key details held against each Fund include:

* name
* description
* internal notes
* distribution amount
* an external ID (used for matching during import)
* a Xero account code (only relevant if your organisation uses the Xero integration)
* and an option to keep the fund anonymous by showing an alias instead of its real name.

Funds also support custom fields, so your organisation can track additional information specific to how they run their funds. Full edit history is retained.

### How it fits into the workflow

Funds aren't selected when someone creates an Application or a Grant — there's no field for it on those forms. Instead, an Administrator allocates Funds afterwards, recording which Fund(s) a record draws from, for which year, and how much.

You can allocate Funds to:

* **Applications** — from the Application's **Fund Allocations** tab.
* **Contracts** — from the Contract's **Allocations** tab, or on the **Funding** step when you create the Contract. This is useful for Contracts that aren't linked to an Application, or whose Application has no allocations.
* **Milestones** — from the Milestone's **Allocations** tab, or per Milestone when you [create a Milestone Batch](https://help.tahua.io/knowledge-base/administrator-help-guides/milestones/create-milestone-batch.md). This is mainly for Milestones that have nothing to inherit from.

To enter allocations for many records at once, use **Fund Management > Fund Allocations**. For step-by-step instructions, see [Allocating Funds](https://help.tahua.io/knowledge-base/administrator-help-guides/fund-management/allocating-funds.md).

From there:

* **Payment batching** — a fund's available balance can be automatically distributed into a batch of payments, based on distribution rules that tie a fund to a category of recipient and payment type.
* **CSV import** — admins can bulk-import or update fund amounts via a CSV template.
* **Reporting** — Funds are a selectable source in the report builder, and can be tagged for organisation, using the same tagging mechanism available on other record types.
* **Payments view** — each Payment has a **Funds** tab showing which Funds it was paid from, and each Fund has a **Payments** tab listing the payments made from it, with links to the Application, Contract and Milestone each one came from.

### Which Fund allocations does a Milestone payment use?

When a Milestone payment is marked as paid and it doesn't already have its own Fund breakdown, Tahua splits it across Funds automatically. This happens however the payment is paid: by an Administrator in Tahua, or when the Xero, QuickBooks Online or MYOB payment sync picks up that the bill has been paid.

Tahua uses the most specific allocations available:

| If…                                         | The payment is split using…                                                                                                                             |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The Milestone has its own allocations       | Only the Milestone's allocations. The Application and Contract allocations are ignored for this Milestone.                                              |
| The Milestone has no allocations of its own | The Application's allocations **combined with** the Contract's allocations (for a Contract Milestone). Allocations to the same Fund are added together. |
| Nothing is allocated anywhere               | No Fund breakdown is added. You can still add one by hand on the payment's **Funds** tab.                                                               |

The split is pro-rata. For example, if an Application is allocated $2,000 to Fund A and $1,000 to Fund B, every Milestone payment is split two-thirds to Fund A and one-third to Fund B. Allocations to the same Fund across different years are combined, and any rounding difference goes on the last Fund so the breakdown always adds up to the payment amount.

A payment that already has a Fund breakdown, for example one entered by hand or one created from a Decision, is left as it is. You can adjust any payment's split afterwards on its **Funds** tab.

{% hint style="info" %}
**Using Xero, QuickBooks Online or MYOB?**

The same split is used to build the bill: a Milestone bill gets one line per allocated Fund. If you add, edit or remove an allocation, any unpaid Milestone bills that draw on it are updated automatically. Paid bills are never changed. See [Xero FAQs](https://help.tahua.io/knowledge-base/integrations-help-guides/xero/xero-faqs.md), [MYOB FAQs](https://help.tahua.io/knowledge-base/integrations-help-guides/myob/myob-faqs.md) or [What does the QuickBooks Integration do?](https://help.tahua.io/knowledge-base/integrations-help-guides/quickbooks-online/what-does-the-quickbooks-integration-do.md).
{% endhint %}

### Admin Abilities

Admins can create, edit, view, and delete Funds, plus: allocate Funds to Applications, Contracts and Milestones, view/manage payments made from a fund, view history, generate a payment batch, recalculate allocations, and import fund amounts via CSV.

Fund form fields: Name, Distribution Amount, Recalculate Allocations (checkbox), Tags, Description, Notes, External ID, Xero Account Code (shown only if your organisation is connected to Xero), Anonymous (checkbox) + Anonymous Name, plus any custom fields your organisation has defined.

Fund list columns: External ID, Name, Distribution Amount, Paid Amount, Available Amount, Anonymous, Anonymous Name, Tags, plus any custom fields flagged for display in the list.

<figure><img src="https://4124979405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F49pNEQ4fXNtxv0yJ5jgn%2Fuploads%2FVrMakgLeNQl7YNIeJp2L%2Fimage.png?alt=media&amp;token=b40c72a2-8a7e-4e20-9c48-bbe4c8861fa6" alt=""><figcaption></figcaption></figure>
