Referral partner
Introduce suitable organisations or clients; handoff, roles and follow-up are agreed per case.
DYNAFIS · PARTNER
Roll out Dynafis across multiple clients or mandates
If you support multiple businesses with e-invoicing and document processes, Dynafis can become a repeatable solution across your client base. General Informatics structures the partner role and technical rollout; current product, compliance and pricing details remain with Dynafis.
Who the model fits
- Tax and accounting practices serving multiple clients
- Bookkeeping and digitalisation service providers
- IT providers, ERP/accounting integrators and implementation consultants
- Partners that want to introduce e-invoicing and document workflows repeatedly across customers
Partner roles
Partner roles
Implementation / solution partner
Support rollout, integrations, data flows, training or support within your own client relationship.
Practice / multi-client multiplier
Evaluate and structure a repeatable Dynafis rollout across several clients or mandates.
Strategic integration partner
For recurring integrations, shared solution building blocks or larger rollout scenarios with clear responsibility boundaries.
How collaboration starts
How collaboration starts
Describe the partner role, target market and typical client context.
GI and Dynafis review fit, scope and required product or integration components.
Define responsibilities for rollout, support, integration and client communication.
Start with a concrete client or small rollout and validate the operating model.
Standardise rollout, handoffs and integrations when demand becomes recurring.
Collaboration model
- Referral, implementation and multi-client rollout are treated as distinct models.
- Commercial terms depend on partner role, scope and repeat potential.
- No public commission or margin promise is made without an approved agreement.
- You can start with one concrete client case without first setting up a large partner programme.
Product boundary & responsibilities
- The GI partner page stays intentionally concise; product details, pricing, compliance information and help remain on Dynafis.
- Partner and support responsibilities are defined before rollout.
- Integrations are only committed after the interface and concrete scope have been reviewed.
- Regulatory deadlines are not hardcoded on this page.
- Client data is handled only within the agreed operating and permission model.
Frequently asked questions
Is this only for tax practices?
No. Bookkeeping providers, IT and integration partners, and consultants with recurring client projects can also fit.
Can I roll Dynafis out to multiple clients?
Yes. The multiplier path is designed for repeatable rollout; the model is structured around client segment, scope and partner role.
Is there a fixed public commission?
No. Commercial terms are agreed from the concrete partner and rollout model.
Where are authoritative product and compliance details?
On the current Dynafis website and documentation. The GI partner page deliberately does not duplicate them.
WORKING MODEL
Clear boundaries. Clean handoffs. Engineering escalation when it is needed.
Clear responsibilities
Roles, communication and handoff points are agreed for each engagement.
NDA available
Confidentiality can be agreed for a project or partner relationship.
Customer protection & white-label
Agency models can include agreed customer protection and background delivery.
Controlled credentials
Access is used only as needed and through agreed secure channels.
Project or recurring
One-off projects and recurring cooperation are both possible, depending on the need.
Engineering escalation
Difficult cases can move from standard delivery into deeper technical analysis and implementation.
DYNAFIS · PARTNER
Review a Dynafis partnership
Describe your organisation, client context and preferred partner role. We will assess a sensible entry point without making a meeting the first requirement.