CASE STUDY · PARTNER CHANNEL

Built once, deployed by the partner.

A software or service provider that wants to offer eInvoicing has two options: become a certified access point, or put someone else's behind its own product.

Region
Australia and New Zealand
Sector
Software and service providers — accounts payable automation, customer communications and document delivery, accounting and advisory
Delivery scope
Certified Peppol access point and Service Metadata Publisher operated on the partner's behalf; one integration build per partner in the idiom that partner already works in — emailed PDF, scheduled file transfer, or a connector embedded in the partner's own product; document validation and format translation; supplier enablement delivered alongside where a partner asked for it; ongoing operation and support of the connector
Technology
Valtatech Peppol access point and SMP, Valtatech integration middleware
Australia & NZPeppolIntegrationPartner channel
1Integration build per partner
3Ways a partner connects
IndependentPartner deployment to end customers

The challenge

Becoming a certified Peppol access point is not a feature. It is accreditation, a Service Metadata Publisher, document validation against evolving specifications, network monitoring and a support obligation that does not stop at five o'clock. For a provider whose product is accounts payable automation, customer communications or accounting services, that is a business they did not intend to be in.

The alternative is to tell customers who are being asked for eInvoicing — by a government buyer, by a mandate, or by a large counterparty — that it is not something they offer. In several of these markets that answer loses the account rather than just the feature.

What we did

One build, in the partner's own idiom. The constraint that matters is not technical capability, it is what the partner already has. So each connector meets the partner where it is rather than asking it to adopt ours.

An accounting and advisory firm whose invoices are produced as PDFs sends them to a dedicated address; they are converted into compliant network documents and delivered. No change to how the firm bills.

A customer communications and document delivery provider already moves files on a schedule, so the connector reads from file transfer — the integration surface its platform was built around — rather than requiring new API development.

An accounts payable automation vendor wanted eInvoicing inside its own product, so the connector sits behind that product's interface and the end customer sees the vendor's software, not ours.

Then the partner runs it. This is the part that distinguishes a channel from a referral. Valtatech-certified partners implement and deploy eInvoicing services independently: once a partner's connector is live, that partner onboards its own customers at its own pace, and does not need us in the contract to win the next one.

Supplier enablement where it was asked for. Getting a buyer onto the network is the easy half; getting their suppliers to send structured documents is the half that stalls. Where a partner wanted that capability for an end customer rather than building it themselves, we ran the enablement programme behind them.

Operated, not just delivered. The access point and SMP are ours to run. Specification changes, certification, monitoring and escalation stay with us, which is the entire reason a partner chose this route rather than building.

THE OUTCOME

Several providers across Australia and New Zealand now sell eInvoicing as part of their own offering, each to multiple end customers, on infrastructure they did not have to build or accredit.

Valtatech is software vendor agnostic. See our Peppol eInvoicing service →

Valtatech-certified partners implement and deploy eInvoicing services independently. Once a partner's connector is live, they onboard their own customers at their own pace, without a Valtatech contract or configuration step in between.

For a provider evaluating this, the questions worth asking are how much of the accreditation, specification tracking and support obligation transfers, and whether the integration meets the systems you already run.

Want eInvoicing in your own product?

Talk to us about putting a certified access point behind your offering.

Start a conversation

← All case studies