Oracle ERP Testing Tool > Test Library > Financials > Intercompany

Syntra Standard Oracle Test Library

Oracle Fusion Create Intercompany Transaction Test Cases

Validate creation of an intercompany transaction between valid participating organizations/entities using configured transaction types, accounts, currencies and amounts.

Test ID	ORCL.R2R.IC.TXN.CREATE
Application	Oracle Fusion Cloud
Product	Financials
Module	Intercompany
Process	Intercompany Transactions
Business Flow	Record-to-Report
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 10 business-readable test steps; SyntraFlow's automation executes approximately 30 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised user can successfully create an intercompany transaction between a valid provider (initiating) organization and receiver organization in Oracle Fusion, using configured transaction types, accounts, currencies and amounts.

The scenario should confirm that:

the selected provider (initiating) organization is accepted
the selected receiver organization forms a valid counterparty relationship with the provider
the configured transaction type is applied correctly
the transaction amount and currency are accepted
the receivable and payable accounts are correctly assigned
the transaction is created with balanced provider and receiver amounts
the transaction reaches the expected status after submission
the created transaction is available for subsequent lifecycle processing

This scenario does not claim that the transaction is approved, exception-handled or accounted — those are separate downstream test cases covered by the Intercompany Approval, Intercompany Exceptions and Intercompany Accounting scenarios.

When to Use This Test

Functional testing of a new Oracle Fusion Intercompany implementation
Regression testing after an Oracle quarterly update
UAT sign-off for intercompany transaction creation
Baseline case referenced by intercompany approval, exception handling and accounting scenarios

Where This Test Fits in the Intercompany Lifecycle

Create

→

Approval

→

Exceptions

→

Accounting

This test covers intercompany transaction creation only, and serves as the entry point for the subsequent approval, exception handling and accounting scenarios in the intercompany lifecycle.

Next Stage →

Intercompany Approval

Preconditions

Oracle Fusion Intercompany is configured and available, and the test user has access.
Provider (initiating) organization is configured and active.
Receiver organization is configured and active, with a valid relationship to the provider.
Valid legal entity and ledger setup exists for the participating organizations, where applicable.
A configured intercompany transaction type is available.
The accounting period intended for the transaction is open.
Valid receivable and payable account combinations are available.

Exact setup, entity relationships and field availability may vary by Oracle Fusion implementation and intercompany configuration.

Sample Test Data

Provider / Initiating Organization	${PROVIDER_ORG} — e.g. US Operations
Receiver Organization	${RECEIVER_ORG} — e.g. UK Operations
Legal Entity	${LEGAL_ENTITY} (where applicable)
Ledger	${LEDGER}
Transaction Type	${TRANSACTION_TYPE}
Transaction Date	${TRANSACTION_DATE}
Currency	${CURRENCY}
Amount	${AMOUNT}
Receivable Account	${RECEIVABLE_ACCOUNT}
Payable Account	${PAYABLE_ACCOUNT}
Balancing Segment	${BALANCING_SEGMENT}
Description / Reference	${DESCRIPTION}

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

Test Steps

10 business-readable steps. SyntraFlow's automation executes ~30 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Navigate to Intercompany Navigate to the Intercompany work area within Oracle Fusion Financials.	The Intercompany work area opens successfully.
2	Create a New Transaction Select the option to create a new intercompany transaction.	The Create Intercompany Transaction page is displayed.
3	Select Provider Organization Select the provider (initiating) organization for the transaction. ${PROVIDER_ORG} This single business step replaces multiple technical actions such as opening search, entering the provider, clicking Search and selecting the result.	The provider organization is accepted and provider-related details are populated or available.
4	Select Receiver Organization Select the receiver organization for the transaction. ${RECEIVER_ORG}	The receiver organization is accepted and is a valid counterparty for the selected provider.
5	Select Transaction Type Select the configured intercompany transaction type. ${TRANSACTION_TYPE}	The transaction type is accepted and relevant accounting rules are applied.
6	Enter Amount and Currency Enter the transaction amount and select the transaction currency. ${AMOUNT} / ${CURRENCY}	The amount and currency are accepted and displayed correctly.
7	Enter Accounting Information Enter or confirm the receivable account, payable account and balancing segment for the transaction. ${RECEIVABLE_ACCOUNT} / ${PAYABLE_ACCOUNT} / ${BALANCING_SEGMENT}	Accounting information is accepted without unexpected validation errors.
8	Save the Transaction Select Save.	Oracle Fusion successfully processes the save request without unexpected errors.
9	Submit the Transaction Submit or complete the intercompany transaction for processing.	The transaction is submitted successfully and moves to the expected next status.
10	Verify Transaction StatusBusiness assertion Confirm the generated transaction number and verify that the transaction reaches the expected status with balanced provider/receiver amounts. This is the main business assertion for the scenario — the test does not stop merely because Save or Submit was clicked successfully.	The intercompany transaction is successfully created between the selected provider and receiver, can be identified by its generated transaction number, shows balanced amounts, and reflects the expected status and correctly assigned receivable/payable accounts.

Expected Results

Oracle Fusion successfully creates the intercompany transaction between the selected provider and receiver.
Provider and receiver amounts are balanced.
Transaction reaches the expected status after submission.
Receivable and payable accounts are correctly assigned.
Transaction type, currency and amount are retained accurately.
No unexpected errors occur during save or submission.
Newly created transaction can be identified or retrieved after submission.
Transaction is available for subsequent approval, exception handling and accounting scenarios.

Key Validation Checkpoints

Provider organization matches the intended test data.
Receiver organization matches the intended test data.
Provider and receiver form a valid configured relationship.
Transaction type is valid and correctly applied.
Transaction amount and currency are correct.
Receivable account is valid.
Payable account is valid.
Balancing segment is valid.
Debit and credit amounts balance.
Save and submit acknowledgements are received.
Transaction number is generated.
Transaction status matches the expected outcome.

Core Business Scenario

Create Intercompany 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 intercompany 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.

Teams do not need to manually duplicate the same intercompany transaction test dozens of times simply to cover different combinations of provider, receiver, legal entity, transaction type, currency, amount and account configuration. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment — though not every generated combination of provider, receiver, currency and account data is automatically valid or executable without review.

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 — Provider Organizations, Receiver Organizations, Legal Entities, Ledgers, Transaction Types, Currencies, Amounts and Accounting combinations.

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 intercompany transaction 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 Create Intercompany 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 Intercompany.

Positive Scenarios

Basic intercompany transaction
Different provider/receiver pairs
Different amounts
Different currencies
Multiple lines
Different transaction types
Different legal entities
Different balancing segments
Current-period transaction

Negative Scenarios

Same provider and receiver where invalid
Invalid provider
Invalid receiver
Invalid transaction type
Invalid account
Closed period
Invalid currency
Missing mandatory fields
Balancing-rule violation
Unsupported entity relationship

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

Standard Library Definition

Provider           ${PROVIDER_ORG}
Receiver           ${RECEIVER_ORG}
Legal Entity       ${LEGAL_ENTITY}
Ledger             ${LEDGER}
Transaction Type   ${TRANSACTION_TYPE}
Currency           ${CURRENCY}
Amount             ${AMOUNT}
Receivable Account ${RECEIVABLE_ACCOUNT}
Payable Account    ${PAYABLE_ACCOUNT}

DataVault

Provider Organizations
  US Operations
  UK Operations
Receiver Organizations
  UK Operations
  DE Operations
Ledgers
  US Primary Ledger
  UK Primary Ledger
Transaction Types
  Intercompany Sale
  Intercompany Cost Allocation
Currencies
  USD
  GBP
  EUR
Accounting
  Valid configured receivable/payable combinations

Jarvis AI Generates

Scenario 01 — Positive: Valid provider + valid receiver + valid accounts
Scenario 02 — Negative: Invalid receiver
Scenario 03 — Negative: Closed period
Scenario 04 — Negative: Balancing account missing
Scenario 05 — Boundary: High-value transaction
Scenario 06 — Configuration: Approval-required relationship
...

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 provider, receiver and account details remain 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 Intercompany Transaction	Positive	Single-line, valid provider and receiver	Syntra Ready
VAR-002	Provider A + Receiver B	Positive/Provider/Receiver	Alternate provider/receiver pair	Syntra Ready
VAR-003	Provider C + Receiver D	Positive/Provider/Receiver	Second alternate provider/receiver pair	Syntra Ready
VAR-004	High-Value Transaction	Positive	Large transaction amount	Syntra Ready
VAR-005	Low-Value Transaction	Positive	Minimal transaction amount at the low boundary	Syntra Ready
VAR-006	EUR Currency Transaction	Positive/Currency	Currency = EUR	Syntra Ready
VAR-007	GBP Currency Transaction	Positive/Currency	Currency = GBP	Syntra Ready
VAR-008	Multi-Line Transaction	Positive	Multiple transaction lines	Syntra Ready
VAR-009	Alternate Transaction Type	Positive/Type	Different configured transaction type	Syntra Ready
VAR-010	Different Legal Entity	Positive	Alternate legal entity / ledger combination	Syntra Ready
VAR-011	Alternate Balancing Segment	Positive/Balance	Different balancing segment value	Syntra Ready
VAR-012	Current-Period Transaction	Positive	Transaction dated in the current open period	Syntra Ready
VAR-013	Cross-Currency Provider/Receiver Pair	Positive/Provider/Receiver/Currency	Provider and receiver use different functional currencies	Syntra Ready
VAR-014	Same Provider and Receiver	Negative/Provider/Receiver	Provider organization equals receiver organization where not permitted	Syntra Ready
VAR-015	Invalid Provider Organization	Negative/Provider	Provider is unconfigured or inactive	Syntra Ready
VAR-016	Invalid Receiver Organization	Negative/Receiver	Receiver is unconfigured or inactive	Syntra Ready
VAR-017	Invalid Transaction Type	Negative/Type	Unconfigured transaction type selected	Syntra Ready
VAR-018	Invalid Receivable Account	Negative/Balance	Receivable account fails validation	Syntra Ready
VAR-019	Invalid Payable Account	Negative/Balance	Payable account fails validation	Syntra Ready
VAR-020	Closed Accounting Period	Negative	Transaction date falls within a closed period	Syntra Ready
VAR-021	Invalid Currency	Negative/Currency	Currency not configured for the provider/receiver pair	Syntra Ready
VAR-022	Missing Mandatory Fields	Negative	Required field left blank	Syntra Ready
VAR-023	Balancing Rule Violation	Negative/Balance	Debit and credit amounts do not balance	Syntra Ready
VAR-024	Unsupported Entity Relationship	Negative/Provider/Receiver	No configured relationship exists between the selected entities	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the intercompany transaction creation process.

Valid Provider + Valid Receiver + Valid Accounts → Transaction Created and Balanced

Negative Testing

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

Invalid Receiver → Expected Validation Displayed
Closed Period → Expected Period Validation Displayed
Balancing Account Missing → Expected Accounting Validation Displayed

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

Scenario	Oracle Outcome	Test Result
Valid provider/receiver pair	Transaction created and balanced	PASS
Invalid receiver	Expected validation appears	PASS
Closed period	Expected period validation appears	PASS
Unexpected system error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Intercompany Transaction Creation Regression Pack

Basic Intercompany Transaction
Provider A + Receiver B
High-Value Transaction
EUR Currency Transaction
Multi-Line Transaction
Alternate Transaction Type
Alternate Balancing Segment
Invalid Receiver Organization
Closed Accounting Period
Balancing Rule Violation

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	Intercompany Transaction Creation Regression Pack
Schedule	Quarterly Update Regression
Tests	24 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

Intercompany Lifecycle

Actual workflow depends on customer intercompany configuration. Stages link to the corresponding test scenario family.

Create

→Approval→Exceptions→Accounting

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 Intercompany Transaction, 10 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 Provider Organization

May internally include

Open Provider Search → Focus Provider Field → Enter Provider → Search → Select Provider → Confirm

Business Step

Enter Accounting Information

May internally include

Open Accounting Section → Enter Receivable Account → Enter Payable Account → Select Balancing Segment → Validate Combination

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 Amount and Currency	Pass	—
Click Submit	Pass	—
Verify Transaction Status	Pass	Pass

Related Intercompany Tests

Creating the intercompany transaction is the first stage of the same intercompany lifecycle — explore the related approval, exception handling and accounting scenarios below.

Intercompany Approval Intercompany Exceptions Intercompany Accounting

Turn This Standard Test into Your Oracle Intercompany Regression Suite

Start with the Syntra Standard intercompany transaction 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 Intercompany 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

Intercompany Test Library Oracle R2R Testing Tool Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What does the Create Intercompany Transaction test validate in Oracle Fusion?

It validates that an intercompany transaction can be created between a valid provider and receiver organization — including transaction type, amount, currency, accounting and balanced provider/receiver amounts — and reaches the expected status after submission.

Can this test run across different entities, ledgers and currencies?

Yes. The scenario is parameterised, so it can be executed with different provider/receiver organizations, legal entities, ledgers, transaction types and currencies without creating separate test cases.

How are the many intercompany transaction variations generated?

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

Does this test use real customer data?

The public Syntra Standard Test Library uses illustrative test data. Where DataVault is connected, customer-specific test dimensions such as provider, receiver, ledger, transaction type, currency and account can be used, protected according to DataVault's data policies.

Can Oracle Fusion intercompany tests be scheduled?

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

What happens after the intercompany transaction is created?

A created transaction moves into the next stages of the intercompany lifecycle — approval (where required by configuration), exception handling for any items that fail processing, and intercompany accounting. These are covered by separate related test scenarios.