Oracle ERP Testing Tool > Test Library > Financials > Intercompany

Syntra Standard Oracle Test Library

Oracle Fusion Intercompany Accounting Test Cases

Validate accounting generated for approved intercompany transactions, including intercompany receivable and payable distributions, balancing entries and General Ledger results where applicable.

Test ID	ORCL.R2R.IC.ACCOUNTING
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 11 business-readable test steps; SyntraFlow's automation executes approximately 31 underlying Oracle Fusion UI actions to complete it.

Test Objective

Validate accounting generated for eligible intercompany transactions and confirm balancing, receivable/payable accounting and General Ledger results where applicable.

The scenario should confirm that:

the Intercompany Receivable distribution is generated correctly for an approved transaction
the Intercompany Payable distribution is generated correctly for the counterparty entity
balancing entries are created according to configured balancing rules and balancing segments
total debits and credits balance across the generated accounting event
the accounting date is correct and falls within the open accounting period
the transaction's accounting status updates correctly once accounting is generated
General Ledger transfer/posting is reflected correctly where included in the scenario's scope
no unexpected accounting errors occur during accounting generation

This scenario does not claim that General Ledger posting is validated for every transaction, or that intercompany netting and settlement are covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test 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 accounting generation
Final-stage scenario in the intercompany lifecycle, following transaction creation, approval and exception handling

Where This Test Fits in the Intercompany Lifecycle

Intercompany Transaction

→

Approved / Accepted

→

Accounting

→

Receivable + Payable Distributions

→

Balancing

→

General Ledger

This test covers accounting generation for an approved intercompany transaction — including receivable, payable and balancing entries — and represents the final stage of the intercompany lifecycle, with General Ledger transfer/posting covered where included in the scenario's scope.

← Previous Stage

Intercompany Exceptions

Preconditions

Oracle Fusion Intercompany is configured and available, with appropriate user access to Intercompany accounting functions.
An intercompany transaction exists that has been approved/accepted and is eligible for accounting generation.
The accounting period intended for the transaction is open.
Valid Intercompany Receivable and Intercompany Payable accounts are configured for the legal entities/business units involved.
Balancing segments and balancing rules are configured for the entities involved in the transaction.
Applicable exchange rates are available for cross-currency intercompany transactions.
The test user has permission to generate accounting for Intercompany transactions.

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

Sample Test Data

Transaction	Approved intercompany transaction, ready for accounting
Intercompany Receivable Account	${IC_RECEIVABLE_ACCOUNT}
Intercompany Payable Account	${IC_PAYABLE_ACCOUNT}
Currency	Matches transaction currency, e.g. USD — EUR used for the multi-currency example
Balancing Segment	${BALANCING_SEGMENT}
Accounting Period	${ACCOUNTING_PERIOD} — current open period

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

Test Steps

11 business-readable steps. SyntraFlow's automation executes ~31 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 in Oracle Fusion.	The Intercompany work area opens successfully.
2	Locate the Approved Transaction Search for and open the intercompany transaction that has been approved/accepted and is eligible for accounting. ${TRANSACTION} This single business step replaces multiple technical actions such as opening search, entering the transaction reference, clicking Search and selecting the result.	The correct transaction is located and its status confirms it is eligible for accounting generation.
3	Initiate Accounting Generation Initiate the Create Accounting process for the selected transaction.	The Create Accounting request is accepted and accounting generation begins without unexpected errors.
4	Review Receivable-Side Distribution Review the Intercompany Receivable distribution generated for the transaction. ${IC_RECEIVABLE_ACCOUNT}	The receivable distribution reflects the expected Intercompany Receivable account and amount.
5	Review Payable-Side Distribution Review the Intercompany Payable distribution generated for the counterparty entity. ${IC_PAYABLE_ACCOUNT}	The payable distribution reflects the expected Intercompany Payable account and amount.
6	Verify Balancing Entries Review the balancing entries generated across the balancing segments involved in the transaction. ${BALANCING_SEGMENT}	Balancing entries are generated according to the configured balancing rules for the entities involved.
7	Verify Debit/Credit Totals Balance Review the total debit and credit amounts across all distributions generated for the accounting event.	Total debits equal total credits for the accounting event.
8	Verify Accounting Date Review the accounting date assigned to the generated distributions. ${ACCOUNTING_PERIOD}	The accounting date falls within the open accounting period and matches the expected period.
9	Verify Accounting Status Updated Review the transaction's accounting status following accounting generation.	The accounting status updates correctly to reflect that accounting has been generated.
10	Review General Ledger Transfer/Posting State Where transfer to General Ledger is included in the test scenario, review the transfer/posting status of the generated accounting. Not every intercompany accounting scenario extends through to GL transfer/posting — scope depends on the specific test scenario and customer configuration.	General Ledger transfer/posting status is reflected correctly where this step is included in the scenario's scope; this step is not applicable to scenarios that stop at accounting generation.
11	Confirm No Unexpected Accounting ErrorsBusiness assertion Review the transaction and the generated accounting event for unexpected errors or exceptions. This is the main business assertion for the scenario — the test does not stop merely because Create Accounting was initiated successfully.	No unexpected accounting errors are present; only expected outcomes for the scenario are observed, with receivable, payable and balancing distributions correctly generated.

Expected Results

Accounting is generated successfully for the approved intercompany transaction.
Intercompany Receivable distribution reflects the expected account and amount.
Intercompany Payable distribution reflects the expected account and amount.
Balancing entries are created according to configured balancing rules.
Total debits equal total credits across the generated accounting event.
Accounting date falls within the open accounting period.
Transaction's accounting status updates correctly to reflect that accounting has been generated.
Where included in the scenario's scope, General Ledger transfer/posting reflects the expected status.
No unexpected accounting errors occur.

Key Validation Checkpoints

Receivable distribution account and amount are correct.
Payable distribution account and amount are correct.
Balancing entries match the configured balancing rules and segments.
Debit and credit totals balance for the accounting event.
Accounting date is within the open accounting period.
Accounting status updates correctly after generation.
General Ledger transfer/posting status is correct where in scope.
No unexpected accounting errors are present.

Core Business Scenario

Intercompany 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 intercompany accounting business 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 accounting test dozens of times simply to cover different combinations of entity pairs, currencies, balancing segments and accounting periods. 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

Intercompany Transaction

The transaction is approved and accepted, and becomes eligible for accounting generation.

Create Accounting

Accounting generation is initiated for the eligible transaction.

Intercompany Receivable

The receivable-side distribution is generated against the configured Intercompany Receivable account.

Intercompany Payable

The payable-side distribution is generated against the configured Intercompany Payable account for the counterparty entity.

Balancing

Balancing entries are generated across the balancing segments involved, and debit/credit totals are confirmed to balance.

General Ledger

Where included in the scenario's scope, accounting is transferred and posted to the General Ledger.

Results + Evidence + Exceptions

Execution results, business assertions, screenshots/evidence and exceptions are captured.

Rather than maintaining dozens of near-duplicate copies of the same intercompany accounting 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 Intercompany 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 Intercompany.

Positive Scenarios

Accounting generated for a valid, approved transaction
Different intercompany entity pairs
Different currencies, including a multi-currency example with an applicable exchange rate
Multiple transaction lines
Different intercompany transaction types
Multiple balancing segments
Accounting generated immediately after approval
Accounting generated across multiple intercompany transactions

Negative Scenarios

Invalid Intercompany Receivable/Payable account
Incomplete approval
Closed accounting period
Balancing-rule failure
Missing exchange rate for a cross-currency transaction
Invalid ledger assignment
Incomplete transaction data
Accounting configuration exception

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 — including intercompany receivable/payable accounts, currency, balancing segment and accounting period — to create variations relevant to the customer's actual implementation.

Standard Library Definition

Transaction             ${TRANSACTION}
Intercompany Receivable  ${IC_RECEIVABLE_ACCOUNT}
Intercompany Payable     ${IC_PAYABLE_ACCOUNT}
Currency                 ${CURRENCY}
Balancing Segment        ${BALANCING_SEGMENT}
Accounting Period        ${ACCOUNTING_PERIOD}

DataVault

Intercompany Receivable Accounts
  IC-REC-US
  IC-REC-UK
Intercompany Payable Accounts
  IC-PAY-US
  IC-PAY-UK
Currencies
  USD
  EUR
  GBP
Balancing Segments
  US Ops
  UK Ops
  EU Ops
Accounting Periods
  Current open period per entity

Jarvis AI Generates

Scenario 01 — US/UK Entity Pair + USD + Current Period
Scenario 02 — UK/EU Entity Pair + EUR + Exchange Rate Applied
Scenario 03 — Multi-Line Transaction + Multiple Balancing Segments
Scenario 04 — Invalid Receivable Account
Scenario 05 — Incomplete Approval
Scenario 06 — Closed Accounting Period
...

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 intercompany accounts, currency and balancing segment configuration 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 Approved Transaction Accounting	Positive	Single transaction, single currency, valid accounts	Syntra Ready
VAR-002	Different Entity Pair	Positive	Accounting generated between a different pair of intercompany entities	Syntra Ready
VAR-003	EUR Currency Transaction	Positive/Currency	Transaction currency = EUR with applicable exchange rate	Syntra Ready
VAR-004	GBP Currency Transaction	Positive/Currency	Transaction currency = GBP with applicable exchange rate	Syntra Ready
VAR-005	Multi-Line Transaction Accounting	Positive	Accounting generated across multiple transaction lines	Syntra Ready
VAR-006	Different Transaction Type	Positive	Accounting generated for an alternate intercompany transaction type	Syntra Ready
VAR-007	Multiple Balancing Segments	Positive/Balancing	Balancing entries span multiple balancing segment values	Syntra Ready
VAR-008	Accounting Immediately After Approval	Positive	Accounting initiated immediately following approval	Syntra Ready
VAR-009	Multiple Transactions in Same Run	Positive	Accounting generated for multiple approved transactions together	Syntra Ready
VAR-010	Receivable Distribution Validation	Positive/Receivable	Confirms the Intercompany Receivable account and amount	Syntra Ready
VAR-011	Payable Distribution Validation	Positive/Payable	Confirms the Intercompany Payable account and amount	Syntra Ready
VAR-012	Accounting Within Current Open Period	Positive/Period	Accounting date falls within the current open period	Syntra Ready
VAR-013	Invalid Receivable Account	Negative/Receivable	Configured Intercompany Receivable account is invalid	Syntra Ready
VAR-014	Invalid Payable Account	Negative/Payable	Configured Intercompany Payable account is invalid	Syntra Ready
VAR-015	Incomplete Approval	Negative	Transaction has not completed the full approval workflow	Syntra Ready
VAR-016	Closed Accounting Period	Negative/Period	Attempted accounting date falls within a closed period	Syntra Ready
VAR-017	Balancing Rule Failure	Negative/Balancing	Transaction cannot be balanced under configured balancing rules	Syntra Ready
VAR-018	Missing Exchange Rate	Negative/Currency	Cross-currency transaction has no applicable exchange rate defined	Syntra Ready
VAR-019	Invalid Ledger Assignment	Negative	Transaction is assigned to an invalid or unavailable ledger	Syntra Ready
VAR-020	Incomplete Transaction Data	Negative	Required transaction data is missing prior to accounting	Syntra Ready
VAR-021	Accounting Configuration Exception	Negative	Accounting method/rule configuration is missing or invalid	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully generate accounting for eligible intercompany transactions.

Approved Transaction + Valid Receivable/Payable Accounts + Valid Balancing Segments → Accounting Generated

Negative Testing

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

Invalid Receivable Account → Expected Account Validation
Incomplete Approval → Expected Accounting Blocked
Balancing Rule Failure → Expected Balancing Validation

A negative test should not be marked as failed simply because Oracle correctly blocks accounting generation for an ineligible transaction. If the expected Oracle validation or block occurs, the negative test has passed.

Scenario	Oracle Outcome	Test Result
Approved, eligible transaction	Accounting generates correctly with balanced receivable and payable distributions	PASS
Incomplete approval	Accounting generation is correctly blocked	PASS
Balancing-rule failure	Expected balancing validation is displayed	PASS
Unexpected system error	Unexpected failure occurs	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Intercompany Accounting Regression Pack

Basic Approved Transaction Accounting
Different Entity Pair
EUR Currency Transaction
Multi-Line Transaction Accounting
Multiple Balancing Segments
Receivable Distribution Validation
Payable Distribution Validation
Invalid Receivable Account
Balancing Rule Failure
Closed Accounting Period

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 Accounting Regression Pack
Schedule	Quarterly Update Regression
Tests	21 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 — Intercompany Accounting, 11 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 Approved Transaction

May internally include

Open Transaction Search → Focus Transaction Reference → Enter Transaction → Search → Select Transaction → Confirm

Business Step

Review Receivable-Side Distribution

May internally include

Open Accounting Distributions → Filter Receivable Line → Capture Account and Amount → Validate

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	—
Review Receivable Distribution	Pass	—
Verify Accounting Status Updated	Pass	Pass

Related Intercompany Tests

Intercompany accounting is the final stage of the same intercompany lifecycle — explore the related transaction creation, approval and exception-handling scenarios below.

Create Intercompany Transaction Intercompany Approval Intercompany Exceptions

Turn This Standard Test into Your Oracle Intercompany Regression Suite

Start with the Syntra Standard intercompany accounting 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 Intercompany Accounting test validate in Oracle Fusion?

It validates that accounting can be generated correctly for an approved intercompany transaction — including the Intercompany Receivable and Intercompany Payable distributions, balancing entries, debit/credit totals and the transaction's accounting status.

What accounting distributions are generated for an intercompany transaction?

A generated accounting event typically includes an Intercompany Receivable distribution for the originating entity, an Intercompany Payable distribution for the counterparty entity, and balancing entries across the balancing segments involved, according to configured balancing rules.

Does this test validate posting to the General Ledger?

Only where General Ledger transfer/posting is explicitly included in the specific test scenario's scope. Not every accounting-generation scenario is validated through to GL posting — where that step is out of scope, it is treated as not applicable rather than assumed to have succeeded.

What happens if accounting cannot be generated for a transaction, for example an invalid account or a closed period?

These are treated as negative test scenarios. A negative test passes when Oracle correctly blocks accounting generation or displays the expected validation — for example for an invalid account, incomplete approval, a closed period or a balancing-rule failure.

How are the many intercompany accounting test variations generated?

Jarvis AI uses this standard accounting scenario together with available DataVault test data and configuration to generate relevant positive and negative variations — for example different entity pairs, currencies, balancing segments and exception conditions — for the customer's environment.

Can the intercompany accounting scenario and its variations be scheduled?

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