Enterprise systems: ERP and CRM

In short

An ERP (Enterprise Resource Planning) system is one integrated, transaction-processing application suite over a single shared database that runs a company's internal functions - finance, procurement, inventory, manufacturing, sales, payroll - so that one business event updates every affected module at once. A CRM (Customer Relationship Management) system manages everything facing outward to the customer - leads, opportunities, quotations, campaigns, service tickets, contact history - and is the "front office" to ERP's "back office". Indian university syllabi (AICTE "Enterprise Systems"/"ERP" electives under IT and CSE, MIS papers) examine ERP modules, architecture, the implementation life cycle, BPR, and ERP-vs-legacy comparisons; CRM is examined as operational/analytical/collaborative types and the sales funnel. Industrially this is one of the largest employers of Indian IT graduates: TCS, Infosys, Wipro, Accenture, Capgemini, Deloitte, LTIMindtree and HCLTech staff thousands of SAP, Oracle, Salesforce and Dynamics consultants, and India-specific compliance (GST, e-invoicing, TDS, e-way bills) is built into every Indian ERP rollout.

Explained

What an enterprise system is, and why integration is the point

• Enterprise system: a single software system spanning functions, locations and legal entities, with a common database, a common data model and shared master data, replacing function-wise "islands of automation".
• The legacy problem: separate stores, accounts and sales systems meant the same customer existed three times with three spellings, stock figures disagreed, and month-end closing needed manual reconciliation.
• Integration benefit: one *business transaction* posts to all modules. A goods receipt simultaneously raises stock, creates a GR/IR liability, updates the purchase order status and feeds the General Ledger - no re-keying, no mismatch.
• Single source of truth: one definition of "customer", "material", "vendor" (master data) and one stream of transaction data (orders, invoices, payments).
• Best-practice embedding: ERP ships pre-built processes; adopting them is configuration, changing them is customisation. Vendors push "fit to standard" because customisation breaks upgrades.
• Historical line: inventory control → MRP (Material Requirements Planning, 1970s: what to buy/make and when) → MRP II (1980s: adds capacity, shop floor and finance) → ERP (1990s, term coined by Gartner) → ERP II / extended ERP (web-enabled, adds SCM, CRM, SRM, PLM, e-commerce) → cloud ERP (SaaS, multi-tenant, today's default for new deployments).

ERP modules and the core end-to-end processes

• Financial Accounting (FI): General Ledger, Accounts Receivable, Accounts Payable, Asset Accounting, banking, statutory reporting, period-end closing.
• Controlling / Cost Accounting (CO): cost centres, profit centres, product costing, internal orders, profitability analysis - management reporting, not statutory.
• Materials Management / Procurement (MM): purchase requisition, RFQ, purchase order, goods receipt, invoice verification, inventory valuation, physical stock.
• Sales and Distribution (SD): enquiry, quotation, sales order, availability check, delivery, picking/packing, shipment, billing.
• Production Planning (PP): BOM (bill of materials), routing, work centres, MPS, MRP run, production order, confirmation, backflushing.
• Quality Management (QM), Plant Maintenance (PM/EAM): inspection lots, preventive and breakdown maintenance orders.
• Human Capital Management (HCM/HR): organisation structure, personnel administration, time, payroll, PF/ESI/professional tax/TDS for India, now often a separate cloud suite (SuccessFactors, Workday, Darwinbox).
• Project System (PS), Warehouse Management (WM/EWM), Supply Chain (APO/IBP), Business Intelligence.
• Procure-to-pay (P2P): requisition → PO → goods receipt → invoice (three-way match of PO, GR and invoice) → payment → GL postings.
• Order-to-cash (O2C): enquiry → quotation → sales order → ATP check → delivery → goods issue (stock down, cost of goods sold up) → invoice (customer debited, revenue and GST credited) → receipt → clearing.
• Plan-to-produce: demand/forecast → MPS → MRP (explodes BOM, nets against stock and open orders) → planned order → production order → material issue → confirmation → goods receipt of finished goods.
• Record-to-report: sub-ledger postings → reconciliation → accruals and depreciation → period close → trial balance → statutory statements.

CRM: types, process and what it stores

• Definition: a strategy plus a system for acquiring, serving and retaining customers by consolidating every interaction into one customer record.
• Operational CRM - automates the customer-facing processes: SFA (sales force automation: leads, accounts, contacts, opportunities, quotations, forecasts), marketing automation (segmentation, campaigns, email/SMS/WhatsApp journeys, lead scoring), service automation (cases/tickets, SLAs, escalation, knowledge base, field service, contact-centre CTI).
• Analytical CRM - mines the collected data: churn prediction, RFM segmentation (recency, frequency, monetary), CLV (customer lifetime value), cross-sell/up-sell propensity, campaign ROI; runs on a warehouse/lakehouse, not on the OLTP tables.
• Collaborative CRM - shares the customer view across sales, service, dealers and partners, and across channels (call, email, web chat, store, app) - the basis of omnichannel service.
• Social and mobile CRM: social listening, WhatsApp Business and field-sales mobile apps - mainstream in Indian FMCG, insurance and real estate.
• Lead-to-cash funnel: lead → qualification (MQL→SQL) → opportunity with stage and probability → quotation → negotiation → order (handed to ERP) → fulfilment → invoice → service and renewal.
• Core objects: Lead, Account, Contact, Opportunity, Product/Price Book, Quote, Order, Case, Activity, Campaign - almost identical across Salesforce, Dynamics 365 and Zoho.
• Why CRM ≠ ERP: CRM optimises *revenue and relationship*, holds fuzzy, high-volume, low-value interaction data, and tolerates incomplete records; ERP optimises *resources and compliance*, and its data must balance to the rupee. Hence the standard integration: CRM owns the lead-to-quote, ERP owns the order-to-cash, with customer master, product/price master, order status, credit limit and invoice/payment flowing between them.

Architecture, deployment and technology

• Three-tier architecture: presentation (browser, GUI, mobile) → application tier (business logic, stateless, horizontally scalable) → database tier. SAP's classic model is SAP GUI → application servers with dispatcher/work processes → one database.
• Layered internals: data model, business-object/logic layer, workflow engine, reporting layer, integration layer (APIs, IDoc/EDI, message queue), security layer.
• Two-tier ERP: a heavy ERP at corporate headquarters plus a lighter/cloud ERP at a subsidiary or new plant, consolidated upward - common for Indian subsidiaries of multinationals.
• Deployment models: on-premise (owned licence, full control, capex, you upgrade); hosted/IaaS; SaaS multi-tenant cloud (one code line, many tenants, vendor upgrades on a fixed cadence, opex, configuration-only extensions); hybrid (ERP on-premise, CRM/HCM in cloud).
• In-memory and columnar: SAP HANA stores data column-wise in RAM so OLTP and analytics run on the same tables, removing many aggregate/index tables - the technical basis of S/4HANA.
• OLTP vs OLAP: ERP/CRM transactions are OLTP (short, write-heavy, normalised, ACID); reporting is OLAP (read-heavy, aggregated, star schema in a warehouse/BI layer).
• Extension and integration: REST/OData/SOAP APIs, webhooks, IDoc/EDI for B2B documents, middleware and integration platforms, event/message queues, RPA for legacy screens. Side-by-side extensions on a platform (SAP BTP, Salesforce Platform, Power Platform) keep the core clean - the "clean core" principle.
• Customisation ladder (cheapest and safest first): configuration → personalisation → extension fields → user exits/BAdIs → side-by-side app → core code modification (last resort).
• Security: role-based access control with authorisation objects, segregation of duties (the person who creates a vendor must not approve its payment), audit trail/change documents, encryption, SSO; audited under the Companies Act 2013 for accounting records and under the DPDP Act 2023 for personal data in CRM.

Implementation life cycle, methodology and risks

1. Pre-evaluation / needs analysis: business case, as-is process study, scope, make-or-buy.
2. Package selection: functional fit, India localisation (GST, TDS, e-invoice, e-way bill), total cost of ownership, vendor viability, partner availability, references.
3. Project preparation: sponsor, steering committee, core team of process owners + consultants, charter, budget.
4. Business blueprint / fit-gap: to-be processes documented; each gap decided as configuration, extension, process change or workaround.
5. Realisation: configure, build extensions, develop interfaces and reports, unit test, build conversion programs.
6. Data migration: extract → cleanse and de-duplicate → map → load master data (chart of accounts, materials, customers, vendors, BOMs) → load opening balances and open items → reconcile. Usually the single biggest source of delay.
7. Testing: unit → integration (full P2P/O2C runs) → UAT by business users → performance/load → security/role testing → mock cut-over rehearsals.
8. Training and change management: role-based training, manuals, key users as internal champions.
9. Go-live and cut-over: big-bang (all modules/sites at once - cheaper, riskier) vs phased (module-wise, site-wise or process-wise) vs parallel run (old and new together - safest, most expensive) vs pilot at one plant then roll out.
10. Post-implementation / hypercare and continuous improvement: stabilise, close defects, measure benefits, periodic upgrades.
11. Methodologies: SAP Activate (with best-practice content and Fit-to-Standard workshops), Oracle OUM/True Cloud Method, Microsoft Sure Step, Salesforce/Agile sprints; cloud projects are increasingly agile with fixed-cadence releases.
12. Why ERP projects fail: no top-management commitment, scope creep, over-customisation, dirty legacy data, under-estimated training, weak change management, mismatch between the package's embedded process and the company's reality, "big-bang on a weak team".
13. BPR (Business Process Re-engineering): redesigning processes to suit the software's best practice instead of bending the software - cheaper to run and upgrade but demands organisational change.
14. Benefits: data integrity, real-time visibility, faster period close, lower inventory and cycle times, statutory compliance, scalability, audit trail. Limitations: high licence + implementation cost (implementation often exceeds licence), long timelines, rigidity, vendor lock-in, dependence on consultants, business disruption at go-live, over-privileged users if roles are designed lazily.

Indian market, compliance and products

• Localisation that every Indian ERP must handle: GST (CGST/SGST/IGST, place of supply, HSN/SAC codes, input-tax credit, GSTR-1/3B/2B reconciliation), e-invoicing via the Invoice Registration Portal returning an IRN and QR code, e-way bill for goods movement, TDS/TCS under the Income-tax Act, Companies Act 2013 schedule III financial statements and depreciation, payroll statutes (PF, ESI, professional tax, gratuity, Payment of Bonus Act), SEZ/EOU and export documentation. Thresholds for mandatory e-invoicing have been lowered in stages (₹500 crore in Oct 2020 down to ₹5 crore turnover from Aug 2023) - verify the current threshold and the 30-day reporting window with the GST portal, as these notifications change.
• DPDP Act 2023: consent, purpose limitation, data-principal rights and breach notification apply directly to CRM contact and consent data from 13 May 2027 under the DPDP Rules 2025 (until then IT Act s.43A and the SPDI Rules 2011 govern).
• ERP products in India: SAP (ECC legacy, S/4HANA, Business One and GROW for mid-market), Oracle (E-Business Suite, Fusion Cloud ERP, NetSuite), Microsoft Dynamics 365 Finance & Operations / Business Central, Infor, Epicor; Indian and open-source: Tally Prime (dominant in small business accounting/GST), Marg, BUSY, ERPNext (open-source, Frappe framework, Python/MariaDB), Odoo, Ramco, Zoho Books/Inventory, plus IDMS-type sector systems.
• CRM products in India: Salesforce Sales/Service Cloud, Microsoft Dynamics 365 Sales, Zoho CRM, Freshworks (Freshsales/Freshdesk), HubSpot, LeadSquared (heavily used in Indian edtech, BFSI and real estate), SAP Sales/Service Cloud, Oracle CX.
• Public-sector and national systems with the same architecture: GeM for procurement, PFMS, IRCTC, GSTN, UPI-linked collections, IFFCO/NTPC/Indian Railways ERP rollouts, SAP/Oracle at most large PSUs.
• Job roles: functional consultant (FI/CO, MM, SD, PP, HCM), technical/ABAP or Apex developer, integration consultant, Basis/cloud administrator, data migration lead, security/GRC analyst, business analyst, CRM administrator, solution architect, support (L1-L3) engineer.

Key points

• ERP - integrated suite over one database automating internal, back-office resource processes across functions and sites.
• CRM - system of record for all customer-facing interactions: sales, marketing and service.
• Single source of truth - one master record per customer/material/vendor; eliminates reconciliation between departments.
• Master vs transaction data - master data is long-lived and shared; transaction data is event-based and time-stamped.
• MRP → MRP II → ERP → ERP II - the evolution from material planning to enterprise-wide, web-extended suites.
• Procure-to-pay - requisition→PO→GR→invoice→payment, validated by the three-way match.
• Order-to-cash - order→ATP check→delivery→goods issue→invoice→collection→clearing.
• BOM and MRP run - BOM explosion nets gross requirements against stock and open orders to give planned orders.
• Three-tier architecture - presentation, application, database; the application tier scales horizontally.
• Configuration vs customisation - configuration is switch-setting within the product; customisation is code change and the main cause of upgrade pain.
• Operational, analytical, collaborative CRM - automate, analyse, and share the customer view.
• RFM and CLV - the two standard analytical-CRM measures for segmentation and customer value.
• Implementation life cycle - selection → blueprint → realisation → data migration → testing → training → cut-over → hypercare.
• Go-live strategies - big-bang, phased, parallel run, pilot; risk falls and cost rises from big-bang to phased to parallel run, while a pilot limits exposure to one site before rollout.
• OLTP vs OLAP - ERP/CRM run short ACID transactions; reporting belongs in a BI/warehouse layer.
• Two-tier ERP - corporate ERP plus a lighter subsidiary ERP, consolidated upward.
• Segregation of duties - no single role may both create and approve the same financial object; an audit must-have.
• Indian localisation - GST with IRN e-invoicing, e-way bill, TDS/TCS, Companies Act 2013 reporting, PF/ESI payroll, DPDP Act 2023 for CRM data.
• Failure causes - over-customisation, dirty data, weak sponsorship and inadequate training, not technology.

Formulas and examples

Example 1 - MRP net requirement and BOM explosion. A pump maker must ship 500 pumps in week 10. Each pump's BOM has 2 bearings. On-hand bearings = 300, scheduled receipt = 200, safety stock = 150.

• Gross requirement for bearings = 500 × 2 = 1,000.
• Net requirement = 1,000 − 300 − 200 + 150 = 650 bearings.
• With a 5% expected scrap, planned order = 650 / 0.95 = 684.2 → 685 bearings, released to arrive before the week-10 build, offset by the supplier's lead time.

Example 2 - EOQ, reorder level and turnover. Annual demand D = 24,000 units, ordering cost S = ₹1,200/order, holding cost H = ₹40/unit/year, lead time 10 days, 300 working days, safety stock 300 units.

• EOQ = √(2 × 24,000 × 1,200 / 40) = √1,440,000 = 1,200 units.
• Orders per year = 24,000 / 1,200 = 20; ordering cost = 20 × 1,200 = ₹24,000.
• Average inventory (cycle) = 1,200 / 2 = 600; holding cost = 600 × 40 = ₹24,000 (equal, as EOQ requires). Total = ₹48,000/year.
• Average daily demand = 24,000 / 300 = 80 → Reorder level = 80 × 10 + 300 = 1,100 units.
• If COGS = ₹4.8 crore and average inventory value = ₹60 lakh, turnover = 4,80,00,000 / 60,00,000 = 8 times/year, i.e. 365/8 ≈ 45.6 days of inventory.

Example 3 - ERP business case, payback and ROI. Cloud ERP for a mid-size Indian manufacturer: subscription ₹36 lakh/year, one-time implementation ₹60 lakh, training ₹8 lakh. Benefits: inventory cut from ₹6 crore to ₹4.8 crore (carrying cost 18%/yr), 4 clerical posts redeployed at ₹4.5 lakh each, ₹6 lakh/yr saved on legacy AMC.

• Annual benefit = inventory saving 1,20,00,000 × 0.18 = ₹21.6 lakh + manpower 4 × 4.5 = ₹18 lakh + AMC ₹6 lakh = ₹45.6 lakh/year.
• Net annual benefit after subscription = 45.6 − 36 = ₹9.6 lakh/year.
• Year-1 investment = 60 + 8 = ₹68 lakh → Payback = 68 / 9.6 ≈ 7.1 years; 3-year TCO = 68 + 3 × 36 = ₹176 lakh, 3-year benefit = 3 × 45.6 = ₹136.8 lakh → the project does not pay back on these numbers. Decision: either the inventory reduction must be deeper, or a lighter-tier product chosen - the standard exam point that soft benefits (visibility, compliance, audit) must be quantified or the business case fails.

Example 4 - CRM pipeline, conversion and CLV. A SaaS firm's quarter: 4,000 leads, 900 qualified, 180 orders won, 320 lost, ₹54 lakh sales-and-marketing spend. Pipeline: 20 opportunities at ₹5 lakh/40%, 12 at ₹8 lakh/60%, 5 at ₹20 lakh/80%.

• Lead→qualified = 900/4,000 = 22.5%; qualified→order = 180/900 = 20%; win rate = 180/(180+320) = 36%.
• CAC = 54,00,000 / 180 = ₹30,000 per customer.
• Weighted pipeline = 20×5×0.40 + 12×8×0.60 + 5×20×0.80 = 40 + 57.6 + 80 = ₹177.6 lakh.
• CLV: ARPU ₹2,000/month, gross margin 70%, monthly churn 2.5% → lifetime = 1/0.025 = 40 months → CLV = 2,000 × 0.70 × 40 = ₹56,000. CLV/CAC = 56,000/30,000 ≈ 1.87 - below the 3× rule of thumb, so acquisition spend or churn needs fixing.

Example 5 - O2C posting with GST (intra-state). Sales order for 100 units at ₹1,200 each, GST 18%, cost per unit ₹800.

• Taxable value = ₹1,20,000; CGST 9% = ₹10,800; SGST 9% = ₹10,800; invoice total = ₹1,41,600.
• Goods issue posts: Cost of Goods Sold Dr ₹80,000 / Inventory Cr ₹80,000 (stock falls by 100 units).
• Billing posts: Customer Dr ₹1,41,600 / Sales Revenue Cr ₹1,20,000 / CGST payable Cr ₹10,800 / SGST payable Cr ₹10,800 - and triggers an IRN request to the e-invoice portal if the firm is above the notified turnover threshold.
• Gross margin = (1,20,000 − 80,000)/1,20,000 = 33.3%. If it were an inter-state sale, a single IGST ₹21,600 would replace CGST+SGST.

-- CRM-to-ERP style query: open sales orders per customer with credit exposure
SELECT c.customer_id,
       c.customer_name,
       SUM(so.net_value)                       AS open_order_value,
       c.credit_limit,
       c.credit_limit - SUM(so.net_value)      AS headroom
FROM   customer    c
JOIN   sales_order so ON so.customer_id = c.customer_id
WHERE  so.status IN ('OPEN','PARTIAL')
GROUP  BY c.customer_id, c.customer_name, c.credit_limit
HAVING SUM(so.net_value) > c.credit_limit   -- blocked for credit check
ORDER  BY open_order_value DESC;

Where it is used

• IT services and consulting: TCS, Infosys, Wipro, Accenture, Capgemini, Deloitte, LTIMindtree, HCLTech - implementation, rollout, AMS/support and upgrade projects for Indian and global clients; the largest fresher intake stream for ERP/CRM skills.
• Manufacturing and automotive: Tata Motors, Mahindra, Bajaj, Ashok Leyland and their tier-1 suppliers run SAP/Oracle for PP, MM, QM and plant maintenance with supplier portals and EDI.
• Banking, insurance and NBFCs: CRM (Salesforce, Dynamics, LeadSquared) for lead management and service, integrated with core banking and ERP for finance and procurement.
• Retail, FMCG and e-commerce: distributor management, stock and GST compliance in ERP; loyalty, campaigns and omnichannel service in CRM - for example FMCG field-sales apps writing orders straight into ERP.
• Public sector and government: GeM procurement, PFMS, GSTN, PSU ERP rollouts (NTPC, IOCL, Indian Railways), state transport and utility billing systems.
• MSMEs and startups: Tally Prime, Zoho One, ERPNext and Odoo give GST-compliant accounting, inventory and basic CRM at a fraction of large-suite cost; ERPNext work is a common Indian fresher entry point because the source is open.

Interview questions

• Q: What makes a system an ERP rather than a collection of applications? A: A single shared database and common data model, so one transaction updates every affected module in real time with no interface or re-keying between functions.
• Q: How do ERP and CRM differ, and how are they integrated? A: ERP runs internal resource and compliance processes, CRM runs customer-facing sales, marketing and service; they integrate by syncing customer and product masters and passing orders from CRM to ERP and order status, credit limit and invoice data back.
• Q: Explain the procure-to-pay cycle and the three-way match. A: Requisition → PO → goods receipt → invoice verification → payment; the three-way match checks that quantity and price agree across the purchase order, the goods receipt and the vendor invoice before payment is released.
• Q: What is the difference between configuration and customisation, and why does it matter? A: Configuration sets options the product already supports; customisation changes or adds code. Customisation costs more, must be retested at every upgrade, and is the main reason ERP upgrades become projects in themselves.
• Q: Difference between master data and transaction data? A: Master data (customer, material, vendor, GL account) is relatively static and shared by many transactions; transaction data (order, invoice, goods movement) records individual time-stamped business events.
• Q: Compare big-bang and phased go-live. A: Big-bang switches everything at once - lower cost and no interim interfaces, but one high-risk weekend; phased goes module or site at a time - lower risk, but longer, and it needs temporary interfaces to the legacy system.
• Q: Why do ERP implementations fail more often for business reasons than technical ones? A: The common causes are weak top-management sponsorship, scope creep, over-customisation, poor data cleansing and insufficient user training and change management - the software usually works as designed.
• Q: What are the three types of CRM? A: Operational (automates sales, marketing, service), analytical (segmentation, churn, CLV from collected data) and collaborative (shares one customer view across channels, departments and partners).
• Q: Why should you not run heavy reports directly on ERP production tables? A: It is an OLTP system tuned for short write transactions; large aggregating queries lock resources and slow business users, so reporting belongs in a BI/warehouse layer or an in-memory analytics engine.
• Q: What is segregation of duties in an ERP role design? A: Splitting conflicting authorisations so no single user can both initiate and approve the same financial action - for example creating a vendor and releasing its payment - which is a standard audit and fraud control.
• Q: Which India-specific requirements must an ERP meet? A: GST with CGST/SGST/IGST and place-of-supply logic, e-invoicing with IRN and QR code above the notified turnover threshold, e-way bills, TDS/TCS, Companies Act 2013 reporting and PF/ESI/professional-tax payroll; CRM personal data also falls under the DPDP Act 2023.
• Q: A sales team keeps its pipeline in spreadsheets despite a CRM licence. What would you do? A: Treat it as adoption, not technology: simplify required fields, embed CRM in the tools they already use (email, mobile, WhatsApp), auto-capture activity, make management reviews run only off CRM reports, and tie incentives to CRM-recorded data.

Common mistakes

• Equating ERP with accounting software, or calling any database-backed app an "ERP" - without cross-module integration on one database, it is not one.
• Thinking CRM is only a contact list; omitting analytical and collaborative CRM when the question asks for types.
• Listing module names (MM, SD, FI) without being able to walk one end-to-end process such as order-to-cash or procure-to-pay.
• Recommending heavy customisation to preserve existing habits, then being unable to explain the upgrade and testing cost.
• Ignoring data migration and cleansing in the implementation plan - in practice the largest schedule risk.
• Omitting the stock/COGS leg when asked what a goods issue posts, or forgetting that CGST+SGST applies intra-state while IGST applies inter-state.
• Arithmetic and unit slips in business-case sums: mixing lakh with crore, quoting a payback without the full TCO, or counting a one-time saving as recurring.
• Quoting specific GST e-invoicing thresholds or DPDP timelines as permanent - they are notified and have changed in stages, so state that they must be verified.

Related topics

REST APIs · API integration and middleware · E-commerce systems · Server-side web development · Database management systems and SQL · Software engineering: SDLC and project management