AWRA OpsHub Search
Portugal · Iberia

In Portugal the invoice is not the regulated thing. The software is.

Most countries write rules about the document: what it must name, which figures it must show, when it must be sent. Portugal does that too, and then does something else. It regulates the program — certified by the tax authority against published requirements, listed by name and certificate number on a register anybody can search, issuing from document series registered before a single invoice is raised, stamping each document with a code drawn from the authority's own scheme. AWRA OpsHub is not on that register. So the question a Portuguese buyer has to settle is not whether our arithmetic is right — it is — but whether we are permitted to issue the document at all. For a business caught by the rule, we are not. That rules out one module. It does not rule out the product, and this page is careful about the difference because the difference is most of what we do.

The four obligations, measured Skip to what does work here

Measured, not estimated

Four things Portugal asks of the software, and how far this product already is

The left column is the obligation. The right is the distance from where the product stands on 5 August 2026 — and the distances are not the same, which is the useful part. Three of the four are engineering. One of them is not a feature at all, and no amount of engineering converts it into one.

The program must be certified by the tax authority

This is the row that matters and the row nobody expects. Certification is granted by the Portuguese tax authority against its own published requirements, and certified programs appear on a public register with a number that goes on the documents they produce. We hold no such certificate. We could scope and price the engineering a submission would need; we could not promise the outcome, because the outcome is theirs to certify and not ours to schedule. Every other refusal on this site ends with a date we would agree with you. This one deliberately does not.

Not a feature — an accreditation

Each document series is registered with the authority before use, and the authority returns a code for it

The distance here is genuinely short, which is worth saying on a page this negative. Document numbers already come from a locked counter held per organization and per year — that is structurally what a series is, and it is why the numbering is orderly rather than a timestamp. What does not exist is the registration step, the code that comes back from it, or the ability to run more than one series. There was a real defect underneath it, and it was ours: until 6 August 2026 that counter was, for sales invoices, credit notes, purchase orders and point-of-sale documents, reconciled against a number unique across the whole installation, so an organization's sequence could skip for reasons belonging to somebody else's business. It is now scoped to the organization. Nothing was renumbered, so gaps created before that date are still printed on documents people hold.

The machinery exists, built for another country

Every document carries a unique document code and a QR code to the authority's specification

Mandatory on invoices and other fiscally relevant documents since the start of 2023. The surprising part is how much of this we already do: our invoice template renders a tax authority's QR code today, in vector, from a stored payload, alongside a receipt number and a receipt signature the authority returned. That is Kenya. The renderer, the library and the place on the page are all in production. What is missing is the Portuguese payload, the code, and the series behind it — which is a specification problem rather than a capability one.

The machinery exists, built for another country

The billing records go to the authority monthly, by the fifth of the following month

One of the permitted routes is a standard structured file covering the billing ledger — the documents, their lines, the customers, the products and the tax codes. We produce nothing of the kind. Our invoice export is seven columns of header data: reference, customer, date, total, balance and status, with no lines, no rates and no tax codes. That is a spreadsheet of invoices, and a ledger export is a different sort of object. The transmission half we have done once, for another authority, and know the cost of.

Not built

The part that gets misread

The turnover figure is real, and it is not the escape hatch it looks like

The obligation to use certified software is usually explained with a number: businesses established in Portugal that turned over more than fifty thousand euros in the previous year must use it. That is accurate, and read on its own it tells a small business it is safe. It is not the only trigger. The professional body for certified accountants sets out the conditions as a set, and the other two matter more than the figure: the obligation also catches anyone who uses invoicing software at all, and anyone required to keep organised accounts or who has opted into them.

Read the second trigger slowly, because it is the one that decides whether this page applies to you. A business under the turnover figure that chooses to raise its invoices from software is choosing to be caught by the rule — the alternative left open to it is paper from an authorised printer, or issuing directly on the authority's own portal. There is no size at which "small enough to use an uncertified system" becomes true. We are stating the triggers rather than applying them: whether your business meets any of them is a question about your establishment, your turnover and your accounts, and it belongs to your accountant rather than to a vendor page.

What this costs in practice

Four ways a shortlist built on features gets Portugal wrong

The shortlist question here is not a feature question

Every procurement checklist asks whether the software handles the rules. In Portugal there is a prior question — whether the software is permitted to issue the document — and it is not answered by any feature comparison, because it is answered by a register.

A turnover figure that reads as permission

The fifty thousand euro trigger is the part everyone quotes and the part that misleads, because a separate condition catches anyone using invoicing software regardless of size. The businesses most likely to read the figure as an exemption are the ones it does not exempt.

A number is not the same as a series

Sequential document numbering is something almost every system does. A registered series with a code the authority supplied is a different object, and a system that has the first can look compliant while having none of the second.

The mainland rate is not the national rate

Madeira and the Azores set lower rates under the same code, and software that ships one figure per country gets the islands wrong on the first invoice, silently and in the customer's favour or against it depending on which way the default fell.

Scope, in three parts rather than two

What runs today, what we would build, and where we stop on purpose

Three columns, because "no" means two entirely different things and one list hides which is which. Read the first item in the middle column carefully: it is the only entry anywhere on this site that sits in that column without a price attached, and it is there because the outcome is decided by somebody who is not us.

Scope in Portugal, and the one item that belongs to a certification body

Real today

  • A locked, per-organization, per-year document counter behind every sales document. The structure a registered series needs, minus the registration.
  • A tax authority QR code rendered on the invoice, in vector, from a stored payload — with a receipt number, a receipt signature and a filing timestamp beside it. Kenyan, live, and evidence that this shape of work is ordinary for us rather than aspirational.
  • Refusal to delete an issued invoice. Corrections run through cancellation or a credit note.
  • Item-level tax treatment travelling with the item onto every document, and a rate column at two decimal places on every sales line.
  • Euro handled as an ordinary base currency with document-level exchange rates.
  • The operational product in full — stock across sites with acknowledged transfers, batch traceability, quality holds, landed costs, procurement with three-way matching, an asset register with named custodians, projects, helpdesk and personnel records.

More we can add — and one of these belongs to a specialist

  • The engineering behind a certified invoicing program, with the certificate awarded by the authority. This is first because it is the only item on any page of this site whose final step is not ours to take: we can scope and build to the requirements, and certification is awarded rather than written. Read that as a fact about where this product is today rather than a promise in either direction.
  • Series registration and an authority-supplied code, so nothing our documents print can be the unique document code. The counter beneath it is the right shape, which shortens the engineering and changes nothing about the paragraph above.
  • One series per document type per year, and no way to declare a second. The counter is per organization and per year, which is the right shape, but a series you cannot name, register or run alongside another is not the series this regime means. Until 6 August 2026 there was a worse problem here — for invoices, credit notes, purchase orders and point-of-sale documents the counter was reconciled against a number unique across the whole installation, so a sequence could skip for reasons belonging to somebody else. That is fixed and scoped to the organization now; the sequence breaks it already created were not closed, because closing them would mean rewriting documents customers hold.
  • Communication of billing records to the authority, and no ledger export file in any prescribed schema. Our invoice export is seven header columns with no lines, no rates and no tax codes.
  • Both tax identification numbers on the invoice. Yours and your customer's are both stored today and the document prints neither, and the customer's address is collected and not rendered. Documented at length on the Netherlands page, true in every European market, and true here.
  • Our profile carries the mainland rate only. Madeira and the Azores set their own lower rates under the same article of the code. An organization on either archipelago is provisioned wrong until somebody changes the default, and we would rather write that here than let it appear on a first invoice.
  • Record integrity assessed against what certification means by non-alterable. Deletion is refused today, which is true, checkable, and a weaker property than the standard describes. We have never been assessed against the record-integrity requirements, and we describe ourselves accordingly until we have been.
  • A Portuguese payroll engine — statutory calculation, social security submission and a contribution schedule on a pay run.

What we would decline, and would rather say now

  • We will not tell you that certification is coming. We would scope and price the engineering a submission needs, on the usual terms — a written specification, a timeline and a price agreed before anything starts. What we will not do is put a date on an outcome that is decided by somebody else. Certification is theirs to certify, and a vendor who implies otherwise is selling you a risk they have not priced.
  • We will not tell you whether the rule catches your business. The conditions turn on where you are established, what you turned over and how you keep your accounts. Naming them is useful; applying them to your company is a determination your accountant makes and signs. A software vendor with a view on it is inviting reliance it cannot carry.
  • We will not be your filing agent, here or anywhere. Even with every integration built, submitting on your behalf and standing behind the contents is not work we would take on. The obligation is yours and software should make it answerable rather than absorb it.
  • We will not claim per-organization data residency, because it does not exist. Hosting region is a property of a deployment. An EU-region deployment is a real thing we would do and price; it is not a setting, and the compliance matrix records where we published otherwise and corrected it.
  • We have no Portuguese reference customer. Nothing here is a case study. If a reference in your own market matters to your decision — and it reasonably might — this is among the most important sentences on the page.

The honest ordering here is unusual, because the first item is not first. Put both tax identification numbers and the customer's address on the printed document, make the document counter genuinely private to each organization, and add the ledger export — 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 the part we would quote today. The Portuguese-specific engineering behind a certification submission — series registration, the document code, the authority's QR payload, the prescribed export schema, and the record-integrity properties the requirements test for — we would scope as a build and price honestly, and we would tell you plainly that finishing it is the beginning of an application rather than the end of one. The precedent for the shape of the work is real rather than rhetorical: a live authority integration with QR, receipt number and signature on the document, and a maintained statutory payroll engine, were both built to specification for one market and are part of the product now. Usual terms, and a date in a quote rather than on a public page.

One thing we would rather state than have inferred. We are not saying the product is unusable in Portugal, and it would be a poor reading of the page. What is ruled out is a module: the issuing of fiscal sales documents by a business the rule catches. Stock, procurement, projects, assets, maintenance, helpdesk and personnel records are untouched by it, and a Portuguese business that keeps invoicing where it already is loses nothing on this page. The reason the finance half gets the top of the page anyway is that discovering it in month three of an implementation would be far worse than reading it now.

Operations in Portugal

The section above is about one module. This is about the other nine.

Everything above concerns the issuing of sales documents. Nothing above touches stock, procurement, projects, assets, maintenance, helpdesk or people, and none of those is regulated by the rule that rules out the first. A Portuguese manufacturer, distributor, agricultural exporter or engineering firm that keeps its invoicing where it already is loses nothing on this page — and gets the part of the product that is actually ours.

Traceability

Batch and expiry held at item level, in both directions

Where a consignment came from, what it was split into and who it went to, held against the batch rather than reconstructed afterwards from paperwork. In wine, cork, olive oil, horticulture and canned fish — the exporting spine of this economy — this is the record somebody asks for at short notice and on a bad day.

Quality holds

Stock blocked from sale while a question is open

A status that quarantines the affected quantity pending release, at batch granularity. The useful property is that it is a state of the stock rather than a note somebody left: the goods cannot be picked while the hold stands, whoever is picking.

Stock transfers

Goods leaving one site for another, acknowledged at both ends

Approved, confirmed transfers with quantities signed for on arrival rather than assumed. For a business running a plant in the north and a distribution point near Lisbon, the difference between a dispatch note and a confirmed receipt is the difference between a stock figure and a guess.

Landed costs

Freight, duty and handling pushed into the unit cost

Charges apportioned across a consignment so an item's cost reflects what it took to get it here. For an Atlantic-facing importer and re-exporter this is the difference between a margin you can defend and one you discover at year end.

Procurement

Approvals that refuse, and a match before anything is paid

Requisition, threshold approval, purchase order, goods receipt and three-way matching, with the supplier record and its prequalification attached. In a company of forty people that control is usually one person's attention; this is how it stops being that without hiring a department.

Assets

Plant and handling equipment with a named custodian and a movement history

Presses, chillers, forklifts, racking and vehicles on a register holding the custodian, the location, the movement history, the inspection rhythm and the documents. A claim about equipment becomes checkable rather than remembered.

The qualification this section needs, and it is a real one: no Portuguese payroll engine. No statutory calculation, no social security submission, no contribution schedule on a pay run — so hours, leave and labour cost here are records rather than a payroll run. It is on the commissionable list, and Kenya's maintained statutory engine is the reason we would price that work rather than guess at it.

Before you buy anything

Four checks that work on any vendor, including us

Search the register before you shortlist anybody

The tax authority publishes the list of certified programs and anyone can search it. Do that for every vendor on your list, including us, before you compare a single feature. It takes two minutes and it is the only question on the list that a demonstration cannot answer.

Settle where your fiscal documents are issued from, first

If a certified package already issues your invoices, the shortlist you are running is for an operations system and this page mostly does not apply to you. If you were hoping one system would do both, find that out in week one rather than week twelve.

Ask any vendor how many document series it can run

One counter per document type is very common and it is not the same thing as a series you registered. The follow-up worth asking is whether the sequence is private to your company or shared with the vendor's other customers — a question almost nobody asks and some systems answer badly, including this one.

If you are in Madeira or the Azores, check the default rate on day one

Any system that ships one rate per country ships the mainland figure. On the islands that is wrong from the first invoice, and it is a two-minute change that nobody makes because nobody looks.

Questions we are asked here

Direct answers, including the one that does not end in a roadmap

Is AWRA OpsHub a certified invoicing program in Portugal?

No. We hold no certificate from the Portuguese tax authority and we do not appear on the register of certified programs, which anybody can search. This is a boundary rather than a backlog, and it is the only one of its kind on this site. Every other refusal we publish ends with work we would agree a price and a timeline for. This one ends differently on purpose: we would scope and price the engineering a submission needs, and the certificate itself is theirs to certify rather than ours to schedule. A vendor who answers this question with a delivery date is describing something they do not control.

Our turnover is well under fifty thousand euros. Does that let us use you for invoicing?

Not by itself, and this is the most consequential misunderstanding on the page. The turnover figure is one of several conditions rather than the only one — 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 keeping organised accounts. 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 right answer; the alternatives left open below the threshold are paper from an authorised printer or issuing on the authority's own portal. Whether your business meets any of the conditions is a determination that belongs to your accountant, and we are not going to make it for you.

Can we use AWRA OpsHub in Portugal at all?

Yes, and the distinction is worth being precise about because both the optimistic and the pessimistic readings of this page are wrong. What is ruled out is the issuing of fiscal sales documents by a business the certification 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 regulated by that rule and work here as they work anywhere. The common shape is a Portuguese company whose invoicing stays in a certified package and whose operations move to us — and if that is you, the section below the fold is your page rather than the one above it.

You already put a tax authority QR code on invoices. How far off is the Portuguese one?

The rendering is close and the rendering is not the problem. Our invoice template already produces an authority QR in vector from a stored payload, beside a receipt number, a receipt signature and a filing timestamp that authority returned — that is Kenya, it is live, and the same components would draw a Portuguese code. What sits behind it is the actual work: a document series registered in advance, the code the authority returns for it, the prescribed payload, and the record-integrity properties the requirements test for. On the roadmap, and commissionable now, with the caveat that governs this whole page — completing that engineering is the start of an application rather than the end of one.

Can you produce the monthly file of billing records?

No. We produce no ledger export in any prescribed schema, and it is worth knowing how far off that is rather than just hearing no: our invoice export is seven columns of header data — reference, customer, date, total, balance and status — with no document lines, no rates and no tax codes. A billing ledger file is a different sort of object, covering documents, lines, customers, products and the tax table together. On the roadmap, and commissionable now, and of everything on this page it is the piece that would most improve the product outside Portugal too, because an export that carries lines and tax codes is what every accountant on every market page has actually been asking for.

Does our invoice number count as a document series?

No, and the gap is narrower and more interesting than it sounds. Our sales documents already draw their reference from a locked counter held per organization and per year, which is structurally what a series is. Two things are missing: the registration step that gets a code back from the authority, and the ability to run more than one series at a time. A third thing is a defect rather than a gap, and we would rather say it here: for invoices, credit notes, purchase orders and point-of-sale documents that counter is reconciled against a number that is unique across the entire platform rather than within your organization, so your sequence is not private to you and can skip without explanation. On the roadmap, and commissionable now — and that last part we would treat as a correction rather than a feature.

We are in Madeira. Is the rate right?

No — not out of the box, and you should change it before your first invoice. Our country profile carries the mainland figure, because it holds one rate per country and Portugal has three: the mainland, Madeira and the Azores each sit at a different level under the same article of the tax code. Nothing in the product knows which archipelago you are in, so it will apply the mainland rate until somebody edits the organization default, which takes about a minute. On the roadmap, and commissionable now: a country profile that can carry regional variants rather than one figure. Until then this is the single most likely way for this page to cost a reader money, which is why it appears three times on it.

Are your records non-alterable?

No, and we are being careful with this answer rather than modest. What is true and checkable: the product refuses to delete an issued invoice, and corrections run through cancellation or a credit note. What we will not do is convert that into a claim of non-alterability in the sense the certification requirements mean, because those requirements test properties of a system's record-keeping that we have never been assessed against, by anybody. This is a boundary rather than a backlog in its present form: the underlying engineering is scopeable, and a vendor asserting the outcome without an assessment behind it is telling you something they do not know.

Does an English-only interface work in Portugal?

Adequately for most teams and less well than in the Netherlands, which is the honest comparison. Portuguese business runs in English at the professional level and a finance or operations lead in Lisbon or Porto will not be slowed by it, but a warehouse floor, a maintenance crew or a field team is a different proposition, and those are exactly the users the operations half of this product is for. An English interface also does not produce a Portuguese-language document, and we do not produce one. On the roadmap, and commissionable now, and larger than it sounds, because it is every screen rather than a document template. If it is a procurement requirement rather than a preference, say so in the first conversation.

Can our data be held in the EU?

Two halves with different answers. On the roadmap, and commissionable now: an EU-region deployment is a real thing we would do, priced as a piece of work, because hosting region is a property of a deployment. A boundary rather than a backlog: it is not a per-organization setting and we will not describe it as one. There is no column, no flag and no switch that puts one organization in a different region from its neighbours, and the sub-processor register is a single list applying to everybody on a deployment. Our compliance matrix claimed otherwise until 5 August 2026; it now says this, with the correction marked.

Do you have Portuguese customers we can speak to?

No. A boundary rather than a backlog, because it is a fact rather than a feature: 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, and we would rather write the sentence than have you find out in month three. What we can show is the same class of work done elsewhere and the specification discipline behind it.

Further reading

The corpus behind this page

Accounting Insights

Sometimes the Regulated Thing Is the Software, Not the Invoice

Most tax rules describe a document. A few describe the program that issues it — accredited by the authority, listed on a public register, issuing from series registered in advance. That is a different kind of requirement, and no feature comparison can answer it.

Read
Accounting Insights

A Number That Is Not Your Own: What a Document Series Actually Is

Every system numbers its invoices sequentially and almost none of them can tell you whether the sequence belongs to you. Ours could not: for five document types the counter was reconciled against a number unique across the whole platform. We published that, then fixed it the next day, and both dates are on the page.

Read
Implementation & Rollout

Buying Operations Software in Portugal: A Straight Guide

One exclusion that is not like the others, and it goes first: we are not a certified invoicing program. Then the four that are ordinary, the check to run before you shortlist anybody, and the questions worth asking every vendor including us.

Read
Point of Sale

Three Shapes a Receipt Rule Can Take

A rule about receipts can be an integration, an architecture or an accreditation, and only the first is something you can shortlist for. The third is answered by a public register in about two minutes and almost nobody evaluating from outside the country knows to look. Our own audit against one European regime, including the six days this site contradicted itself.

Read
Implementation & Rollout

Buying Operations Software in the Netherlands: A Straight Guide

Five exclusions at the top rather than the bottom: no VAT numbers on the invoice, no VIES check, no reverse-charge treatment, no Belastingdienst connection, no Dutch reference customer. Then the questions worth asking everybody else.

Read
Accounting Insights

Three Reasons for a Zero, and Two Places to Put Them

Zero-rated, exempt and reverse-charged all print as nothing and mean different things for who accounts for the tax and what can be recovered. Our schema has two values for the three, no value for the third — and charges the standard rate if you invent one.

Read

Next step

The Portuguese conversation starts with a question no demonstration answers.

Search the register, decide where your fiscal documents get issued from, and then talk to us about everything else — which, on this product, is most of it. If the operations half is what you actually need, none of the page above is your problem.

Talk to us about Portugal Read the Netherlands page, which argues the document half