DEV Community

SARVO
SARVO

Posted on

SAP Implementation Partner With a Guarantee: Write Acceptance Criteria That Make 'Delivered' Testable

If you are hiring an SAP implementation partner with a guarantee attached, the clause that matters most is not the refund clause. It is the definition of "delivered". A money-back promise on undelivered work only helps if both sides can agree, without a long argument, whether the work was delivered. For technical teams, that means acceptance criteria you can actually test.

This guide shows how to write them, using the SARVO Verified Guarantee as the worked example.

What the guarantee actually covers

On SARVO, the Verified Guarantee applies when you hire a SARVO Verified partner through SARVO. The terms, as set out on the SARVO Verified Guarantee page, are:

  • The partner refunds 100% of the initial project fees if the agreed work is not delivered.
  • You can also cancel in writing within the first 14 days, no reason needed.
  • The partner pays the refund within 14 days.
  • If a refund is not honoured, SARVO reviews both sides and mediates, and can remove the partner's Verified tick. SARVO is not a party to your contract and does not hold your payments; you pay the partner directly.

What it does not cover:

  • Work or licences already delivered and used
  • Third-party software costs, such as vendor subscriptions
  • Requests made after the window
  • Partners who are not SARVO Verified

Terms are set per agreement, so confirm the guarantee clause is in your contract before you sign. If it is missing, ask the partner to add it.

Notice the phrase that carries the weight: agreed work. For an SAP project, that is where your acceptance criteria come in.

Why "delivered" is hard to define on SAP projects

SAP projects tend to be large, phased, and dependent on your own team. A configuration can be technically complete but untested. A data load can run but produce a trial balance that does not match. An interface can work in a test system but not against production volumes. Without written criteria, "delivered" becomes a matter of opinion.

That uncertainty hurts both sides. Buyers cannot tell whether a phase is done; partners cannot close a phase cleanly. Good acceptance criteria fix this, with or without a guarantee.

SAP implementation partner with guarantee: scope the initial phase tightly

The guarantee refers to initial project fees. The practical implication for buyers is to make the initial phase a well-defined, testable piece of work, rather than a vague first payment against a large programme.

Ways to do that:

  • Define the initial phase as a discrete deliverable: for example, a fit-gap assessment with documented outputs, or a configured prototype for a named set of processes.
  • List exactly what the initial project fees pay for.
  • Keep licence costs and vendor subscriptions out of that list. Third-party software costs are excluded from the guarantee, so mixing them into the initial fees only creates confusion.

How to write acceptance criteria a developer would respect

Use the same discipline you would use for a user story.

1. Name the process, not the module

Weak: "FI module configured."
Better: "Vendor invoice posting for domestic purchases with GST, from goods receipt to invoice posting, tested end to end with five sample invoices provided by the buyer."

2. Specify the test data

State whose data, how many records, and which edge cases. Provide the samples yourself, so the test is not designed around what already works.

3. Specify the expected result

Expected postings, expected tax amounts, expected report output. If a number must match, say which number and to what.

4. Name who tests and who signs off

A named person on your side runs the test; a named person signs off. Give them a time box.

5. Define the evidence

Screenshots, test logs or a signed checklist. Something both sides can point to.

6. Separate defects from change requests

Agree how a failing test is classified: a defect against agreed scope (partner fixes) or a new requirement (change request). This one rule prevents most disputes.

A sample acceptance list for an initial SAP phase

Adapt this to your scope. Each line should be testable by someone who did not build it.

  • Documented list of in-scope processes, signed by both sides
  • Organisation structure configured as per the agreed design document
  • Each in-scope process executed end to end in the test system with buyer-provided data
  • Tax calculation matches the buyer's expected values for every sample document
  • Agreed reports produce output that reconciles with the buyer's reference figures
  • Agreed interfaces tested with sample volumes stated in the scope
  • Open defects list reviewed; no defects classified as critical remain open
  • Training for named key users delivered and attendance recorded

The 14-day window and your test plan

The 14-day written cancellation exists for a reason: it gives you an early exit if the engagement is not a fit. Use those two weeks deliberately:

  • Hold the kickoff and meet the actual delivery team
  • Review the first design or fit-gap outputs
  • Check that the team's understanding of your processes matches yours

If something is clearly wrong, the window is the time to say so in writing. After it closes, the remaining protection is for agreed work not delivered, which is why the acceptance criteria above matter.

Finding SAP partners

SARVO lists SAP implementation companies on its SAP partners in India page. Listing a technology does not mean the company is an authorised SAP partner, and being listed is not the same as being SARVO Verified. The guarantee applies only when you hire a SARVO Verified partner through SARVO, so filter for SARVO Verified partners if the money-back terms matter to you, and confirm the clause is in your contract.

Checklist before you sign

  • Initial phase defined as a discrete deliverable
  • Initial project fees itemised, with licences and third-party costs separated
  • Acceptance criteria written per process, with test data and sign-off owners
  • Defect vs change-request rule agreed
  • Guarantee clause present in the contract
  • Kick-off and first reviews scheduled inside the first 14 days

Write the criteria once and you get a cleaner project whether or not you ever need the guarantee. If you want SARVO to introduce Verified partners, the free matching request on the guarantee page is the place to start.

Disclosure: I work on SARVO.

Top comments (0)