About the role
Salesforce Master Data Analyst · WXP Entitlements and Contractual PLs Design to Operate
E2E Software · SW CRM & Sales Automation
Job title Salesforce Master Data Analyst — WXP Entitlements and Contractual PLs
Level Intermediate · 3–5 years of relevant experience
Delivery scope Salesforce account and entitlement master data for WXP for RIS, RIS CRM and contractual renewals
Location Bengaluru (India)
Time zone AMS coverage — AMS shift from Bengaluru, overlap with US Central required
Value stream Design to Operate · E2E Software Products · SW CRM & Sales Automation
Supports WXP Entitlements · Contractual PLs · SW renewals and co-terming
Systems Salesforce (Sales Cloud, Data Migration / Account Loader) · HPD · OSS · Apollo · Excel · Jira
Why this role exists
This is a Salesforce data role. Account records, OPSI assignment, duplicate resolution, Account Loader files and the entitlements that hang off them all live in Salesforce, and all of them are worked here. The renewals order report is the input that triggers the work; the system being worked is Salesforce.
Before a renewal can become an opportunity, somebody has to establish which customer it belongs to, whether that customer already exists in Salesforce and in HPD, whether the record is clean enough to use, and what to do when it is not. Today that is done account by account, by hand. This is that work — hands-on, high volume, and more than data entry because the holder has to decide whether two records are the same company and be able to say why afterwards.
What the role owns
1 · Order cleanup and party classification
— Take the renewals order report from OSS and isolate the rows that need mastering, working across End Customer, Ship To, Sold To and Reseller rather than one field.
— Classify each row as end customer or partner. For direct orders this follows the End Customer field; for indirect orders it is a judgement across all four, supported by Copilot, Apollo and the account record.
— Treat party type as a property of the order, not of the account — the same company can be the end customer on one renewal and the reseller on the next.
— Correct address, state and province values against the Salesforce picklist before the file is built, rather than after the upload fails. Log what was changed and keep the original value.
— Consolidate multiple product lines for the same customer where the order format allows it.
2 · Account matching and disposition
— Match each end customer to its OPSI across Salesforce and HPD, and record the evidence behind the match — not only the result.
— Route every account into its disposition: valid in both systems, valid in HPD only, carrying error or duplicate data, or no HPD OPSI at all. A data-quality problem takes precedence over system presence.
— Create the Salesforce account from HPD where the OPSI exists but the account does not, and apply OPSI assignment where none has been made.
— Flag duplicates and assemble the comparison — former names, aliases, address variants, order history — so the merge-or-keep decision can be made on evidence.
— Where no OPSI exists, assemble the identity evidence pack the Master Data Team asked for: legal entity name, registration country and company URL. Supply evidence, never a conclusion.
3 · Load, error handling and opportunity creation
— Build the Account Loader and Data Migration files from the mastered list, and check before upload whether the order or opportunity already exists in Salesforce — rework that lands after the work is done is the most expensive kind.
— Work the Salesforce success and error files: split the failures by reason code, correct them and rebuild the corrective file.
— Escalate rather than pushing the same failing record at Salesforce repeatedly.
— Reconcile the success file back against the OPSI list so that what was loaded is what was intended, and the opportunity lands on the right account.
4 · Making the next cycle shorter
— Notice the patterns. Where the same defect, the same name variant or the same reason code comes back every run, raise it rather than correcting it a second time.
— Describe each repeating case clearly enough that the Product Owner and the Salesforce developer can turn it into a validation or a matching rule — the holder identifies the rule, the developer builds it.
— Test rules once built against real records and say honestly whether they work, including where they produce wrong matches.
— Build the simple helpers that are within reach — spreadsheet lookups, reconciliation templates, saved reports. Anything beyond that goes to the developer.
5 · Where this work lands
— WXP Entitlements — an entitlement is only as good as the Salesforce account it hangs off. One created against the wrong customer is not recoverable downstream, which is why the matching decision in section 2 matters more than the volume in section 1.
— Contractual PLs — product line data on contractual renewals, where the same customer appears across several lines and has to resolve to one Salesforce account before the renewal can be built.
— BPID and trading-structure setup in Salesforce where it blocks order flow.
— Customer 360, which consumes the same mastered account data and inherits whatever is left wrong here.
6 · How the work is run
— Work inside the Jira flow with the rest of the value stream — estimated, tracked and visible. No side queues.
— Log time against the project and the work item, so volume and progress can be measured rather than asserted.
— Keep the operating procedure for each queue current, so the work is transferable and does not sit with one person.
— Report throughput and blockers on the agreed cadence, in numbers rather than impressions.
Required experience and skills
Must have
— Three to five years of relevant experience in master data, data operations, order management or CRM data quality.
— Hands-on Salesforce data work: Data Loader or Data Migration templates, Account Loader files, success and error file handling, and the reason codes behind a failed upload.
— Able to decide whether two records are the same company from name, address, country and order history — and explain the decision afterwards. This is tested at interview with real examples.
— Comfortable working from an order report across several party fields rather than one clean customer column.
— Strong Excel — lookups, reconciliation across files, large volumes without losing rows.
— Precision and stamina under volume, with the discipline to log every change and keep the original value.
— Able to say that a record is not determinable and route it, rather than guessing to clear a queue.
— Clear written English. The evidence packs this role produces are read by people who were not in the conversation.
Attitude we are selecting for
— Treats a repeating correction as a problem to raise, not a task to repeat. We are not asking the holder to build the automation, but we are asking them to see it.
Nice to have
— Fortune 100 experience in customer master, order management, entitlements or channel operations.
— Familiarity with OPSI, BPID, HPD, OSS or equivalent enterprise customer and order master structures.
— Exposure to renewals, co-terming or subscription order flows.
— Salesforce Administrator certification, or practical experience of duplicate management rules in Salesforce.
— Any scripting — SQL, Python, Power Query — used to speed up reconciliation work. Useful, not required.
— Exposure to entitlement or subscription data models in Salesforce.