Reduce the AP team from 100 to 70 FTE.
Fictional worked example
AI works, but the proposed reduction is too aggressive
An accounts-payable team has achieved a substantial productivity improvement from AI. Management proposes removing 30 FTE. The Stress Test supports a structural reduction, but only 18 FTE now.
You do not have to prove that AI failed to challenge the restructuring that follows.
Decision at a glance
The proposal and the evidence do not support the same number.
A concentrated structural block is supported after period-end, control and coverage requirements are protected.
Use redeployment, temporary assignment and attrition where they improve implementation inside the 18-position envelope.
The proposed 30-FTE immediate reduction outruns the evidence.
Evidence behind the case
AI productivity is real. The question is how much structural capacity it creates.
Observed evidence
- Average invoice-processing time is 31% lower.
- Net human workload is approximately 24% lower once exception handling, controls and remaining human work are included.
- Approximately 18 FTE-equivalent of released capacity is concentrated in high-volume standard invoice processing.
- Approximately 6 FTE-equivalent remains dispersed in small fractions across continuing roles.
- Month-end and quarter-end workload has not fallen by the same amount as average workload.
- Quality and control-error rates are unchanged.
- The staffing model supports removing the concentrated 18-FTE block while preserving current minimum period-end coverage.
Economics and remaining assumptions
Assumptions still carrying the recommendation
- Standard invoice volumes remain stable.
- Current AI accuracy persists at scale.
- Period-end demand does not increase materially.
- Dispersed productivity gains may eventually consolidate, but that has not yet been demonstrated.
The capacity bridge
The gap appears before the structural decision.
The same six-stage capacity bridge used in the Stress Test shows why a 31% productivity result does not establish a 30-FTE reduction.
AI productivity
Average invoice-processing time is 31% lower.
Net human work change
Net human workload is approximately 24% lower.
Released capacity
Approximately 24 FTE-equivalent is released.
Structurally addressable capacity
Approximately 18 FTE forms an identifiable block. Around 6 FTE-equivalent remains dispersed.
Capacity that must remain
Period-end coverage, exceptions, controls and continuing-role requirements protect the rest.
Capacity available for choice
Approximately 18 FTE is available now.
The four questions
Where the proposed 30-FTE reduction survives, and where it fails.
How much human work is actually no longer required?
SupportedAverage processing time is 31% lower, but that is not the number used for the structural decision. Once exceptions, controls and remaining human activity are included, net human workload is approximately 24% lower.
Is released capacity structurally addressable?
PartlyApproximately 18 FTE-equivalent is concentrated in high-volume standard invoice processing and forms an identifiable block. The remaining approximately 6 FTE-equivalent is spread through continuing roles in small fractions.
What capacity must remain to protect performance, coverage, skills and resilience?
18 FTE availablePeriod-end demand is the binding operating constraint. The retained organisation still needs capacity for exceptions, financial controls, period-end peaks, ERP-specific capability, escalation and reconciliation.
Is the proposed reduction, at this amount and timing, economically better than the credible alternatives?
18 now is strongerThe credible choices are not only “cut 30” or “do nothing”. Different amounts, timing and implementation mechanisms need to be compared.
Stress Test conclusion
Choose a different structural option.
AI has genuinely reduced human work and a structural reduction is justified. The proposed 30-FTE immediate reduction is not the strongest available choice.
What could change the answer
The 18-FTE recommendation is supported now, not pre-approved forever.
Open conditions
- Complete two quarter-end cycles after the initial reduction.
- Track whether dispersed released capacity consolidates into identifiable structural units.
- Monitor exceptions, control performance and period-end service.
- Use suitable internal vacancies or temporary assignments where they improve implementation economics.
- Recalculate minimum staffing before approving another permanent tranche.
Retest the amount if
- Dispersed gains consolidate into identifiable capacity.
- Sustainable vacancies emerge.
- Period-end demand materially changes.
- Exception or control workload changes.
- Restoration time or cost changes materially.
- A materially higher-value use of the capacity emerges.
What this example shows
AI can work, a structural reduction can be justified, and the proposed reduction can still be wrong.
A productivity result does not close the gap between measured work reduction and the structural capacity the organisation can actually remove.
AI Restructuring Business Case Stress Test
Apply the same test to your own case.
Use the parent resource to test the bridge from AI productivity to a proposed permanent capacity decision.