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

Oracle Fusion Create Credit Memo Test Cases

Validates that Oracle Fusion Payables correctly creates, values, and processes supplier credit memos — whether entered as standalone unmatched credits or matched against an existing invoice or PO — so that supplier balances, tax, and accounting are adjusted accurately.

Test IDORCL.P2P.AP.INV.CREATE.CREDITMEMO
ApplicationOracle Fusion Cloud
ProductFinancials
ModuleAccounts Payable
ProcessInvoice Processing
Business FlowProcure-to-Pay
Scenario TypePositive / Functional
Test UsageFunctional Testing / Regression Testing / UAT
PriorityHigh
AutomationSyntraFlow Ready
LibrarySyntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 14 business-readable test steps; SyntraFlow's automation executes approximately 39 underlying Oracle Fusion UI actions to complete it.

Test Objective

This scenario validates the creation and downstream processing of supplier credit memos in Oracle Fusion Payables, confirming that credit amounts, tax, and distributions are captured correctly regardless of whether the credit is standalone or tied to a prior invoice.

The scenario should confirm that:

  • A credit memo can be created for a valid supplier and supplier site with a negative or credit-typed amount
  • Credit memos can be entered as unmatched (standalone) documents with manually keyed distributions
  • Credit memos can be entered with a reference to an existing invoice for full or partial credit
  • Credit memo line amounts do not exceed the outstanding balance of the referenced invoice when matched
  • Tax is recalculated or reversed proportionally to the credited amount and line
  • Distribution combinations on the credit memo mirror or appropriately offset the original invoice's accounting
  • Multi-currency credit memos inherit the currency and conversion rate context of the referenced invoice or business unit
  • The credit memo validates, routes through approval, and creates accounting as a credit-typed AP transaction
  • The resulting credit balance is available for application against future payments or for refund processing

This scenario tests the creation of a new credit memo document; it is distinct from cancelling or voiding an existing invoice, which reverses a transaction rather than recording a new supplier credit.

When to Use This Test

  • Supplier issues a credit note for damaged, short-shipped, or returned goods against a previously paid or unpaid invoice
  • Accounts Payable processes a pricing correction or rebate credit that reduces the amount owed to a supplier
  • AP clerk enters a standalone credit memo for an overpayment or duplicate payment recovery not tied to a specific invoice line
  • Procurement-driven return requires a credit memo matched to the original purchase order and receipt for a returned quantity
  • Finance team applies a partial credit against one line of a multi-line invoice while leaving other lines unaffected
  • Shared services team processes a foreign-currency credit memo that must reconcile against an invoice booked in a different functional currency

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

Supplier
Credit Memo Creation
Validation
Approval
Accounting
Application / Refund

Credit Memo Creation is the entry point for reducing a supplier's outstanding balance; downstream steps determine whether the credit offsets a future payment or is refunded directly to the supplier.

Preconditions

  1. Supplier and supplier site are active and enabled for invoicing in the target business unit
  2. For matched credit memos, the reference invoice exists, is validated, and has an open (non-zero) balance
  3. Accounting period for the credit memo date is open in both the subledger and, if applicable, the referenced invoice's ledger
  4. Payables invoice options and supplier site defaults (payment terms, liability account, tax registration) are configured
  5. Tax rules and tax classification codes applicable to the original transaction type are active
  6. Distribution set or expense/liability account combinations are valid in the current chart of accounts
  7. User has the Accounts Payable Invoice Entry role with credit memo creation privileges
  8. Approval hierarchy/workflow rules for AP credit memos are configured for the business unit
  9. Currency and conversion rate type are defined for the transaction currency if different from the ledger currency

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

Sample Test Data

SupplierRedwood Office Supplies Inc.
Supplier SiteRWD-US-EAST
Invoice TypeCredit Memo
Credit Memo NumberCM-2026-08421
Credit Memo Date12-Aug-2026
Reference Invoice NumberINV-2026-10233 (blank for unmatched)
Business UnitUS1 Business Unit
CurrencyUSD
Credit Amount-1,250.00
Line Type / DescriptionItem — Returned Units (Qty 25)
Tax Classification CodeSTANDARD_REVERSE
Distribution Combination01-000-2210-0000-000 (AP Liability offset)
Payment TermsNet 30 (inherited from reference invoice)

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

Test Steps

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

#User ActionExpected Result
1
Navigate to Invoices
Open the Invoices work area and select Create Invoice
Create Invoice page opens with Business Unit defaulted
2
Set Invoice Type
Set Invoice Type to Credit Memo
Invoice Type = Credit Memo
Header fields adjust to accept a credit-typed transaction
3
Select supplier
Enter the supplier and supplier site
Redwood Office Supplies Inc. / RWD-US-EAST
Supplier defaults (liability account, payment terms, currency) populate
4
Enter credit memo header
Enter the credit memo number and credit memo date
CM-2026-08421 / 12-Aug-2026
Header accepts values within an open accounting period
5
Reference original invoice (if matched)
Enter the reference invoice number to link the credit to an existing invoice
INV-2026-10233

Skipped for unmatched/standalone credit memos

System retrieves the invoice's supplier, currency, and open balance for validation against the credit
6
Enter credit line(s)
Enter one or more credit lines with description, quantity or amount, and account distribution
Item line, Qty 25, -1,250.00
Line amount is captured as a negative/credit value against the correct account
7
Apply tax classification
Select or confirm the tax classification code for the credit line
STANDARD_REVERSE
Tax is calculated and reversed proportionally to the credited amount
8
Review distributions
Review or adjust the distribution accounting combination generated for the credit line
01-000-2210-0000-000
Distribution mirrors or appropriately offsets the original invoice's accounting
9
Validate credit memo
Submit the credit memo for validation
Validation completes with no holds; status changes to Validated
10
Submit for approval
Submit the validated credit memo into the approval workflow
Credit memo routes to the configured approver based on amount and business unit rules
11
Approve credit memo
Approver reviews and approves the credit memo
Approval status updates to Approved and the document becomes eligible for accounting
12
Create accounting
Run Create Accounting for the credit memo
Accounting entries post: debit AP Liability, credit Expense/Charge account, reversing the invoice's original entry proportionally
13
Confirm available credit
View the supplier's account balance to confirm the credit is available for application or refund
Credit memo amount appears as an open credit balance against the supplier
14
Validate business outcomeBusiness assertion
Confirm the credit memo correctly reduced the supplier's payable balance and, where matched, the referenced invoice's open amount
Supplier balance and referenced invoice balance reflect the credited amount accurately, with no unexpected variance

Expected Results

  • Credit memo is created with a valid negative/credit amount against an active supplier and site
  • Unmatched credit memos post correctly using manually entered distributions
  • Matched credit memos correctly reduce the open balance of the referenced invoice, whether full or partial
  • Tax is recalculated or reversed in proportion to the credited line amount
  • Distribution accounting reflects an appropriate offset to the original expense or liability account
  • Multi-currency credit memos inherit the correct currency and conversion rate context
  • Credit memo validates without unintended holds and routes through the standard approval workflow
  • Accounting entries post correctly, reversing the proportional share of the original invoice's accounting impact
  • The resulting credit is available for application against a future payment or for refund processing
  • Partial credits leave the remaining unmatched balance of the invoice line intact and unaffected

Key Validation Checkpoints

  • Invoice Type field correctly set and locked to Credit Memo
  • Credit amount is captured as negative or credit-typed, not a duplicate positive invoice
  • Reference invoice, when provided, belongs to the same supplier and has sufficient open balance
  • Credit memo currency matches the reference invoice currency where matched
  • Tax classification and calculated tax amount are consistent with the original transaction's tax treatment
  • Distribution combination is valid in the current chart of accounts and open period
  • Validation completes with no unresolved holds for a clean positive scenario
  • Approval workflow routes to the correct approver tier based on credit amount
  • Create Accounting produces balanced, correctly signed journal entries
  • Supplier account balance reflects the reduced payable amount post-accounting
  • Referenced invoice's open balance decreases by exactly the matched credit amount
  • Audit trail retains linkage between the credit memo and its reference invoice, if any
Core Business Scenario
Create Credit Memo
Business Steps
14
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 create credit memo 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

01
Syntra Standard Test
Reusable business process and automation logic.
02
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.
03
Jarvis AI
Analyses the standard scenario together with available test data and generates relevant scenario variations.
04
Positive + Negative Test Variations
Positive, negative, boundary and configuration-specific scenarios.
05
Regression Pack
Selected variations can be grouped into an executable suite.
06
On-Demand / Scheduled / Batch Execution
Execute immediately or schedule the regression pack for unattended batch execution.
07
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
  • Basic Supplier Credit Memo
  • Full Credit
  • Partial Credit
  • Credit Against Invoice
  • Credit Against Invoice Line
  • Multi-Line Credit Memo
  • Alternate Accounting Distribution
  • Alternate Tax Treatment
  • Foreign Currency Credit Memo
Negative Scenarios
  • Invalid Supplier
  • Invalid Reference Invoice
  • Invalid Amount
  • Invalid Distribution
  • Invalid Accounting Date
  • Closed Period
  • Invalid Matching Conditions

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 expands a single standard credit memo definition into multiple realistic supplier, amount, and matching combinations, so the same business logic is exercised across varied real-world conditions without hand-authoring each row.

Standard Library Definition

Supplier: {{Supplier}} | Site: {{SupplierSite}} | Amount: {{CreditAmount}} | Reference Invoice: {{RefInvoice}} | Currency: {{Currency}}

DataVault

Supplier=[Redwood Office Supplies Inc., Atlas Industrial Parts, Meridian Logistics Co.] | Amount=[-450.00, -1250.00, -3800.75] | RefInvoice=[INV-2026-10233, INV-2026-10981, null] | Currency=[USD, EUR, GBP]

Jarvis AI Generates

1) Redwood Office Supplies Inc. | -450.00 | INV-2026-10233 | USD
2) Atlas Industrial Parts | -1250.00 | INV-2026-10981 | EUR
3) Meridian Logistics Co. | -3800.75 | (unmatched) | GBP
4) Redwood Office Supplies Inc. | -1250.00 | (unmatched) | USD
5) Atlas Industrial Parts | -450.00 | INV-2026-10233 | EUR
6) Meridian Logistics Co. | -3800.75 | INV-2026-10981 | GBP

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 the individual credit memo variations covered by this scenario, filterable by credit type and matching condition, each mapped to Syntra Standard's automated execution engine.

IDVariationTypeKey DifferenceExecution
VAR-001Basic Unmatched Credit MemoPositive/UnmatchedNo reference invoice; manually entered distributionsSyntra Ready
VAR-002Full Credit Against InvoicePositive/Full Credit/MatchedCredit amount equals full invoice balanceSyntra Ready
VAR-003Partial Credit Against InvoicePositive/Partial Credit/MatchedCredit amount less than invoice balance; remainder stays openSyntra Ready
VAR-004Credit Against Single Invoice LinePositive/Partial Credit/MatchedCredit applies to one line of a multi-line invoice onlySyntra Ready
VAR-005Multi-Line Credit MemoPositive/MatchedMultiple credit lines across different accounts on one documentSyntra Ready
VAR-006Alternate Distribution CombinationPositive/UnmatchedNon-default expense account used for the credit offsetSyntra Ready
VAR-007Alternate Tax TreatmentPositive/MatchedDifferent tax classification code reversing a non-standard rateSyntra Ready
VAR-008Foreign Currency Credit MemoPositive/MatchedCredit currency differs from ledger currency; conversion rate appliedSyntra Ready
VAR-009Invalid Reference InvoiceNegative/MatchedReference invoice number does not exist or belongs to a different supplierSyntra Ready
VAR-010Credit Exceeds Invoice BalanceNegative/MatchedCredit amount exceeds the referenced invoice's remaining open balanceSyntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

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

Valid data → Create Credit Memo completes successfully

Negative Testing

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

  • Invalid Supplier → Expected Oracle validation
  • Invalid Reference Invoice → Expected Oracle validation
  • Invalid Amount → 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.

ScenarioOracle OutcomeTest Result
Full credit matched to open invoiceCredit memo validates and reduces invoice balance to zeroPASS
Partial credit against one invoice lineOnly the targeted line's balance is reduced; other lines remain openPASS
Credit memo referencing a nonexistent invoice numberSystem correctly blocks the reference and raises an invalid-invoice errorPASS
Credit memo entered in a closed accounting periodSystem correctly rejects the transaction date and prompts for an open periodPASS
Credit memo submitted with a suspended distribution accountValidation unexpectedly completes without flagging the inactive account combinationFAIL

Turn AI-Generated Variations into a Regression Pack

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

AP Credit Memo Regression Pack

  • Basic Unmatched Credit Memo
  • Full Credit Against Invoice
  • Partial Credit Against Invoice
  • Credit Against Single Invoice Line
  • Multi-Line Credit Memo
  • Foreign Currency Credit Memo
  • Invalid Reference Invoice
  • Credit Exceeds Invoice Balance
  • Closed Period Rejection
  • Invalid Distribution Combination
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
PackAP Credit Memo Regression Pack
ScheduleWeekly Regression
Tests20 scenarios
ExecutionBatch Mode
Start10:00 PM
EnvironmentOracle Fusion TEST
StatusScheduled

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.

38
Total Scenarios
36
Passed
1
Failed
1
Exceptions
24
Positive Tests
14
Negative Tests
38
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 — Create Credit Memo, 14 Business Steps
DataVault — Customer-Specific Test Data
Jarvis AI — Generate Positive + Negative Variations
Regression Pack — Select Relevant Coverage
SyntraFlow Execution — Each Variation
Detailed UI Actions
Business Assertions
Evidence
PASS / FAIL

Business Step → Underlying UI Actions

Business Step
Enter credit memo header and select supplier
May internally include
Open Invoices work area -> Click Create Invoice -> Select Invoice Type 'Credit Memo' -> Enter Supplier 'Redwood Office Supplies Inc.' -> Enter Supplier Site 'RWD-US-EAST' -> Enter Credit Memo Number -> Enter Credit Memo Date -> Confirm header defaults populate
Business Step
Enter credit line and validate
May internally include
Click Lines tab -> Enter Line Description -> Enter Quantity -> Enter Credit Amount as negative value -> Select Tax Classification Code -> Confirm Distribution Combination -> Click Validate -> Confirm status changes to Validated with no holds

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.

StepAction StatusBusiness Validation
Enter credit line amountPass
Apply tax classificationPass
Validate credit memoPass
Create accountingPass
Confirm supplier balance reduced by credited amountPassPass

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 Create Credit Memo 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

Download Test Case

Full objective, preconditions, test data and steps.

Add to Test Library

Save to your SyntraFlow regression suite.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Frequently Asked Questions

How is a credit memo different from cancelling an invoice in Oracle Fusion?
Cancelling an invoice voids the original transaction entirely, reversing its accounting as if it never existed. A credit memo is a new, separate document that records a supplier's credit against the AP balance — it can stand alone or reference an existing invoice, but it does not delete or void that invoice.
What is the difference between a matched and unmatched credit memo?
A matched credit memo references a specific existing invoice (or invoice line) and reduces that invoice's open balance directly. An unmatched credit memo is entered as a standalone document with its own manually keyed distributions, with no link to a prior invoice — commonly used for overpayment recovery or vendor rebates not tied to one transaction.
Can a credit memo be partially applied to an invoice?
Yes. A partial credit reduces only part of the referenced invoice's or invoice line's balance, leaving the remainder open for normal payment. Oracle Fusion validates that the credited amount does not exceed the available open balance on the referenced document.
How does tax get handled on a credit memo?
Tax is recalculated or reversed proportionally to the credited line amount, using the same or a corresponding reversal tax classification code as the original transaction, so the net tax liability accurately reflects the reduced taxable amount.
Does a credit memo automatically offset a supplier payment?
Not automatically — once validated and accounted, the credit memo becomes an available open credit balance on the supplier's account. It is then applied during a subsequent payment run (offsetting the payment amount) or, if no future payable exists, processed as a refund.
What happens if a credit memo is entered in a closed accounting period?
Oracle Fusion Payables blocks the transaction date and requires the user to select a date within an open period, or the accounting period must be reopened by a controller before the credit memo can be validated and accounted.
Download Test Case