Oracle ERP Testing Tool > Test Library > Financials > Accounts Payable > Invoice Processing

Syntra Standard Oracle Test Library

Oracle Fusion Invoice Distribution Test Cases

Validates how Oracle Fusion splits a single Payables invoice line's amount across one or more accounting distributions — the segment-level combinations that ultimately feed the Create Accounting process.

Test ID	ORCL.P2P.AP.INV.DISTRIBUTION
Application	Oracle Fusion Cloud
Product	Financials
Module	Accounts Payable
Process	Invoice Processing
Business Flow	Procure-to-Pay
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 12 business-readable test steps; SyntraFlow's automation executes approximately 34 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test case validates the creation and processing of accounting distributions associated with Oracle Fusion Payables invoice lines, confirming that a line's total amount is correctly and completely divided across valid account combinations before accounting.

The scenario should confirm that:

A single invoice line can generate one or multiple accounting distributions
Distribution amounts sum exactly to the parent invoice line amount with no variance
Each distribution carries a valid, enabled, detail-postable account combination
Cost center, balancing segment, and natural account segments combine correctly per the chart of accounts
Project-related distributions carry valid project, task, and expenditure type values
Distributions flagged for asset tracking are correctly identified for transfer to Fixed Assets
Distribution accounting dates fall within an open or future-enterable GL period
Distributions derived from a Distribution Set or PO match populate with correct default combinations
Invalid, disabled, or mismatched distribution data is rejected during invoice validation

Distribution mechanics — how one line's amount splits across accounts, cost centers, projects, and asset flags — are distinct from the overall Create Accounting process covered by the sibling Invoice Accounting test case, which validates the resulting journal entries and GL posting.

When to Use This Test

Splitting a single invoice line across multiple cost centers for shared-services allocation
Allocating a services invoice line across a project and task for capitalizable project costs
Distributing a freight or tax line proportionally across multiple item distributions
Validating that manually entered distribution combinations respect cross-validation rules before approval
Confirming distribution-level accounting dates correctly determine the GL period for posting
Verifying asset-flagged distributions route correctly to Mass Additions for capitalization

Where This Test Fits in the Procure-to-Pay Process

Invoice Line

→

Distribution Definition

→

Multiple Distributions

→

Accounting

→

General Ledger

Distributions originate from a PO match, a Distribution Set, or manual entry, and their segment combinations feed directly into Create Accounting; exact behavior varies by each customer's chart of accounts and cross-validation rule configuration.

Next Stage →

Invoice Accounting

Preconditions

Oracle Fusion Payables invoice (standard or PO-matched) exists in Incomplete or Saved status with at least one invoice line
Business unit is associated with a ledger and a valid chart of accounts structure
Cross-validation rules and account combination security rules are configured for the chart of accounts
Distribution Set, if used, is defined and assigned to the supplier site or invoice line
Project, task, and expenditure type combinations are set up in Oracle Project Costing for project-related lines
Asset category and corporate book are configured in Fixed Assets for asset-tracked lines
GL period corresponding to the distribution accounting date is in Open or Future Enterable status
User has Accounts Payable Invoice Entry, or an equivalent duty role, with distribution edit privileges
Supplier site is not on an invoice or payment hold that would block distribution entry

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

Sample Test Data

Invoice Line Amount	12,500.00 USD
Distribution Line 1 Amount	7,500.00 USD (60%)
Distribution Line 2 Amount	5,000.00 USD (40%)
Natural Account (Distribution 1)	71100 - Office Supplies Expense
Natural Account (Distribution 2)	71150 - IT Equipment Expense
Cost Center (Distribution 1)	4100 - Finance Dept
Cost Center (Distribution 2)	4200 - IT Dept
Balancing Segment (Company)	01 - US Operating Entity
Project Number	PRJ-10045 - ERP Rollout Phase 2
Task Number	1.2 - Testing & Validation
Expenditure Type	Contract Labor
Distribution Accounting Date	15-Mar-2026

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

Test Steps

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

#	User Action	Expected Result
1	Open Invoice Distributions Open the invoice and navigate to the Lines tab, then expand Distributions for the selected invoice line.	Distributions region displays with existing or auto-generated distribution rows for the line.
2	Review Auto-Generated Distribution Review the distribution line(s) automatically created from the PO match or the assigned Distribution Set. Distribution Set: Standard Office Expense Split	Auto-generated distribution reflects the source PO schedule or Distribution Set percentages.
3	Split Line into Multiple Distributions Split the invoice line amount into two distributions by entering a specific amount or percentage for each. Distribution 1: 7,500.00 USD (60%); Distribution 2: 5,000.00 USD (40%)	Two distribution rows are created; combined amounts equal the invoice line total.
4	Enter Natural Account Segment Enter the natural account segment for each distribution to identify the expense or asset classification. 71100 - Office Supplies Expense; 71150 - IT Equipment Expense	Natural account segment is accepted and displayed on each distribution line.
5	Enter Cost Center Segment Enter the cost center segment for each distribution to identify the responsible department. 4100 - Finance Dept; 4200 - IT Dept	Cost center segment is accepted and combined with the natural account into a full combination.
6	Enter Balancing Segment Confirm or enter the balancing segment (company/legal entity) for each distribution. 01 - US Operating Entity	Balancing segment is valid for the invoice's ledger and legal entity.
7	Enter Project Distribution Details For project-related distributions, enter the project, task, and expenditure type. PRJ-10045; Task 1.2; Contract Labor Applies only to distributions tied to a capital or billable project.	Project, task, and expenditure type are accepted and pass Project Costing edit validation.
8	Flag Distribution as Asset Mark the distribution as Track as Asset and select the asset category where the cost is capitalizable. Asset Category: IT Equipment - Computers Applies only to asset-related distributions.	Distribution is flagged for transfer to Fixed Assets Mass Additions after accounting.
9	Set or Override Distribution Accounting Date Confirm the default distribution accounting date or override it to prorate across periods. 15-Mar-2026	Accounting date is accepted and falls within an open or future-enterable period.
10	Verify Distribution Total Verify that the sum of all distribution amounts equals the invoice line amount before saving. Line Amount: 12,500.00 USD	Distribution total matches the line amount exactly; no variance is flagged.
11	Submit Invoice for Validation Submit the invoice for validation to trigger Oracle's distribution and account combination edits.	Invoice validation engine checks each distribution's account combination, cross-validation rules, and total.
12	Confirm Distribution ReadinessBusiness assertion Confirm the invoice reaches Validated status with all distributions correctly formed and ready for accounting.	All distributions carry valid, enabled account combinations; totals reconcile to each line; invoice is ready for Create Accounting.

Expected Results

Distributions generated automatically from PO match reflect the PO shipment/distribution schedule
Manually added distribution lines accept user-entered account segments
Split distributions sum precisely to the invoice line amount with no rounding variance
Distributions with invalid account combinations are rejected with a clear validation error
Distributions referencing disabled accounts are blocked from saving or validation
Distributions with mismatched totals prevent the invoice from reaching Validated status
Project-related distributions correctly populate the interface used for cost import to Project Costing
Asset-tracked distributions become eligible for Mass Additions after invoice accounting
Distributions dated in a closed period are rejected or require accounting date correction
Successfully validated distributions are ready for the Create Accounting process without further correction

Key Validation Checkpoints

Distribution total equals invoice line amount exactly, with no variance
Each distribution account combination exists and is enabled in the chart of accounts
Account combination is a valid, detail (non-summary) posting combination
Combination passes all applicable cross-validation rules
Balancing segment value is valid for the invoice's ledger and legal entity
Cost center segment maps to an active department
Project, task, and expenditure type values, where present, are valid and open for charging
Asset flag, when set, is paired with a valid asset category
Distribution accounting date falls within an open or future-enterable period
Distribution accounting date defaults correctly from the invoice or line unless explicitly overridden
Number of distribution lines matches the expected split (manual, Distribution Set, or PO-derived)
Invoice validation status reflects success or failure consistent with distribution data quality

Core Business Scenario

Invoice Distributions

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. 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 invoice distributions test case dozens of times simply to cover different combinations of data and configuration. 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.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Business Units, Suppliers, Supplier Sites, Currencies, Payment Terms, Accounting combinations, Tax configurations, Dates, Amounts 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 business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Create Standard Supplier Invoice 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 Payable Invoice Processing.

Positive Scenarios

Single distribution
Multiple distributions
Split distribution
Different natural accounts
Different cost centers
Different balancing segments where applicable
Project-related distribution where applicable
Asset-related distribution where applicable
Different accounting dates

Negative Scenarios

Invalid account combination
Disabled account
Missing distribution
Distribution total mismatch
Invalid project information
Invalid accounting date
Closed period

These are representative examples only. 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

The distribution logic stays constant across customers — split the line, assign accounts, validate the total. DataVault swaps in each customer's actual natural accounts, cost centers, balancing segments, and project values so the same Syntra Standard test runs unchanged against any chart of accounts.

Standard Library Definition

Invoice Line Amount: {{line_amount}} | Distribution 1: {{account_1}}-{{cost_center_1}} — {{pct_1}}% | Distribution 2: {{account_2}}-{{cost_center_2}} — {{pct_2}}%

DataVault

Natural Accounts: 71100 (Office Supplies), 71150 (IT Equipment), 74200 (Contract Labor) | Cost Centers: 4100 (Finance), 4200 (IT), 4300 (Operations) | Balancing Segments: 01 (US Ops), 02 (EMEA Ops) | Projects: PRJ-10045 (ERP Rollout Phase 2)

Jarvis AI Generates

01-4100-71100-000-000 : 7,500.00 USD (60%)
01-4200-71150-000-000 : 5,000.00 USD (40%)
01-4300-74200-000-000 : 3,200.00 USD (100%)
02-4100-71100-000-000 : 2,800.00 USD (100%)
01-4100-71100-PRJ10045-1.2 : 4,600.00 USD (project distribution)
01-4200-71150-000-000 : 1,900.00 USD (asset-tracked distribution)

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. They remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Every distribution variation below runs against the same business steps; only the DataVault-supplied account segments, split logic, or negative condition change.

ID	Variation	Type	Key Difference	Execution
VAR-001	Single Distribution — Full Line to One Account	Single	Entire line amount posted to one natural account and cost center combination	Syntra Ready
VAR-002	Multiple Distributions — Two-Way Split	Multiple	Line split 60/40 across two natural accounts	Syntra Ready
VAR-003	Multiple Distributions — Cost Center Allocation	Multiple/Cost Center	Three-way split across cost centers for shared-services allocation	Syntra Ready
VAR-004	Project-Related Distribution	Project	Distribution carries project, task, and expenditure type for capitalizable cost	Syntra Ready
VAR-005	Asset-Related Distribution	Single	Distribution flagged Track as Asset for Mass Additions transfer	Syntra Ready
VAR-006	Different Accounting Dates Across Distributions	Multiple	Distributions split across two GL periods with different accounting dates	Syntra Ready
VAR-007	Invalid Account Combination	Negative	Distribution references a segment combination that fails cross-validation rules	Syntra Ready
VAR-008	Disabled Account	Negative	Distribution references a natural account that has been end-dated or disabled	Syntra Ready
VAR-009	Distribution Total Mismatch	Negative	Sum of distribution amounts does not equal the invoice line amount	Syntra Ready
VAR-010	Closed Period Accounting Date	Negative	Distribution accounting date falls within a closed GL period	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

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

Valid data → Invoice Distributions completes successfully

Negative Testing

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

Invalid account combination → Expected Oracle validation
Disabled account → Expected Oracle validation
Missing distribution → Expected Oracle validation

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

Scenario	Oracle Outcome	Test Result
Two-way distribution split with valid cost centers	Invoice validates successfully; both distributions post with correct account combinations	PASS
Distribution referencing a disabled natural account	Oracle rejects the combination with an 'Account is disabled' validation error	PASS
Distribution total does not equal the invoice line amount	Oracle blocks validation with a 'Distribution amount does not equal line amount' error	PASS
Project-related distribution with valid project, task, and expenditure type	Distribution is accepted and interfaced correctly to Project Costing	PASS
Distribution accounting date within an open period	Invoice validation raised an unexpected internal application error instead of processing the distribution normally	FAIL

Turn AI-Generated Variations into a Regression Pack

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

AP Invoice Distributions Regression Pack

Single distribution — full line amount
Two-way distribution split by cost center
Multi-way distribution split by natural account
Project and task distribution
Asset-tracked distribution
PO-matched distribution inheritance
Distribution Set default population
Invalid account combination rejection
Distribution total mismatch rejection
Closed period accounting date rejection

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	AP Invoice Distributions Regression Pack
Schedule	Weekly Regression
Tests	20 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

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 — Invoice Distributions, 12 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

Split an invoice line into two accounting distributions by cost center

May internally include

Open Invoice > Lines > Distributions -> Click Split -> Enter Cost Center 4100 (60%) -> Enter Cost Center 4200 (40%) -> Confirm

Business Step

Enter a project-related distribution with task and expenditure type

May internally include

Open Distribution row -> Click Project Details -> Enter Project PRJ-10045 -> Enter Task 1.2 -> Enter Expenditure Type Contract Labor -> Confirm

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 primary distribution account combination	Pass	—
Split line into two distributions with cost center allocation	Pass	Pass
Enter project, task, and expenditure type on distribution	Pass	Pass
Submit invoice for validation with a balanced distribution total	Pass	Pass
Submit invoice for validation with an invalid account combination	Pass	Pass

Related Oracle Fusion AP Invoice Test Cases

Part of the same Procure-to-Pay invoice lifecycle. Linked cards are live; the rest are on the Syntra Standard Test Library roadmap.

Create Standard Invoice Create PO Matched Invoice Invoice Validation Invoice Holds Invoice Accounting Invoice Approval Create Credit Memo

Turn This Standard Test into Your Oracle Regression Suite

Start with the Syntra Standard Invoice Distributions 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 Oracle ERP Testing Tool

Use This Oracle Fusion Test Case

Download Test Case

Full objective, preconditions, test data and steps.

Excel (.xlsx) CSV JSON

Add to Test Library

Save to your SyntraFlow regression suite.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Oracle ERP Testing Tool Test Library Financials Accounts Payable Invoice Processing Oracle Invoice Distribution Testing Oracle Payables Testing Tool

Frequently Asked Questions

Can one invoice line have more than one accounting distribution?

Yes. A single Payables invoice line can be split into multiple distributions, each carrying its own account combination, amount, and optional project or asset attributes. The split can come from a PO match, a Distribution Set, or manual entry.

What determines how a line's amount is split across distributions?

The split is driven by the source of the distribution — a PO shipment schedule, a predefined Distribution Set, or manual user entry — and is ultimately governed by each customer's chart of accounts and cross-validation rule configuration.

What happens if distribution totals don't equal the line amount?

Oracle blocks the invoice from reaching Validated status and raises a distribution amount mismatch error. This is treated as expected, correct system behavior when tested as a negative scenario.

How does this test case differ from the Invoice Accounting test case?

This test case validates line-to-distribution split mechanics — how one line's amount divides across accounts, cost centers, and projects. Invoice Accounting validates the broader Create Accounting process and the resulting GL journal entries.

How are project-related distributions tested?

By verifying that project, task, and expenditure type combinations entered on a distribution are valid, open for charging, and correctly interfaced to Oracle Project Costing.

Does distribution testing depend on customer-specific configuration?

Yes. DataVault substitutes each customer's actual natural accounts, cost centers, balancing segments, and cross-validation rules into the same Syntra Standard test logic, so the scenario stays valid across different chart of accounts setups.

Download Test Case