Oracle ERP Testing Tool > Test Library > Financials > Accounts Receivable > Receipts

Syntra Standard Oracle Test Library

Oracle Fusion Create Standard Receipt Test Cases

Validate creation of a standard customer receipt in Oracle Fusion Receivables using a valid customer, receipt method, remittance bank account, currency, amount and receipt date, and confirm the resulting receipt is correctly recorded.

Test ID	ORCL.O2C.AR.RCP.CREATE.STANDARD
Application	Oracle Fusion Cloud
Product	Financials
Module	Accounts Receivable
Process	Receipts
Business Flow	Order-to-Cash
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 28 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates that Oracle Fusion Receivables can create a standard customer receipt using a valid customer, receipt method, remittance bank account, currency, amount and receipt date.

The scenario should confirm that:

the correct business unit and customer are selected for the receipt
the receipt method and remittance bank account are valid and accepted for the transaction
the receipt amount, currency and receipt date are correctly applied
Oracle Fusion creates the receipt and returns a retrievable receipt number
the receipt status reflects successful creation
the resulting receipt record is available for subsequent application, unapplication and reversal scenarios

This scenario validates creation of the receipt itself. Applying a receipt to a transaction, partial application, unapplication and reversal are covered by separate test scenarios within the same AR Receipt lifecycle.

When to Use This Test

Functional testing of standard receipt creation for a new Oracle Fusion Receivables implementation
Regression testing of receipt creation after an Oracle quarterly update affecting Receipts
UAT sign-off for AR receipt entry controls before go-live
Baseline case referenced by the apply, partial application, unapply and reverse scenarios within the same AR Receipt lifecycle

Where This Test Fits in the AR Receipt Process

Open Receivables

→

Create Receipt

→

Select Business Unit

→

Select Customer

→

Select Receipt Method

→

Select Bank Account

→

Enter Amount/Currency/Date

→

Verify Receipt Status

This test covers creating a standard customer receipt and confirming the resulting receipt number and status. It is the entry point for the AR Receipt lifecycle and is a prerequisite for the subsequent application, partial application, unapplication and reversal scenarios.

Next Stage →

Apply Receipt

Preconditions

The Receivables business unit is configured for receipt entry.
An active customer, and where required a customer account and customer site, is available.
The receipt method used for the test is active and configured for the business unit.
A remittance bank account is configured for the receipt method and business unit.
The receipt currency is enabled for the business unit or customer.
The receipt date falls within a valid, open period.
The test user has receipt-entry privileges in Oracle Fusion Receivables.

Exact preconditions and field requirements vary by Oracle Fusion implementation, receipt method and business unit configuration.

Sample Test Data

Business Unit	${BUSINESS_UNIT}
Customer	${CUSTOMER}
Customer Account	${CUSTOMER_ACCOUNT}
Customer Site	${CUSTOMER_SITE}
Receipt Method	${RECEIPT_METHOD}
Remittance Bank Account	${REMITTANCE_BANK_ACCOUNT}
Receipt Number	${RECEIPT_NUMBER}
Receipt Amount	${RECEIPT_AMOUNT}
Currency	${CURRENCY}
Receipt Date	${RECEIPT_DATE}

Sample values are illustrative. Replace them with valid customer, banking and currency data from the target Oracle Fusion environment; not every field applies to every receipt method or configuration.

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion Cloud with a user account that has Accounts Receivable receipt-entry access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Receivables Navigate to the Receivables work area.	The Receivables work area opens successfully.
3	Open Receipts Open the Receipts task within Receivables to begin creating a new receipt.	The Create Receipt page opens.
4	Create a New Receipt Start a new standard receipt entry.	A blank receipt entry form is displayed, ready for input.
5	Select Business Unit Select the business unit for the receipt. ${BUSINESS_UNIT}	The selected business unit is accepted and applicable receipt options are updated accordingly.
6	Select Customer Select the customer, and customer account or site where applicable, that the receipt is for. ${CUSTOMER} / ${CUSTOMER_ACCOUNT} / ${CUSTOMER_SITE} This single business step replaces multiple technical actions such as searching for the customer, selecting the account and selecting the site where applicable.	The selected customer is accepted and associated with the receipt.
7	Select Receipt Method Select the receipt method to be used for the receipt. ${RECEIPT_METHOD}	The selected receipt method is accepted and applicable bank account options are updated accordingly.
8	Select Remittance Bank Account Select the remittance bank account the receipt will be deposited to. ${REMITTANCE_BANK_ACCOUNT}	The selected bank account is accepted as valid for the receipt method and business unit.
9	Enter Receipt Amount Enter the receipt amount. ${RECEIPT_AMOUNT}	The receipt amount is accepted without validation errors.
10	Enter Currency and Receipt Date Enter the receipt currency and receipt date. ${CURRENCY} / ${RECEIPT_DATE}	The currency and receipt date are accepted without validation errors.
11	Save Receipt Save the receipt to submit it for creation. ${RECEIPT_NUMBER}	Oracle Fusion creates the receipt and returns a confirmation.
12	Verify Receipt Number and StatusBusiness assertion Retrieve the saved receipt and confirm the generated receipt number and resulting receipt status. This is the main business assertion for the scenario — the test does not stop merely because the save action succeeded; the saved receipt must be retrievable with the correct details.	A receipt number is generated and retained, and the receipt status correctly reflects successful creation with the entered customer, amount, currency, method and bank account.

Expected Results

A standard receipt is created successfully using a valid customer, receipt method, remittance bank account, currency and amount.
The correct receipt amount and currency are applied.
The receipt method and remittance bank account match the selected values.
Receipt status reflects successful creation.
A receipt number is generated and retained.
The receipt record is retrievable for subsequent application, unapplication and reversal scenarios.

Key Validation Checkpoints

Receipt created successfully.
Receipt number generated and retained.
Correct customer associated with the receipt, where applicable.
Correct receipt amount.
Correct currency.
Correct receipt method.
Correct remittance bank account.
Correct receipt status.
Receipt retrievable after save.

Core Business Scenario

Create Standard Receipt

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 Create Standard Receipt scenario. Jarvis AI can extend this scenario by generating additional positive and negative receipt variations across customers, business units, receipt methods, bank accounts, currencies and receipt dates using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate receipt-creation test for every customer, bank account, currency and receipt method combination. Jarvis uses the standard Create Standard Receipt scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Open Receipts

The Create Receipt task is opened within the Receivables work area.

Select Receipt Details

Business unit, customer, receipt method, remittance bank account, currency and receipt date are selected.

Create Receipt

The receipt is saved and created in Oracle Fusion Receivables.

Confirm Receipt

Receipt status and the generated receipt number are confirmed.

Available for Application

The created receipt is available for application, partial application, unapplication or reversal.

Regression Pack

Selected receipt-creation variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Rather than maintaining a separate test for every customer, bank account, currency, receipt method and date combination, SyntraFlow maintains one core Create Standard Receipt scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Create Standard Receipt 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 Receivable Receipts.

Positive Scenarios

Basic standard receipt
Different customers
Different business units
Different receipt methods
Different bank accounts
Different currencies
Different receipt amounts
Different receipt dates
High-value receipt
Receipt with customer reference
Unidentified/unapplied receipt where business process permits

Negative Scenarios

Inactive customer
Invalid customer account
Invalid receipt method
Invalid bank account
Unsupported currency
Zero amount
Invalid amount
Invalid receipt date
Duplicate receipt number where applicable
Missing mandatory data
Invalid business unit
Security/access issue

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, receipt methods, banking setup and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely reflects the customers, bank accounts, currencies and receipt methods configured in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct receipt-creation scenarios relevant to the customer's actual implementation.

Standard Library Definition

Business Unit            ${BUSINESS_UNIT}
Customer                 ${CUSTOMER}
Customer Account         ${CUSTOMER_ACCOUNT}
Customer Site            ${CUSTOMER_SITE}
Receipt Method           ${RECEIPT_METHOD}
Remittance Bank Acct     ${REMITTANCE_BANK_ACCOUNT}
Receipt Number           ${RECEIPT_NUMBER}
Receipt Amount           ${RECEIPT_AMOUNT}
Currency                 ${CURRENCY}
Receipt Date             ${RECEIPT_DATE}

DataVault

Business Units
  Configured Business Units and receipt calendars
Customers
  Active customers, accounts and sites with valid receipt setup
Receipt Methods
  Check, EFT, Wire and configured remittance rules
Bank Accounts
  Remittance accounts per Business Unit and receipt method
Currencies
  USD, GBP, EUR + unconfigured pairs
Accounting Periods
  Open and closed periods per ledger

Jarvis AI Generates

Scenario 01 — Standard Customer + EFT + USD
Scenario 02 — Alternate Customer Site + Check
Scenario 03 — High-Value Receipt
Scenario 04 — Unidentified Receipt
Scenario 05 — Inactive Customer
Scenario 06 — Invalid Bank Account
...

Customer-specific test data and AI-generated receipt variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific dimensions such as customers, bank accounts and receipt configuration remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of Create Standard Receipt scenarios Jarvis can generate from this business scenario, spanning customer, method, bank, currency and date conditions. 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 Standard Receipt	Positive	Standard customer, method, bank account, currency and date	Syntra Ready
VAR-002	Different Customer	Positive/Customer	Alternate active customer used for the receipt	Syntra Ready
VAR-003	Different Business Unit	Positive	Receipt created under a different Business Unit	Syntra Ready
VAR-004	Different Receipt Method	Positive/Method	Alternate receipt method, e.g. EFT vs Check	Syntra Ready
VAR-005	Different Bank Account	Positive/Bank	Alternate remittance bank account	Syntra Ready
VAR-006	Different Currency	Positive/Currency	Receipt created in a different currency	Syntra Ready
VAR-007	Different Receipt Amount	Positive	Alternate receipt amount within normal range	Syntra Ready
VAR-008	Different Receipt Date	Positive/Date	Receipt created with a different valid receipt date	Syntra Ready
VAR-009	High-Value Receipt	Positive	Receipt amount at or near a high-value threshold	Syntra Ready
VAR-010	Receipt With Customer Reference	Positive/Customer	Customer reference or remittance note captured on the receipt	Syntra Ready
VAR-011	Unidentified/Unapplied Receipt	Positive	Receipt created without immediate application, where the business process permits	Syntra Ready
VAR-012	Inactive Customer	Negative/Customer	Customer record is inactive	Syntra Ready
VAR-013	Invalid Customer Account	Negative/Customer	Customer account is invalid or inactive for receipts	Syntra Ready
VAR-014	Invalid Receipt Method	Negative/Method	Receipt method not enabled for the business unit	Syntra Ready
VAR-015	Invalid Bank Account	Negative/Bank	Bank account not valid for the selected receipt method	Syntra Ready
VAR-016	Unsupported Currency	Negative/Currency	Currency not configured for the bank account or business unit	Syntra Ready
VAR-017	Zero Amount	Negative	Receipt amount entered as zero	Syntra Ready
VAR-018	Invalid Amount	Negative	Receipt amount is negative or non-numeric	Syntra Ready
VAR-019	Invalid Receipt Date	Negative/Date	Receipt date is outside a valid or open range	Syntra Ready
VAR-020	Duplicate Receipt Number	Negative	Receipt number matches an existing receipt, where applicable	Syntra Ready
VAR-021	Missing Mandatory Data	Negative	Required receipt field left blank	Syntra Ready
VAR-022	Invalid Business Unit	Negative	Business unit reference is invalid or not accessible	Syntra Ready
VAR-023	Security/Access Issue	Negative	User lacks receipt-entry access for the business unit or customer	Syntra Ready

Positive and Negative Receipt Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion Receivables successfully creates a receipt when the customer, receipt method, bank account, currency and amount are all valid.

Active Customer + Valid Method/Bank/Currency → Receipt Created Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around customer status, banking configuration, currency and amount during receipt creation.

Inactive Customer → Expected Customer Validation
Invalid Receipt Method → Expected Configuration Validation
Invalid Bank Account → Expected Banking Validation
Zero Amount → Expected Amount Validation
Duplicate Receipt Number → Expected Duplicate Validation

A negative test passes when Oracle correctly produces the expected validation or prevents the invalid action, not when it silently accepts invalid data.

Scenario	Oracle Outcome	Test Result
Valid receipt	Receipt created	PASS
Invalid receipt method	Configuration validation occurs	PASS
Inactive customer	Validation occurs	PASS
Duplicate receipt number	Validation occurs	PASS
Unexpected application crash	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

AR Create Standard Receipt Regression Pack

Basic Standard Receipt
Different Customer
Different Receipt Method
Different Bank Account
Different Currency
High-Value Receipt
Unidentified/Unapplied Receipt
Inactive Customer
Invalid Bank Account
Zero Amount
Duplicate Receipt Number
Security/Access Issue

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 receipt-creation scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected receipt-creation 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	AR Create Standard Receipt Regression Pack
Schedule	Nightly Regression
Tests	23 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

AR Receipt Lifecycle

Lockbox Receipt Processing creates receipts through an automated batch path and shares the Create / Import stage. Exact processing depends on receipt method, customer setup, currency and customer-specific Oracle Fusion configuration. Stages link to the corresponding test scenario family.

Create / Import

→Apply→Partial Application→Unapply→Reverse

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 Create Standard Receipt scenario, available DataVault test data and expected business outcomes to generate additional receipt-creation 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 Standard Receipt, 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

Select Customer

May internally include

Open Customer Search → Enter Customer → Select Account → Select Site → Confirm

Business Step

Save Receipt

May internally include

Validate Form → Submit Receipt → Poll Confirmation → Capture Receipt Number

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
Save Receipt	Pass	—
Enter Receipt Amount	Pass	—
Verify Receipt Number and Status	Pass	Pass

Related AR Receipt Tests

Creating a receipt is the entry point of the same customer receipt lifecycle — explore the related application and receipt-processing scenarios below.

Apply Receipt Lockbox Receipt Processing Transaction Completion

Turn This Standard Test into Your Oracle AR Receipt Regression Suite

Start with the Syntra Standard Create Standard Receipt test, use DataVault to provide environment-specific customer, bank account and receipt method data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore AR Receipts 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

Oracle ERP Testing Tool Test Library Financials Accounts Receivable AR Receipts AR Billing Syntra DataVault

Frequently Asked Questions

What does the Create Standard Receipt test validate?

It validates that Oracle Fusion Receivables can create a standard customer receipt using a valid customer, receipt method, remittance bank account, currency, amount and receipt date, and that the resulting receipt number and status are correct.

How does this differ from Apply Receipt?

Create Standard Receipt focuses on the underlying mechanics of creating a receipt — selecting a customer, receipt method, bank account, currency and amount. Apply Receipt is a related scenario that attaches an already-created receipt to a specific customer transaction, such as an invoice.

Are unidentified or unapplied receipts supported by this test?

Yes, where the customer's business process permits it. Jarvis can generate a variation where the receipt is created without being immediately applied to a transaction, consistent with the customer's Oracle Fusion configuration.

Do all these receipt variations need separate library pages?

No. Jarvis AI generates customer, business unit, method, bank account, currency and date variations from this single standard scenario rather than requiring a separate indexable page for each combination.

Does SyntraFlow move real customer funds when running this test?

No. SyntraFlow automates the Oracle Fusion Receivables user interface within a test or UAT environment; it is a test automation product and does not process real payments or move real customer funds.