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

Syntra Standard Oracle Test Library

Oracle Fusion Import Bank Statement Test Cases

Validate that Oracle Fusion Cash Management can receive a bank statement through the configured import mechanism and create the expected statement records for processing.

Test ID	ORCL.R2R.CM.BS.IMPORT
Application	Oracle Fusion Cloud
Product	Financials
Module	Cash Management
Process	Bank Statements
Business Flow	Record-to-Report / Cash Management
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 12 business-readable test steps; SyntraFlow's automation executes approximately 34 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that Oracle Fusion Cash Management can receive a bank statement through the configured import mechanism and create the expected statement records for processing.

The scenario should confirm that:

the configured import mechanism or source is invoked correctly for the selected bank account
a valid statement file or feed is accepted for import
Oracle Fusion creates a statement record with the expected header — account, statement number, date, currency and opening/closing balance
transaction lines in the imported statement match the count and amounts in the source file or feed
the imported statement becomes available for downstream parsing and validation
invalid or incomplete import data produces the expected import exception rather than a silently incorrect statement

This scenario covers the import step only — parsing individual transaction lines, statement validation and processing/reconciliation against cash transactions are covered by separate downstream test scenarios.

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 import
Baseline case referenced by parse, validate, process and exception-handling scenarios within the same bank statement lifecycle

Where This Test Fits in the Bank Statement Lifecycle

Import

→

Parse

→

Validate

→

Process

→

Inquiry

This test covers the import step only, and serves as the entry point for the bank statement lifecycle — parsing, validation and processing scenarios all build on the statement record created here.

Next Stage →

Load & Parse Bank Statement

Preconditions

Oracle Fusion Cash Management is configured and available.
A bank account is configured and active in Cash Management.
An import mechanism or source is configured for the bank account.
A valid statement file or feed is available for import.
The test user has permission to import bank statements.

Exact setup, import mechanism and field availability may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Bank Account	${BANK_ACCOUNT}
Bank	${BANK}
Statement Number	${STATEMENT_NUMBER}
Statement Date	${STATEMENT_DATE}
Currency	${CURRENCY}
Statement Format	${STATEMENT_FORMAT} — example or customer-configured format
File Name	${FILE_NAME}
Opening Balance	${OPENING_BALANCE}
Closing Balance	${CLOSING_BALANCE}
Transaction Count	${TRANSACTION_COUNT}
Transaction Amounts	${TRANSACTION_AMOUNTS}

Sample values are illustrative. Statement format examples represent example or customer-configured formats — not a claim that any specific format is universally supported. Replace all values with valid data from the target Oracle Fusion environment.

Test Steps

12 business-readable steps. SyntraFlow's automation executes ~34 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	Select the Target Bank Account Select the bank account the statement will be imported against. ${BANK_ACCOUNT}	The correct bank account is selected and its import options are available.
5	Initiate Statement Import Initiate the statement import process for the selected bank account.	The import dialog or process opens successfully.
6	Select or Confirm the Import Source/File Select or confirm the statement file or configured import source/feed to be used. ${FILE_NAME} This single business step replaces multiple technical actions such as opening the file browser, selecting the file, confirming the file type and closing the dialog.	The selected file or source is accepted and ready for submission.
7	Submit the Import Submit the statement import.	Oracle Fusion accepts the import submission and starts processing it without unexpected errors.
8	Monitor Import Status Monitor the status of the import process until it completes.	The import process reaches a completed status within the expected time.
9	Review Import Results/Log Review the import results or process log for errors or warnings.	The import log shows the expected outcome for a successful import, with no unexpected errors or warnings.
10	Locate the Imported Statement Search for and open the newly imported bank statement. ${STATEMENT_NUMBER}	The imported statement is located and can be opened for review.
11	Verify Statement Header Fields Review the statement header — bank account, statement number, date, currency, opening balance and closing balance.	Header fields match the values in the imported source file or feed.
12	Verify Transaction Count Matches SourceBusiness assertion Compare the number of transaction lines on the imported statement against the source file or feed. ${TRANSACTION_COUNT} This is the main business assertion for the scenario — the test does not stop merely because the import process completed successfully.	The imported statement contains a statement record with the expected header and a transaction count that matches the imported source.

Expected Results

Oracle Fusion successfully creates a statement record with the expected header — account, date, currency, opening balance and closing balance.
Transaction lines on the imported statement match the imported source in count and amount.
The import process completes without unexpected errors.
The imported statement is available for parsing, validation and downstream processing.
Invalid or incomplete import data produces the expected import exception rather than a silently incorrect statement.

Key Validation Checkpoints

Correct bank account is associated with the imported statement.
Statement number is populated correctly.
Statement date matches the source.
Currency matches the source or configured account currency.
Opening balance matches the source.
Closing balance matches the source.
Transaction count matches the source file or feed.
Transaction amounts are consistent with the source.
Import completion status is received.
Import log/results contain no unexpected errors.
Imported statement record can be located and opened after import.
Captured statement identifier can be used by subsequent automated scenarios.

Core Business Scenario

Import Bank Statement

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 import 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 import test dozens of times simply to cover different combinations of bank account, currency, statement format, file condition or invalid data. 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 — Banks, Bank Accounts, Currencies, Statement Formats, Transaction Codes, Amounts and other relevant test attributes, where configured and connected.

Jarvis AI

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

Positive + Negative Test Variations

Positive, negative, format and account-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 import 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 Import Bank Statement 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

Valid bank statement import
Import against different bank accounts
Import in different currencies
Statement with multiple transactions
Statement with a single transaction
Import with different statement dates
Multiple statement files imported in one run
Import across multiple accounts
Statement with debit and credit transactions

Negative Scenarios

Invalid bank account
Unsupported or invalid format
Missing mandatory fields
Duplicate statement
Invalid statement number
Invalid currency
Invalid statement date
Corrupt file
Empty file
Invalid opening/closing balances
Access/security issue
Import mechanism unavailable

These are representative examples only. Statement formats, supported import mechanisms and negative-scenario behavior depend entirely on the customer's Oracle Fusion configuration — no specific format (for example BAI2, MT940, CAMT or a custom format) is claimed to be generally or universally supported.

Generated Using Your DataVault Test Data

Generic test data often fails to represent the configuration of a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault — Bank, Bank Account, Currency, Statement Format, Transaction Code and Amount — to create import variations relevant to the customer's actual implementation.

Standard Library Definition

Bank Account       ${BANK_ACCOUNT}
Bank               ${BANK}
Statement Number   ${STATEMENT_NUMBER}
Statement Date     ${STATEMENT_DATE}
Currency           ${CURRENCY}
Statement Format   ${STATEMENT_FORMAT}
Opening Balance    ${OPENING_BALANCE}
Closing Balance    ${CLOSING_BALANCE}

DataVault

Banks
  Bank A
  Bank B
Bank Accounts
  Operating Account (USD)
  Payroll Account (GBP)
  Regional Account (EUR)
Currencies
  USD
  GBP
  EUR
Statement Formats
  Example/configured format A
  Example/configured format B
Transaction Codes
  Configured per bank account
Amounts
  Representative debit/credit amounts

Jarvis AI Generates

Scenario 01 — Operating Account + USD + Example Format A
Scenario 02 — Payroll Account + GBP + Multiple Transactions
Scenario 03 — Regional Account + EUR + Single Transaction
Scenario 04 — Multiple Statement Files in One Run
Scenario 05 — Invalid Bank Account
Scenario 06 — Duplicate Statement
...

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 and statement details remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of import 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	Valid Bank Statement Import	Positive	Valid bank account, valid format, statement imports successfully	Syntra Ready
VAR-002	Import — Bank Account A	Positive/Account	Different configured bank account	Syntra Ready
VAR-003	Import — Bank Account B	Positive/Account	Second configured bank account	Syntra Ready
VAR-004	Import — USD Statement	Positive/Currency	Currency = USD	Syntra Ready
VAR-005	Import — EUR Statement	Positive/Currency	Currency = EUR	Syntra Ready
VAR-006	Import — GBP Statement	Positive/Currency	Currency = GBP	Syntra Ready
VAR-007	Multiple Transactions in Statement	Positive	Statement contains multiple transaction lines	Syntra Ready
VAR-008	Single Transaction Statement	Positive	Statement contains exactly one transaction line	Syntra Ready
VAR-009	Different Statement Date	Positive	Statement date differs from a prior import	Syntra Ready
VAR-010	Multiple Statement Files in One Import Run	Positive/File	More than one statement file imported in sequence	Syntra Ready
VAR-011	Example Configured Format A	Positive/Format	Example or customer-configured statement format A	Syntra Ready
VAR-012	Example Configured Format B	Positive/Format	Example or customer-configured statement format B	Syntra Ready
VAR-013	Import Across Multiple Accounts	Positive/Account	Single import run covering multiple bank accounts	Syntra Ready
VAR-014	Statement with Debit and Credit Transactions	Positive	Statement contains both debit and credit transaction lines	Syntra Ready
VAR-015	Invalid Bank Account	Negative/Account	Bank account not configured or inactive	Syntra Ready
VAR-016	Unsupported/Invalid Format	Negative/Format	File format not recognized or not configured for the account	Syntra Ready
VAR-017	Missing Mandatory Fields	Negative	Statement header missing a required field	Syntra Ready
VAR-018	Duplicate Statement Import	Negative/Duplicate	Statement number/date already imported	Syntra Ready
VAR-019	Invalid Statement Number	Negative	Statement number fails expected format or uniqueness rules	Syntra Ready
VAR-020	Invalid Currency	Negative/Currency	Currency not configured for the bank account	Syntra Ready
VAR-021	Invalid Statement Date	Negative	Statement date outside expected range or malformed	Syntra Ready
VAR-022	Corrupt File	Negative/File	File cannot be parsed or read by the import mechanism	Syntra Ready
VAR-023	Empty File	Negative/File	File contains no statement data	Syntra Ready
VAR-024	Invalid Opening/Closing Balances	Negative	Balances missing, non-numeric or inconsistent	Syntra Ready
VAR-025	Import Access/Security Issue	Negative	User lacks required import permission or role	Syntra Ready

Automatically Expand Positive and Negative Import Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the bank statement import process.

Valid Bank Account + Valid Format + Balanced Statement → Statement Imported

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's validations, business rules and exception handling around statement import.

Invalid Bank Account → Expected Account Validation
Duplicate Statement → Expected Duplicate Validation
Closing Balance Mismatch → Expected Balance Validation

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

Scenario	Oracle Outcome	Test Result
Valid statement import	Statement imported successfully	PASS
Duplicate statement	Duplicate validation occurs	PASS
Unknown bank account	Account 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.

Bank Statement Import Regression Pack

Valid Bank Statement Import
Import — Bank Account A
Import — USD Statement
Import — EUR Statement
Multiple Transactions in Statement
Multiple Statement Files in One Import Run
Import Across Multiple Accounts
Invalid Bank Account
Duplicate Statement Import
Corrupt File

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 Import Regression Pack
Schedule	Nightly Regression
Tests	25 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 — Import Bank Statement, 12 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

Select or Confirm the Import Source/File

May internally include

Open Import Dialog → Open File Browser → Select File → Confirm File Type → Close Dialog

Business Step

Monitor Import Status

May internally include

Open Process Monitor → Search Process → Poll Status → Confirm Completion

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
Submit the Import	Pass	—
Monitor Import Status	Pass	—
Verify Statement Header Fields	Pass	Pass

Related Bank Statement Tests

Statement import is the entry point of the same bank statement lifecycle — explore the related parsing, validation, exception and inquiry scenarios below.

Load & Parse Bank Statement Validate Bank Statement Bank Statement Exceptions Bank Statement Inquiry

Turn This Standard Test into Your Oracle Cash Management Regression Suite

Start with the Syntra Standard bank statement import 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 Bank Statement 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

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

Frequently Asked Questions

What does the Import Bank Statement test validate in Oracle Fusion Cash Management?

It validates that a bank statement can be received through the configured import mechanism and that Oracle Fusion creates a statement record with the expected header — bank account, statement number, date, currency, opening balance and closing balance — along with transaction lines matching the imported source.

Which bank statement formats are supported?

Supported formats depend entirely on the customer's Oracle Fusion configuration and connected import mechanisms. Any format referenced in this test library is an example or customer-configured format, not a claim of universal support.

What happens if an invalid or corrupt file is imported?

An invalid, corrupt, empty or incomplete file is expected to produce the corresponding Oracle Fusion import exception rather than a silently created or incorrect statement. This is treated as a passing negative test when the expected exception occurs.

How are the many import test variations generated?

Jarvis AI uses this standard import scenario together with available DataVault test data and configuration to generate relevant positive, negative and format-specific variations for the customer's environment.

Can this Oracle Fusion bank statement import test be scheduled?

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

Does this test cover parsing individual transaction lines?

No. This scenario validates that the statement is imported and that header fields and transaction count match the source. Line-level parsing is covered by the separate Load & Parse Bank Statement scenario.