# ERP vendor selection meeting agenda | SourceX

Canonical: https://refer.sourcex.si/resources/vendor-selection-meeting-agenda
Last updated: 2026-11-04

The decisions at risk are the ones written on closed documents: price overrides, credit-hold releases, accepted three-way-match variances, out-of-policy returns and write-offs with reason codes. A clean-data scope moves what the new ERP needs to run and leaves that record behind. This 30-minute agenda brings the owner and the controller into one room for five timed blocks, sets out who answers each one and what a good answer sounds like, and closes with the owner's decision, plus an optional, disclosed introduction to SourceX.

It is one of the tools in the [ERP vendor selection playbook](/guides/moment-vendor-selection-erp-selection-advisors). Book it for the narrow window when the shortlist exists, the data approach is being drafted, and the word "clean" has appeared in a scope document: too early and nobody knows what will move, too late and the scope is signed.

## Who sits at the table

| Seat | Usually held by | Why they are there |
|---|---|---|
| Owner | CEO, with the CFO | Decides where exception history goes and whether to hear about licensing |
| Controller | Head of finance operations | Knows variance, write-off and credit-memo history |
| Process owners | Sales operations and credit managers, on call | Speak for overrides and holds if the controller cannot |
| Selection advisor (you) | The partner running the agenda | Chairs, keeps time, records answers |

Vendors, implementation partners and the wider project team are not invited. The meeting is about the company's own history, not about either shortlisted product.

## The agenda at a glance

Illustrative. A 310-person industrial distributor choosing between two cloud ERPs, with a proposed scope of "clean data plus two years of closed invoices".

| Minutes | Question for the block | Who answers | Output |
|---|---|---|---|
| 0 to 4 | What date or event is driving the selection? | Owner | The platform or contract date |
| 4 to 10 | What does the proposed migration scope carry, and what does it exclude? | Controller | Scope in one sentence |
| 10 to 20 | Which operational decisions would vanish from a clean-data migration? | Controller and process owners | Exception types, years held, owner per type |
| 20 to 25 | What happens to the old ERP after go-live, and for how long? | Owner | Read-only period or decommission date |
| 25 to 30 | Would you like to hear whether that history could be licensed? | Owner | Yes: introduction. No: stop |

## What a good answer sounds like

### Minutes 0 to 4: the driver

Good: "GP support ends in 2031 and our hosting contract renews in 2027, so we want to be live by then." Weak: "it is time to modernize". A dated driver tells you whether the old system will be switched off or left running.

### Minutes 4 to 10: the scope

Good: "Customers, items, vendors, open orders, opening balances, and two years of closed invoices." That sentence is the baseline. Everything older and everything recorded on closed documents falls outside it.

### Minutes 10 to 20: the exception history

This block is the reason for the meeting. Use three prompts in order, and let the controller and process owners do the talking.

| Prompt | A good answer sounds like | If the answer is vague |
|---|---|---|
| "Where do people record a judgment call that breaks the normal rule?" | "Pricing exceptions carry a reason code on the order line; credit releases go in the hold log with a note." | Ask for the screen or field name, not an example |
| "Does the proposed scope bring any of that across?" | "Only two years of AP matching exceptions; nothing from sales or credit." | Read the scope sentence from block two back to them |
| "How far back does it go, and who could explain it?" | "Eleven years for pricing, nine for credit; the sales operations and credit managers know it best." | Ask for the earliest fiscal year in the system |

Write down one line per exception type: what it is, how many years, whether the scope carries it, and who can speak for it. Nobody needs to open a record to answer.

Accepted matching exceptions are worth explaining in the room. Microsoft's documentation for Dynamics 365 Finance describes three-way matching as comparing invoice price with purchase order price, and invoiced quantity with the product receipt quantity; a quantity difference is a matching error. Each time someone accepted that error, the approval and its reason were recorded on a document the new system will never open.

Good answers name a person for every row. A row with no owner is itself a finding.

### Minutes 20 to 25: the old system's future

Good: "Read-only for 18 months, then decommissioned with the hosting contract." This tells the owner how long the exception history stays reachable without any extra decision. "We have not decided" is a valid answer and a useful one; it means nobody owns the question yet.

### Minutes 25 to 30: disclosure first, then the question

Say it plainly before you ask: SourceX licenses approved business data directly from companies for AI training and evaluation; you are a referral partner and may receive a reward if a qualifying license completes; SourceX funds it separately and it never reduces the company's payment; a lead, meeting or signature alone does not trigger payment. Then ask, and accept either answer. Your vendor recommendation does not change with it.

## Platform dates that often set the clock

Dated vendor events are a common reason a selection exists at all, and they decide how long the old system stays reachable. Microsoft has announced the end of support for Dynamics GP, with security updates available until April 30, 2031. SAP lists mainstream maintenance for SAP ERP 6.0 enhancement packages 6 to 8 through the end of 2027, with optional extended maintenance until the end of 2030 at a premium. Use the date the company names in the first block; do not import one it has not mentioned.

## Answers that end the meeting early

| What you hear | Why to stop | What to record |
|---|---|---|
| "We are migrating full history, not clean data" | Nothing is left behind | Full-history scope |
| "We keep the old system indefinitely" | No loss event exists | Indefinite read-only |
| "Our contracts bar any reuse of transaction records" | The company may lack rights to license | Rights restriction noted |
| "We have about 40 staff" | Below the 50 full-time employee baseline | Headcount; no introduction |
| "Not interested in licensing" | The owner declined | Declined; close the file |

## The decision you leave with

A good meeting ends with one written line per exception type, an owner for each, the old system's end date, and the owner's answer to the opt-in. Send the owner the first three items; keep the disclosure and the opt-in in your own notes.

If the answer is yes, check the baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Then use the [vendor selection introduction email](/resources/vendor-selection-introduction-email). The [vendor selection archive context checklist](/resources/vendor-selection-archive-context-checklist) tracks the dates between scope sign-off and switch-off.

Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application. Unknown until SourceX reviews it: dataset fit, the rights review result and any offer. The [software selection consultant page](/for/software-selection-consultant) covers the role more broadly; the [sell-side kickoff agenda](/resources/sell-side-kickoff-meeting-agenda), the [AI strategy offsite agenda](/resources/ai-strategy-offsite-agenda) and the [CFO monthly review agenda](/guides/monthly-financial-review-meeting-agenda-cfo) show the same opt-in pattern in other meetings.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the exception table fills with years of history and the owner says yes at minute 25, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before the migration scope is signed.

## Sources

- https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2024/09/25/announcing-end-of-support-for-dynamics-gp/
- https://support.sap.com/en/offerings-programs/strategy.html
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/three-way-matching-policies
- https://refer.sourcex.si/terms
