{
  "test_id": "ORCL.P2P.AP.PAY.ELECTRONIC",
  "scenario_name": "Electronic Payment",
  "application": "Oracle Fusion Cloud",
  "product": "Financials",
  "module": "Accounts Payable",
  "process": "Payments",
  "business_flow": "Procure-to-Pay",
  "scenario_type": "Positive / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/financials/accounts-payable/payments/electronic-payment/",
  "objective": {
    "intro": "The objective of this test is to verify that Oracle Fusion Accounts Payable can create and process an electronic supplier payment using a configured payment method, bank account and payment process profile.",
    "confirms": [
      "an eligible invoice or invoices can be selected for electronic payment",
      "the intended electronic payment method is applied to the payment",
      "the correct supplier bank account and disbursement bank account are used",
      "the payment amount and currency on the created payment match the source invoice(s)",
      "the payment reaches the expected status after processing",
      "a payment file or output is generated where the payment process profile is configured to produce one",
      "sensitive supplier banking details are not unnecessarily exposed in test evidence or reports"
    ],
    "scope_note": "This scenario validates the Oracle Fusion electronic payment creation and processing workflow, and any file or output generated within Oracle Fusion's test environment. It does not transmit funds to a bank or any external payment network — SyntraFlow executes this scenario as test automation against Oracle Fusion TEST/UAT environments only."
  },
  "preconditions": [
    "One or more eligible invoices exist and are approved for payment.",
    "The supplier is configured for electronic payment with a valid and active supplier bank account.",
    "A disbursement bank account is configured and active for the paying business unit.",
    "A payment process profile supporting the intended electronic payment method is available.",
    "The accounting period for the payment date is open.",
    "The test user has permission to create and process electronic payments."
  ],
  "test_data": [
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Supplier Bank Account",
      "example": "${SUPPLIER_BANK_ACCOUNT}"
    },
    {
      "field": "Disbursement Bank Account",
      "example": "${DISBURSEMENT_BANK_ACCOUNT}"
    },
    {
      "field": "Payment Method",
      "example": "${PAYMENT_METHOD}"
    },
    {
      "field": "Payment Process Profile",
      "example": "${PAYMENT_PROCESS_PROFILE}"
    },
    {
      "field": "Payment Currency",
      "example": "${PAYMENT_CURRENCY}"
    },
    {
      "field": "Invoice Number",
      "example": "${INVOICE_NUMBER}"
    },
    {
      "field": "Payment Amount",
      "example": "${PAYMENT_AMOUNT}"
    },
    {
      "field": "Payment Date",
      "example": "${PAYMENT_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign in to Oracle Fusion",
      "action": "Sign in to the Oracle Fusion environment using an authorised Accounts Payable test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion home page is displayed successfully and the user session is established.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Payables Payments",
      "action": "Navigate to the Payables work area and open the Payments task.",
      "test_data": "",
      "expected_result": "The Payments work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select the Eligible Supplier and Invoice(s)",
      "action": "Select the eligible supplier and one or more approved invoices to be paid electronically.",
      "test_data": "${SUPPLIER} / ${INVOICE_NUMBER}",
      "expected_result": "The correct supplier and invoice(s) are selected and available for payment.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select the Electronic Payment Method",
      "action": "Select the intended electronic payment method for the payment.",
      "test_data": "${PAYMENT_METHOD}",
      "expected_result": "The electronic payment method is applied to the payment.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select the Disbursement Bank Account",
      "action": "Select the disbursement bank account the payment will be issued from.",
      "test_data": "${DISBURSEMENT_BANK_ACCOUNT}",
      "expected_result": "The correct disbursement bank account is selected for the payment.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify the Supplier Bank Account Details",
      "action": "Review the supplier bank account associated with the payment to confirm it is valid and active.",
      "test_data": "${SUPPLIER_BANK_ACCOUNT}",
      "expected_result": "The supplier bank account displayed is valid, active and correctly associated with the supplier.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the supplier bank account detail panel and confirming its active status and ownership."
    },
    {
      "step_number": 7,
      "step_name": "Select the Payment Process Profile",
      "action": "Select the payment process profile that supports the intended electronic payment method.",
      "test_data": "${PAYMENT_PROCESS_PROFILE}",
      "expected_result": "The selected payment process profile is applied to the payment.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Review Payment Amount and Currency",
      "action": "Review the payment amount and currency calculated from the selected invoice(s).",
      "test_data": "${PAYMENT_AMOUNT} / ${PAYMENT_CURRENCY}",
      "expected_result": "The payment amount and currency match the source invoice(s).",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Create and Submit the Electronic Payment",
      "action": "Create and submit the electronic payment for processing.",
      "test_data": "${PAYMENT_DATE}",
      "expected_result": "Oracle Fusion accepts the payment submission and begins processing it without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 10,
      "step_name": "Confirm the Resulting Payment Status",
      "action": "Review the payment record after processing to confirm its resulting status.",
      "test_data": "",
      "expected_result": "The payment reaches the expected status for a successfully processed electronic payment.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 11,
      "step_name": "Verify the Payment File or Output Where Applicable",
      "action": "Where the payment process profile is configured to produce a payment file or output, confirm it has been generated within Oracle Fusion.",
      "test_data": "",
      "expected_result": "A payment file or output record is created within Oracle Fusion for the processed payment, where applicable to the configured payment process profile. This confirms the file is created in Oracle Fusion's test environment — it does not confirm or imply that funds have been transmitted to a bank.",
      "validation_type": "business_assertion",
      "note": "This is a supporting business assertion for the scenario — file/output creation is verified only where the tested payment process profile is configured to produce one."
    },
    {
      "step_number": 12,
      "step_name": "Verify No Sensitive Bank Data Is Unnecessarily Exposed in Evidence",
      "action": "Review the captured test evidence and reports to confirm sensitive supplier banking details are masked or omitted where not required.",
      "test_data": "",
      "expected_result": "Test evidence and reports do not unnecessarily expose sensitive banking information such as full account or routing numbers.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — a correctly processed payment that also protects sensitive banking data is a passing test."
    }
  ],
  "expected_results": [
    "An electronic payment is successfully created against the selected eligible invoice(s).",
    "The intended electronic payment method is applied to the payment.",
    "The correct supplier bank account and disbursement bank account are used.",
    "The payment amount and currency match the source invoice(s).",
    "The payment reaches the expected status after processing.",
    "A payment file or output is generated where the payment process profile is configured to produce one, within Oracle Fusion's test environment.",
    "Sensitive banking details are not unnecessarily exposed in test evidence or reports."
  ],
  "validation_checkpoints": [
    "Electronic payment is created against the selected invoice(s).",
    "Intended electronic payment method is correctly selected.",
    "Correct supplier and disbursement bank accounts are used.",
    "Payment amount and currency are correct.",
    "Payment status correctly reflects successful processing.",
    "Payment file or output is created within Oracle Fusion where applicable.",
    "No sensitive bank information is unnecessarily exposed in reports or evidence."
  ]
}