Allocation Errors

The allocation system enforces a set of Allocation Rules however migration of data from external systems can lead to a number of issues noted below.

Source Transaction Problems

The transaction header or lines may have an incorrect status when compared to the funds allocated to/from them.
- The transaction appears to be paid when it is either underpaid, not paid, part paid or over paid.
- ...and so on...
The Tran_Type entity does not match the Entity_Id on the lines.
The Asset_Id or Name_Id of funds and paid items do not match.
Cheques and deposits may have negative lines which are incorrect.

The Allocation_Date of the allocation is incorrect, so reports using this as the date that a bill for example was paid will be incorrect.
The total allocations from a funds transaction like a deposit may exceed the value of that deposit meaning that it is Over Allocated.
The total allocations from a funds transaction like a deposit may be negative, meaning that the deposit is Under Allocated.
The total allocations to a paid transaction like an invoice may exceed the value of that deposit meaning that it is Over Paid.
The total allocations to a paid transaction like an invoice may be negative, meaning that the deposit is Under Paid.
A negative allocation links a -ve funds line to a -ve paid line. This allocation should be +ve.

Generally allocation problems can be fixed by reversing one or more allocations. A number of stored procedures are available to assist with this:

am_allocate_fix can be provided with a Line_Id and it will reverse allocations and reallocate funds to correct the problem.
am_allocate_cancel will create an allocation that reverses the nominated allocation(s).
am_allocate_adjust can adjust the value of an existing allocation by creating a reversing allocation and another allocation for the new amount.