Skip to main content
SAAPRO Logo
Why Pronto Xi Users Go Back to Excel, and How to Reduce Spreadsheet Dependency
Support & OptimisationBy SAAPROUpdated

Why Pronto Xi Users Go Back to Excel, and How to Reduce Spreadsheet Dependency

A practical guide to why Pronto Xi users return to Excel, how to separate useful analysis from risky shadow systems, and how to reduce spreadsheet dependency without defaulting to custom development.

When Pronto Xi users repeatedly export data, rebuild reports or manage operational information in Excel, the problem is rarely Excel itself. The spreadsheet is often compensating for an unmet reporting, process, data, integration, training or usability need.

That distinction matters.

Pronto Xi is designed as an integrated ERP and analytics platform spanning finance, supply chain, operations, workforce and analytics. Its Business Intelligence capability uses IBM Cognos Analytics, while Pronto Connect provides APIs and integration mechanisms for connecting Pronto Xi with other applications.

Yet spreadsheets can still become embedded around any ERP.

The wrong executive response is:

“Get everyone out of Excel.”

The better question is:

“What business need is this spreadsheet solving that our governed systems are not?”

For CFOs and CIOs seeking greater ROI from Pronto Xi, recurring spreadsheet dependency is therefore useful evidence of friction somewhere in the operating model.

A practical diagnostic chain is:

Process → Data → Reporting → Integration → Skills → Governance

The aim is not zero spreadsheets.

It is:

Zero uncontrolled critical processes that should live in a governed system.

Are spreadsheets a problem in a Pronto Xi environment?

Not automatically.

General ERP guidance

Excel and other spreadsheets remain useful for:

  • ad-hoc analysis;
  • scenario modelling;
  • budgeting assumptions;
  • temporary calculations;
  • investigation;
  • presenting and manipulating governed data.

The concern begins when a workbook becomes part of the operating system of the business.

For example:

  • critical master data exists only in Excel;
  • inventory or production status is maintained outside Pronto Xi;
  • month-end depends on manually maintained workbooks;
  • employees repeatedly export, manipulate and re-enter data;
  • important KPIs differ depending on whose spreadsheet is opened;
  • only one person understands a critical workbook.

At that point, the issue is no longer spreadsheet preference.

It is spreadsheet dependency.

Four types of spreadsheet use

Not every spreadsheet should receive the same treatment.

1. Analytical spreadsheet

Used for:

  • modelling;
  • one-off analysis;
  • scenario testing;
  • presentation.

Usually legitimate if its source data is governed and the workbook is not pretending to be the system of record.

2. Reporting workaround

A recurring workbook recreates information that users cannot obtain conveniently from the existing reporting environment.

Typical symptoms:

  • the same Pronto export is performed every week;
  • formulas are repeatedly copied;
  • management reports depend on manual preparation.

This often points to a reporting or data-model problem.

3. Process workaround

A spreadsheet coordinates an operational process outside the formal system.

Examples might include:

  • approvals;
  • shortages;
  • job tracking;
  • order status;
  • project actions.

This usually points to a process, configuration, integration or functional gap.

4. Shadow system

The workbook stores critical business data, rules or operational status unavailable elsewhere.

This is the highest-risk category.

It may contain:

  • unique master data;
  • transaction history;
  • critical formulas;
  • separate approvals;
  • data used for financial or operational decisions.

The spreadsheet has effectively become a small, unmanaged application.

How do you know whether a spreadsheet is material?

Use a simple risk test.

FactorQuestion
Business impactWhat happens if the workbook is wrong?
FrequencyIs it used daily, weekly, monthly or occasionally?
Manual interventionHow much copying, manipulation or re-keying occurs?
System-of-record roleDoes unique information exist only here?
Key-person dependencyCan anyone else operate and explain it?
ControlAre access, formulas, changes and versions governed?

A useful prioritisation formula is:

Business impact × Recurrence × Control weakness

Do not spend months cataloguing every workbook in the organisation.

Find the ones capable of:

  • stopping a business process;
  • affecting financial reporting;
  • changing customer or supplier outcomes;
  • creating material operational risk.

One particularly useful question is:

If this spreadsheet disappeared tomorrow, what business process would stop?

That quickly distinguishes personal analysis from genuine shadow infrastructure.

Why do Pronto Xi users go back to spreadsheets?

1. They cannot get the information they need easily

Reporting is a common reason.

Users may need:

  • a different view;
  • additional calculations;
  • combined datasets;
  • exception reporting;
  • recurring management KPIs;
  • easier filtering.

Pronto-specific capability

Pronto Xi's Business Intelligence environment uses IBM Cognos Analytics. Current Pronto documentation describes operational and custom reporting, dashboards, visualisations, scheduled reports, data modules and the ability to combine Pronto Xi data with external sources.

That does not mean Cognos is automatically the answer to every spreadsheet.

The question is:

Is this fundamentally a recurring reporting requirement?

If yes, consider whether it belongs in:

  • an existing Pronto report;
  • Cognos;
  • a governed dashboard;
  • a data model;
  • another approved analytics platform.

If not, keep investigating.

2. Users do not trust the numbers

A user who says:

“My spreadsheet is more accurate than Pronto.”

is signalling something important.

Potential causes include:

  • incomplete or incorrect master data;
  • late transactions;
  • inconsistent coding;
  • different KPI definitions;
  • incorrect reporting logic;
  • integration delays;
  • misunderstanding of what a report measures.

Before producing another report, determine:

Is the underlying data wrong, or are two reports measuring different things?

That distinction is critical.

A reporting tool cannot fix bad source data.

Likewise, correcting good data will not solve a disagreement caused by different definitions.

Pronto's analytics material emphasises governed reporting and the ability to create repeatable data models across Pronto Xi and other sources.

3. The business process does not fit how people actually work

Employees often create a spreadsheet because the formal process feels slower, harder or incomplete.

This might reveal:

  • underused standard functionality;
  • outdated configuration;
  • an unnecessary process step;
  • missing workflow;
  • a genuine functional gap;
  • information required from another application.

Do not immediately rebuild the workbook inside Pronto Xi.

Ask:

Why does this process need to exist outside the ERP?

Fix the cause rather than reproducing the workaround.

4. Information is trapped between systems

Some spreadsheets act as manual middleware.

The process becomes:

System A → Export → Excel → Clean/transform → Re-key/upload → Pronto Xi

If this happens repeatedly, the problem may be integration rather than reporting.

Pronto-specific capability

Pronto Connect provides a RESTful API and integration framework for connecting Pronto Xi with external applications. Pronto's current documentation also describes webhooks, event triggers and integration with middleware or other applications.

That does not mean every spreadsheet transfer deserves an API.

For a temporary, low-volume process, manual handling may still be economically sensible.

But repeated, high-volume or high-risk transfers deserve investigation.

5. Excel is easier and more familiar

This human factor is often underestimated.

Users return to spreadsheets because they offer:

  • familiarity;
  • speed;
  • autonomy;
  • flexibility;
  • easy experimentation;
  • immediate control.

A technically superior solution does not guarantee adoption.

A governed alternative must usually be sufficiently easier, faster or more trustworthy than the workaround, or users will recreate the workaround.

Pronto-specific capability

Pronto Software currently provides a Learning Management System with self-paced training, learning plans and organisation-level progress tracking. Pronto Plus also provides customer support resources, manuals, release information and forums.

But training should not simply teach:

“Click here, then click there.”

Effective ERP training needs to explain:

what the process is, why it matters and what happens downstream.

Users who understand the consequences of a transaction are less likely to maintain unnecessary parallel processes.

6. The spreadsheet solved a problem years ago and never disappeared

Some workarounds are simply historical.

They may have been created before:

  • a Pronto capability existed;
  • an integration was implemented;
  • reporting improved;
  • the business process changed.

The workaround survives because nobody asks whether it is still necessary.

A useful question is:

If we designed this process from scratch today, would we still create this spreadsheet?

If not, it may be technical debt disguised as normal work.

7. Management wants information that was never captured

Not every spreadsheet problem is a reporting problem.

If management wants to analyse an attribute that is:

  • not recorded;
  • inconsistently recorded;
  • hidden in free text;

then a better report cannot reliably create the missing information.

The sequence should be:

Business question → Required data → Data owner → Capture process → Reporting

not:

Business question → Build another spreadsheet.

8. The spreadsheet is faster than waiting for a system change

This is one of Excel's genuine strengths.

A business user can solve today's problem immediately.

The danger comes when:

temporary workaround → recurring process → permanent dependency

without anyone making that decision consciously.

A sensible governance principle is:

Temporary spreadsheets are acceptable. Permanent shadow systems require review.

Should every spreadsheet be replaced?

No.

The right response depends on what the spreadsheet is doing.

SituationLikely response
Genuine ad-hoc analysisKeep the spreadsheet
Repeated management reportImprove governed reporting
Operational tracking outside ProntoReview the process/configuration
Repeated transfer between applicationsAssess integration
Users do not know existing functionalityTraining/support
Poor data creates manual correctionsFix data ownership
Genuine unmet functional requirementEvaluate configuration, extension or other solution
Obsolete workaroundRetire it

A recurring spreadsheet does not automatically mean:

“Build a Cognos report.”

Nor does it automatically justify customisation.

Diagnose first.

How should critical spreadsheets be governed if they remain?

Sometimes the correct answer is to keep the workbook.

If it supports a material business activity, govern it appropriately.

General spreadsheet-control guidance

Consider:

  • a named business owner;
  • documented purpose;
  • clearly identified data sources;
  • controlled access;
  • protected critical formulas;
  • version control;
  • review of material changes;
  • backup and recovery;
  • documented operating instructions;
  • periodic review of whether the workbook is still required.

The amount of governance should reflect the workbook's risk.

A personal scenario model does not require the same control environment as a workbook used to calculate material financial results.

What does spreadsheet dependency actually cost?

The licence cost is rarely relevant.

The economic cost sits in the surrounding work.

Potential components include:

  • Preparation hours
  • Reconciliation hours
  • Re-keying
  • Error/rework
  • Support effort
  • Key-person exposure

For example, if a recurring workbook requires:

  • 10 hours to prepare;
  • 4 hours to reconcile;
  • 2 hours of corrections;

each month, that is:

192 hours per year

before considering risk or management delay.

The correct comparison is then not:

Excel vs Pronto

but:

Cost of maintaining the workaround vs cost of fixing the underlying requirement

The appropriate solution might be a report, process change, training, integration or configuration improvement.

Where does the ROI come from?

Removing a spreadsheet creates no ROI by itself.

The economic value appears only when the work behind it changes.

Potential benefits include:

Less manual effort

Reduce:

  • exports;
  • transformations;
  • copying;
  • re-keying.

Less reconciliation

Use agreed definitions and governed data rather than repeatedly proving which number is correct.

Faster decisions

Make recurring information available without waiting for workbook preparation.

Lower key-person dependency

Move critical business logic and process knowledge away from one employee's file.

Stronger control

Make important transactions, data and calculations more traceable.

Greater ERP utilisation

Use existing Pronto Xi, BI or integration capability where it provides better economics than maintaining parallel work.

Better scalability

Allow transaction volume or organisational complexity to grow without multiplying manual spreadsheet work.

The ROI is not eliminating Excel. It is eliminating unnecessary work, delay and risk.

Do not replace every spreadsheet with custom development

Spreadsheet dependency can sometimes lead organisations directly toward bespoke development.

That should not be the default.

A practical sequence is:

  1. Existing Pronto Xi capability
  2. Process improvement
  3. Data improvement
  4. Training
  5. Governed reporting
  6. Integration
  7. Configuration
  8. Customisation where justified

Pronto Xi includes integrated applications, Business Intelligence capability and an API/integration platform, so existing capabilities should be assessed before bespoke development is assumed necessary.

Customisation can still be entirely appropriate where there is a genuine requirement and the business benefit justifies its implementation, testing and ongoing support.

What does a mature Pronto Xi environment look like?

A mature environment can still contain many spreadsheets.

The difference is where responsibility lies.

Critical transactions

Belong in governed operational systems.

Master data

Has an agreed system of record and owner.

Recurring management information

Comes from governed data and agreed definitions.

System-to-system data movement

Is automated where volume, recurrence and risk justify it.

Spreadsheets

Remain available for flexible analysis, modelling and exploration.

The target operating principle is:

One governed operational truth, with flexibility at the analytical edge.

A practical spreadsheet-dependency audit

Start with critical recurring spreadsheets rather than every file in the organisation.

For each one ask:

What business process or decision depends on it?

Determine materiality.

Where does the data come from?

Identify Pronto Xi, external systems and manual inputs.

What happens to the data?

Document:

  • formulas;
  • transformations;
  • mappings;
  • corrections;
  • manual judgement.

Is unique information stored here?

If yes, understand why it is not in a governed system.

Who owns it?

Every material workbook needs accountable ownership.

What happens if it disappears tomorrow?

This identifies dependency.

Why can't the requirement be met elsewhere?

Classify the root cause:

Reporting → Process → Data → Integration → Training → Genuine functional gap

Then select the simplest appropriate remedy.

Need Pronto Xi reporting, functional or integration expertise to work through this audit? Talk to SAAPRO.

A 90-day improvement approach

Days 1–30: Identify material dependency

Focus on recurring spreadsheets supporting:

  • finance;
  • inventory;
  • manufacturing;
  • procurement;
  • sales;
  • projects;
  • payroll;
  • executive reporting.

Rank each using:

Business impact × Recurrence × Control weakness

Days 31–60: Diagnose the cause

Classify each priority workbook:

  • analytical;
  • reporting workaround;
  • process workaround;
  • shadow system.

Then determine whether the root cause is:

  • reporting;
  • process;
  • data;
  • integration;
  • capability;
  • configuration;
  • genuine functional need.

Days 61–90: Fix a small number of high-value cases

Select two or three workarounds with measurable cost or risk.

Baseline:

  • preparation hours;
  • reconciliation hours;
  • re-keying;
  • users involved;
  • exceptions;
  • key-person dependency.

Then implement the simplest appropriate solution.

Success is not:

“We replaced Excel.”

Success is:

“We preserved the required business capability while reducing recurring work, risk or delay.”

Where SAAPRO fits

Recurring spreadsheet dependency can expose different capability gaps.

Depending on the root cause, an organisation may need a Pronto Xi Business Analyst, Functional Consultant, Application Analyst, Cognos/reporting specialist, integration developer or ERP Manager.

SAAPRO specialises in the Pronto Xi talent market and can help organisations identify the capability required where recurring workarounds indicate an ERP skills or resourcing gap. Contact SAAPRO to discuss your requirement.

Disclosure: SAAPRO is an independent Pronto Xi recruitment specialist and is not Pronto Software or an ecommerce implementation vendor.

Frequently Asked Questions

Common reasons include unmet reporting needs, data-quality concerns, manual processes, missing integrations, insufficient training, user familiarity and historical workarounds. The spreadsheet itself is often a symptom, so organisations should identify the underlying requirement before choosing a solution.

Yes. Pronto Xi’s Business Intelligence environment uses IBM Cognos Analytics and supports operational reporting, custom reports, dashboards, visualisations and scheduled reporting. The exact capability available to users depends on the organisation’s Pronto Xi environment, licensing and implementation.

Yes. Pronto Connect provides API capabilities for connecting Pronto Xi with external applications, and current Pronto documentation also describes webhooks and other integration mechanisms. Whether integration is justified depends on transaction volume, recurrence, cost, complexity and risk.

No. Spreadsheets remain useful for analysis, modelling and temporary work. The risk arises when they become uncontrolled operational systems, contain unique critical data or create recurring manual processes that duplicate governed systems.

Ask what would happen if the spreadsheet disappeared or produced the wrong result. Consider its business impact, frequency, manual manipulation, system-of-record role, key-person dependency and control environment.

Identify recurring critical spreadsheets, classify their purpose and diagnose the root cause. The appropriate solution may be better reporting, process redesign, data improvement, training, integration, configuration, or retaining the spreadsheet with stronger controls.

More questions?FAQs - Securing Pronto Resources for Your Next Project

Key Takeaways

  • ✓The important question is not “Why are people still using Excel?” It is “Why has this spreadsheet become necessary?”
  • ✓Recurring spreadsheet dependency usually points somewhere else: Reporting gap → Process gap → Data gap → Integration gap → Capability gap → Genuine functional need.
  • ✓Pronto Xi provides an integrated ERP environment, Business Intelligence using IBM Cognos Analytics, and integration through Pronto Connect, but technology alone does not remove workarounds.
  • ✓The objective is to keep critical transactions and master data in governed systems, produce recurring management information from governed data, and let spreadsheets remain where their flexibility genuinely adds value.
  • ✓That is a more useful measure of ERP maturity than counting how many Excel files employees use.

Sources · Last reviewed

  1. Pronto Xi ERP & analytics
  2. Analytics (Business Intelligence applications)
  3. Pronto Xi Business Intelligence overview (PDF)
  4. API Integration Platform (Pronto Connect)
  5. Pronto Software Education Learning Management System
  6. Pronto Xi Help (Pronto Plus)
Share with