Your PAC is changing its domain: what to check before your invoices stop going out
A PAC address change looks like a technical chore, but it can leave you unable to issue or void invoices. What we checked at SuiteHub when Digifact announced it was retiring its old domain, as a checklist any small business can follow.
Digifact announced it is retiring apinuc.digifact.com.pa, the address many
systems use to send it electronic invoices. The new one is
nucpa.digifact.com, and the deadline to switch is November 30.
At a glance it looks like a chore: someone changes a URL and that’s it. In practice, if your system still points to the old address the day it’s shut down, you stop issuing invoices. And in Panama, no electronic invoice means no formal sale.
When the notice arrived, we did a full review at SuiteHub before touching anything. Here is that review, as a checklist, for any small business, whatever system it runs.
First, understand what changes
In Panama’s model your system doesn’t send the invoice to the DGI (the tax authority). It sends it to a PAC (an authorized certification provider), which validates it, transmits it and returns the CUFE, the invoice’s unique code. To talk to the PAC, your system needs its address. If the PAC moves, your system has to know.
Start by reading the notice calmly and writing down three things:
- Which address is being retired and which one replaces it. Exact names.
- When the old one stops working. “Starting on” and “until” are not the same thing.
- Whether anything besides the address changes: user, token, certificates or service version. In what we reviewed, only the address changes.
The first suspect is rarely the cause
When something network related fails, the first thought is the firewall. So we checked that first: can the server reach the new address?
It could. The server allowed outbound traffic and was already reaching nucpa.
The problem was somewhere else: where the old address lived.
I mention it because it’s a common trap: you lose an afternoon with your hosting provider while the real change is somewhere else.
Where the PAC address lives
This is what taught us the most. In our case, the PAC address was in two places at once:
- In the code, as a default value. Every new system was born with the old address already written in.
- In each installation’s saved settings. When a system was set up, that default value got stored in its database.
That means fixing the code isn’t enough. Existing installations have the old address saved and will keep using it, even if the new version of the program ships with the right one.
If your system comes from a vendor, the question to ask is simple:
“Is the PAC address in the code, in my company’s settings, or in both? Who changes each one, and when?”
If the answer is “it updates itself”, ask them to show you where the current value can be seen.
It’s not only issuing: voiding and lookups too
We almost missed this one, and it’s the point I most want you to take away.
An invoice issued through a PAC is voided through that same PAC. We found a system that was already issuing through another provider, so in theory the Digifact change didn’t affect it. But its older invoices, the ones issued through Digifact, are voided through Digifact. And that operation still pointed to the old address.
If you switched PACs in recent months, check the old one’s settings too. As long as you have invoices from it that may need voiding or lookups, it’s still part of your operation.
Testing and production are two addresses
PACs have a testing environment and a production environment, each with its own
address. For Digifact, testnucpa for testing and nucpa for production.
When you review, confirm both. It’s common to fix production and leave testing broken. You find out weeks later, when someone wants to try something and nothing works.
How we made the change without scares
This was the order, and it works for any system:
- Inventory, without touching anything. A list of every system or branch that invoices, which PAC it uses, in which environment and which address it has saved. If you have several branches or legal entities, don’t assume they’re all the same.
- Backup before changing. A copy of each installation’s database, right before touching its settings.
- Change the value and clear the session. Many systems store an access token the PAC issued under the old address. If it isn’t deleted, the system may keep trying to use it. We left the address empty so the system picks the right one for its environment, and deleted the stored token.
- Test the connection and issue a test invoice. If your system has a “test connection” button, use it. Then issue a small real invoice or one in the testing environment.
- Fix the code afterwards. With the data up to date, the code change keeps new installations from being born with the old address. That step can wait a few days. The data step can’t.
We did it in phases, one installation at a time, starting with the ones in production. None was touched without a backup first.
The short list
If you have five minutes, this is what I would check:
- Which PAC do I use today? Which one did I use before?
- Where is the PAC address stored in my system?
- Is it right in production and in testing?
- Can I void an old invoice issued through the previous PAC?
- Does my software vendor know about the change and have a date to make it?
- Is there a database backup from before the change?
- Did I issue a test invoice after the change?
Don’t leave it for the last day
November 30 is a Monday. If you make the change on Friday the 27th and something goes wrong, you have a weekend of sales without invoices. Do it with time to spare, on a quiet day, with someone who can roll it back if needed.
A domain change shouldn’t be an emergency. It only becomes one when nobody knew where the old address was stored.
If your system invoices through Digifact and you don’t know where to start, write to me. I’ll tell you what to check in your case.
Comments
Comments via GitHub Discussions, requires GitHub login.