Inside Delhi's P2P Settlement: Event-Driven Control Plane, Split Fees, Escrow-Aligned GL

Opening Insight: Delhi’s P2P Pilot, Escrow, and Rules-as-Software

Delhi’s P2P pilot is the right kind of pressure test: retail‑scale trading running on infrastructure built for centralized settlement. What’s new is not the trading itself but the operating model behind it: uniform 15‑minute, MDM‑validated intervals; RBI‑compliant escrow as the cash spine; and explicit split participation fees (INR 0.21/kWh per side) treated as policy, not spreadsheet logic.

All three need to be encoded as rules‑as‑software and streamed end‑to‑end into ETRM, billing, credit, and the GL. Ignore that shift and the costs show up quickly: margin leakage, P&L distortion, settlement variance, audit gaps, and close slippage.

Treat the shift as software and an event‑driven control plane eliminates those costs by separating energy from fees and UPERC/CERC charges, preserving audit‑ready lineage, and scaling across intra‑Delhi waivers and Delhi–UP trades.

What follows: a pragmatic architecture, core‑systems integration flows, and a phased roadmap with accountable owners and timelines; clear standards for interval hygiene and escrow‑to‑ledger controls; KPIs and trade‑offs; and FAQs on billing/GL mappings, network charges, eligibility, and RPO attribution. The destination is modernization without wholesale replacement, with applied AI reserved for exception triage and data quality, and outcomes that operators can measure (>98% STP, D+1 close, >99.5% invoice‑to‑ledger match).

Operational and Financial Fallout

Ignore the pilot’s mechanics and the costs stack quickly.

• Margin leakage — the INR 0.42/kWh fee (INR 0.21/kWh per side) isn’t split on bills, so costs fall into energy price and spreads erode.
• P&L distortion — RBI‑compliant escrow settles before GL auto‑postings for energy/fees, leaving ETRM and ledger out of sync and forcing rough accruals.
• Regulatory exposure — UPERC wheeling and CERC‑linked ISTS waivers/charges aren’t encoded, and certain trades’ RPO attribution lacks meter‑to‑invoice lineage.
• Audit findings — no traceable path from 15‑minute MDM blocks through P2P fee, UPERC/ISTS, and GST lines to GL accounts weakens audit‑ready lineage.
• Operational fragility — MDM gaps like the Day‑3 14:27 two‑block miss halted runs until 15:05, swelling exceptions and delaying prioritized P2P billing.
• Settlement variance — interval mismatches and weak event handling break the uniform 15‑minute Delhi↔UP mapping, triggering rebills and disputes.
• Counterparty exposure — no micro‑limits or escrow‑aware collections for many small participants increases disputes and write‑offs.
• Close slippage — manual onboarding, meter fixes, and reconciliations push past the 10:00–14:00 escrow‑to‑GL window, extending the monthly close.

Faster, Safer Trading Ops

Fixing billing, settlement, data, and controls converts high‑volume retail trades

into faster, safer, more profitable operations.

• Faster decisions and close: Uniform 15‑minute blocks validated in MDM and applied Delhi↔UP reduce disputes and rework.
• Lower operating cost: Straight‑through processing from meter to bill and auto GL postings shrink manual reconciliation.
• Accurate P&L and pricing: The INR 0.42/kWh fee split (INR 0.21/kWh per side) posts as distinct bill/GL lines, eliminating misposts and spread dilution.
• Reduced settlement variance: Event‑driven flows with idempotent controls and escrow‑to‑ledger alignment propagate clean, deduplicated entries.
• Stronger credit outcomes: Micro‑limits, escrow integration, and automated collections manage many small counterparties without ballooning exposure.
• Compliance by design: Rules‑as‑software for fee splits, Delhi waivers, UPERC wheeling, and CERC‑linked ISTS decisions, with audit‑ready lineage and immutable records.
• RPO attribution when eligible: Traceable meter‑to‑invoice data support attribution to the distribution licensee’s RPO where allowed.
• Operational resilience: Exception handling on interval gaps and versioned lineage let corrected blocks reflow without breaking bills or the GL.

Unified Control‑Plane Model

Adopt an event‑driven, policy‑coded, integrated end‑to‑end control‑plane that unifies fees, metering, settlement, and governance. It turns thousands of micro‑trades into clean bill lines and audit‑ready GL entries, cutting variance and leakage. The same model scales from intra‑Delhi waivers to Delhi–UP trades without rework.

• Interval and lineage first: Normalize 15‑minute smart‑meter reads in MDM, then stream to the platform, escrow, monthly bills, and GL with traceability from source to ledger.
• Rules‑as‑software: Encode the INR 0.42/kWh charge (INR 0.21/kWh per side), intra‑Delhi waivers, UPERC wheeling, ISTS per CERC decisions, GST on fees, and RPO attribution where allowed.
• Escrow to ledger: Net receivables/payables in RBI‑compliant escrow, separate participation fees from energy, and post idempotently into ETRM, billing, credit, and GL.
• Clear fee engine and billing: Show “P2P Transaction Fee (Buyer/Seller)” as distinct lines; don’t bury fees in price; map postings so expenses, revenues, and payables hit the right GL buckets.
• Uniform time‑blocks and exceptions: Keep 15‑minute blocks across Delhi↔UP; prioritize P2P billing; route meter gaps through exception handling so corrected blocks reflow automatically.
• Credit and participation controls: Verified‑credentials onboarding for <200 kW consumers and rooftop‑solar prosumers; micro‑limits, collections, and dispute workflows; penalties substituted/relaxed per pilot.

Architecture, Roadmap, and Org

Arcelian makes the pilot’s INR 0.42/kWh split fee, waivers, and 15‑minute settlement land cleanly on bills and the GL while preserving risk controls. The approach is an event‑driven control plane with escrow alignment, audit‑ready lineage,

Control‑Plane Architecture for Meter‑to‑Settlement: Components, Data Models, and Rule Governance

• Event‑driven, policy‑coded control plane governing meter‑to‑settlement.
• Governed data/lineage domains: smart meters/MDM, pricing, billing, and ledger/escrow, traceable from source to GL.
• Rules‑as‑software service : applies the consumer participation fee split (INR 0.21/kWh per side), intra‑Delhi waivers, UPERC‑governed wheeling, CERC‑linked ISTS waivers/charges, RPO attribution, and penalty substitutions.
• API/event integration with idempotent handlers to eliminate duplicates; versioned rules and lineage for audit.
• Security posture: protect blockchain/payment layers and PII with zero‑trust patterns, segregation of duties, and continuous monitoring.

ETRM and Core‑Systems Integration: Flows, Escrow/GL Alignment, Interval Handling

• Stream uniform 15‑minute intervals, trade confirmations, and settlement states into ETRM, billing, credit, and GL.
• Enforce MDM validation before settlement; missing/estimated blocks are flagged and reflow via events.
• Use the blockchain‑based trust layer and RBI‑compliant escrow ; net receivables/payables with the fee separated from energy.
• Auto‑post GL entries with clear line items: P2P Transaction Fee (Buyer/Seller), UPERC wheeling, ISTS (per CERC), and GST; maintain ledger mappings.
• Idempotent posting and exception flows keep escrow‑to‑ledger alignment and prevent duplicate entries.

Roadmap: Phased Delivery with Owners and Timelines

• Onboarding readiness with verified‑credentials workflow; cross‑functional product owner for meter‑to‑settlement accountable for data quality and rules.
• Normalize 15‑minute intervals across metering, MDM, trading, billing, and GL — Owner: CIO/Head of Data; Timeline: 6–8 weeks.
• Implement per‑kWh fee engine and jurisdictional charge model — Owner: Head of Billing/CFO; Timeline: 4–6 weeks.
• Stand up RBI‑compliant escrow and straight‑through GL postings — Owner: Treasurer/Controller; Timeline: 4–6 weeks.
• Establish micro‑credit limits, dispute handling, and collections for many small participants — Owner: CRO/Middle Office; Timeline: 3–5 weeks.
• Codify RPO attribution, waivers, and penalty substitutions as a rules service — Owner: Regulatory/IT; Timeline: 3–4 weeks.

Operating Model, Roles, and Culture: Ownership, Skills/Training, Governance Alignment

• Name a product owner for meter‑to‑settlement; align Finance and IT on fee modeling, revenue recognition, and GL mappings.
• Middle Office sets micro‑counterparty credit policy with escrow‑aware exposure and dispute workflows.
• Schedulers and operations receive training on uniform 15‑minute standards, MDM hygiene, and exception playbooks.
• Risk validates escrow‑to‑ledger alignment, micro‑limits, and idempotent control effectiveness.
• Treat pilots as production‑grade: prioritized P2P billing, reversible changes, and documented lineage.

KPIs and Trade‑offs

Measurable outcomes and failure modes

• Interval normalization coverage: percentage of trades with validated 15‑minute MDM data before settlement; failure mode: settlements using estimated data.
• Idempotency effectiveness: duplicate event/posting rate approaching zero; failure mode: double‑posting in GL or escrow mismatches.
• Escrow‑to‑ledger reconciliation: daily auto‑recon success rate; failure mode: unreconciled balances or aging exceptions.
• Rules accuracy and auditability: percentage of transactions with versioned rule attribution and lineage; failure mode: rule drift or untraceable adjustments.
• Fee separation and recognition: correctness of P2P Transaction Fee (Buyer/Seller) accounting; failure mode: fee embedded in energy revenue.
• RPO attribution correctness and waiver application accuracy; failure mode: compliance exceptions or penalty leakage.
• Credit risk control: micro‑limit breaches and dispute cycle time; failure mode: exposure overruns or delayed collections.
• Throughput and latency: time from meter read to settled GL posting; failure mode: backlog or missed cycle cutoffs.
• Training and process adherence: completion rates and exception playbook usage; failure mode: operational errors due to knowledge gaps.

Key trade‑offs to manage

• Speed of onboarding vs. strength of verified‑credentials and KYC controls.
• Granular 15‑minute precision vs. system load and storage costs.
• Flexibility of jurisdictional rule changes vs. governance and audit stability.
• Automation of straight‑through processing vs. manual review for edge cases.
• Escrow friction and working capital impact vs. reduction in counterparty credit risk.

Pilot KPIs and Settlement Trade‑offs

KPIs:

• Settlement variance
• Close‑cycle speed
• Exception rates/queues
• Escrow‑to‑ledger alignment
• Clarity of risk attribution by trade/participant
• Audit‑ready lineage from smart meter/MDM to invoice and GL

Trade‑offs:

• Separate fee lines vs bury‑in‑price (clarity and GL accuracy win)
• Exception management vs blunt penalties (pilot substitutes/relaxes penalties)
• Uniform 15‑minute discipline vs added operational overhead (reduces disputes and variance)

Executive FAQs: Delhi P2P Pilot

How will fees show up on bills and in the GL?

The pilot charges INR 0.42/kWh, split INR 0.21/kWh per side. Bill it as P2P Transaction Fee (Buyer/Seller) apart from energy and any UPERC/ISTS lines. GL postings: Buyer Dr Expense  Transaction Fees; Cr Cash/Escrow. Seller Dr Cash/Escrow; Cr Other Income  Participation Fee Recovery (or netted). Keep the fee outside energy to avoid misposting.

Which network/transmission charges apply or are waived?

Inside Delhi, wheeling/network/open‑access are waived. For DelhiUP, apply UPERC wheeling and show Inter‑state Wheeling (UPERC). ISTS depends on CERC decisions: if waived, omit; if not, post ISTS Charges (CERC). Treat these beside, not inside, the participation fee.

How do clearing and settlement work, and what controls are expected?

Smart‑meter 15‑minute blocks are validated in MDM, then quantities land on the platform. The platform nets receivables/payables and settles via RBI‑compliant escrow, separating the per‑side fee. Bills ingest the statement and auto‑post to the GL. Risk should set micro‑credit limits and reconcile escrow‑to‑ledger with idempotent exceptions.

What interval standards must we enforce to avoid variance?

The pilot runs on uniform 15‑minute intervals across Delhi and UP. Settle only on MDM‑validated, gap‑free blocks; hold runs and republish if intervals are missing. This reduces disputes and close‑cycle slippage. Interval hygiene matters more than after‑the‑fact fixes.

Who can participate, how does RPO attribution work, and who owns the near‑term build?

Eligible participants are consumers under 200 kW and rooftop‑solar prosumers after DISCOM verification. Certain trades can be credited toward the distribution licensees RPO when the consumer is not obligated.

Near‑term builds:

• Billing/CFO  fee engine and jurisdictional charges (46 weeks)
• CIO/Data  interval normalization (68)
• Treasurer/Controller  escrow plus straight‑through GL (46)
• CRO/Middle Office  micro‑limits and collections (35)
• Regulatory/IT  codify RPO, waivers, and penalty substitutions (34)

Own the Meter‑to‑Settlement Shift

Delhis sandbox shows bilateral micro‑trades will stress fee handling, settlement, and controls; on legacy rails you invite leakage, P&L distortion, and compliance risk. Long term, trading operations must process thousands of 15‑minute blocks with clean

escrow‑to‑ledger alignment, transparent consumer participation fees of INR 0.42/kWh split INR 0.21 per side, and consistent treatment of UPERC wheeling and CERC‑linked ISTS outcomes.

Risk posture depends on micro‑credit limits, exception workflows, and audit‑ready lineage from smart meter and MDM to invoice and GL, enabling RPO attribution where eligible.

Ownership is non‑negotiable: finance stands up the per‑kWh fee engine and mappings, data/IT normalizes intervals, treasury implements RBI‑compliant escrow straight‑through, and middle office governs micro‑exposure and disputes.

Strategic takeaway: establish an event‑driven, rules‑as‑software control plane that codifies the fee split and waivers, streams interval and settlement events into ETRM, billing, credit, and GL, and moves the pilot pattern to scale without losing control.

Operationalize Delhi P2P Now

The Delhi sandbox exposes sharp gaps: split fees that must post cleanly to the GL, 15‑minute interval settlement via MDM, RBI‑compliant escrow tied to the ledger, micro‑limits for many small counterparties, jurisdictional waivers and RPO rules, and audit‑ready lineage. Arcelian turns those rules into operating software and controls that scale. Request a rapid pilot readiness assessment focused on consumer P2P trading—fees, trading mechanism, data lineage, and control‑plane design—and within two weeks you’ll know what to fix, what to keep, and what to build.

• Split fee lines and GL mapping → Fee and charge intelligence → Clean INR 0.21/kWh per‑side postings.
• 15‑minute MDM settlement and escrow alignment → Event‑driven integration → Uniform blocks, RBI‑compliant escrow linked to GL.
• Micro‑counterparty exposure → Risk and credit modernization → Micro‑limits, escrow‑aware exposure, and automated collections.
• Waivers, RPO, and lineage gaps → Controls and compliance → Codified UPERC/CERC, RPO, and audit‑ready provenance.

Process Optimization & Automation: Digital integration & interoperability

Operationalizing Delhi’s P2P pilot demands a modernization strategy that treats metering, ETRM, billing, escrow, and GL as peers on an event‑driven control plane. The integration decision points are clear: normalize 15‑minute intervals in the MDM as the canonical source of truth; propagate fee‑engine outputs ( INR 0.42/kWh split, INR 0.21/kWh per side) as explicit event attributes; enforce RBI‑compliant escrow alignment and idempotent GL posting with correlation keys. Jurisdictional logic (UPERC/CERC) should be encapsulated as policy modules bound to the same event stream so pricing, charges, and tax treatments remain audit‑ready and testable.

The objective is meter‑to‑invoice‑to‑ledger straight‑through processing with minimal reconciliation surface area.

A pragmatic integration roadmap sequences capability in thin, verify‑as‑you‑go slices: (1) establish a versioned, canonical “IntervalMeasured” event with clock/zone discipline and

interval completeness rules; (2) enrich at the edge with contract and counterparty references for the ETRM architecture; (3) apply the fee engine and credit controls; (4) post to RBI‑aligned escrow and GL using exactly‑once semantics and idempotent keys; (5) overlay UPERC/CERC policy handlers.

Use a pub/sub bus that guarantees ordering within meter-partitioned streams, standardize on correlation IDs, and maintain a deterministic mapping from event IDs to ledger entries to reduce settlement variance and P&L leakage.

Where AI or Agentic AI is employed, confine it to exception triage and data quality suggestions driven off the immutable event log, with maker‑checker controls and full lineage from front to back office.

Key trade-offs to resolve up front

• Extend the current stack vs. replace: prefer brownfield extensions that externalize integration and controls, deferring ETRM replacement.
• Synchronous APIs vs. asynchronous events: default to async for throughput; reserve sync for escrow confirmations and GL acknowledgments.
• Posting granularity: batch by 15‑minute slices for performance, but preserve per‑trade keys for reversals and audit.

This reinforces the blog’s thesis that interoperability—not wholesale system replacement—unlocks scalable, compliant P2P settlement in Delhi while delivering measurable outcomes: >98% STP on micro‑trades, D+1 close, and invoice‑to‑ledger match rates above 99.5%.

Frequently Asked Questions

How should the INR 0.42/kWh participation fee appear on invoices and in the general ledger?

Split the fee equally at INR 0.21/kWh per side and show it as distinct lines — “P2P Transaction Fee (Buyer)” and “P2P Transaction Fee (Seller)” — separate from energy and from any UPERC/ISTS charges. Keep GST on the fee where applicable. Example GL mappings: Buyer — Dr Expense: Transaction Fees; Cr Cash/Escrow. Seller — Dr Cash/Escrow; Cr Other Income: Participation Fee Recovery (or netted). Do not bury the fee in the energy price to avoid misposting and spread dilution.

Which network or transmission charges apply for intra‑Delhi and Delhi–UP trades?

Inside Delhi, wheeling/network/open‑access charges are waived. For Delhi–UP trades, apply UPERC wheeling and show it as a separate line such as “Inter‑state Wheeling (UPERC).” ISTS is contingent on CERC decisions: if waived, omit; if payable, post as “ISTS Charges (CERC).” Treat these charges alongside — not inside — the participation fee.

What should we do when 15‑minute smart‑meter blocks are late, missing, or corrected?

Settle only on MDM‑validated, gap‑free 15‑minute blocks. If intervals are missing, hold the run, re‑poll, and post after the corrected blocks

republish. Use exception handling with idempotent posting and versioned lineage so corrected intervals reflow automatically to bills and the GL without duplicates. This reduces disputes, settlement variance, and close‑cycle slippage.

Trend Watch: Delhi P2P pilot and event‑driven control plane

The Delhi P2P pilot is accelerating a structural shift to an event-driven control plane where policy is code and cash moves in lockstep with the ledger. Expect the template to outlive the DERC sandbox: 15-minute settlement anchored by smart meter MDM validation, explicit treatment of the INR 0.42/kWh fee as a split consumer participation fee ( INR 0.21/kWh per side), and RBI-compliant escrow that posts cleanly and idempotently into the GL. As UPERC wheeling charges and CERC ISTS waivers toggle, rules-as-software keeps pricing, tax, and RPO attribution consistent while maintaining audit-ready lineage across ETRM integration and digital operations.

What to operationalize next for energy trading modernization and AI in ETRM

• Escrow-to-ledger alignment as a first-class capability: drive “P2P Transaction Fee (Buyer/Seller)” as distinct events and GL lines, with correlation keys for reversals and automated risk analytics on micro-counterparties.
• Interval hygiene at scale: enforce gap detection and replay around MDM, using agentic assistants to predict missing blocks, triage exceptions, and contain settlement variance before it hits monthly bills.
• Regulatory volatility by design: codify UPERC/CERC outcomes so UPERC wheeling charges and any CERC ISTS waivers reprice instantly without burying fees in energy.

Firms that treat this as energy-IT housekeeping will trail; operators that industrialize rules, events, and escrow alignment will unlock >98% STP, D+1 close , and durable trust. The prize isn’t just cleaner invoices—it’s a defensible operating edge where meter-to-invoice-to-GL flows are programmable, compliant, and ready to scale prosumer growth.

Closing Insight

Delhi’s pilot is not a billing tweak but a control‑system reset: if rules become software and cash moves with the ledger, P2P volatility becomes manageable throughput, not operational drag.

Advantage will accrue to operators who encode UPERC/CERC outcomes and the INR 0.42/kWh participation fee ( INR 0.21/kWh per side) as event‑native policy, stream escrow‑to‑GL with idempotent postings, and enforce 15‑minute interval truth from MDM to invoice. Applied AI belongs at the edges—predicting missing blocks, triaging exceptions, and sharpening micro‑credit limits—so risk management is continuous and settlement variance collapses without sacrificing compliance or RPO attribution. The near‑term mandate is clear: name the meter‑to‑settlement product owner, harden interval hygiene, stand up escrow alignment, and ship the fee/charge model—converting legacy ETRM plumbing into a programmable, resilient fabric primed

to scale prosumer growth and close D+1 with confidence.

Partner with Arcelian

Arcelian helps operators operationalize Delhi’s P2P model—encoding the INR 0.42/kWh participation fee as INR 0.21/kWh per side, enforcing MDM‑validated 15‑minute intervals, aligning RBI‑compliant escrow to the GL with idempotent postings, and codifying UPERC/CERC rules—within an event‑driven control plane integrated to your ETRM, billing, credit, and ledger.

Expect clean fee lines and mappings, micro‑credit discipline, audit‑ready lineage, and measurable outcomes (>98% STP, D+1 close , >99.5% invoice‑to‑ledger match ) without wholesale replacement. Connect with our team to review your meter‑to‑settlement design and co‑shape a phased modernization plan that reduces variance, hardens compliance, and scales prosumer growth with confidence.