This function is part of the prepayments cycle. In prepayment entry (see Payments entry documentation), it cannot be allocated to an order. In this case, the prepayment open item paid remains to be allocated. The allocation leads to the total or partial deduction of the prepayment on the selected invoice(s).

If there is more than one invoice, you need to process each prepayment allocation separately.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Header criteria

You must enter the company and a Pay-by BP; the site is optional. The prepayment allocation is carried out for that BP.

Grid content

The open items to be processed are displayed in a grid. Some columns cannot be modified.

Allocation

By default, this column is Unallocated. You must select an allocation to post the open item:

  • Order: The payment is allocated to an order and you must enter the order number in the Order/Invoice column.
  • Invoice: The payment is allocated to an invoice and you must select the Invoice type and enter the invoice number in the Order/Invoice column.

The currency of the allocated open item (order or invoice) must be the same as the payment currency. It can be different from the bank currency.

Currency and Paid

These fields display the prepayment amount and its currency. They cannot be modified.

Amount to allocate

By default, this column displays the remaining amount to be allocated for the given payment (balance). You can post the prepayment to several orders or invoices. In that case, you can change the allocation amount for a specific open item. You can only allocate to one open item at a time, then repeat the process for another open item. As long as the payment is not completely allocated, the amount displays along with its various allocations.

Site and Payment

Both columns displays information on the prepayment settlement: site where the payment is recorded and payment number.

Type, Entry number and Tax

These three columns display information about the accounting entry generated when validating the payment (bank posting) and cannot be modified.

Saving the allocation

When saving the allocation, you can enter a value date (see the DACVALDAT - Value date management parameter - TRS chapter, BNK group). The log file indicates:

  • The order/invoice allocated to the payment
  • The amount
  • The G/L entry number generated

Generating the prepayment transfer journal

A prepayment transfer journal can be generated when:

  • The payment group is different from the invoice group.
  • The tax is adjusted if the payment uses an accounting destination with the prepayment type ACPTR.

Prepayment transfers in currency

The exchange rate applied when generating the G/L entry depends on the the CHGRATIPT - Prepayment exchange rate parameter value (TRS chapter, PPY group).

Reports

By default, the following reports are associated with this function :

  UNALLOCCASH2 : Prepayments to allocate

  UNALLOCCASH1 : List of prepymts to allocate

This can be changed using a different setup.

Specific Buttons

Assignment

Use this button to automatically assign invoices to payments. By default, the older invoices are allocated to the payments preloaded in the grid.

This automatic allocation includes several steps:

  • Grouping prepayment open items not yet allocated
  • Sorting prepayment open items by currency then by amount (from the highest to the lowest)
  • Reviewing all the prepayment open items to post an invoice open item
  • Displaying invoice open item from the oldest to the most recent

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Open item being matched

You cannot allocate a prepayment to an open item currently being matched. This is typically caused by one of the following situations:

  • An allocation of two or more prepayments to the same invoice at a time. In this case you need to process each prepayment allocation in a separate step, (i.e., assign and validate first allocation, then repeat subsequently).
  • A pending matching is in progress in another function.
  • A matching is waiting to be processed by the accounting batch server.

Tables used

SEEREFERTTO Refer to documentation Implementation