Skip to main content
DigitalSanctum.
Published reference case Definition v12

Expense Reimbursement

See why reimbursement claims stall, and what to improve first.

This published Expense Reimbursement model exposes correction loops, policy exceptions, approvals, audit controls and recovery outcomes across four roles. Sanctum Chat is the process-analysis assistant used to structure source knowledge; Sanctum Flow validates and presents the resulting BPMN.

Model my process

Start with a document or a short conversation. No BPMN knowledge required.

Inspect the published process

The evidence points to correction turnaround as the dominant elapsed-time constraint. Inspect the current process, the directional scenario and the unvalidated redesign opportunities separately.

Definition validation evidence

Definition
Expense Reimbursement v12
Standard tested
OMG BPMN 2.0.2
Validation
XSD, Tier-0 and presentation gates passed
Operating scope
18 top-level + 56 drill-down steps

Executive finding

Correction turnaround drives the long tail

Correct, resubmit or withdraw contributes about 81% of simulated elapsed time under the baseline assumptions, and the P95 exceeds 13 days.

Priority: Measure correction-age bands, clarify evidence defects at first contact and test guided correction reminders before redesigning approvals.

Validated

Current process

Definition v12 passed OMG BPMN 2.0.2 and Sanctum Flow validation.

18 top-level activities

56 drill-down activities

Simulated

Operating improvement

Median
12.37h → 6.84h
P95
331.54h → 152.6h

Directional synthetic elapsed-time scenario, not measured client performance.

Candidate next step

Potential redesign interventions

The opportunities are hypotheses to test. No separately validated future-state BPMN is claimed.

Live Process Lab

Inspect the definition. Then test the operating assumptions.

The definition below is served by Sanctum Flow. It is not copied into this website. Use its Definition, Baseline simulation, Operating improvement and Evidence views to inspect the same versioned showcase bundle.

Scope: Claim preparation, validation, correction, policy-exception handling, manager approval, control investigation, finance audit, reimbursement processing, technical recovery, notification and record retention. Excludes: Corporate-card settlement, travel booking, procurement, tax treatment, bank execution, settlement confirmation, fraud-investigation procedure and policy design.

Sanctum Flow · Expense Reimbursement v12

Open full screen
Text alternative: process overview (18 top-level steps)
  1. 1.Reimbursement needed
  2. 2.Capture and validate claim
  3. 3.Resolve correction request
  4. 4.Assess policy and exceptions
  5. 5.Complete manager review
  6. 6.Investigate controls and audit
  7. 7.Process reimbursement and recovery
  8. 8.Rejection outcome
  9. 9.Notify and record reimbursement
  10. 10.Notify and record rejection
  11. 11.Notify and record withdrawal
  12. 12.Notify and record correction expiry
  13. 13.Notify and record cancellation
  14. 14.Reimbursement recorded
  15. 15.Claim rejected
  16. 16.Claim withdrawn
  17. 17.Correction expired
  18. 18.Reimbursement cancelled

Capture and validate claim drill-down (6 steps)

  1. 1.Claim capture started
  2. 2.Prepare and submit claim
  3. 3.Validate claim
  4. 4.Claim complete?
  5. 5.Claim validated
  6. 6.Correction required

Resolve correction request drill-down (6 steps)

  1. 1.Correction response started
  2. 2.Correct, resubmit or withdraw claim
  3. 3.Employee response?
  4. 4.Claim resubmitted
  5. 5.Claim withdrawn
  6. 6.Correction expired

Assess policy and exceptions drill-down (13 steps)

  1. 1.Policy assessment started
  2. 2.Policy compliant?
  3. 3.Policy-breach route?
  4. 4.Review delegated exception
  5. 5.Delegated exception approved?
  6. 6.Review director exception
  7. 7.Director exception approved?
  8. 8.Policy route approved
  9. 9.Policy route rejected
  10. 10.Delegated exception approved
  11. 11.Delegated exception rejected
  12. 12.Director exception approved
  13. 13.Director exception rejected

Complete manager review drill-down (8 steps)

  1. 1.Manager review started
  2. 2.Review claim
  3. 3.Assign substitute manager review
  4. 4.Manager review complete
  5. 5.Manager decision?
  6. 6.Manager approved
  7. 7.Manager correction required
  8. 8.Manager rejected

Investigate controls and audit drill-down (15 steps)

  1. 1.Audit assessment started
  2. 2.Finance audit required?
  3. 3.Control investigation required?
  4. 4.Investigate control flag
  5. 5.Control issue substantiated?
  6. 6.Finance audit route
  7. 7.Perform finance audit
  8. 8.Assign substitute auditor review
  9. 9.Finance audit complete
  10. 10.Finance audit decision?
  11. 11.Audit route approved
  12. 12.Finance audit approved
  13. 13.Audit correction required
  14. 14.Audit route rejected
  15. 15.Control issue substantiated

Process reimbursement and recovery drill-down (8 steps)

  1. 1.Reimbursement processing started
  2. 2.Reimbursement route
  3. 3.Process reimbursement instruction
  4. 4.Processing confirmed?
  5. 5.Recover reimbursement processing
  6. 6.Continue technical recovery?
  7. 7.Reimbursement processing confirmed
  8. 8.Reimbursement recovery cancelled

Current operating assumptions

Illustrative

Employee correction turnaround dominates elapsed time and creates a long tail when claims require resubmission. Manager review is the next material contributor under the controlled assumptions.

P50 elapsed
12.37h
P95 elapsed
331.54h

Operating improvement

Directional

Faster correction turnaround, manager review and finance audit reduce elapsed time while preserving the exact published v12 BPMN control design.

P50 elapsed
6.84h
44.7% lower
P95 elapsed
152.6h
54% lower

What changes in the operating improvement

The validated BPMN control design stays fixed. Only these disclosed synthetic operating assumptions change:

  • Employee correction response 96 hr mean → 48 hr mean
  • Manager review 8 hr mean → 4 hr mean
  • Finance audit 4 hr mean → 2 hr mean

Proposed redesign interventions

What to test next, without pretending a future-state model is already approved.

These interventions are derived from the controlled source and scenario findings. They are not yet a separately validated or owner-approved future-state BPMN.

Guided digital capture and correction

Validate and classify claims at intake, then present incomplete claims through a focused correction experience.

Control requirement

Required evidence, withdrawal and correction expiry must remain explicit and auditable.

Automated policy routing

Apply policy and authority checks before human work, reserving delegated exception review for claims that need it.

Control requirement

Ambiguous or non-compliant claims must fail closed to review or rejection.

Positive low-risk eligibility

Test straight-through approval only where the claim has positive low-risk eligibility evidence; route every other case to accountable review.

Control requirement

Automation must record the policy version and eligibility evidence and must never infer approval from missing data.

Risk-based audit and monitored recovery

Direct flagged claims to audit and make reimbursement failure, retry and cancellation observable rather than implicit.

Control requirement

Audit, recovery, notification and retention outcomes remain explicit in the future control model.

These are precomputed, synthetic, directional results. They are not a client forecast. Elapsed cycle time is not used in the labour-value calculator below.

What the scenario exposes

Bottlenecks become an economic question

A diagram explains the control flow. Scenario analysis shows where waiting and manual work accumulate, so improvement decisions can be tested rather than guessed.

Finding 1

Correction turnaround drives the long tail

Correct, resubmit or withdraw contributes about 81% of simulated elapsed time under the baseline assumptions, and the P95 exceeds 13 days.

Test next

Measure correction-age bands, clarify evidence defects at first contact and test guided correction reminders before redesigning approvals.

Finding 2

Manager review is the next controllable delay

Manager review is the second-largest simulated bottleneck after employee correction, despite affecting fewer cases than routine validation.

Test next

Measure queue age and review eligibility for positively evidenced, low-risk claims while keeping ambiguous cases fail-closed.

Finding 3

Tail reduction needs operating change, not a prettier diagram

Halving three disclosed timing assumptions reduces simulated P50 by 44.7% and P95 by 54.0% without changing BPMN semantics.

Test next

Validate these timing assumptions against real operating data before proposing automation or staffing changes.

Finding 4

Elapsed time and labour value are different

Most correction delay is waiting time; converting the 12.37-hour median cycle directly into labour savings would materially overstate value.

Test next

Use Flow simulation for elapsed performance and the calculator below only for explicit touch-time capacity assumptions.

Who this is for

For leaders accountable for claim speed, policy and control.

Expense reimbursement becomes difficult to govern when evidence, approvals, policy decisions, audit work and recovery are managed as separate conversations.

Finance and people leaders

Understand why reimbursement age grows and where employee experience, policy and financial control interact.

Finance operations

Inspect correction, rejection, withdrawal, expiry and recovery paths alongside the ordinary reimbursement journey.

Transformation and automation teams

Begin with a validated control model before testing intake, routing, timing or automation changes.

Explore your own volume

Model labour capacity separately

This calculator models labour capacity using the assumptions you enter. It is separate from the elapsed-time simulation above and does not include implementation cost.

Illustrative only. This is not a quote, guarantee or financial forecast.

Per claim
A$13
Capacity / year
2,400 hours
Illustrative / year
A$156,000

Formula: monthly volume × 12 × touch-time reduction ÷ 60 × loaded hourly cost.

Method and provenance How process knowledge becomes validated BPMN View the modelling workflow, controlled benchmark status, source material and generation evidence.
  1. 1

    Describe or provide

    Share a non-confidential SOP, operating manual or explain the work conversationally.

  2. 2

    Clarify and structure

    Sanctum Chat asks about actors, decisions, exceptions, controls, timing and missing outcomes.

  3. 3

    Validate and investigate

    Sanctum Flow checks the definition, renders it and runs disclosed operating scenarios.

Published definition evidence

The v12 BPMN definition is published and passed its structural and professional-presentation gates. The 5,000-run simulation is reproducible synthetic analysis of that model. A controlled multi-run Sanctum Chat generation benchmark and a validated future-state BPMN remain separate, unclaimed work.

Evidence pending
Read the disclosed synthetic source SOP

Evidence before claims

Know exactly what has and has not been proven

Definition
Expense Reimbursement v12
Published artifact f323c49129bf… with frozen semantic fingerprint 6c0e58d3ab0d…
Conformance
XSD + Tier-0 + PPG
Zero Tier-0 findings, zero presentation findings and publish_ready=true
Simulation
5,000 deterministic runs
Seed 20260813; synthetic directional assumptions, not measured performance
Human review
Required before operational use
Publication is not represented as OMG certification, tax advice or client approval
Scenario assumptions
  • Both scenarios use the exact published v12 BPMN and its frozen semantic fingerprint; only three timing distributions change.
  • Results use 5,000 deterministic Monte Carlo runs with seed 20260813 and synthetic probabilities and timings from ER-BENCH-SOP-001 v0.3.1.
  • Cycle-time results describe elapsed time and are deliberately separate from the labour-capacity calculator.
  • All five terminal outcomes were observed across the baseline runs: reimbursed, rejected, withdrawn, expired and cancelled.
Current limitations
  • The model does not include queues, calendars, staffing levels, resource capacity, utilisation, claim value or monetary cost.
  • Subprocess outcomes are not correlated with parent outcome gateways in this simulator version.
  • The scenario is directional synthetic evidence, not measured client performance, a forecast or a savings guarantee.
  • A future-state BPMN must be separately refined, validated and owner-reviewed before it can be presented as evidence.

A useful engagement should leave reusable assets

  • ✓ Versioned BPMN definition
  • ✓ Plain-language process narrative
  • ✓ Roles and accountability map
  • ✓ Controls and exception catalogue
  • ✓ KPI and SLA definitions
  • ✓ Disclosed improvement scenarios

Related process models

Published

Invoice Approval Process

Invoice receipt through control validation, approval decision and posting to the payment queue. Payment execution, bank settlement and remittance advice are explicitly out of scope.

View model →
Planned

Accounts Payable Workflow

Vendor invoice capture, 2-way/3-way matching, payment run generation, remittance advice, and early payment discount handling.

Planned

Travel Request & Approval

Travel request submission, budget check, manager approval, booking arrangement, expense pre-authorisation, and post-trip reconciliation.

Start with one process

Bring the SOP nobody has time to model

Tell us what the process does and where it hurts. We will arrange a secure way to review source documents after qualification.

Model my process Browse the library