Law 256 of 2021 Explained: Mandatory Electronic Invoicing in Panama

Law 256 of 2021 transformed Panama's invoicing system. Since its entry into force (and gradual implementation through Executive Decree 367 and subsequent resolutions), electronic invoicing ceased to be optional and became mandatory — first for large taxpayers, then cascading across the rest of the formal sector. If your company still issues paper invoices or uses legacy systems without transmission to the DGI, this article is for you.

Important: this article is educational. Panama's electronic invoicing regulations are complex and are updated through periodic resolutions. Before making operational decisions, verify with your accountant, tax advisor, or directly with the DGI.

What does Law 256 establish?

In essence, Law 256 of 2021 establishes:

• Mandatory electronic invoicing for all individuals and legal entities conducting commercial activities in Panama.
• Each electronic invoice must include a CUFE (Unique Electronic Invoice Code) generated by an authorized PAC.
• Invoices must be transmitted in real time to the DGI through the PAC.
• The issuer must digitally archive electronic documents for the legal retention period (typically 5 years).
• Electronic invoices have full legal validity for accounting, tax, and commercial purposes.

The law is complemented by Executive Decree 367, which regulates implementation, and Resolution 201-7136, which defines the requirements for authorized PACs.

The phased calendar

Rather than an abrupt "switch," implementation was designed in waves by size and sector:

• Phase 1: large taxpayers and specific sectors (hydrocarbons, telecommunications, banking).
• Subsequent phases: medium taxpayers, then small taxpayers, per the calendar established by the DGI through resolution.
• Permanent exception: companies with annual revenues below B/.36,000 may continue using the DGI free invoicing tool instead of a PAC.

Implication: if your company exceeds the B/.36,000 annual threshold and has not yet migrated to a PAC, migration is not optional — it is legally and operationally urgent.

The actors in the system

Panama's electronic invoicing system has four main actors:

1. Issuer (the company)

Generates the invoice from their system (ERP, accounting software, POS).

2. PAC — Authorized Qualified Provider

A company certified by the DGI under Resolution 201-7136. The PAC validates the invoice, applies the CUFE, adds a digital signature, and transmits it to the DGI in real time. The main PACs in Panama are:

• WebPOS — specialized in the local market with dedicated support.
• Alanube — API-first platform, high availability, regional presence.
• The Factory HKA — enterprise platform used throughout Latin America.

For a detailed comparison, see our authorized PAC guide.

3. DGI — General Revenue Directorate

Receives the validated invoice from the PAC, registers it in its system, and makes it available to the recipient. Maintains fiscal control of transactions.

4. Recipient (customer)

Can look up the invoice on the DGI portal using the CUFE and download it. If they are a taxpayer, they can credit it as a tax credit on their Form 430.

The electronic invoice flow

1. Issuer generates the invoice from their ERP, entering customer data, products/services, ITBMS, and withholdings if applicable.
2. System digitally signs the invoice with the issuer's digital certificate.
3. PAC receives the invoice, validates it syntactically and semantically, applies the CUFE and the PAC's own signature.
4. PAC transmits to the DGI in real time.
5. DGI registers the invoice in its system.
6. PAC returns the CUFE and an acceptance receipt to the issuer.
7. Issuer delivers the electronic invoice with CUFE to the customer (PDF, XML, or both depending on the agreed format).

All of this typically occurs in less than 5 seconds from when the issuer clicks "Issue invoice."

What happens if the transmission fails?

The regulations include contingency scenarios for when the PAC or DGI are temporarily unavailable:

• The issuer can generate the invoice with a provisional CUFE (specific format for contingency situations).
• When connectivity is restored, the PAC retransmits pending invoices.
• The invoice already delivered to the customer remains valid; only the moment of DGI confirmation changes.

It is the issuer's responsibility (and their system's) to correctly implement this contingency flow.

Penalties for non-compliance

Non-compliance with Law 256 can result in:

• Fines for issuing invoices without a CUFE or outside the system.
• Surcharges on ITBMS not correctly invoiced.
• Suspension of invoicing privileges (in extreme cases).
• Inability to obtain a tax clearance certificate from the DGI, which blocks banking transactions, public contracts, and other operations.

Fines escalate based on repeat violations and the invoiced amount.

What you need to comply

To issue valid electronic invoices under Law 256, your company needs:

1. A contracted PAC (WebPOS, Alanube, or The Factory HKA, or whichever the DGI designates).
2. A valid digital certificate issued by a recognized certification authority in Panama. Typically renewed every 1-2 years.
3. A billing system integrated with the PAC: this could be your ERP (like cifraHQ), POS software, or a dedicated invoicing tool.
4. Internal processes ensuring that every taxable sale generates an electronic invoice with a CUFE.
5. Digital archiving of issued and received invoices for the legal retention period.

The IFRS dimension

Electronic invoicing also impacts accounting under IFRS:

• Each electronic invoice with a CUFE becomes the documentary support for the transaction.
• The accounting entry must reflect the invoice in the correct period.
• Reconciliation between the ITBMS declaration (Form 430) and accounting records is straightforward when everything is integrated in an ERP.

Companies with separate invoicing and accounting systems spend significant time reconciling — an integrated ERP eliminates that work.

Common mistakes with Law 256

1. Assuming the "free invoicing tool" covers any company: it only applies below the B/.36,000 annual threshold (see our DGI free invoicing tool migration guide).
2. Not migrating after exceeding the threshold: compliance is mandatory from the moment the threshold is exceeded, not at year-end.
3. Using pre-printed paper invoices as "backup": they have no legal validity under Law 256 for taxable transactions.
4. Not storing the CUFE in the accounting system: the CUFE is the unique reference enabling traceability in an audit.
5. Underestimating the implementation timeline: PAC integration + digital certificate + sandbox testing typically takes 2-4 weeks.

How cifraHQ helps with Law 256 compliance

cifraHQ integrates natively with all three main authorized PACs (WebPOS, Alanube, The Factory HKA), automates CUFE generation on every invoice, transmits in real time to the DGI without manual intervention, handles contingency scenarios automatically, digitally archives all invoices with their CUFE for the legal retention period, and produces the consolidated reports for the monthly Form 430. The result: electronic invoicing, IFRS accounting, payroll, and tax declarations in a single platform.

Ready to migrate to electronic invoicing with a complete ERP? Request a demo or read our DGI free invoicing tool to PAC migration guide.

Official resources

• Dirección General de Ingresos (DGI)
• Law 256 of 2021 — official text
• Executive Decree 367 — implementing regulation

This article is educational and does not constitute legal advice. Electronic invoicing regulations are updated periodically; verify with your tax advisor before making operational decisions.