Payments grouping code
Typically, transactions are grouped with an event number that represents an allocation at a point in time. For example, if two invoices are cleared by one payment by the same allocation, that equals a single event:
- Invoice 1: 100
- Invoice 2: 200
- Cash: 300
If the cash payment is allocated in two sessions, then there are two events:
- Invoice 1: 100
- Cash 1: 100
- Invoice 1: 200
- Cash 1: 200
A super event is required to link items that belong to several events. This super event number is known as a grouping code (GC). This code remains active until the value of all linked items, invoices, and cash, reaches zero as a result of all allocations, adjustments, and write-offs.
How Infor meets this requirement
In SyteLine, AP payment processing requires that all transactions be fully allocated prior to posting (i.e. vendor invoices, vouchers, writeoffs, etc.)
Although there is no grouping code ID, each payment header represents a group of allocated transactions.