In Enterprise Resource Planning, Order-to-Cash (O2C) and Procure-to-Pay (P2P) are
two critical "mirror" processes that manage how money flows in and out of a business.
Order-to-Cash (O2C): The Sales Side
O2C refers to the entire lifecycle of a customer order, from the moment it is placed until the
payment is received and recorded. It focuses on revenue generation and inbound cash flow.
● Primary Objective: Fulfill customer orders efficiently and collect payment as quickly as possible.
● Key Stakeholders: Sales teams, fulfillment/warehouse teams, and Accounts Receivable (AR).
● ERP Process Steps:
Procure-to-Pay (P2P): The Purchasing Side
P2P refers to the process of acquiring goods or services from suppliers and paying for them. It
focuses on cost control, compliance, and outbound cash flow.
● Primary Objective: Ensure business gets what it needs at right price while managing expenses.
● Key Stakeholders: Internal department requesters, procurement teams & Accounts Payable (AP).
● ERP Process Steps:
Key Comparison
Feature Order to Cash Procure to Pay
Business Role Seller (Customer facing) Buyer (Supplier Facing)
Cash Flow Inbound (Revenue) Outbound (Expenses)
Financial Team Accounts Receivable Accounts Payable
Core Document Sales Order Purchase Order
Metrics / KPIs Days Sales Outstanding Days Payable Outstanding
(DSO) (DPO)
Project Management Methodologies
1. Agile
• Iterative, incremental approach — work is broken into short cycles called sprints (typically
2–4 weeks)
• Requirements evolve throughout the project based on continuous customer feedback
• Cross-functional teams work collaboratively; no rigid hierarchy
• Key ceremonies: Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective
• Deliverable at the end of each sprint is a working, potentially shippable product increment
• Change is embraced — backlog can be reprioritized at any time
• Best suited for: software development, product design, R&D — any project where
requirements are unclear or likely to change
• Risk is low per sprint; issues are caught and fixed early in the cycle
2. Waterfall
• Linear, sequential approach — each phase must be fully completed before the next
begins
• Phases are fixed: Requirements → Design → Development → Testing → Deployment →
Maintenance
• Detailed documentation is produced at every stage before moving forward
• Customer involvement is mainly at the beginning (requirements) and end (delivery)
• Change requests mid-project are costly and disruptive — requirements must be locked
upfront
• Works well when scope, timeline, and technology are well-understood and stable
• Best suited for: construction, manufacturing, government contracts, ERP implementations
with fixed specs
• Risk is high — bugs or wrong requirements discovered late in the cycle are expensive to
fix
3. ASAP (Accelerated SAP) methodology
• SAP's proprietary implementation methodology, specifically designed for SAP ERP
deployments
• Structured into 5 phases: Project Preparation → Business Blueprint → Realization →
Final Preparation → Go-Live & Support
• Heavily documentation-driven — each phase produces formal deliverables and sign-offs
• Business Blueprint phase is critical — all current and future business processes are
mapped and agreed upon
• Realization phase involves configuring the SAP system, building custom programs
(ABAP), and unit testing
• Final Preparation covers end-user training, data migration, cutover planning, and stress
testing
• Go-Live is a controlled event — typically a "big bang" cutover from legacy to SAP on a
fixed date
• Best suited for: large enterprises implementing SAP S/4HANA or SAP ECC with
complex, multi-module scope
BPM and BPR in ERP
Business Process Management (BPM)
• BPM is a systematic approach to continuously improving and optimizing business
processes within an organization.
• It is an ongoing, cyclical activity — processes are monitored, analyzed, and refined over
time without major disruption to existing operations.
• In ERP, BPM involves mapping current workflows, identifying inefficiencies, and making
incremental improvements to how the system is used.
• Tools like SAP Business Workflow or process mining tools help monitor and manage
processes in real time.
• Key focus: "How can we do what we already do — but better and faster?"
• Example: Tweaking the P2P approval workflow in SAP to reduce the number of approval
levels from 4 to 2, cutting cycle time
Business Process Reengineering (BPR)
• BPR is a radical, ground-up redesign of core business processes to achieve dramatic
improvements in performance, cost, speed, or quality.
• Unlike BPM, BPR does not improve existing processes — it questions whether those
processes should exist at all and rebuilds from scratch.
• In ERP implementations (especially SAP using ASAP methodology), BPR typically
happens during the Business Blueprint phase — where legacy processes are challenged
and replaced with SAP best practices.
• Involves significant organizational change: roles, responsibilities, and department
structures may be completely restructured.
• Key focus: "Why do we do it this way at all? Let's redesign it entirely."
• Example: A company that used manual purchase orders via email completely replaces
the process with a fully automated SAP MM procurement cycle with electronic approvals,
3-way matching, and vendor portals
Bullwhip Effect - What is it?
• The Bullwhip Effect is a supply chain phenomenon where small fluctuations in customer
demand at the retail end cause increasingly large swings in orders further up the supply
chain — at the distributor, manufacturer, and supplier levels.
How it happens — step by step
• A retailer notices a slight increase in customer demand and orders extra stock "just in
case" — adding a safety buffer.
• The distributor sees the retailer's inflated order and assumes demand is rising — orders
even more from the manufacturer.
• The manufacturer, seeing large orders from multiple distributors, ramps up production
significantly.
• The raw material supplier receives massive orders and over-produces.
• When actual consumer demand normalizes or drops, the entire chain is left with excess
inventory, idle capacity, and wasted resources
What is ERP? Importance of ERP
What is ERP?
• ERP stands for Enterprise Resource Planning — an integrated software system that
centralizes and manages all core business processes of an organization through a single
unified platform and database.
• Rather than having separate, siloed systems for finance, HR, procurement, sales, and
inventory, ERP brings all of these functions together so they share data in real time.
• Leading ERP systems include SAP S/4HANA, Oracle ERP Cloud, Microsoft Dynamics
365, and Tally (for SMEs).
• The foundation of ERP is a single source of truth — one central database that all
departments read from and write to, eliminating duplication and inconsistency.
Core modules in a typical ERP system
• Financial Accounting (FI) — general ledger, accounts payable, accounts receivable
• Controlling (CO) — cost centers, profit centers, internal reporting
• Materials Management (MM) — procurement, inventory, vendor management
• Sales & Distribution (SD) — order management, pricing, billing
• Human Capital Management (HCM) — payroll, recruitment, attendance
• Production Planning (PP) — manufacturing orders, capacity planning
• Quality Management (QM) — inspection, defect tracking
Importance of ERP
1. Integration — eliminates data silos; a sales order in SD automatically updates inventory
in MM and revenue in FI — no manual re-entry
2. Real-time information — management gets live dashboards and reports instead of
waiting for end-of-month summaries
3. Process standardization — ERP enforces best-practice workflows across all
departments, reducing errors and inconsistency
4. Regulatory compliance — built-in tax calculations (GST, VAT), audit trails, and financial
reporting standards (IFRS, Ind AS) are automatically enforced
5. Cost reduction — automation of routine tasks (invoicing, payroll, reordering) reduces
manual labor and human error
6. Scalability — as the business grows, new modules, plants, or company codes can be
added without replacing the core system
7. Better decision making — accurate, consolidated data enables leadership to make
faster, evidence-based decisions
8. Customer satisfaction — integrated O2C process means faster order processing,
accurate invoicing, and on-time delivery
GRC in ERP — Governance, Risk and Compliance
What is GRC?
• GRC stands for Governance, Risk Management, and Compliance — a structured
framework that ensures an organization operates ethically, manages risks proactively,
and adheres to legal and regulatory requirements.
• In the context of ERP (especially SAP), GRC is not just a concept — it is an embedded
module (SAP GRC) that automates and enforces controls directly within business
processes.
• The three pillars work together: weak governance increases risk, unmanaged risk leads
to non-compliance, and non-compliance signals governance failure.
1. Governance
• Refers to the policies, rules, and structures that guide how an organization is directed
and controlled.
• In ERP, governance ensures that the right people have the right access to the right data
— no more, no less.
• Enforced through role-based access controls (RBAC), approval hierarchies, and audit
trails.
• Example: Only the Finance Manager can approve payments above ₹10 lakhs in SAP —
enforced by system configuration, not just policy.
2. Risk Management
• The process of identifying, assessing, and mitigating risks that could disrupt business
operations or cause financial loss.
• ERP systems help by flagging Segregation of Duties (SoD) conflicts — where one person
has too much control over a process end-to-end.
• SoD example: The same employee should NOT be able to both create a vendor and
process a payment to that vendor — this is a classic fraud risk.
• SAP GRC Access Control module automatically scans for SoD violations and alerts
administrators.
3. Compliance
• Ensuring the organization meets all external legal, regulatory, and industry standards —
such as GST laws, IFRS/Ind AS accounting standards, SOX (Sarbanes-Oxley), or
GDPR.
• ERP enforces compliance by building regulatory rules into system workflows — e.g., GST
calculation is automatic in SAP, leaving no room for manual error or manipulation.
• Audit logs in ERP maintain a complete, tamper-proof record of every transaction —
critical during regulatory audits.