AccountsIQ + Keystone

Keep your AccountsIQ.
Replace the spreadsheets running production.

AccountsIQ is a brilliant Irish accounts package — for accounts. It is not where you trace a batch, build a retailer-formatted dispatch note, or run a BRCGS mock recall. Keystone is the production layer that sits next to AccountsIQ — not on top of it, not instead of it. Our founding partner runs both, live in production.

AccountsIQ-ready out of the box — no replacement, no migration
Dispatched orders publish to AccountsIQ as invoiced sales, automatically
Your finance team keeps working in AccountsIQ — nothing changes for them
Live in production at Cashel Farmhouse Cheesemakers

Book a discovery call See pricing

The architecture

Finance in AccountsIQ. Production in Keystone.

For most food producers, the real daily work happens outside accounts: orders come in, production is planned, batches are made, stock is allocated, dispatch notes are prepared, COAs are generated, pallet labels are printed, traceability records are maintained, customer-specific codes are handled, audit evidence is pulled together. AccountsIQ does not solve any of those — and it should not. AccountsIQ is for customers, suppliers, invoices, VAT, ledger, payments and statutory reporting. Keystone is for everything else.

Where each system lives

A clean split, with one bridge.

AccountsIQ keeps doing

Sales ledger, purchase ledger, VAT returns, P&L, balance sheet, statutory reporting — exactly as it does today.

Keystone owns

Sales orders, weekly planner, batches, QC, dispatch notes, COAs, retailer pallet labels, batch traceability and mock recalls.

The handshake

When Keystone dispatches an order, it posts the invoiced sale to AccountsIQ via API. Stock movements update. Your finance team never re-keys anything.

What stays in Excel

Nothing operational. If something is being tracked in a spreadsheet today that affects dispatch, traceability or QC — it belongs in Keystone.

Why this works commercially

You are not signing up for an ERP migration.

AccountsIQ is trusted. Your finance team knows it. Your accountant signs off the year-end on it. There is no reason to disrupt that. The risk in most failed food-ERP projects is exactly the moment you try to replace the accounts package — staff resistance, year-end mismatch, audit trail gaps. Keystone removes that entire risk by leaving AccountsIQ exactly where it is. We bolt on the production reality your team currently survives on through Excel.

FAQ

Questions buyers actually ask.

Are you saying AccountsIQ is bad at production?

Not at all. AccountsIQ is best-in-class for Irish food finance. It is just not what BRCGS Issue 9 asks for in §5.4, and it is not where retailers expect their dispatch notes and COAs to come from. Two systems, two different jobs.

Do you publish invoices to AccountsIQ automatically?

Yes — dispatched orders post as invoiced sales via the AccountsIQ API. We configure mappings during implementation (typically 4–6 hours of work).

What about Sage or QuickBooks?

Both supported as scoped integrations. AccountsIQ is our reference because our founding partner runs it.

Is the integration two-way?

Currently one-way (Keystone → AccountsIQ) for invoiced sales. Optional two-way customer-master sync is a scoped extra.

Will it break my AccountsIQ if Keystone goes down?

No — Keystone writes to AccountsIQ in batches. If Keystone is unavailable, AccountsIQ keeps working; we replay missed writes when service resumes.

How do I explain this to my accountant?

“Nothing changes for AccountsIQ. We are adding a production system that auto-posts invoiced sales when an order ships.” That is usually the whole conversation.

Ready to see if Keystone fits your floor?

20-minute discovery call. No sales pitch. Written scope within 48 hours if we fit — referral to someone better if we don't.

Talk to us

Keep your AccountsIQ.Replace the spreadsheets running production.