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

Syntra Standard Oracle Test Library

Oracle Fusion Manual Bank Statement Entry Test Cases

Validate creation of a bank statement manually in Oracle Fusion Cash Management, where the customer's business process permits manual entry as an alternative to file-based import.

Test ID	ORCL.R2R.CM.BS.CREATE.MANUAL
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	Medium
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 32 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 successfully create a bank statement manually in Oracle Fusion Cash Management, where the customer's business process permits manual entry rather than file-based import.

The scenario should confirm that:

the selected bank account is valid and manual statement entry is permitted for it
statement header information — statement number, date, currency and opening balance — can be entered
one or more transaction lines (debit or credit, amount, reference) can be entered manually
the entered closing balance is accepted
transaction totals reconcile with the entered opening and closing balances
the manual statement can be saved successfully
the saved statement is available for the same downstream validation and processing lifecycle as an imported statement

This scenario covers manual statement creation only — the validation, processing and inquiry stages that apply equally to imported statements are covered by separate downstream test scenarios.

When to Use This Test

Functional testing of manual bank statement entry where the customer's business process does not use file-based import
Regression testing after an Oracle quarterly update
UAT sign-off for manually entered bank statements
Fallback/exception coverage when an automated statement file or feed is unavailable

Where This Test Fits in the Bank Statement Lifecycle

Manual Entry

→

Validate

→

Process

→

Inquiry

Manual Entry is an alternate entry point into the bank statement lifecycle for bank accounts where the customer's business process permits manual creation. Rather than an Import and Parse stage, a manually entered statement is created directly and feeds straight into Validate: Manual Entry → Validate → Process → Inquiry. This bypasses the Import and Parse stages used for file-based statements, since there is no file to import or parse.

← Previous Stage

Load & Parse Bank Statement

Next Stage →

Bank Statement Exceptions

Preconditions

Oracle Fusion Cash Management is configured and available.
Manual statement entry is permitted and configured for the relevant bank account.
The bank account is active in Cash Management.
The test user has the appropriate manual bank statement entry security/role.
Valid reference data — currency, transaction types — is available for entry.

Exact setup, manual-entry permissions and field availability may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Bank Account	${BANK_ACCOUNT}
Statement Number	${STATEMENT_NUMBER}
Statement Date	${STATEMENT_DATE}
Currency	${CURRENCY}
Transaction Lines (Debit/Credit, Amount, Reference)	${TRANSACTION_LINES}
Opening Balance	${OPENING_BALANCE}
Closing Balance	${CLOSING_BALANCE}

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

Test Steps

12 business-readable steps. SyntraFlow's automation executes ~32 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	Initiate Manual Statement Entry Initiate manual bank statement entry.	The Create Bank Statement page opens for manual entry.
5	Select the Bank Account Select the bank account the statement will be manually entered against. ${BANK_ACCOUNT}	The correct bank account is selected and manual entry fields are made available.
6	Enter Statement Header Enter the statement header — statement number, statement date, currency and opening balance. ${STATEMENT_NUMBER}, ${STATEMENT_DATE}, ${CURRENCY}, ${OPENING_BALANCE} This single business step replaces multiple technical actions such as focusing each header field, entering its value and confirming it individually.	All statement header fields are accepted.
7	Enter Transaction Line(s) Enter one or more transaction lines — debit or credit, amount and reference. ${TRANSACTION_LINES} This single business step replaces multiple technical actions such as opening Add Line, selecting debit or credit, entering the amount and entering the reference for each line.	Each transaction line is accepted and added to the statement.
8	Enter Closing Balance Enter the statement closing balance. ${CLOSING_BALANCE}	The closing balance is accepted.
9	Verify Statement Totals Are Consistent Review the entered transaction lines against the opening and closing balances.	Transaction totals are internally consistent — opening balance plus entered lines equals the entered closing balance.
10	Save the Manual Statement Select Save.	Oracle Fusion successfully processes the save request without unexpected errors.
11	Validate the Manual Statement Submit or trigger validation of the saved manual statement.	The manual statement is accepted into the same validation flow used for imported statements.
12	Verify Statement StatusBusiness assertion Confirm the generated statement identifier and verify the manual statement's status. This is the main business assertion for the scenario — the test does not stop merely because Save was clicked successfully.	The manual statement is successfully created, can be identified by its statement number, and is available for the same downstream validation and processing lifecycle as an imported statement.

Expected Results

Oracle Fusion successfully creates a manual bank statement using the entered header and transaction line data.
Correct bank account is associated with the manually entered statement.
Statement number, date, currency and opening balance are retained.
Entered transaction lines are accepted and reflect the intended debit/credit amounts and references.
Transaction totals reconcile with the entered opening and closing balances.
No unexpected save errors occur.
The manually entered statement can be identified or retrieved after Save.
The statement is available for the same validation, processing and inquiry lifecycle as an imported statement.

Key Validation Checkpoints

Bank account matches the intended test data.
Manual entry is permitted for the selected bank account.
Statement number is populated correctly.
Statement date is correct.
Currency matches the account's configured currency.
Opening balance is correct.
Each transaction line's debit/credit type, amount and reference are correct.
Closing balance equals opening balance plus entered transaction lines.
Save acknowledgement is received.
Statement record exists and is available for validation after Save.

Core Business Scenario

Manual Bank Statement Entry

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 manual bank statement entry 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 manual entry test dozens of times simply to cover different combinations of bank account, currency, transaction line type, reference 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 — Bank Accounts, Currencies, Transaction Types and reference values, 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, boundary 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 manual entry 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 Manual Bank Statement Entry 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

Create single-line statement
Create multi-line statement
Debit transaction
Credit transaction
Different currencies
Different dates
Different bank accounts
Different transaction references
Valid opening/closing balance

Negative Scenarios

Invalid bank account
Missing statement number
Invalid currency
Invalid date
Closing balance mismatch
Missing transaction amount
Invalid transaction type
Duplicate statement number
Invalid line details

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 configuration of a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault — Bank Account, Currency and reference values — to create manual entry variations relevant to the customer's actual implementation.

Standard Library Definition

Bank Account       ${BANK_ACCOUNT}
Statement Number   ${STATEMENT_NUMBER}
Statement Date     ${STATEMENT_DATE}
Currency           ${CURRENCY}
Transaction Lines  ${TRANSACTION_LINES}
Opening Balance    ${OPENING_BALANCE}
Closing Balance    ${CLOSING_BALANCE}

DataVault

Bank Accounts
  Operating Account (USD)
  Payroll Account (GBP)
  Regional Account (EUR)
Currencies
  USD
  GBP
  EUR
Transaction Types
  Deposit
  Withdrawal
  Transfer
Reference Values
  Representative reference/description text per bank account

Jarvis AI Generates

Scenario 01 — Operating Account + USD + Single Debit Line
Scenario 02 — Payroll Account + GBP + Multi-Line Statement
Scenario 03 — Regional Account + EUR + Credit Line
Scenario 04 — Invalid Bank Account
Scenario 05 — Closing Balance Mismatch
Scenario 06 — Duplicate Statement Number
...

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

Example Test Variations

Representative examples of manual entry 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	Single-Line Manual Statement	Positive	One manually entered transaction line	Syntra Ready
VAR-002	Multi-Line Manual Statement	Positive	Multiple manually entered transaction lines	Syntra Ready
VAR-003	Debit Transaction Line	Positive	Manually entered debit line	Syntra Ready
VAR-004	Credit Transaction Line	Positive	Manually entered credit line	Syntra Ready
VAR-005	USD Statement	Positive/Currency	Currency = USD	Syntra Ready
VAR-006	EUR Statement	Positive/Currency	Currency = EUR	Syntra Ready
VAR-007	GBP Statement	Positive/Currency	Currency = GBP	Syntra Ready
VAR-008	Different Statement Date	Positive	Statement date within an open period, differing from a prior entry	Syntra Ready
VAR-009	Alternate Bank Account	Positive/Account	Different active bank account selected	Syntra Ready
VAR-010	Different Transaction Reference	Positive	Unique reference value entered per transaction line	Syntra Ready
VAR-011	Valid Opening/Closing Balance	Positive/Balance	Closing balance equals opening balance plus entered lines	Syntra Ready
VAR-012	Invalid Bank Account	Negative/Account	Bank account does not exist or is inactive	Syntra Ready
VAR-013	Missing Statement Number	Negative	Required statement number left blank	Syntra Ready
VAR-014	Invalid Currency	Negative/Currency	Currency not configured for the selected bank account	Syntra Ready
VAR-015	Invalid Statement Date	Negative	Statement date outside a valid or open period	Syntra Ready
VAR-016	Closing Balance Mismatch	Negative/Balance	Closing balance does not equal opening balance plus entered lines	Syntra Ready
VAR-017	Missing Transaction Amount	Negative	Required transaction line amount left blank	Syntra Ready
VAR-018	Invalid Transaction Type	Negative	Transaction type/code not recognized	Syntra Ready
VAR-019	Duplicate Statement Number	Negative/Duplicate	Statement number already exists for this bank account	Syntra Ready
VAR-020	Invalid Line Details	Negative	Transaction line reference fails required format/validation	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete manual statement creation.

Valid Bank Account + Balanced Transaction Line(s) + Valid Opening/Closing Balance → Statement Created Successfully

Negative Testing

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

Closing Balance Mismatch → Expected Balance Validation
Duplicate Statement Number → Expected Duplicate Validation
Missing Statement Number → Expected Required-Field Validation

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

Scenario	Oracle Outcome	Test Result
Valid single-line statement entry	Statement created successfully	PASS
Closing balance mismatch	Expected balance validation appears	PASS
Duplicate statement number	Duplicate validation occurs	PASS
Unexpected save error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Manual Bank Statement Entry Regression Pack

Single-Line Manual Statement
Multi-Line Manual Statement
Debit Transaction Line
Credit Transaction Line
USD Statement
EUR Statement
Alternate Bank Account
Valid Opening/Closing Balance
Duplicate Statement Number
Closing Balance Mismatch

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	Manual Bank Statement Entry Regression Pack
Schedule	Nightly 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

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 — Manual Bank Statement Entry, 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

Enter Statement Header

May internally include

Focus Statement Number → Enter Number → Open Date Picker → Select Date → Select Currency → Enter Opening Balance

Business Step

Enter Transaction Line(s)

May internally include

Open Add Line → Select Debit/Credit → Enter Amount → Enter Reference → Confirm Line → Repeat for Additional Lines

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 Closing Balance	Pass	—
Click Save	Pass	—
Verify Statement Status	Pass	Pass

Related Bank Statement Tests

Manual entry feeds into the same downstream validation, processing and inquiry stages as an imported statement — explore the related scenarios below.

Validate Bank Statement Process Bank Statement Bank Statement Inquiry Import Bank Statement

Turn This Standard Test into Your Oracle Cash Management Regression Suite

Start with the Syntra Standard manual bank statement entry 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

When is manual bank statement entry used instead of import?

Manual entry is used for bank accounts where the customer's business process does not use a file-based import or automated feed, or as a fallback when an import file is unavailable or delayed. Whether manual entry is permitted for a given bank account depends on the customer's Oracle Fusion configuration.

Does a manually entered statement follow the same validation as an imported statement?

Yes. Once saved, a manually entered statement enters the same validation and processing lifecycle used for imported statements — Manual Entry → Validate → Process → Inquiry.

Can this test create a multi-line manual statement?

Yes. The scenario supports entering one or more transaction lines per statement, including combinations of debit and credit lines, as covered by the positive test variations.

Does manual entry skip the Import and Parse stages of the bank statement lifecycle?

Yes. Manual entry is an alternate entry point that bypasses the Import and Parse stages used for file-based statements, since there is no file to import or parse. It feeds directly into Validate.

How are the many manual entry test variations generated?

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

Can this Oracle Fusion manual bank statement entry test be scheduled?

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