Oracle ERP Testing Tool > Test Library > Financials > Cash Management > Bank Statements

Syntra Standard Oracle Test Library

Oracle Fusion Bank Statement Inquiry & Verification Test Cases

Validate search, retrieval and review of Oracle Fusion bank statements and their transaction-level details across every stage of the bank statement lifecycle.

Test ID	ORCL.R2R.CM.BS.INQUIRY
Application	Oracle Fusion Cloud
Product	Financials
Module	Cash Management
Process	Bank Statements
Business Flow	Record-to-Report / Cash Management
Scenario Type	Positive & Negative / 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 search and review UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 12 business-readable test steps; SyntraFlow's automation executes approximately 30 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised Cash Management user can search for, retrieve and review Oracle Fusion bank statements and their transaction-level detail, using search criteria such as bank account, statement number, date, currency or status.

The scenario should confirm that:

the entered search criteria are accepted without unexpected errors
the correct bank statement(s) are returned for valid search criteria
a correctly empty result set is returned when no statement matches the criteria
a correctly access-restricted result is returned when a statement falls outside the user's security access
statement header details displayed match the underlying statement record
transaction lines displayed match the underlying statement data
balances and totals displayed match the underlying statement data
processing and reconciliation status displayed match the underlying statement data
transaction-level detail can be retrieved where available

This scenario validates search, retrieval and review only — it does not create, import, validate, process or reprocess bank statements. Those are separate scenarios in the same lifecycle.

When to Use This Test

Functional testing of a new Oracle Fusion Cash Management implementation
Regression testing after an Oracle quarterly update
UAT sign-off for Cash Management bank statement search and review
Verifying statement state at any stage of the bank statement lifecycle — imported, validated, processed, exception or reprocessed

Where This Test Fits in the Bank Statement Lifecycle

Import

→

Parse

→

Validate

→

Process

→

Exception Handling

→

Reprocess

→

Inquiry

Inquiry is shown as the final stage in this flow, but in practice it is used throughout the lifecycle — after import, after validation, after processing, during exception handling and after reprocessing — to search for and verify the current state of a statement at any point, not only at the end.

← Previous Stage

Reprocess Bank Statement

Preconditions

Oracle Fusion Cash Management access with inquiry/view privileges is available to the test user.
Bank statements of varying status (imported, validated, processed, exception, reprocessed) exist in the environment to search for.
Valid search criteria are available, including bank account, statement number, date, currency and status.
The test user's security access is scoped to a known set of bank accounts, so an access-restricted search can be exercised.

Exact search fields, filters and access restrictions may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Bank Account	${BANK_ACCOUNT}
Statement Number	${STATEMENT_NUMBER}
Date	${STATEMENT_DATE}
Currency	${CURRENCY} — e.g. USD, GBP, EUR
Status	${STATEMENT_STATUS} — Imported / Validated / Processed / Exception / Reprocessed
Expected Statement Status	Status expected for the matching statement(s)
Expected Transaction Count	Scenario-defined
Expected Balances	Opening and closing balance for the statement

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment and available DataVault bank statement records.

Test Steps

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

#	User Action	Expected Result
1	Sign in to Oracle Fusion Sign in to the Oracle Fusion environment using an authorised Cash Management test user.	Oracle Fusion home page is displayed successfully and the user session is established.
2	Navigate to Cash Management Navigate to the Cash Management work area.	The Cash Management work area opens successfully.
3	Open Bank Statements Open the Bank Statements task within Cash Management.	The Bank Statements work area is displayed.
4	Enter Search Criteria Enter search criteria — bank account, statement number, date, currency or status. ${BANK_ACCOUNT} / ${STATEMENT_NUMBER} / ${STATEMENT_DATE} / ${CURRENCY} / ${STATEMENT_STATUS} This single business step replaces multiple technical actions such as focusing each search field, entering each value and confirming entry.	The entered search criteria are accepted without unexpected errors.
5	Execute the Search Submit the search.	Oracle Fusion returns a result set based on the entered criteria — one or more matching statements, or a correctly empty or access-restricted result.
6	Review the Returned Statement(s) Review the list of statements returned by the search.	The returned statement(s) match the entered search criteria, or the result set correctly reflects no match or restricted access.
7	Select a Statement to Review Select a statement from the result set to open for detailed review.	The selected statement opens and its detail is displayed.
8	Review Statement Header Details Review the statement header — bank account, statement number, date, currency and status.	Header details displayed match the underlying statement record.
9	Review Transaction Lines Review the transaction lines listed on the statement.	Transaction lines displayed match the underlying statement data.
10	Review Balances and Totals Review the opening balance, closing balance and transaction totals for the statement.	Balances and totals displayed match the underlying statement data.
11	Review Processing/Reconciliation Status Review the statement's processing and reconciliation status.	Processing and reconciliation status displayed match the underlying statement data.
12	Drill Into Transaction DetailsBusiness assertion Where available, drill into an individual transaction line to review its full detail. This is the main business assertion for the scenario — the test does not stop merely because a search returned results without an application error.	Search criteria correctly returned the matching statement(s), and statement header, transaction lines, balances, references and processing status displayed match the underlying statement data — including a correctly empty or access-restricted result where that is the expected outcome.

Expected Results

Search criteria correctly return the matching statement(s), including a correctly empty result set or a correctly access-restricted result where applicable.
Statement header details displayed (bank account, statement number, date, currency, status) match the underlying statement record.
Transaction lines displayed match the underlying statement transactions.
Balances and totals displayed match the underlying statement data.
References and processing/reconciliation status displayed match the underlying statement data.
Transaction-level detail can be retrieved where available.

Key Validation Checkpoints

Search criteria are accepted without unexpected errors.
Returned statement(s) match the entered bank account, statement number, date, currency or status.
Statement header fields match the underlying record.
Transaction line count and detail match the underlying record.
Opening and closing balances match the underlying record.
Processing/reconciliation status matches the underlying record.
Empty result sets are returned correctly when no statement matches the criteria.
Access-restricted results are returned correctly for statements outside the user's security access.

Core Business Scenario

Bank Statement Inquiry

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 Bank Statement Inquiry business scenario. Jarvis AI can extend this scenario by generating additional search-criteria and review variations using customer-specific bank statement data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same inquiry test dozens of times simply to cover different combinations of bank account, statement number, date, currency, status, empty results and access restrictions. 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 bank statement search and verification data required for scenario generation — Bank Accounts, Statement Numbers, Dates, Currencies, Statuses 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 access-restriction 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 search and review tests, SyntraFlow maintains this single Bank Statement Inquiry scenario and lets Jarvis AI generate relevant search-criteria and review variations from the customer's available bank statement data.

AI-Generated Test Variations

The same Bank Statement Inquiry 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 Cash Management Bank Statements.

Positive Scenarios

Search by bank account
Search by statement number
Search by date
Search by currency
Search by status
Search for an imported statement
Search for a processed statement
Search for an exception statement
Review transaction lines
Review balances
Review references
Review processing status
Review import source

Negative Scenarios

Search with no matching criteria (expected empty result)
Invalid or malformed search criteria
Search for a statement outside the user's bank account/security access (expected access-restricted result)
Search across an empty date range with no data

These are representative examples only. Available search criteria, statement statuses and access restrictions can depend on the customer's Oracle Fusion configuration, bank formats and security setup — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

DataVault can supply search and verification test dimensions — bank account, statement number, date, currency and expected status — where configured and connected, so generated inquiry scenarios reflect the customer's actual banking setup rather than generic placeholder data.

Standard Library Definition

Bank Account      ${BANK_ACCOUNT}
Statement Number  ${STATEMENT_NUMBER}
Date              ${STATEMENT_DATE}
Currency          ${CURRENCY}
Status            ${STATEMENT_STATUS}

DataVault

Bank Accounts
  Operating Account (USD)
  Payroll Account (GBP)
  Collections Account (EUR)
Statement Statuses
  Imported
  Validated
  Processed
  Exception
  Reprocessed
Date Ranges
  Current period
  Prior period
Currencies
  USD
  GBP
  EUR

Jarvis AI Generates

Scenario 01 — Search Operating Account + Processed Status
Scenario 02 — Search Payroll Account + Date Range
Scenario 03 — Search Collections Account + EUR
Scenario 04 — Search Exception Statement
Scenario 05 — Search With No Matching Criteria
Scenario 06 — Search Outside Security Access
...

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 bank account, statement number and transaction detail 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	Search by Bank Account	Account	Search using bank account only	Syntra Ready
VAR-002	Search by Statement Number	Statement	Search using statement number only	Syntra Ready
VAR-003	Search by Date	Date	Search using statement date only	Syntra Ready
VAR-004	Search by Currency	Currency	Search using currency only	Syntra Ready
VAR-005	Search by Status	Status	Search using statement status only	Syntra Ready
VAR-006	Search — Bank Account + Date Range	Account/Date	Combined bank account and date range	Syntra Ready
VAR-007	Search — Bank Account + Status	Account/Status	Combined bank account and status	Syntra Ready
VAR-008	Search — Statement Number + Currency	Statement/Currency	Combined statement number and currency	Syntra Ready
VAR-009	Search Imported Statement	Status	Status = Imported	Syntra Ready
VAR-010	Search Validated Statement	Status	Status = Validated	Syntra Ready
VAR-011	Search Processed Statement	Status	Status = Processed	Syntra Ready
VAR-012	Search Exception Statement	Status	Status = Exception	Syntra Ready
VAR-013	Search Reprocessed Statement	Status	Status = Reprocessed	Syntra Ready
VAR-014	Review Transaction Lines	Statement	Review line-level transaction detail after search	Syntra Ready
VAR-015	Review Balances and Totals	Statement	Review opening and closing balance	Syntra Ready
VAR-016	Review References	Statement	Review statement and transaction reference fields	Syntra Ready
VAR-017	Review Processing/Reconciliation Status	Status	Review processing and reconciliation status detail	Syntra Ready
VAR-018	Review Import Source	Source	Review the originating import batch/source for the statement	Syntra Ready
VAR-019	Search With No Matching Criteria	Account/Statement	Expected empty result set	Syntra Ready
VAR-020	Invalid or Malformed Search Criteria	Statement	Expected search validation message	Syntra Ready
VAR-021	Search Outside Security Access	Account	Expected access-restricted result	Syntra Ready
VAR-022	Search Across Empty Date Range	Date	Expected empty result set, no statements in range	Syntra Ready

Correctly Expected Search Results Are Passing Tests

Positive Testing

Jarvis generates search and review scenarios using criteria expected to correctly return one or more matching bank statements.

Valid Bank Account + Valid Statement Number + Valid Date → Matching Statement Returned

Negative Testing

Jarvis can generate search scenarios designed to exercise Oracle's search validations, empty-result handling and security access restrictions.

No Matching Search Criteria → Expected Empty Result Set
Search Outside Security Access → Expected Access-Restricted Result
Invalid/Malformed Search Criteria → Expected Search Validation

For an inquiry scenario, a search that returns exactly the expected result is a pass — including a correctly empty result set when no statement matches the criteria, and a correctly access-restricted result when a statement falls outside the user's security access. A test should not be marked failed simply because no rows, or a restricted result, were returned; it fails only when the returned result does not match what was expected.

Scenario	Oracle Outcome	Test Result
Valid search criteria	Correct statement returned with matching details	PASS
Search with no matching criteria	Correctly empty result set	PASS
Search outside security access	Correctly access-restricted result	PASS
Unexpected search/processor error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Bank Statement Inquiry Regression Pack

Search by Bank Account
Search by Statement Number
Search by Date
Search Processed Statement
Search Exception Statement
Review Transaction Lines
Review Balances and Totals
Review Processing/Reconciliation Status
Search With No Matching Criteria
Search Outside Security Access

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	Bank Statement Inquiry Regression Pack
Schedule	Nightly Regression
Tests	22 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

Bank Statement Lifecycle

Exact processing depends on customer banking setup, formats and integrations. Manual entry can enter this flow directly at Validate. Stages link to the corresponding test scenario family.

Import→Parse→Validate→Process→Exception Handling→Reprocess→

Inquiry

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 — Bank Statement Inquiry, 12 Business Steps

↓

DataVault — Customer-Specific Bank Statement Search Data

↓

Jarvis AI — Generate Search-Criteria + Review 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

Enter Search Criteria

May internally include

Open Search Panel → Focus Bank Account Field → Enter Bank Account → Enter Statement Number → Select Date Range → Select Currency → Select Status

Business Step

Drill Into Transaction Details

May internally include

Select Transaction Line → Open Transaction Detail → Capture Reference/Amount/Date → Close Detail

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
Execute the Search	Pass	—
Open Statement Detail	Pass	—
Verify Statement, Transaction and Balance Detail Match	Pass	Pass

Related Bank Statement Tests

Inquiry is used to verify statement state throughout the same Cash Management bank statement lifecycle — explore the related import, processing, reprocessing and exception scenarios below.

Import Bank Statement Process Bank Statement Reprocess Bank Statement Bank Statement Exceptions

Turn This Standard Test into Your Oracle Cash Management Regression Suite

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

Automate with SyntraFlow Explore Bank Statements 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

Bank Statements Cash Management Oracle Cash Management Testing Tool Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What can be searched using the Oracle Fusion Bank Statement Inquiry test?

Statements can be searched by bank account, statement number, date, currency or status, individually or in combination. Results can then be reviewed at header, transaction-line and balance level.

Does this test include exception and reprocessed statements?

Yes. Search and review coverage includes statements at every status in the lifecycle — imported, validated, processed, exception and reprocessed.

What happens when a search returns no results?

A correctly empty result set — where the search criteria genuinely match no statement — is treated as a pass. The test only fails if the returned result does not match what was expected for the given criteria.

Does this test check access restrictions on bank statement search?

Yes. Where a searched statement or bank account falls outside the test user's security access, a correctly access-restricted result is expected and treated as a pass, not a failure.

How are the many bank statement inquiry test variations generated?

Jarvis AI uses this standard inquiry scenario together with available DataVault test data and configuration to generate relevant search-criteria, review and access-restriction variations for the customer's environment.

Can this Bank Statement Inquiry test be scheduled?

Yes. Selected inquiry variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution.