ERPTwin
Menu
SDVA01VF04intermediate

Milestone Billing with a Billing Plan (No Delivery)

Billing independent of delivery: an installation project is invoiced in three milestones (30/40/30) from the sales order's billing plan. Each date becomes due when its milestone is reached — not before.

Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.

Digital twin

Docs
SAP DOCUMENTSVisualization of Milestone Billing with a Billing Plan (No Delivery). All information shown in the scene is also available in the caption and the panels next to it.
Demo data

01Order with a milestone billing plan

Order 10000320: ₹3,00,000, billed 30/40/30 at three milestones.

Business scenario

Demo Retail buys a ₹3,00,000 conveyor installation: 30% at contract signing, 40% when installed, 30% after acceptance.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

  1. 01

    Order with a milestone billing plan open in twin

    Order 10000320: ₹3,00,000, billed 30/40/30 at three milestones.

    Large projects are paid in stages that follow progress, not shipments.

  2. 02

    Contract signed — bill milestone 1 open in twin

    Milestone 1 reached: ₹90,000 invoiced.

    Order-related billing: the sales order, not a delivery, is the reference.

  3. 03

    Installation is half done open in twin

    The customer asks for the second invoice now, to use this year's budget. The installation is not finished.

    In project billing, milestones are often confirmed in PS (network activities) and released automatically — configuration dependent.

  4. 04

    Revenue before performance open in twin

    Invoicing before the milestone books revenue for work not yet done, which auditors will challenge.

    If prepayment is wanted, a down payment request is the correct tool, not an early milestone invoice.

  5. 05

    Installed — bill milestone 2 open in twin

    Installation complete: ₹1,20,000 invoiced.

    The billing plan shows billed and open dates at any time.

  6. 06

    Accepted — bill milestone 3 open in twin

    Customer acceptance: final ₹90,000 invoiced. Total ₹3,00,000.

    The order is now fully billed.

  7. 07

    Fully billed open in twin

    Three invoices from one order, each released by its milestone.

    Billing plans decouple billing from deliveries.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

This part of the process does not change stock.

Accounting impact

Milestone invoice — contract signing

Typical

Contract signed — bill milestone 1

  • Dr Customer receivable₹90,000
  • Cr Revenue — installation services (ERL)₹90,000

Order-related billing from a billing plan date; no delivery or goods issue is involved.

Milestone invoice — installation

Typical

Installed — bill milestone 2

  • Dr Customer receivable₹1,20,000
  • Cr Revenue — installation services (ERL)₹1,20,000

Order-related billing from a billing plan date; no delivery or goods issue is involved.

Milestone invoice — acceptance

Typical

Accepted — bill milestone 3

  • Dr Customer receivable₹90,000
  • Cr Revenue — installation services (ERL)₹90,000

Order-related billing from a billing plan date; no delivery or goods issue is involved.

Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.

Movement type

This flow spans several documents rather than a single movement type.

Bills projects and long-running services in stages agreed with the customer, independent of deliveries.

Transactions & Fiori apps

  • VA01 — Sales Order with Billing Plan
  • VF04 — Billing Due List
  • VF01 — Create Billing Document
  • Create Billing Documents

Differences by SAP version

Billing plans per item category; milestone link to PS.

Configuration

  • Billing plan types

    Typical

    Milestone (e.g. 01) and periodic (e.g. 02) — typical delivered examples.

  • Milestone release from PS

    Configuration dependent

    Network/WBS milestones can remove billing blocks automatically.

Prerequisites

  • Item category with billing plan
  • Billing plan type (milestone or periodic)
  • Date categories with billing blocks for milestones

Master data

Customer
Payment terms per milestone invoice.

Organizational structure

  • Sales area 1000/10/00

Tables

TableDescription
FPLA / FPLTBilling plan and dates

Integration

  • FIReceivable and revenue per milestone invoice.

Common errors

  • “Milestone not in the billing due list”

    Likely causes: Billing block not removed; Date in the future

    Where to look: Billing plan tab of the item

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

  1. CHECK 1

    Due list

    • Billing block on the date?
    • Billing date reached?

Interview questions

  • What billing plan types exist?

    Milestone billing (amounts or percentages billed when milestones are reached, often linked to project milestones) and periodic billing (the same amount at regular intervals, e.g. monthly rent). Both are order-related billing without deliveries.

Quiz

Q1 · Multiple choice

What is milestone billing based on?

References

  • SAP SE — SAP Help Portal: Billing Plans (source)
  • SAP SE — SAP Help Portal: Milestone Billing (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history

VersionChange
1.0.0Initial version.