ERPNext Accounting in Portugal

Where the Portuguese ledger should live

Under Portuguese invoicing rules, approval belongs to one producer's program in one version. Because ERPNext's code is open for anyone to change, an instance you host yourself carries no such approval by default. Whether any ERPNext app or hosted service may issue Portuguese invoices is a claim the publisher should put in writing for your contabilista to review, and rechecked after every upgrade. Until that is confirmed, I treat it as unconfirmed.

That leaves three ledger designs to compare:

1. ERPNext as ledger, separate issuing program: an approved Portuguese program issues invoices; each document flows into ERPNext as a posted record with its official references. Operations and accounting stay together in ERPNext.
2. Contabilista's software as ledger: ERPNext runs stock, purchasing and projects, and summarized data goes to the accountant, who keeps the statutory books.
3. ERPNext issues invoices through an app: only if the publisher confirms in writing exactly which product, version, hosting and level of modification its position covers, and your accountant accepts it.

Each design changes who produces the SAF-T files, who closes the month and how audits run. I put the comparison on paper so management chooses knowingly. The architecture options are introduced on ERPNext in Portugal; this page follows the ledger consequences. I do not give tax advice and do not declare any setup compliant.

SNC chart and IVA templates, including the islands

Portuguese accounts follow the SNC, the national accounting standard, with a chart structure every contabilista knows. Ask Frappe or the partner whether a maintained Portuguese chart ships with your release. In any case I build or adjust the chart with your accountant, keep statutory accounts recognizable, and move management detail into cost centers and accounting dimensions.

IVA templates then need to reflect Portuguese practice:

• Regional rates: the Azores and Madeira apply their own IVA rates, so customers or deliveries there need separate templates selected by tax category or address.
• Exemptions: exempt operations must state the legal reason on the document, which matters most when ERPNext issues anything a customer sees.
• Reverse charge: certain domestic sectors and most intra-community purchases shift the tax to the buyer, as your accountant confirms.
• Intra-community and exports: EU business customers with valid VAT numbers and sales outside the EU handled through tax categories.
• Deductibility: partially deductible costs, such as some vehicle expenses, posted so the non-deductible share is visible.

If invoices come from a separate program, its tax codes must map one to one onto ERPNext templates, or the IVA reports in the two systems will disagree. I build that mapping table and test it on every tax case the contabilista lists. General features are on ERPNext Accounting.

Bringing invoices into ERPNext without double counting

In the first design, the issuing program and ERPNext must agree on every sales document. The risk is two numbering sequences, two versions of the truth and a month-end spent reconciling them. I specify the link around a few rules:

• One issuer: only the approved program assigns invoice series and numbers. ERPNext stores them, along with the ATCUD code, as references on the imported record and never generates its own customer-facing number.
• A defined trigger: an approved order or delivery in ERPNext requests the invoice; the program issues it and returns the result.
• Credit notes and cancellations: handled in the program first, then mirrored in ERPNext, each with its own test case.
• Payments in one place: receipts recorded where the receivables ledger lives, with any receipt documents your accountant requires issued by the program.
• Daily control: a report comparing totals by series between the program and ERPNext, with failed transfers in a queue that has a named owner.

Communication of invoice data to the tax authority and the invoicing SAF-T file normally come from the program that issued the documents. The accounting SAF-T file comes from whichever system holds the ledger; ERPNext does not, to my knowledge, produce it from the core product, so an app or custom development would be needed and must be confirmed with Frappe or the partner. My system integration service covers the specification method.

Banks, payment references and withholding

Portuguese finance teams reconcile statements from domestic banks, collect by SEPA direct debit and often receive customer payments through payment references issued via a payment provider. ERPNext's bank reconciliation tool works on imported statements or bank integrations. Which statement formats your version reads cleanly, and whether some converter or add-on must sit in between, is worth checking with sample files from each bank before configuration.

The items I test with your finance lead:

• Statement import and matching rules for invoice references, grouped receipts and bank charges.
• SEPA collections: mandate data on customers, the remittance file and returned debits posted back to receivables.
• Payment references: if you use a provider for references customers pay at ATMs or online, how payment confirmations reach ERPNext, through an existing connector or custom work.
• Withholding: invoices from independent workers and certain services may carry withholding, which ERPNext handles through withholding categories or deduction lines; your accountant confirms the cases and the returns that follow.
• Foreign currency: exporters and service firms billing clients abroad in US dollars or pounds need revaluation rules agreed with the accountant.

For technology and service companies billing foreign group entities, intercompany charges and their documentation also need design; the multi-currency page covers the general approach.

Upgrades, ownership and cases where ERPNext should not hold the books

In Portugal the integration between ERPNext and the issuing program is the most fragile part of the setup. Every ERPNext upgrade, every program update and every change to the tax authority's technical rules is a reason to retest it. Whether you run on Frappe Cloud, a European cloud you manage or a partner's hosting, I write down who applies upgrades, who retests the link and who answers when invoices stop flowing.

Habits I build into the plan:

• Try every upgrade first on a cloned database, then replay a month already closed: same totals by series, same IVA figures, same balances.
• Avoid upgrades close to filing dates your accountant flags.
• Put any bespoke logic in its own app, leaving the core untouched.
• Document the integration so another developer could take it over.

ERPNext Accounting is the wrong choice in Portugal when the contabilista keeps the books in Portuguese software and the integration would only duplicate them, when the board wants a single supplier answerable for both operations and invoicing, or when nobody can own the integration. A platform whose vendor or partner confirms Portuguese status for your exact setup, such as Odoo Accounting in Portugal, may then be simpler. I resell no software or hosting. The Portugal ERP consultant page explains remote delivery.