Costing overrides with retro pay
Summary:
Retro elements pick up costing overrides from their originating element. How does this work?
Content (please ensure you mask any confidential information):
- Add a backdated element entry with an element entry level costing override
- Run retro
- View the retro element entry - the costing override is not visible in the retro element entry
- Run a quickpay
- Check costing output - the retro element is costed with the costing override from the originating element
This is desired behaviour, but I'd really like to understand what the costing process is doing here. Do retro elements get some kind of special treatment by the costing logic to pull in costing overrides from the earlier period? Does anyone know what magic is going on here?
Tagged:
1