{
  "test_id": "ORCL.P2P.AP.PAY.VOID",
  "scenario_name": "Void 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/void-payment/",
  "objective": {
    "intro": "The objective of this test is to verify that an authorised Accounts Payable user can void an eligible supplier payment in Oracle Fusion Payables, and confirm the resulting effect on the payment and its related invoice.",
    "confirms": [
      "the selected payment is eligible to be voided and has not already been voided",
      "the void date is accepted",
      "the void reason is accepted and retained against the void transaction",
      "payment status correctly updates to Voided",
      "the related invoice balance and eligibility for further payment are updated correctly",
      "the original payment remains traceable in payment history rather than being removed",
      "accounting impact of the void is handled correctly where applicable"
    ],
    "scope_note": "This scenario does not claim that every downstream accounting, reconciliation or bank-file scenario is covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test scenarios."
  },
  "preconditions": [
    "Oracle Fusion Payments (Accounts Payable) is configured and available to the test user.",
    "An existing supplier payment exists and is eligible to be voided.",
    "The payment has not already been voided.",
    "The test user has the appropriate security/privilege to void payments.",
    "The accounting period intended for the void is open, or the void is otherwise permitted per period-close configuration.",
    "The invoice associated with the payment is available and traceable."
  ],
  "test_data": [
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Payment Number",
      "example": "${PAYMENT_NUMBER}"
    },
    {
      "field": "Payment Status",
      "example": "Issued — eligible for void"
    },
    {
      "field": "Payment Amount",
      "example": "${PAYMENT_AMOUNT}"
    },
    {
      "field": "Payment Method",
      "example": "${PAYMENT_METHOD}"
    },
    {
      "field": "Related Invoice",
      "example": "${INVOICE_NUMBER}"
    },
    {
      "field": "Void Date",
      "example": "${VOID_DATE}"
    },
    {
      "field": "Void Reason",
      "example": "${VOID_REASON}"
    },
    {
      "field": "Accounting Period",
      "example": "Open period, or a later period where void is permitted by configuration"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Search for the Existing Payment",
      "action": "Navigate to the Oracle Fusion Payments work area and search for the existing supplier payment to be voided.",
      "test_data": "${SUPPLIER} / ${PAYMENT_NUMBER}",
      "expected_result": "The correct payment is located and its current status is confirmed as eligible for void.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening search, entering the supplier or payment number, clicking Search and selecting the result."
    },
    {
      "step_number": 2,
      "step_name": "Open the Payment",
      "action": "Open the located payment to review its details.",
      "test_data": "",
      "expected_result": "The payment details page opens, showing payment amount, payment method and the related invoice.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select Void",
      "action": "Select the Void action for the payment.",
      "test_data": "",
      "expected_result": "The Void Payment page or dialog opens for the selected payment.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter Void Date",
      "action": "Enter the date the payment is to be voided.",
      "test_data": "${VOID_DATE}",
      "expected_result": "The void date is accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Void Reason",
      "action": "Enter the reason for voiding the payment.",
      "test_data": "${VOID_REASON}",
      "expected_result": "The void reason is accepted and retained against the void transaction.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Confirm Void",
      "action": "Confirm and submit the void.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the void request without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Payment Status",
      "action": "Confirm the payment's status following the void.",
      "test_data": "",
      "expected_result": "Payment status updates to Voided, with the void date and void reason correctly recorded.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Invoice Balance/Eligibility Updated",
      "action": "Confirm the balance and payment eligibility of the invoice associated with the voided payment.",
      "test_data": "${INVOICE_NUMBER}",
      "expected_result": "Invoice balance and eligibility for further payment are updated correctly to reflect the void.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 9,
      "step_name": "Verify Original Payment Remains Traceable in History",
      "action": "Confirm that the original payment record remains visible and traceable in payment history.",
      "test_data": "",
      "expected_result": "The original payment remains traceable, showing its Voided status and the linked void transaction, rather than being removed from history.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — a payment void must be traceable and must not silently remove financial history."
    }
  ],
  "expected_results": [
    "An eligible supplier payment voids successfully.",
    "Payment status updates correctly to Voided.",
    "Void date and void reason are correctly recorded.",
    "Invoice balance and payment eligibility are updated to reflect the void.",
    "The original payment remains traceable in payment history.",
    "Accounting impact of the void is handled correctly where applicable.",
    "No unexpected save errors occur.",
    "The voided payment does not silently disappear from history or reporting."
  ],
  "validation_checkpoints": [
    "Payment status becomes Voided.",
    "Void date is correctly recorded.",
    "Void reason is retained.",
    "Invoice balance/status is updated correctly.",
    "Invoice becomes eligible for further payment where applicable.",
    "Accounting impact is handled appropriately.",
    "Original payment remains traceable."
  ]
}