On your bank’s public website, you can read opening hours without signing in. To see your balance or make a payment, you use a different part of the service. Both may carry the same logo, but the first screen is not doing the same job as the second.

An invoice provider can have several parts too. We can understand them by following one invoice, rather than starting with a list of technical names. The question at each step is simple: who is asking which program to do what?

A page to read and a service to work in

A program is a set of instructions that tells a computer how to perform a task. The program you use to open websites is a browser. It asks another computer system for information and uses the reply to display a page. The answering system is commonly called a server. It may do more than send fixed text: a program there can look up information and decide what reply to return. 11

For example, an accountant visits an invoice supplier’s public website to read its prices. Anybody may be able to request those pages. The website is presenting the offer; the accountant has not yet asked it to open her company’s invoice records.

She then selects Sign in and supplies the information needed for her account. The working area she reaches is often called a customer portal. A portal is a way for people to use the service through screens and buttons. In our example, it shows the company’s invoices and their delivery states.

When she selects an invoice, the browser asks the service for that document. The service must decide which person is making the request and whether that person may read that invoice. Only then should it send the contents for display. Identifying the user through sign-in is not the same as giving that user permission for every document held by the provider. This distinction matters particularly when many businesses share the service. 3

The public pages and the portal might share computers or programs, or might be operated separately. A portal may even be reached at a different address. You cannot tell the exact arrangement from a matching logo. When a supplier says “we tested the website”, you therefore want to know whether that included the working service after sign-in or only the pages anybody can read.

When your accounting program sends instead of your employee typing

Now suppose the accountant has already entered the invoice in her accounting program. Typing the same customer, items and amounts into the portal would repeat the work. The accounting program can instead be given a way to communicate directly with the supplier’s program.

The programs need an agreement about what requests mean and how replies are returned. For instance, the accounting program might ask the provider to accept a new invoice, then later ask for the progress of that submission. The provider’s program must recognise the request and send a reply the accounting program can understand. It is not a person reading the screen and copying the numbers.

This agreed interface between programs is called an application programming interface, shortened to API. The useful idea is communication between programs. A customer API lets your software ask the service to do work on behalf of your business. You may only see the result, such as a status inside your accounting program, rather than a separate website.

In an example exchange, the accounting program sends the invoice details together with the information identifying the business it acts for. The service checks whether that business may submit the document, performs the allowed work, and replies. When the program later asks about the invoice, the service again has to check access to the requested record. Being connected is not permission to work with another customer’s invoices. 3

The portal and the API are not necessarily two independent systems. A portal can use an API behind its buttons: a person’s click causes the browser’s program to send a request. The difference we are describing is who starts the work and how they interact with it. Exact shared components need to be explained by the supplier.

Suppose the portal stops displaying progress while the accounting program still receives progress replies. In that imagined case, the display problem has not stopped all invoice work. Another failure could affect both because they share a component. Saying simply “the website is down” hides the distinction that would help support understand the problem.

The journey between providers is another connection

Our invoice has reached the sending business’s provider. It still needs to reach the buyer. In Peppol’s basic model, each business connects to its own provider, and the providers exchange the document. There are four roles: sender, sending provider, receiving provider and receiver. This arrangement is called the four-corner model. The word describes the roles, not four computers that every customer must own. 2

Peppol provides common specifications for exchanging documents and finding the delivery destination. Providers following those rules can exchange on behalf of their customers, including customers that selected different providers. This is different from requiring your accountant to learn the buyer’s software or negotiate a new technical connection for every trading partner. 2

The provider’s function for connecting to the Peppol network is called an Access Point. Think of the name as identifying its network delivery role. It is not the same as the public price page, and it is not automatically the connection your accounting program uses to reach your supplier. One connection concerns your business and your supplier; the next concerns delivery between providers. 2

A supplier may operate several of these functions itself or arrange some through partners. One commercial package can therefore contain several technical jobs. One support contact can still be convenient, provided it can follow those jobs when something goes wrong.

In our example, the accountant sees “accepted” after submitting the invoice. Later she sees a delivery update. The supplier needs to explain what each status means in its service. Acceptance by one part of the route does not, by itself, tell her that the buyer has read the document or will pay it.

A notification and a saved copy are different again

The accountant might receive an email saying an invoice’s state has changed. In that arrangement, email notifies her about an event; it is not necessarily the route carrying the invoice itself. A notification saying “received” needs the same explanation as the screen: received by which part of the process? This is a question about the particular package, not a universal meaning of the word.

Storage is another job. The accounting program may retain the company’s copies, or the supplier may offer storage and later retrieval. A working list on screen does not explain how long records remain or what happens when you leave. You need that part of the arrangement made clear if you intend to rely on it.

The different parts also explain why one security claim cannot cover everything by implication. A public-page result does not test whether another customer can read your invoice. A statement about network delivery does not describe every permission in the portal. Those other tasks need their own explanation. This does not mean that each part is bad or that every part must have a different supplier.

Ask for one invented invoice to be followed through the actual package: from preparation, through submission and delivery, to the place where you retrieve your copy. The supplier can show the ordinary workflow without showing anybody else’s records. Testing customer separation is different work, to be agreed with an authorised assessor and invented test data.

You do not need to memorise every name. The practical result is being able to say, “Our program submitted the invoice, this part accepted it, and this is where delivery progress is shown.” That is enough of a map to understand the next explanation when a customer calls about a missing document.

Sources

2 — OpenPeppol interoperability framework

3 — OWASP API1:2023 Broken Object Level Authorization

11 — MDN: How the web works