5 Modules That Don't Belong in Your ERP: Why Suite Thinking Ruins Your Procurement

Five departments sit at the table. Each one has a wish list. HR wants skill management. Sales needs lead scoring. Administration demands compliant document archiving. The project manager insists on Kanban boards. The quality manager wants audit management with CAPA tracking. All five wishes end up in the same document: the ERP requirements catalogue. All classified as knockout criteria.

The result is something I see in tender after tender: a catalogue with 177 criteria, 131 of them classified as A-criteria — mandatory knockout requirements. That’s 74 percent, far above any reasonable benchmark. What starts as structured procurement ends as a wish concert that no single system can serve.

The requirements aren’t wrong. They’re in the wrong document. This architecture decision is a core topic in my ERP consulting for SMEs.

How Departments Hijack Procurement

The typical sequence: IT drafts a core ERP catalogue — financial accounting, procurement, production. Then the document goes on tour. Every department adds their requirements. And since nobody rates their own needs as secondary, almost everything becomes a knockout criterion.

What happens when a vendor fails a single A-criterion? They’re out. Not because their ERP is bad, but because their CRM module doesn’t do lead scoring at Salesforce level. Or because their document management doesn’t support 100-year archival. The departments don’t protect the quality of the selection with their A-criteria — they destroy it.

The way out is a clean architecture decision: What belongs in the ERP? What belongs in a specialist system? And where’s the interface?

HR — Three Wishes No ERP Fulfils

Workforce planning (HR-13), talent development (HR-14), skill management (HR-15) — all three classified as knockout criteria, all three with a risk score of 4. No mid-market ERP delivers these functions at the depth a modern HR department needs. SAP Business ByDesign manages master data and absences. Dynamics 365 handles onboarding workflows. Strategic talent management? Not even close.

Anyone who defines these three as knockout criteria isn’t tendering for an ERP — they’re tendering for Workday. Or SuccessFactors. Or Personio. ERP systems are transaction-oriented: calculate payroll, generate postings, charge cost centres. Talent management is relationship-oriented: identify potential, plan development, secure succession. Fundamentally different data models.

Recommendation: Downgrade HR-13 to HR-15 from A to B. Instead, as an A-criterion: “The ERP must provide a documented API for bidirectional exchange of personnel master data.”

CRM — In the ERP or With the ERP?

Salesforce didn’t become the market leader by being a good ERP module. HubSpot didn’t win 200,000 customers by doing warehouse management on the side. Yet tenders routinely demand lead management, opportunity tracking and campaign management as A-criteria in the ERP.

The critical question: Do you need CRM in your ERP or CRM with your ERP?

I distinguish three CRM maturity levels:

• Level 1 — Administrative: Contact database, interaction history, quote tracking. The ERP module is fine.
• Level 2 — Steering: Pipeline management, forecasting, sales reporting. Time to go hybrid.
• Level 3 — Strategic: Marketing automation, predictive analytics, account-based marketing. A specialist system is mandatory.

Writing Level 3 CRM depth as a knockout criterion into the ERP tender is like buying a van and demanding it also compete in Formula 1.

Recommendation: CRM functional depth as a B-criterion. API for customer master data synchronisation as an A-criterion.

DMS — Compliance Doesn’t Belong in the ERP

Public sector organisations have a special relationship with documents. GoBD, TR-RESISCAN, BSI baseline protection, long-term archiving spanning 10, 30, sometimes 100 years — these are legal obligations in Germany. And that’s exactly why they end up as A-criteria in the ERP catalogue.

But ERP systems are transaction-oriented, not document-oriented. No Tier-1 ERP delivers a full-featured DMS natively. SAP has ArchiveLink — an interface, not a DMS. Dynamics uses SharePoint — fine for collaboration, not for compliant long-term archiving. The specialists — d.velop, ELO, DocuWare — have been focused on document management for decades.

For public sector tenders, BSI baseline protection alone — tenant separation, encryption at rest, granular access rights, field-level logging — requires capabilities that no ERP module delivers without massive customisation. And massive customisation is the opposite of what makes an ERP implementation successful.

Recommendation: Remove DMS criteria from the ERP catalogue. As an A-criterion: “Integration with external DMS systems via CMIS, REST API or ArchiveLink.”

Project Management — Financial Yes, Operational No

The entire organisation has been using Jira for years. Then the ERP tender arrives, and the requirements catalogue demands multi-project management, resource planning, milestone tracking — all as A-criteria. Nobody plans to abandon Jira. But nobody distinguished between two fundamentally different worlds:

Financial PM belongs in the ERP: project budgets, cost centres, hourly rates, progress billing, project cost accounting. SAP PS, Dynamics 365 Project Operations and Oracle PPM are built for this.

Operational PM belongs in a specialist tool: task breakdown, sprints, Kanban boards, collaboration. Jira, Asana, Monday.com deliver a user experience no ERP can match. Force 200 developers to manage their sprint tasks in the ERP, and you’ll see workarounds on day one — and a quiet reintroduction of Jira within six months. Without an ERP interface, because nobody planned for one.

Recommendation: Financial PM stays as an A-criterion. Operational PM gets removed. Instead: “API for importing time entries and exporting project structures.”

Quality Management / ISO 9001 — The Counter-Question

Would your quality department accept a QM system that also happens to do accounting?

The question sounds absurd. But that’s exactly what a requirements catalogue demands when it defines QM as a knockout criterion in the ERP. Criterion ERP-31, risk score 4: document control, audit management, CAPA processes, complaint management, supplier evaluation — all in the ERP.

ISO 9001 requires a quality management system. It doesn’t require that system to live in the ERP. The standard is technology-agnostic. Whether it runs in SAP, Babtec or a well-configured SharePoint is irrelevant to the auditor.

The industry reality makes it even clearer: automotive suppliers (IATF 16949) need Babtec QSYS or iqs CAQ. Medical devices (ISO 13485) require Qualityze or MasterControl. Professional services get by with ConSense or a DMS with workflow. In no case is the ERP the right home.

Recommendation: Downgrade ERP-31 from A to B. As an A-criterion: “Bidirectional exchange of supplier, material and batch data with external QM systems.”

The Rule of Thumb

Five modules, one pattern. In every case, the same reversal applies:

• Functional depth (HR, CRM, DMS, PM, QM): Currently A-criterion in ERP → B-criterion or separate tender
• Interface capability (REST API, middleware, standard connectors): Currently not required → A-criterion in ERP
• Master data ownership in ERP (customers, suppliers, personnel): Currently implicitly assumed → A-criterion, explicitly stated

This reversal opens the vendor market instead of closing it. ERP systems that excel at finance and logistics can suddenly compete — even without a QM or DMS module. And those are often the better ERP systems, because they focus on their core.

The cost myth. “Multiple systems are more expensive than one!” Yes, more licences cost more. But: shorter implementation, fewer customisations, higher user acceptance, lower-risk updates. Total cost of ownership over five years is frequently lower — confirmed by the satisfaction studies from Trovarit.

Next Step

Five modules, five architecture decisions — and all of them need to be made before the tender goes out. I review your requirements catalogue for hidden suite constraints that limit the market and compromise quality.

→ Schedule a consultation — free of charge

→ Or read more first: AI as a Knockout Criterion in ERP Tenders