Oracle Fusion Invoice Accounting Test Cases
Validate that Oracle Fusion generates correct, balanced accounting entries for validated Payables invoices - covering standard, PO-matched, credit memo, and prepayment scenarios across Draft and Final accounting modes.
| Test ID | ORCL.P2P.AP.INV.ACCOUNTING |
| 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 13 business-readable test steps; SyntraFlow's automation executes approximately 36 underlying Oracle Fusion UI actions to complete it.
Test Objective
Validate that Oracle Fusion Payables correctly creates accounting for eligible invoices and confirm the resulting accounting outcome matches the expected debit and credit treatment.
The scenario should confirm that:
- Only invoices with a Validated status (and required approvals complete) are eligible for Create Accounting
- The Create Accounting process derives correct debit and credit lines based on Subledger Accounting rules
- Invoice accounting status updates from Unaccounted to Accounted, or Partially Accounted where applicable
- The accounting date assigned to generated entries falls within an Open or Future-Enterable period
- Distribution combinations used for accounting are valid, active, and reflect the correct expense, liability, or prepayment accounts
- Multi-line and multi-distribution invoices generate one balanced accounting entry set per invoice
- Draft mode accounting can be previewed and reviewed before Final mode accounting is submitted
- Accounting exceptions (invalid combination, closed period, incomplete distribution) are correctly captured and reported
- Credit memo and prepayment invoices generate the correct reversing or asset-based accounting treatment
This scenario validates accounting creation only; it does not assert that journal entries have been transferred to or posted in the General Ledger unless that action is explicitly included in the scenario steps.
When to Use This Test
- Validate accounting generation for standard, PO-matched, credit memo, and prepayment invoices ahead of period close
- Confirm invoice accounting status transitions correctly during regression testing after Payables patch updates
- Verify accounting exceptions are correctly raised for invoices in closed periods or with invalid distribution combinations
- Test accounting derivation consistency across different ledger and chart-of-accounts configurations
- Confirm the Draft mode accounting review workflow before committing Final mode accounting
- Validate accounting behavior for multi-line invoices with mixed expense, freight, and tax distributions
Where This Test Fits in the Procure-to-Pay Process
Create Accounting is a Subledger Accounting (SLA) process that runs after invoice validation and approval, translating invoice distributions into balanced journal entries; transfer to and posting in General Ledger are separate downstream actions outside this scenario's assertions.
Preconditions
- Invoice exists in Payables with Validation Status = Validated and, where required, Approval Status = Approved
- Invoice has no active holds that would block the accounting process
- The ledger and business unit configuration has an active Subledger Accounting method assigned
- The accounting period corresponding to the invoice's accounting date is Open or Future-Enterable in both Payables and General Ledger calendars
- Distribution lines reference valid, enabled natural account and distribution combinations (charge, liability, prepayment, or tax accounts as applicable)
- Application Accounting Definitions, Journal Line Rules, and Account Rules are configured for the Payables subledger
- User has role access to run Create Accounting (Submit Accounting) from the invoice or via Scheduled Processes
- Supplier and business unit are associated with a liability account per Payables Financial Options setup
- For PO-matched invoices, purchase order distribution and accrual accounts are valid and available for derivation
Exact setup and field availability may vary by Oracle Fusion implementation and security configuration.
Sample Test Data
| Invoice Number | INV-AP-100245 |
| Business Unit | US1 Business Unit |
| Supplier | Global Parts Supply Inc. |
| Invoice Type | Standard |
| Invoice Amount | 12,450.00 USD |
| Accounting Date | 15-Aug-2026 |
| Ledger | US Primary Ledger |
| Expense Distribution | 01-000-7420-0000-000 (Office Supplies Expense) |
| Liability Account | 01-000-2210-0000-000 (AP Trade Liability) |
| Accounting Period | Aug-2026 |
| Accounting Mode | Draft, then Final |
| Currency | USD (Ledger Currency) |
Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.
Test Steps
13 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 | Confirm invoice eligibility Open the invoice in Manage Invoices and confirm Validation Status = Validated with no blocking holds Invoice Number: INV-AP-100245 | Invoice status confirmed as Validated and eligible for accounting |
| 2 | Confirm accounting period status Verify the accounting period corresponding to the invoice's accounting date is Open in Payables and General Ledger Period: Aug-2026 | Accounting period status = Open |
| 3 | Submit Create Accounting in Draft mode From the invoice, select Actions > Create Accounting and run with Accounting Mode = Draft Accounting Mode: Draft | Process completes and draft accounting entries are generated for review |
| 4 | Review draft accounting entries Open the Review Accounting Entries page and inspect the generated debit and credit lines | Draft entries display balanced debit expense and credit liability lines matching the distribution setup |
| 5 | Confirm no draft accounting errors Check the draft accounting output for exceptions or unposted lines before proceeding to Final mode | No accounting exceptions are present in the draft run |
| 6 | Submit Create Accounting in Final mode Rerun Create Accounting on the invoice with Accounting Mode = Final Accounting Mode: Final | Process completes successfully and invoice accounting status updates to Accounted |
| 7 | Verify invoice accounting status Navigate back to the invoice header and check the Accounting Status field | Accounting Status = Accounted |
| 8 | Verify accounting entries Open View Accounting Journal Entries for the invoice and inspect the generated lines | Journal entries show a debit to the Expense/Charge account and a credit to the AP Liability account, with amounts equal to invoice line and tax totals |
| 9 | Verify accounting date and period Confirm the accounting date on the generated journal matches the invoice's designated accounting date and period Accounting Date: 15-Aug-2026 | Accounting date = 15-Aug-2026, accounting period = Aug-2026 |
| 10 | Verify distribution-to-account mapping Compare each invoice distribution line to its corresponding generated accounting line | Every distribution line maps to a correct and traceable accounting line |
| 11 | Verify multi-line invoice balancing For invoices with multiple distributions, sum total debits and total credits across the accounting set Applies to multi-line and multi-distribution variations | Total debits equal total credits for the invoice's accounting entry set |
| 12 | Verify scenario-specific accounting treatment For PO-matched, credit memo, or prepayment invoices, confirm the accounts and entry direction reflect the correct treatment (PO accrual derivation, reversed debit/credit for credit memos, or prepayment asset account for prepayments) Applies to PO-Matched, Credit Memo, and Prepayment variations | Scenario-specific accounts and entry direction are correctly applied |
| 13 | Confirm overall invoice accounting outcomeBusiness assertion Review the complete accounting result for the invoice against the expected accounting treatment for its scenario type | Invoice accounting reflects the correct financial treatment: accurate accounts, balanced entries, correct accounting date, and Accounted status |
Expected Results
- Invoice accounting status changes from Unaccounted to Accounted after successful Final mode processing
- Draft mode accounting entries are available for preview prior to Final submission
- Debit and credit accounting lines are generated in balance for each invoice distribution
- Expense or charge accounts reflect the correct natural account per the distribution setup
- The AP Liability account is correctly credited for the invoice liability amount
- Accounting date and period on generated entries match the invoice's designated accounting date
- PO-matched invoices derive distribution accounts consistent with purchase order accounting setup
- Credit memo and prepayment invoices generate the appropriate reversing or asset-based accounting treatment
- Accounting exceptions are captured and displayed in Review Accounting Errors for ineligible invoices
- No unexpected system errors occur during Draft or Final accounting submission for eligible invoices
Key Validation Checkpoints
- Accounting process completes without error for eligible invoices
- Invoice accounting status correctly reflects Accounted, Partially Accounted, or Unaccounted
- Expected accounting entries (debit and credit) are generated per distribution line
- The liability account is accurately represented and equals the invoice liability amount
- Expense, charge, or prepayment accounts are accurately represented per distribution combination
- Accounting date assigned to journal entries matches the invoice's accounting date
- Accounting period is correctly derived and confirmed open at time of processing
- Accounting errors and exceptions are correctly captured for ineligible invoices (closed period, invalid combination, unvalidated invoice)
- Draft accounting entries match Final accounting entries when no changes occur between runs
- Multi-line invoices produce balanced accounting sets where total debits equal total credits
- PO-matched invoice distributions correctly inherit purchase order accounting setup
- Credit memo accounting entries correctly reverse the original invoice's accounting direction
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 accounting 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
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.
- Account standard invoice
- Account PO-matched invoice
- Account credit memo
- Account prepayment
- Multi-line invoice accounting
- Multiple distributions
- Different accounting dates
- Different ledger/configuration combinations
- Unvalidated invoice
- Invalid distribution
- Closed accounting period
- Accounting configuration exception
- Incomplete accounting data
- Other expected accounting exceptions
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
DataVault supplies the ledger, period, account, and distribution template combinations behind each invoice accounting scenario, letting Syntra Standard generate realistic accounting variations without hand-authoring every account string.
Standard Library Definition
Invoice: INV-AP-100245
Business Unit: US1 Business Unit
Ledger: US Primary Ledger
Accounting Date: {ACCOUNTING_DATE}
Expense Distribution: {EXPENSE_ACCOUNT}
Liability Distribution: {LIABILITY_ACCOUNT}
Accounting Mode: Draft -> Final
DataVault
Ledgers: [US Primary Ledger, UK Primary Ledger, APAC Secondary Ledger] Accounting Periods: [Jul-2026 (Closed), Aug-2026 (Open), Sep-2026 (Future-Enterable)] Accounts: [7420-Office Supplies Expense, 7510-Freight Expense, 1410-Prepayments Asset, 2210-AP Trade Liability] Distribution Templates: [Standard Expense, PO Accrual, Prepayment Asset, Multi-Line Mixed]
Jarvis AI Generates
GEN-01: US Primary Ledger | Aug-2026 (Open) | 7420-Office Supplies / 2210-AP Liability | Standard Expense GEN-02: UK Primary Ledger | Aug-2026 (Open) | 7510-Freight / 2210-AP Liability | Multi-Line Mixed GEN-03: US Primary Ledger | Jul-2026 (Closed) | 7420-Office Supplies / 2210-AP Liability | Standard Expense [Negative] GEN-04: APAC Secondary Ledger | Sep-2026 (Future-Enterable) | 1410-Prepayments / 2210-AP Liability | Prepayment Asset GEN-05: US Primary Ledger | Aug-2026 (Open) | 7610-PO Accrual / 2210-AP Liability | PO Accrual GEN-06: US Primary Ledger | Aug-2026 (Open) | 9999-Invalid Combination / 2210-AP Liability | Standard Expense [Negative]
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
Explore how Syntra Standard varies invoice accounting scenarios across ledgers, periods, distribution types, and expected exceptions - each row is a Syntra-ready test case generated from the DataVault combinations above.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| VAR-001 | Standard Invoice - Draft to Final Accounting | Standard | Single-line standard invoice; accounting run in Draft mode then Final mode | Syntra Ready |
| VAR-002 | PO-Matched Invoice Accounting | PO-Matched | Distribution combination derived from PO accrual account rather than manual entry | Syntra Ready |
| VAR-003 | Credit Memo Reversal Accounting | Credit Memo | Accounting direction reversed relative to the original invoice: debit liability, credit expense | Syntra Ready |
| VAR-004 | Prepayment Invoice Accounting | Standard | Debits the Prepayment asset account instead of an expense account | Syntra Ready |
| VAR-005 | Multi-Line Mixed Distribution Accounting | Multi-Line | Five distribution lines spanning expense, freight, and tax accounts on one invoice | Syntra Ready |
| VAR-006 | Cross-Ledger Accounting - UK Primary Ledger | Standard | Same scenario re-run against the UK Primary Ledger configuration and chart of accounts | Syntra Ready |
| VAR-007 | Unvalidated Invoice Accounting Attempt | Negative | Create Accounting submitted before the invoice reaches Validated status | Syntra Ready |
| VAR-008 | Closed Period Accounting Exception | Negative | Accounting date falls within a closed Payables/GL period | Syntra Ready |
| VAR-009 | Invalid Distribution Combination Exception | Negative | Distribution references an inactive or invalid natural account combination | Syntra Ready |
| VAR-010 | Incomplete Accounting Data Exception | Negative | Distribution line is missing a required accounting flexfield segment | Syntra Ready |
No variations match this filter.
Automatically Expand Positive and Negative Test Coverage
Positive Testing
Jarvis generates scenarios using combinations expected to successfully complete the business process.
Valid data → Invoice Accounting completes successfully
Negative Testing
Jarvis can generate scenarios designed to exercise validations, business rules and exception handling.
- Unvalidated invoice → Expected Oracle validation
- Invalid distribution → Expected Oracle validation
- Closed accounting period → 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 |
|---|---|---|
| Standard invoice accounting (Final mode) | Accounting entries generated; invoice status = Accounted | PASS |
| PO-matched invoice accounting | Distribution accounts correctly derived from PO accrual setup; status = Accounted | PASS |
| Accounting attempted on a closed period | Oracle correctly blocks accounting with a period-not-open exception | PASS |
| Accounting attempted with an invalid distribution combination | Oracle correctly rejects the entry with an inactive-account-combination error | PASS |
| Accounting submitted for an unvalidated invoice | Unexpected system error - process failed without a clear exception message routed to Review Accounting Errors | FAIL |
Turn AI-Generated Variations into a Regression Pack
Users can select generated scenarios and group them into reusable execution packs.
AP Invoice Accounting Regression Pack
- Standard Invoice Accounting
- PO-Matched Invoice Accounting
- Credit Memo Accounting
- Prepayment Accounting
- Multi-Line Distribution Accounting
- Cross-Ledger Accounting
- Unvalidated Invoice Exception
- Closed Period Exception
- Invalid Distribution Exception
- Incomplete Accounting Data Exception
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.
| Pack | AP Invoice Accounting 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.
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.
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.
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.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
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 |
|---|---|---|
| Submit Create Accounting - Draft mode | Pass | — |
| Submit Create Accounting - Final mode | Pass | Pass |
| Verify accounting entries balance (debit = credit) | Pass | Pass |
| Attempt accounting on invoice with invalid distribution 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.
Turn This Standard Test into Your Oracle Regression Suite
Start with the Syntra Standard Invoice 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.
Use This Oracle Fusion Test Case
Add to Test Library
Save to your SyntraFlow regression suite.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.