From procurement policy to a production-ready P2P control tower

A global manufacturer operates procurement through email, spreadsheets and different ERP workflows across business units. ASE captures the operating model, exposes control gaps, generates a unified application and connects it to the existing enterprise landscape.

Example project. The company, systems and figures are made up.

Book a guided build All example projects

The situation

Procurement spans twelve business units in four countries, each with its own approval matrix, tax treatment and exception habits. Requisition-to-payment visibility is limited, invoice holds accumulate from receipt gaps, purchase-order discrepancies and master-data errors, and internal controls are evidenced manually at period end.

The request

Create one governed experience for requesting, approving, receiving and paying for goods and services without replacing our core ERP platforms.

Systems involved

12 business units across four countries
SAP S/4HANA and Oracle ERP
Coupa for sourcing and supplier onboarding
Email and spreadsheet-based exception handling
Different approval and tax rules by entity
Limited requisition-to-payment visibility
Invoice holds caused by receipts, PO discrepancies and master-data errors

How it runs

Step by step

What ASE does at each stage and who approves it.

DiscoverHuman approval gate

Inputs

Procurement policies and delegation of authority
Approval matrices and entity tax rules
Standard operating procedures and ERP interface specs
Supplier rules, audit findings and workshop transcripts

Agent activity

Ingest policy, procedure and interface documentation across entities
Reconstruct the current-state requisition-to-payment process model
Build a source inventory, control matrix and exception taxonomy

Human authority

Process owner confirms scope, policy authority and permitted entity variations.

Approval criteria: Scope, policy authority and entity variations are named and confirmed by the process owner.

Outputs

Current-state process model
Source and interface inventory
Control matrix
Exception taxonomy

Traceability created

Each control links to its originating policy clause
Each exception type links to the observed evidence

Hand-off: Confirmed process model and control matrix become the baseline for requirements.

Output

What ASE produced

Sample outputs from this project. All data is made up.

Current-state process map

Reconstructed requisition-to-payment flow with control and exception points.

REQUISITION → APPROVAL → PO → RECEIPT → INVOICE → MATCH → PAYMENT
entities: 12 · countries: 4 · variants detected: 9
control points: 23 (14 automated · 9 manual)
exception classes: receipt-missing, po-quantity, price-variance, vendor-master
break: BU-EU-03 approves outside delegation matrix (audit finding AF-118)

Approvals

Where people decide

Discover
Confirm scope, policy authority and entity variations
Approved by: Process owner
Define
Approve the requirements baseline and control set
Approved by: Procurement, finance and internal controls
Design
Approve integration and access patterns
Approved by: Architecture and security
Validate
Approve journey and control evidence
Approved by: Business owners and internal controls
Deploy
Authorize the controlled rollout
Approved by: Release owner

Solution

What got built

Target architecture

EXPERIENCE intake · approval workbench · match dashboard · exception queue
SERVICES rules service · match service · notification · audit event store
CANONICAL unified P2P model (requisition, PO, receipt, invoice, payment)
INTEGRATION SAP S/4HANA · Oracle ERP · Coupa · tax determination
GOVERNANCE delegation of authority · SoD · audit lineage · approval gates

How it traces back

Policy 4.2.1 → REQ-P2P-018 → CTL-07 → ADR-P2P-004 → TC-P2P-131 → REL-P2P-014

Targets

What a pilot would test

Goals to prove in a pilot, not client results.

Approval time
Illustrative baseline 3.8 days
Modeled pilot target 1.5–2.0 days
Target range depends on system and process complexity
Invoices requiring manual intervention
Illustrative baseline 42%
Modeled pilot target 25–30%
Potential outcome to validate
Status inquiries per 1,000 invoices
Illustrative baseline 95
Modeled pilot target 40–55
Potential outcome to validate
Control-to-test traceability
Modeled pilot target 100% for in-scope controls
Target range depends on system and process complexity