You finish an invoice, press Send and return to your work. A moment later, the screen says it was sent. What has actually happened? Has your customer received it? Is a copy still available? Who could open that copy?

These are ordinary business questions, but the single button hides several different jobs. Understanding those jobs is the beginning of trusting a provider. You do not need to learn how to build a computer system. You need a picture of what the service does with the information you give it.

An invoice becomes information another program can use

An invoice on paper has a customer name, items, amounts and payment information. In a computer, those details are saved as information that programs can read. A program is a set of instructions a computer follows: your accounting program uses those instructions to organise the details, calculate amounts and show you an invoice. What you see on the screen is a presentation of the information, not the only form in which it can exist.

For example, an accountant prepares an invoice for replacement parts. She checks the customer and amount, then selects Send. Her program can pass the invoice information to a program operated by a delivery provider. That receiving program can reply that it accepted the submission. The accountant may never see the provider’s computer, but the exchange still happens. Computers operated to answer other computers’ requests are commonly called servers. Your computer does not have to hold the whole service for you to use it. 11

Here we have deliberately described an example, not every possible package. Some businesses prepare invoices on a provider’s website instead of using their own accounting program. Some services carry documents but do not keep the long-term copies the business needs. Others offer several jobs together. One screen can make these arrangements look identical until you need an old document or help with a failed delivery.

An invoice contains more than an amount. It can reveal a trading relationship, a price agreed with one customer and what that customer bought. Trust therefore concerns what the provider does with that information, as well as whether the Send button works.

Acceptance by your provider is one step of the journey

Imagine the accountant’s program receives the reply “accepted”. In this example, that means the provider has accepted the submission for processing. It does not automatically mean the buyer’s accountant has opened it. A displayed status is useful only when you know which event it describes. The provider should explain its own wording rather than expecting you to guess.

For electronic exchange through Peppol, the sending business works with a service provider, while the receiving business works with its own provider. The two providers exchange the document using shared rules. This makes it possible to trade with a business that chose a different provider, rather than requiring every pair of businesses to arrange a separate technical connection. Peppol is the name of that framework and network, not the name of one company that stores everyone’s invoices. 2

Follow our invoice: the accountant prepares it; her provider receives it; the receiving provider takes it onward to the customer. Those are distinct steps even if the accountant experiences them as one click. A supplier may perform several of them or use partners. You can still have one support contact, but that contact needs to help explain where the document has reached.

Suppose the customer calls to say the invoice is missing. Repeatedly clicking Send is not a substitute for understanding the status. First you want the service to show what happened to the original submission. A demonstration with an invented invoice can make the difference between “received by our service” and “delivered onward” understandable before you depend on it in daily work.

Keeping a copy and deciding who may read it

Delivery and storage are separate jobs. A parcel carrier can deliver a box without becoming your warehouse. Likewise, moving an invoice does not, by itself, promise that you can open your copy years later. Your accounting program may keep that copy, or the purchased package may include storage and retrieval. Neither arrangement is automatically better; the important point is knowing which you have.

Return to the replacement-parts invoice. Several months later, the customer asks why an item cost that amount. The business now needs the contents of the old invoice, not just a green mark saying something was sent. A useful storage arrangement lets the right employee find the relevant document. If you change providers, you also need to know how to take the records you rely on with you and use them afterwards. These are matters to agree for the actual service, not features to infer from the word “digital”.

Next consider two businesses using the same provider. Both may sign in successfully, but that does not make their documents shared property. Signing in identifies the person using the account. When that person asks to open an invoice, the service separately needs to decide whether that person may access that particular document. It must make the decision before sending the contents. 3

Even within your own business, different people may need different rights. The accountant might prepare invoices; another colleague might only read them; the owner might approve sensitive changes. These are examples of work arrangements, not a universal rule about job titles. The service’s permissions should support the arrangement you actually need. Merely hiding a button on a screen is not a substitute for the service checking whether the requested action is allowed. 3

Availability is another part of the promise. A document may remain private but be temporarily unreachable. If the service that holds your working copies stops responding, you need a way to continue or get help. Where your own program holds the copies, that question belongs partly to your own setup. Ask each supplier about the functions it actually provides, not about an archive it never offered.

Make the promise visible in an ordinary demonstration

A security badge can be useful, but it is not a description of all these jobs. A report about a public homepage may examine a very different part of the provider’s work from the service used after sign-in. Good reporting explains what was examined, when, and what could not be checked. These are recommendations for making results understandable, not a guarantee that every possible weakness has been found. 8

A helpful supplier explanation might be: “Your program keeps the invoice copy. We deliver it through this partner. This screen shows when we accepted it and when the next delivery step completed. If it stops here, contact our support.” Another package might include storage and show how an authorised employee retrieves an old document. The explanation differs because the purchased service differs.

For a buying demonstration, ask the supplier to follow one invented invoice from preparation to receipt and then reopen its copy. Include the accountant’s ordinary work, not just the fastest route through a polished presentation. You are asking to understand the product, not asking for access to another customer’s records.

Before agreeing to the service, settle where your usable copies will remain and who will help if delivery stops. Trust becomes more meaningful when “we take care of your invoices” has been translated into those concrete jobs.

Sources

2 — OpenPeppol interoperability framework

3 — OWASP API1:2023 Broken Object Level Authorization

8 — OWASP WSTG v4.2 Reporting

11 — MDN: How the web works