Put two supplier offers side by side. One includes a portal, another emphasizes the connection to your accounting software. Both say “secure electronic invoicing.” Are they offering the same thing?
Before comparing the price or the security badges, describe the work you need the service to do. Choosing a digital postman is not just choosing who carries a document. It may also mean choosing the screen your staff use, the people who resolve problems and the place where records are kept. Those functions need not all be included in the same offer.
A useful way to read an offer is to turn each noun back into an action. A portal is the website where staff sign in and do work. An accounting connection lets one program send information to another without a person copying every field by hand. Transport carries the document between agreed points. Retention keeps records for later use. Support helps resolve a problem. These functions interact, but paying for one does not tell you that all the others are included.
For this lesson, follow a wholesaler’s day from preparing a document to knowing what happened to it. At the start, it owns the source data and approves the invoice in its accounting program. At the end, its employee needs an understandable result and a next action if something failed. Between those points lie the functions to compare. A supplier’s description becomes easier to question once you can place its promised function in this journey.
Begin with an ordinary working day
For example, a small wholesaler prepares invoices in an existing accounting program. Its staff want to send approved documents, see whether they were processed and resolve rejections. The accounting program may remain the main source of its invoice records. This gives the suppliers a concrete description of the work to price.
Another company may need the provider to supply document storage and a portal for several offices. Even if both companies send similar invoices, they are not necessarily buying the same service. Write your own needs in a short paragraph before asking suppliers to price them.
Then follow the document. What remains in your software? What does the provider receive? Where will staff see the result? Which tasks remain yours, such as creating users or correcting rejected invoices? This is enough to start a useful conversation without knowing how every computer on the supplier’s side works.
Peppol provides rules and technical arrangements for exchanging documents through service providers. That is an important part of the route, but it does not describe every feature around it. Ask who supplies the actual Peppol connection and which company is responsible to you for the portal, integration and support in the offer. 6
Decide what must work before admiring the extras
Separate necessities from conveniences. A useful starting list might include understandable document states, appropriate staff access, support when work gets stuck and a way to recover or hand over the functions you buy. Your own workflow determines the list; these are suggested purchasing criteria, not a universal legal checklist.
An extra dashboard may save time. A polished interface may be easier to learn. Neither solves the problem if nobody can explain what happens to an uncertain invoice submission. Conversely, a minor issue on a public brochure page need not outweigh a clear and well-supported explanation of the purchased service.
Treat a public website as a shop window. Its condition can prompt a question about maintenance, but you cannot inspect the whole business through it. The idea that repeated public defects might reflect wider management habits is a hypothesis to investigate, not proof about the security of customers’ accounts.
Spend the most attention where dependence is greatest. NIST (the US National Institute of Standards and Technology)‘s supplier-risk guide recommends considering how important the service is, the sensitivity of information and the access the supplier has. If losing this service stops your invoicing, recovery and support deserve more attention than a feature you rarely use. 8
Consider why access matters in the wholesaler’s day. One employee prepares invoices, another approves them, and an outside accountant may need only agreed records. A convenient shared password would not explain which person should do which task. A useful supplier answer describes the permissions that fit these jobs and how they are changed when somebody leaves. You are asking how the bought service fits your work, not demanding that every firm use the same staffing pattern. This follows NIST’s emphasis on the importance, information and access involved in the supplier relationship. 8
The same reasoning applies to support and recovery. If an interruption would stop the wholesaler from sending invoices, a clearly usable support route is essential. If all invoice records are retained in its own accounting system and the provider only carries messages, demanding a provider archive can distract from the real question: how unfinished transmissions are resolved. The best comparison is not the longest list. It is a clear account of the necessary jobs and the person or service responsible for each.
Ask to see one complete piece of work
A useful comparison is to give shortlisted suppliers the same simple scenario. Ask them to explain a normal submission, an understandable rejection and a support case. Where record retention is included, also ask how recovered records are checked. You are comparing the ability to do your work, not how many technical terms the presenter can name.
Any demonstration should take place in a separate test environment, be authorized by the supplier, use made-up invoices and temporary test accounts, and have agreed actions, small volumes and stopping conditions. Keep it out of live customer records and production disruptions, and exclude real chargeable onward messages. A buying decision does not require experimenting on someone else’s account.
Afterwards, distinguish what you saw from what you were told. A demonstration shows particular examples. A policy explains intended practice. An independent review has a defined subject and period. Ask for the form of explanation that fits the question rather than collecting documents for their own sake.
Do not turn these different kinds of support into an invented percentage of safety. If an essential question remains unanswered, name it. NIST’s Cybersecurity Framework is based on outcomes rather than one prescribed implementation; that is a useful model for asking whether the necessary work can be done and maintained. 2
Compare the relationship as well as the price
Ask suppliers to price the same required functions, including setup, the accounting connection, needed support, any retention and help with leaving. A base tariff is not a full comparison if one offer leaves important work to your staff. Use written offers and explicit assumptions rather than guesses presented as measured costs.
Imagine the same rejection in two offers. In one, an employee reads the reason, corrects the source document and follows the documented resubmission procedure. In the other, the employee must contact paid support to learn the next step. Either arrangement might suit a customer, but the base prices do not describe the same amount of help or staff effort. Have each supplier explain and price the arrangement it actually offers. This illustrates why comparable work comes before a price ranking.
Do the same for leaving. An export is a transfer of records out of the service, usually into files you can take away. A collection of files is useful only if the next person or program understands what they contain. For the wholesaler, losing the processing history may leave uncertainty about documents even when the source invoices are still present. Agree what information is needed, how a made-up sample will be checked and what transition help costs. NIST includes planning beyond the end of the service agreement; it does not create a universal export entitlement for every product. 2
Keep separate questions separate. A requirement to enter a commercial relationship does not, by itself, tell you whether a base tariff is charged. A free service does not tell you what optional work costs. Public or private ownership also does not answer whether the actual service meets your needs. Compare equivalent responsibilities and functions.
Discuss the end of the relationship before signing. What can you take away, can you understand and reuse it, and who coordinates the change? NIST includes planning for activities after a supplier agreement ends, as well as checking recovery outcomes. A proposed export or recovery arrangement still needs to match the service you actually purchase. 2
Agree how important problems will be communicated after you join. Who receives your concern, who follows it through and what remains your team’s job? Treat privacy, accessibility, security and commercial fit as related but separate questions; a scanner’s label cannot settle a legal assessment.
Finally, explain the choice to a colleague without using the supplier’s score or slogans. “This service fits our existing software, showed us how rejections are resolved, and has an agreed handover route; this remaining limitation is acceptable because…” is a decision another person can understand. You are not promising that nothing will ever fail. You are choosing an arrangement you know how to use when ordinary work—and the occasional difficult day—arrives.