PAC Panama: playbook to migrate off CFEG in 2026

60-second summary

As of January 1, 2026, Panama's DGI shut down the Free Invoicer (CFEG) for every taxpayer billing more than USD 36,000 a year or issuing more than 100 documents a month. That forces 18,000+ Panamanian taxpayers to migrate to a PAC this year. Fines start at USD 500 and reach USD 10,000 for repeat offenders. This playbook ships the migration in 7 days without stopping operations.

• CFEG (DGI Free Invoicer) is now closed for taxpayers above USD 36,000/year or 100 docs/month — exceeding either threshold triggers the obligation.
• PAC (Qualified Authorized Provider) is the only legal channel for almost every Panamanian SMB starting in 2026.
• Formal deadline: January 1, 2026. DGI is granting an informal grace window through mid-year, but enforcement is already active.
• Fines: USD 500 first offense, up to USD 10,000 on repeat (Executive Decree 766/2020 plus follow-up DGI resolutions).
• Affected universe: 18,000+ taxpayers — 30 to 40 % of Panama's active e-invoicing base.
• Realistic timeline for SMBs running Odoo + l10n_pa: 5 to 7 business days with proper prep.

Why the DGI is shutting CFEG in 2026

Panama rolled out its Electronic Invoicing System (SFE) through Executive Decree 766 of December 29, 2020. The scheme is standard for the region: the state receives every transaction's structured data in real time through one of two channels.

• DGI Free Invoicer (CFEG, formerly FGD): a free web portal aimed at micro-businesses.
• PAC (Qualified Authorized Provider): a certified private provider that handles the full outbound document flow.

CFEG started as a temporary tool for the smallest taxpayers. By 2024–2025 it had spun out of control: tens of thousands of taxpayers used CFEG as their primary infrastructure even at hundreds of thousands of dollars in annual revenue. The portal saturated, validation latency climbed, and the DGI lost grip on data quality.

In mid-2025 the DGI published the resolution that caps CFEG eligibility to two simultaneous criteria: annual revenue ≤ USD 36,000 and ≤ 100 documents/month. Exceed either one in any month and you lose CFEG access and must migrate to a PAC.

Per estimates from the Chamber of Commerce, Industries and Agriculture of Panama (CCIAP) and independent market analysts, over 18,000 taxpayers fall under the migration obligation during 2026. It's LATAM's most concrete compliance window of the year: clear dates, clear amounts, clear deadline.

For comparison: the equivalent SUNAT reform in Peru reached about 25 % of taxpayers; DIAN's in Colombia hit about 15 %. Panama is moving 30 to 40 % of its base in a single calendar year. We unpack the full regulatory picture in DGI PAC migration — the Panama compliance pillar.

What a PAC actually does — and what it doesn't

What a PAC does:

1. Receives the structured document (XML on the DGI schema) from the client's ERP or POS via REST API.
2. Cryptographically signs the document with its own certificate plus the taxpayer's digital certificate.
3. Transmits the document to the DGI in real time.
4. Returns the CUFE (Unique Electronic Invoice Code) — the validated document's unique identifier.
5. Archives documents for 5+ years (compliance archive).
6. Provides a dashboard for lookup, cancellation, and credit notes.

What a PAC does NOT do: it doesn't determine your tax base, it doesn't auto-correct data errors, and it doesn't replace your accounting system. The PAC is only the transmission channel to the DGI; the rest is on your ERP and your accountant.

The 7-day playbook with Odoo and l10n_pa

This plan assumes you already run Odoo Enterprise or Community, your accounting team understands e-invoicing, and your RUC is active. Starting from Excel or a legacy system without an API adds 30 to 60 days before this playbook even kicks off.

#1. Day 1 — audit

Compare the last 12 months of revenue against the USD 36,000 threshold. Compute average documents per month. List every RUC you issue under (one RUC equals one separate PAC contract). Identify your current channel: CFEG, custom ERP, manual XML. Close the audit with a 2-page document signed by the CFO.

#2. Day 2 — choose your PAC

The DGI certified roughly 10 PACs for 2026. Selection criteria:

• API quality: RESTful, real sandbox, idempotency built in, automatic retry for transient failures.
• Pricing: per document (USD 0.05 to 0.15) or subscription (USD 50 to 800/month depending on volume).
• SLA: uptime ≥ 99.9 %, submission latency under 3 seconds.
• Ready integrations: Odoo connector, SAP B1, NetSuite — or at minimum a REST API for custom builds.
• Support: live Spanish-speaking team, response under 2 hours.

#3. Day 3 — contract and onboarding

Sign the contract with the PAC, receive API credentials, upload your company's digital certificate (issued by the DGI), and get sandbox access. Most PACs deliver onboarding documented as a Postman collection or OpenAPI spec.

#4. Day 4 — Odoo configuration

Install l10n_pa (Odoo Community Association — community-maintained, not Odoo SA official). Add the PAC adapter: the provider's official module when it exists, or custom REST when it doesn't. Configure the mapping: document types (Invoice, Credit Note, Debit Note), TaxIDs (ITBMS 7 %, exempt, withholding), and calculation rules. This is the stage where a prior Odoo audit saves 1 to 3 days of rework.

#5. Day 5 — sandbox testing

Issue 10 to 15 sandbox documents: standard invoice, exempt, multi-line, multi-tax, credit note, cancellation within 24 hours. Verify the CUFE comes back, the document appears in the PAC dashboard, and any failure is reproducible. Log every failed case with its DGI error code.

#6. Day 6 — go-live

Morning: final sync of any pending CFEG documents. At 2:00 PM: switch Odoo to production PAC. Issue 2 or 3 production documents to small clients as a real-world test. Watch the error stream for 4 hours with the accounting team and a developer on standby.

#7. Day 7 + 30 — stabilization

Daily reconciliation: documents issued vs accepted by the DGI. Weekly review of error patterns. On day 30 close with the monthly accounting audit and correct any drift. When the migration goes right, monthly closing ships earlier than the previous month — clean CUFE data eliminates manual rework.

When the playbook works — and when it doesn't

Not every profile fits in 7 days. The variance depends on ERP state, number of RUCs, and tax regime.

If your case is one of the last three rows, don't improvise. A planned Odoo implementation for LATAM SMBs pays for itself in 6 months against the cost of fines plus paused operations.

The 5 mistakes that wreck migrations

Mistake 1: "the DGI will push the deadline like SUNAT does in Peru." The DGI in Panama has historically respected its tax deadlines. Decree 766/2020 was postponed several times during implementation between 2020 and 2025, but it was never canceled. January 2026 is the close of a 5-year transition. Betting on another delay costs USD 500 to 10,000 plus disrupted operations.

Mistake 2: picking the PAC on price, not API quality. The cheapest PAC (USD 0.03/document versus the average of 0.08) usually ships the worst API: no idempotency, weak retry logic, email-only support. When you run 5,000 docs/month and the API drops for 30 minutes, you lose documents and reprocess by hand. Saving USD 250/month converts into USD 2,000 of operational loss plus accounting team overtime.

Mistake 3: skipping edge cases in testing. 70 % of companies test only "normal invoices with no surprises." Production includes credit notes, 24-hour cancellations, multi-currency (USD primary + EUR for exports), exempt transactions, ITBMS reverse charge for Free Zone clients. One edge case breaks 2 to 3 weeks in and tanks monthly closing — 4 to 8 hours of reclassification work for the team.

Mistake 4: not training accounting on PAC error codes. The PAC returns specific DGI codes: DOC-001 missing tax base, DOC-014 invalid customer RUC, DOC-022 duplicate document number. If the accounting team can't read them, documents stack up in the queue. Minimum training: 2 hours plus a one-page error code cheat sheet.

Mistake 5: forgetting the certificate renewal. Yes, it's worth repeating: the digital certificate expires in 12–24 months, renewal takes 5–10 business days, and during that window the PAC rejects 100 % of your documents. It's the #1 cause of post-go-live production incidents.

Anonymous case: logistics operator in Panama City

Context: a Panama City logistics operator serving Canal-related clients. Annual revenue ~USD 2.3M, ~3,500 documents/month. Through 2025 it ran CFEG plus a custom Excel-based billing process.

What they did:

• 2-day audit: revenue overshot the threshold by 64×, document volume by 35× — well past any DGI tolerance zone.
• Picked their PAC on API quality (not the cheapest, but the best Odoo connector by sandbox testing).
• In parallel they migrated from Excel to Odoo Community + l10n_pa + a custom PAC adapter.
• 4-day testing window: multi-currency USD/EUR, ITBMS, exempt for Free Zone clients.
• Go-live across one weekend: Friday final sync, Monday production.

Result: first month at 99.4 % issuance success rate (vs the industry average of ~85 % for fresh migrations). Monthly close shipped 2 days earlier than usual thanks to clean CUFE data. Zero DGI fines in the first 90 days.

Cost: USD 12,000 total (Odoo setup + PAC integration + 6 days of consulting). PAC monthly cost: USD 180. ROI inside 3 months — the company now saves 12 to 16 hours/month of accounting reconciliation and avoided at least USD 1,500 in potential fines.

Monthly closing ships earlier than it did on CFEG. Data lands clean from day one — we used to burn 6 hours rebuilding what the portal had broken.

Download the full migration checklist

The full PDF runs 25 pages: the 7 days step by step, sandbox testing protocols, the list of certified PACs for 2026, templates for accounting reconciliation, the error-code cheat sheet, and contract language for PAC negotiation. Updated May 25, 2026.

Download the PAC Panama Migration Playbook (PDF) →

FAQ