{
  "test_id": "ORCL.O2C.AR.RCP.LOCKBOX",
  "scenario_name": "Lockbox Receipt Processing",
  "application": "Oracle Fusion Cloud",
  "product": "Financials",
  "module": "Accounts Receivable",
  "process": "Receipts",
  "business_flow": "Order-to-Cash",
  "scenario_type": "Integration / Data Quality / Business Rule Testing",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/financials/accounts-receivable/receipts/lockbox-receipt-processing/",
  "objective": {
    "intro": "The objective of this test is to validate automated receipt creation and application from configured lockbox input data in Oracle Fusion Accounts Receivable — confirming that the input is correctly imported, the paying customer is correctly identified, transactions are correctly matched against open invoices or customer references, receipts are correctly created and applied, and any item that cannot be confidently processed is surfaced as a clearly classified exception rather than silently dropped or misapplied.",
    "confirms": [
      "the configured lockbox input is correctly imported into Oracle Fusion",
      "the expected number of receipts is created from the input data",
      "the correct paying customer is identified for each transaction",
      "each transaction is correctly matched to the intended invoice, customer reference or open item",
      "the correct amount is applied against the matched invoice(s)",
      "exceptions — unmatched, ambiguous, duplicate or invalid items — are correctly surfaced rather than silently accepted",
      "unmatched or partially matched items are handled according to configured matching and application rules",
      "the resulting batch or process status correctly reflects the outcome, including any unresolved exceptions"
    ],
    "scope_note": "This scenario validates the automated lockbox receipt path end-to-end — import, matching, creation, application and exception surfacing. A failed or exception-generating lockbox run is not automatically treated as an Oracle application defect; data, configuration and integration causes are considered first, consistent with SyntraFlow's failure classification approach."
  },
  "preconditions": [
    "A lockbox is configured for the bank and the relevant transmission format.",
    "Valid customer and transaction reference data is available in the input to exercise successful matching.",
    "Matching rules are configured for customer identification and transaction/invoice matching.",
    "The disbursement/remittance bank account associated with the lockbox is configured in Oracle Fusion.",
    "The test user or process has access to review lockbox processing results, created receipts and exceptions."
  ],
  "test_data": [
    {
      "field": "Lockbox",
      "example": "${LOCKBOX}"
    },
    {
      "field": "Transmission Format",
      "example": "${TRANSMISSION_FORMAT} — example or customer-configured format"
    },
    {
      "field": "Bank Account",
      "example": "${BANK_ACCOUNT}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Customer Account",
      "example": "${CUSTOMER_ACCOUNT}"
    },
    {
      "field": "Customer Reference",
      "example": "${CUSTOMER_REFERENCE}"
    },
    {
      "field": "Invoice Number",
      "example": "${INVOICE_NUMBER}"
    },
    {
      "field": "Transaction Reference",
      "example": "${TRANSACTION_REFERENCE}"
    },
    {
      "field": "Receipt Amount",
      "example": "${RECEIPT_AMOUNT}"
    },
    {
      "field": "Currency",
      "example": "${CURRENCY}"
    },
    {
      "field": "Receipt Date",
      "example": "${RECEIPT_DATE}"
    },
    {
      "field": "Matching Rule",
      "example": "${MATCHING_RULE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Load Configured Lockbox Input",
      "action": "Load the configured lockbox input file for the target bank account and transmission format.",
      "test_data": "${LOCKBOX} / ${BANK_ACCOUNT} / ${TRANSMISSION_FORMAT}",
      "expected_result": "The lockbox input is available for import against the configured bank account.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Run Import / Processing",
      "action": "Run the lockbox import and processing action in Oracle Fusion Accounts Receivable.",
      "test_data": "",
      "expected_result": "Oracle Fusion accepts the submission and begins import and processing.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the lockbox processing screen, submitting the import request and polling for completion."
    },
    {
      "step_number": 3,
      "step_name": "Review Imported Receipt Records",
      "action": "Review the receipt records imported from the lockbox input.",
      "test_data": "",
      "expected_result": "Imported records match the expected count and content of the source input.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Validate Customer Identification",
      "action": "Review the customer identified for each imported transaction against ${CUSTOMER} / ${CUSTOMER_ACCOUNT} / ${CUSTOMER_REFERENCE}.",
      "test_data": "${CUSTOMER} / ${CUSTOMER_ACCOUNT} / ${CUSTOMER_REFERENCE}",
      "expected_result": "The correct paying customer is identified for each transaction with valid reference data.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Validate Transaction Matching",
      "action": "Review how each transaction is matched to invoices or open items using the configured ${MATCHING_RULE}.",
      "test_data": "${INVOICE_NUMBER} / ${TRANSACTION_REFERENCE} / ${MATCHING_RULE}",
      "expected_result": "Each transaction is matched to the correct invoice, customer reference or open item according to the configured matching rule.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Generated Receipts",
      "action": "Review the receipts created from the matched transactions.",
      "test_data": "",
      "expected_result": "Receipts are created for successfully matched transactions with correct customer, amount, currency and date.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Review Applied Amounts",
      "action": "Review the amounts applied against matched invoices for each generated receipt.",
      "test_data": "${RECEIPT_AMOUNT} / ${CURRENCY}",
      "expected_result": "Applied amounts correctly reduce the balance of the matched invoice(s) and reconcile to the receipt amount.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Review Exceptions",
      "action": "Review any transactions that could not be confidently matched or applied — unmatched, ambiguous, duplicate or invalid items.",
      "test_data": "",
      "expected_result": "Every transaction that cannot be confidently processed is surfaced as a clearly classified exception rather than silently accepted, dropped or misapplied.",
      "validation_type": "business_assertion",
      "note": "Failed or exception-flagged items are not automatically treated as Oracle application defects — data, configuration and integration causes are considered first."
    },
    {
      "step_number": 9,
      "step_name": "Verify Batch / Process Status",
      "action": "Confirm the overall lockbox batch or process status reflects the actual outcome of the run.",
      "test_data": "",
      "expected_result": "Batch or process status accurately reflects successfully applied receipts and any unresolved exceptions — never a status implying complete, unqualified success when exceptions remain.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — a run that correctly surfaces exceptions is a passing test, not a failure."
    }
  ],
  "expected_results": [
    "The configured lockbox input is correctly imported into Oracle Fusion Accounts Receivable.",
    "The correct paying customer is identified for each transaction with valid reference data.",
    "Each transaction is correctly matched to the intended invoice, customer reference or open item using the configured matching rule.",
    "Receipts are created and applied with correct customer, amount, currency and date.",
    "Unmatched, ambiguous, duplicate or invalid items are surfaced as clearly classified exceptions rather than silently accepted.",
    "Unmatched or partially matched items are handled according to configured matching and application rules.",
    "Batch or process status correctly reflects the outcome, including any unresolved exceptions.",
    "No lockbox exception is automatically treated as a confirmed Oracle application defect without supporting evidence."
  ],
  "validation_checkpoints": [
    "Lockbox input correctly imported.",
    "Expected receipts created from the input data.",
    "Correct customers identified for each transaction.",
    "Correct transactions matched to invoices, references or open items.",
    "Correct amounts applied against matched invoices.",
    "Exceptions correctly surfaced rather than silently accepted.",
    "Unmatched items handled according to configured matching and application rules.",
    "Batch/process status correctly reflects the run outcome."
  ]
}