Buying Operations Software in Portugal: A Straight Guide
Five things to know before you shortlist us, one of which is not like the other four. Then the two-minute check that should come before any feature comparison, an honest account of who we fit and who we do not, and the questions worth putting to every vendor on your list.
Most vendor guides put the limitations at the end, after the reader has invested twenty minutes and a certain amount of hope. This one puts them first, and the Portuguese list has an awkward property that makes the ordering matter more than usual: the first item on it is not a gap. It is not something we have not got round to, and it is not something you could pay us to close by a date. Presenting it in the same list as four ordinary gaps would flatten the one distinction a Portuguese buyer most needs, so it is separated out and explained.
The one that is not like the others
We are not a certified invoicing program in Portugal
Businesses established in Portugal are required — subject to conditions set out below — to issue invoices from software certified by the tax authority, which publishes the register of certified programs for anyone to search. We are not on it. Everywhere else on our site, a "no" ends with terms: this is on the roadmap, it is commissionable, here is what a written specification and a price would look like. That ending is not available here. We would scope and price the engineering a submission needs; the certificate itself is granted by the authority against its own requirements, and putting a date on somebody else's decision is not something we are willing to do. Read this as a fact about where the product stands today rather than a promise in either direction.
What follows from that is narrower than it sounds, and getting the scope right in both directions matters. What is ruled out is the issuing of fiscal sales documents by a business the rule catches. Stock across sites, batch traceability, quality holds, landed costs, procurement with approvals and three-way matching, projects, assets with named custodians, maintenance, helpdesk and personnel records are not touched by it. The common and entirely workable shape here is a Portuguese company whose invoicing stays in a certified package and whose operations move to us.
The conditions, because the turnover figure gets quoted alone
The obligation is usually explained with one number: businesses established in Portugal that turned over more than fifty thousand euros in the previous year must use certified software. That is accurate and, read by itself, it tells a small business it is in the clear. It is one of several conditions. The professional body for certified accountants sets them out together, and another of them catches anyone who uses invoicing software at all, with a further one for businesses required to keep organised accounts or who have opted into them.
Read together, they close the door the figure appears to leave open. Choosing to raise your invoices from software is itself one of the triggers, so there is no size at which an uncertified system becomes the correct answer; what stays available below the threshold is paper from an authorised printer, or issuing directly on the authority's own portal. We are naming the conditions, not applying them. Whether any of them applies to your business turns on where you are established, what you turned over and how you keep your accounts, and that determination belongs to your accountant rather than to a vendor's blog.
The other four, which are ordinary gaps
These behave like every other exclusion we publish: they have a shape, a price and a specification, and we would quote them.
| What is missing | What it means for you |
|---|---|
| Neither tax identification number reaches the invoice | Yours and your customer's are both stored, and the customer's address is collected too. None of the three prints on the document. The data is in the database and the fix is a template and a query, which is why this sits first among the ordinary items rather than last. |
| No ledger export in any prescribed schema | Our invoice export is seven columns of header data — reference, customer, date, total, balance, status — with no document lines, no rates and no tax codes. A billing ledger file is a different sort of object, and we do not produce one. |
| Our country profile carries the mainland rate only | Madeira and the Azores sit lower under the same tax code, and the product holds one rate per country. If you are on either archipelago, change the organization default before your first invoice. It takes a minute and nobody does it, because nobody looks. |
| No Portuguese payroll engine | No statutory calculation, no social security submission, no contribution schedule on a pay run. Hours, leave and labour cost are records here, and labour cost attribution to projects and cost centres does work. |
| No Portuguese reference customer | Nothing we publish about this market is a case study. This product was built in Nairobi for East African operations, and its live authority integration is Kenyan. If a reference in your own market matters to your decision — and it reasonably might — that is a good reason to choose something else. |
The check to run before any feature comparison
This takes two minutes per vendor and it is the only question on your evaluation that a demonstration cannot answer: search the tax authority's register of certified programs for every vendor on your list, including us, and note the name and number you find or do not find. Do it before you build the matrix, not after. A feature comparison run against a vendor that turns out to be ineligible is not a comparison that produced the wrong winner — it is one that never had a valid field.
Two things to watch for while you do it. A vendor answering "we are fully compliant" is answering a question about capability with a claim, when you asked a question about accreditation that has a public answer — ask again, and ask for the register entry. And a vendor offering a date for its certification is describing a decision it does not control; that answer tells you something useful, and what it tells you is not encouraging.
Who we fit here, and who should rule us out
A good fit
- A manufacturer, distributor, food or drink exporter, or engineering firm whose invoicing already lives in a certified package and whose operations live in spreadsheets. This is the common shape and essentially nothing in this guide is your problem.
- A business whose real question is stock across more than one site, and whether the figure on the screen is a position or a guess.
- Anyone who needs batch and expiry traceability in both directions — where a consignment came from, what it was split into, who it went to — held against the batch rather than reconstructed from paperwork afterwards.
- A procurement function that needs approvals that actually refuse, and a three-way match before anything is paid, without hiring a department to enforce it.
- A group with operations outside Portugal as well, where the operational system needs to span them and the fiscal documents stay local in each.
Rule us out
- You need one system to issue your Portuguese fiscal invoices. We cannot be that system for a business the certification rule catches, and no configuration changes it.
- You need the monthly communication of billing records produced from the same system that holds the transactions. We produce nothing of the kind.
- A Portuguese-language interface is a procurement requirement rather than a preference. Ours is English, and that is a genuine limitation for a warehouse floor or a maintenance crew even where it is not one for a finance lead.
- You need a Portuguese payroll run rather than labour cost attribution.
- A local reference customer is a condition of purchase. We do not have one and would rather say so now.
Six questions worth asking every vendor on your list
Including us, and we have answered all six in public
Are you on the register of certified programs, and under what name and number?
What a good answer sounds like
A name and a number you verify yourself, or a straight no. Ours is a straight no.
What a bad answer is telling you
A claim of compliance in place of a register entry means the question has not been understood, or has been understood and dodged.
How many document series can I run, and can I declare them in advance?
What a good answer sounds like
Named series, declarable before use. Ours runs one counter per document type per year.
What a bad answer is telling you
One counter per document type is very common and is not the same as a series you registered. In a market that registers series, that difference is the requirement.
Is the numbering sequence private to my company or shared with your other customers?
What a good answer sounds like
Private, enforced per company. Ours is not, for five document types, and we have written about it.
What a bad answer is telling you
Hesitation means nobody has checked. It is a five-minute look at their schema, and it decides whether a missing number in your ledger is a question you can answer.
Show me a generated invoice PDF, not the tax settings screen.
What a good answer sounds like
The document, with the identifiers and the address on it.
What a bad answer is telling you
A settings screen proves a field exists. It does not prove the field reaches the document — on our product it does not, and we are not the only ones.
What exactly does your export contain — headers only, or lines and tax codes?
What a good answer sounds like
A sample file, opened in front of you.
What a bad answer is telling you
If the answer is a list of report names, ask for the file. Ours is seven header columns and we would rather tell you than have you open it in week three.
If your software cannot issue our fiscal documents, what is left for it to do?
What a good answer sounds like
A frank division of labour. For an operations system the honest answer is most of the product.
What a bad answer is telling you
If everything falls apart without invoicing, you are being sold an accounting package with an operations module attached, rather than the reverse. Useful to know either way.
Two things worth ignoring
-
Rate tables on vendor pages
Portugal has a standard rate and two lower ones, and which goods and services sit on the lower ones is set by lists annexed to the tax code — lists that move. A vendor page printing the menu is publishing something that will be quietly wrong at some point and quoted anyway. Take the structure from a vendor if you like and the assignments from your accountant. What a vendor page should tell you is what its own software does with the rates, which is a fact about the software and is checkable.
-
Compliance badges that are not the register
Security certifications, quality standards and hosting accreditations are real things and none of them is the register you actually need to search. A page full of logos can coexist with an absence from the one list that matters here. Search the list.
What AWRA OpsHub does today
- The operational product in full — stock across sites with acknowledged transfers, batch and expiry traceability, quality holds that block picking, landed costs pushed into unit cost, procurement with approvals and three-way matching, an asset register with named custodians, projects, helpdesk and personnel records.
- A locked, per-organization, per-year document counter behind every sales document — the structure a registered series needs, minus the registration.
- A tax authority's machine-readable code rendered on the invoice, in vector, from a stored payload, beside a receipt number, a receipt signature and a filing timestamp. Kenyan, live, and evidence that this shape of work is ordinary for us.
- Refusal to delete an issued invoice. Corrections run through cancellation or a credit note.
- Euro handled as an ordinary base currency at two decimal places, with document-level exchange rates.
What it does not do
- A certified invoicing program, and no register entry. First because it is the only item on this site that is not work we can be commissioned to complete.
- Series registration and the code an authority returns for it, so nothing our documents print can be a unique document code.
- A sequence private to your organization, for invoices, credit notes, purchase orders and point-of-sale documents. A defect of ours, and we would treat it as a correction rather than a feature.
- A ledger export in any prescribed schema, and no communication of billing records to any Portuguese authority.
- Both tax identification numbers and the customer's address on the printed invoice. All three are stored and none of them prints.
- Regional rates. Our profile carries the mainland figure; Madeira and the Azores sit lower and nothing in the product knows which you are in.
- A Portuguese payroll engine, and no Portuguese-language interface.
Not ours, by choice
- We will not date the certification. We would scope and price the engineering on the usual terms. The certificate is theirs to certify, and a vendor implying otherwise is selling you a risk it has not priced.
- We will not tell you whether the rule catches your business. The conditions turn on facts about your establishment, your turnover and your accounts, and applying them is a determination your accountant makes and signs.
- We will not describe our records as non-alterable in the sense the certification requirements mean. Deletion is refused, which is true, checkable and weaker, and we have never been assessed against those requirements by anybody.
- We will not be your filing agent, here or anywhere. The obligation is yours and software should make it answerable rather than absorb it.
- We will not claim per-organization data residency. Hosting region is a property of a deployment. An EU-region deployment is real work we would price; it is not a setting, and our compliance matrix records where we published otherwise and corrected it.
The ordering here is unusual because the first exclusion is not first in the work. Put both tax identification numbers and the customer's address on the printed document, make the document counter genuinely private to each organization, and build a ledger export that carries lines and tax codes rather than seven header columns — three pieces of work that are specified, small to middling, and that improve every European market in the product rather than only this one. That is what we would quote today. The Portugal-specific engineering behind a certification submission — series registration, the document code, the authority's own machine-readable payload, the prescribed schema and the record-integrity properties the requirements test for — we would scope as a build and price honestly, telling you plainly that completing it begins an application rather than ends one. Usual terms: a written specification, a timeline and a price agreed before anything starts, and no dates on a public page.
The sentence we would rather write than have inferred: none of this makes the product unusable in Portugal, and reading it that way would be a mistake in the other direction. One module is ruled out for businesses the rule catches. Nine are not. If your invoicing already lives somewhere certified, the whole first half of this guide is somebody else's problem and what you are actually evaluating is the operations half.
What is not built for Portugal 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 Portugal. 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 the engineering behind a certification submission, scoped honestly, 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.
Three builds we would quote, and one thing we would not pretend to schedule
Start with the work that is specified and portable. Put both tax identification numbers and the customer's address on the printed document — all three are stored today and none of them prints. Make the document counter genuinely private to each organization, because for sales invoices, credit notes, purchase orders and point-of-sale documents it is currently reconciled against a number unique across the whole platform, so a sequence can skip for reasons that have nothing to do with the business reading it; that one we would treat as a correction rather than a feature. Then a ledger export that carries documents, lines, customers, products and tax codes, instead of the seven header columns the invoice export emits today. All three improve every European market in the product rather than only this one. The Portuguese-specific engineering is a separate and larger piece — document series registered with the authority in advance, the unique document code that comes back, the authority's own QR payload rendered on the document, the prescribed export schema, and the record-integrity properties the requirements test for — and we would scope and price it like any other build. What we would not do is put a date on the certification itself. That is granted by the Portuguese tax authority against its own requirements, and finishing the engineering is the beginning of an application rather than the end of one. Every other paragraph in this section of the site ends with terms we would agree with you; this one ends by saying which part is not ours to agree.
Banks and payments
SEPA credit transfers and direct debits, Multibanco references and bank statement feeds wired into the Payments Register, so money in and out reconciles against the documents that authorised it 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
A Portuguese payroll engine with statutory withholding and social security contributions computed on live employee records, and the monthly schedules produced in the layout the filing body expects. 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
Search the register first, decide where your fiscal documents get issued from second, and only then compare features. If the answer is that invoicing stays where it is, nearly everything in this guide stops applying to you and the conversation gets a great deal simpler.
The long version, with our own code measured against it
Our Portugal page sets out all four obligations against what the product actually does today, including the three where the distance is shorter than we expected and the one where distance is not the relevant measure.
Read the Portugal page