Phase 6: Invoicing & Print Formatting

Prerequisite Check: Phase 5 must be complete. We need: Billing Schemas producing billing documents (Phase 5, Steps 5.8–5.10), FI-CA Document Types ZI/ZR (Phase 2, Step 2.3), and the Account Determination mapping (Phase 2, Step 2.5). Billing calculates the math — this phase posts it to FI-CA and builds the customer-facing print document. Invoicing is the bridge between raw billing calculation and the formatted, mailable bill.

Section A: FI-CA Account Determination for Invoicing (Prerequisite Injection)

⚠️ Critical Prerequisite: Before executing EA19 (Invoicing), the revenue mapping for billing/invoicing Posting Areas must be fully configured. While Phase 2 (Step 2.5) established basic Account Determination, the invoicing-specific posting areas require additional configuration defining exactly how billing line items map to G/L accounts during the invoicing posting. Without this, EA19 will abort with error FK 740 (“Account determination failed — no G/L account found for posting area”).

Step 6.1 — Configure Account Determination for Billing / Invoicing Posting Areas

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Account Determination: Posting Areas Overview

SAP displays a tree structure of Posting Areas. The key posting areas for IS-U Invoicing are:

2. Double-click on Posting Area 0100 (Billing).

Screen 3 — Posting Area 0100: Account Assignment Rules

3. Click New Entries to define account determination rules:

4. Click Save (Ctrl+S).

5. Navigate to Posting Area 0300 (Tax) → Click New Entries:

6. Click Save (Ctrl+S).

Revenue Account Architecture

FI-CA Subledger (Posting Area 0100)         FI-GL (via Reconciliation Key)
──────────────────────────────────         ──────────────────────────────

Billing Run (EA00) creates:                ZC Document (via FPG1):
  Debit: 1200000000 (AR Control)             DR: 1200000000 (AR)
  Credit: per Rate Type ───────────→          CR: 4100000000 (Rev-Res)
    ENRG → 4100000000 (Residential)           CR: 4200000000 (Rev-Com)
    DEMA → 4400000000 (Demand Rev)            CR: 4400000000 (Rev-Dem)
    CUST → 4500000000 (Cust Chg Rev)          etc.
    FUEL → 4600000000 (Fuel Adj Rev)
    TRAN → 4700000000 (Trans Rev)
    DIST → 4800000000 (Dist Rev)
    TAXS → 2300000000 (Tax Payable)
    TAXM → 2310000000 (Tax Payable)

Why This Step

Account Determination for Posting Areas is the granular mapping layer that assigns each billing line item type to exact G/L accounts. Phase 2 (Step 2.5) established the basic Main/Sub Transaction → G/L mapping. This step extends that mapping with:

1. Rate Type granularity — each charge type (energy, demand, customer charge, riders, taxes) posts to a distinct revenue account for regulatory reporting
2. TOU sub-detail — optionally splitting residential revenue into Peak/Off-Peak/Super Off-Peak revenue accounts for management reporting
3. Tax posting — routing tax collections to liability accounts (Tax Payable), not revenue accounts

Without this, invoicing would post all revenue to a single generic account, making PUCO-required regulatory filings impossible.

Key Configuration Notes

• ⚠️ The Posting Areas are separate from the basic Account Determination in Phase 2, Step 2.5. The basic mapping defines the fallback; the Posting Area mapping provides the granular override.
• All Debit postings go to the AR control account (1200000000). This is the FI-CA subledger’s receivable — it represents the customer’s obligation.
• The Credit accounts are revenue accounts (P&L) or liability accounts (tax payable). These must exist in Chart of Accounts CAOH (Phase 1).

Section B: Invoicing Process Configuration

Step 6.2 — Configure Invoicing Process (EA19 Rules)

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Invoicing Configuration: Overview

2. Click New Entries.

Screen 3 — New Entry: Invoicing Process Details

3. Click Save (Ctrl+S).

Part B: Invoicing Sequence Rules

Screen 4 — Invoicing Sequence: Processing Steps

4. Click New Entries to define the invoicing processing sequence:

5. Click Save (Ctrl+S).

Why This Step

Invoicing (EA19) is the posting engine that converts billing calculations into financial documents. Billing (EA00) produces a billing order with calculated amounts; invoicing takes those amounts and:

1. Posts them to the FI-CA subledger
2. Creates the customer-facing print document
3. Determines the payment due date
4. Evaluates whether late payment penalties apply from prior periods

Step 6.3 — Define Due Date Calculation Rules

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Due Date Rules: Table View

2. Click New Entries.

Screen 3 — New Entry: Due Date Rule Details

3. Click Save (Ctrl+S).
4. Repeat for each Due Date Rule:

Complete Due Date Rules

Why This Step

Due date calculation directly impacts cash flow and revenue collection. PUCO regulations specify minimum net days for utility invoices. The grace period ensures that a customer is not penalized for minor delays (e.g., weekend mail delivery).

Step 6.4 — Define Late Payment Penalty Configuration

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Penalty Rules: Table View

2. Click New Entries.

Screen 3 — New Entry: Penalty Rule Details

3. Click Save (Ctrl+S).

Complete Late Payment Penalty Rules

Why This Step

Late payment penalties are a regulated utility’s primary mechanism for encouraging timely payment. PUCO Rule 4901:1-10-21 sets the maximum allowable late payment charge for residential customers — the system cap must be configured to comply with this regulation.

Section C: Bill Print & Application Forms

Step 6.5 — Configure the Print Workbench (Bill Format)

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Application Forms: Table View

2. Click New Entries.

Screen 3 — New Entry: Application Form Header

3. Click Save (Ctrl+S) → click Edit Form to open the PDF designer.

Part B: Bill Layout — Mandatory Sections (PUCO Compliance)

⚠️ State regulatory requirements mandate specific information on every customer bill. The form layout must include all of the following sections:

Complete Application Forms

Why This Step

The printed (or PDF) bill is the primary touchpoint between the utility and the customer. Regulatory bodies like PUCO require specific information to be present, clearly formatted, and accurate. The Print Workbench uses SAP Adobe Forms to produce compliant bill layouts.

Key Configuration Notes

• ⚠️ PUCO 4901:1-10-22 requires that the bill clearly identify whether consumption was estimated. When EDM Replacement Value Procedures (Phase 4, Step 4.9) fill missing data, the affected intervals carry an estimation flag. The bill form must check this flag and print (E) next to estimated values.
• The 13-month usage history chart is a PUCO requirement designed to help customers compare current usage against the same period in the prior year.
• QR Code inclusion is a modern best practice that reduces call center volume by directing customers to the payment portal — reducing paper check processing.

Step 6.6 — Configure Bill Distribution Channels

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Distribution Channels: Table View

2. Click New Entries.

Screen 3 — New Entry: Channel Details

3. Click Save (Ctrl+S).
4. Repeat for each channel:

Complete Distribution Channels

Part B: Per-Customer Channel Assignment

SPRO Path: SPRO → SAP Utilities → Invoicing → Print Document → Distribution → Assign Distribution Channel to Correspondence Variant

5. Map the correspondence variants (from Phase 4, Step 4.2 — Contract Account Categories) to distribution channels:

6. Click Save (Ctrl+S).

Why This Step

Bill distribution must support multiple channels because customers have different preferences. The correspondence variant assigned to each Contract Account Category (Phase 4, Step 4.2) drives the automatic selection of distribution channels during invoicing.

Step 6.7 — Configure Invoicing Run (EA19) Parameters

SAP Screen Flow

Screen 1 — Invoicing: Selection Parameters

1. Execute EA19.
2. Enter selection parameters:

3. Click Execute (⏩).

Screen 2 — Invoicing Results Log

Post-Invoicing Verification

Common Invoicing Errors

Why This Step

EA19 is the production invoicing transaction. In production, it runs as a batch job immediately after EA00 (billing). The two are often chained: EA00 (billing run) → EA19 (invoicing run) → FPG1 (G/L transfer).

Phase 6 — Completion Checklist

🔗 Invoicing and print formatting are now configured. Proceed to Phase 7: Customer Service (Move-In / Move-Out) to define front-office operations.