
Oracle Revenue QA Engineer
Wipro • Singapore, Singapore
**Role & seniority: ** Functional/Testing Engineer (Oracle Revenue Management/Receivables domain); senior-level hands-on, functional consultant mindset (evidence, triage, regression ownership).
**Stack/tools: ** Oracle Fusion (Revenue Management/RMCS, Revenue Accounting, Receivables), Oracle ERP patch/regression testing; ESS jobs, OIC, REST/SOAP, SFTP; SQL for reconciliation evidence; Jira/ALM; Postman/API testing; Playwright; AI-agent execution (Claude-assisted authoring mentioned).
**Top 3 responsibilities: **
-
Quarterly Oracle patch testing with release-note impact analysis (RMCS/Revenue Accounting/AR/Tax), define regression scope by revenue-recognition risk, execute scenarios, capture evidence, maintain tracker.
-
Revenue functional testing end-to-end: contracts/performance obligations/recognition & scheduling (ESS), revenue accounting entries and GL impact, billing-to-revenue reconciliation, AR processes, tax/WHT validation.
-
Integration/data validation across upstream source → Fusion → RMCS → revenue accounting → GL → reporting; validate migrations and interface correctness; use SQL evidence.
-
Must-have skills:
-
Hands-on functional expertise in Oracle Revenue Management (RMCS) and Oracle Fusion Receivables.
-
Strong revenue accounting fundamentals (recognition, deferred vs recognized, billing-to-revenue reconciliation, subledger→GL) plus tax/WHT knowledge.
-
Test design/execution with **scena
-
Full Description
Key Responsibilities
Quarterly Oracle patch testing: analyse release notes for impact on RMCS, Revenue Accounting, AR and Tax; define sanity → focused → full regression scope by revenue-recognition risk; prepare environments and data; execute scenarios, capture evidence and own the tracker.
Revenue functional testing: revenue contracts, performance obligations, recognition and scheduling via ESS jobs; revenue accounting entries and GL impact; billing-to-revenue reconciliation; Receivables (billing, receipts, adjustments, credit memos, invoice approval); tax and withholding on revenue transactions.
Integration and data validation: validate the chain upstream source → Fusion → RMCS → revenue accounting → GL → reporting; interfaces (OIC, REST/SOAP, SFTP); Fusion-to-RMCS migration correctness; SQL queries as reconciliation evidence.
Automation and AI-enabled execution: maintain patch automation for revenue and AR scenarios; separate genuine failures from environment issues; support the move to Playwright and AI-agent execution.
Regression ownership: build and maintain regression suites across RMCS, Revenue Accounting and AR; run daily regression, triage failures and drive closure against fix-rate and burn-rate goals.
Project and enhancement testing: functional, integration/E2E and regression testing for revenue projects — reconciliation migration to out-of-the-box Oracle Revenue Management, RMCS data-model and upstream application changes, contract-compliance validation; test strategy, scenarios, cases and RTM.
Defect management: log defects with repro steps, evidence, severity and functional RCA; adhere to SLAs and escalation protocol.
Close, control and reporting: support quarter-end revenue close and reporting; production validation after deployment; SOX-style evidence and audit support; status updates, test summary and sign-off packs; work with Revenue/Controllership SMEs, engineering and Oracle consultants. Required Skills (Must Have)
-
Hands-on functional knowledge of Oracle Revenue Management (RMCS) — contracts, performance obligations, recognition, scheduling, ESS jobs — and Oracle Fusion Receivables.
-
Strong revenue accounting fundamentals: recognition principles, deferred vs. recognised revenue, billing-to-revenue reconciliation, subledger-to-GL flows; working knowledge of transaction tax / WHT.
-
Test scenario/case design, execution and evidence; defect lifecycle and triage; SIT/UAT support; ERP patch and regression testing; release-note impact analysis; RTM, test summary reports and sign-off packs.
-
Clear, numbers-first status reporting; thinks like a functional consultant, not a script-runner.
-
Good to Have
-
Automation and data (strongly preferred): automating long-running ESS/job-dependent flows, Playwright, AI-agent test execution, SQL for revenue reconciliation.
-
Jira / ALM; Postman / API testing; Claude-assisted test authoring.