Two providers can both offer e-invoicing and still leave your finance team with very different amounts of work. The quotation is only part of the decision. Your team also needs to know how data reaches the provider, what happens when an invoice fails and who helps resolve it.
Start with the official checks
Verify the provider’s current status against the Ministry of Finance ASP list. The Ministry updates this list periodically. Accreditation should be checked for the relevant legal entity, rather than assumed from a partner’s logo.
The Ministry’s provider-selection guide, dated 23 February 2026, covers experience, product ownership, integration, data management, security, service levels, pricing and scalability. Use the current portal and amended legislation alongside that guide. This article adds a suggested evaluation exercise; it is not a provider ranking.
Write a one-page brief before requesting demos
Describe your billing systems, transaction volumes, business entities, currencies and the person who will own the process. Note the systems you cannot change easily. Include manual invoices and anything your normal export does not cover.
Then separate what is essential for launch from features you may want later. A simple initial workflow with a clear owner may serve you better than a long list of untested add-ons.
Give shortlisted providers the same practical exercise
Prepare a small set of synthetic invoice examples based on your business. Include a clean ordinary transaction, a missing field, a duplicate reference and a correction scenario relevant to your operations. Ask each provider to explain the proposed handling, assumptions and work your team must do.
Watch what the accountant can see. Is an error understandable? Can they find the original transaction? Can they tell whether an item needs attention without asking a developer? Record the answers while they are fresh.
Ask six questions that make comparison easier
- What exactly connects to our system? Ask for a written integration boundary and the responsibilities on both sides.
- Who supports us? Identify the accountable support team, escalation route and contractual response arrangements.
- Where does our data go? Ask how storage, access and subcontractors fit your organisation’s requirements.
- What changes the bill? Compare setup, integration, volume, support and change costs on a common scenario.
- What happens when something fails? Ask for the proposed detection, investigation and recovery process.
- How do we leave or change? Clarify export, transition assistance and contractual restrictions before committing.
Use a comparison sheet with evidence
For each provider, write the answer, the evidence you saw, the unresolved question and its owner. A simple “demonstrated / needs confirmation / not suitable” assessment is often more useful than a score to two decimal places.
For example, if your team depends on an older ERP, a connector claim needs a test against your actual configuration. If your main risk is unresolved exceptions, place more emphasis on the review workflow. These are choices for your situation, not universal weights.
Put the delivery plan beside the commercial agreement
Before signing, identify the milestones that depend on your team: cleaning records, agreeing mappings, making systems available and reviewing test results. Ask the provider to confirm dependencies and assumptions in writing. A target date without those details is difficult to manage.
Check your applicable appointment and implementation dates separately using our October readiness checklist and the latest official notices. Choosing a provider does not complete the implementation.
Share your systems and e-invoicing questions with Finaxil if you want help preparing the finance brief, cleaning the data or planning the hand-offs. We have not independently assessed or endorsed the providers on the Ministry’s list.
Sources checked on 24 October 2026. General preparation guidance; confirm your own requirements and contract terms with appropriate advisers.
