ReAI and Nexbal
ReAI focuses on accounting and business operations. Nexbal focuses on the electronic invoicing infrastructure that software teams need.
ReAI is a Nexbal partner. The relationship connects two different needs: a business needs to work with invoices in its accounting system, while a software platform needs infrastructure for exchanging electronic documents.
Keeping those roles clear helps you choose the right starting point. Most businesses looking for an accounting system do not need to design a Peppol integration themselves.
Which conversation should you start?
| Your need | Relevant starting point |
|---|---|
| Accounting software for a Norwegian business | ReAI |
| A broader workflow covering invoicing, online sales, point of sale and stock | ReAI |
| Peppol sending or receiving inside your own software product | Nexbal |
| Planning participant onboarding, validation and document statuses | Nexbal |
| Moving an existing electronic invoicing integration to another provider | Nexbal |
The exact services, document flows and responsibilities should be agreed for your project. A partnership is not a claim that every product supports every country or document type.
If you are choosing business software
ReAI’s invoicing and accounting system is a starting point for Norwegian businesses that need to issue invoices and manage the accounts. Describe the documents you send, your customers’ reference requirements and how you follow unpaid invoices.
Ask how an ordinary invoice, a credit note and an electronic rejection are handled in the application. The decision is about the business workflow, not just the way a document is transported. A Norwegian company using accounting software and a software vendor building invoicing for its own customers have different starting points.
If you are building a software platform
Nexbal is the relevant conversation when your product needs Peppol infrastructure. Prepare a short description of your users, sender and receiver roles, intended documents and launch markets.
Before implementation, agree where each responsibility sits:
- Your product captures the business data and communicates with its users.
- The integration needs a clear contract for validation, submission and status updates.
- Support needs references that connect the original document to its processing history.
- Accounting outcomes must not be inferred from transport status alone.
Use the SaaS onboarding checklist and pre-production test matrix to structure that discussion.
Discuss fit before committing to a rollout
Contact Nexbal with your current setup and the first flow you want to support. Describe whether you are choosing software for your own business or adding invoicing to a product, so the conversation starts with the right requirement.
See if Nexbal can lower your Peppol cost
Share your current setup, provider, or first document flow and Nexbal can tell you whether there is a cheaper, simpler way forward.