Contents
Who this article is for: it applies to clubs operating in the Dominican Republic that must issue electronic fiscal receipts (e-CF / e-NCF).
What is this integration?
The integration with the Dominican Republic Tax Authority (DGII) lets you issue electronic fiscal receipts (e-CF) from Golfmanager in compliance with Dominican regulations. When an invoice is signed, Golfmanager generates it in electronic format (XML) and sends it to the Voxel signer, which signs it digitally and returns the fiscal data (the security code and the QR code) that are added to the invoice.
The Voxel signer is a small program (middleware) installed on a computer at the club. It receives the electronic invoice, signs it with the digital certificate (which the signer itself holds) and processes it toward the Dominican tax authority, returning the fiscal data that must appear on the invoice.
What problem does it solve?
Complying with Dominican tax rules: it issues valid electronic fiscal receipts with no manual processes.
It adds the QR and the fiscal data (security code, NCF, signing date) to the invoice automatically.
It avoids fiscal-classification errors by mapping invoice types, taxes and payment methods to their Dominican legal designations.
It controls the NCF numbering (series, ranges, expiration and exhaustion alerts).
It leaves a trail of every signing attempt (successful or failed) in a transactions log.
Which systems does it connect, and which way does the data flow?
It connects Golfmanager with the Voxel signer (installed on the club's network) and, through it, with the Dominican tax authority:
Golfmanager generates the invoice in electronic format (XML) when it's confirmed.
On signing, it sends that XML to the Voxel signer on the local network.
The signer signs it digitally and processes it toward the tax authority.
The signer returns the security code, which Golfmanager uses to build the QR and stores on the invoice.
The signer communicates over the club's local network (its IP address is configured).
What information is exchanged?
Information | Direction | Purpose |
Invoice in electronic format (XML) | Golfmanager → Signer → Tax authority | Sign and declare the receipt |
Security code (identifier) | Signer → Golfmanager | Build the QR and the fiscal data |
Submission result (success / error) | Signer → Golfmanager | Confirm the signature and keep a record |
Prerequisites (before turning the integration on)
Have the Voxel signer installed and running on a club computer, with its digital certificate loaded, reachable from Golfmanager by its IP address.
Have the Dominican Republic Tax Authority module installed (ask your Golfmanager consultant), along with the billing and customers modules.
Have the NCF series configured (numbering range and expiration) for each type of receipt.
Have the legal designations mapped for invoice types, taxes and payment methods. Without this, signing will error.
Have the company date and the club's fiscal data (RNC) filled in.
Billing permissions to configure and sign.
How to set it up (step by step)
Step 1 — Install the module
Ask your Golfmanager consultant to install the Dominican Republic Tax Authority module.
Step 2 — Connection with the signer
Go to Settings > Billing > Dominican Republic Tax Authority.
Enter the Voxel signer IP address (the computer where it's installed; the port is already implicit in the system, you only need the IP).
Select the Default invoice type.
Decide whether to turn on Automatically sign invoices when confirmed.
Save your changes.
Step 3 — Company fiscal data
In the company record, check that the RNC is filled in and set the company date (required to issue receipts).
Save your changes.
Step 4 — Configure the NCF series
In the invoice numbering series configuration, set for each series: start number, end number, expiration, whether it's active, and optionally the remaining-numbers alert and the alert email.
Save your changes.
ℹ️ Each series corresponds to a type of receipt (e-NCF). When a series reaches its end number or its expiration date, it can no longer issue, and a new one must be created.
Step 5 — Map the legal designations
Indicate which Dominican fiscal category each element corresponds to:
On each invoice type, fill in RD Treasury invoice type.
On each payment method, fill in RD Treasury payment method ID.
On each tax, fill in RD Treasury code.
Save in each case.
⚠️ Important: if any of these mappings is missing, when you try to sign the invoice the system will error stating so. It's best to configure them all before starting.
Step 6 — Customer data
On each customer record, flag whether their document is foreign (foreign passport/tax ID) or national (RNC).
If applicable, assign them their own invoice type (it overrides the default type for that customer).
Save your changes.
Each configuration field explained
Below, each field is explained: what it is, how it affects the system, how it behaves, and an example of use. They're grouped into: connection, NCF series, legal designations, and company/customer.
Connection and behavior (Settings > Billing > Dominican Republic Tax Authority)
Voxel signer IP address
Field name: IP address of the offline invoice signer.
Description: the IP of the local-network computer where the Voxel signer is installed.
System impact: it's where Golfmanager sends invoices to be signed. Without it, signing isn't possible.
System behavior: if it's empty, signing shows the notice "The signer IP is not configured". The port is implicit.
Example of use / what happens: you enter the signer computer's IP and save; from then on invoices can be signed.
Default invoice type
Field name: Default invoice type. Required field.
Description: the invoice type applied when no other is specified.
System impact: it determines the series/numbering and the fiscal designation of invoices that don't have a specific type.
System behavior: if it isn't set, when saving customers/invoices the system warns that a default invoice type is missing.
Example of use / what happens: you select "Electronic consumption bill" as the default for final-consumer sales.
Automatically sign invoices when confirmed
Field name: Automatically sign invoices when confirmed. It's a toggle (on/off, off by default).
Description: decides whether each invoice is signed on its own as soon as it's confirmed.
System impact: on, it automates signing; off, you sign by hand with the button.
System behavior: with auto-sign, if the signer isn't reachable the invoice won't be signed and you'll be warned; you'll have to retry the signing manually.
Example of use / what happens: you turn it on so you don't have to click "Sign" on every invoice; you leave it off if you prefer to review before signing.
NCF series (on each invoice numbering series)
Start number
Field name: Start number.
Description: the first number of the series' authorized range.
System impact: it marks where the series starts numbering.
System behavior: if the counter falls below the start, the system warns that the value is below the start of the series.
Example of use / what happens: you enter the first number of the range the DGII authorized for you.
End number
Field name: End number.
Description: the last number of the series' authorized range.
System impact: it marks the series limit.
System behavior: on reaching it, the series can no longer issue ("The series has reached the last value") and a new one must be created.
Example of use / what happens: you enter the last number of the authorized range; when it runs out, you register another series.
Expiration
Field name: Expiration.
Description: the expiration date of the NCF series.
System impact: after that date, the series can't issue any more receipts.
System behavior: on confirming an invoice with an expired series, the system warns that "The series has expired". This date is also printed on the invoice.
Example of use / what happens: you enter the expiration date the DGII indicates for that range.
Active
Field name: Active.
Description: indicates whether the series is in use.
System impact: only active series can issue.
System behavior: if the series isn't active, on confirming invoices with it the system warns that "The series is not active".
Example of use / what happens: you activate the series in force and deactivate the ones you no longer use.
Remaining-numbers alert
Field name: Remaining-numbers alert.
Description: how many numbers before exhausting the series you want to receive a warning.
System impact: it helps you anticipate the series running out.
System behavior: when that many receipts are left before the end, a warning is sent to the alert email.
Example of use / what happens: you set 50 so you're warned when 50 receipts are left and can arrange another series in time.
Alert email
Field name: Alert email.
Description: the address the series-exhaustion warning is sent to.
System impact: it's the recipient of the warning above.
System behavior: it receives the email when the "remaining-numbers alert" threshold is reached.
Example of use / what happens: you set the club administrator's email so they receive the warning.
Legal designations
RD Treasury invoice type (on each invoice type)
Field name: RD Treasury invoice type.
Description: maps Golfmanager's invoice type to the Dominican legal designation.
System impact: it defines which class of e-CF is declared.
System behavior: if an invoice type doesn't have this mapping, on signing the system warns that "the invoice type is not associated with any RD Treasury type".
Options: Electronic commercial invoice (tax credit); Electronic consumption bill; Electronic credit note; Electronic debit note; Electronic receipt for special regimes; Government electronic receipt.
RD Treasury payment method ID (on each payment method)
Field name: RD Treasury payment method ID.
Description: relates each payment method to its Dominican legal designation.
System impact: it classifies the payment means on the receipt.
System behavior: if not mapped, the invoice may not sign correctly.
Options: Cash; Check, transfer or deposit; Debit or credit card; Credit sale; Vouchers or gift certificates; Credit note.
RD Treasury code (on each tax)
Field name: RD Treasury code.
Description: maps each tax to its Dominican legal designation.
System impact: it determines how each tax on the invoice is declared.
System behavior: if a tax on the invoice has no code, on signing the system warns that "the tax does not have an associated Dominican treasury code".
Options: ITBIS; ISC (excise tax); Ad Valorem; Exempt; Legal tip; CDT (contribution to the development of telecommunications).
Company and customer
Company date
Field name: Company date (on the company record).
Description: the club's fiscal reference date for the DGII.
System impact: it's required to issue receipts; it's copied onto each invoice when it's created.
System behavior: if it's missing, the system warns that "the company date is required".
Example of use / what happens: you fill it in once with the relevant date and invoices inherit it.
Foreign document (on the customer record)
Field name: Foreign document (foreign tax ID/passport).
Description: indicates whether the customer's document is foreign rather than a national RNC.
System impact: it makes the customer's document be declared correctly as foreign.
System behavior: it adjusts the customer's fiscal treatment on the receipt.
Example of use / what happens: you flag it on a customer with a foreign passport.
Customer invoice type (on the customer record)
Field name: Invoice type.
Description: the preferred invoice type for that customer (it overrides the default type).
System impact: that customer's invoices use this type instead of the global one.
System behavior: if it's empty, the configuration's default type is used.
Example of use / what happens: you assign a business customer "Electronic commercial invoice (tax credit)".
How it works day to day
Signing an invoice
There are several ways, depending on the configuration:
Automatic: if you enabled "Automatically sign invoices when confirmed", each invoice is signed on its own when confirmed.
Manual (one invoice): in the invoice detail, in the actions menu, click "Sign invoice". Golfmanager sends it to the signer and, if all goes well, the invoice is signed with its QR and security code. You'll see the message "Invoice signed correctly".
Bulk (several invoices): in the invoice list, select several and use the sign invoices action. The system tells you how many were signed correctly.
Downloading the XML
The invoice detail also has the "Download Voxel XML" action, which downloads the electronic document that would be sent to the signer. It's useful for review or support. It's only available if the invoice is confirmed.
ℹ️ An invoice can only be signed once. Once signed, its signing date is recorded and, if you try to sign it again, the system warns that "it is already signed".
The NCF series (numbering and expiration)
Each numbering series corresponds to a type of receipt (e-NCF) and has an authorized range (start and end number), an expiration date and an active/inactive status. Golfmanager automatically controls:
That the series is active and not expired when issuing.
That the end number isn't exceeded.
The sending of an email warning when few numbers remain (per the "remaining-numbers alert").
When a series runs out or expires, a new one must be registered with its range and expiration.
What appears on the invoice
After signing, the printed or downloadable version (PDF) and the POS ticket include:
The NCF / e-NCF (receipt number).
The sequence expiration (the series' expiration).
The RNC of the club and, if applicable, of the customer.
The fiscal QR code.
The signing date and the security code returned by the signer.
Checking the transactions
The module keeps a RD Treasury Transactions log with each signing attempt. Each record shows:
The associated invoice.
The document sent (the request XML).
Whether it was successful or failed.
The response received from the signer.
It's the first screen to check when an invoice hasn't been signed correctly. You access it from the Billing menu.
Limitations to keep in mind
It depends on the Voxel signer: it must be installed, powered on and reachable by its IP, with its digital certificate loaded. If it doesn't respond, invoices can't be signed.
The digital certificate is held by the signer, not Golfmanager; its validity is managed in the signer itself.
Each invoice is signed only once. After signing it's locked against further submissions.
You must map the legal designations (invoice type, tax, payment method) before signing.
NCF series have a range and expiration: you must renew them before they run out or expire.
Proforma and internal invoices aren't signed and don't generate an e-CF.
It's specific to the Dominican Republic: it doesn't apply to other countries.
Frequently asked questions
Does Golfmanager send invoices directly to the DGII?
Not directly: Golfmanager generates the electronic invoice and sends it to the Voxel signer on the local network, which is what signs it with the digital certificate and processes it toward the Dominican tax authority. Golfmanager stores the result and the fiscal data (QR, security code).
What is the Voxel signer and where is it installed?
It's a small program (middleware) installed on a club computer, on the local network. It holds the digital certificate and signs the invoices. In Golfmanager you only configure its IP address.
How do I sign an invoice?
Three ways: automatically on confirmation (if you enable that option), manually with the "Sign invoice" button in the detail, or in bulk by selecting several invoices in the list.
Can I sign an invoice twice?
No. An invoice is signed only once. If you try again, the system warns that "it is already signed". Its signing date is recorded.
When signing, a notice says a designation is unmapped. What do I do?
A Dominican fiscal code is missing on some element. Check that the invoice type has its "RD Treasury invoice type", that each tax has its "RD Treasury code" and that each payment method has its "RD Treasury payment method ID". Map them and sign again.
I get "the invoice type is not associated with any RD Treasury type". What should I check?
The invoice type used doesn't have the RD Treasury invoice type field filled in. Edit it, select the relevant designation and save.
I get "the tax does not have an associated Dominican treasury code". What should I check?
Some tax on the invoice doesn't have the RD Treasury code filled in. Go to Taxes, assign it the code (ITBIS, ISC, etc.) and sign again.
I get "Could not reach the Voxel signer". What do I do?
The signer is off or the IP is wrong. Check that the signer is powered on and reachable on the network and that the configured IP is correct; then sign again.
I get "The signer IP is not configured". What should I check?
The signer IP address is missing in the configuration. Go to Settings > Billing > Dominican Republic Tax Authority and enter it.
I get a "Voxel error: …". What does it mean?
It's an error returned by the signer itself (for example, a receipt detail the tax authority doesn't accept or a certificate problem). Review the detail in RD Treasury Transactions, correct what's indicated and sign again.
I get "The series has expired". What do I do?
The NCF series has passed its expiration date. Register a new series with its range and a future expiration, and mark it active.
I get "The series has reached the last value". What do I do?
The series has reached its end number and can't issue any more. Create a new series with a new range authorized by the DGII.
I get "The series is not active". What should I check?
The series is marked inactive. Edit it and mark it active (or use another series that is).
I get "the company date is required". What should I check?
The company date is missing on the club record. Fill it in and try again; invoices inherit it when created.
How do I know if an NCF series is running out?
Configure the remaining-numbers alert and an alert email on the series: when that many receipts are left before the end, the system sends a warning to that address so you can arrange a new series in time.
Which receipt types does it support?
Electronic commercial invoice (tax credit), Electronic consumption bill, Electronic credit note, Debit note, Special-regime receipt and Government receipt. Each Golfmanager invoice type is mapped to one of them.
How do I handle credit notes?
Use an invoice type mapped to Electronic credit note. The credit note must reference the original invoice; Golfmanager includes that reference in the receipt.
Can I invoice a final consumer without the customer's RNC?
Yes. For final-consumer sales the electronic consumption bill is used; the receipt is issued without the customer's RNC (the QR is built with the company's data and the invoice).
A customer has a foreign passport. How do I configure it?
On their record, flag the foreign document field. That way the document is declared as foreign rather than as a national RNC.
What fiscal data appears on the signed invoice?
The NCF, the sequence expiration, the RNC of the club (and of the customer if applicable), the QR code, the signing date and the security code.
What is "Download Voxel XML" for?
It downloads the electronic document that would be sent to the signer, useful for review or support. It's only available if the invoice is confirmed.
An invoice hasn't been signed. Where do I look at what happened?
In RD Treasury Transactions (Billing menu): each signing attempt leaves the XML sent, whether it was successful or failed, and the signer's response. The error detail is there.
Are proforma or internal invoices signed?
No. Proforma and internal invoices don't generate an electronic receipt and can't be signed; they use their internal numbering.
Can auto-sign fail?
Yes: if you have auto-sign enabled and the signer isn't reachable on confirmation, the invoice won't be signed and you'll be warned. In that case, sign it manually again when the signer is available.
Who renews or manages the digital certificate?
The digital certificate is held by the Voxel signer, not Golfmanager. Its loading and validity are managed in the signer itself; if it expires, signing will fail until it's renewed.
Recommended best practices
Configure all the legal designations (invoice types, taxes and payment methods) before you start signing.
Keep the Voxel signer always running with a stable IP on the network, and its certificate valid.
Watch the NCF series: configure the remaining-numbers alert and renew before they run out or expire.
Flag foreign customers correctly so the receipt comes out right.
Decide whether to use auto-sign (on confirmation) or manual, based on your workflow.
On a failure, check Transactions first: the submission detail and the signer's response are there.