> For the complete documentation index, see [llms.txt](https://guide.acumensystems.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.acumensystems.com.au/system-parts/debtors/receipts/receipt-allocation.md).

# Receipt Allocation

All receipts must be fully allocated against either the customers transactions or the Ledgers before the receipt can be considered complete (inactive). This allocation phase can be separated from the receipt entry phase so that it may be carried out by accounts staff.

While you may nominate the transactions and amount to be posted by hand, for Account receipts it is usually far easier to have the computer automatically post the receipt. Automatic distribution of Account receipts uses a principle of best match, searching as follows:

* A total balance for an age or ages that matches the receipt total.
* A sequence of transactions starting from the oldest first that adds up to the receipt total.
* A single transaction balance matching the receipt total.
* A sequence of transactions starting from the oldest first and skipping one transaction that adds up to the receipt total.
* As above skipping 2 then 3 transactions etc.
* If no exact match is found then the oldest transactions are allocated until the receipt total is fully allocated. This may result in a partial allocation against the last transaction loaded to the receipt. If there are insufficient transactions to fully allocate the receipt then the balance will remain unallocated.

![](https://4292890076-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MIXjqwujolmdHaVH5d4%2F-MTICoChbYHSo0Y1OE_g%2F-MTIEBcM9rYWwyv9yrDG%2FReceiptAllocation.png?alt=media\&token=9f4ca46f-6c98-4fd0-ac2f-b70613c2fd9c)

If the automatic distribution facility makes allocations against transactions you do not wish to be allocated, you can enter a zero amount to be allocated to these transactions (or any other amount). You can then use the auto distribution option again to allocate the amount freed by these alterations. In this event the distribution system will skip over the allocations that are already on the receipt and allocate to new transactions (assuming there are other transactions to choose from).

Note that a receipt can be processed any time. There is no need to allocate any amount of a receipt before it is processed against the files. Likewise the receipt can be partially allocated, processed, further allocated and processed as many times as is necessary. The only restriction is that once an amount is posted it can no longer be altered. Thus once the receipt amount has been posted the value of the receipt or its discount cannot be altered. Likewise once an allocation is made to a transaction from a receipt and is processed, that allocation cannot be increased, decreased or removed.

{% hint style="warning" %}
**Caution**. If you have a receipt for a customer that has allocations and has not been processed, then you begin a second receipt for the same customer, do not use the automatic distribution feature as it will be unable to detect the allocations already placed on the first receipt. Either process the first receipt, or remove the allocations from the first receipt and process it. Alternatively manually enter the allocations on the second receipt to ensure that the same transaction is not allocated for both receipts.
{% endhint %}


---

# 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://guide.acumensystems.com.au/system-parts/debtors/receipts/receipt-allocation.md?ask=<question>&goal=<endgoal>
```

`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.