Within the current solution, if a cycle count is auto-posted (meaning, it's within the threshold specified on the Warehouse Worker record), the action to create/post the counting journal takes place when the specific cycle count line is processed. The issue with this is, if a user backs out of the work, rather than completing any remaining lines on the cycle count work, the reference to the 'Counting discrepancies accepted' work is severed and you are left with a 'Counting discrepancies accepted' work and a counting journal that you can not tie back to the original source order (i.e. the work the user backed out of). This presents a potential audit concern.

Instead, if the posting of the counting journal was delayed until the original Cycle Count work was completed, you would no longer lose this relation to the source order.