Skip to content

Implementation

Choosing a provider is a decision. Getting it working is a project.

Most of what goes wrong in e-invoicing happens after the provider is appointed, in the gap between a signed contract and a system that actually transmits clean invoices at month-end. We run that middle, whether you appointed your provider through us or before you had ever heard of us.

How the work runs

01

Discovery and current-state review

Your systems, your invoice data, your document types, and the people who will have to live with the result.

02

Requirements definition

What the connection has to do, written down before anyone builds anything, so the provider is held to a specification rather than a conversation.

03

Architecture and data mapping

Your invoice fields mapped into the required structured format, including the fields your system does not currently capture — which is usually where the real work is.

04

Provider coordination

We sit between your team and your provider's onboarding process, in their technical language and yours, so your finance team is not translating.

05

Integration and validation

Building and proving the connection, then validating against real invoice cases including the ones constructed to fail.

06

User acceptance testing

Your team confirms it works the way they actually invoice, not the way the process diagram says they do.

07

Go-live and staged cutover

In stages, with a rollback position, rather than a single overnight switch across every entity.

08

Stabilisation

The first full month-end after go-live is the real test. We stay through it.

Where the line sits

What we do. What your accredited provider does.

This is the question every prospect eventually asks, usually three conversations in: if I already have an accredited provider, what is left for you to do? The honest answer is that appointing a provider settles one decision out of a project with many. Here is the split.

Your business

What stays yours

  • Your ERP or accounting system
  • Your finance team and their workflow
  • Your invoice data and customer records
  • The commercial relationship with your provider

CoreholdSolutions

What we take on

  • Establishing what the regulation requires of your business specifically
  • Defining requirements before any provider conversation
  • Scoring and selecting the accredited provider that fits your systems
  • Mapping your invoice data into the required structured format
  • Coordinating the integration with your provider and your IT side
  • Testing, including the cases designed to fail
  • Go-live planning and staged cutover
  • Monitoring, rejection resolution and reconciliation after go-live

Your accredited provider

What only they can do

  • Transmitting your invoices across the network
  • Receiving invoices addressed to you
  • The reporting leg to the Federal Tax Authority
  • Everything the accreditation itself authorises

We are not an accredited service provider and do not perform any of the functions in the third column. That separation is deliberate: it is what allows us to advise on which provider you should appoint without a commercial answer waiting at the end of it.

So why do I need you if I already have a provider?

Because choosing a provider is a procurement decision, and what follows it is an integration project. Your invoice data still has to map correctly, validate against real cases, survive testing, and cut over without breaking month-end — and somebody has to own that across finance, IT and the provider. That is the work.

Already appointed a provider?

That is a normal starting point and it changes nothing about how we work. We are not going to reopen a decision you have already made and paid for. We work with whichever accredited provider you have appointed, take the specification from there, and get the integration done.

Already have an ERP?

Having an ERP is not the same as having a completed e-invoicing implementation. Most systems can be made to work; the question is what has to be configured, mapped, tested and changed operationally to get there — and that answer is specific to your instance, not to the product name.

Already have an accountant?

Keep them. Your accountant handles accounting and tax, and nothing here changes that. This is a systems integration project that happens to be driven by a tax regulation, and it needs a different kind of hands.