KvK Trade Register
Retrieves company details using the Chamber of Commerce (KvK) number as soon as a new contact is created.
We use cookies to make the site work and, with your consent, for analytics and marketing. You can change your choice at any time at the bottom of the page.Cookie statement
NEXERA CoreIntegrations
The core's own modules need no integration between them: orders, stock, documents and accounting share one data model. For what lies outside, such as the bank, the Chamber of Commerce (KvK) and the Dutch Tax Administration, there are integrations. Here you can see, for each integration, what is live, what is coming and what we build per customer.
We only mark something as "live" once it runs at a customer. Until then, this page states honestly where it stands.
Retrieves company details using the Chamber of Commerce (KvK) number as soon as a new contact is created.
VAT numbers of EU customers are checked before reverse charge is allowed on an invoice, and again every Monday.
Imports statements in the XML format that Dutch banks supply, then matches them against invoices and payments.
An approved payment run becomes a payment file for the bank. Recorded before it leaves the building.
The audit file for the accountant and the Dutch Tax Administration, per legal entity and per period, and always reproducible.
Electronic purchase invoices in UBL are imported, with supplier, amounts and VAT.
Invoices and documents sent to your own inbox address arrive in the document inbox. If processing fails, Finance is notified.
Quotations, confirmations, invoices and payment reminders are sent from NEXERA Core, in the contact's language, and appear on the timeline.
Lists and reports to a spreadsheet, written as text so that a cell never runs a formula.
Statements arrive automatically every morning through a PSD2 aggregator, instead of uploading a file. Built; switched on once the agreement with the aggregator is in place.
Purchase invoices are recognised, matched with order and receipt, and approved in Cobox by Effect. NEXERA Core posts and pays.
An agent monitors the integrations, explains what is going wrong and prepares the fix.
Sales invoices as e-invoices under EN 16931, through a certified Peppol access point.
The consignment note signed digitally through a certified eFTI platform, using the data from the shipment.
Exchanging the accounts with DATEV, for the German tax adviser (Steuerberater) of companies with accounts in Germany.
Approve, scan invoices and read the morning briefing, on iOS and Android.
Sales and stock movements per store, posted daily to the right cost centre.
Orders in, stock and prices back. For example Shopify, WooCommerce or Lightspeed.
Weighed weight on the delivery note and invoice, labels with batch and best-before date.
Orders, delivery notes and invoices in the buyer's format.
Transport requests, shipment status and documents back and forth.
Completion reports and consumption from the line, fed back into the production order.
How we integrate
Every integration runs in the test environment first, with a separate key for each environment and signed messages.
If something goes wrong, the integration reports it. Failing silently, so that an error only comes to light at the month-end close, is exactly what we want to prevent.
Integrations with external services use signed messages and a separate key for development, test and production.
SecurityA new integration runs in the test environment on real examples, and only goes to production once it is approved.
ImplementationA failed transmission or import reaches the right role as a notification, and is recorded in the audit trail.
Audit trailNo. Contacts, items, orders, stock, logistics and accounting share one data model. An order and its invoice are the same record, not two systems updating each other.
Yes, as customisation on the core. We build the integration in your test environment, check it against real examples and then take it live.
The same team that built it. Integrations are monitored; an error comes in as a notification instead of failing silently.
Yes. The core has an API, with a separate key for each environment. We build integrations on it. If your own IT team wants to connect to it, we agree with each customer which functions will be made available.
Only if you switch them on. Questions to LIV on screen go to Claude from Anthropic by default, through a European cloud region. On the phone, LIV runs on Core Voice, with Grok Voice from xAI; that speech is processed in real time in the US. The Security page shows where each type of data is processed.
NEXERA Core
Bring your list of systems to the demo. We show what the core absorbs, what we integrate and what that means for the first phase.