Operating model

How SolaBill Works with Orchida

A clear division between customer software and the regulated Accredited Service Provider function. The integration remains subject to signed agreements, sandbox acceptance, customer appointment and production approval.

Last updated 18 August 2026

Customer responsibilities

The customer remains responsible for complete and accurate commercial inputs.

Provide legal identity, tax registration, buyer, supply, payment and line-item data.
Approve invoices and corrections through authorized users.
Maintain ERP and business records required by applicable law.

SolaBill responsibilities

SolaBill is the customer workflow and integration layer.

Portal, customer API, ERP integration, drafts, approvals and tenant access controls.
Ordinary business-data checks, idempotency, workflow evidence and customer exports.
Display separate provider, exchange, authority and receiver outcomes exactly as returned.

Orchida responsibilities

After appointment and production approval, the eligible Orchida entity performs the regulated provider functions.

Generate and validate the regulated PINT-AE document, including the mandatory tax-invoice structure.
Perform regulated Peppol exchange and required authority reporting.
Return provider evidence and statuses for SolaBill to retain and display.

Current boundary

SolaBill is not independently accredited, is not a Peppol Access Point and does not report directly to the FTA. Production traffic remains disabled until every contractual and technical gate is complete.