Jamaica’s Digital Backbone: Why Electronic Invoicing Is the Easy Part
The Prime Minister is right—but the real challenge lies deeper: building a system where the country finally works as one
There was a moment, almost understated, in the Prime Minister’s contribution to the 2026/27 Budget Debate that revealed more than perhaps was intended.
In responding to proposals for electronic invoicing, Prime Minister Andrew Holness did not reject the idea. Instead, he acknowledged it—then pointed to something far more consequential.
Jamaica is not yet structurally ready.
Not because the country lacks ambition. Not because the policy is flawed. But because the systems required to support it—secure, integrated, and operating as one—are still in development.
Electronic invoicing, often framed as a tool to improve tax compliance, is not a starting point. It is an outcome. A visible layer that depends entirely on what sits beneath.
And what sits beneath, at present, is fragmented.
A Country of Systems, Not Yet a System
Across Jamaica’s public sector, there is no shortage of digital activity. Ministries have implemented platforms. Agencies have adopted tools. Departments have built solutions—sometimes quickly, sometimes creatively—to meet immediate needs.
Individually, many of these systems work.
Collectively, they do not.
“What Jamaica lacks is an integrated system across ministries—a unified digital ecosystem where departments actually speak to each other,” says Dean Jones, founder of Jamaica Homes and a project manager with experience in complex system delivery.
“We’ve implemented solutions on a surface level. Some are effective. But they weren’t designed as part of a single, connected architecture.”
This distinction matters.
Because electronic invoicing is not a standalone function. It requires data to move securely and consistently across multiple parts of government—tax authorities, regulatory bodies, financial systems, and businesses—often in real time.
Without integration, the system does not flow.
It stalls.
The Missing Backbone
To understand the challenge, it helps to step away from the language of software and think instead in terms of structure.
Imagine a city—not the buildings themselves, but the infrastructure beneath them. The unseen networks that allow everything to function together: power, water, transport, communication.
Jamaica’s digital environment resembles a city where individual buildings are complete, but the connections between them remain partial.
“There’s no central spine,” Jones explains. “No digital backbone linking everything together in a deliberate, structured way.”
What exists instead is a collection of systems developed at different times, for different purposes, using different standards. Some connect. Many do not. Some are modern. Others remain rooted in older technologies that are difficult to adapt.
This is not a failure of effort. It is the natural result of incremental development without a single unifying architecture.
But incremental systems cannot support transformational outcomes.
The Data Beneath the Surface
If systems are fragmented, data is even more so.
Within ministries and agencies, information exists in abundance—but rarely in a consistent or unified form. Large Excel spreadsheets remain common, often holding thousands of lines of operational data. Legacy platforms—some built years ago—continue to perform critical functions. In other cases, bespoke tools developed internally have become essential, yet isolated.
“You will find data everywhere,” Jones notes. “Different formats, different structures, different levels of quality.”
In some instances, systems were created to solve specific problems—and did so effectively. But over time, they have become silos: self-contained, difficult to integrate, and often dependent on internal knowledge that is not easily transferred.
The challenge is not simply accessing data.
It is reconciling it.
When Progress Collides with Reality
Transformation, when uneven, creates its own friction.
A ministry may implement a modern platform designed for integration. But if the departments it depends on are operating with incompatible data or outdated systems, progress slows—or reverses.
“You can deploy something new and still have to rework it,” Jones says, “because another part of the system isn’t ready—whether that’s data quality, structure, or process.”
This is the reality of large-scale change.
And it is precisely why the Prime Minister’s emphasis on infrastructure is not cautionary—it is foundational.
Electronic invoicing does not simplify a fragmented system.
It exposes it.
Security Before Function
Among the most important elements raised in the Prime Minister’s remarks was the need for public key infrastructure (PKI)—a critical component in securing digital transactions.
PKI ensures that data can be trusted. That identities are verified. That records cannot be altered without detection.
In the context of electronic invoicing, this is non-negotiable.
Invoices are financial instruments. They carry legal and economic weight. They move across institutions and must remain secure at every stage.
Without robust security, the system cannot function with confidence.
And like integration, security cannot be layered on at the end. It must be embedded from the beginning.
The Acceleration of AI
If the challenges are structural, the tools available to address them are evolving rapidly.
Artificial intelligence offers a way to accelerate one of the most complex aspects of digital transformation: making sense of fragmented, inconsistent data.
“What would have taken years can now be significantly compressed,” Jones observes.
“If the backbone is in place, AI can help map, clean, and connect data across systems much faster than traditional approaches.”
But the emphasis remains on structure.
AI does not replace architecture. It depends on it.
“It’s an amplifier,” Jones adds. “It works best when there’s a clear framework—when the system has somewhere for that intelligence to operate.”
Without that framework, AI risks becoming another layer within the same fragmented landscape.
Building What Doesn’t Yet Exist
The path forward is not defined by a single project or initiative. It requires coordinated effort across multiple fronts.
A national digital architecture must define how systems interact. Data standards must be established and enforced. Infrastructure must be secure, resilient, and scalable. Ministries must align—not just technically, but operationally.
And behind all of this sits a less visible, but equally critical requirement: capability.
Because systems do not implement themselves.
Building While Moving
There is, however, another way to think about this transition—one that does not rely on waiting for perfection before progress begins.
It is possible to run two tracks at once.
Electronic invoicing can move forward as a visible reform, while the deeper work of building the national digital backbone continues beneath it. The challenge is not in doing both—but in ensuring they are aligned.
“It’s like running two trains on the same line,” says Dean Jones. “One is the backbone—the core infrastructure. The other is the system you want to deliver, like e-invoicing.”
“The key is making sure the backbone train is slightly ahead—so that when the second train arrives, the track is already there.”
This is where architecture becomes critical.
With the right design, the same framework can guide both efforts. The same standards, the same data structures, the same security principles. Not two separate journeys—but two coordinated movements toward the same destination.
Without that alignment, systems risk arriving at different points—out of sync, incompatible, and difficult to reconcile.
With it, progres
The Human Dimension
Technology may be the focus, but people determine the outcome.
Large-scale transformation depends on adoption—on the ability of individuals and organisations to understand, use, and sustain new systems.
“This is the bigger task,” Jones notes. “Not just building systems, but building understanding.”
That means training at every level. Not once, but continuously. Staff must be equipped to operate new platforms. Leadership must understand how to guide change. And those responsible for training others must themselves be supported.
“Training the trainers becomes essential,” he adds.
Because without that continuity, even the most sophisticated system will struggle to deliver.
More Than a Policy Shift
Electronic invoicing may appear, on the surface, as a discrete reform—technical, administrative, measurable.
But in reality, it represents something broader.
A shift in how government functions. A move toward integration, transparency, and efficiency. A recognition that modern economies depend not just on policy, but on systems that work together seamlessly.
It is not the beginning of transformation.
It is a marker of progress within it.
A Rare Alignment
One detail in the Prime Minister’s remarks stands out: there is consensus.
Across political lines, there is agreement that electronic invoicing is necessary.
That alignment matters.
Because the transformation required to support it—deep, structural, and long-term—cannot be achieved in isolation or interruption. It requires continuity. It requires shared commitment.
And it requires a clear understanding of what must come first.
The Shape of What Comes Next
Jamaica stands at a point where ambition is no longer the constraint.
The vision is clear. The direction is set. The tools are available.
What remains is the work of connection.
To build a system where ministries do not operate in parallel, but in coordination. Where data flows with purpose. Where infrastructure supports, rather than limits, progress.
“We need the right backbone,” Jones says. “The right map. The right team.”
From there, integration becomes possible.
And once integration is achieved, systems such as electronic invoicing become not complex—but natural.
In the end, the Prime Minister’s remarks were not a hesitation.
They were a recognition.
Before Jamaica can layer on the visible features of a modern digital economy, the structure beneath must be built—and built well.
But that does not mean standing still.
It means building with intention, so that what is created today connects seamlessly with what comes next.
Because when that structure is in place, the system does more than function.
It works as one.