Why AccountsIQ and Sage don't solve batch traceability alone

Every Irish food producer I've audited in the last three years has the same gap. They've invested heavily in accounting software — typically Sage 50, Sage 200, AccountsIQ, or Xero — and they assume it will handle batch traceability. It doesn't. It can't. It was never designed to.

What accounting software is for

Accounting software books the financial transaction. A purchase invoice. A sales invoice. A bank reconciliation. A VAT return. It is exceptionally good at this. It is also where your accountant lives and where your statutory accounts originate. You should not throw it out.

What batch traceability actually requires

When the FSAI inspector knocks (or, more likely, when your largest retailer's quality team emails at 16:47 on a Friday asking for the COA on batch #L2024-08-471), you need to answer five questions in under fifteen minutes:

• Which raw-material lots fed into this finished-batch number?
• Which finished products contain those raw-material lots? (the 'one-up' question)
• Which customers received those finished products? (the 'one-down' question)
• What were the QC results — temperature, pH, water activity, micro results — for this batch?
• Where are the dispatch notes, COAs and shipping documents that prove all of the above?

None of these questions can be answered from Sage or AccountsIQ. The data isn't there. The schema doesn't support it. The reports don't exist.

What the missing layer looks like

The missing layer is a production system. It sits between the floor and the accounts. It captures:

• Goods-in receipt with supplier-lot numbers
• Production batch records linked to raw-material lots
• QC checks per batch, with retention
• Dispatch records linked to customer purchase orders
• COA generation from the QC data
• Mock-recall query: 'Show me everywhere lot ABC123 went' in under 60 seconds

It then talks to accounting — the dispatch becomes a sales invoice in Sage; the receipt becomes a purchase invoice. Two systems, one source of truth, no double-entry.

How Keystone does it

We built Keystone for Cashel Farmhouse Cheesemakers because every off-the-shelf option was either €40k of generic ERP they didn't need, or a spreadsheet held together with a forty-year-old prayer. Keystone is the boring, opinionated, retailer-ready production layer that sits between the floor and Sage. Batch records. QC. Dispatch. COAs in four seconds. Mock-recall in twelve.

What to do next

If your batch traceability lives in spreadsheets and 'Mary's notebook', it's time to fix it before the next FSAI / BRCGS audit catches you. Talk to us about Keystone or a custom production system.