Bookkeeping for medtech, separate from the QMS

Regulated startups still have to invoice and keep books. HAVGATE's bookkeeping module does that work beside the eQMS. It is not the device history record, and it is not turned into one.

What is in the product today

The bookkeeping area in the application includes customers, quotes, invoices, receipts, a ledger, statements, reports, projects and a Swiss QR-bill path. It is enabled per workspace. Public pages do not drop a visitor into that screen. A workspace owner turns it on. The same company can run the eQMS without opening bookkeeping.

Why a device company cares

Purchasing is a quality process and a money process. MDSAP Chapter 7 and ISO 13485 clause 7.4 ask who the approved supplier is, what you ordered, and how you checked what arrived. Finance asks what you were invoiced and whether you paid it. Those questions meet, and they should not be the same record. An invoice number on a CAPA, or a CAPA number inside a sales ledger, makes both files harder to explain to an auditor and to an accountant.

The link that is not built yet

The codebase does not attach a bookkeeping invoice to an approved supplier record, and it does not block payment because a supplier evaluation lapsed. A person can keep the supplier file in the supplier module and the bill in bookkeeping, and they can write the supplier name in both places. That is a manual link. Calling it an automatic trace is not accurate.

What stays in quality

• Approved suppliers, risk and re-evaluation stay in supplier quality.
• Nonconforming purchased product stays a nonconformance, then a CAPA if your procedure says so.
• The purchase specification, if you control it, stays a controlled document.
• The commercial invoice, the receipt and the ledger stay in bookkeeping.

The pricing page is the audit platform only. Bookkeeping is a separate module and is not included in those plans.