ERP Demo Script: Test Your Shortlist Before You Buy

An ERP demo script is a set of business scenarios that each shortlisted vendor must walk through using the same inputs and expected outcomes. It helps your team compare how systems handle your work, including exceptions, instead of comparing the polish of their presentations.

Start with the process that is driving your replacement decision. If subscription amendments consume your close, test an amendment. If intercompany reconciliation holds up reporting, test a mismatch. A familiar dashboard is useful, but it does not prove either problem is solved.

The scenarios below are examples you can adapt. Their amounts are invented test data, not customer results, prices, or accounting recommendations.

Download the free ERP demo evidence worksheet. Use one editable Excel copy per vendor to record the four scenarios, what you observed, delivery dependencies, and follow-up owners. Each scenario starts as not demonstrated; update its status after recording the evidence. No contact details are required to download it.

What to send vendors before an ERP demo

Give each vendor a short company profile, the workflows in scope, sample inputs, the outputs you expect, and the roles that should perform the work. Use fictional or appropriately anonymized records. Include the implementation partner when the proposed solution depends on its configuration or add-ons.

SAP's ERP evaluation guidance recommends giving candidates a script or required functions before demonstrations and checking whether important capabilities are available today. That is useful process advice even when SAP is not on your shortlist.

Ask the vendor to label each step as available in the quoted product, requiring configuration, dependent on another product, custom development, or unproven. Keep those labels separate from your score. Two systems can finish the same scenario while leaving you with very different support obligations.

Key takeaway

For each ERP demo scenario, record six things: the business requirement, the test input, the expected result, the observed result, the delivery dependency, and the person responsible for closing any gap.

These six fields are this guide's suggested evidence record. They are not an industry certification or a universal selection standard.

ERP demo script 1: a subscription changes after billing

This scenario suits a software or subscription business considering an AI accounting platform, NetSuite, or a finance application paired with a billing system.

Use a fictional annual contract and an amendment midway through the term. Have your controller specify the expected billing and revenue treatment before the demo. The test is whether the system follows the approved treatment and preserves its history.

1. Import the original contract from the system that owns it.
2. Show the invoice, the revenue schedule, and the reconciliation between them.
3. Apply the amendment and explain which upstream fields changed.
4. Trace the revised schedule back to the source document and approval.
5. Repeat the import. Show how the integration avoids a duplicate.
6. Show how a reviewer corrects a mistaken interpretation without losing the original record.

For an AI-assisted workflow, add an ambiguous contract term. Ask the vendor to show the uncertainty, the review queue, and the approval permission. A generated explanation is not enough evidence that the posting is correct.

In NetSuite versus Rillet, the relevant decision is broader suite coverage versus a finance-focused architecture. This test helps establish whether the narrower platform actually covers your difficult finance work.

ERP demo script 2: intercompany balances disagree

This scenario suits a group with multiple legal entities. Start with a fictional charge of 10,000 in the parent entity and a corresponding entry of 9,800 in a subsidiary. The mismatch is intentional; it tests the resolution workflow.

Ask the presenter to identify the discrepancy, assign ownership, correct it with an audit trail, and rerun consolidation. If currencies differ, have the finance owner provide the rates and expected treatment. Inspect both the group report and the entity-level entries behind it.

Then restrict the operator to one entity. Can that role see or change another entity's books? Can the group controller review the adjustment without receiving administrator privileges?

Key takeaway

A consolidation demo should prove both the final group result and the route back to the underlying entity records. A combined report alone does not demonstrate how mismatches, permissions, and adjustments are controlled.

Do not assume every business needs the same consolidation depth. Simple management reporting and a group with complex ownership structures call for different proof. Use the Sage Intacct and NetSuite comparison to identify the capabilities worth testing for your structure.

ERP demo script 3: a partial shipment comes back

Use this scenario when inventory and fulfillment are part of the replacement scope. A financial-ledger demonstration cannot settle an operational ERP decision.

Create an order for 12 units when only eight are available. Ship the available quantity, retain the backorder, and then return two units. Ask the vendor to show the order status, availability, customer credit, inventory effect, and the connection to the financial records.

Adapt the test to your business. A distributor might add a second warehouse. A manufacturer might add a component shortage. A lot-controlled business should use a specific lot and trace the returned units to their original shipment.

Record where each action happens. If a separate warehouse or commerce application performs it, include that product, connector, reconciliation process, and support owner in your evaluation. This can be a sound design; it still needs to be tested and priced.

ERP demo script 4: an integration fails and recovers

Pick a record type that matters to your close or operations, such as an invoice, payment, or shipment. Ask for a safe demonstration of an interrupted synchronization, followed by a retry.

Look for an alert with enough context to diagnose the failure, a named owner, and a visible resolution. Test a repeated record and a record that arrives out of sequence. Ask how the team detects missing records as well as duplicates.

This is particularly useful when comparing AI-native accounting systems. An integration logo tells you which application is advertised as connected. It does not tell you the direction of synchronization, the supported objects, the treatment of historical data, or how a rejected update is repaired.

Microsoft's implementation testing guidance calls for defined test cases, expected outcomes, ownership, and documented results. Applying that discipline during selection gives the implementation team a useful starting point for later testing.

How to compare the results

Have the process owners record their observations before discussing a preferred vendor. Otherwise, enthusiasm for one part of the demonstration can influence unrelated scores.

Use a rating scale your team can explain. Keep “not demonstrated” distinct from “demonstrated and failed.” A missing answer needs follow-up; a failed critical requirement may change the shortlist.

Weight the criteria around your business priorities, then review the high-impact gaps individually. A strong average should not hide a requirement that the project cannot operate without. The ERP Scorecard methodology explains how our initial fit model works; your live demonstration adds evidence the questionnaire cannot observe.

For every unresolved item, record the next test, its owner, and the date you need the answer. Where a promised capability affects scope or implementation cost, reconcile it with the proposal. The SOW risk scan can help identify missing operational protections, but it does not replace review of the agreement.

ERP demo questions buyers ask

Should every vendor receive the same script?

Yes, for the business outcomes you need to compare. Let vendors show different workflows for achieving those outcomes. Requiring identical clicks can unfairly favor whichever system your team already knows.

Is a successful demo enough to select an ERP?

No. It is one source of evidence. You still need to evaluate delivery capacity, full cost, references relevant to your scope, migration, support, and unresolved requirements.

Can a fit assessment replace the demo?

No. An assessment helps narrow the field and identify requirements to probe. A demo tests the proposed configuration and integrations. Start with the free ERP fit questionnaire, then use the gaps in your report to choose the scenarios that deserve the most time.