Integrating Spiff with Salesforce: the plan reads an opportunity or an order

The commission run paid the sales manager. The opportunity owner was the person the written plan pays. The manager's name sat on a team field somebody had mapped because it was present. The owner field was the one payroll uses, and the run did not read it. On payday the figure in the tool and the figure in the pay file disagreed, and a second argument started about the rate. The demo had used a percentage nobody in payroll recognised. The close date had been edited after the period locked, and the run had treated the edit as a new credit. Sellers opened disputes. The acquisition date had been used as permission to invent a rate and to skip the question of who is paid. Payroll does not pay an invented rate, and it does not pay the wrong person because a field was nearby.

That payday is the integration this page is about. Salesforce completed the Spiff acquisition on 1 February 2024. Spiff is incentive compensation. It does not set your commission rate. The connector is the opportunity or the order the plan reads. Name the failure when the plan pays the wrong person. Do not invent a payout percentage. A diagram that skips the object and the person is a poster. The build sits on the Spiff implementation page. The ownership story sits on what happened to Spiff. This page is the person who gets paid.

#The system

This page quotes the completion once: "Salesforce completed its acquisition of Spiff on February 1, 2024." Read it as a date. Completion was 1 February 2024. The sentence does not describe your plan, your accelerators, or your payroll file. It does not say the product sets a rate. It does not say which person an opportunity pays. It does not give a price or an end date. Write 1 February 2024 in the pack, and stop adding a percentage the sentence does not contain.

The team joined Sales Cloud. That places the work next to opportunities and orders. Joining Sales Cloud is not a rename of the opportunity, and it is not a new commission percentage. You bring the plan rules you already pay people on. The product can calculate from those rules. It does not invent them. Customers who already pay on a written plan keep that plan. The completion changed the owner of the product. It did not, on the facts this page uses, change what a seller is owed.

Name the system that holds the plan, and the system that holds the opportunity or the order. Spiff reads. Salesforce holds the record the plan is allowed to read. Payroll, or whatever file actually pays, is a third place if the pay file is not the plan. Write it down if the payday figure and the plan figure can differ. The opening story was that difference, plus the wrong person. Two failures. Do not call them one "sync".

This page will not invent a connector product name beyond the object the plan reads. The connector is the opportunity or the order. It is not a middleware SKU, and it is not a daily cap. The cited sentence does not publish a licence fee. This page does not give Spiff an end date. The completion was not a shutdown.

#The object

The connector is the opportunity or the order the plan reads. Pick one for this plan, or write two lines if the plan truly reads both. An opportunity the seller owns is a fair object when the written plan pays on closed opportunities. An order is a fair object when the plan pays when the order is booked, not when the opportunity is merely likely. "The deal" is not an object. A deal can be an opportunity, an order, or both, and those dates differ. The run that paid on a close-date edit was reading a field without a lock. Name the field as well as the object.

Name the person field the plan may pay. Owner is a fair field when the written plan says the owner is paid. A manager field is a fair field only when the plan says the manager is paid. Mapping a field because it is on the layout is how the manager was paid. Write the field. If the plan pays a split, name every person field in the split and the rule that uses them. Do not invent the split percentages. They come from the plan you already pay, or they are not in the design.

Do not invent a payout percentage. A demo rate is not a plan. If payroll cannot recognise the number, it is not the rate. Leave the rate blank in the tool until the written plan is in the room. A blank is more honest than a round number that makes a chart look finished. Accelerators, caps, and draws follow the same rule. This page will not supply them. Your plan will, or the line stays empty.

The object has a period. Name when the plan stops reading edits. A close date changed after the lock is not a new credit unless the plan says so. Write the lock. A run that re-reads an open field will pay twice and look accurate. The dispute on payday is the cost of that missing line.

#The failure when the plan pays the wrong person

The failure is the wrong person. The manager was paid. The owner was not. Or both were paid and the plan names one. Or a leaver was paid because the user was deactivated in Salesforce and the plan still held the old id. Write the sentence: the plan paid this person, the plan should have paid that person, and here is who is told before payday, not after.

Say what payroll does when the names disagree. They do not average the two amounts. They do not pay both to be kind. They stop the file, or they pay the person the written plan names, and the other figure waits. Write which. A dispute queue with no named reader will open on payday in public. Name the reader on a day that is not payday.

A wrong rate is a second failure, and it is not an excuse to invent a better one. If the rate in the tool is not the rate in the plan, the tool is wrong. Correct it from the plan. Do not tune the percentage until the pay file matches a demo. The demo is not a source.

The call does not land at all when the opportunity or the order is missing, the owner field is blank, or the run points at a sandbox the pay file does not use. Each of those should pay nobody, not a default manager. A default person is how the wrong person gets paid on a quiet record. Refuse the blank. Hold the line out of the file. Tell the named reader.

Do not describe the miss as a CRM migration. You are not reloading opportunities so a commission can calculate. You are reading the object the plan already uses. If the object is wrong, change the line. Do not move the CRM to suit a percentage you invented.

#A diagram that omits three names is a poster

A diagram that does not name the system, the object, and the failure is a poster. Spiff's logo, an arrow, and "Sales Cloud" do not say whether the plan reads the opportunity or the order, which person field it pays, or what happens when that person is wrong. Draw the object. Draw the person field. Draw the payday failure and the reader who sees it before the file goes out.

Do not draw a percentage on the arrow. A number on a poster becomes the rate. If the plan's rate is not in the room, the arrow has no number. Write "plan rate, not invented" on the line if someone demands a figure.

Do not draw every object in the sales process. A quote, a lead, and a contract are not the connector until the plan says it reads them. Cross them out. One object, or two named ones. The rest is a poster about the company.

#What you settle before a run pays anyone

Write five lines before a run. The object the plan reads. The person field. The rate's home, which is the written plan, not this page. The lock. The person who stops a file when the name is wrong.

Then say what you are not buying. You are not buying a commission rate. You are not buying a percentage for the demo. You are not buying a migration of opportunities. You are not buying a price this page does not state. You are not buying an end date. Bring the plan you already pay. Leave the blank where the plan is silent.

The implementation page is where the plan rules and the refusal to invent a rate are taken apart. What happened to Spiff is where 1 February 2024 and the refusal to invent a purchase price are kept. Use those pages when the meeting argues about the acquisition. Bring the meeting back to the person who was paid.

Agree who may point the plan at a new field. A manager field is a new design, not a convenience. The poster does not gain a person because the layout had a spare lookup.

#A test you can run

Pick one closed opportunity or one order whose owner payroll already agrees. Run the plan in a place that cannot pay. Confirm the person on the result is the owner, not the manager, unless the written plan says otherwise. Confirm the rate matches the plan. If you had to type a rate to make the run finish, the test failed. Remove the typed rate.

Then force the wrong person. Blank the owner, or point a copy of the record at the manager only. The result should pay nobody, or it should raise the named reader. It should not pay the manager by default. If it does, the mapping is the Saturday failure, waiting for payday.

Change the close date after your lock, on a test record. Confirm it does not create a second credit. If it does, the lock is not a lock. Fix that before anyone trusts the file.

The integration is ready when a payroll clerk can see the object, the person field, and the lock without asking which demo rate was used. If the page still pays the manager because the field was present, send it back. 1 February 2024 did not decide who is owed.