Hanuma Global
Services Consulting & Training Resources Insights & articles Country mandate tracker Readiness scorecard Our global reach Company About us How we work Helios ↗ Contact us
FAQ

Questions, answered.

The things we get asked on nearly every project — about compliance, formats and the network, how we work, and how this site handles your data.

E-invoicing basics

What is e-invoicing compliance?

It means issuing, exchanging and reporting invoices in the exact electronic format and process a country's tax authority mandates — the correct syntax (UBL, CII, PINT), the validation rules, and the control model (clearance, reporting or exchange). We help you meet those requirements in every market you operate in.

Which countries require e-invoicing?

Dozens now do, and more each year — Italy, India, Saudi Arabia, Malaysia, Poland, France, Germany, Belgium and many others. Our live country-mandate tracker shows the status, required format and timeline for each, with sources.

What is the difference between e-invoicing and e-reporting?

E-invoicing is about exchanging the invoice itself with your customer in a structured format. E-reporting is about sending transaction data to the tax authority. A mandate can require one, the other, or both — and they are often on different dates and scopes, so we plan them separately.

What are Peppol and PINT?

Peppol is an international network for exchanging compliant documents through certified access points, using a four- or five-corner model. PINT (Peppol International) is the global invoice specification, localised by country profiles. We work across the Peppol network and every PINT specification.

Formats & standards

What e-invoice formats do you support?

Any-to-any conversion across UBL, CII, PINT, Factur-X and national syntaxes such as XRechnung, ZUGFeRD and FatturaPA — delivered with mapping documents, sample files and QA so the output is verifiable, not just plausible.

What is EN 16931, and do we need to care about it?

EN 16931 is the European standard that defines the meaning of a core invoice, independent of syntax. Most EU mandates build on it, so getting your data mapped to the EN 16931 model once makes each national variant an adapter rather than a rebuild. Our guide to the layers explains how it fits with UBL and PINT.

Our invoice passes validation but still gets rejected — can you help?

Yes — this is one of the most common things we're called in for. A local Schematron pass is only the first of several checks, and the gap is usually a code-list version, a national rule or a counterparty difference. We wrote up the six places it usually hides.

Working with us

Who do you work with?

Service providers, Peppol authorities, enterprises going cross-border, and startups building e-invoicing solutions.

How does an engagement start?

Usually with a scoped mandate analysis: we assess your specifications against the target country's requirements and hand back the specification, the mapping and the effort — in weeks, not quarters. See how we work for the engagement model, or tell us where you are stuck.

Can you help us go cross-border?

Yes. We assess your current setup against each target country's mandate, design the solution and reduce compliance risk, so you can enter new markets without discovering the requirements the hard way.

Do you provide training?

Yes — we offer consulting and training for teams that want to build the capability in-house, from EN 16931 and Peppol fundamentals to hands-on validation and mapping.

Data & this site

Do you track visitors or use cookies on this site?

No third-party analytics and no tracking cookies. We keep a privacy-preserving pageview count in which your IP address is turned into a country code on our own server and immediately discarded — no profiles, no sessions. The privacy page has the detail, and our global reach page shows exactly what we publish.

Still have a question?

Ask a specialist directly — if it is a good question, it usually becomes the next article or FAQ.