Buying Operations Software in Ireland: A Straight Guide
What to ask, what to ignore, and the four things that should take us off your shortlist — written by the vendor, which is a reason to read the disqualifying list first.
A buyer's guide written by a vendor is a compromised document, so the useful thing to do with it is read the exclusions first. Ours: we have no integration with Revenue of any kind, no Irish payroll engine, no per-line VAT rate selection, and no Irish reference customer. If any one of those four is central to your decision, you can stop here and you have saved a fortnight.
What follows is the rest of it — the questions that are worth asking any operations vendor selling into Ireland, including the ones that are awkward for us. The bias in this document is not in the answers; it is in which questions got asked. So the second half is a list of the questions we would ask if we were buying.
The four exclusions, in full
| What is missing | What that means in practice |
|---|---|
| No Revenue integration | No ROS connection, no VAT3, no Return of Trading Details, no VIES, no Intrastat. Nothing files. Returns are produced by your accounting system or your accountant, from exports. |
| No Irish payroll engine | No PAYE, PRSI or USC calculation, no submission on a pay run, no pension auto-enrolment assessment. Labour cost is attributed to projects and cost centres, which is useful and is not payroll. |
| No per-line VAT rate | A line gets your organization's default rate or zero. If your invoices mix positive rates, the rate has to be settled somewhere else. |
| No Irish reference customer | Nothing we would say about Ireland is a case study. Our live tax-authority integration is Kenyan and this product was built in Nairobi. |
One thing that is genuinely not a problem here
Language. Our interface is English-only, and in Ireland that is simply not a constraint — which is worth stating precisely because it is a real constraint in most of the other European markets we serve with a directory page rather than a guide. If you are comparing our Ireland page with our Canada page, the Quebec paragraph there is the difference, and it is a legal one rather than a preference.
Where we are a straightforward fit
Not a feature list — a shape of business. We are worth a conversation if most of these describe you.
- Your tax is handled by an accounting system or an accountant, and what you need from an operations system is clean exports rather than a tax engine.
- Your invoices sit largely on one rate, so an organization default is correct rather than a compromise.
- Your real problem is procurement, approvals, stock across locations, or project cost — the operational half, where the time actually goes.
- You care about an audit trail on decisions, not only on records: who approved what, at what threshold, against which budget.
- You buy in more than one currency and want the rate recorded on the document rather than reconstructed from a monthly average.
Where you should rule us out
These are disqualifying rather than difficult, and we would rather write them than have you find them in month three.
| If this is true of you | Why we are the wrong choice |
|---|---|
| Your invoices routinely mix two or more positive VAT rates | A line gets the default or zero. You would be managing the difference by hand on every mixed document, and the failure mode is a plausible wrong number rather than an error. |
| You want your operations system to file your VAT | It does not file anything, anywhere, and the honest sequence to get there starts with a schema change rather than a submission button. |
| You need Irish payroll in the same system | There is no PAYE, PRSI or USC calculation and no submission. Our one statutory payroll engine is Kenyan. |
| An Irish implementation reference is a requirement | We do not have one, and no amount of describing the same class of work elsewhere is the same thing as having one. |
| You need the zero-rated and exempt distinction preserved in the data | Both collapse to the same nil on a line today, so the record cannot tell you afterwards which you meant. |
Six questions to ask every vendor, including us
None of these can be answered with a brochure
Which record is the VAT rate a property of — the organization, the item, or the line?
What a good answer sounds like
A noun, straight away.
What a bad answer is telling you
A feature name instead of a record means nobody knows, and the answer is usually the organization.
Show me an invoice with two different positive rates on it. On screen, not on a slide.
What a good answer sounds like
A document, produced in under a minute.
What a bad answer is telling you
If the demonstration substitutes taxable-plus-exempt, that is a different capability being passed off as this one.
What happens to a rate value your system does not recognise?
What a good answer sounds like
It is rejected.
What a bad answer is telling you
If it falls through to a default, the system will produce wrong tax precisely when somebody tries to be careful. Ours does this today.
Who produces the VAT return, and from which records?
What a good answer sounds like
A named system and a named record, with an export in between if two systems are involved.
What a bad answer is telling you
If the answer involves a spreadsheet nobody owns, the spreadsheet is part of your compliance chain.
What exports exist, and in what formats?
What a good answer sounds like
CSV, XLSX and JSON, with a schema you can look at.
What a bad answer is telling you
PDF-only reporting means every handoff downstream is re-typing.
Name an Irish customer I can speak to.
What a good answer sounds like
A name, or a straight no.
What a bad answer is telling you
A hedge — "we have European customers", "we can arrange a reference" — is a no that has not been said. Ours is a no.
Two things worth ignoring
First, rate tables on vendor pages. Ireland's rungs are stable and what sits on them has moved more than once, so a vendor page printing the full list is telling you when it was last edited rather than what the law says. Get structures from a vendor and numbers from your accountant. We deliberately do not print the list, which is either discipline or an excuse depending on your view, and either way you should check the date on any page that does.
Second, compliance badges without a scope. "GDPR compliant" as a claim on a features page is not a statement about anything checkable. The useful version names the specific capability and its limits — which of your obligations the software can evidence, and which it cannot. Ours are set out row by row on our compliance matrix, with two rows carrying a code-verification date and eleven carrying an explicit statement that they do not.
What AWRA OpsHub does today
- Procurement end to end — requests, approvals, orders, receipts, three-way matching, supplier records and prequalification.
- Inventory across locations with transfers, approvals, counts, adjustments and per-item movement history.
- Projects, time and budget control, with checks at the point of commitment rather than reporting afterwards.
- A rate column on every sales line, item-level treatment, and per-levy arithmetic against each levy's own base.
- Machine-readable exports in CSV, XLSX and JSON, which is what a handoff to an accounting system needs.
What it does not do
- Per-line rate selection, which is the gap that matters most for a mixed-rate Irish business.
- A stored distinction between zero-rated and exempt.
- Any Revenue integration, in any form.
- An Irish payroll engine — no PAYE, PRSI, USC or pay-run submission.
- A VAT return output, and no tax dataset in the report catalog.
Not ours, by choice
- We will not tell you which rate applies to a supply. Your accountant makes and signs that determination.
- We will not be your filing agent, even once an integration exists.
- We will not claim per-organization data residency. Hosting region is a property of a deployment; an EU-region deployment is real and priced, and it is not a setting.
- We have no Irish reference customer, and we would rather write that here than let you assume otherwise.
The Irish sequence is a rate set, a line selector, a preserved zero-rated and exempt distinction, and then a return assembled from all three. The first is the one without which the rest is decorative, and it would improve every multi-rate market rather than only this one. The precedent is Kenya — a live tax-authority integration and a maintained statutory payroll engine, both built to specification and both still ours to run. A written specification, a timeline and a price agreed before anything starts.
What is not built for Ireland today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in Ireland. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a rate per line rather than per organization, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
The three builds, and the first one is the whole thing
A rate selected per line from a set the organization defines, rather than one default rate with a zero override — because a country with five live VAT rates cannot be served by a model with two outcomes, and today an item treatment our resolver does not recognise silently produces the standard rate. Then a stored distinction between zero-rated and exempt, which currently collapse to the same nil on a line and mean different things on a return. Then a return assembled from both. The first build is a schema and resolver change, it is the one without which the other two are decorative, and it would improve every multi-rate market in the product rather than only this one — which is the argument for doing it properly rather than for one country.
Banks and payments
SEPA credit transfers and direct debits, plus bank statement feeds wired into the Payments Register, so money in and out reconciles against documents rather than being re-keyed from a bank screen.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
An Irish payroll engine with PAYE, PRSI and USC computed on live employee records, submission on each pay run, and pension auto-enrolment assessment. None of it exists today; labour cost attribution to projects and cost centres does.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedThe one-line version
If your tax lives somewhere else and your problem is operations, this is a short and straightforward conversation. If you want your operations system to determine and file Irish VAT, it is the wrong system today, and the four exclusions at the top of this page are the fastest way to find that out.
Bring a mixed invoice
The fastest way to find out whether we fit is to show us a real document with more than one rate on it and let us tell you exactly what our schema would do with it.
Read the Ireland page