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

Syntra Standard Oracle Test Library

Oracle Fusion Complete & Incomplete Transaction Test Cases

Validate Oracle Receivables transaction completion, incompletion and prerequisite business rules — confirming that a valid transaction can be completed successfully and that transactions with missing or invalid prerequisite data are correctly blocked from completion.

Test ID	ORCL.O2C.AR.BILL.TXN.COMPLETE
Application	Oracle Fusion Cloud
Product	Receivables
Module	Accounts Receivable
Process	Billing
Business Flow	Order-to-Cash
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 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 36 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify Oracle Receivables transaction completion, incompletion and prerequisite business rules — confirming that an authorised Receivables user can successfully complete a valid transaction, and that Oracle Fusion correctly blocks completion when required prerequisite data such as customer, accounting or transaction line information is missing or invalid.

The scenario should confirm that:

the transaction date falls within an open accounting period
a valid customer and customer site are associated with the transaction
required accounting information is present and valid
transaction lines are complete and internally consistent
the transaction can be completed successfully when all prerequisite data is valid
completion is correctly blocked when required customer, accounting, line or date data is missing or invalid
the transaction's completion status accurately reflects the underlying data condition
a transaction number is assigned and retained after successful completion

This scenario focuses on the completion/incompletion decision itself and the prerequisite business rules that govern it — it does not claim to validate downstream transaction accounting, receipt application or revenue recognition, which are covered by separate 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 Receivables transaction completion
Baseline case referenced by transaction accounting and downstream Order-to-Cash variations

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

Customer Setup

→

Transaction Creation

→

Transaction Completion

→

Transaction Accounting

→

Receipt Application

→

Collections

→

Revenue Recognition

This test covers the completion and incompletion decision for a Receivables transaction, and serves as a prerequisite gate before accounting, receipt application and downstream Order-to-Cash processing.

← Previous Stage

Transaction Adjustments

Next Stage →

Transaction Accounting

Preconditions

Oracle Fusion Receivables is configured and available.
The test user has permission to complete Receivables transactions.
A valid draft/incomplete transaction exists and is ready for completion.
Customer exists, is active, and has the required data configured.
Customer site is active and valid for the transaction.
Accounting period is open for the transaction date.
A valid account combination is available for accounting.
All mandatory transaction header and line fields are populated (for the positive completion path).

Exact field requirements and completion business rules may vary by Oracle Fusion Receivables configuration and implementation.

Sample Test Data

Transaction	Draft/incomplete transaction ready for completion
Customer Information	Complete and valid
Accounting Information	Valid account combination
Accounting Period	Open
Transaction Date	Valid/open-period date
Missing Field Scenario	Scenario-defined — e.g. missing customer or accounting information for negative cases

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 ~36 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 Receivables test user.	Oracle Fusion home page is displayed successfully and the user session is established.
2	Navigate to Receivables Open the Navigator and navigate to the Receivables work area.	The Receivables work area opens successfully.
3	Open Billing Open the Billing task within Receivables and access the transactions list.	The Billing transactions list is displayed.
4	Locate the Draft/Incomplete Transaction Search for and open the draft or incomplete transaction identified for completion testing. ${TRANSACTION_NUMBER} This single business step replaces multiple technical actions such as opening search, entering the transaction number, clicking Search and selecting the result.	The correct transaction is located and opened.
5	Review Transaction Header and Line Data Review the transaction date, customer, customer site, accounting information and transaction lines.	Transaction header and line data are displayed and available for review.
6	Verify Required Fields Are Populated Confirm whether fields required for completion — transaction date, customer, customer site, accounting information and transaction lines — are populated as defined for this scenario.	Required fields are populated as defined for the scenario — complete for positive cases, intentionally missing or invalid for negative cases.
7	Attempt Transaction Completion Select Complete on the transaction.	Oracle Fusion processes the completion request.
8	Validate Completion Business RulesBusiness assertion Allow Oracle to evaluate prerequisite completion business rules — accounting period status, customer and customer site validity, accounting information and transaction line completeness. This is a core business assertion — the scenario evaluates whether Oracle's rule evaluation matches the expected outcome for the data provided, not merely whether the Complete action was clicked.	Oracle correctly applies completion business rules based on the data present on the transaction.
9	Review Completion StatusBusiness assertion Review the resulting transaction status after the completion attempt.	For valid, complete data the transaction status changes to Complete. For missing or invalid prerequisite data the transaction remains Incomplete.
10	Review the Exception/Error Reason (If Incomplete) Where completion is blocked, review the exception or error message returned by Oracle.	The exception/error reason correctly identifies the missing or invalid prerequisite data.
11	Correct Missing/Invalid Data Where Applicable For scenarios that require it, correct the missing or invalid field identified in the exception. ${CORRECTED_FIELD_VALUE}	The corrected field value is accepted.
12	Re-Attempt Completion Select Complete again after correcting the data.	Oracle Fusion re-processes the completion request.
13	Validate Final Transaction StatusBusiness assertion Confirm the final transaction status following the completion attempt(s).	The final status matches the expected outcome for the scenario — Complete for corrected/valid data, Incomplete where the scenario intentionally leaves prerequisite data missing or invalid.
14	Validate Transaction Number Assignment on Successful CompletionBusiness assertion Where the transaction completes successfully, confirm the transaction number is assigned or retained. This is the main business assertion for the positive completion path — the test does not stop merely because Complete was clicked without error.	The transaction number is available and can be used by subsequent scenarios.

Expected Results

Oracle Fusion successfully completes a transaction when all required, valid prerequisite data is present and assigns/retains the transaction number.
Attempts to complete a transaction with missing or invalid customer, accounting, transaction line or date data are correctly blocked with an appropriate exception.
The transaction's completion status accurately reflects the underlying data condition.
Correcting the missing or invalid data and re-attempting completion succeeds.
No unexpected application errors occur during completion or blocked-completion scenarios.
Completed transactions are available for subsequent accounting and downstream Order-to-Cash processing.

Key Validation Checkpoints

Transaction date falls within an open accounting period.
Customer and customer site are valid and active.
Accounting information is present and valid.
Transaction lines are complete and consistent.
Completion is accepted only when prerequisite rules are satisfied.
Exception/error message correctly identifies the missing or invalid data.
Completion status accurately reflects the outcome.
Transaction number is assigned/retained on successful completion.
Corrected transactions can be successfully re-completed.
Incomplete transactions remain in Draft/Incomplete status until corrected.

Core Business Scenario

Complete & Incomplete Transactions

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 transaction completion scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations — covering different customers, accounting periods, transaction dates and missing-data conditions — using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same completion test case dozens of times simply to cover different customers, currencies, accounting periods or missing-field conditions. 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 for transaction completion.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Customers, Customer Sites, Accounting Periods, Transaction Dates, Account combinations 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 completion 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 completion 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 Complete & Incomplete Transactions 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

Complete a valid transaction with all required data
Re-complete a transaction after correcting missing/invalid data
Completion across different customers
Completion across different customer sites
Completion across different currencies
Completion within different open accounting periods
Completion of a single-line transaction
Completion of a multi-line transaction

Negative Scenarios

Attempt completion with missing customer information
Attempt completion with missing customer site
Attempt completion with missing accounting information
Attempt completion with an invalid or missing transaction date
Attempt completion in a closed accounting period
Attempt completion with missing transaction line data
Incomplete transaction remains in Draft status
Attempt completion with missing required tax information

These are representative examples only. Completion business rules 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. Jarvis can use approved test data available through Syntra DataVault — such as Customer, Accounting Period, Transaction Date and Account dimensions where configured and connected — to create completion variations relevant to the customer's actual implementation. Customer-specific data remains protected according to DataVault policies.

Standard Library Definition

Transaction        ${TRANSACTION_NUMBER}
Customer           ${CUSTOMER}
Customer Site      ${CUSTOMER_SITE}
Accounting Period  ${ACCOUNTING_PERIOD}
Transaction Date   ${TRANSACTION_DATE}
Accounting         ${ACCOUNT_COMBINATION}

DataVault

Customers
  Customer A
  Customer B
  Customer C
Customer Sites
  Bill-To Site 1
  Bill-To Site 2
Accounting Periods
  Open period(s) per calendar
Transaction Dates
  Valid dates within open period
Accounts
  Valid configured combinations

Jarvis AI Generates

Scenario 01 — Customer A + Open Period + Valid Accounting
Scenario 02 — Customer B + Missing Customer Site
Scenario 03 — Missing Accounting Information
Scenario 04 — Closed Accounting Period
Scenario 05 — Re-Completion After Correction
Scenario 06 — Multi-Line Transaction Completion
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is configured and connected, customer data used for generation remains within the customer's controlled SyntraFlow environment and is protected according to DataVault policies.

Example Test Variations

Representative examples of transaction completion 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 Transaction Completion	Positive	Single line / valid customer / valid accounting	Syntra Ready
VAR-002	Multi-Line Transaction Completion	Positive/Boundary	Multiple transaction lines	Syntra Ready
VAR-003	Completion for Alternate Customer	Positive/Customer	Different customer	Syntra Ready
VAR-004	Completion for Alternate Customer Site	Positive/Customer	Different customer site	Syntra Ready
VAR-005	EUR Currency Completion	Positive/Currency	EUR transaction currency	Syntra Ready
VAR-006	GBP Currency Completion	Positive/Currency	GBP transaction currency	Syntra Ready
VAR-007	Completion Within Open Accounting Period	Positive/Accounting	Transaction date within open period	Syntra Ready
VAR-008	Re-Completion After Correcting Missing Customer	Positive/Customer	Corrected customer, second completion attempt	Syntra Ready
VAR-009	Re-Completion After Correcting Accounting Information	Positive/Accounting	Corrected accounting distribution, second attempt	Syntra Ready
VAR-010	Completion With Applicable Tax	Positive/Tax	Valid tax determinants present	Syntra Ready
VAR-011	Missing Customer Information	Negative/Customer	Customer field not populated	Syntra Ready
VAR-012	Missing Customer Site	Negative/Customer	Customer site not populated	Syntra Ready
VAR-013	Missing Accounting Information	Negative/Accounting	Accounting distribution not populated	Syntra Ready
VAR-014	Invalid Transaction Date	Negative	Transaction date outside valid range	Syntra Ready
VAR-015	Missing Transaction Date	Negative	Transaction date field blank	Syntra Ready
VAR-016	Closed Accounting Period	Negative/Accounting	Transaction date falls in a closed period	Syntra Ready
VAR-017	Missing Transaction Line Data	Negative	Required line amount/item not populated	Syntra Ready
VAR-018	Missing Required Tax Information	Negative/Tax	Required tax classification missing	Syntra Ready
VAR-019	Incomplete Transaction Remains in Draft	Negative	No completion attempted, transaction left Incomplete	Syntra Ready
VAR-020	Invalid Customer Site for Transaction	Negative/Customer	Customer site not valid for the transaction	Syntra Ready
VAR-021	Maximum Practical Line Count Completion	Boundary	Transaction with a high number of lines	Syntra Ready
VAR-022	Completion at Accounting Period Boundary Date	Boundary/Accounting	Transaction date at the period close boundary	Syntra Ready

Automatically Expand Positive and Negative Completion Coverage

Positive Testing

Jarvis generates scenarios using data combinations expected to allow successful transaction completion.

Valid Customer + Valid Customer Site + Open Period + Valid Accounting → Transaction Completed

Negative Testing

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

Missing Customer → Expected Required-Field Validation
Missing Accounting Information → Expected Accounting Validation
Closed Accounting Period → Expected Period Status Validation

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

Scenario	Oracle Outcome	Test Result
Valid transaction with complete data	Transaction completed	PASS
Missing customer information	Required-field validation displayed	PASS
Missing accounting information	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 completion scenarios and group them into reusable execution packs.

AR Transaction Completion Regression Pack

Basic Transaction Completion
Multi-Line Transaction Completion
Multi-Customer Completion
Multi-Currency Completion
Re-Completion After Correction
Missing Customer Validation
Missing Accounting Validation
Closed Period Validation
Missing Tax Validation
Boundary Line-Count Completion

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 completion 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 Transaction Completion Regression Pack
Schedule	Quarterly Update Regression
Tests	38 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

112

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 transaction completion scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment.

Generate

Positive and negative completion 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 — Complete & Incomplete Transactions, 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

Locate the Draft/Incomplete Transaction

May internally include

Open Billing List → Apply Transaction Number Filter → Search → Select Transaction → Open

Business Step

Attempt Transaction Completion

May internally include

Click Complete → Wait for Rule Evaluation → Read Status/Message → Capture Result

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
Attempt Transaction Completion	Pass	—
Review Completion Status	Pass	—
Validate Transaction Number Assignment	Pass	Pass

Continue Testing the AR Billing Lifecycle

Complete & Incomplete Transactions works alongside the other core Accounts Receivable Billing scenarios in the Syntra Standard Test Library.

Create Transaction Credit Memo Debit Memo Transaction Adjustments Transaction Accounting

Turn This Standard Test into Your Oracle Receivables Regression Suite

Start with the Syntra Standard transaction completion 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 Accounts Receivable Billing

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 the Complete & Incomplete Transactions test case validate?

It validates that Oracle Fusion Receivables completes a transaction when all prerequisite data — transaction date, customer, customer site, accounting information and transaction lines — is valid, and that completion is correctly blocked when required data is missing or invalid.

What happens when required data is missing on an Oracle Receivables transaction?

Oracle Fusion is expected to block completion and return an exception identifying the missing or invalid prerequisite data. The transaction remains in Incomplete status until the data is corrected and completion is re-attempted.

What is the difference between a Draft, Incomplete and Completed transaction in Oracle Receivables?

A Draft or Incomplete transaction has not yet satisfied all prerequisite business rules for completion. A Completed transaction has passed those rules and is assigned a transaction number, making it available for downstream accounting and Order-to-Cash processing.

How are test variations for transaction completion generated?

Jarvis AI uses this standard business scenario together with available DataVault test data — such as Customer, Accounting Period, Transaction Date and Account dimensions where configured — to generate relevant positive and negative completion variations for the customer's environment.

Does this test use real customer data?

The public library page shows representative, illustrative examples only. Where Syntra DataVault is configured and connected, customer-specific test data used to generate variations remains within the customer's controlled environment and is protected according to DataVault policies.

Can transaction completion testing be scheduled?

Yes. Selected completion scenarios or regression packs can be scheduled for unattended batch execution — for example nightly, before a release, or ahead of a quarterly Oracle update.