Panama Government E-Invoicing Requirements for Suppliers

Since June 30, 2022, every supplier selling goods or services to a Panamanian government entity must issue electronic invoices through the SFEP (Sistema de Facturación Electrónica de Panamá). Resolution 201-5215 eliminated paper-based invoicing for state purchases, making electronic submission the sole accepted format for public-sector transactions.

If you already invoice commercial customers through SFEP, government sales do not require a separate system. They do, however, impose three additional requirements that standard B2B invoices do not carry:

1. Prior authorization (autorización previa). Before a government invoice reaches the buyer, it must be validated by a PAC (Proveedor Autorizado Certificado). This pre-delivery validation step has no equivalent in commercial invoicing.
2. Mandatory CPBS coding. Every line item must include a goods-and-services classification code in field C10, drawn from the CPBS (Codificación Panameña de Bienes y Servicios). Standard B2B invoices do not require this field.
3. Government receiver-type classification. Field B401 must identify the buyer as a government entity. Misclassifying the receiver type will cause the invoice to fail validation.

The volume of commerce flowing through Panama's public procurement framework makes these requirements relevant to a wide range of suppliers. The Panama Canal Authority alone represents annual purchases of as much as $250 million, spanning port and marine equipment, building materials, industrial equipment, and transportation materials.

The legislative foundation for this system is Law 256 of 2021, which modernized Panama's electronic invoicing framework and granted the DGI (Dirección General de Ingresos) authority to administer it. The DGI sets the technical standards, certifies PACs, and enforces compliance for both commercial and government invoicing.

This guide focuses specifically on what changes when your buyer is a public entity. For suppliers who need a broader overview of Panama's electronic invoicing obligations, see our coverage of Panama's SFEP electronic invoicing requirements. What follows here covers the Panama government e-invoicing requirements that apply specifically to public-sector sales: the prior authorization workflow, CPBS coding, and the full supplier process for submitting compliant invoices through SFEP.

---

Why Government Sales Require Prior Authorization

When you sell to a Panamanian government entity, the invoicing workflow changes in one critical way: your electronic invoice must be authorized before you can deliver it to the buyer. This is the prior authorization requirement (autorización previa), and it is the single biggest operational difference between government invoicing and standard commercial invoicing under Panama's SFEP.

Prior vs. Posterior Authorization

For sales to end consumers, Panama allows posterior authorization. You generate the invoice, deliver it to the buyer, and then submit it to a PAC (Proveedor Autorizado Certificado) for validation within the same calendar day. The buyer gets the invoice immediately; validation happens after the fact.

Government sales do not work this way. Prior authorization means:

1. You generate the electronic invoice.
2. You submit it to your PAC for validation.
3. The PAC validates the invoice and returns confirmation.
4. Only then do you deliver the authorized invoice to the government entity.

There is no grace period, no same-day window. The invoice cannot reach the government buyer until the PAC has validated it. Delivering an unauthorized invoice to a public entity is non-compliant.

Who Else Requires Prior Authorization

Government entities are not the only receiver type that triggers this requirement. Prior authorization applies to three receiver categories:

• Government entities (the focus of this article)
• Registered taxpayers (contribuyentes)
• Foreign entities

If your business sells across multiple receiver types, you are likely already using prior authorization for taxpayer-to-taxpayer transactions.

Why a PAC Relationship Is Non-Negotiable

Because prior authorization is mandatory for government invoices, you must work through a PAC. Panama's free government-provided billing tool (the Facturador Gratuito) does not support prior authorization for government sales. It is designed for low-volume businesses issuing invoices to end consumers under the posterior authorization model.

If you are currently using the Facturador Gratuito and win a government contract, you will need to establish a PAC relationship before you can issue your first compliant invoice. For suppliers evaluating their options, understanding the differences between choosing between Panama's free biller and a PAC provider is an essential first step.

The practical takeaway: factor PAC onboarding into your timeline when preparing to supply government entities. The authorization step adds processing time to every invoice, and your PAC's uptime and response speed become directly tied to how quickly you can bill your government customers.

---

Mandatory CPBS Coding and Receiver-Type Classification

Two invoice fields separate a government sale from a standard B2B transaction in Panama's electronic invoicing system: the B401 receiver-type classification and the C10 CPBS code. Getting either one wrong does not create a paperwork problem you can fix later. It triggers an immediate validation failure at the PAC level, and your invoice is rejected before it ever reaches the government buyer.

The B401 Receiver-Type Field

Every electronic invoice in Panama includes a receiver-type classification in field B401. This field tells the system what kind of entity is receiving the invoice. For commercial sales between private companies, B401 carries a standard taxpayer classification. When your buyer is a government entity, B401 must be set to the government receiver type.

This distinction matters beyond simple categorization. The B401 value is what determines which validation path your invoice follows at the PAC. A government receiver type triggers the prior-authorization validation workflow. If you submit an invoice to a government entity but leave B401 set to a standard commercial receiver type, one of two things happens: the invoice either routes to the wrong validation path entirely, or the PAC rejects it outright because the receiver classification conflicts with the entity's registered status in the DGI system.

B401 must be correct at the moment of submission. There is no post-submission correction path.

The C10 CPBS Code Requirement

Field C10 carries the CPBS classification, Panama's Codificación Panameña de Bienes y Servicios. On a standard B2B invoice, C10 is optional. Most suppliers leave it blank without consequence. On a government invoice, C10 becomes mandatory for every line item.

CPBS codes are built on the UNSPSC (United Nations Standard Products and Services Code) framework, adapted for Panama's classification needs. They organize goods and services into standardized segments and families. A segment represents a broad category (office equipment, professional services, construction materials), while a family narrows the classification within that segment. The DGI publishes the applicable CPBS classification tables, and suppliers familiar with UNSPSC coding can use their existing mappings as a starting point.

You need to map each product or service you sell to the government to its correct CPBS segment and family code before generating the invoice. If you supply cleaning services, that maps to a specific CPBS family. If you supply both cleaning services and cleaning products on the same invoice, each line item carries its own distinct CPBS code.

Suppliers who sell a narrow range of goods or services to government buyers can establish their CPBS mappings once and reuse them. Suppliers with diverse catalogs need a more systematic approach, maintaining a lookup table that ties internal product codes to their CPBS equivalents.

Why These Fields Fail Validation Together

Both B401 and C10 are checked during the PAC authorization step, not in some downstream audit. The validation logic is straightforward: if B401 indicates a government receiver, the PAC expects valid CPBS codes on every line item in C10. A missing CPBS code, an invalid code, or a malformed entry stops the invoice from being authorized.

This means a single uncoded line item on a 50-line invoice will reject the entire submission. The PAC does not partially authorize invoices or flag individual lines for correction. You resubmit the full invoice once every field passes validation.

---

The Role of CAFE in Government Invoice Transactions

Every electronic invoice processed through Panama's SFEP system receives a CAFE (Código de Autorización de Factura Electrónica), the authorization code that confirms the invoice has been successfully validated. Think of it as the digital fingerprint proving your invoice passed through the required authorization process and is recognized by the DGI as legitimate.

The CAFE is generated when your PAC validates the invoice data and transmits it to the SFEP. For standard commercial invoices between private parties, the CAFE confirms proper electronic processing. For government invoices, its role is more consequential.

Why CAFE carries extra weight in government transactions: Because invoices to public entities require prior authorization, the CAFE functions as direct proof that your invoice completed the mandatory authorization workflow. Without it, the government buyer has no way to confirm the invoice followed the required process. In practice, the government entity receiving your invoice will check the CAFE to verify it was properly authorized before routing it through their internal payment processing. No valid CAFE, no payment.

The CAFE is embedded directly in the electronic invoice document and can be independently verified through the DGI's verification systems. Retain the CAFE for every government invoice as part of your compliance records. If a government entity questions an invoice or delays payment citing authorization concerns, the CAFE is your first line of evidence that the invoice was properly submitted and validated through the SFEP prior-authorization process.

---

Step-by-Step Supplier Workflow for Government Invoices

The individual requirements covered above converge into a single end-to-end process whenever you issue an electronic invoice to a Panamanian government buyer through the SFEP. The workflow below consolidates every obligation into a sequential reference your accounting team can follow each time a government sale closes.

Step 1: Prepare the invoice in your invoicing system. Populate all standard SFEP invoice fields, then address the government-specific requirements: set the B401 receiver-type field to the government entity classification, and assign the correct CPBS code (field C10) to every line item on the invoice. No line can be left without a CPBS classification. Verify the government buyer's RUC and entity name against DGI records before moving forward.

Step 2: Submit the invoice to your PAC for prior authorization. Send the completed invoice to your Proveedor Autorizado Certificado for autorización previa. The PAC must authorize the invoice before it reaches the buyer.

Step 3: Receive validation results from the PAC. The PAC checks the full invoice payload, including the government-specific fields. If validation fails, you will receive error codes identifying the problem. The most frequent causes of rejection:

• Missing or invalid CPBS codes on one or more line items
• Incorrect B401 receiver-type classification (e.g., submitting with a private-sector receiver type)
• Incomplete standard SFEP fields that would also fail in non-government invoices

Correct the flagged errors in your invoicing system and resubmit. There is no partial approval; every field must pass.

Step 4: Receive the CAFE upon successful validation. Once the PAC confirms the invoice data is correct, it generates the Código de Autorización de Factura Electrónica. This alphanumeric code is the DGI's proof that your invoice was authorized before delivery. The CAFE is embedded in the invoice's electronic representation and encoded in its QR code.

Step 5: Deliver the authorized invoice to the government entity. With the CAFE attached, transmit the invoice to your government buyer through whatever channel the entity accepts. The buyer can independently verify the CAFE against DGI systems to confirm the invoice is legitimate and pre-authorized. An invoice delivered to a government entity without a valid CAFE is not compliant.

Step 6: The invoice enters the government procurement payment cycle. Once the government entity accepts the authorized invoice, it moves into the public-sector payment process governed by Panama's procurement and treasury rules. Your compliance obligation on the invoicing side is complete at delivery of the CAFE-bearing document.

A note on the Facturador Gratuito: Suppliers using the DGI's free invoicing tool cannot process government invoices through it. The Facturador Gratuito does not support the prior-authorization flow required when invoicing government entities. If you sell to both private and public buyers, you need a PAC-connected invoicing system for the government sales, even if the free tool handles your other volume.

Suppliers operating across Latin America will encounter analogous but distinct public-sector invoicing rules in each jurisdiction. If you also invoice government entities in Uruguay, reviewing Uruguay's public-sector e-invoicing requirements for suppliers will help you map the differences rather than assume Panama's SFEP rules carry over.