The shipment with a rate change halfway through the month. The invoice that arrived without the required proof of delivery. The load that had to be tendered again after the first transportation provider declined.

If you are evaluating a freight audit and payment provider or a transportation management system for 2027, bring those transactions to the demonstration. Ask each prospective provider to work through them, using the records and requirements your team had to manage.

A feature checklist establishes what is available. A transaction walkthrough lets you examine how those capabilities operate together, where someone must intervene, and how the next person knows what to do.

Set up the demonstration around your requirements

Select examples that represent recurring work or meaningful business exposure. Prepare a small, anonymized package for each one, including the relevant contract terms, shipment details, invoice, supporting documents, and customer business rules. State what your team needs to accomplish without prescribing every screen or step.

Use the same requirements for every prospective provider and give each comparable preparation time. Identify which services are in scope. For a TMS-only selection, the provider may need to show how information reaches your audit system. For freight audit and payment, it may need to show how shipment details arrive from your existing TMS.

The scenarios below are illustrative. Replace their details with your own transactions and configured requirements. Record what the provider demonstrates, what requires configuration or integration, and what remains a proposed capability.

Scenario one: A rate changes midway through the month

A revised agreement takes effect on January 15. One shipment is picked up on January 14 and delivered on January 16. Another is picked up on January 15. Both invoices arrive in February. Your agreement specifies that the pickup date determines the applicable base rate.

Ask the provider to show how it maintains both contract versions, records the effective date, and selects the applicable terms for each shipment. Include a related fuel or accessorial provision if that is part of your actual agreement.

Then introduce an invoice that uses the wrong version. Follow the discrepancy through review, correction, and approval. Ask who can change the rate record, who approves that change, and how the original calculation and subsequent action remain traceable.

For a TMS demonstration, examine shipment rating and the information passed to audit. For freight audit and payment, examine invoice validation and the handling of the discrepancy. Confirm where responsibility sits if the two functions use different systems.

Scenario two: An invoice arrives without required proof of delivery

An invoice contains the expected shipment reference and agreed charges, but your configured payment-approval requirement calls for proof of delivery. The attachment is missing. Later, a document arrives bearing a different shipment reference.

Ask the provider to show how it recognizes the missing requirement, assigns the exception, and requests the correct document. Establish what happens to the invoice and payment status while the information is outstanding, according to your rules.

Next, ask it to process the mismatched document. Can the process check that the document relates to this shipment and satisfies the configured requirement? Where does automated processing end and human review begin? Who contacts the transportation provider, and who can approve an authorized exception?

Finally, provide the correct document. Follow the transaction back into processing. Check whether duplicate submissions create extra work and whether an internal user can see what was missing, what arrived, and why the invoice is now eligible to proceed.

Document handling deserves specific questions when AI is part of the proposal. Ask the provider to demonstrate the checks, the evidence retained, and the treatment of uncertain results. Capture, document verification, and approval each perform a different job within the workflow.

Scenario three: A shipment has to be tendered again

A shipment is rated and tendered under the routing guide. The first transportation provider declines. A second accepts at a higher agreed rate, and your rules require approval before proceeding. The invoice later arrives with an additional charge.

In the TMS, ask the provider to show the original tender, the decline, the available alternatives, and the approval for the replacement option. Can the planner see what changed and record why? If approval is delayed, who receives the next notification and how does the planner know the current status?

Then follow the accepted rate and shipment details into audit. Ask how the invoice is checked against the authorized replacement arrangement and how the additional charge is evaluated against the applicable terms and documentation.

The first quoted rate may remain useful for understanding the variance. The authorized replacement rate establishes a different expectation for invoice review. Ask how the process preserves both without treating every increase as a billing error.

If a separate system or service owns part of the process, ask to see the handoff and how a failed or delayed transfer is detected. Name the party responsible for investigating it.

Score the work your team would still have to do

After each walkthrough, record the exception trigger, the assigned owner, the next action, and the evidence required to resolve it. Include what your internal team must do, what the provider’s service team handles, and what depends on a transportation provider or another system.

Look at the user experience as well. Can a reviewer find the relevant contract, document, approval, and current status from the transaction? Must someone rekey information or assemble a spreadsheet? Can users tell whether an issue is awaiting information, approval, or a technical correction?

Keep the evaluation consistent across providers. Distinguish capabilities demonstrated during the session from those dependent on additional configuration, paid services, integrations, or future development. Include that work in the implementation scope and commercial comparison.

For requirements that matter most, carry the scenarios into acceptance testing. Agree on expected outcomes, responsibilities, and the evidence that will establish whether the configured solution meets your needs.

Evaluate how the information stays connected

These three scenarios cross the boundaries between procurement, transportation execution, document handling, freight audit, and payment approval. Evaluating each function separately can leave those handoffs unexplored.

At nVision Global, IMPACT TMS and freight audit and payment use a shared rate engine to support shipment rating and invoice audit. Customer-specific business rules and supporting-document requirements help govern how transactions are reviewed and moved through the process.

One Vision™ is nVision’s strategy for bringing fragmented transportation information together, validating and verifying it, and applying customer audit, documentation, and business-rule requirements. That information foundation supports transportation financial intelligence and investigation of the financial outcome of a shipment.

Apply the same transaction tests when evaluating nVision. Ask us to show the relevant capabilities, the configured requirements, and the responsibilities across the proposed scope. Trace the records through the exception and examine how the result can be explained.

Leave the demo with a transaction you can follow

For your 2027 RFP, ask the people who plan shipments, review invoices, and resolve payment questions to nominate one transaction that repeatedly causes trouble. Have them attend the walkthrough and assess the work they would perform in the proposed process.

By the end, you should be able to follow the exception from its first signal through its resolution, identify who owns each step, and see the record of what happened. Use any gaps to sharpen the requirements before you commit.