Skip to content
UnionStack logo UnionStack

Learning centre · People & structure

Configure positions, pay rates and dues

Configure UnionStack position information so membership, compensation and dues reporting share a dependable model.

Workflow context

What this guide helps you accomplish

Configure UnionStack position information so membership, compensation and dues reporting share a dependable model.

Position, step, pay and dues data must be traceable to an approved source because small configuration errors can affect high-value reporting.

Working principle
Position data should be traceable to approved organizational and agreement information, especially when it affects pay or dues.

Before you begin

Prepare the following before changing shared configuration or records:

  • An approved naming standard and a clear source for identity, position, organizational and agreement information.
  • A representative branch of the union structure, including the relationships that make the records meaningful.
  • Fake people and position records that can be changed safely during testing.
  • An approved fake agreement example with effective dates, units, precision and expected calculations.

Procedure

Complete the steps in order with fake or approved test information first. Record configuration decisions that will affect other teams.

01

Define position types

Separate position types only where responsibilities, compensation, dues or reporting meaningfully differ. Use names staff recognize.

02

Configure steps and rates

Document the source and effective period for step or pay-rate information. Confirm precision, units and any exceptional arrangements.

03

Connect positions to people and entities

Link each position to the correct person and organizational context so representation and reporting remain meaningful.

04

Record dues information deliberately

Use approved fields and values for dues calculations or reporting. Restrict access where the information is sensitive.

05

Handle changes without losing context

Update effective information through the organization’s process and preserve prior terms or values needed for audit and interpretation.

06

Reconcile reports to source decisions

Sample calculated or reported values against agreements and approved records after configuration changes.

Product view

UnionStack position details showing fake step, pay rate and dues information
UnionStack 2.0 test environment using fake data. Interface details may vary with your organization’s types, fields, permissions and terminology.

Video demonstration

Troubleshooting

Use the symptoms below to diagnose the workflow before widening access, adding duplicate configuration or bypassing an intended control.

A rate appears correct but uses the wrong effective period

Inspect the source agreement and all effective dates before editing the value. Preserve the prior period where it remains necessary for history or reconciliation.

A person or entity appears more than once

Stop before adding another record. Compare identifiers, contact details and connected positions, then use the organization’s correction process to preserve the authoritative record.

A relationship is technically valid but confusing

Open both connected records and confirm the relationship label answers a useful operational question. Rename or remove relationships that staff cannot interpret consistently.

A report does not match the expected structure

Inspect the underlying type, status, effective dates and entity relationships before changing the report. Correct the source record and rerun the same filter.

Validation checklist

Do not treat the procedure as complete until an authorized second person can reproduce the intended result.

  • A sample position reproduces the approved rate and dues expectation for the tested effective date.
  • The record can be found using the identifiers and terminology staff actually use.
  • Current and historical relationships are distinguishable without overwriting useful history.
  • A user can move from the person to the relevant position, entity or agreement in context.
  • A sample report produces the expected population after source records are reviewed.

Version applicability

UnionStack 2.0

This guide was verified for UnionStack 2.0 on August 16, 2026. Available fields, types, relationships, navigation and access can vary with tenant configuration and user permissions.

Continue learning

Return to the UnionStack Learning Centre, or take the UnionStack product tour to see how these parts connect.