Value Stream Mapping for Superannuation and Pension Administration: From Contribution Receipt to Benefit Paid Without the Rollover Drag

In superannuation and pension administration, the member experiences one outcome: a contribution is received, a rollover is processed, or a benefit is paid accurately and on time. Behind that outcome, however, work may cross administration platforms, identity verification, compliance, investment operations, custody, insurers, payment teams and member communications.

Value stream mapping makes this end-to-end flow visible. It connects the member request to the final outcome, separates touch time from queue time, and shows where defects, handoffs and approval delays create the rollover drag.

This guide presents a worked hypothetical case for a fund processing standard member benefit and rollover cases. It is an improvement model, not legal advice. Any future-state design must preserve applicable fund rules, member consent, reporting and payment obligations. For Australian operations, administrators should validate their design against current ATO rollover reporting requirements and APRA payment standards guidance.

1. Define the Value Stream and Its Boundaries

The fundamental purpose of value stream mapping in financial services is to analyse the complete flow of value, information and decisions, not merely the tasks performed by one department.

Product family

Select one product family with sufficiently similar processing characteristics:

Standard member benefit and rollover cases involving receipt, validation, calculation, approval, payment, allocation and member statement.

Scope boundaries

• Start: Contribution or rollover request received in the administration workflow.
• End: Benefit or rollover paid, allocated or reconciled, with the member statement issued.
• Included: Identity and completeness checks, eligibility, benefit calculation, approvals, external fund or custody handoffs, payment, reconciliation and correspondence.
• Excluded: Complex defined-benefit cases, deceased estates, disputes and cases requiring specialist legal interpretation.

This scope gives the team a manageable value stream while preserving the member’s complete experience. The Voice of the Customer may include fast payment, accurate tax treatment and clear communication. The Voice of the Business may prioritise compliance, cost control and operational resilience. The Voice of the Process is the actual data showing whether the process consistently meets both requirements.

2. Current-State Map: Where the Rollover Drag Accumulates

Assume the fund processes 340 standard cases per month. A process walk identifies the following current-state flow:

Receive request → Validate identity and completeness → Check eligibility and calculate benefit → Obtain approval → Exchange data with external parties → Pay and reconcile → Issue statement and close

The team records 157 minutes of touch time, but the case spends most of its life waiting in queues.

The average rework rate is 22%. In other words, approximately 75 cases per month return to an earlier step because of failed validations, incorrect benefit calculations, missing information or reconciliation exceptions.

Process Cycle Efficiency

Assume one business day contains 480 minutes:

• Queue time: 12.5 × 480 = 6,000 minutes
• Touch time: 157 minutes
• Total lead time: 6,157 minutes
• Value-added time identified by the team: 95 minutes

[
\text{PCE} = \frac{95}{6,157} \times 100 = 1.54%
]

The process is not necessarily short of effort. It is short of flow. Only 1.54% of total lead time directly changes the member’s outcome. The remaining time is queueing, handoff, inspection, rework or administrative delay. The Lean 6 Sigma Hub Process Cycle Efficiency Calculator can help teams perform this analysis with their own observations.

3. Identify the Eight DOWNTIME Wastes

A current-state map should convert observations into focused improvement opportunities.

1. Defects: Failed identity validations, incorrect benefit calculations, incomplete rollover data and reconciliation errors generate rework. A defect prevention strategy should address the upstream cause, not simply add another inspection step.

2. Overproduction: Premature statements, duplicate correspondence and repeated status notifications create work before the underlying transaction is stable.

3. Waiting: Nightly payment runs, supervisor queues, external responses and identity verification holds extend lead time without increasing member value.

4. Non-utilisation of talent: Experienced specialists may spend significant time on data entry, document chasing and manual status updates rather than exception analysis and member-risk decisions.

5. Transportation: Digital work is transported through handoffs between administration, custody, insurers, payment operations and external funds. Each transfer creates a risk of lost context or delayed ownership.

6. Inventory: Unallocated contributions, unresolved rollover cases and incomplete claims are work in process. Excess inventory hides bottlenecks and increases the likelihood of ageing cases.

7. Motion: Administrators switch between portals, spreadsheets, email, document repositories and core platforms to complete one case. Manual lookups add time and increase the chance of transcription errors.

8. Excess processing: Multiple approvals, redundant checks and repeated data validation may be performed without a risk-based reason. Control activities should remain effective while becoming more proportionate.

In the Analyse phase of DMAIC, use Pareto analysis, process stratification, cause-and-effect diagrams and exception data to distinguish common-cause variation from special-cause events. The objective is not to remove necessary governance. It is to make the required control work more reliable and less repetitive.

4. Build the Future State: Flow, Pull and Standard Work

The future-state design should be built around the member outcome and the process constraint. A useful design is:

Single digital intake → Upfront verification → Rules-based calculation → Risk-based approval → Pull-triggered payment → Automatic reconciliation → Event-based statement

Future-state principles

• Level-load daily processing: Replace large nightly batches with a daily capacity plan. For 340 monthly cases across 20 business days, the demand rate is approximately 17 cases per day. Staff to the demand pattern rather than allowing cases to accumulate.
• Use standard work: Create one digital checklist for identity, eligibility, calculation, approval and closure. Define an owner, completion rule and escalation trigger for each step.
• Introduce digital verification: Validate member, fund, bank and rollover data at intake. Route only exceptions to specialists.
• Create pull triggers: Payment, reconciliation and correspondence should be triggered by completion of the preceding verified step, not by a weekly or ad hoc batch.
• Apply risk-based approval: Standard low-risk cases can follow a defined approval rule; complex or high-risk cases can receive specialist review.
• Control work in process: Set queue limits, for example, no more than two business days of unprocessed standard cases in any work centre.
• Use visual management: An Andon-style alert can identify ageing cases, failed validations, stalled external responses and breached internal service triggers in real time.

Agile methods complement this Lean Six Sigma project when improvement work is delivered in short, testable increments. The DMAIC structure provides analytical discipline; two-week Agile sprints can pilot digital verification, approval rules or reconciliation changes without waiting for a single large release.

5. Current Versus Future Performance

The following targets are hypothetical but operationally specific.

The target is not simply faster processing. It is higher first-pass yield, fewer avoidable interventions and a controlled flow that can be sustained. The equation Y = f(x) is useful here: payment accuracy and lead time, represented by Y, depend on critical inputs such as identity completeness, calculation rules, approval logic and data quality.

6. A 90-Day Kaizen Sequence

Days 1–30: Establish the baseline

Owners: Black Belt or improvement lead, Operations Manager, Member Administration Lead

• Observe 30–50 real cases across standard and exception pathways.
• Confirm touch time, queue time, rework categories and touch-count definitions.
• Build the current-state map and Pareto of defects.
• Set daily demand, capacity and ageing dashboards.
• Target: 100% of standard cases measured; baseline PCE validated; top three causes covering at least 70% of rework identified.

Days 31–60: Pilot the future state

Owners: Product Owner, IT Workflow Lead, Compliance Representative, Team Supervisors

• Pilot a digital intake checklist and upfront verification.
• Introduce level-loaded daily work allocation.
• Test a risk-based approval pathway with documented controls.
• Create pull triggers for payment and reconciliation.
• Run two-week Agile improvement sprints and review results using DMAIC evidence.
• Target: Lead time below 5 business days, rework below 12%, and at least 70% first-pass completion in the pilot group.

Days 61–90: Control and scale

Owners: Operations Director, Black Belt, Quality and Risk Leads

• Standardise the successful workflow and train all relevant teams.
• Add control charts for lead time, rework, first-pass yield and ageing inventory.
• Define escalation rules for Andon alerts and external handoff delays.
• Review the value stream monthly and refresh the business case with verified benefits.
• Target: 2.2-business-day average lead time, 7% rework, 85% standard-case first-pass yield and no uncontrolled queue exceeding two business days.

7. Build the Capability to Sustain the Gain

Value stream mapping is more than a diagram. It is a management method for connecting member value, process data, governance and improvement execution.

A Yellow Belt can support observation, data collection and local standard work. A Green Belt can lead the cross-functional project, analyse variation and validate the future state. A Black Belt can manage the statistical analysis, mentor improvement teams and ensure the solution scales across products and administrators.

Build the capability to remove rollover drag with confidence. Explore Lean 6 Sigma Hub’s CSSC-accredited, self-paced Lean Six Sigma Green Belt training, or progress through the Black Belt programme to lead complex financial-services transformation.

Kaizen. Kai-Care. Kai-Done. Lean Six Sigma