Index
Who this article is for: It applies to clubs that operate in Panama and must issue electronic invoices.
What is this integration?
The Panama tax integration lets you issue electronic invoices from Golfmanager, complying with the regulations of the DGI (Dirección General de Ingresos, the tax authority). When you invoice, Golfmanager sends the document to an authorized processor (PAC, "Factura Panamá"), which certifies it with the DGI and returns the CUFE (Código Único de Factura Electrónica) and the invoice identifier.
The electronic invoice is the legal way to invoice in Panama. To issue it, a PAC (authorized provider) is used to certify the document with the DGI. The CUFE is the unique code that identifies each electronic invoice.
What problem does it solve?
Comply with Panamanian tax regulations by issuing valid electronic invoices, with no manual processes.
Processes and certifies the invoice and obtains the CUFE.
Keeps consistency between what is invoiced in Golfmanager and what is declared to the DGI.
Leaves a trail of every operation (each processed invoice is recorded with its result).
Which systems does it connect and in which direction does the data flow?
It connects Golfmanager with the authorized processor (PAC, "Factura Panamá") and, through it, with the DGI:
Golfmanager generates the invoice and sends it to be processed.
The processor certifies it with the DGI and returns the CUFE and the invoice identifier.
Golfmanager stores the CUFE, the identifier and the authorized XML on the invoice.
What information is exchanged?
Information | Direction | Purpose |
Invoice data (issuer, receiver, line items, taxes, payment method) | Golfmanager → Processor → DGI | Process the electronic invoice |
CUFE, identifier and authorized XML | DGI → Processor → Golfmanager | Store the certified invoice |
Prerequisites (before activating the integration)
Operate in Panama and be required to use electronic invoicing.
Have the "Factura Panamá" service contracted (authorized processor) and its connection details (username, password and endpoint).
Have the module installed, together with the invoicing module.
Have the issuer's RUC and the details of the establishment and point of issuance.
System/billing management permissions to configure.
How to set it up (step by step)
Step 1 — Issuer and service data
Log in to Golfmanager with an administrator user.
Go to Settings > Factura Panamá.
Enter the Issuer RUC.
Enter the Username and Password of Factura Panamá.
Enter the Endpoint (the processor's service address).
Enter the Establishment and the Point of issuance.
Leave the Production mode off to start (test). There is a separate version of each value for test and production.
Save the changes. The username and password are stored encrypted.
Step 2 — Taxes and product codes
Check that your taxes use the Panama codes (ITBMS, ISC or OTI).
Assign each product its Panama product code.
Step 3 — Customer fiscal data
Go to the customer record.
Fill in the National identification (RUC/ID) and the Verification digit.
Fill in the Location code, the Province, the District and the Corregimiento/Canton.
Save the changes.
Step 4 — Payment method and test
On each invoice, indicate the payment method (cash, card, transfer, etc.).
Process a test invoice and check that you obtain the CUFE.
When everything works, turn on the Production mode with the real credentials.
⚠️ Recommendation: always start in test mode with the test credentials, process a sample invoice and move to production only when everything works.
Explanation of each field
Below is a description of each field in the integration: where it is, what it means, its impact on the system, and a usage example (what happens when it is used and how the system behaves). The issuer and service data have a test version and a production version.
A) Issuer settings (Settings > Factura Panamá)
1. Production mode
Description: a switch that indicates whether you work in test (off) or production (on).
Impact on the system: it determines which set of data is used (test or production) and whether invoices are real before the DGI. Off by default.
Usage example: you turn it on when you finish validating the integration.
What happens when it is used: off, invoices are processed against the test environment; on, they are real.
System behavior: based on the switch, Golfmanager uses the test or production RUC, username, password, endpoint, establishment and point.
2. Issuer RUC
Description: the RUC (tax ID) of your club/company as the issuer.
Impact on the system: it is mandatory. It identifies the issuer on the electronic invoice.
Usage example: you enter your company's RUC.
What happens when it is used: invoices are issued in the name of that RUC.
System behavior: if it is missing, processing shows "Falta el RUC del emisor en la configuración de Factura Panamá".
3. Username and 4. Password (Factura Panamá)
Description: the credentials of the authorized processor's service, provided by your supplier.
Impact on the system: mandatory to authenticate with the PAC. Stored encrypted.
Usage example: you copy them from the provider and paste them.
What happens when it is used: each invoice is sent to the processor authenticated with these credentials.
System behavior: if they are incorrect, the processor rejects the operation; the error detail is kept in the transactions log.
5. Endpoint
Description: the address of the processor's service that Golfmanager sends the invoices to.
Impact on the system: mandatory. It determines which server (test or production) it connects to.
Usage example: you paste the URL your provider indicates.
What happens when it is used: processing travels to that address.
System behavior: if it is missing, "Falta el endpoint en la configuración de Factura Panamá" appears; if it is incorrect or the service does not respond, processing fails.
6. Establishment and 7. Point
Description: the establishment (premises) and the point of issuance, which identify where and from which point the invoice is issued.
Impact on the system: mandatory. They are part of the receipt numbering.
Usage example: you enter them with the values the processor/DGI indicates.
What happens when it is used: the electronic invoice is issued with that establishment and point.
System behavior: if either is missing, "Falta el establecimiento…" or "Falta el punto en la configuración de Factura Panamá" appears.
B) Customer fiscal data (customer record)
8. National identification (RUC/ID)
Description: the RUC or ID (cédula) of the invoice receiver.
Impact on the system: it is essential to process that customer's invoice.
Usage example: you fill in the customer's RUC/ID.
What happens when it is used: the invoice is issued in the name of that receiver.
System behavior: if it is missing, "Cliente no tiene ID nacional para factura Panamá" appears and it is not processed.
9. Verification digit
Description: the verification digit (DV) associated with the customer's identification.
Impact on the system: required to validate the identification.
Usage example: you fill it in next to the RUC/ID.
What happens when it is used: it accompanies the receiver's identification.
System behavior: if it is missing, "Cliente no posee digito verificador (facturapanama)" appears.
10. Location code, 11. Province, District and Corregimiento/Canton
Description: the customer's geographic data required by the electronic invoice.
Impact on the system: mandatory to process; they identify the receiver's location.
Usage example: you fill in the customer's location code and province/district/corregimiento.
What happens when it is used: the invoice includes that regional information.
System behavior: if the location code is missing, "Cliente requiere un código de ubicación de factura Panamá" appears; if the province/district/corregimiento is missing, "Falta información regional de factura Panamá de cliente".
C) Products and taxes
12. Panama product code
Description: the product/service code sent to the processor on each line.
Impact on the system: it is mandatory on each invoice line.
Usage example: on a green fee, you assign its Panama product code on the product record.
What happens when it is used: each line is issued with its code.
System behavior: if a product has no code, "Producto no tiene código de factura Panamá" appears and it is not processed.
13. Tax code (ITBMS / ISC / OTI)
Description: the tax code according to Panama: ITBMS (transfer of goods and services, e.g. 7%, 10%, 15% or exempt), ISC (selective consumption tax) or OTI (other taxes).
Impact on the system: mandatory on each tax of the invoice; it defines the tax breakdown.
Usage example: on your VAT tax you use the corresponding ITBMS code.
What happens when it is used: the invoice breaks down the tax correctly.
System behavior: if it is missing or the code is not valid, "Código de impuesto faltante, use uno de los impuestos validos ISC, ITBMS u OTI" appears.
D) Invoice
14. Payment method
Description: how the invoice was paid (cash, credit, credit/debit card, transfer, check, voucher, gift card, payment point, etc.).
Impact on the system: the electronic invoice requires it.
Usage example: you select "Cash" or "Credit card" on the invoice.
What happens when it is used: the receipt reflects that payment method.
System behavior: if you don't indicate it, processing may fail or the processor may reject the invoice.
15. CUFE and 16. Panama Invoice ID (result, read-only)
Description: the CUFE (unique code) and the identifier of the invoice that the processor returns after certifying it.
Impact on the system: they confirm the invoice is certified. They are not typed by hand.
Usage example: they appear after clicking "Procesar factura SAT".
What happens when it is used: once the invoice has a CUFE, it is a valid fiscal receipt.
System behavior: Golfmanager stores the CUFE, the identifier and the authorized XML, and records the operation in the Factura Panamá transactions list.
How to use it day to day (step by step)
Create or open the invoice in Golfmanager.
Check that the customer's fiscal data (RUC/ID, verification digit, location) and the payment method are present.
Click the "Procesar factura SAT" action on the invoice detail.
Review the result: if everything is correct, the invoice is certified and Golfmanager stores its CUFE and identifier.
ℹ️ Once processed and with a CUFE, the invoice is a valid fiscal document. Any correction must follow the procedure allowed by the regulations (it is not simply modified). The receipt's PDF/QR is handled by the processor; Golfmanager stores the authorized XML and the CUFE.
Key tax concepts
Concept | What it is |
CUFE | Unique Electronic Invoice Code that identifies the document |
RUC | Tax identification of the issuer (and the customer, where applicable) |
Establishment and Point | Identify the premises and the issuance point in the numbering |
ITBMS / ISC / OTI | Panama's taxes (transfer of goods and services, selective consumption, others) |
Payment method | How the invoice was paid (cash, card, transfer…) |
Limitations to keep in mind
It depends on the processor and the DGI: if the service is unavailable, you cannot process at that moment.
The fiscal data must be complete (RUC, verification digit, location, product code, tax and payment method); if any is missing, processing fails.
An invoice with a CUFE is a fiscal document: its correction follows the regulatory procedure (it is not simply edited).
The module processes invoices; cancellation or credit notes are handled according to the DGI/your processor's procedure.
The receipt's PDF/QR is generated by the processor; Golfmanager stores the authorized XML and the CUFE.
It operates in USD and is specific to Panama. Do not mix test with production.
Frequently asked questions
When processing, "Falta la configuración de Factura Panamá" appears, or that the RUC, establishment, point or endpoint is missing.
Some connection data for the mode in use is missing. Go to Settings > Factura Panamá and complete the Issuer RUC, the username, the password, the endpoint, the establishment and the point (the test ones if you are in test, the production ones if you are in production) and save.
I get "Producto no tiene código de factura Panamá" (the product has no Panama invoice code).
That product has no Panama code assigned. Fill in the "Panama product code" on the product record and process again.
I get "Código de impuesto faltante, use uno de los impuestos validos ISC, ITBMS u OTI".
The applied tax has no valid Panama code. Check that your taxes use the ITBMS, ISC or OTI codes and process again.
It tells me customer data is missing (national ID, verification digit or location).
The receiver must have a RUC/ID, verification digit and location data. Complete the national identification, the verification digit, the location code and the province/district/corregimiento on the customer record and process again. Possible messages are "Cliente no tiene ID nacional…", "Cliente no posee digito verificador…", "Cliente requiere un código de ubicación…" and "Falta información regional…".
It says the customer has no address, email or nationality.
The processor requires those receiver details. Complete the street/address, the email and the nationality on the customer record and process again.
The invoice is not processed because the payment method is missing.
The electronic invoice requires the payment method. Select it on the invoice (cash, card, transfer, check, etc.) and process again.
The CUFE is not obtained / the processor does not respond.
The processor's service or the DGI may be unavailable, or the document may have been rejected. Review the error detail in the transactions log and retry when the service is available.
The processor rejects the invoice.
This is usually due to incomplete or incorrect fiscal data (of the customer, the taxes or the products). The message returned by the processor indicates the reason; correct the data it points to and process again.
Can I cancel an invoice or issue a credit note from Golfmanager?
The module takes care of processing invoices and obtaining the CUFE. Cancellation or credit notes are handled according to the procedure of the DGI and your processor. Check with your provider how to proceed in each case.
Does Golfmanager generate the invoice's PDF and QR code?
No. Golfmanager stores the authorized XML and the CUFE; the receipt's PDF/QR is generated and delivered by the authorized processor. Check with your provider how to obtain it or send it to the customer.
How do I run a test before invoicing for real?
Leave Production mode off and use the test credentials and data; process a sample invoice and check that you obtain the CUFE. When everything works, turn on Production mode with the real credentials.
In which currency are invoices issued?
In US dollars (USD).
Which taxes does it support?
Panama's: ITBMS (with rates such as 7%, 10% or 15%, plus exempt), ISC (selective consumption tax) and OTI (other taxes). Each tax in your Golfmanager must use the corresponding code.
Can I edit an invoice that already has a CUFE?
No. An invoice with a CUFE is a valid, unalterable fiscal document. Any correction must follow the procedure allowed by the regulations.
Where do I see the result of each processed invoice?
On the invoice itself (CUFE and identifier) and in the Factura Panamá transactions log, where the result, the authorized XML and, if any, the error message are kept.
Who is the processor and where do I get the credentials?
It is the "Factura Panamá" service (an authorized PAC) you contract separately. Your provider gives you the username, the password and the endpoint, both for test and production.
Recommended best practices
Complete your customers' fiscal data (RUC/ID, verification digit, location) before invoicing.
Assign the Panama code to the products and check that taxes use ITBMS/ISC/OTI.
Review the issuer and service data (establishment and point) at rollout.
Process a test invoice and check the CUFE before operating for real.
Always indicate the payment method on the invoice.