🏠 Home PTP Tower Architecture 📝 ADA Editor ↗
IAO Architecture

PM-150 — Enable Payment

Architecture Document (TOGAF BDAT)

Procure To Pay (PTP) Tower
Capability PM-150 · PM Procure Materials and Services (Direct and Indirect)

IAO Program · R1 – R5
Generated: May 2026
Sajiv Francis

IAO Architecture Pipeline — Intel Confidential

Page 1↑ Back to TOCPM-150 — Enable Payment

Table of Contents

Page 2↑ Back to TOCPM-150 — Enable Payment

1. Executive Summary

This Architecture Document defines the Business, Data, Application, and Technology (BDAT) architecture for PM-150 Enable Payment within the IAO program. It includes 12 BPMN process diagram(s) in Section 3.

Dimension Value
Tower Procure To Pay (PTP)
Process Group PM Procure Materials and Services (Direct and Indirect)
Capability PM-150 - Enable Payment
Release R1 – R5
Total Systems 0
System Status 0 Deployed, 0 Developing, 0 EOL, 0 Pending IAPM
RICEFW Objects 26 Interfaces, 21 Enhancements

System nodes in architecture diagrams are IAPM-linked where matches exist (0/0 matched) — click any linked node to open its IAPM page. Diagrams require securityLevel: 'loose' for click events.

Page 3↑ Back to TOCPM-150 — Enable Payment

2. Business Context & Objectives

2.1 Classification

Level Value
L0 Tower Procure To Pay
L1 Process PM Procure Materials and Services (Direct and Indirect)
L2 Capability PM-150 - Enable Payment

2.2 Business Drivers

# Driver Description Strategic Alignment Priority
1 Procurement Process Standardization Standardize procurement processes across direct, indirect, and services on S/4 HANA + Ariba IDM 2.0 Procurement Excellence High
2 Supplier Collaboration Enhancement Enable digital supplier collaboration for consignment, subcontracting, and quality management Supplier Ecosystem High
3 Payment Automation Automate invoice verification, three-way matching, and payment execution Finance Efficiency Medium
4 PM-150 Process Migration Migrate Enable Payment business processes and 0 integrated systems from legacy to S/4 HANA target architecture IDM 2.0 Procurement High
Page 4↑ Back to TOCPM-150 — Enable Payment

2.3 Success Criteria

Metric Target Measure Baseline Owner
PO Cycle Time < 24 hours Requisition approval to PO dispatch to supplier 48 hours (current) Procurement Lead
Invoice Automation Rate > 80% Invoices processed without manual intervention (touchless) 45% (current) AP Manager
Supplier On-Time Delivery > 95% Supplier adherence to confirmed delivery date 89% (current) Supplier Management
PM-150 Migration Completeness 100% flow chains validated All 0 flow chains verified in target state 0% (pre-migration) Tower Architect

2.4 Companion Documents

Document Description
Business Architecture Included in this document (Section 3) — process flows from BPMN diagrams
This Document Full BDAT Architecture — Business + Data + Application + Technology
Page 5↑ Back to TOCPM-150 — Enable Payment

3. Business Architecture (TOGAF “B”)

3.1 Business Process Overview

This capability includes 12 business process(es) modeled in BPMN 2.0, covering the end-to-end workflow for PM-150 Enable Payment.

# Step ID Process Name Lanes Tasks Gateways
1 PM-150-010_Match_P.O.and_Goods_Receipt_Notice(3_Way_Match) PM-150-010_Match_P.O.and_Goods_Receipt_Notice(3_Way_Match) Invoice Resolution Team 3 4
2 PM-150-020_Process_Touchless_Invoice_Receipt PM-150-020_Process_Touchless_Invoice_Receipt Accounts Payable Accountant 3 2
3 PM-150-030_Receive_Invoice_from_Vendor PM-150-030_Receive_Invoice_from_Vendor Invoice Data Entry 1 0
4 PM-150-060_Process_Non-PO_Invoice PM-150-060_Process_Non-PO_Invoice Invoice Data Entry 5 2
5 PM-150-080_Match_Receipt_of_Goods_and_Services_to_Invoice_(2-way_match) PM-150-080_Match_Receipt_of_Goods_and_Services_to_Invoice_(2-way_match) Invoice Resolution Team 3 5
6 PM-150-090_Receive_Procurement_Card_Invoice PM-150-090_Receive_Procurement_Card_Invoice Procurement Agent 4 1
7 PM-150-100_Process_Procurement_Card_Invoice PM-150-100_Process_Procurement_Card_Invoice Procurement Agent 4 1
8 PM-150-130_Notify_Appropriate_Party PM-150-130_Notify_Appropriate_Party Payment Processor 5 0
9 PM-150-160_Propose_Vendor_Payment PM-150-160_Propose_Vendor_Payment Payment Processor 6 4
10 PM-150-170_Identify_Optimum_Timing_for_Payment PM-150-170_Identify_Optimum_Timing_for_Payment Accounts Payable Accountant 7 4
11 PM-150-200_Update_Financial_Records PM-150-200_Update_Financial_Records Payment Processor 3 1
12 PM-150_Enable_Payment PM-150_Enable_Payment Accounts Payable Accountant 1 5
Page 6↑ Back to TOCPM-150 — Enable Payment

3.2 Business Process Diagrams

BUSINESS ARCHITECTURE — 3.2.1 PM-150-010_Match_P.O.and_Goods_Receipt_Notice(3_Way_Match) — PM-150-010_Match_P.O.and_Goods_Receipt_Notice(3_Way_Match)

Swim Lanes: Invoice Resolution Team | Tasks: 3 | Gateways: 4

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Invoice Resolution Team"] n1["fa:fa-user Perform Quantity Block Webcycle"] n2["fa:fa-user Reject Invoice Back to Supplier"] n3[["fa:fa-cog Perform 3 Way Match"]] n4(["fa:fa-play Receive Materials"]) n5(["fa:fa-stop Communicated Invoice Rejection to Supplier"]) n6["Process Touchless Invoice Receipt"] n7["Receive Invoice from Vendor"] n8{{"fa:fa-code-branch Any Discrepancy / Mismatch?"}} n9{{"fa:fa-code-branch exclusiveGateway"}} n10{{"fa:fa-code-branch 3 way Match Successful?"}} n11{{"fa:fa-code-branch exclusiveGateway"}} end n3 --> n8 n7 --> n9 n9 --> n3 n4 --> n9 n1 --> n10 n2 --> n5 n11 --> n6 n8 -->|"Yes"| n1 n8 -->|"No"| n11 n10 -->|"Yes"| n11 n10 -->|"No"| n2 class n1 userTask class n2 userTask class n3 serviceTask class n4 startEvt class n5 endEvt class n6 startEvt class n7 startEvt class n8 gateway class n9 gateway class n10 gateway class n11 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.2 PM-150-020_Process_Touchless_Invoice_Receipt — PM-150-020_Process_Touchless_Invoice_Receipt

Swim Lanes: Accounts Payable Accountant | Tasks: 3 | Gateways: 2

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Accounts Payable Accountant"] n1["fa:fa-user Process Invoice Manually"] n2[["fa:fa-cog Execute Touchless Invoice Processing"]] n3[["fa:fa-cog Post Invoice Receipt"]] n4["Identify Optimum Timing for payment"] n5["Exception Handling"] n6{{"fa:fa-code-branch Execution Type?"}} n7{{"fa:fa-code-branch exclusiveGateway"}} end n2 --> n7 n3 --> n4 n1 --> n7 n7 --> n3 n6 -->|"Stop"| n1 n6 -->|"Auto Post"| n2 n5 --> n6 class n1 userTask class n2 serviceTask class n3 serviceTask class n4 startEvt class n5 startEvt class n6 gateway class n7 gateway
👁 View Diagram
Page 7↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.3 PM-150-030_Receive_Invoice_from_Vendor — PM-150-030_Receive_Invoice_from_Vendor

Swim Lanes: Invoice Data Entry | Tasks: 1 | Gateways: 0

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Invoice Data Entry"] n1[["fa:fa-cog Send Invoice to Readsoft"]] n2["Process invoice"] n3["A Create and Release Electronic Payment (EFT/DI)_Global"] n4["Invoice Received"] end n1 --> n2 n3 --> n4 n4 --> n1 class n1 serviceTask class n2 startEvt class n3 startEvt class n4 startEvt
👁 View Diagram
Page 8↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.4 PM-150-060_Process_Non-PO_Invoice — PM-150-060_Process_Non-PO_Invoice

Swim Lanes: Invoice Data Entry | Tasks: 5 | Gateways: 2

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Invoice Data Entry"] n1[["fa:fa-cog Initiate Single Approval Per Invoice"]] n2[["fa:fa-cog Send Invoice Information to Readsoft"]] n3[["fa:fa-cog Post Non-PO Invoice"]] n4[["fa:fa-cog Initiate Approvals in Ariba B and I"]] n5[["fa:fa-cog Initiate Approval in ECheck Tool"]] n6(["fa:fa-play Invoice Details Uploaded"]) n7(["fa:fa-play Invoice Created"]) n8(["fa:fa-play Invoice Created"]) n9(["fa:fa-play Invoice Received in Vistex"]) n10(["fa:fa-play IAC or BPO/IAC Invoice Received in Ariba"]) n11(["fa:fa-stop Check Exceptions"]) n12(["fa:fa-stop Invoice Sent Back to the Business Unit"]) n13["Post Invoice"] n14{{"fa:fa-code-branch Approved?"}} n15{{"fa:fa-code-branch exclusiveGateway"}} end n6 --> n1 n1 --> n14 n9 --> n3 n14 -->|"Yes"| n15 n4 --> n15 n15 --> n2 n7 --> n15 n8 --> n5 n5 --> n15 n10 --> n4 n3 --> n13 n14 -->|"No"| n12 n2 --> n11 class n1 serviceTask class n2 serviceTask class n3 serviceTask class n4 serviceTask class n5 serviceTask class n6 startEvt class n7 startEvt class n8 startEvt class n9 startEvt class n10 startEvt class n11 endEvt class n12 endEvt class n13 startEvt class n14 gateway class n15 gateway
👁 View Diagram
Page 9↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.5 PM-150-080_Match_Receipt_of_Goods_and_Services_to_Invoice_(2-way_match) — PM-150-080_Match_Receipt_of_Goods_and_Services_to_Invoice_(2-way_match)

Swim Lanes: Invoice Resolution Team | Tasks: 3 | Gateways: 5

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Invoice Resolution Team"] n1["fa:fa-user Approval Received"] n2["fa:fa-user Invoice Sent back to Supplier"] n3["fa:fa-user Review by AP Processor to Determine Re-trigger or Reject"] n4(["fa:fa-stop Invoice Sent back to Supplier"]) n5(["fa:fa-stop Post Invoice"]) n6["Receive Invoice from Vendor"] n7{{"fa:fa-code-branch Approval Determination?"}} n8{{"fa:fa-code-branch Request for Approval - Approved or Rejected?"}} n9{{"fa:fa-code-branch exclusiveGateway"}} n10{{"fa:fa-code-branch Re-trigger RFA?"}} n11{{"fa:fa-code-branch exclusiveGateway"}} end n6 --> n11 n7 -->|"Yes"| n8 n8 -->|"Approved"| n1 n2 --> n4 n1 --> n9 n7 -->|"No"| n9 n3 --> n10 n10 -->|"Reject"| n2 n11 --> n7 n9 --> n5 n8 -->|"Rejected"| n3 n10 -->|"Re-trigger"| n11 class n1 userTask class n2 userTask class n3 userTask class n4 endEvt class n5 endEvt class n6 startEvt class n7 gateway class n8 gateway class n9 gateway class n10 gateway class n11 gateway
👁 View Diagram
Page 10↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.6 PM-150-090_Receive_Procurement_Card_Invoice — PM-150-090_Receive_Procurement_Card_Invoice

Swim Lanes: Procurement Agent | Tasks: 4 | Gateways: 1

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Procurement Agent"] n1["fa:fa-user Identify Requirements Allowing Procurement Card Usage​"] n2["fa:fa-user Purchase Using Procurement Card"] n3["fa:fa-user Authorize CPC Card Holder"] n4[["fa:fa-cog Manage P-Card Purchases"]] n5(["fa:fa-play Item Needed to be Purchased"]) n6["Purchase Materials and Services"] n7["Payment Statement Sent"] n8["Enable Payment"] n9["GL/Cost Center Spends Actualized"] n10{{"fa:fa-code-branch exclusiveGateway"}} end n5 --> n1 n1 --> n3 n2 --> n10 n10 --> n4 n4 --> n7 n7 --> n9 n9 --> n8 n10 --> n6 n3 --> n2 class n1 userTask class n2 userTask class n3 userTask class n4 serviceTask class n5 startEvt class n6 startEvt class n7 startEvt class n8 startEvt class n9 startEvt class n10 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.7 PM-150-100_Process_Procurement_Card_Invoice — PM-150-100_Process_Procurement_Card_Invoice

Swim Lanes: Procurement Agent | Tasks: 4 | Gateways: 1

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Procurement Agent"] n1["fa:fa-user Identify Requirements Allowing Procurement Card Usage​"] n2["fa:fa-user Purchase Using Procurement Card"] n3["fa:fa-user Authorize CPC Card Holder"] n4[["fa:fa-cog Manage P-Card Purchases"]] n5(["fa:fa-play Item Needed to be Purchased"]) n6["Purchase Materials and Services"] n7["Payment Statement Sent"] n8["Enable Payment"] n9["GL/Cost Center Spends Actualized"] n10{{"fa:fa-code-branch exclusiveGateway"}} end n5 --> n1 n1 --> n3 n2 --> n10 n10 --> n4 n4 --> n7 n7 --> n9 n9 --> n8 n10 --> n6 n3 --> n2 class n1 userTask class n2 userTask class n3 userTask class n4 serviceTask class n5 startEvt class n6 startEvt class n7 startEvt class n8 startEvt class n9 startEvt class n10 gateway
👁 View Diagram
Page 11↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.8 PM-150-130_Notify_Appropriate_Party — PM-150-130_Notify_Appropriate_Party

Swim Lanes: Payment Processor | Tasks: 5 | Gateways: 0

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Payment Processor"] n1["Gather Approvals in APM"] n2[["fa:fa-cog Call Standard Events"]] n3[["fa:fa-cog Transfer MBC Data to Bank"]] n4[["fa:fa-cog Stop Generation of Payment Advise"]] n5["Send File for Remittance Advice"] n6(["fa:fa-stop Remittance Advice Sent"]) n7["Payment Program Run completed"] n8["Landing Page - PM-150-180 Create and Release Electronic Payment (EFT/DI)"] end n8 --> n2 n1 --> n3 n3 --> n5 n5 --> n6 n7 --> n1 n2 --> n4 n4 --> n7 class n2 serviceTask class n3 serviceTask class n4 serviceTask class n6 endEvt class n7 startEvt class n8 startEvt
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.9 PM-150-160_Propose_Vendor_Payment — PM-150-160_Propose_Vendor_Payment

Swim Lanes: Payment Processor | Tasks: 6 | Gateways: 4

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Payment Processor"] n1["Initiate Payment Process"] n2["Input Parameters Details for Payment"] n3["Execute Manual Payment Proposal"] n4["Review Payment Proposal"] n5["Involve Processor to Clear the Concerns"] n6[["fa:fa-cog Execute Scheduled Payment Proposal"]] n7["Create and Release Electronic Payment (EFT/EDI)"] n8["Identify Optimum Timing for Payment"] n9{{"fa:fa-code-branch Type?"}} n10{{"fa:fa-code-branch Errors Found?"}} n11{{"fa:fa-code-branch exclusiveGateway"}} n12{{"fa:fa-code-branch exclusiveGateway"}} end n8 --> n9 n1 --> n2 n2 --> n3 n3 --> n12 n9 -->|"Manual"| n1 n4 --> n10 n10 -->|"Yes"| n5 n9 -->|"Automatic"| n6 n5 --> n11 n10 -->|"No"| n11 n12 --> n4 n6 --> n12 n11 --> n7 class n6 serviceTask class n7 startEvt class n8 startEvt class n9 gateway class n10 gateway class n11 gateway class n12 gateway
👁 View Diagram
Page 12↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.10 PM-150-170_Identify_Optimum_Timing_for_Payment — PM-150-170_Identify_Optimum_Timing_for_Payment

Swim Lanes: Accounts Payable Accountant | Tasks: 7 | Gateways: 4

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Accounts Payable Accountant"] n1["Receive Base Line Date and Payment Terms"] n2["Block Invoice for Instalment Payment"] n3["Block Invoice for Custom Declaration Sheet"] n4["Block Invoice for Additional Documents"] n5["Unblock the Invoice - Manually or Automatically"] n6["fa:fa-user Block Invoice Manually"] n7[["fa:fa-cog Calculate Net Due Date"]] n8["Propose Vendor Payment"] n9["Process Invoice"] n10{{"fa:fa-code-branch Invoice Block needed or not ?"}} n11{{"fa:fa-code-branch exclusiveGateway"}} n12{{"fa:fa-code-branch Types of Block?"}} n13{{"fa:fa-code-branch exclusiveGateway"}} end n9 --> n1 n1 --> n7 n10 -->|"Yes"| n12 n4 --> n13 n6 --> n13 n10 -->|"No"| n11 n11 --> n8 n13 --> n5 n5 --> n11 n7 --> n10 n2 --> n13 n3 --> n13 n12 -->|"Custom Declaration Sheet"| n3 n12 -->|"Additional Documents"| n4 n12 -->|"Instalment Payment"| n2 n12 -->|"Manual Payment Block"| n6 class n6 userTask class n7 serviceTask class n8 startEvt class n9 startEvt class n10 gateway class n11 gateway class n12 gateway class n13 gateway
👁 View Diagram

BUSINESS ARCHITECTURE — 3.2.11 PM-150-200_Update_Financial_Records — PM-150-200_Update_Financial_Records

Swim Lanes: Payment Processor | Tasks: 3 | Gateways: 1

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Payment Processor"] n1[["fa:fa-cog Payment Sent to Bank Via MBC"]] n2[["fa:fa-cog Update Status in Manage Bank Messages App"]] n3[["fa:fa-cog Receive Acknowledgement File from Bank Via MBC"]] n4(["fa:fa-stop Payment Status Reconciled"]) n5["B Record Corrections - For Bank Rejections"] n6["A Record Corrections - APM"] n7{{"fa:fa-code-branch exclusiveGateway"}} end n1 --> n3 n3 --> n2 n2 --> n4 n5 --> n7 n6 --> n7 n7 --> n1 class n1 serviceTask class n2 serviceTask class n3 serviceTask class n4 endEvt class n5 startEvt class n6 startEvt class n7 gateway
👁 View Diagram
Page 13↑ Back to TOCPM-150 — Enable Payment

BUSINESS ARCHITECTURE — 3.2.12 PM-150_Enable_Payment — PM-150_Enable_Payment

Swim Lanes: Accounts Payable Accountant | Tasks: 1 | Gateways: 5

Legend: ● Start · ● End · User Task · Service Task · ◇ Gateway · Sub-Process

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'fontFamily': 'Segoe UI, Arial, sans-serif','primaryColor': '#e8f0fe', 'primaryBorderColor': '#0071c5','lineColor': '#37474F', 'secondaryColor': '#f5f8fc'}, 'flowchart': {'useMaxWidth': false, 'htmlLabels': true, 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 50}} }%% flowchart TD classDef startEvt fill:#4CAF50,stroke:#2E7D32,color:#000,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef endEvt fill:#C62828,stroke:#B71C1C,color:#fff,font-weight:bold,stroke-width:2px,rx:20,ry:20 classDef userTask fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1 classDef serviceTask fill:#FFF3E0,stroke:#E65100,stroke-width:2px,color:#BF360C classDef gateway fill:#FFF9C4,stroke:#F57F17,stroke-width:2px,color:#E65100 classDef subProc fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px,color:#4A148C subgraph lane_0["Accounts Payable Accountant"] n1["Validate Invoice"] n2(["fa:fa-play Invoice Submitted/Provided by Supplier or Internal BU"]) n3(["fa:fa-stop Financial Records Updated"]) n4{{"fa:fa-code-branch PO Based?"}} n5{{"fa:fa-code-branch GR based Check Box?"}} n6{{"fa:fa-code-branch exclusiveGateway"}} n7{{"fa:fa-code-branch Validation Errors?"}} n8{{"fa:fa-code-branch exclusiveGateway"}} n9[["fa:fa-folder-open Process Invoice"]] n10[["fa:fa-folder-open Record Corrections"]] n11[["fa:fa-folder-open Process Non-PO Invoice"]] n12[["fa:fa-folder-open Match Receipt of Goods and Services to Invoice (2-way match)"]] n13[["fa:fa-folder-open Match P.O. and Goods Receipt Notice (3 Way Match)"]] n14[["fa:fa-folder-open Identify Optimum Timing for Payment"]] n15[["fa:fa-folder-open Propose Vendor Payment"]] n16[["fa:fa-folder-open Create and Release Electronic Payment (EFT/EDI)"]] n17[["fa:fa-folder-open Notify Appropriate Party"]] n18[["fa:fa-folder-open Update Financial Records"]] n19[["fa:fa-folder-open Receive Invoice from Vendor"]] n20[["fa:fa-folder-open Resolve Discrepancies/ Exception Handling"]] n21[["fa:fa-folder-open Process Touchless Invoice Receipt"]] n22[["fa:fa-folder-open Process Touchless Invoice Receipt"]] end n9 --> n5 n12 --> n6 n13 --> n6 n4 -->|"Yes"| n9 n4 -->|"No"| n11 n14 --> n15 n15 --> n16 n17 --> n10 n16 --> n17 n10 --> n18 n18 --> n3 n19 --> n1 n2 --> n19 n1 --> n7 n20 --> n8 n21 --> n8 n8 --> n4 n11 --> n6 n7 -->|"Yes"| n20 n7 -->|"No"| n21 n6 --> n22 n22 --> n14 n5 -->|"No"| n12 n5 -->|"Yes"| n13 class n2 startEvt class n3 endEvt class n4 gateway class n5 gateway class n6 gateway class n7 gateway class n8 gateway class n9 subProc class n10 subProc class n11 subProc class n12 subProc class n13 subProc class n14 subProc class n15 subProc class n16 subProc class n17 subProc class n18 subProc class n19 subProc class n20 subProc class n21 subProc class n22 subProc
👁 View Diagram
Page 14↑ Back to TOCPM-150 — Enable Payment

3.3 Business Roles & Responsibilities

Role / Lane Processes Involved Description
Invoice Resolution Team PM-150-010_Match_P.O.and_Goods_Receipt_Notice(3_Way_Match), PM-150-080_Match_Receipt_of_Goods_and_Services_to_Invoice_(2-way_match),
Accounts Payable Accountant PM-150-020_Process_Touchless_Invoice_Receipt, PM-150-170_Identify_Optimum_Timing_for_Payment, PM-150_Enable_Payment
Invoice Data Entry PM-150-030_Receive_Invoice_from_Vendor, PM-150-060_Process_Non-PO_Invoice,
Procurement Agent PM-150-090_Receive_Procurement_Card_Invoice, PM-150-100_Process_Procurement_Card_Invoice,
Payment Processor PM-150-130_Notify_Appropriate_Party, PM-150-160_Propose_Vendor_Payment, PM-150-200_Update_Financial_Records,
Page 15↑ Back to TOCPM-150 — Enable Payment

3.4 Process Readiness

Process readiness for PM-150 — Enable Payment with automated risk flags from Config Tracker, User Story Tracker, RICEFW Object Tracker, ECA Object Tracker.

L2 Description L3 In-Scope Config User Stories RICEFW ECA Status
PM-150 Enable Payment 16/16 18% (3/17) 0F/0G/0 249/256 † 67/69 † 🔴

† RICEFW/ECA counts are shared across Sub-Tower pool — PM-150 shares with PM-040, PM-050, PM-070, PM-080, PM-090, PM-110. Object Tracker does not tag objects at L2 granularity; counts represent the combined sub-tower total.

Risk Flags for PM-150: - 🔴 Config Incomplete — Config at 18% (3/17)

📄 Full Process Readiness Detail → — per-capability breakdown with config items, RICEFW objects, transport analysis, and QA verification. For the comprehensive L1/L0 readiness rollup across all capabilities, see the L0 Tower Summary.

Data Sources: Config Tracker, User Story Tracker, S4 R3 Object Tracker, ECA R3 Object Tracker (Smartsheet exports). RICEFW and ECA objects are matched via Sub-Tower Name → L2 mapping. Generated .

Page 16↑ Back to TOCPM-150 — Enable Payment

4. Data Architecture (TOGAF “D”)

4.1 Data Flows — Source to Target

Data flows with DB platform details will be populated when tower architects complete the extended flow template columns (42-47) via the Input Portal.

4.2 Data Flow Diagrams

DATA ARCHITECTURE — Database-to-database data flows. Applications (blue) sit above their hosting databases (green cylinders). Thick arrows show data movement between databases.

4.3 Data Lineage

Data lineage (source schema/object → target schema/object mappings) will be populated when tower architects provide validated schema details via the Input Portal.

4.4 RICEFW Data Objects

RICEFW data objects (Reports and Conversions) will be auto-populated from the Smartsheet Object Tracker when matched to this capability.

4.5 Data Governance & Quality

Standard governance framework per Intel IDM 2.0 data management policies. Capability-specific governance details will be populated from the Input Portal when tower architects complete the Data Governance tab.

Concern Approach
Data Ownership Per-entity owners aligned to Procure To Pay tower organizational structure
Data Classification Per Intel corporate data classification policies
Data Retention Per Intel corporate retention policies
Data Quality Validated at source; reconciliation at target
Page 17↑ Back to TOCPM-150 — Enable Payment

5. Application Architecture (TOGAF “A”)

5.4 Component Overview

System Inventory

System IAPM ID Status

5.5 Development Object Inventory

Summary: 47 SAP, 26 Interfaces | RICEFW: 26 Interfaces, 21 Enhancements

5.5.1 SAP Development Objects

SAP platform objects (Reports, Interfaces, Conversions, Enhancements, Forms, Workflows) developed on S/4, MDG, or S/4 BOT:

Object ID Type Description Status Dev System Complexity
PTPI1657 Interface Interface to send Invoice PAID Status from CFIN to IP 10. Object Complete 01.S4 03.Medium
PTPI1533 Interface Pay@accept – Inbound Interface to fetch the values from FCE ODS to SAP S/4 HA… 10. Object Complete 01.S4 03.Medium
PTPI1428_IP Interface Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… 10. Object Complete 01.S4 04.Low
PTPI1428_IF Interface Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… 10. Object Complete 01.S4 03.Medium
PTPI0822_IP Interface Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… 10. Object Complete 01.S4 03.Medium
PTPI0822_IF Interface Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… 10. Object Complete 01.S4 04.Low
PTPI0821_IP Interface Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… 10. Object Complete 01.S4 03.Medium
PTPI0821_IF Interface Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… 10. Object Complete 01.S4 04.Low
PTPI0820_IP Interface Carbon Copy Invoice Integration from SAP S/4 to Ariba Network 10. Object Complete 01.S4 03.Medium
PTPI0820_IF Interface Carbon Copy Invoice Integration from SAP S/4 to Ariba Network 10. Object Complete 01.S4 04.Low
PTPI0819_IP Interface Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… 10. Object Complete 01.S4 03.Medium
PTPI0819_IF Interface Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… 10. Object Complete 01.S4 04.Low
PTPI0710_IP Interface S4 Manual Invoice Release Blocking functionality requires connection with GTT… 10. Object Complete 01.S4 03.Medium
PTPI0710_IF Interface S4 Manual Invoice Release Blocking functionality requires connection with GTT… 10. Object Complete 01.S4 04.Low
PTPI0692_IP Interface Custom program to send configurations from S4 system to Illumis 10. Object Complete 01.S4 03.Medium
PTPI0692_IF Interface Custom program to send configurations from S4 system to Illumis 10. Object Complete 01.S4 04.Low
PTPI0691_IP Interface Custom program to send the supplier master data from S4 system to Illumis. 10. Object Complete 01.S4 03.Medium
PTPI0691_IF Interface Custom program to send the supplier master data from S4 system to Illumis. 10. Object Complete 01.S4 04.Low
PTPI0685 Interface Custom program to send the Transactions (Invoices) from IF system to Illumis 10. Object Complete 01.S4 03.Medium
PTPI0470 Interface Payment Proposal after invoice posted from SAP S/4 HANA CFIN to Ariba 10. Object Complete 01.S4 03.Medium
PTPI0469 Interface Payment Remittance after payment posted from CFIN to IP/IF and from IP/IF to … 10. Object Complete 01.S4 03.Medium
PTPI0468 Interface Payment Status after payment is cancelled / Void from CFIN to IP / IF and Fro… 10. Object Complete 01.S4 02.High
PTPI0466_IP Interface Payment Remittance after payment posted from CFIN to IP/IF for Readsoft 10. Object Complete 01.S4 03.Medium
PTPI0466_IF Interface Payment Remittance after payment posted from CFIN to IP/IF for Readsoft 10. Object Complete 01.S4 04.Low
PTPI0388_IP Interface Custom program to send the Purchase order from SAP S4 system to Illumis 10. Object Complete 01.S4 02.High
PTPI0388_IF Interface Custom program to send the Purchase order from SAP S4 system to Illumis 10. Object Complete 01.S4 03.Medium
PTPE1687 Enhancement Automate Warranty Credit Memo Posting 10. Object Complete 01.S4 03.Medium
PTPE1656 Enhancement Enhancement to Update Invoice PAID Status from CFIN to IF & IP ARIBA Standard… 10. Object Complete 01.S4 03.Medium
PTPE1606_IP Enhancement Custom enhancement to edit the posted accounting document for Payment Term, B… 10. Object Complete 01.S4 03.Medium
PTPE1606_IF Enhancement Custom enhancement to edit the posted accounting document for Payment Term, B… 10. Object Complete 01.S4 04.Low
PTPE1606_CFIN Enhancement Custom enhancement to edit the posted accounting document for Payment Term, B… 10. Object Complete 01.S4 03.Medium
PTPE1440_IP Enhancement Custom program to generate a PDF printout of SAP self-billing invoices (ERS/C… 10. Object Complete 01.S4 03.Medium
PTPE1440_IF Enhancement Custom program to generate a PDF printout of SAP self-billing invoices (ERS/C… 10. Object Complete 01.S4 04.Low
PTPE1422_IP Enhancement Enhancement to Update Invoice PAID Status from CFIN to IF & IP ARIBA Standard… 10. Object Complete 01.S4 03.Medium
PTPE1422_IF Enhancement Enhancement to Update Invoice PAID Status from CFIN to IF & IP ARIBA Standard… 10. Object Complete 01.S4 04.Low
PTPE1139_IP Enhancement Custom Enhancements for Payment Proposal, payment remittance, payment status,… 10. Object Complete 01.S4 04.Low
PTPE1139_IF Enhancement Custom Enhancements for Payment Proposal, payment remittance, payment status,… 10. Object Complete 01.S4 04.Low
PTPE1139_CFIN Enhancement Custom Enhancements for Payment Proposal, payment remittance, payment status,… 10. Object Complete 01.S4 03.Medium
PTPE0732 Enhancement Pay@Accept Custom Program to release the invoice - SAP S/4 HANA IP and IF 10. Object Complete 01.S4 03.Medium
PTPE0471 Enhancement Review the auto reversal of payment documents, Reset clearing of invoice and … 99. Rejected/Cancelled/On Hold 01.S4 02.High
PTPE0371_IP Enhancement Standard BTE for Manage Supplier Line items to add the PO and Supplier name -… 10. Object Complete 01.S4 04.Low
PTPE0371_IF Enhancement Standard BTE for Manage Supplier Line items to add the PO and Supplier name -… 10. Object Complete 01.S4 04.Low
PTPE0371_CFIN Enhancement Standard BTE for Manage Supplier Line items to add the PO and Supplier name -… 10. Object Complete 01.S4 03.Medium
PTPE0318_IP Enhancement Custom program to block the vendor invoice based on the different business sc… 10. Object Complete 01.S4 04.Low
PTPE0318_IF Enhancement Custom program to block the vendor invoice based on the different business sc… 10. Object Complete 01.S4 03.Medium
PTPE0241_IP Enhancement Payment Term Mass change functionality in FBL1N Vendor Line item report 10. Object Complete 01.S4 03.Medium
PTPE0241_IF Enhancement Payment Term Mass change functionality in FBL1N Vendor Line item report 10. Object Complete 01.S4 04.Low

5.5.3 Interface Objects

Holistic view of all interface objects by L2 capability — includes ECA → S/4, S/4 → ECA, boundary system, and inter-platform interfaces with middleware and integration approach:

Object ID Description Source → Target Middleware Approach Status
PTPI1657 Interface to send Invoice PAID Status from CFIN to IP NA 10. Object Complete
PTPI1533 Pay@accept – Inbound Interface to fetch the values from FCE ODS to SAP S/4 HA… APIGEE 10. Object Complete
PTPI1428_IP Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… → S/4 APIGEE 10. Object Complete
PTPI1428_IF Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… → S/4 APIGEE 10. Object Complete
PTPI0822_IP Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… SAP Ariba Network → S/4 NA 10. Object Complete
PTPI0822_IF Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… SAP Ariba Network → S/4 NA 10. Object Complete
PTPI0821_IP Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0821_IF Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0820_IP Carbon Copy Invoice Integration from SAP S/4 to Ariba Network S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0820_IF Carbon Copy Invoice Integration from SAP S/4 to Ariba Network S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0819_IP Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… S/4 → OpenText MULESOFT 10. Object Complete
PTPI0819_IF Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… S/4 → OpenText MULESOFT 10. Object Complete
PTPI0710_IP S4 Manual Invoice Release Blocking functionality requires connection with GTT… S/4 → GTT (Custom Tracker) NA 10. Object Complete
PTPI0710_IF S4 Manual Invoice Release Blocking functionality requires connection with GTT… S/4 → GTT (Custom Tracker) NA 10. Object Complete
PTPI0692_IP Custom program to send configurations from S4 system to Illumis S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete
PTPI0692_IF Custom program to send configurations from S4 system to Illumis S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete
PTPI0691_IP Custom program to send the supplier master data from S4 system to Illumis. S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete
PTPI0691_IF Custom program to send the supplier master data from S4 system to Illumis. S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete
PTPI0685 Custom program to send the Transactions (Invoices) from IF system to Illumis S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete
PTPI0470 Payment Proposal after invoice posted from SAP S/4 HANA CFIN to Ariba S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0469 Payment Remittance after payment posted from CFIN to IP/IF and from IP/IF to … S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0468 Payment Status after payment is cancelled / Void from CFIN to IP / IF and Fro… S/4 → SAP Ariba Network NA 10. Object Complete
PTPI0466_IP Payment Remittance after payment posted from CFIN to IP/IF for Readsoft S/4 → Readsoft NA 10. Object Complete
PTPI0466_IF Payment Remittance after payment posted from CFIN to IP/IF for Readsoft S/4 → Readsoft NA 10. Object Complete
PTPI0388_IP Custom program to send the Purchase order from SAP S4 system to Illumis S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete
PTPI0388_IF Custom program to send the Purchase order from SAP S4 system to Illumis S/4 → Accounts Payable Recovery Tool SFT 10. Object Complete

5.5.5 Scheduling & Batch Objects

This section provides a holistic view of all batch processing and job scheduling — both internal SAP background jobs (SM37) and external orchestration (AutoSys, CWA).

5.5.5b External Scheduling Objects

External scheduling data is not yet available. Pending either AutoSys API access or a JIL export to the External Job Scheduling Tracker.

Scheduling and batch job data will be auto-populated once SAP background job extraction (TBTCO/TBTCP via ADT) is run against the development systems and AutoSys metadata is available. Run python scripts/fetch_sap_background_jobs.py to extract SAP internal jobs.

5.5.6 Boundary Application Dependencies

The following development objects integrate with boundary applications (external systems outside the S/4 HANA core):

Object ID Description Boundary Application Source → Target
PTPI1533 Pay@accept – Inbound Interface to fetch the values from FCE ODS to SAP S/4 HA… FCE Operational Data Services - METS Smart Order Management
PTPI1428_IP Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… Customs Tracker → S/4
PTPI1428_IF Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… Customs Tracker → S/4
PTPI0822_IP Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… SAP Ariba Network SAP Ariba Network → S/4
PTPI0822_IF Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… SAP Ariba Network SAP Ariba Network → S/4
PTPI0821_IP Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… SAP Ariba Network S/4 → SAP Ariba Network
PTPI0821_IF Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… SAP Ariba Network S/4 → SAP Ariba Network
PTPI0820_IP Carbon Copy Invoice Integration from SAP S/4 to Ariba Network SAP Ariba Network S/4 → SAP Ariba Network
PTPI0820_IF Carbon Copy Invoice Integration from SAP S/4 to Ariba Network SAP Ariba Network S/4 → SAP Ariba Network
PTPI0819_IP Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… OpenText S/4 → OpenText
PTPI0819_IF Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… OpenText S/4 → OpenText
PTPI0710_IP S4 Manual Invoice Release Blocking functionality requires connection with GTT… SAP ECC - Accounts Payable; Customs Tracker S/4 → GTT (Custom Tracker)
PTPI0710_IF S4 Manual Invoice Release Blocking functionality requires connection with GTT… SAP ECC - Accounts Payable; Customs Tracker S/4 → GTT (Custom Tracker)
PTPI0692_IP Custom program to send configurations from S4 system to Illumis Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
PTPI0692_IF Custom program to send configurations from S4 system to Illumis Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
PTPI0691_IP Custom program to send the supplier master data from S4 system to Illumis. Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
PTPI0691_IF Custom program to send the supplier master data from S4 system to Illumis. Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
PTPI0685 Custom program to send the Transactions (Invoices) from IF system to Illumis Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
PTPI0470 Payment Proposal after invoice posted from SAP S/4 HANA CFIN to Ariba SAP Ariba Network; SAP Ariba Invoicing S/4 → SAP Ariba Network
PTPI0469 Payment Remittance after payment posted from CFIN to IP/IF and from IP/IF to … SAP Ariba Network; SAP Ariba Invoicing S/4 → SAP Ariba Network
PTPI0468 Payment Status after payment is cancelled / Void from CFIN to IP / IF and Fro… SAP Ariba Network; SAP Ariba Invoicing S/4 → SAP Ariba Network
PTPI0466_IP Payment Remittance after payment posted from CFIN to IP/IF for Readsoft Readsoft - WorkCycle; Readsoft - Process Director Accounts Payable IP S/4 → Readsoft
PTPI0466_IF Payment Remittance after payment posted from CFIN to IP/IF for Readsoft Readsoft - WorkCycle; Readsoft - Process Director Accounts Payable IF S/4 → Readsoft
PTPI0388_IP Custom program to send the Purchase order from SAP S4 system to Illumis Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
PTPI0388_IF Custom program to send the Purchase order from SAP S4 system to Illumis Accounts Payable Recoveries (APR) S/4 → Accounts Payable Recovery Tool
Page 18↑ Back to TOCPM-150 — Enable Payment

5.6 Integration Patterns

Integration patterns will be populated when tower architects provide validated middleware and protocol details via the extended flow template.

6. Technology Architecture (TOGAF “T”)

6.1 Platform & Infrastructure

TECHNOLOGY / PLATFORM ARCHITECTURE — Platforms (green) host applications (blue). Thick arrows show platform-to-platform integration flows.

Platform Inventory

Platform inventory will be populated when tower architects provide validated technology platform details via the extended flow template.

6.2 SAP Development Object Status

Metric DEV QAS PRD
Transport Requests — — —
Custom Code Objects — — —
CDS Views — — —
Fiori Apps — — —
BAdIs / Enhancements — — —

6.3 NFRs & Design Principles

Category Requirement Target / SLA Priority
Performance Order/transaction processing within interactive SLA < 3 seconds for online transactions High
Availability Business-critical systems available during extended hours 99.9% (06:00-22:00 all time zones) High
Scalability Support seasonal and promotional volume spikes Handle 2x baseline transaction volume Medium
Recoverability Customer-facing systems recover within business impact window RPO < 30 min, RTO < 2 hours High
Data Volume Support transactional data growth from business expansion 10M+ documents/year Medium
Latency Near-real-time integration for order status updates < 30 seconds for status propagation Medium
Concurrency Support global user base across business functions 300+ concurrent users Medium

6.4 Security & Governance

Concern Approach Standard / Policy Owner
Authentication Single Sign-On (SSO) via Intel corporate Azure AD identity Intel IT Security Policy - Identity Management IT Security
Authorization Role-based access control (RBAC) with SAP authorization objects Intel SAP Security Standards - Role Design SAP Security Team
Data Classification All financial/operational data classified per Intel Data Classification Standard Intel Data Classification Policy Data Governance
Data Encryption (at rest) AES-256 encryption for SAP HANA database and file storage Intel Encryption Standard Infrastructure Security
Data Encryption (in transit) TLS 1.3 for all system-to-system and user-to-system communication Intel Network Security Policy Network Engineering
Network Segmentation SAP systems in dedicated network zones with firewall controls Intel Network Architecture Standard Network Security
API Security OAuth 2.0 / certificate-based authentication for all API integrations Intel API Security Guidelines Integration Architecture
Audit Logging Comprehensive audit trail for all data changes and user actions (SAP Security Audit Log) SOX Compliance / Intel Audit Policy Internal Audit
Certificate Management Automated certificate lifecycle management for system-to-system trust Intel PKI Standard Certificate Authority Team
Compliance SOX controls, export control (EAR/ITAR) screening, data privacy (GDPR) Intel Corporate Compliance Framework Compliance Office

6.5 ECA Development Object Status

Metric Count
ECA Objects (active) 69
ECA Complete 67 (97%)
ECA In Progress 2
ECA Rejected/Cancelled 2
Total Interface Dependencies 26

Data Source: ECA [R3] IDM Object Tracker (Smartsheet). Objects matched via Sub-Tower Name → L2 capability mapping. Rejected/cancelled/on-hold objects excluded from active counts.

Page 19↑ Back to TOCPM-150 — Enable Payment

7. Project Context

7.1 Project Roadmap & Go-Live Plan

ID Description FS TDD Build FUT Status
PTPI1657 Interface to send Invoice PAID Status from CFIN to IP 2025-08-08 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 2025-12-03 00:00:00 (100%) 4. Completed
PTPI1533 Pay@accept – Inbound Interface to fetch the values from FCE ODS to SAP S/4 HA… 2025-09-08 00:00:00 (100%) 2025-10-03 00:00:00 (100%) 2025-10-03 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI1428_IP Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… 2025-06-11 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI1428_IF Setting Up Inbound Interface from SPT tool/GTT(Global Trade and Tax) system t… 2025-06-11 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI0822_IP Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… 2025-02-21 00:00:00 (100%) 2025-04-11 00:00:00 (100%) 2025-04-11 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI0822_IF Ariba Invoice Integration through (CIG - Cloud Integration Gateway (Currently… 2025-02-21 00:00:00 (100%) 2025-04-02 00:00:00 (100%) 2025-04-02 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI0821_IP Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… 2025-03-15 00:00:00 (100%) 2025-05-15 00:00:00 (100%) 2025-05-15 00:00:00 (100%) 2025-12-03 00:00:00 (100%) 1. On Track
PTPI0821_IF Invoice Status Update from SAP S/4 to Ariba Network through CIG - Cloud Integ… 2025-03-15 00:00:00 (100%) 2025-05-15 00:00:00 (100%) 2025-05-15 00:00:00 (100%) 2025-12-03 00:00:00 (100%) 1. On Track
PTPI0820_IP Carbon Copy Invoice Integration from SAP S/4 to Ariba Network 2025-03-21 00:00:00 (100%) 2025-08-13 00:00:00 (100%) 2025-08-13 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI0820_IF Carbon Copy Invoice Integration from SAP S/4 to Ariba Network 2025-03-21 00:00:00 (100%) 2025-08-13 00:00:00 (100%) 2025-08-13 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track
PTPI0819_IP Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… 2024-12-13 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-10-09 00:00:00 (100%)
PTPI0819_IF Intel B2B – XML (3C7) Notify of Self Billing Invoice – Interface to send noti… 2024-12-13 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-10-09 00:00:00 (100%)
PTPI0710_IP S4 Manual Invoice Release Blocking functionality requires connection with GTT… 2025-04-18 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-10-09 00:00:00 (100%)
PTPI0710_IF S4 Manual Invoice Release Blocking functionality requires connection with GTT… 2025-04-18 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-10-09 00:00:00 (100%)
PTPI0692_IP Custom program to send configurations from S4 system to Illumis 2024-12-20 00:00:00 (100%) 2025-04-25 00:00:00 (100%) 2025-04-25 00:00:00 (100%) 2025-09-10 00:00:00 (100%)
PTPI0692_IF Custom program to send configurations from S4 system to Illumis 2024-12-20 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-09-10 00:00:00 (100%) 5. Not Dispositioned
PTPI0691_IP Custom program to send the supplier master data from S4 system to Illumis. 2024-12-20 00:00:00 (100%) 2025-04-25 00:00:00 (100%) 2025-04-25 00:00:00 (100%) 2025-09-10 00:00:00 (100%)
PTPI0691_IF Custom program to send the supplier master data from S4 system to Illumis. 2024-12-20 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-05-02 00:00:00 (100%) 2025-09-10 00:00:00 (100%)
PTPI0685 Custom program to send the Transactions (Invoices) from IF system to Illumis 2025-08-08 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2025-08-08 00:00:00 (100%) 2026-01-07 00:00:00 (100%) 4. Completed
PTPI0470 Payment Proposal after invoice posted from SAP S/4 HANA CFIN to Ariba 2025-11-05 00:00:00 (100%) 2025-12-03 00:00:00 (100%) 2025-12-03 00:00:00 (100%) 2025-11-05 00:00:00 (100%) 1. On Track

… and 27 more objects (see full Object Tracker)

Page 20↑ Back to TOCPM-150 — Enable Payment

7.2 RAID Log

RAID items will be auto-populated from the Smartsheet RAID log when matched to this capability.

7.3 Recommendations & Next Steps

# Category Recommendation Priority Owner Target Date Status
1 Architecture Complete extended flow attributes (Data Entity, Integration Pattern, Tech Platform) in Flows tab for full BDAT coverage High Tower Architect 2026-Q2 Open
2 Data Define data ownership and classification for all 0 flow chains to satisfy Data Architecture (TOGAF D) requirements Medium Data Architect 2026-Q3 Open
3 Testing Develop integration test scenarios covering all 0 flow chains for FUT/SIT readiness High Test Lead 2026-Q3 Open
4 Business Architecture Review and validate Business Architecture process steps against latest Signavio/BIC process models Medium Business Analyst 2026-Q2 Open
5 Security Complete security review for API integrations and data flows per Intel Security Architecture standards Medium Security Architect 2026-Q3 Open

PM-150 — Architecture Document (TOGAF BDAT) · Procure To Pay · Generated: May 2026

Page 21↑ Back to TOCPM-150 — Enable Payment
IAO Architecture Document | Intel IDM 2.0 | Generated by IAO Architecture Pipeline
↑ Back to TOC PM-150 — Enable Payment IAO Architecture Pipeline — Intel Confidential