Oracle ERP Testing Tool > Test Library > Financials > General Ledger > Journals
Syntra Standard Oracle Test Library

Oracle Fusion Journal Reversal Test Cases

Validate Oracle Fusion journal reversal processing and confirm correct reversal creation, period handling and resulting accounting effect.

Test IDORCL.R2R.GL.JRN.REVERSE
ApplicationOracle Fusion Cloud
ProductFinancials
ModuleGeneral Ledger
ProcessJournals
Business FlowRecord-to-Report
Scenario TypePositive / Functional
Test UsageFunctional Testing / Regression Testing / UAT
PriorityHigh
AutomationSyntraFlow Ready
LibrarySyntra 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 13 business-readable test steps; SyntraFlow's automation executes approximately 40 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised General Ledger user can reverse a posted journal in Oracle Fusion General Ledger — generating a correct reversal journal, applying a valid reversal period and method, posting that reversal, and confirming the resulting net accounting effect together with the original journal.

The scenario should confirm that:

  • the original journal is Posted and eligible for reversal
  • the reversal period is accepted, consistent with the ledger's reversal period configuration
  • the reversal method (manual or automatic) is applied correctly
  • the reversal journal is generated with debit and credit amounts correctly reversed line-by-line
  • the reversal journal correctly references the original journal
  • the reversal journal passes validation and can be posted
  • the original journal's status reflects that it has been reversed
  • the combined net accounting effect of the original and reversal journals is correct once both are posted

This scenario does not claim that journal creation, validation, approval or posting of the original journal are covered — those are separate upstream test cases in the same GL Journals library. The reversal journal's own posting is included so the net accounting effect can be verified.

When to Use This Test

  • Functional testing of Oracle Fusion GL journal reversal for a new implementation
  • Regression testing after an Oracle quarterly update
  • UAT sign-off for period-close journal reversal processing
  • Baseline case for validating net accounting effect across original and reversal journals within the same GL journal lifecycle

Where This Test Fits in the Record-to-Report Process

Journal Entry
Validation
Approval
Posting
Reverse
Financial Reporting

This test covers reversal of an already posted journal — including reversal period and method selection and posting of the reversal itself — and confirms the combined net accounting effect once both journals are posted. Journal creation, validation, approval and posting of the original journal are covered by separate upstream test cases in the same GL Journals library.

Preconditions

  1. Oracle Fusion General Ledger access is configured for the test user.
  2. A posted journal eligible for reversal exists.
  3. A valid reversal period is available — the same period or a subsequent open period, depending on ledger configuration.
  4. Reversal method and reversal category are configured, manual and/or automatic as applicable to the journal source.
  5. The accounting period intended for the reversal is open.
  6. The test user has permission to reverse and post General Ledger journals.

Exact setup, reversal-period rules and field availability may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Original Posted Journal${ORIGINAL_JOURNAL} — e.g. GL-JRN-10045 (Posted)
Ledger${LEDGER} — e.g. Vision Operations (USD)
Reversal Period${REVERSAL_PERIOD} — same-period example: Jul-25; next-period example: Aug-25
Reversal Method${REVERSAL_METHOD} — Manual or Automatic, where configured for the journal source
Currency${CURRENCY} — matches original journal; foreign-currency example: EUR

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

Test Steps

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

#User ActionExpected Result
1
Sign in to Oracle Fusion
Sign in to the Oracle Fusion environment using an authorised General Ledger test user.
Oracle Fusion home page is displayed successfully and the user session is established.
2
Navigate to General Ledger > Journals
Navigate to the General Ledger Journals work area.
The Journals work area opens successfully.
3
Locate the Posted Journal to Reverse
Search for and open the original posted journal that is eligible for reversal.
${ORIGINAL_JOURNAL}

This single business step replaces multiple technical actions such as opening search, entering the journal or batch number, clicking Search and selecting the result.

The correct original journal is located and its status confirms it is Posted and eligible for reversal.
4
Initiate Journal Reversal
Select Reverse Journal for the located journal.
The Reverse Journal dialog opens, pre-referencing the original journal.
5
Select Reversal Period
Select the accounting period into which the reversal journal should be created.
${REVERSAL_PERIOD}
The selected reversal period is accepted, consistent with the ledger's reversal period configuration (same period or a subsequent open period).
6
Select Reversal Method
Select the reversal method — manual reversal now, or automatic reversal on a defined trigger — where configured for the journal source.
${REVERSAL_METHOD}
The selected reversal method is accepted.
7
Review the Generated Reversal Journal
Review the reversal journal generated by Oracle, including header details and reversed line amounts.
The reversal journal mirrors the original journal's lines with debit and credit amounts reversed, and references the original journal.
8
Save the Reversal Journal
Select Save on the reversal journal.
Oracle Fusion successfully processes the save request without unexpected errors.
9
Validate the Reversal Journal
Run journal validation on the newly created reversal journal.
The reversal journal passes validation without unexpected errors.
10
Post the Reversal Journal
Submit the reversal journal for posting.
The reversal journal reaches Posted status.
11
Verify Original and Reversal Journal Statuses
Confirm the status of both the original journal and the newly posted reversal journal.
The original journal is flagged as Reversed and the reversal journal shows Posted status.
12
Verify Net Accounting Effect Across Both JournalsBusiness assertion
Compare the account balances contributed by the original journal and the reversal journal together.

This is a primary business assertion for the scenario, completing the Create Journal → Post → Verify Accounting → Reverse → Post Reversal → Verify Net Effect chain. It confirms the reversal actually offsets the original journal's accounting impact — a materially higher-value check than simply confirming the Reverse action or Post action completed.

The combined net accounting effect of the original and reversal journals is correct — zero net impact on affected accounts for a full reversal.
13
Verify Reversal Reference to the Original JournalBusiness assertion
Confirm the reversal journal carries a traceable reference back to the original journal, and that the original journal exposes a reference to its reversal.

This is the closing business assertion for the scenario — confirming full traceability between the original and reversal journals for audit and reporting purposes.

The reversal journal is identifiable by its generated journal number and reference, with confirmed cross-reference linkage to the original posted journal.

Expected Results

  • Reversal journal is created successfully and correctly references the original posted journal.
  • Reversal journal lines mirror the original journal with debit and credit amounts reversed.
  • Reversal period is applied consistent with the ledger's reversal period configuration.
  • Reversal method (manual or automatic) is applied as intended.
  • Reversal journal passes validation without unexpected errors.
  • Reversal journal can be posted successfully.
  • Original journal status reflects that it has been reversed.
  • Combined net accounting effect of the original and reversal journals is correct — zero net impact for a full reversal.
  • Reversal journal is available for subsequent inquiry and reporting scenarios.

Key Validation Checkpoints

  • Original journal status is Posted and eligible for reversal.
  • Reversal period matches intended test data and ledger configuration.
  • Reversal method matches intended test data.
  • Reversal journal line amounts are the exact reverse of the original journal.
  • Reversal journal references the original journal number/batch.
  • Reversal journal passes validation.
  • Reversal journal reaches Posted status.
  • Original journal exposes a reference to its reversal.
  • Net accounting effect across both journals nets to zero for a full reversal.
  • Captured reversal journal number/identifier can be used by subsequent automated scenarios.
Core Business Scenario
Reverse Journal
Business Steps
13
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 journal reversal business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific ledger, period and currency data available through Syntra DataVault.

Teams do not need to manually duplicate the same reversal test dozens of times simply to cover different combinations of ledger, reversal period, reversal method and currency. Jarvis uses the standard business scenario as the foundation — including the full create-to-reverse lifecycle chain — and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

01
Syntra Standard Test
Reusable Create Journal → Post → Verify Accounting → Reverse → Post Reversal → Verify Net Effect business process and automation logic — framed around the resulting accounting effect rather than only whether the Reverse action completes.
02
Customer DataVault
Provides approved customer-specific test data and configuration required for scenario generation — Ledgers, Original Journals, Reversal Periods, Reversal Methods, Currencies and other relevant test attributes.
03
Jarvis AI
Analyses the standard scenario together with available test data and generates relevant scenario variations.
04
Positive + Negative Test Variations
Positive, negative, period and currency-specific reversal scenarios.
05
Regression Pack
Selected variations can be grouped into an executable suite.
06
On-Demand / Scheduled / Batch Execution
Execute immediately or schedule the regression pack for unattended batch execution.
07
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 Journal 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 General Ledger Journals.

Positive Scenarios
  • Reverse posted journal
  • Reverse in same period, where permitted
  • Reverse in subsequent period
  • Manual reversal
  • Automatic reversal, where configured
  • Reverse multi-line journal
  • Reverse foreign-currency journal
  • Post reversal journal
Negative Scenarios
  • Attempt to reverse unposted journal
  • Invalid reversal period
  • Closed reversal period
  • Invalid reversal configuration
  • Already-reversed journal
  • Missing reversal information

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 reversal configuration 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

Ledger              ${LEDGER}
Original Journal     ${ORIGINAL_JOURNAL}
Reversal Period      ${REVERSAL_PERIOD}
Reversal Method      ${REVERSAL_METHOD}
Currency             ${CURRENCY}

DataVault

Ledgers
  Vision Operations (USD)
  UK Operations (GBP)
Posted Journals
  Per ledger, eligible for reversal
Periods
  Jul-25 (current)
  Aug-25 (next)
Reversal Methods
  Manual
  Automatic
Currencies
  USD
  GBP
  EUR

Jarvis AI Generates

Scenario 01 — Vision Operations + Same-Period Manual Reversal
Scenario 02 — UK Operations + Next-Period Automatic Reversal
Scenario 03 — Multi-Line Journal + EUR
Scenario 04 — E2E Create → Post → Reverse → Post Reversal → Verify Net Effect
Scenario 05 — Attempt to Reverse Unposted Journal
Scenario 06 — Already-Reversed Journal
...

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 ledger, original journal and reversal period 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.

IDVariationTypeKey DifferenceExecution
VAR-001Reverse Posted JournalPositiveBaseline reversal of a single-line posted journalSyntra Ready
VAR-002Reverse in Same PeriodPositive/PeriodReversal period = original journal's periodSyntra Ready
VAR-003Reverse in Subsequent PeriodPositive/PeriodReversal period = next open periodSyntra Ready
VAR-004Manual ReversalPositive/ManualReversal method = ManualSyntra Ready
VAR-005Automatic ReversalPositive/AutomaticReversal method = Automatic, where configuredSyntra Ready
VAR-006Reverse Multi-Line JournalPositiveOriginal journal has multiple lines/distributionsSyntra Ready
VAR-007Reverse EUR-Denominated JournalPositive/CurrencyCurrency = EURSyntra Ready
VAR-008Reverse GBP-Denominated JournalPositive/CurrencyCurrency = GBPSyntra Ready
VAR-009Post the Reversal JournalPositiveReversal journal posted after creationSyntra Ready
VAR-010Verify Original Journal Status After ReversalPositiveOriginal journal flagged as ReversedSyntra Ready
VAR-011Reversal with Alternate Reversal CategoryPositiveNon-default reversal categorySyntra Ready
VAR-012E2E: Create → Post → Reverse → Post Reversal → Verify Net EffectPositiveFull lifecycle chain culminating in a net accounting effect assertionSyntra Ready
VAR-013E2E: Foreign-Currency Full Reversal LifecyclePositive/CurrencyFull create-to-reverse chain executed on an EUR journalSyntra Ready
VAR-014Attempt to Reverse Unposted JournalNegativeOriginal journal status = Draft/UnpostedSyntra Ready
VAR-015Invalid Reversal PeriodNegative/PeriodReversal period does not exist or is invalid for the ledgerSyntra Ready
VAR-016Closed Reversal PeriodNegative/PeriodSelected reversal period is closedSyntra Ready
VAR-017Invalid Reversal ConfigurationNegativeReversal method/category not configured for the journal sourceSyntra Ready
VAR-018Already-Reversed JournalNegativeOriginal journal already has a recorded reversalSyntra Ready
VAR-019Missing Reversal InformationNegativeRequired reversal period or method left blankSyntra Ready
VAR-020Automatic Reversal Without ConfigurationNegative/AutomaticAutomatic reversal requested but not enabled for the journal sourceSyntra Ready

Automatically Expand Positive and Negative Reversal Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully create, post and reverse a journal.

Posted Journal + Valid Reversal Period + Valid Reversal Method → Reversal Journal Created and Posted

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's reversal validations and business rules.

  • Reverse Unposted Journal → Expected Status Validation
  • Invalid Reversal Period → Expected Period Validation
  • Already-Reversed Journal → Expected Duplicate Reversal Validation

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

ScenarioOracle OutcomeTest Result
Eligible posted journalReversal journal created and posts successfullyPASS
Attempt to reverse unposted journalReversal correctly blockedPASS
Already-reversed journalDuplicate reversal correctly blockedPASS
Unexpected processor errorUnexpected failureFAIL

Turn AI-Generated Variations into a Regression Pack

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

GL Journal Reversal Regression Pack

  • Reverse Posted Journal
  • Reverse in Same Period
  • Reverse in Subsequent Period
  • Manual Reversal
  • Automatic Reversal
  • Reverse Multi-Line Journal
  • Reverse EUR-Denominated Journal
  • E2E: Create → Post → Reverse → Post Reversal → Verify Net Effect
  • Invalid Reversal Period
  • Already-Reversed Journal
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
PackGL Journal Reversal Regression Pack
ScheduleQuarterly Update Regression
Tests20 scenarios
ExecutionBatch Mode
Start10:00 PM
EnvironmentOracle Fusion TEST
StatusScheduled

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.

20
Total Scenarios
18
Passed
1
Failed
1
Exceptions
13
Positive Tests
7
Negative Tests
74
Business Assertions

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

Journal Lifecycle

Not every journal moves through every stage, and approval depends on customer configuration. Stages link to the corresponding test scenario family.

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 Journal, 13 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
Locate the Posted Journal to Reverse
May internally include
Open Journal Search → Focus Journal/Batch Number → Enter Journal → Search → Select Journal → Confirm Posted Status
Business Step
Verify Net Accounting Effect Across Both Journals
May internally include
Open Journal Lines (Original) → Capture Line Amounts → Open Journal Lines (Reversal) → Capture Line Amounts → Compare Net Balance Per Account

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 — clicking Reverse or Post can both succeed while the resulting accounting effect is still wrong. This is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

StepAction StatusBusiness Validation
Click ReversePass
Click Post (Reversal Journal)Pass
Verify Net Accounting EffectPassPass

Related GL Journal Tests

Journal reversal is one stage of the same General Ledger journal lifecycle — explore the related creation, validation, posting and inquiry scenarios below.

Turn This Standard Test into Your Oracle GL Reversal Regression Suite

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

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.

Frequently Asked Questions

What does the Reverse Journal test validate in Oracle Fusion General Ledger?
It validates that a posted journal can be reversed correctly — including reversal period and method selection, generation of a reversal journal with debit and credit amounts reversed, posting of that reversal, and the resulting net accounting effect across both journals.
Can this test reverse a journal into a different accounting period?
Yes. The scenario covers reversal into the same period and into a subsequent period, depending on what the ledger's reversal period configuration permits.
What is the net accounting effect this test verifies?
Once both the original journal and its reversal are posted, the combined debit and credit impact on the affected accounts should net to zero for a full reversal. This test treats that combined outcome as the primary assertion, not just whether the Reverse or Post actions completed without error.
What is the difference between manual and automatic reversal?
Manual reversal is triggered directly by a user selecting Reverse Journal. Automatic reversal is generated based on configured reversal criteria for the journal source, where enabled. Both are covered as variations of this same business scenario.
How are the many journal reversal test variations generated?
Jarvis AI uses this standard reversal scenario together with available DataVault test data and configuration to generate relevant positive, negative, period and currency variations for the customer's environment.
Can the reversal scenario and its variations be scheduled?
Yes. Selected reversal variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution.