Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

ERP for Analytical Laboratories: LIMS, ISO 17025 and Billing, Which Architecture?

Accredited testing lab: do you need a LIMS, an ERP or both? Data flows, ISO 17025 requirements, three architectures compared and an implementation plan.

ERP for Analytical Laboratories: LIMS, ISO 17025 and Billing, Which Architecture?

In a private testing laboratory (environmental, food, industrial biology), the same question comes up at every software renewal: do we need a LIMS, an ERP, or both? The LIMS (Laboratory Information Management System) manages the sample and the result. The ERP manages quotes, invoices, purchasing, inventory and payroll. The two overlap in a few areas, and those overlaps are where projects go off the rails.

This guide is written for managing directors and CFOs of laboratories with 20 to 300 employees. It starts from the lab’s real data flows, goes through the ISO/IEC 17025 requirements that affect the information system, compares three architectures and gives a recommendation by company size.

What a LIMS does, and what it will never do

A LIMS is built around one object: the sample, from receipt to validated result. It typically can:

  • register the sample, assign it a unique ID and track its chain of custody (who received, stored, sub-sampled and analysed it);
  • assign tests according to methods, test schedules and specifications;
  • connect to instruments (chromatographs, spectrometers, balances) and capture results;
  • apply validation rules, limit compliance checks and second-person review;
  • issue the test report, with its version and signature;
  • keep an audit trail of changes.

What a LIMS does not do, or does poorly: general and cost accounting, supplier management and purchasing with approval workflows, payroll and timesheets, treasury, dunning, consolidation. Some vendors offer invoicing or reagent inventory modules. They cover a laboratory need, rarely the needs of a finance department that has to close the books, pass audits and steer the business.

Conversely, an ERP will never handle samples properly: no concept of an accredited method, no native link to instruments, no technical validation of results. An ERP that claims to replace the LIMS ends up as costly custom development that is hard to defend in an accreditation assessment.

The dividing rule is simple: the LIMS owns technical data, the ERP owns commercial and financial data. The rest is an interface question.

Mapping the flows: from quote to invoice

Here is the laboratory value chain and the system that should own each step.

StepContentOwning system
Quote and contractPrice list per test, volume discounts, termsERP (or CRM)
Sample receiptRegistration, unique ID, receipt conditionsLIMS
SchedulingAssignment to technicians, instruments, methodsLIMS
Testing and resultsData entry, instrument import, technical validationLIMS
Test reportIssue, signature, delivery to the clientLIMS
InvoicingOne line per test performed, at the contract rateERP, fed by the LIMS
Collection and dunningDue dates, disputes, DSOERP

Two breaks almost always occur.

From quote to sample. The client signs a quote for a list of tests. On receipt, the lab must find that quote in the LIMS to know what to analyse. Without a link, data is keyed twice and the gaps between quoted and performed work are never reconciled.

From report to invoice. This is the costliest break. If sales administration re-keys the list of completed tests by hand, two risks appear: forgotten tests (so unbilled) and tests billed at the wrong rate. In a lab with a high volume of small analyses, this revenue leakage often exceeds the cost of the software that would prevent it.

One special case not to forget: subcontracting. When the lab sends a test to a partner laboratory, the purchase, the tracking of the report received and the re-invoicing to the end client must all be tied to the original job. Our article on the procure-to-pay process in the ERP details the purchasing flow to put alongside it.

ISO/IEC 17025 requirements that affect the information system

ISO/IEC 17025 sets out the general requirements for the competence of testing and calibration laboratories (ISO/IEC 17025:2017). Without reproducing the standard, here are the families of requirements that weigh on the software architecture.

Traceability of samples and results. Every result must be linkable to the sample, the method, the operator, the equipment used and the test conditions. The LIMS is the natural home for this chain. The ERP should not duplicate it; it should reference it (job number, report number).

Calibration and equipment control. Measuring instruments must be calibrated and verified, with metrological traceability. Tracking calibration due dates is the laboratory’s job. Equipment maintenance, on the other hand, looks a lot like CMMS: preventive plans, work orders, spare parts. If your ERP already carries a CMMS, read our guide on industrial maintenance in the ERP to decide which system holds the instrument fleet.

Document control. Methods, work instructions, procedures: the lab must control versions, approvals and distribution. A LIMS or a quality management system (QMS) handles this. An ERP is not built for it.

Data integrity and the computerised system. The standard requires that data and information be controlled, and that information management systems be validated for their intended use, protected against unauthorised access, backed up and retained so as to guarantee integrity. This is the requirement that bears most directly on the architecture choice: the more systems handle technical data, the heavier the integrity demonstration.

What assessors look at on the IT side

Accreditation bodies publish guidance on this. In France, COFRAC is the accreditation body and publishes reference documents on its site, notably LAB REF 02 (accreditation requirements for ISO 17025), LAB GTA 86 (implementation recommendations on data control and information management) and GEN GTA 02 (technical guide on information systems, including data integrity). Other national bodies such as UKAS in the UK or DAkkS in Germany publish their own equivalents.

These documents are PDFs we could not review in detail for this article: before any project, have your quality manager read the current version from your own accreditation body. The questions you should expect an assessor to ask follow from the standard: how was the system validated? Who can modify a result, and is the change traced? How is data backed up and can it be restored? What happens during a version upgrade? The ERP’s role in this mechanism is to never be the place where a result can be changed.

Three possible architectures

LIMS alone + accountingERP with laboratory moduleLIMS + ERP integrated
PrincipleLIMS for technical work, invoicing in the LIMS or a simple accounting toolThe ERP also carries lab functions (samples, results)Two specialised systems connected by interfaces
AdvantagesOne technical system, simple validation, fast startOne database, one vendor, no interfaceEach system does its own job, scalability, full financial control
LimitsWeak financial steering, manual purchasing and inventory, double entry in accountingLimited lab depth, hard to defend in an accreditation assessment, heavy reliance on custom developmentInterface cost and complexity, two validations, two update cycles
Client profileSmall single-site lab, simple activityLab inside an industrial group already on that ERP, few analysesMulti-site, multi-client lab with subcontracting and margin pressure

A few vendor names, for illustration only, to make the landscape concrete. On the LIMS side there are LabWare (LIMS and ELN, with sector-specific offerings including water and food), LabVantage, STARLIMS (a vendor now part of Abbott) and Thermo Fisher SampleManager. Other, smaller or European vendors serve mid-sized testing labs. Product names and versions change quickly: check them on the vendors’ sites, and do not treat this list as a shortlist.

Our recommendation by size

  • Under 30 employees, one site, a homogeneous activity: LIMS alone plus a cloud accounting package. Do not build an architecture you cannot afford to maintain. Do insist on a reliable export of completed tests to invoicing.
  • 30 to 100 employees, several test families, subcontracting, first real steering needs: integrated LIMS plus ERP, with a deliberately thin interface scope (customers, contracts, price list, billable lines, consumables).
  • Over 100 employees, multi-site: integrated LIMS plus ERP, with a managed integration layer (bus or orchestration tool) and master data governance.
  • In-house lab of an industrial group: the ERP’s laboratory module may be enough if accreditation covers only a few methods. As soon as the lab sells analyses to third parties, move to a LIMS.

The ERP lab module remains the most fragile choice for an accredited laboratory that lives off selling analyses. This is not a judgement on ERPs; it is a question of functional depth in the core business.

Critical integration points

Four objects decide the quality of the integration. Define a master system for each.

Customer and contract master data. The customer is created once, in the ERP (or CRM), with its commercial terms. The LIMS receives it read-only. The usual trap is the double master: a customer exists under two names, and its analyses are invoiced to the wrong account.

Price list per test. A LIMS test (method, matrix, parameter) must map to a billable ERP item, with its rates per contract. This mapping table is the heart of automated invoicing. It requires real cleanup upfront: historical test codes, duplicates, outdated rates. Watch for bundled tests, rush surcharges and tests rerun after a non-conformity, which must not be billed twice.

Consumables and reagents. Reagents have lots, expiry dates and sometimes certificates. The question is: who holds the stock? Two models work. Either the ERP manages purchasing, receipts and valued inventory, and the LIMS consumes lots it receives by reference. Or the LIMS tracks lot and expiry (needed for method traceability) and the ERP keeps only the valuation. In both cases, the lot used for a test must be retrievable from the report.

Equipment and maintenance. The instrument fleet exists as a fixed asset in the ERP (accounting, depreciation) and as metrological equipment in the LIMS or QMS (calibration, verification, in-service or out-of-service status). The link is a unique equipment number. An instrument whose calibration has expired must be blocked from use in the LIMS, not merely trigger an alert in the ERP.

Profitability by test type and by client

This is where LIMS and ERP integration pays off most, because the LIMS knows how much time and which resources were consumed, and the ERP knows what that cost and earned.

The full cost of a test adds up:

  • technician time (preparation, analysis, review), valued at the loaded hourly cost;
  • instrument time, with depreciation and maintenance;
  • reagents and consumables, at the actual cost of the lots used;
  • any subcontracting;
  • the share of overhead: quality, accreditation, premises, sample collection logistics.

Compared with the price invoiced, it gives the margin per test type and, aggregated by contract, the margin per client. The findings are common: loss-leader tests sold below full cost to build loyalty, clients with frequent small samples whose logistics cost eats the margin, rush jobs insufficiently surcharged, rejections and reruns never charged back. The general method, with its indicators, is detailed in our article on customer profitability analysis: it applies directly here, provided the LIMS reports usable times and consumptions.

A caution: do not invent precision. If the LIMS does not capture actual times, use standard times per method, documented and reviewed, rather than falsely precise figures.

Project pitfalls and implementation plan

Pitfall 1: choosing the ERP before mapping the flows. Start with the flows from the earlier section, together with the quality manager and sales administration.

Pitfall 2: underestimating computerised system validation. The LIMS is a system whose validation assessors will examine. So is the interface to the ERP, as soon as it carries data that appears in reports (job numbers, client identifiers). Plan for specifications, documented tests, acceptance records and an update procedure, with the quality manager involved from day one.

Pitfall 3: historical data migration. Migrate the data needed for the traceability required by your retention obligations, not the whole history. Define what is migrated, what is archived read-only, and verify accessibility for the whole retention period.

Pitfall 4: an IT-only project. The LIMS touches accreditation, hence quality. The ERP touches finance. A steering committee of MD, CFO, quality and technical manager is essential.

Pitfall 5: replacing the LIMS and the ERP in the same year. When possible, stagger them: the first project stabilises the technical data, the second plugs invoicing into it.

A typical plan, to adapt to your size:

  1. Scoping: flow mapping, choice of the master system for each object, accreditation requirements identified with quality.
  2. Selection: demo on a real end-to-end scenario (one quote, three samples, one report, one invoice), not a generic demo.
  3. Interface design: test-to-item mapping table, customer master, error and rerun handling.
  4. Build and validation: documented tests, validation by quality, training.
  5. Cutover: a short dual-running period on a pilot scope (one client or one test family), then rollout.
  6. Follow-up: monthly reconciliation of tests performed versus tests invoiced, to catch gaps.

Key takeaways

An accredited laboratory does not have to choose between LIMS and ERP: each has its role. The LIMS guarantees the technical data and accreditation compliance. The ERP guarantees invoicing, purchasing, accounting and steering. What decides success is the quality of the interface and the clarity of the master system for each piece of data.

If you are unsure about the architecture, or if your test invoicing still relies on re-keying, a short architecture audit can settle the question before you commit a budget. Contact DigitsLane to discuss it. To go further, see also our guide on the procure-to-pay process and our article on customer profitability analysis.