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

Syntra Standard Oracle Test Library

Oracle Fusion Create Receivables Transaction Test Cases

Validate Oracle Fusion Receivables transaction creation across customer, business unit, transaction type, currency, payment terms, invoice lines, tax and accounting combinations using reusable automated test scenarios.

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

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 14 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 Accounts Receivable user can successfully create a valid Receivables transaction in Oracle Fusion Receivables using valid business unit, transaction source, transaction type, customer, transaction line, tax and accounting information.

The scenario should confirm that:

the selected Business Unit is accepted
a valid Transaction Source and Transaction Type can be selected
the correct Customer and Customer Site can be selected
the transaction date is accepted for an open accounting period
the transaction currency and payment terms are accepted
transaction line, quantity and unit price information can be entered
applicable tax is calculated and applied where relevant
a valid Receivable and Revenue account combination is assigned
the transaction can be saved and completed successfully
the completed transaction is available for subsequent lifecycle processing

This scenario does not claim that the transaction is transferred to the general ledger, applied to a receipt or included in dunning and collections — those are separate downstream test cases.

When to Use This Test

Functional testing of a new Oracle Fusion Receivables implementation
Regression testing after an Oracle quarterly update
UAT sign-off for Accounts Receivable transaction entry
Baseline case referenced by credit memo, debit memo and transaction adjustment variations

Where This Test Fits in the Order-to-Cash Process

Customer

→

Transaction Creation

→

Completion

→

Accounting

→

Receipt Application

→

Collections

→

Reconciliation

This test covers Receivables transaction creation only, and serves as a prerequisite for subsequent completion, accounting, receipt application and collections scenarios.

Next Stage →

Credit Memo

Preconditions

Oracle Fusion Receivables is configured and available.
Relevant Business Unit exists and is active for Receivables.
Customer exists and is active.
Customer Site (Bill-to) is active and valid for the Business Unit.
Transaction Type is configured and active.
Transaction Source is configured and active.
Accounting period is open.
Valid Receivable and Revenue account combination is available.
The test user has permission to create Receivables transactions.

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

Sample Test Data

Business Unit	Active Receivables Business Unit
Customer	Active customer
Customer Site	Valid Bill-to site
Currency	Enabled transaction currency
Transaction Type	Valid AR transaction type
Transaction Source	Active transaction source
Payment Terms	Active payment terms
Transaction Date	Valid date within an open accounting period
Amount	Scenario-defined quantity and unit price
Account	Valid Receivable / Revenue account combination

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

Test Steps

14 business-readable steps. SyntraFlow's automation executes ~40 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 Accounts Receivable test user.	Oracle Fusion home page is displayed successfully and the user session is established.
2	Navigate to Receivables Navigate to the Receivables work area.	The Receivables work area opens successfully.
3	Open Billing Open the Billing task and select Create Transaction.	The Create Transaction page is displayed.
4	Create a New Transaction Start a new Receivables transaction.	A blank transaction entry form is displayed and ready for input.
5	Select Business Unit Select or enter the required Business Unit for the transaction. ${BUSINESS_UNIT}	The Business Unit is accepted and transaction-entry fields are available.
6	Select Transaction Source and Transaction Type Select the required Transaction Source and Transaction Type for the transaction. ${TRANSACTION_SOURCE} / ${TRANSACTION_TYPE}	Transaction Source and Transaction Type are accepted and related defaults are applied where configured.
7	Select Customer and Bill-to Site Open Customer search, search for the required customer, select the customer and confirm the Bill-to site. ${CUSTOMER} / ${CUSTOMER_SITE} This single business step replaces multiple technical actions such as opening search, entering the customer, clicking Search, selecting the result and confirming the site.	The correct customer and Bill-to site are selected and customer-related details are populated or available.
8	Enter Transaction Date Select or enter the transaction date. ${TRANSACTION_DATE} The automation may use several date-picker actions internally. Individual increment/decrement actions are not exposed as separate business test steps.	The required transaction date is populated correctly and falls within an open accounting period.
9	Enter Transaction Line Details Enter the description and item or memo line details for transaction line 1. ${LINE_DESCRIPTION}	Line details are accepted and retained.
10	Enter Quantity and Unit Price Enter the quantity and unit price for the transaction line. ${QUANTITY} / ${UNIT_PRICE}	Quantity and unit price are accepted and the line amount is calculated correctly.
11	Validate Tax and Accounting Distributions Review the tax calculated on the line, where applicable, and enter or confirm the Receivable and Revenue account distributions. ${ACCOUNT_COMBINATION}	Tax is calculated correctly where applicable, and the accounting distribution is accepted without unexpected validation errors.
12	Save the Transaction Select Save.	Oracle Fusion successfully processes the save request without unexpected errors.
13	Complete the Transaction Select Complete to finalize the transaction.	The transaction is completed and its status changes to Complete.
14	Verify Transaction Number and StatusBusiness assertion Confirm the Oracle save and completion acknowledgement and verify that the newly created transaction record is available with an assigned transaction number. This is the main business assertion for the scenario — the test does not stop merely because Save or Complete was clicked successfully.	The transaction is successfully created and can be identified by the assigned transaction number, with a status of Complete. Where technically possible, the transaction is retrieved or confirmed after completion.

Expected Results

Oracle Fusion successfully creates the Receivables transaction using the selected test data.
Correct Business Unit, Customer and Customer Site are associated with the transaction.
Transaction line, quantity, unit price and tax are recorded and calculated correctly.
Valid Receivable and Revenue account combination is associated with the transaction.
The transaction is completed and assigned a transaction number.
No unexpected save or completion errors occur.
The newly created transaction can be identified or retrieved after completion.

Key Validation Checkpoints

Business Unit matches the intended test data.
Customer and Customer Site selection is correct.
Transaction Type and Transaction Source are correct.
Transaction date falls within an open accounting period.
Currency and payment terms are correct.
Line quantity and unit price are correct.
Tax is calculated where applicable.
Receivable and Revenue accounts are valid.
Save and Complete acknowledgements are received.
Transaction record exists with an assigned transaction number after completion.

Core Business Scenario

Create Receivables Transaction

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 Receivables transaction creation 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, where connected.

Teams do not need to manually duplicate the same test case dozens of times simply to cover different combinations of customer, business unit, currency, payment terms, transaction type, tax or invalid conditions. Jarvis uses the standard business scenario as the foundation and can generate 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

Where connected, can provide approved customer-specific test data and configuration required for scenario generation — Business Units, Customers, Customer Sites, Currencies, Payment Terms, Transaction Types, Accounting combinations, Tax configurations and other relevant test attributes.

Jarvis AI

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

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

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

Results + Evidence + Exceptions

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

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

AI-Generated Test Variations

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

Positive Scenarios

Different active customers
Different Business Units
Different currencies
Different payment terms
Single-line transaction
Multi-line transaction
Different transaction types
Different transaction sources
Taxable transaction
Non-taxable transaction
Different Customer Sites
Multiple accounting distributions

Negative Scenarios

Missing customer
Invalid customer site
Missing transaction type
Invalid account combination
Closed accounting period
Invalid transaction amount
Mandatory field missing

These are representative examples only. Only scenarios that are valid Oracle business cases are included, and 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 Syntra DataVault is connected and configured, Jarvis can use approved customer-specific implementation data — protected according to DataVault policies — to create variations relevant to the customer's actual Receivables setup.

Standard Library Definition

Business Unit    ${BUSINESS_UNIT}
Customer         ${CUSTOMER}
Customer Site    ${CUSTOMER_SITE}
Transaction Type ${TRANSACTION_TYPE}
Currency         ${CURRENCY}
Payment Terms    ${PAYMENT_TERMS}
Account          ${ACCOUNT_COMBINATION}
Tax              ${TAX_CODE}

DataVault

Business Units
  US Operations
  UK Operations
Customers
  Customer A
  Customer B
  Customer C
Currencies
  USD
  GBP
  EUR
Payment Terms
  Net 30
  Net 45
  Immediate
Tax Codes
  Standard
  Exempt
Accounting
  Valid configured combinations

Jarvis AI Generates

Scenario 01 — UK Operations + Customer A + GBP + Net 30
Scenario 02 — US Operations + Customer B + USD + Net 45
Scenario 03 — Multi-Line + Customer C + EUR
Scenario 04 — Taxable Transaction + Standard Tax Code
Scenario 05 — Missing Customer
Scenario 06 — Invalid Account Combination
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer data remains protected according to that customer's DataVault policies and is used only 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	Basic Standard Transaction	Positive	Single line / valid customer	Syntra Ready
VAR-002	Multi-Line Transaction	Positive	Multiple transaction lines	Syntra Ready
VAR-003	GBP Transaction	Positive/Currency	GBP currency	Syntra Ready
VAR-004	EUR Transaction	Positive/Currency	EUR currency	Syntra Ready
VAR-005	INR Transaction	Positive/Currency	INR currency	Syntra Ready
VAR-006	Net 45 Payment Terms	Positive	Net 45 payment terms	Syntra Ready
VAR-007	Immediate Payment Terms	Positive	Immediate payment terms	Syntra Ready
VAR-008	Alternate Business Unit	Positive	Different Business Unit	Syntra Ready
VAR-009	Alternate Customer Site	Positive/Customer	Different Bill-to site	Syntra Ready
VAR-010	Second Active Customer	Positive/Customer	Different active customer	Syntra Ready
VAR-011	Taxable Transaction	Positive/Tax	Tax calculated on line	Syntra Ready
VAR-012	Non-Taxable Transaction	Positive/Tax	Tax-exempt customer or item	Syntra Ready
VAR-013	Alternate Transaction Type	Positive	Different valid transaction type	Syntra Ready
VAR-014	Alternate Transaction Source	Positive	Different active transaction source	Syntra Ready
VAR-015	Multiple Accounting Distributions	Positive/Accounting	Split Receivable/Revenue accounts	Syntra Ready
VAR-016	Missing Customer	Negative/Customer	Required customer not selected	Syntra Ready
VAR-017	Invalid Customer Site	Negative/Customer	Site not valid for Business Unit	Syntra Ready
VAR-018	Missing Transaction Type	Negative	Required transaction type not selected	Syntra Ready
VAR-019	Invalid Account Combination	Negative/Accounting	Invalid Receivable/Revenue account	Syntra Ready
VAR-020	Closed Accounting Period	Negative	Transaction date outside open period	Syntra Ready
VAR-021	Invalid Transaction Amount	Negative/Boundary	Negative or non-numeric line amount	Syntra Ready
VAR-022	Missing Mandatory Line Data	Negative	Required line field left blank	Syntra Ready
VAR-023	Near-Zero Amount Line	Boundary	Minimal valid line amount	Syntra Ready
VAR-024	High-Value Transaction	Boundary	Large transaction amount	Syntra Ready
VAR-025	Maximum Practical Line Count	Boundary	Large number of transaction lines	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the business process.

Valid Customer + Valid BU + Valid Currency + Valid Account → Transaction Created

Negative Testing

Jarvis can generate scenarios designed to exercise validations, business rules and exception handling.

Missing Customer → Expected Required-Field Validation
Invalid Account Combination → Expected Accounting Validation
Closed Accounting Period → Expected Period-Status Validation

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

Scenario	Oracle Outcome	Test Result
Valid standard transaction	Transaction created	PASS
Missing customer	Required-field validation displayed	PASS
Invalid account combination	Accounting validation displayed	PASS
Closed accounting period	Period-status validation displayed	PASS
Unexpected application error	Unexpected error	FAIL

Turn AI-Generated Variations into a Regression Pack

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

AR Billing Transaction Regression Pack

Basic Standard Transaction
Multi-Line Transaction
GBP Transaction
EUR Transaction
Taxable Transaction
Multiple Accounting Distributions
Missing Customer
Invalid Account Combination
Closed Accounting Period
Missing Mandatory Line Data

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

Run On-Demand or Schedule Automated Batch Execution

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

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

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

Pack	AR Billing Transaction Regression Pack
Schedule	Quarterly Update 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

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 — Create Receivables Transaction, 14 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 Customer and Bill-to Site

May internally include

Open Customer Search → Enter Customer → Search → Select Customer → Select Bill-to Site → Confirm

Business Step

Enter Transaction Date

May internally include

Open Date Field → Open Date Picker → Navigate Month → Select Date

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 Transaction Line Amount	Pass	—
Click Save	Pass	—
Verify Transaction Created	Pass	Pass

Continue Testing the AR Billing Lifecycle

This scenario is part of the same Receivables billing lifecycle — explore the related transaction types and downstream processing scenarios below.

Credit Memo Debit Memo Transaction Adjustments Transaction Completion Transaction Accounting

Turn This Standard Test into Your Oracle Regression Suite

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

Automate with SyntraFlow Explore AR Billing 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

Accounts Receivable Billing Accounts Receivable Test Library Oracle AR Testing Tool Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What does this test validate?

This scenario verifies that a valid Receivables transaction can be created in Oracle Fusion using a valid Business Unit, Transaction Source, Transaction Type, Customer, Customer Site, transaction line, tax and accounting information, and that the transaction can be saved and completed successfully.

Can this run against different currencies and payment terms?

Yes. The standard scenario can be parameterised with different enabled currencies and active payment terms, and Jarvis can generate representative variations covering common combinations.

How are test variations generated?

Jarvis AI uses this standard business scenario together with available DataVault test data and configuration to generate additional positive, negative and boundary variations designed to reflect the customer's Receivables setup.

Does this test use real customer data?

The public Syntra Standard Test Library uses illustrative, non-production examples only. Where a customer connects Syntra DataVault, customer-specific implementation data can be used for generated variations and is handled according to that customer's DataVault configuration and data protection policies, not exposed on this public page.

Can this be scheduled as part of a regression pack?

Yes. This scenario and its generated variations can be grouped into a regression pack and executed on demand or on a schedule, such as nightly, before a release or after a quarterly Oracle update.

Does this test validate downstream accounting or receipt application?

No. This scenario focuses on transaction creation and completion only. Transfer to the general ledger, receipt application and collections activity are covered by separate downstream test scenarios.