Panama Government E-Invoicing Requirements for Suppliers

After a 2022 extension, Panama gave state suppliers until October 31, 2022 to adopt electronic invoicing for public-sector sales. Since that transition deadline, government purchases have required invoices issued through the SFEP (Sistema de Facturación Electrónica de Panamá), under the conditions set by Law 256 and DGI Resolution 201-5215.

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:

Prior authorization (autorización previa). Before a government invoice reaches the buyer, it must be authorized through the supplier's permitted SFEP modality. This pre-delivery validation step has no equivalent in ordinary consumer invoicing.
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.
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's government-sales guidance identifies Resolution 201-5215 as the basis for the public-sector e-invoicing requirement, while the DGI sets the technical standards, certifies PACs, and enforces compliance for both commercial and government invoicing.

This guide focuses on the public-sector rules: prior authorization, CPBS coding, B401 receiver classification, CAFE validation, and the supplier workflow through SFEP. For suppliers who need a broader overview of Panama's electronic invoicing obligations, see our coverage of Panama's SFEP electronic invoicing requirements.

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 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:

You generate the electronic invoice.
You submit it through the allowed SFEP modality for authorization.
The authorization channel validates the invoice and returns confirmation.
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 SFEP authorization is complete. Delivering an unauthorized invoice to a public entity is non-compliant.

Confirm Your Allowed SFEP Modality

Because government invoices must be electronically authorized before the public entity can treat them as valid, confirm which SFEP modality your business is allowed to use before bidding. Official MEF/DGI guidance says state suppliers could adopt either the Facturador Gratuito or a PAC, while current free-biller thresholds may still push higher-volume suppliers toward a PAC or DGI-certified own system.

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: build authorization onboarding and testing into your timeline before preparing to supply government entities.

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, 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 determines which validation path your invoice follows. 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 it is rejected 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.

Map each product or service you sell to the government to the CPBS/UNSPSC code format required for field C10 in the current DGI technical specification 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 authorization, not in some downstream audit. The validation logic is straightforward: if B401 indicates a government receiver, the system 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 authorization process does not partially approve 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. It is the authorization evidence that shows the invoice passed the required SFEP validation process.

The CAFE is generated when the invoice data is validated and transmitted through 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. For more detail on checking invoice identifiers, see the guide to Panama CUFE invoice validation. 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 for prior authorization. Send the completed invoice through your permitted SFEP modality for autorización previa. The invoice must be authorized before it reaches the buyer.

Step 3: Receive validation results. The authorization process 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 validation confirms the invoice data is correct, the system 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: Official MEF guidance has allowed state suppliers to adopt electronic invoicing through either the Facturador Gratuito or a PAC. In practice, eligibility and operating fit still matter: suppliers above the current free-biller thresholds, or suppliers that need integration and higher-volume handling, should plan around a PAC or DGI-certified own system rather than assuming the free tool will cover government sales.

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.