Before the trigger
Eligible services can be unpublished. A wrong unapproved request can be cancelled with a reason; its history remains.
Services & revenue
Every PO line.
A traceable outcome.
Publish customer services to the right DUs, request revenue and review the actual items. Keep approved, pending and remaining value distinct.
For project service teams and eligible revenue reviewers.
01
Customer PO linesPO · Line · PO-Line · Quantity · Currency
Publish to a DU ↓
02
Published servicesService code → standard revenue milestone
Milestone closure or manual request ↓
03
Revenue eFlowCaptured items · Evidence · Revenue reviewers
Item decisions ↓
ApprovedReturnedRejected
A decision for each delivered item
Open the eFlow.
See exactly what you’re approving.
An eFlow can contain several PO lines. Select the eligible rows, inspect their evidence and record the decision with a reason.
EF-00044 · Installation acceptanceFictional example · DU-00125 · USD
Partially approved| PO | Line | PO-Line | DU code | Item | Qty | Value (USD) | Evidence | Status |
|---|---|---|---|---|---|---|---|---|
| PO-26014 | 10 | PO-26014-10 | DU-00125 | Installation | 1 | 1,200 | Acceptance.pdf | Approved |
| PO-26014 | 20 | PO-26014-20 | DU-00125 | Testing | 1 | 300 | Test report.pdf | Returned |
| PO-26014 | 30 | PO-26014-30 | DU-00125 | Extra visit | 1 | 150 | Site note.txt | Rejected |
Approved rows retain the decision. Returned rows can be corrected and resubmitted; rejected captured items are final.
Keep the measures separate
Published is not approved.
Pending is not earned.
The revenue dashboard follows monthly posting and the published pipeline. Reviewers are configured separately from WO approvals, including milestones that have no WO.
Explore the monthly chart ↗- Remaining
- Current published value less net approved revenue, floored per line. Pending requests are still inside this measure.
- Pending
- Requests awaiting a settled decision. This is a review workload, not approved revenue.
- Net approved
- Approved revenue less approved reversals, grouped by posting period and kept separate by currency.
When delivery or acceptance changes
Correct the record.
Keep the original decision.
After approval
Request a reversal for selected approved items or the remaining full eFlow. Keep the original item and supporting evidence.
After reversal review
An approved linked negative entry reduces net revenue in its posting period. Manual requests need explicit correction when milestones reopen.
MSDP records service revenue approval. Invoicing, payment collection, credit notes and ERP posting are future integration work.
Start with your source data
One customer PO.
A complete acceptance cycle.
Agree quantity basis, currency, item mapping and eligible revenue reviewers. Test publication, a partial decision, returned evidence and a reversal before wider use.
Plan the service pilot ↗Explore another part of the operation