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

Syntra Standard Oracle Test Library

Oracle Fusion Receivables Transaction Accounting Test Cases

Validate accounting generation and financial distributions associated with Receivables billing transactions.

Test ID	ORCL.O2C.AR.BILL.TXN.ACCOUNT
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 36 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that Oracle Fusion correctly generates accounting distributions for a completed Receivables billing transaction, including receivable, revenue and, where applicable, tax distributions using valid account combinations within an open accounting period.

The scenario should confirm that:

a valid, completed transaction is available and ready for accounting generation
a receivable distribution is generated using a valid account combination
a revenue distribution is generated using a valid account combination
a tax distribution is generated where applicable, using a valid account combination
the accounting period is open and accepts the accounting entries
generated distribution amounts reconcile to the transaction amount
the transaction's accounting status reflects successful generation
posting/transfer status is updated where applicable, subject to configuration

This scenario does not claim that every generated accounting entry is automatically valid for every Oracle Fusion configuration, or that transfer to General Ledger always completes automatically — those outcomes depend on the customer's subledger accounting rules, ledger setup and GL configuration.

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 accounting
Baseline case referenced by receipt application, collections and reconciliation scenarios

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

Order Entry

→

Transaction Creation

→

Transaction Completion

→

Transaction Accounting

→

Receipt Application

→

Collections

→

Reconciliation

This test covers accounting generation for a completed Receivables transaction and serves as a prerequisite for downstream receipt application, collections and reconciliation scenarios.

← Previous Stage

Transaction Completion

Preconditions

Oracle Fusion Receivables is configured and available.
The test user has access to Receivables and Billing functionality.
A valid, completed Receivables transaction exists and is ready for accounting.
The accounting period covering the transaction date is open.
Valid account combinations are configured for receivable, revenue and, where applicable, tax accounts.
Subledger accounting rules are configured for Receivables transactions.
An appropriate accounting method and ledger are assigned to the business unit.
The test user has permission to generate accounting for Receivables transactions.

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

Sample Test Data

Transaction	Completed AR transaction (e.g. SYN-AR-10045)
Receivable Account	Valid account combination (Receivable)
Revenue Account	Valid account combination (Revenue)
Tax Account	Valid account combination (Tax), where applicable
Accounting Period	Open (current test period)
Distribution Type	Receivable, Revenue, Tax, or Multiple

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 Navigate to the Receivables work area.	The Receivables work area opens successfully.
3	Open Billing Open the Billing task within Receivables.	The Manage Transactions / Billing page is displayed.
4	Locate the Completed Transaction Search for and open the completed Receivables transaction that requires accounting. ${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	Open the Transaction for Accounting Review Open the transaction's accounting and distributions view.	The transaction's accounting details are accessible for review.
6	Initiate Accounting Generation Initiate the accounting generation action for the transaction.	The accounting generation process starts without unexpected errors.
7	Review Receivable Distribution Review the receivable distribution generated for the transaction. ${RECEIVABLE_ACCOUNT}	A receivable distribution is present and uses a valid account combination.
8	Review Revenue Distribution Review the revenue distribution generated for the transaction. ${REVENUE_ACCOUNT}	A revenue distribution is present and uses a valid account combination.
9	Review Tax Distribution Where Applicable Review the tax distribution generated for the transaction, where tax applies. ${TAX_ACCOUNT}	A tax distribution is present and uses a valid account combination, where applicable.
10	Validate Account Combinations Validate that the receivable, revenue and tax account combinations used are valid and active.	All account combinations used are valid for the ledger and business unit.
11	Validate Accounting Period Status Confirm the accounting period covering the transaction date is open. ${ACCOUNTING_PERIOD}	The accounting period status is Open and accepts the accounting entries.
12	Generate / Create Accounting Complete the accounting generation (Create Accounting) for the transaction.	Oracle Fusion successfully processes the accounting generation request without unexpected errors.
13	Review Accounting Status Review the transaction's accounting status after generation.	Accounting status reflects successful generation (e.g. Accounted).
14	Validate Distribution Amounts ReconcileBusiness assertion Confirm that receivable, revenue and tax distribution amounts reconcile to the transaction amount, and confirm posting/transfer status where applicable. This is the main business assertion for the scenario — the test confirms both distribution accuracy and posting/transfer status where applicable, not merely that accounting generation was initiated.	Distribution amounts sum to the transaction total, and posting/transfer status is reflected where applicable, subject to configuration.

Expected Results

Oracle Fusion successfully generates accounting for the completed transaction.
A receivable distribution is generated using a valid account combination.
A revenue distribution is generated using a valid account combination.
A tax distribution is generated where applicable, using a valid account combination.
Distribution amounts reconcile to the transaction amount.
The accounting period accepts the transaction without period-status errors.
Accounting status reflects successful generation.
Posting/transfer status is updated where applicable, subject to configuration.
No unexpected accounting validation errors occur.

Key Validation Checkpoints

Transaction is complete and available for accounting.
Receivable distribution account combination is valid.
Revenue distribution account combination is valid.
Tax distribution account combination is valid, where applicable.
Distribution amounts sum to the transaction total.
Accounting period status is Open.
Accounting status updates to reflect successful generation.
Posting/transfer status is reflected where applicable.

Core Business Scenario

Receivables Transaction Accounting

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 business scenario for generating accounting on a completed Receivables transaction. 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 test case dozens of times simply to cover different combinations of transaction type, account combination, currency, customer, business unit or accounting period. 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 Receivables transaction accounting.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Transactions, Account Combinations, Currencies, Accounting Periods, Customers 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 Receivables transaction accounting scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Receivables Transaction Accounting 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

Generate accounting for a standard completed transaction
Receivable distribution generated using a valid account combination
Revenue distribution generated using a valid account combination
Tax distribution generated where applicable
Multiple/combined distributions on a single transaction
Accounting for different customers and business units
Accounting across different currencies
Accounting for multi-line transactions
Successful transfer/posting to General Ledger, where applicable

Negative Scenarios

Invalid receivable, revenue or tax account combination
Closed accounting period
Accounting validation failure
Missing required distribution
Transaction not eligible for accounting (incomplete or on hold)

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, controls and subledger accounting rules — not every Oracle configuration behaves identically, and generated accounting is not automatically valid for GL posting in every configuration.

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 to create variations relevant to the customer's actual implementation.

Standard Library Definition

Transaction         ${TRANSACTION}
Receivable Account  ${RECEIVABLE_ACCOUNT}
Revenue Account     ${REVENUE_ACCOUNT}
Tax Account         ${TAX_ACCOUNT}
Accounting Period   ${ACCOUNTING_PERIOD}
Distribution Type   ${DISTRIBUTION_TYPE}

DataVault

Transactions
  Completed AR Transactions (by Business Unit)
Account Combinations
  Receivable / Revenue / Tax (valid, configured)
Currencies
  USD
  GBP
  EUR
Accounting Periods
  Open / Closed (by ledger)
Customers
  Customer A
  Customer B
  Customer C

Jarvis AI Generates

Scenario 01 — Standard Accounting Generation, USD, Customer A
Scenario 02 — Multi-Distribution (Receivable+Revenue+Tax), Customer B
Scenario 03 — GBP Transaction Accounting
Scenario 04 — Closed Accounting Period (Negative)
Scenario 05 — Invalid Account Combination (Negative)
...

Customer-specific transaction and account data used to generate variations are not published to the Syntra Standard Test Library and remain within the customer's controlled SyntraFlow environment and access model, subject to DataVault policies including data masking where configured.

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	Standard Accounting Generation	Positive/Accounting	Single transaction, standard distributions	Syntra Ready
VAR-002	Receivable Distribution Only	Positive/Accounting	Receivable distribution generated	Syntra Ready
VAR-003	Revenue Distribution	Positive/Accounting	Revenue distribution generated	Syntra Ready
VAR-004	Tax Distribution	Positive/Tax/Accounting	Tax distribution generated where applicable	Syntra Ready
VAR-005	Multiple Combined Distributions	Positive/Accounting	Receivable + revenue + tax combined	Syntra Ready
VAR-006	GBP Transaction Accounting	Positive/Currency	GBP currency	Syntra Ready
VAR-007	EUR Transaction Accounting	Positive/Currency	EUR currency	Syntra Ready
VAR-008	Accounting for Customer A	Positive/Customer	Business-unit specific customer	Syntra Ready
VAR-009	Accounting for Customer B	Positive/Customer	Different customer / business unit	Syntra Ready
VAR-010	Multi-Line Transaction Accounting	Positive/Accounting	Transaction with multiple lines	Syntra Ready
VAR-011	Zero-Tax Transaction Accounting	Positive/Boundary/Tax	No tax applicable	Syntra Ready
VAR-012	Maximum Distribution Lines	Positive/Boundary/Accounting	Large number of distribution lines	Syntra Ready
VAR-013	Successful Transfer to General Ledger	Positive/Accounting	Posting/transfer status updated, where applicable	Syntra Ready
VAR-014	Accounting for Alternate Business Unit	Positive/Accounting/Customer	Different business unit	Syntra Ready
VAR-015	Tax-Exempt Transaction Accounting	Positive/Tax	Tax-exempt customer or transaction	Syntra Ready
VAR-016	Standard Recurring Transaction Accounting	Positive/Accounting	Standard recurring transaction type	Syntra Ready
VAR-017	Invalid Receivable Account	Negative/Accounting	Invalid receivable account combination	Syntra Ready
VAR-018	Invalid Revenue Account	Negative/Accounting	Invalid revenue account combination	Syntra Ready
VAR-019	Closed Accounting Period	Negative/Accounting	Accounting period closed	Syntra Ready
VAR-020	Accounting Validation Failure	Negative/Accounting	Expected validation error on generation	Syntra Ready
VAR-021	Missing Required Distribution	Negative/Accounting	Required distribution not generated	Syntra Ready
VAR-022	Transaction Not Eligible for Accounting	Negative	Transaction incomplete or on hold	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete transaction accounting.

Completed Transaction + Valid Receivable/Revenue/Tax Accounts + Open Period → Accounting Generated

Negative Testing

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

Invalid Account Combination → Expected Accounting Validation
Closed Accounting Period → Expected Period-Status Validation
Transaction Not Eligible → Expected Eligibility Validation

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

Scenario	Oracle Outcome	Test Result
Standard completed transaction	Accounting generated	PASS
Invalid account combination	Accounting validation displayed	PASS
Closed accounting period	Period-status validation displayed	PASS
Transaction not eligible for accounting	Eligibility 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 Transaction Accounting Regression Pack

Standard Accounting Generation
Receivable Distribution Only
Revenue Distribution
Tax Distribution
Multiple Combined Distributions
GBP Transaction Accounting
Multi-Line Transaction Accounting
Invalid Receivable Account
Closed Accounting Period
Missing Required Distribution

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 Transaction Accounting Regression Pack
Schedule	Quarterly Update Regression
Tests	36 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

108

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 — Receivables Transaction Accounting, 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 Completed Transaction

May internally include

Open Billing Work Area → Open Transactions Search → Enter Transaction Number → Search → Select Transaction

Business Step

Review Receivable, Revenue and Tax Distributions

May internally include

Open Distributions Tab → Expand Receivable Lines → Expand Revenue Lines → Expand Tax Lines → Capture Amounts

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
Initiate Accounting Generation	Pass	—
Generate Accounting	Pass	—
Verify Distributions Reconcile	Pass	Pass

Continue Testing the AR Billing Lifecycle

Part of the same Order-to-Cash Receivables billing lifecycle. All five related scenarios below are live pages in the Syntra Standard Test Library.

Create Transaction Credit Memo Debit Memo Transaction Adjustments Transaction Completion

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 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

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

Frequently Asked Questions

What does the Receivables Transaction Accounting test validate?

It validates that Oracle Fusion correctly generates accounting distributions — receivable, revenue and, where applicable, tax — for a completed Receivables billing transaction, using valid account combinations within an open accounting period.

What accounting distributions are generated for a Receivables transaction?

A Receivables transaction typically generates a receivable distribution and one or more revenue distributions, plus a tax distribution where tax applies. Distribution structure depends on the transaction lines and the customer's subledger accounting configuration.

Does this test validate posting to the General Ledger?

This test validates that accounting is generated and that distribution amounts reconcile to the transaction, and checks posting/transfer status where applicable. It does not claim that transfer to General Ledger always completes automatically — that depends on the customer's subledger accounting rules and GL configuration.

How are test variations for transaction accounting generated?

Jarvis uses this standard business scenario together with available DataVault test data — transactions, account combinations, currencies and accounting periods — to generate relevant positive and negative variations for the customer's environment.

Does this test use real customer data?

The public Syntra Standard Test Library shows the reusable standard test definition and representative examples only. Customer-specific transaction and account data used to generate variations remain within the customer's controlled SyntraFlow environment, subject to DataVault policies including data masking where configured.

Can this Oracle Fusion Receivables test be scheduled?

Yes. This scenario, or a regression pack that includes it, can be run on demand or scheduled for unattended batch execution — for example nightly, before a release, or ahead of a quarterly Oracle update.