Salesforce QA Lead – Revenue Lifecycle Program

Revenue Lifecycle Validation

 Lead end-to-end validation of Quote Order Invoice Payment→ → →

lifecycle.

 Validate pricing, discount tiers, amendments, renewals, credit memos,

refunds, and partial payments.

 Ensure financial state modeling aligns across systems.2️⃣

Reconciliation & Financial Integrity

 Design and execute structured reconciliation strategies (expected vs actual

state modeling).

 Validate exception lifecycle handling, variance categorization, and tie-out

processes.

 Define and enforce financial system-of-record boundaries.3️⃣

Integration & SIT Ownership

 Own System Integration Testing across upstream/downstream systems.

 Validate tax integrations (e.g., Avalara).

 Perform payload-level field mapping validation and data transformation

checks.

 Ensure idempotent replay, structured retry logic, and quarantine handling

for batch failures.4️⃣

Batch & High-Volume Validation

 Validate high-volume batch processing scenarios.

 Detect malformed data, duplicate handling, and reprocessing controls.

 Account for governor limits and platform constraints.5️⃣

QA Leadership & Governance

 Lead a QA team (manual + automation).

 Maintain requirement-to-test traceability.

 Conduct defect root cause analysis and implement prevention controls.

 Ensure audit traceability and compliance alignment.

Required Skills & Experience

 8+ years in Salesforce QA with strong Revenue Cloud.

 Deep experience validating financial lifecycle flows in Revenue Cloud

 Strong understanding of reconciliation frameworks and financial state

validation.

 Hands-on experience in SIT ownership for integration-heavy programs.

 Knowledge of batch architecture validation and error lifecycle modeling.

 Exposure to automation frameworks (Selenium/Cypress preferred).

 Strong analytical and documentation skills.

Good to Have

 Healthcare domain exposure (Behavioral Health / Insurance).

 Experience handling discount miscalculation or revenue-impacting defect

prevention controls.

 Experience defining financial boundary enforcement across systems.