A payroll file reports deductions. A bank deposit reports money received. They can arrive on different days and disagree. UnionStack retains these as distinct evidence so staff can explain an unresolved remittance rather than treating receipt, review and payment as one status.
Step 01
Inspect and map the source
Choose the employer and pay-period context, inspect the supported CSV or XLSX source and review column mappings. Confirm person and payroll identities before accepting rows. Preserve the original file and its provenance where protected-file storage is configured. A submission receipt alone does not mean the data is complete or posted.
Step 02
Resolve exceptions before posting
Compare the staged population and amounts with expected coverage. Investigate missing units, unidentified people and calculation differences. Keep the reason and evidence for any permitted decision. Post only through the authorized review path; correct posted history with the supported correction workflow rather than editing away its origin.
Step 03
Allocate cash and explain the remainder
Review imported bank transactions and scoped matching suggestions where enabled. Allocate the actual deposit to the relevant remittances, then inspect any unallocated amount or unpaid portion. Keep member withholding history, cash allocation and policy-based standing separate when answering a member or employer inquiry.