Global E-Invoicing Framework

A group running Dynamics 365 Finance & Operations across several markets rarely faces one e-invoicing problem. It faces one per country, each with its own schema, its own accreditation route, its own clearance or periodic-reporting model, and its own mandate date set by a tax authority that has no interest in your release calendar.

The usual response is a sequence of one-off localisation efforts: a bespoke XML generator for one market, a middleware flow for the next, a portal upload driven from a spreadsheet for a third. Each was reasonable in isolation. Together they mean nobody can answer the plain questions — how many invoices were rejected last month and why, which legal entity is behind on archiving, what happens when a signing certificate expires on a Friday evening, who re-submits the 40 documents that failed while the provider was down — because the answers live in different systems and in different people's heads. Every new market restarts the cycle, and every audit becomes an archaeology exercise.

The Global E-Invoicing Framework is a build-to-order X++ application that ECOSIRE designs and builds for your environment. Nothing here is a shrink-wrapped download; we scope your countries, your providers and your document flows, quote a fixed price, then build and deliver the model into your own LCS pipeline.

What ECOSIRE builds

Country profiles and format governance

A country profile is a first-class record in F&O, not a hard-coded branch. Each profile binds a country/region to the Electronic reporting format and model-mapping configurations that produce its outbound document, the mandatory field set that must be present before a document may leave, the clearance model in force (pre-clearance, post-clearance or periodic reporting), the tax registration identifiers required, and the legal entities it applies to. Profiles are effective-dated, so a mandate that starts on a known date does not require a code change, and multi-entity groups can run two rulesets for the same country while a phased mandate rolls out.

Service provider connectivity

One connector abstraction, several concrete implementations. Endpoints, timeouts, authentication mode and payload envelope are configuration; the code path is shared. Credentials and signing certificates are retrieved from Azure Key Vault rather than stored in tables or attachments, and certificate expiry is surfaced as a warning on the workspace well before it becomes an outage. Where a market requires digital signature before transmission, the signing step is a defined extension point so a change of provider does not become a rebuild.

Submission, status and retry

Every document enters an outbound queue with an explicit lifecycle: pending, validating, submitted, accepted, rejected, cancelled, archived. Submission runs on the SysOperation batch framework with recurrence, bounded parallelism and backoff on retry, so a provider outage produces a queue that drains when the service returns rather than a morning of manual re-keying. Rejections are stored with the raw provider response alongside a readable reason, and re-submission after correction is a controlled action, not a delete-and-repost.

Clearance write-back and document output

Where a market issues a clearance identifier, UUID, hash or QR payload, the framework writes it back to the posted invoice record and makes it available to print management, so the customer-facing PDF carries exactly what the authority issued. Extensions to posted invoice handling are implemented through Chain of Command and event handlers on the standard posting classes — no overlayering, and no forked copies of standard objects to maintain across updates.

Archiving and audit evidence

Submitted payload, provider acknowledgement and rendered document are retained together against the invoice, with configurable retention per country. A Data management framework export project produces a period pack for auditors without anyone opening a developer tool, and the full trail is reachable as data entities and OData for whatever downstream evidence store you already run.

Operations and monitoring

A workspace gives finance and IT the same picture: volumes by legal entity and country, aged rejections, documents blocked on missing master data, certificates approaching expiry, and the last successful call per provider. Business events fire on acceptance and rejection so Power Automate or your service desk can pick up exceptions without polling the database.

Who this is for

Groups operating multiple legal entities on F&O in markets that already mandate electronic invoicing, or that have a mandate published with a live date. It is equally aimed at organisations that already built one or two country solutions and now need the third without repeating the pattern. If you operate in a single country with a stable, well-served format, standard platform capability plus a provider connection may be all you need, and we will say so during scoping rather than sell you a framework.

How delivery works

1. Scoping call. We walk through your legal entities, countries, document types (sales invoices, free text invoices, project invoices, credit notes), current providers or accreditation status, and your F&O version and update cadence. 2. Fixed quote. You receive a written scope naming every country profile, connector and document type included, the assumptions behind them, and the price. Countries outside that list are quoted separately rather than absorbed silently. 3. Build. We develop the model as X++ extensions in a dedicated model and package, with Electronic reporting configurations versioned alongside. You get progress checkpoints, not a black box. 4. Install in test. The deployable package goes into your sandbox through your LCS pipeline. We configure the profiles with you, run end-to-end submissions against provider test endpoints, and work through the exceptions that only real master data produces. 5. Production. After your sign-off, the same package is promoted through your normal release process. We are on the call for the first production submissions. 6. Support. A defined support window follows go-live for defects and configuration questions, with an option to extend for new markets or provider changes.

What we do not claim

This is software we build for you, on request. There is no instant download and no free trial, and typical lead time is two to four weeks from an agreed scope. We are not a tax authority, an accreditation body or a certified service provider, and we do not resell provider subscriptions — you keep that contract, and the framework talks to it. Legal and tax determinations remain yours and your advisers'; what we deliver is the governed mechanism that turns those decisions into compliant, auditable, repeatable transmissions from F&O.