Data Sources

A company integrates Salesforce with its ICM platform via a nightly batch extract. Every evening at 11 PM, a scheduled job pulls all opportunities with 'Closed-Won' status changed that day, maps the Salesforce fields (Amount, CloseDate, Owner, Product Family) to ICM fields (Revenue, BookingDate, PayeeID, ProductCode), and loads them as order records. A reconciliation report runs each morning comparing Salesforce closed-won count against ICM orders received.

Section 2.4 — Data Sources
Compensation calculations are based on eligible transactions sourced from the company CRM system of record (Salesforce). Orders are extracted daily and loaded into the compensation platform. In the event of a discrepancy between CRM data and compensation records, the CRM system of record shall prevail. Reps must ensure their CRM data is accurate; disputes based on missing or incorrect CRM entries will be resolved per Section 8.

Integration Health Dashboard showing: records received today vs. expected, field mapping error count, duplicate records detected, last successful sync timestamp, and a 30-day trend line of daily record volumes with anomaly flags.

The SPM platform is configured to pull a nightly extract from SAP containing all invoices with status 'Posted' dated within the prior 24 hours. The extract maps SAP field VBELN (billing document number) to the SPM transaction ID, NETWR (net value) to credited amount, and ERDAT (creation date) to the commission recognition date, feeding 150–300 daily transactions into the comp engine.

Sales credit for all hardware and software transactions shall be sourced exclusively from ERP invoice records with a posting status of 'Complete.' CRM opportunity data may not substitute for ERP data as the basis for commission calculation. Transactions absent from the ERP extract will not be credited until the following processing cycle after the ERP record is confirmed. SPM Data Engineers are responsible for maintaining the ERP-to-SPM field mapping documentation and validating extract completeness before each pay period close.

ERP Integration Reconciliation Report: compares transaction counts and total credited amounts between the ERP source extract and the SPM system for each processing cycle. Flags missing records, value discrepancies, and field mapping errors. Used by SPM Data Engineers and Compensation Analysts to validate data completeness before the pay period is locked for commission processing.

A hardware rep's plan credits commissions on ship date. An $80,000 order placed December 20 ships in two parts: $50,000 ships December 29 and $30,000 ships January 4. The OMS feeds both shipment records to the SPM system, crediting $50,000 (and a $2,500 commission) in December and $30,000 (and a $1,500 commission) in January.

For all hardware product lines, sales credit shall be assigned based on the ship date recorded in the Order Management System at the line-item level. Partial shipments are credited in the period corresponding to each shipment's recorded ship date. Orders on hold, backorders, or orders in 'Pending Fulfillment' status are not eligible for commission credit until shipment confirmation is received from the OMS. OMS data feeds to the SPM system are processed nightly with a 24-hour lag.

Order Fulfillment vs. Commission Credit Report: matches open orders from the OMS against commission credits posted in the SPM system, showing order date, expected ship date, actual ship date, partial shipment status, credited amount per period, and any gaps between OMS records and SPM credits. Used by SPM analysts to identify orders that have shipped but not yet been credited due to feed delays.

A rep's $300,000 multi-year contract is amended in Month 4 to add $75,000 in ACV, changing the TCV from $900,000 to $1,125,000. The CMS pushes the amendment record to the SPM system with an effective date, triggering incremental quota credit of $75,000 and an additional $3,750 commission (5% rate) in the amendment period.

All quota credit and commission calculations for subscription and enterprise license transactions shall reference contract records sourced from the Contract Management System as the system of record. The effective date of any contract amendment, upgrade, or cancellation as recorded in the CMS determines the period in which the compensation adjustment is recognized. Contracts not yet fully executed in the CMS (status other than 'Fully Executed') are ineligible for commission crediting regardless of CRM opportunity stage or ERP invoice status.

Contract Amendment Impact Report: lists all contract amendments processed in the period by rep, showing the original contract value, amendment date, amended value, net ACV change, quota credit adjustment, and commission delta. Used by Compensation Analysts to validate that amendment-driven commission adjustments match the terms recorded in the Contract Management System.