LIMS + ERP: The Strategic Integration with SAP or Business Central (Navision) to Automate Laboratory Invoicing

1. The problem: two systems, one client, and an invoice that takes two weeks to go out

Thursday, 5:40 PM. The analyst validates the last parameter of a PFAS package, signs off the certificate in the LIMS, and sends it to the client. The technical work is done. The invoice is not.

Two weeks later, someone in administration opens the LIMS in one tab and SAP —or Navision— in another, and starts copying: customer code, order reference, parameters tested, whether there was a rush turnaround, whether part of the package was subcontracted to another lab. A slip in the tax rate, a customer code that doesn’t match exactly between the two systems, a rush surcharge that gets forgotten, and the invoice goes out wrong or, worse, doesn’t go out at all.

This isn’t a problem of careless people. It’s the logical consequence of running two systems of record —one technical, one financial— that don’t talk to each other. The bigger the lab grows, the more expensive that silence becomes.

2. What integrating a LIMS with an ERP means (and what it doesn’t)

Direct answer: integrating the LIMS with the ERP means that when a billable event happens in the lab —a validated test, a signed certificate, a milestone in a recurring sampling contract— that information travels automatically to the ERP as an order or invoice line, without anyone re-entering it.

It doesn’t mean merging the two systems, or having the LIMS take over accounting. The LIMS remains the system of record for the technical side: chain of custody, methods, uncertainty, reports. The ERP remains the system of record for the financial side: tax handling, payment terms, posting, treasury. The integration is the bridge between the two, not a replacement for either.

What exactly counts as a “billable event”?

In a lab, it isn’t always “one sample.” It can be an individual parameter, a complete analytical package, a consolidated report covering several samples from the same monitoring point, or a milestone within a framework contract for recurring sampling with a public authority. Designing the integration starts by defining, for each client type and contract type, which event triggers the invoice — not by picking the connection technology.

3. How a LIMS connects to SAP: OData, BAPI, IDoc, and the role of Integration Suite

A lab’s “SAP” can actually be one of three different products, and each integrates differently. SAP Business One, aimed at small and mid-sized companies, exposes its Service Layer, a REST API sitting directly on the application server. SAP S/4HANA —the current strategic version, cloud or on-premise— publishes OData v2 (on-premise) and v4 (cloud) services over business objects such as the sales order or the billing document, designed for CRUD operations (create, read, update, delete) over HTTP. Older installations running on SAP ECC (SAP R/3) rely on BAPIs and RFC (synchronous calls into SAP’s own functions) and on IDocs, a format originally built for EDI that’s still common in long-established integrations.

When the scenario gets complex —multiple entities, retry logic, format transformation, error monitoring— an intermediate layer is usually introduced, typically SAP Integration Suite (the evolution of SAP Cloud Platform Integration and the older PI/PO), which acts as translator and buffer between the LIMS and the SAP core. The LIMS doesn’t need to “speak SAP”: it needs to speak to the middleware, and the middleware handles the rest.

4. How a LIMS connects to Microsoft Dynamics 365 Business Central (formerly Navision)

Many labs still call their ERP “Navision” even though, technically, it’s been something else for years. Navision was rebranded Microsoft Dynamics NAV in 2005, and since 2018 its cloud evolution has been sold as Microsoft Dynamics 365 Business Central. The name changed; much of the underlying business logic didn’t.

Business Central resolves the integration more directly than SAP: it exposes a native REST/OData v4 API, with roughly 44 ready-to-use standard endpoints —customers, items, sales orders, sales invoices, among others— authenticated through Microsoft Entra ID (formerly Azure Active Directory). For the case this article focuses on, the relevant endpoint is sales invoices: the LIMS can send, via an HTTP call with the right token, a customer and a set of detail lines, and Business Central creates the corresponding sales document, ready for accounting and tax processing. Legacy on-premise installations of classic Dynamics NAV also expose OData and SOAP services, though with more security limitations and less API coverage than the cloud version.

5. From validated result to invoice: the automated flow, step by step

Regardless of whether the target ERP is SAP or Business Central, the conceptual flow is the same. Only the technology carrying it changes:

Step	What happens
1. Customer creation or sync	The customer code matches, character for character, in the LIMS and in the ERP.
2. Order registration	The contracted analytical package and applicable rate (standard, framework contract, or special) are linked.
3. Execution and technical validation	Tests are completed and validated according to the lab’s management system.
4. Certificate signature	The results report is signed and closed out in the LIMS.
5. Billable event generation	The LIMS builds the detail lines: parameter, matrix, urgency, subcontracting.
6. ERP API call	OData/REST creates the sales document or invoice in SAP or Business Central.
7. Commercial terms applied	The ERP resolves tax, withholding, payment method, and payment terms.
8. Issuance via the required channel	The applicable public-sector e-invoicing portal if the client is a government body; a format compatible with the relevant real-time verification system where one applies.
9. Reconciliation	Payment status is visible from both the LIMS and the ERP.

6. Why a lab’s invoicing isn’t a generic invoice

This is where most integration projects get stuck — not on the API call, but on the catalog. A generic ERP works natively with “items” and fixed price lists. A water-testing lab invoices in a far more granular way:

Analytical granularity: By individual parameter or by complete analytical package, with different prices depending on the volume contracted.

Rush turnarounds: When the client requests a shortened turnaround time and the lab applies a specific surcharge.

Subcontracting: Tests referred out to another accredited laboratory —for example, a PFAS parameter outside the lab’s own accreditation scope— that needs to be passed through with its corresponding margin.

Framework contracts with public authorities: Unit prices agreed in the tender, aggregated periodic invoicing, sometimes by sampling batch rather than by individual sample.

Credit notes and refunds: When a result is voided due to a nonconformity or a test is repeated at no cost to the client.

Before connecting any API, it’s worth sitting down together whoever manages the analytical catalog in the LIMS and whoever manages the item and price master in the ERP, and getting both catalogs to speak exactly the same language: same code, same billing unit, same exception logic. It’s organizational work, not programming work, and it almost always takes longer than the technical integration itself.

7. The regulatory context that makes this integration urgent

Why now, rather than in two years? Because e-invoicing mandates are advancing on multiple, uncoordinated timelines across markets, and public-sector invoicing is often already mandatory today:

Public-sector (B2G) e-invoicing: In the EU, public-sector e-invoicing has been mandatory for years under Directive 2014/55/EU; Spain implemented it from January 2015 through its FACE portal, in Facturae format. A lab invoicing municipalities, water consortia, or river basin authorities is already subject to this kind of obligation wherever it operates.

Real-time invoice verification: Beyond the EU’s cross-border framework, several countries already run — or are phasing in — real-time invoice verification and clearance systems of their own. Spain’s version, Verifactu, was postponed to 1 January 2027 for corporate taxpayers and 1 July 2027 for the rest, under a Royal Decree-Law published in December 2025.

Mandatory B2B e-invoicing: The EU’s VAT in the Digital Age (ViDA) package sets a 2030 floor for cross-border intra-EU B2B e-invoicing, but individual member states are moving faster on domestic mandates: Belgium and Poland went live in early 2026, France follows for large and mid-sized firms in September 2026, and Spain’s own domestic B2B mandate (under the Crea y Crece law) was still awaiting its implementing regulation as of mid-2026.

LIMS-ERP integration doesn’t, on its own, solve technical compliance with a real-time verification system like Verifactu —that depends on the certified invoicing software the ERP uses— but it does solve the part that usually breaks first: making sure the data reaching the invoicing system is correct, complete, and traceable back to its source. And that same documentary traceability —what was invoiced, from which result, validated by whom— is exactly the kind of trail that accreditation-body auditors (UKAS, A2LA, DAkkS, ENAC, or their equivalents) value when reviewing a lab’s management system, even though it falls outside the technical scope of ISO/IEC 17025 accreditation itself.

8. What the lab gains: benefits beyond “saving admin time”

Fewer days to invoice (and to collect): The time between result validation and invoice issuance stops depending on administration’s workload.

No more revenue leakage: A validated test that nobody moved into the ERP is work done and never billed. The integration makes that gap visible instead of hiding it.

Margin visibility: By cross-referencing operating cost (LIMS) with sale price (ERP), the lab can see real margin by client or contract, not just gross revenue.

Fewer tax and pricing errors: Each piece of data travels once, so a mis-applied tax rate or price no longer depends on someone typing it correctly twice.

Extended traceability: The link between the technical result and the resulting commercial document is recorded consistently — useful in both an accreditation audit and a tax inspection.

9. How to choose the right integration approach

There’s no single correct way to build the bridge between the LIMS and the ERP. The choice depends on invoice volume, whether the ERP is cloud or on-premise, and the IT resources available:

Approach	When it makes sense	Things to consider
Point-to-point integration (custom script)	Low to medium volume, a single ERP, a trusted internal or external technical team.	Fast to get running; requires ongoing maintenance as the ERP version changes.
Middleware / iPaaS (SAP Integration Suite, Power Automate, generic platforms)	Multiple entities, several connected systems, need for monitoring and retries.	Higher upfront and licensing cost; in exchange, greater traceability and resilience.
Native LIMS connector	When the LIMS already offers webhooks or prebuilt connectors to the chosen ERP.	Less development effort; worth validating exactly which fields and events it actually covers.

10. Common mistakes when integrating LIMS and ERP for invoicing

Misaligned catalogs: A LIMS parameter with no exact equivalent in the ERP’s item master produces incomplete or mispriced invoices.

Missing idempotency: If a retry after a network failure isn’t controlled for, the same test can end up invoiced twice.

Skipping the test environment: Testing directly in production, without an ERP sandbox, multiplies the risk of errors the client can see.

Ignoring the credit-note flow: Without an automated credit-note flow, every nonconformity or repeated test forces a manual correction.

Delegating all pricing logic to the ERP: If the LIMS doesn’t track the commercial status of a test, there’s no way to prevent it from being billed twice — or never.

11. Frequently asked questions

Do I need an ERP if I already have a LIMS?

No. Many small labs invoice directly from the LIMS or from a standalone invoicing program. Integration starts to make sense past a certain volume, or when the lab is part of a group with a corporate ERP already in place.

How long does a LIMS-SAP or LIMS-Business Central integration take?

It depends on scope, but a minimum viable flow —from billable event in the LIMS to draft invoice in the ERP— is typically measured in weeks, not months, provided the parameter and item catalogs are aligned beforehand. The part that takes the most time usually isn’t the technical connection, but that upfront data-organization work.

Does this integration affect ISO/IEC 17025 accreditation?

It isn’t part of the accredited technical scope, but it strengthens the documentary traceability between the result and the resulting commercial document — something auditors from accreditation bodies such as UKAS, A2LA, or DAkkS view favorably when reviewing the management system.

Does this integration help with real-time invoice verification systems like Verifactu?

It solves the source of the data —what’s being invoiced and from which result— but technical compliance with a system like Verifactu (chained record-keeping, QR codes, submission to the tax authority) depends on the certified invoicing software used by the ERP or the invoicing program connected to it.

What if I’m still on classic on-premise Navision instead of cloud Business Central?

Legacy on-premise installations of Dynamics NAV also expose OData and SOAP services, so integration remains possible, though with more security limitations and less standard API coverage than the cloud version of Business Central.