A supplier presentation shows an invoice leaving the accounting program and appearing in the customer portal. The screen looks clear and the process is quick. What should you ask next?
Ask what happens when the invoice cannot be processed. A normal submission shows one useful part of the service. A rejected or interrupted submission helps you understand the part your staff will need when something does not go as expected.
A click is the beginning of a conversation between programs, not a description of everything they accomplish. In a simple demonstration, your accounting program sends the approved document to the supplier’s receiving program. The supplier answers. That answer may concern its own acceptance of the submission. Further work can then carry the document onward. The screen shows what the product has chosen to display about that work; it is worth asking which event produced each displayed message.
Keep the same invented invoice in view so these steps do not become disconnected promises. The presenter can identify it in the sending program, show the corresponding supplier record and explain what happened next. You do not need to inspect real customer records to learn the route. The point is to connect your action, the receiving service’s action and the information your staff will rely on. For Peppol, OpenPeppol describes distinct sending and receiving participants and their service providers; that network journey is not identical to the customer’s first click. 6
Follow one document, not a list of features
Use a made-up invoice as the thread through the presentation. Begin where your employee approves it. Follow the software connection that sends it, the service that carries it onward and the place where you later see its status. You are not asking for a tour of every technical component. You are learning where your work goes and who helps at each step.
The distinction matters when several businesses supply the service. In Peppol, electronic documents travel through service providers and the network uses separate components to find recipients. The company selling you a portal may not operate every part of that arrangement. Ask which company provides the connection and who handles your support case if the problem crosses that boundary. 6
Think of buying a delivery service. Seeing the booking screen is useful, but you also want to know what happens if a parcel cannot be delivered. The same question belongs in an invoice demonstration: what does the customer see, and what should the customer do?
Let the example fail safely
Propose an agreed demonstration in a separate test environment, often called a sandbox. Use made-up invoices and temporary test accounts. The supplier should authorize the actions in advance, keep the volume small and agree when to stop. Exclude real customer records, live credentials, production interruptions and chargeable onward transactions. These are recommendations for a safe purchasing exercise, not a requirement to test a supplier yourself.
For example, ask the presenter to show a document that is deliberately unsuitable for the agreed test case. Does the service explain why it was rejected? Can your employee tell whether to correct it, wait or contact support? Then ask the presenter to show what happens when the outcome of a submission is uncertain and the employee is considering sending it again.
Suppose the agreed test document lacks information the demonstrated service requires. The supplier shows where it is rejected and where the reason appears. Follow the correction as well: does your employee change the source document, use a permitted editing function or ask somebody else to approve a replacement? The supplier should explain its actual workflow. It is not enough to display “invalid” if your staff cannot tell which step to take next. This missing-information case is an illustrative buying exercise, not an assertion of a particular Peppol validation rule.
Now contrast rejection with silence. In the second demonstration, imagine that the answer does not reach the sending program. Rejection tells you something the service decided; silence only tells you the expected answer was not received. The service may already have begun work. Have the presenter explain how the test record is located and how a repeat is handled under that product’s documented procedure. The lesson is not “always resend” or “never resend.” It is to find the original operation’s result before choosing the next operation.
The important part is the explanation of the product’s actual status labels. “Received” may describe one stage of processing, not the end of the whole journey. Ask the supplier to connect each relevant label to the event it records. Do not assume that every provider uses the same words in the same way.
Bring support into the example. Show how an ordinary customer opens the case without attaching a real invoice unnecessarily. Ask who takes over if the accounting connection and the transport service disagree. This reveals a practical difference between “support is included” and knowing how to get an unresolved document moving again.
A screen, a policy and a review answer different questions
A demonstration shows selected behaviour under particular conditions. A written policy describes how the supplier intends to work. An independent assessment examines a stated subject over its own scope and period. These can complement each other, but one does not replace all the others.
For instance, an account demonstration might show that an ordinary user cannot perform an administrator’s action. Have the supplier check what happened to the test record as well as what appeared on screen. A refusal message is less useful if nobody verifies whether work was nevertheless performed behind it. One successful example still does not establish that every route through the application behaves correctly.
Similarly, an audit summary is most useful when you can identify the company, service and period it covers. A supplier may reasonably protect confidential details. A redacted summary or a structured explanation can sometimes answer your question without exposing another customer’s information.
Put the most effort into the functions you depend on. NIST (the US National Institute of Standards and Technology)‘s supplier-risk guide recommends asking how important the supplier is to your work, what sensitive information is involved and what the supplier can access. Use those answers to decide what the agreement needs to cover. A small public-page defect and a failure that prevents all invoicing should not consume equal attention merely because each occupies one questionnaire row. 8
“We have backups” needs a second sentence
If the supplier stores records for you, ask how it establishes that a recovered record is usable. If it only carries documents onward, ask about restoring that function and resolving unfinished submissions. Do not demand an archive demonstration from a company that does not sell an archive.
A backup is a separately kept copy intended to help recover information if the working copy is lost or damaged. Restoring means putting the needed information and functions back into usable operation. For example, if you buy document storage, a recovered invoice file needs to open and correspond to the right record and attachments. A system that shows the file name but cannot retrieve its contents has not demonstrated that outcome. This is a practical application of checking restored material, not a claim that a particular supplier has lost documents. 2
The same distinction helps you listen to a recovery presentation. A slide describing an intended recovery time is a plan. A written commitment says what has been agreed. An exercise report tells you what happened in a particular rehearsal and what still failed. A supplier can explain these without exposing confidential customer data. Read them together to understand what your own team would do during the interruption, rather than trying to turn one number into certainty.
NIST’s Cybersecurity Framework includes checking the integrity of backup material before restoration and verifying restored systems before confirming normal operation. The business lesson is that having a backup and having a working recovered service are separate achievements. 2
Ask the supplier to distinguish its recovery target, its contractual promise and what happened in an actual exercise. A target says what it aims to achieve; an exercise describes a particular attempt. Neither should silently be presented as a guarantee for every incident.
End the meeting with the answer to one ordinary question: “If our employee gets stuck here, what happens next?” Note what was demonstrated, what was only explained and what still needs an answer. That gives your staff something more useful than a list of reassuring feature names.