Skip to content

Contact Info

Portugal

Knowing which system really issues your documents

What does an ERP audit cover in Portugal?

An ERP audit in Portugal examines a running system independently, separate from the statutory audit and the accountant's work. I map every program that issues documents, prepare questions for vendors about the invoicing software rules, check series and ATCUD on layouts, compare SAF-T test exports with the ledger, trace recharges, transport documents and the payroll file, and rank the findings. It is delivered remotely.

Last reviewed by Vikas Saroj

A Portuguese company can believe its invoicing is under control and still have documents leaving from places nobody mapped: a point of sale at one site, a hotel system at another, credit notes typed in a spreadsheet, a pro-forma sent from the CRM. Each one touches the rules on invoicing software, document series and the SAF-T file in its own way.

I run independent ERP audits remotely for Portuguese service centers, exporters, hospitality groups and distributors. The scope is systems, controls and data flows. It is not a financial audit, and your statutory auditor, contabilista certificado and tax advisor keep their roles in full. Points with tax implications are handed to them as questions.

No software vendor or implementer pays me anything, so the findings are not a route to a new product. The engagement runs in English; Portuguese documents, layouts and screens are reviewed together with someone from your finance or operations team.

ERPNext desk showing the Profit and Loss Statement report with income, expense and net profit totals and a quarterly trend chart
  • Map of where documents are issued
  • Program and version questions
  • Series and ATCUD consistency
  • SAF-T export against the ledger
  • Recharges and transport documents
  • Access, licenses and reports
Audit Areas

What a Portuguese ERP audit covers

Every finding carries its evidence, a responsible person and a proposed remedy, and tax points are framed for your accountant.

Document Issuance Map

Every system and person that creates invoices, credit notes, receipts or transport documents, listed with the program and version used, so you can see whether any document leaves outside the intended route.

Vendor Status Questions

Written questions for each vendor or implementer about how the exact version, edition and customizations you run relate to the invoicing software rules. I record their answers; I do not give a compliance view.

Series and ATCUD Review

Document series by site and type, how they were communicated, whether codes appear on every printed and PDF layout, and whether numbering is continuous after updates or template changes.

SAF-T and Ledger Checks

Test exports compared with the ledger and subledgers for sample periods, with master data gaps such as missing tax numbers or country codes listed for correction. Your accountant validates the file itself.

Recharges and Movements

Intercompany recharges from service centers, markups and allocation keys, plus transport documents for goods leaving warehouses or sites, reviewed for manual steps and gaps between systems.

Access and Licenses

Who can create series, edit layouts, post manual journals and release payments, dormant and shared accounts, and licenses or seats that are paid for but not used.

How I Work

A focused review in three parts

Map

Find every source of documents

01
Request an Assessment
  • Management concerns captured
  • Sites and systems listed
  • Programs and versions noted
  • Viewing access requested

Verify

Compare what systems produce

02
Discuss Your Project
  • Series and layouts sampled
  • Test exports reconciled
  • Recharges traced end to end
  • Rights and users exported

Report

Ranked findings and open questions

03
Talk About Next Steps
  • Findings checked with owners
  • Vendor questions issued
  • Accountant question list
  • Readout and next steps

A system audit, separate from the statutory auditor and the accountant

Portuguese companies already work with a contabilista certificado and, where required, a statutory auditor, so it helps to say clearly what this review is. An ERP audit examines the software landscape: how it is configured, which controls it enforces, how data moves to the accountant, the tax authority and other systems, and whether management reports can be trusted. It gives no opinion on the financial statements and no tax advice.

The moments when a Portuguese business tends to need it are recognizable:

  • A foreign group has bought the company and wants to understand its systems before integrating them.
  • A service center has grown faster than its recharging process and finance spends days on allocations each month.
  • A hotel or restaurant group has added sites, each with its own point of sale or property system.
  • The implementer who built the setup is no longer involved and nobody has a full picture.

The work combines interviews with finance, operations and IT, sessions where staff show real tasks on screen, and viewing access to configuration and transactions. Draft findings are checked with the people responsible before they are written into the report. The core method is the one behind my ERP health check; what follows is what Portuguese rules and practice add to it.

Where are documents issued, and by which program?

Portugal expects invoices and certain other documents to come from invoicing software that meets the tax authority's requirements, and that status is tied to a specific product and version. An audit therefore starts with a plain inventory: every place a document can be produced.

SourceWhat I check
Main ERPProgram, edition and version in use, customizations to invoicing, update history
Point of sale or property systemWhich documents it issues itself and how they reach the ledger
CRM or quoting toolWhether anything it sends could be read as an invoice rather than a quotation
Spreadsheets or word processorAny credit notes, receipts or debit notes produced outside a system
Warehouse or delivery appTransport documents for goods movements

For each program I prepare written questions for the vendor or implementer: does their statement about the invoicing rules cover the exact version and edition you run, and have any customizations or extensions changed how documents are created? I record what they say. I do not describe any product as compliant, and I do not judge the answers; your contabilista certificado and tax advisor assess what the findings mean for you.

This inventory alone often settles arguments, because it replaces assumptions with a single page everyone can read.

Series, ATCUD and the SAF-T export, checked for consistency

Document series and the ATCUD code printed on each document are where small configuration slips become visible to customers and inspectors. I sample series by site and document type and check that:

  • each series in use was communicated before its first document, as your accountant expects;
  • the code and QR element appear on every layout, including PDF copies, emailed documents and reprints;
  • numbering stays continuous after software updates, template changes or a move between sites;
  • cancelled documents follow the procedure your accountant has set, rather than being deleted.

The SAF-T export gets a separate check. A file that the system produces without errors can still be incomplete. I generate test exports for sample periods and compare their totals with the ledger and subledgers, then trace differences to their cause: customers without tax numbers, wrong country codes, manual journals bypassing tax logic, or documents issued in another system and posted only as a summary. Your accountant validates the file with their own tools and decides on any correction.

None of this asks me to interpret the law. The audit shows whether the system behaves consistently with the rules your advisors apply, and where it does not. For how the same checks fit into a new implementation, see my ERP implementation page for Portugal.

Recharges, transport documents and the payroll file

Nearshore service centers in Portugal live on recharges. Hours or costs are captured, allocated to sister companies with agreed keys and markups, and invoiced each period. When this runs partly in spreadsheets, finance spends the first days of every month rebuilding it. I trace a sample recharge from time capture to intercompany invoice and to the counterparty's acknowledgment, noting each manual step and every point where the allocation key could be changed without trace. Transfer pricing itself is a matter for your advisors.

Companies moving goods need a different check. Transport documents must accompany certain movements, and their creation and communication should follow the warehouse process rather than depend on someone remembering. I review how documents are produced for deliveries, transfers between sites and returns, and whether the warehouse can work when a connection fails.

Payroll usually runs at the accountant's office or with a payroll bureau. I look at the monthly file they send: the route it takes into the ledger, the accounts and cost centers it lands on, who reconciles it to the payroll summary and who can see the underlying salary data. Contribution and withholding questions stay with the provider.

Findings here often lead to multi-company setup work or a tidier integration, rather than a new system.

Access, licenses, reports and the written findings

User rights get special attention in Portugal because a few permissions carry compliance weight. I check who can create or change document series, edit invoice layouts, cancel documents and post manual journals on tax accounts, alongside the usual pairs of duties that should be separated: supplier bank details versus payment release, credit limits versus sales approval. Dormant accounts, departed staff and implementer logins left open are listed too. Personal data of employees, guests and customers is checked so each role sees only what it needs; your advisor interprets the GDPR obligations.

Licenses are compared with actual use: users billed but absent for months, modules in the subscription that nobody opens, seats shared between several people.

Reports come last. I ask managers which figures they trust and which they rebuild in spreadsheets, then trace the distrusted ones to their cause.

The report contains a summary for management, findings ranked by business risk with evidence, the document issuance map, the vendor question list, a separate list for your contabilista certificado and a proposed order of work. I present it remotely in a slot that suits the Portuguese working day; travel happens only by arrangement. Should the findings reveal a deeper problem, my Portuguese ERP rescue service follows on, and ERP optimization handles lighter fixes. See the Portugal hub and my ERP consultant page for Portugal for the rest.

Not sure where to start?

Tell me about your business and current systems. I’ll suggest the most sensible first step.

Book a Consultation
Related

Related Services

  • ERP Health Check
  • ERP Optimization
  • ERP for Multi-Company Operations
  • Independent ERP Second Opinion
  • ERPNext Consulting
Portugal

More for Portugal Businesses

  • Portugal overview
  • ERP Consultant
  • Freelance ERP Consultant
  • ERP Business Analyst
  • ERP Requirements Consultant
  • ERP Selection Consultant
  • ERP Implementation Consultant
  • ERP Rescue Consultant
  • CRM Consultant
  • System Integration Consultant
Other Markets

ERP Audit Consultant Elsewhere

  • USA
  • UK
  • UAE
  • Saudi Arabia
  • Qatar
  • Oman
  • Kuwait
  • Bahrain

Not sure which ERP you need?

Do not choose software first.

Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.

  • Independent ERP advice before you invest - I do not resell software
  • Work directly with Vikas - no account managers or junior handoffs
  • Business analysis before software implementation
  • One consultant who understands both your business and the technology
FAQ

Questions About ERP Audit Portugal

No. That status attaches to a particular product and release and is a matter for the vendor and the tax authority, with your accountant advising you. The audit records which programs and versions issue your documents, which customizations exist, and the written questions to put to each vendor. You then have a factual basis for that conversation.

No. A statutory auditor gives an opinion on the financial statements. An ERP audit reviews the software, its controls and its data flows, and offers neither assurance on the accounts nor tax advice. Some findings, such as editable layouts or unreconciled exports, may still be useful to your auditor and accountant.

It covers how they connect to the ERP and which documents they issue, because that affects series, SAF-T and the ledger. I do not audit those systems in depth. If one of them turns out to be the source of a problem, the report says so and suggests who should look further.

Often yes, because recharging is where manual work and risk accumulate. The audit traces costs from capture to intercompany invoice, checks allocation keys and access rights, and reviews how documents and SAF-T exports handle group customers. The result is a clear list of fixes, many of them in configuration rather than new software.

Still have questions? Let’s talk them through.

Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.

Book a Consultation
Vikas Saroj seated at a meeting table with a laptop and notebook
Working Model Remote · Worldwide
Email Address hello@vikassaroj.com
Book a Consultation

Let’s Discuss Your ERP Audit Portugal Project

Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.

Chat on WhatsApp