Agreement handling for Norwegian consumer invoicing

This page is for partners and vendors with Norwegian senders using consumer invoicing (B2CNO) through Maventa.

Maventa is changing how the main vendor agreement is activated. The changes apply to the main vendor agreement only, which covers eFaktura to netbank and Vipps together with the fallback routes email and print. AvtaleGiro (direct debit), its activation and its mandate handling are not affected.

eFaktura invoices are sent to MPS (Mastercard Payment Services) under Maventa’s own agreement. Sending under the service provider’s own agreement with MPS is the direction MPS recommends for handling issuer accounts, and it is how Maventa handles Norwegian senders.

The changes take effect 26.10.2026

The short version: moving a sender to Maventa will no longer take over or replace their existing eFaktura setup, and Visma Sign will no longer be needed for eFaktura. Your invoice payloads do not change, and senders that are already active need no action.

What is changing

eFaktura invoices are sent under Maventa’s agreement with MPS

Rather than each sender holding an individual issuer registration at MPS, Maventa submits eFaktura invoices under a single Maventa agreement with MPS. Each sender’s own organisation number still travels with every invoice as the legal organisation number, so invoices are attributed to the correct sender exactly as before.

Consumers see no difference. The invoice content, the sender name shown in the netbank, and the payment details are unchanged.

What happens to your existing senders

Senders that are already active keep sending without interruption, and there is nothing for you or them to do.

Maventa does not maintain individual registrations for them at MPS, and their invoices are sent under Maventa’s own agreement, exactly as for new senders. None of this is visible in your integration: the sender’s own organisation number continues to identify them on every invoice, and their eFaktura recipients are unaffected.

The only exception is a small number of senders who have their own billing account set with MPS. Those are left untouched and continue to send under their own organisation number.

The takeover process will disappear, and so will Visma Sign for eFaktura

This is the change that matters most for onboarding.

Today, activating the main vendor agreement means transferring a sender’s existing agreement to Maventa. If MPS reports that the sender’s organisation number is already registered by another service provider, a person with signatory rights has to sign through Visma Sign to authorise the takeover, and the old agreement has to be terminated before activation can complete. Every move from another provider has to be planned as a cutover, coordinated between the sender, their previous provider and Maventa.

After the change, none of that applies. Maventa sends under its own agreement with MPS and will not touch a sender’s registration with another provider. Nothing is transferred and nothing is terminated. A sender can be active with Maventa and with their previous provider at the same time, and MPS does not block this.

Visma Sign will no longer be used for eFaktura activation at all. Because there is no takeover, there is nothing left to authorise, so no signature is required from anyone regardless of whether the sender is already registered elsewhere. Visma Sign is still used for AvtaleGiro, where it serves a different purpose, described in The AvtaleGiro agreement and its activation are not changing.

Activation does not wait on MPS

There is no registration at MPS for a sender and nothing to poll. Activation is processed in the background through Maventa’s queue, so it completes within moments rather than hours. It is not synchronous with the API call, but you will not be waiting long enough to need a “pending, please wait” screen. If a sender’s status has not changed to ACTIVE within an hour, contact Maventa support.

Senders are also reachable across all banks straight away. Each bank fetches new agreements from MPS on its own schedule, which is what makes a per-sender registration slow to take effect everywhere. Sending happens under Maventa’s agreement, which is already established with every bank, so there is no per-bank propagation delay for a newly activated sender.

What changes in the API

The way you activate does not change, on either API. What changes is what comes back.

If you use the REST API

You continue to activate the main vendor agreement through the company profiles endpoint with network: "BANK", and the profile subscription remains the record of the sender’s registration.

• The signer name and email in network_settings are not required fields, and will no longer be used for anything. With no signature to send, there is nobody to address it to. Integrations that continue to send these values will keep working, so no change is forced on you.
• GET /v1/services/b2cno returns today what MPS knows about the sender’s organisation number, but after the change it reports the status in Maventa:

RESERVED will be deprecated and will no longer be returned. It exists today to signal that another service provider holds the sender’s registration and that a signature is needed. Since neither the takeover nor the signature remains, the value has nothing left to report. If your integration branches on RESERVED, that branch will become dead code and can be removed.

• Activating a sender that is already active is still rejected with 422, but the error becomes Profile is already registered for given endpoint id instead of Agreement is already active. Only integrations that match on the error itself need updating.
• Deleting the sender’s BANK network profile is how you turn the service off. The consumer invoicing route is removed from the sender and they can no longer send B2C invoices. Nothing is checked at MPS any more, so deletion no longer depends on what MPS reports about the sender.

If you use the SOAP API (v1.1)

Activation continues through b2c_issuer_agreement_order.

• A successful activation returns OK. The response OK: Email sent to <signer_email> will no longer be returned, because no agreement is sent for signing.
• signer_name and signer_email remain in the method signature and are not being removed, so the SOAP contract is unchanged. They are simply no longer used to send anything. You can keep on passing the values you pass today if you need to, or not.
• Re-ordering an agreement for a sender that is already active returns OK.
• disable_b2c_issuer_agreement is how you will turn the service off. It will return OK, the consumer invoicing route is removed from the sender, and they can no longer send B2C invoices. It no longer checks anything at MPS, so ERROR: Cannot disable agreement. Issuer state is ... will no longer be returned. The method name does not change, even though what it switches off is now the service rather than an agreement.

The AvtaleGiro agreement and its activation are not changing

One part of the change does reach AvtaleGiro invoices, because they travel through the same eFaktura channel. Both are covered below.

What stays the same:

• AvtaleGiro requires a direct debit agreement between the sender and their bank, tied to the bank account number the agreement is registered on. It is arranged manually with the bank, using customer ID 229221 to identify Visma, and it sits outside Maventa.
• If a sender’s mandates are currently held by another service provider, a person with signatory rights still authorises a takeover through Visma Sign. This is a different thing from the eFaktura takeover being removed. It exists so that Maventa can retrieve the sender’s existing direct debit mandates through the ATG mandate API. It does not transfer the direct debit agreement, which stays between the sender and their bank.
• Direct debit mandates continue to be fetched by Visma only.
• Activating AvtaleGiro in Maventa does not stop a sender’s existing deduction file route. The invoice notification can go through Maventa while the deduction file goes through the previous provider. This has always been true for AvtaleGiro, and eFaktura now behaves the same way, so the two channels no longer differ on this point.

What changes:

• AvtaleGiro invoices are sent through the same eFaktura channel, so they are also submitted under Maventa’s agreement with MPS, exactly as described earlier on this page. Nothing changes in your payloads, and the sender’s own organisation number still identifies them on every invoice.

What you need to do

Very little, but one thing to check before 26.10.2026, and some cleanup you can do whenever it suits you.

Before 26.10.2026

Whenever it suits you

• On REST, if your integration matches on the Agreement is already active error when activating, update it. That error will no longer be returned, and activating an already-active sender will be rejected with Profile is already registered for given endpoint id instead.
• If your integration handles ERROR: Cannot disable agreement. Issuer state is ... on SOAP, or a failed profile deletion on REST, those will no longer occur. Turning the service off now always succeeds unless the service is not enabled in the first place.
• If your integration branches on the RESERVED status, or handles the agreement signing flow for eFaktura, that code can be retired after the change goes live.
• If your onboarding process treats a move from another provider as a cutover, for example by asking senders to close their old agreement first or by collecting a signatory for Visma Sign, you can simplify it. Neither step will be required for eFaktura.
• If your integration shows a “pending, please wait” state during activation, you can remove it.
• No changes are needed to invoice payloads, and no senders need to be re-activated.

Timeline

Questions

For questions about your integration, contact Maventa support.

The activation process is also documented in context in Consumer Invoicing (Norway), with the API methods in the B2CNO API and the B2C Norway SOAP methods.