Oracle ERP Testing Tool > Test Library > Financials > Accounts Receivable > Receipts

Syntra Standard Oracle Test Library

Oracle Fusion Receipt Reversal Test Cases

Validate reversal of an eligible customer receipt and confirm resulting receipt, transaction and accounting status.

Test ID	ORCL.O2C.AR.RCP.REVERSE
Application	Oracle Fusion Cloud
Product	Financials
Module	Accounts Receivable
Process	Receipts
Business Flow	Order-to-Cash
Scenario Type	Positive / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 9 business-readable test steps; SyntraFlow's automation executes approximately 22 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised Accounts Receivable user can reverse an eligible customer receipt in Oracle Fusion Receivables, and that the resulting receipt, transaction and accounting status correctly reflect the reversal.

The scenario should confirm that:

the selected receipt is eligible for reversal and has not already been reversed
the reversal date and reversal reason are accepted
the receipt is correctly marked as reversed
any existing receipt applications are reversed or adjusted appropriately
transaction balances affected by the original receipt are restored where expected
accounting impact of the reversal is updated where applicable
the reversal remains traceable back to the original receipt

This scenario does not claim that every downstream lockbox, bank reconciliation or accounting-period configuration is covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test scenarios.

When to Use This Test

Functional testing of Oracle Fusion Receivables receipt reversal processing
Regression testing after an Oracle quarterly update
UAT sign-off for correction and exception-driven receipt lifecycle events
Baseline case referenced by receipt re-entry and replacement scenarios following a reversal

Where This Test Fits in the AR Receipt Lifecycle

Existing Receipt

→

Check Reversal Eligibility

→

Select Reverse

→

Enter Reversal Date/Reason

→

Confirm Reversal

→

Receipt Status Updated

→

Applications/Balances Updated

This test covers reversal of an existing customer receipt, and depends on a valid, eligible receipt already recorded in Oracle Fusion Receivables.

← Previous Stage

Unapply Receipt

Preconditions

Oracle Fusion Receivables is configured and available.
An existing receipt is recorded against a customer and is eligible for reversal (for example, it has not already been reversed).
The accounting period intended for the reversal is open, or reversal is otherwise permitted per configuration.
Reversal reason lookup values required for the reversal are available.
The test user has permission to reverse receipts in Oracle Fusion Receivables.

Exact eligibility rules, reversal reasons and field availability may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Customer	${CUSTOMER}
Receipt Number	${RECEIPT_NUMBER}
Receipt Amount	${RECEIPT_AMOUNT}
Receipt Method	${RECEIPT_METHOD}
Receipt Date	${RECEIPT_DATE}
Reversal Date	${REVERSAL_DATE}
Reversal Reason	${REVERSAL_REASON}
Application Status Before Reversal	Applied / Unapplied / Partially Applied

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.

Test Steps

9 business-readable steps. SyntraFlow's automation executes ~22 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Search for the Existing Receipt Search for the existing receipt by customer and receipt number. ${CUSTOMER} / ${RECEIPT_NUMBER} This single business step replaces multiple technical actions such as opening receipt search, entering the customer and receipt number, and selecting the result.	The correct receipt is located.
2	Open the Receipt Open the located receipt to review its current details.	Receipt details, including status and any existing applications, are displayed.
3	Check Reversal Eligibility Review the receipt to confirm it is eligible for reversal, including that it has not already been reversed.	Receipt status confirms it is eligible for reversal.
4	Select Reverse Select the Reverse action on the receipt.	The reversal entry page opens for the selected receipt.
5	Enter Reversal Date Enter the reversal date. ${REVERSAL_DATE}	Reversal date is accepted without unexpected validation errors.
6	Enter Reversal Reason Enter or select the reversal reason. ${REVERSAL_REASON}	Reversal reason is accepted.
7	Confirm Reversal Select Save/Confirm to complete the reversal.	Oracle Fusion processes the reversal request without unexpected errors.
8	Verify Receipt Status Updated Confirm the receipt's status following the reversal.	The receipt is marked Reversed, with the reversal date and reversal reason correctly retained.
9	Verify Applications/Balances Updated AccordinglyBusiness assertion Confirm that any receipt applications and affected transaction balances reflect the reversal, and verify the overall reversed receipt record. This is the main business assertion for the scenario — the test does not stop merely because Save was clicked successfully.	Receipt applications are reversed or adjusted appropriately, transaction balances are restored where expected, and accounting impact is updated where applicable.

Expected Results

An eligible customer receipt reverses successfully.
The receipt is correctly marked as reversed.
Reversal date and reversal reason are correctly retained on the transaction.
Receipt applications are reversed or adjusted appropriately.
Transaction balances affected by the original receipt are restored where expected.
Accounting impact of the reversal is updated where applicable.
No unexpected save errors occur.
The reversal remains traceable to the original receipt for audit purposes.

Key Validation Checkpoints

Receipt marked reversed.
Reversal date correct.
Reversal reason retained.
Receipt applications reversed/adjusted appropriately.
Transaction balances restored where expected.
Accounting impact updated where applicable.
Reversal remains traceable.

Core Business Scenario

Reverse Receipt

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core receipt reversal business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same reversal test dozens of times simply to cover different combinations of application status, reversal reason, timing and receipt method. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — customers, receipts, receipt methods, reversal reasons and other relevant test attributes.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining dozens of near-duplicate copies of the same reversal test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Reverse Receipt business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to Accounts Receivable Receipts.

Positive Scenarios

Reverse an unapplied receipt
Reverse an applied receipt
Reverse a fully applied receipt
Reverse a partially applied receipt
Reversal with different reversal reasons
Same-period reversal
Later-period reversal where permitted
Reversal followed by a replacement receipt
Reversal across different receipt methods

Negative Scenarios

Attempt to reverse an already-reversed receipt
Attempt to reverse an ineligible receipt
Invalid reversal date
Reversal dated within a closed accounting period
Missing reversal reason
Invalid receipt status for reversal
Unauthorized user attempts reversal
Downstream transaction state prevents reversal

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, controls and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data often fails to represent the receipt and application history of a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to create reversal variations relevant to the customer's actual implementation.

Standard Library Definition

Customer         ${CUSTOMER}
Receipt Number   ${RECEIPT_NUMBER}
Receipt Amount   ${RECEIPT_AMOUNT}
Receipt Method   ${RECEIPT_METHOD}
Reversal Date    ${REVERSAL_DATE}
Reversal Reason  ${REVERSAL_REASON}

DataVault

Receipts
  Receipt A — Unapplied
  Receipt B — Fully Applied
  Receipt C — Partially Applied
  Receipt D — Already Reversed
Receipt Methods
  Wire, Check, Credit Card
Reversal Reasons
  Bank Return, Customer Request, Data Entry Error

Jarvis AI Generates

Scenario 01 — Receipt A + Unapplied + Reverse
Scenario 02 — Receipt B + Fully Applied + Reverse
Scenario 03 — Receipt C + Partially Applied + Reverse
Scenario 04 — Reverse Already-Reversed Receipt D (Negative)
Scenario 05 — Reversal in Closed Period (Negative)
Scenario 06 — Missing Reversal Reason (Negative)
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific data such as customer and receipt details remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of scenarios Jarvis can generate from this business scenario. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Reverse Unapplied Receipt	Unapplied	Receipt has no applications at time of reversal	Syntra Ready
VAR-002	Reverse Applied Receipt	Applied	Receipt fully applied to a single transaction	Syntra Ready
VAR-003	Reverse Fully Applied Receipt	Applied	Full application amount reversed	Syntra Ready
VAR-004	Reverse Partially Applied Receipt	Applied	Only part of receipt amount applied prior to reversal	Syntra Ready
VAR-005	Reversal With Bank Return Reason	Reason	Reversal reason = Bank Return	Syntra Ready
VAR-006	Reversal With Customer Request Reason	Reason	Reversal reason = Customer Request	Syntra Ready
VAR-007	Same-Period Reversal	Period	Reversal dated within the same open period as the receipt	Syntra Ready
VAR-008	Later-Period Reversal	Period	Reversal dated in a later open period, where permitted	Syntra Ready
VAR-009	Reversal Followed by Replacement Receipt	Status	New receipt created after reversal to replace it	Syntra Ready
VAR-010	Reversal Across Different Receipt Methods	Status	Receipt method = Wire / Check / Credit Card	Syntra Ready
VAR-011	Attempt to Reverse Already-Reversed Receipt	Status	Receipt has already been reversed once	Syntra Ready
VAR-012	Attempt to Reverse Ineligible Receipt	Status	Receipt status does not permit reversal	Syntra Ready
VAR-013	Invalid Reversal Date	Period	Reversal date precedes the receipt date	Syntra Ready
VAR-014	Reversal in Closed Period	Period	Reversal date falls within a closed accounting period	Syntra Ready
VAR-015	Missing Reversal Reason	Reason	Required reversal reason left blank	Syntra Ready
VAR-016	Invalid Receipt Status for Reversal	Status	Receipt status is inconsistent with reversal eligibility rules	Syntra Ready
VAR-017	Unauthorized User Attempts Reversal	Status	User lacks reversal privilege/security	Syntra Ready
VAR-018	Downstream State Prevents Reversal	Applied	Receipt application feeds a closed or locked downstream process	Syntra Ready
VAR-019	Reversal of Multi-Application Receipt	Applied	Receipt applied across multiple transactions before reversal	Syntra Ready
VAR-020	Reversal of On-Account Applied Receipt	Applied	Receipt applied on-account rather than to a specific transaction	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully reverse an eligible customer receipt.

Eligible Receipt + Valid Reversal Date + Valid Reversal Reason → Receipt Reversed

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's reversal eligibility rules, validations and security around receipt reversal.

Already Reversed Receipt → Expected Duplicate Reversal Validation
Closed Period → Expected Period Validation
Missing Reversal Reason → Expected Required Field Validation
Unauthorized User → Expected Security Validation
Ineligible Receipt Status → Expected Eligibility Validation

A negative test should not be marked as failed simply because Oracle correctly blocks an invalid reversal attempt. If the expected Oracle validation occurs, the negative test has passed.

Scenario	Oracle Outcome	Test Result
Eligible receipt	Reversal completes successfully	PASS
Already reversed receipt	Reversal prevented	PASS
Closed period	Period validation occurs	PASS
Unauthorized user	Security validation occurs	PASS
Unexpected system error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated scenarios and group them into reusable execution packs.

AR Receipt Reversal Regression Pack

Reverse Unapplied Receipt
Reverse Fully Applied Receipt
Reverse Partially Applied Receipt
Same-Period Reversal
Later-Period Reversal
Reversal Followed by Replacement Receipt
Attempt to Reverse Already-Reversed Receipt
Reversal in Closed Period
Missing Reversal Reason
Unauthorized User Attempts Reversal

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	AR Receipt Reversal Regression Pack
Schedule	Quarterly Update Regression
Tests	20 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

AR Receipt Lifecycle

Lockbox Receipt Processing creates receipts through an automated batch path and shares the Create / Import stage. Exact processing depends on receipt method, customer setup, currency and customer-specific Oracle Fusion configuration. Stages link to the corresponding test scenario family.

Create / Import→Apply→Partial Application→Unapply→

Reverse

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Library — Reverse Receipt, 9 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Check Reversal Eligibility

May internally include

Open Receipt → Read Status Field → Confirm Not Already Reversed → Confirm Eligible Status

Business Step

Enter Reversal Reason

May internally include

Open Reversal Reason List of Values → Select Reason → Confirm Selection

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

Step	Action Status	Business Validation
Enter Reversal Date	Pass	—
Click Save/Confirm	Pass	—
Verify Receipt Reversed	Pass	Pass

Related AR Receipt Tests

Reversal is one stage of the same AR receipt lifecycle — explore the related creation, application and unapplication scenarios below.

Unapply Receipt Create Standard Receipt Apply Receipt

Turn This Standard Test into Your Oracle Receivables Regression Suite

Start with the Syntra Standard reversal test, use DataVault to provide environment-specific test data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore AR Receipts Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

AR Receipts Test Library Accounts Receivable Test Library Financials Test Library Oracle ERP Testing Tool Syntra DataVault

Frequently Asked Questions

What does the Reverse Receipt test validate in Oracle Fusion Receivables?

It validates that an eligible customer receipt can be reversed correctly — including confirming reversal eligibility, entering a reversal date and reason, and verifying that receipt status, applications and transaction balances correctly reflect the reversal.

How is reversing a receipt different from voiding a payment?

Receipt reversal is an Accounts Receivable action against a customer receipt — it reverses money recorded as received from a customer. Voiding a payment is an Accounts Payable action against a supplier payment. This scenario is scoped to AR receipt reversal only; supplier payment voiding is covered by a separate Accounts Payable test scenario.

Can a reversed receipt be recreated?

Where the underlying business reason still requires a receipt — for example, the customer's funds are subsequently confirmed as received — a new receipt can typically be created. This scenario includes a positive variation covering reversal followed by creation of a replacement receipt.

What happens to applications on the reversed receipt?

Where the receipt had existing applications to customer transactions, those applications are expected to be reversed or adjusted appropriately as part of the reversal, and affected transaction balances restored where expected. This is covered as a distinct validation checkpoint alongside reversal of an unapplied receipt.

What security or period considerations apply to receipt reversal?

Reversal typically requires an appropriate security privilege, and the reversal date generally needs to fall within an open accounting period unless the customer's configuration permits reversal into a later period. Both unauthorized-user and closed-period conditions are covered as negative variations of this scenario.