A late flag needs a defensible schedule, deadline and receipt interpretation. The reporting obligation and payment obligation are separate. Start with the arrangement that explains what the employer or unit owes the union in information and timing.
Step 01
Verify the expected occurrence
Review the effective arrangement, included units, recurrence, due date, time zone and nil-submission policy. Confirm source evidence with the owner before treating a generated occurrence as authoritative. A missing configuration should produce a configuration question, not an accusation that an employer is late.
Step 02
Classify the actual gap
Compare receipts with expected reporting and payment separately. Investigate an unmatched file before requesting a duplicate. A received submission can still require completeness review; a deposit can arrive without the reporting needed to allocate it. Record what is known and what remains unverified.
Step 03
Assign and retain the follow-up
Use the staff follow-up queue to assign responsibility, document the issue and apply a permitted bounded snooze with a reason. Review the retained history when work resumes. Employer statements expose only their permitted aggregate scope; do not send member-level exceptions as a shortcut.