International Peer-Reviewed JournalOpen AccessISSN 2456-8880
irejournals@gmail.com+91-7433024337

Home / Current Issue / Paper 1722515

1722515 Vol 10 · Issue 2 Download Paper

From Software Acquisition to Operational Capability: Measuring ERP-Enabled Performance: A Transaction-Level Benchmarking Study and Prospective Matched-Case Evaluation Framework for SMES And Government Vendors

Nkosana Mkandla Marlon Munjoma Melody Sydney Flora Phiri Munashe Naphtali Mupa

Subject area: Science,Engineering and Technology  ·  Area of research: Digital Transformation

DOI: https://doi.org/10.64388/IREV10I2-1722515

Abstract

Enterprise resource planning (ERP) projects are often evaluated at acquisition, configuration or go-live, although the economic and operational value of an integrated system depends on whether the organisation redesigns processes, governs data, embeds controls, develops user capability and measures realised benefits. This study develops an acquisition-to-capability framework and tests its operational measurement layer using a public 70,000-record analytical extract of the DataCo Smart Supply Chain dataset. The extract contains 44,026 unique orders dated from 2015 to 2018. Analysis was conducted at order and order-line levels using descriptive statistics, cross-segment heat maps, robust logistic regression, holdout prediction, calibration assessment, bootstrap confidence intervals and sensitivity testing of a six-component ERP Operational Capability Index (EOCI). The order-level late-delivery rate was 54.7%, severe delay affected 23.6%, negative-profit exposure affected 19.6%, and hard workflow exceptions affected 10.8%. Shipping configuration was the dominant observable delivery factor: compared with Standard Class, adjusted late-delivery odds were 34.22 times higher for First Class, 5.42 times higher for Second Class and 1.40 times higher for Same Day. A leakage-controlled holdout model achieved an area under the receiver operating characteristic curve of 0.731, a Brier score of 0.197, a calibration intercept of 0.008 and a calibration slope of 0.967. Observed on-time delivery rose from 11.2% in the lowest readiness quartile to 62.9% in the highest, a 51.6-percentage-point difference. EOCI rankings were stable under alternative weights (Spearman rho=0.998). The shipping-mode odds ratios reflect this dataset's own service-level design and are reported as a demonstration of what transaction-level analytics can reveal, not as a general finding about ERP-enabled delivery performance. The findings show that transaction visibility can diagnose capability gaps, but software records alone cannot establish implementation causality. The paper therefore specifies a matched difference-in-differences field protocol, KPI dictionary, governance gates and implementation playbook for SMEs and small government vendors. The central conclusion is that ERP value is realised through a governed operating system, not through software possession.

Keywords

enterprise resource planning; operational capability; process redesign; data governance; internal controls; user adoption; SME digital transformation; government vendors; supply-chain analytics; benefits realization

References

[1] Aladwani, A.M. (2001) 'Change management strategies for successful ERP implementation', Business Process Management Journal, 7(3), pp. 266-275. https://doi.org/10.1108/14637150110392764.

[2] Alles, M.G., Kogan, A. and Vasarhelyi, M.A. (2006) 'Continuous monitoring of business process controls: A pilot implementation of a continuous auditing system at Siemens', International Journal of Accounting Information Systems, 7(2), pp. 137-161. https://doi.org/10.1016/j.accinf.2005.10.004.

[3] AlMuhayfith, S. and Shaiti, H. (2020) 'The impact of enterprise resource planning on business performance: With the discussion on its relationship with open innovation', Journal of Open Innovation: Technology, Market, and Complexity, 6(3), 87. https://doi.org/10.3390/joitmc6030087.

[4] Aloini, D., Dulmin, R. and Mininno, V. (2007) 'Risk management in ERP project introduction: Review of the literature', Information & Management, 44(6), pp. 547-567. https://doi.org/10.1016/j.im.2007.05.004.

[5] Amoako-Gyampah, K. and Salam, A.F. (2004) 'An extension of the technology acceptance model in an ERP implementation environment', Information & Management, 41(6), pp. 731-745. https://doi.org/10.1016/j.im.2003.08.010.

[6] Austin, P.C. and Stuart, E.A. (2015) 'Moving towards best practice when using inverse probability of treatment weighting using the propensity score to estimate causal treatment effects in observational studies', Statistics in Medicine, 34(28), pp. 3661-3679. https://doi.org/10.1002/sim.6607.

[7] Bertrand, M., Duflo, E. and Mullainathan, S. (2004) 'How much should we trust differences-in-differences estimates?', Quarterly Journal of Economics, 119(1), pp. 249-275. https://doi.org/10.1162/003355304772839588.

[8] Bharadwaj, A.S. (2000) 'A resource-based perspective on information technology capability and firm performance: An empirical investigation', MIS Quarterly, 24(1), pp. 169-196. https://doi.org/10.2307/3250983.

[9] Bradford, M. and Florin, J. (2003) 'Examining the role of innovation diffusion factors on the implementation success of enterprise resource planning systems', International Journal of Accounting Information Systems, 4(3), pp. 205-225. https://doi.org/10.1016/S1467-0895(03)00026-5.

[10] Callaway, B. and Sant'Anna, P.H.C. (2021) 'Difference-in-differences with multiple time periods', Journal of Econometrics, 225(2), pp. 200-230. https://doi.org/10.1016/j.jeconom.2020.12.001.

[11] Chingezi, E., Chingezi, L., Ganyani, L., Yelduora, P.G. and Mupa, M.N. (2026a) 'Accounting analytics for inventory integrity and working capital control: Continuous auditing approaches for ERP-enabled supply chains', Iconic Research and Engineering Journals, 10(1), pp. 48-58. https://doi.org/10.64388/IREV10I1-1719387.

[12] Chingezi, E., Chingezi, L., Ganyani, L., Yelduora, P.G. and Mupa, M.N. (2026b) 'Reducing repeat findings and control failures in operationally intensive U.S. enterprises: A data-driven internal audit framework for remediation, loss prevention, and governance improvement', World Journal of Advanced Research and Reviews, 30(3), pp. 2188-2199. https://doi.org/10.30574/wjarr.2026.30.3.1792.

[13] Chou, S.-W. and Chang, Y.-C. (2008) 'The implementation factors that influence the ERP benefits', Decision Support Systems, 46(1), pp. 149-157. https://doi.org/10.1016/j.dss.2008.06.003.

[14] Chukwuemeka, O.D.T. and Mupa, M.N. (2026a) 'Predictive training analytics for competency-based pilot instruction: Early detection of checkride risk, procedural noncompliance and safety-relevant learning gaps', World Journal of Advanced Research and Reviews, 30(3), pp. 1928-1942. https://doi.org/10.30574/wjarr.2026.30.3.1774.

[15] Constante, F., Silva, F. and Pereira, A. (2019) DataCo Smart Supply Chain for Big Data Analysis. Mendeley Data, Version 5. https://doi.org/10.17632/8gx2fvg2k6.5.

[16] Cotteleer, M.J. and Bendoly, E. (2006) 'Order lead-time improvement following enterprise information technology implementation: An empirical study', MIS Quarterly, 30(3), pp. 643-660. https://doi.org/10.2307/25148743.

[17] Davenport, T.H. (1998) 'Putting the enterprise into the enterprise system', Harvard Business Review, 76(4), pp. 121-131.

[18] DeLone, W.H. and McLean, E.R. (2003) 'The DeLone and McLean model of information systems success: A ten-year update', Journal of Management Information Systems, 19(4), pp. 9-30. https://doi.org/10.1080/07421222.2003.11045748.

[19] Eller, R., Alford, P., Kallmunzer, A. and Peters, M. (2020) 'Antecedents, consequences, and challenges of small and medium-sized enterprise digitalization', Journal of Business Research, 112, pp. 119-127. https://doi.org/10.1016/j.jbusres.2020.03.004.

[20] Gattiker, T.F. and Goodhue, D.L. (2005) 'What happens after ERP implementation: Understanding the impact of interdependence and differentiation on plant-level outcomes', MIS Quarterly, 29(3), pp. 559-585. https://doi.org/10.2307/25148695.

[21] Hendricks, K.B., Singhal, V.R. and Stratman, J.K. (2007) 'The impact of enterprise systems on corporate performance: A study of ERP, SCM, and CRM system implementations', Journal of Operations Management, 25(1), pp. 65-82. https://doi.org/10.1016/j.jom.2006.02.002.

[22] Hitt, L.M., Wu, D.J. and Zhou, X. (2002) 'Investment in enterprise resource planning: Business impact and productivity measures', Journal of Management Information Systems, 19(1), pp. 71-98. https://doi.org/10.1080/07421222.2002.11045716.

[23] Kallunki, J.-P., Laitinen, E.K. and Silvola, H. (2011) 'Impact of enterprise resource planning systems on management control systems and firm performance', International Journal of Accounting Information Systems, 12(1), pp. 20-39. https://doi.org/10.1016/j.accinf.2010.02.001.

[24] Kuhn, J.R. and Sutton, S.G. (2010) 'Continuous auditing in ERP system environments: The current state and future directions', Journal of Information Systems, 24(1), pp. 91-112. https://doi.org/10.2308/jis.2010.24.1.91.

[25] Madapusi, A. and D'Souza, D. (2012) 'The influence of ERP system implementation on the operational performance of an organization', International Journal of Information Management, 32(1), pp. 24-34. https://doi.org/10.1016/j.ijinfomgt.2011.09.001.

[26] McAfee, A. (2002) 'The impact of enterprise information technology adoption on operational performance: An empirical investigation', Production and Operations Management, 11(1), pp. 33-53. https://doi.org/10.1111/j.1937-5956.2002.tb00183.x.

[27] Nah, F.F.-H., Lau, J.L.-S. and Kuang, J. (2001) 'Critical factors for successful implementation of enterprise systems', Business Process Management Journal, 7(3), pp. 285-296. https://doi.org/10.1108/14637150110392782.

[28] Nicolaou, A.I. (2004) 'Firm performance effects in relation to the implementation and use of enterprise resource planning systems', Journal of Information Systems, 18(2), pp. 79-105. https://doi.org/10.2308/jis.2004.18.2.79.

[29] Nicolaou, A.I. and Bhattacharya, S. (2006) 'Organizational performance effects of ERP systems usage: The impact of post-implementation changes', International Journal of Accounting Information Systems, 7(1), pp. 18-35. https://doi.org/10.1016/j.accinf.2005.12.002.

[30] Petter, S., DeLone, W. and McLean, E.R. (2013) 'Information systems success: The quest for the independent variables', Journal of Management Information Systems, 29(4), pp. 7-62. https://doi.org/10.2753/MIS0742-1222290401.

[31] Ram, J., Corkindale, D. and Wu, M.-L. (2013) 'Implementation critical success factors (CSFs) for ERP: Do they contribute to implementation success and post-implementation performance?', International Journal of Production Economics, 144(1), pp. 157-174. https://doi.org/10.1016/j.ijpe.2013.01.032.

[32] Ruivo, P., Oliveira, T. and Neto, M. (2014) 'Examine ERP post-implementation stages of use and value: Empirical evidence from Portuguese SMEs', International Journal of Accounting Information Systems, 15(2), pp. 166-184. https://doi.org/10.1016/j.accinf.2014.01.002.

[33] Seddon, P.B., Calvert, C. and Yang, S. (2010) 'A multi-project model of key factors affecting organizational benefits from enterprise systems', MIS Quarterly, 34(2), pp. 305-328. https://doi.org/10.2307/20721429.

[34] Seethamraju, R. (2013) 'Influence of ERP systems on business process agility', IIMB Management Review, 25(3), pp. 137-149. https://doi.org/10.1016/j.iimb.2013.05.001.

[35] Shang, S. and Seddon, P.B. (2002) 'Assessing and managing the benefits of enterprise systems: The business manager's perspective', Information Systems Journal, 12(4), pp. 271-299. https://doi.org/10.1046/j.1365-2575.2002.00132.x.

[36] Strong, D.M. and Volkoff, O. (2010) 'Understanding organization-enterprise system fit: A path to theorizing the information technology artifact', MIS Quarterly, 34(4), pp. 731-756. https://doi.org/10.2307/25750703.

[37] Sykes, T.A., Venkatesh, V. and Johnson, J.L. (2014) 'Enterprise system implementation and employee job performance: Understanding the role of advice networks', MIS Quarterly, 38(1), pp. 51-72. https://doi.org/10.25300/MISQ/2014/38.1.03.

[38] Trkman, P. (2010) 'The critical success factors of business process management', International Journal of Information Management, 30(2), pp. 125-134. https://doi.org/10.1016/j.ijinfomgt.2009.07.003.

[39] Umble, E.J., Haft, R.R. and Umble, M.M. (2003) 'Enterprise resource planning: Implementation procedures and critical success factors', European Journal of Operational Research, 146(2), pp. 241-257. https://doi.org/10.1016/S0377-2217(02)00547-7.

[40] Uwizeyemungu, S. and Raymond, L. (2012) 'Impact of an ERP system's capabilities upon the realisation of its business value: A resource-based perspective', Information Technology and Management, 13(2), pp. 69-90. https://doi.org/10.1007/s10799-012-0118-9.

[41] Venkatesh, V., Morris, M.G., Davis, G.B. and Davis, F.D. (2003) 'User acceptance of information technology: Toward a unified view', MIS Quarterly, 27(3), pp. 425-478. https://doi.org/10.2307/30036540.

[42] Wang, R.Y. and Strong, D.M. (1996) 'Beyond accuracy: What data quality means to data consumers', Journal of Management Information Systems, 12(4), pp. 5-33. https://doi.org/10.1080/07421222.1996.11518099.

[43] Xu, H., Nord, J.H., Brown, N. and Nord, G.D. (2002) 'Data quality issues in implementing an ERP', Industrial Management & Data Systems, 102(1), pp. 47-58. https://doi.org/10.1108/02635570210414668.

[44] Zerbino, P., Aloini, D., Dulmin, R. and Mininno, V. (2021) 'Why enterprise resource planning initiatives do succeed in the long run: A case-based causal network', PLOS ONE, 16(12), e0260798. https://doi.org/10.1371/journal.pone.0260798.

[45] Appendix A. Detailed Field KPI Dictionary

[46] Table 19. Publication-ready KPI dictionary for prospective studies

[47] KPI

[48] Definition

[49] Source

[50] Recommended analysis

[51] Control note

[52] Order-to-cash cycle

[53] Calendar days from accepted order to cleared cash

[54] Order, shipment, invoice, receipt timestamps

[55] Median and 90th percentile; separate customer terms

[56] Excludes disputed orders only if reason documented

[57] Inventory accuracy

[58] 1 - sum absolute count variance / sum system quantity

[59] Cycle-count and ERP stock records

[60] By site, class and item criticality

[61] Negative or zero denominators require defined handling

[62] Reporting latency

[63] Hours/days from reporting cutoff to approved report availability

[64] Close calendar, workflow audit log

[65] Median by report; 95th percentile

[66] Definition must distinguish draft from approved

[67] Invoice rejection

[68] Rejected or returned invoices / submitted invoices

[69] Billing workflow, customer portal, contract system

[70] By reason, customer/agency and value

[71] Duplicates and administrative returns separated

[72] Delivery reliability

[73] On-time complete deliveries / due deliveries

[74] Promise date, shipment, proof of delivery

[75] By service class, contract and root cause

[76] Promise-date changes logged and governed

[77] User adoption

[78] Active competent users / assigned users

[79] Audit log plus task-based assessment

[80] Role specific; monthly/quarterly

[81] Logins alone are insufficient

[82] Control exception rate

[83] Material exceptions / eligible transactions

[84] Control engine and workflow

[85] By control, cause, owner and recurrence

[86] Control changes versioned

[87] Corrective-action closure

[88] Actions closed with verified evidence / actions due

[89] Issue tracker

[90] On-time and overdue ageing

[91] Reopened actions reported separately

[92] Data-quality defect rate

[93] Validated critical defects / records sampled or processed

[94] Data-quality rules and sampling

[95] Completeness, validity, consistency, uniqueness, timeliness

[96] Automated passes do not replace accuracy sampling

[97] Benefit realisation

[98] Verified cumulative benefit / approved target

[99] Benefit register and finance validation

[100] By benefit owner and intervention component

[101] Avoid double counting and unsupported attribution

[102] Appendix B. ERP Capability Evidence Checklist

[103] Approved current-state and future-state process maps with end-to-end ownership.

[104] Requirements traceability linking process, data, control, report and integration needs to testing.

[105] Master-data standards, ownership, migration reconciliation and unresolved-defect register.

[106] Role/access matrix, segregation-of-duties analysis and approval-workflow evidence.

[107] Test coverage for normal, exception, reversal, security, integration and recovery scenarios.

[108] Role-based training materials, task assessments, attendance and remediation evidence.

[109] Super-user and support model with severity, response, escalation and closure expectations.

[110] Baseline KPI pack with signed definitions and historical trends.

[111] Cutover decision, rollback plan, open-risk acceptance and hypercare plan.

[112] Post-go-live adoption, data-quality, control, service and benefits dashboard.

[113] Change-control and release records linking configuration changes to retesting.

[114] Post-implementation review documenting benefits, failures, lessons and next actions.

[115] Appendix C. Interpretation Guide for the EOCI

[116] Table 20. EOCI interpretation bands

[117] Score

[118] Tier

[119] Recommended response

[120] 70-100

[121] Strong

[122] Observed group-level outcomes are comparatively controlled; investigate sustainability, hidden workarounds and cost

[123] 60-69.9

[124] Controlled

[125] Generally functioning with targeted weaknesses; prioritise the lowest component and recurrent exceptions

[126] 50-59.9

[127] Fragile

[128] Material delivery/control weakness; conduct root-cause review and define corrective programme

[129] Below 50

[130] Critical

[131] Systematic capability mismatch or severe outcome failure; executive ownership and immediate redesign required

[132] Note: Bands are managerial heuristics developed for this paper. They require validation before external benchmarking or high-stakes use.

[133] Appendix D. Reproducibility and Quality-Control Notes

[134] Use Order Id as the delivery-level aggregation key and verify within-order consistency before aggregation.

[135] Exclude realised outcomes from predictors when building pre-dispatch risk models.

[136] Retain a temporally separated or site-separated external test set where available; random holdout is a minimum, not a final validation.

[137] Report discrimination and calibration together. A high AUC does not guarantee accurate probabilities.

[138] Version all metric definitions, data transformations, exclusion rules, model code and dashboard logic.

[139] Preserve a cohort-flow table showing source rows, exclusions, duplicates, aggregation and final samples.

[140] Assess missingness and data-quality mechanisms; do not interpret complete fields as necessarily accurate.

[141] Perform subgroup and site-level analyses before operational deployment, and document where estimates are unstable.

[142] Use human review for exceptions and record overrides, rationales and outcomes so that the workflow itself can be evaluated.

[143] Reproduce the present analysis on the full source dataset before journal submission and archive the exact extract checksum.

How to cite this paper

Nkosana Mkandla, Marlon Munjoma, Melody Sydney, Flora Phiri, Munashe Naphtali Mupa "From Software Acquisition to Operational Capability: Measuring ERP-Enabled Performance: A Transaction-Level Benchmarking Study and Prospective Matched-Case Evaluation Framework for SMES And Government Vendors" Iconic Research And Engineering Journals Volume 10 Issue 2 2026 Page 3127-3153 https://doi.org/10.64388/IREV10I2-1722515
Nkosana Mkandla, Marlon Munjoma, Melody Sydney, Flora Phiri, Munashe Naphtali Mupa "From Software Acquisition to Operational Capability: Measuring ERP-Enabled Performance: A Transaction-Level Benchmarking Study and Prospective Matched-Case Evaluation Framework for SMES And Government Vendors" Iconic Research And Engineering Journals, vol. 10, no. 2, Aug. 2026, doi: https://doi.org/10.64388/IREV10I2-1722515
Nkosana Mkandla, Marlon Munjoma, Melody Sydney, Flora Phiri, Munashe Naphtali Mupa (2026). From Software Acquisition to Operational Capability: Measuring ERP-Enabled Performance: A Transaction-Level Benchmarking Study and Prospective Matched-Case Evaluation Framework for SMES And Government Vendors. Iconic Research And Engineering Journals, 10(2). doi: https://doi.org/10.64388/IREV10I2-1722515
Nkosana Mkandla, Marlon Munjoma, Melody Sydney, Flora Phiri, Munashe Naphtali Mupa "From Software Acquisition to Operational Capability: Measuring ERP-Enabled Performance: A Transaction-Level Benchmarking Study and Prospective Matched-Case Evaluation Framework for SMES And Government Vendors" Iconic Research And Engineering Journals, vol. 10, no. 2, Aug. 2026. Crossref, https://doi.org/10.64388/IREV10I2-1722515
@article{1722515,
      author = {Nkosana Mkandla, Marlon Munjoma, Melody Sydney, Flora Phiri, Munashe Naphtali Mupa},
      title = {From Software Acquisition to Operational Capability: Measuring ERP-Enabled Performance: A Transaction-Level Benchmarking Study and Prospective Matched-Case Evaluation Framework for SMES And Government Vendors},
      journal = {Iconic Research And Engineering Journals},
      year = {2026},
      volume = {10},
      number = {2},
      pages = {3127-3153},
      issn = {2456-8880},
      url = {https://www.irejournals.com/formatedpaper/1722515.pdf},
      abstract = {Enterprise resource planning (ERP) projects are often evaluated at acquisition, configuration or go-live, although the economic and operational value of an integrated system depends on whether the organisation redesigns processes, governs data, embeds controls, develops user capability and measures realised benefits. This study develops an acquisition-to-capability framework and tests its operational measurement layer using a public 70,000-record analytical extract of the DataCo Smart Supply Chain dataset. The extract contains 44,026 unique orders dated from 2015 to 2018. Analysis was conducted at order and order-line levels using descriptive statistics, cross-segment heat maps, robust logistic regression, holdout prediction, calibration assessment, bootstrap confidence intervals and sensitivity testing of a six-component ERP Operational Capability Index (EOCI). The order-level late-delivery rate was 54.7%, severe delay affected 23.6%, negative-profit exposure affected 19.6%, and hard workflow exceptions affected 10.8%. Shipping configuration was the dominant observable delivery factor: compared with Standard Class, adjusted late-delivery odds were 34.22 times higher for First Class, 5.42 times higher for Second Class and 1.40 times higher for Same Day. A leakage-controlled holdout model achieved an area under the receiver operating characteristic curve of 0.731, a Brier score of 0.197, a calibration intercept of 0.008 and a calibration slope of 0.967. Observed on-time delivery rose from 11.2% in the lowest readiness quartile to 62.9% in the highest, a 51.6-percentage-point difference. EOCI rankings were stable under alternative weights (Spearman rho=0.998). The shipping-mode odds ratios reflect this dataset's own service-level design and are reported as a demonstration of what transaction-level analytics can reveal, not as a general finding about ERP-enabled delivery performance. The findings show that transaction visibility can diagnose capability gaps, but software records alone cannot establish implementation causality. The paper therefore specifies a matched difference-in-differences field protocol, KPI dictionary, governance gates and implementation playbook for SMEs and small government vendors. The central conclusion is that ERP value is realised through a governed operating system, not through software possession.},
      keywords = {enterprise resource planning; operational capability; process redesign; data governance; internal controls; user adoption; SME digital transformation; government vendors; supply-chain analytics; benefits realization},
      month = {August},
      doi = {https://doi.org/10.64388/IREV10I2-1722515}
  }