Mexico CFDI E-Invoicing & Complementos

The problem

Mexican CFDI is not a document format bolted onto an invoice — it is a lifecycle. A sales invoice must be built to the CFDI 4.0 schema with the correct UsoCFDI, RegimenFiscal, ObjetoImp and product/service keys, signed, sent to an authorised PAC for stamping, and stored with the returned UUID and timbre. Then a customer payment triggers a complemento de pago referencing every UUID it settles. Then a shipment of goods on public roads triggers carta porte with route, vehicle, operator and merchandise detail. And a mistake cannot simply be reversed: cancellation runs through an acceptance workflow with a stated reason and, for most reasons, a substituting UUID.

Dynamics 365 Finance & Operations handles the accounting side of all of this cleanly. What breaks in practice is the state machine around it: which invoices are stamped, which payments are missing their complemento, what happens when the PAC times out after signing but before the response is stored, and how a warehouse supervisor gets a carta porte for a load that was picked twenty minutes ago. Getting that wrong does not just create rework — an unstamped invoice is not a fiscal document, and a payment without its complemento is an open exposure at audit.

What ECOSIRE builds

ECOSIRE builds a CFDI extension for your F&O environment as X++ extension code in its own model — event handlers, chain of command, table and form extensions, no overlayering — deployed as a package through your LCS or Azure DevOps pipeline.

CFDI 4.0 generation and stamping

We map sales invoices, free text invoices, project invoices and credit notes to the CFDI 4.0 XML, including the emisor/receptor blocks, tax breakdown for IVA and retenciones, ClaveProdServ and ClaveUnidad per line, and the catalogue-driven fields. The stamping call to your chosen PAC runs through a service layer with a durable request record: the request is written before the call, so a timeout after signature never loses a UUID. The returned TimbreFiscalDigital, UUID, certificate serial and stamped XML are stored against the invoice and made available to the printed document and to your PDF delivery.

Complemento de pago

Customer payments in the settlement journal generate the payment complemento, resolving every settled UUID, the partiality number, previous and current balances and the currency handling. A batch job identifies payments that require a complemento and have not produced one — the single most valuable control in the whole build, because that gap is otherwise invisible until an audit.

Carta porte

For goods movements, carta porte is generated from the shipment or transfer order using warehouse data already in F&O: items and quantities from the load, plus configured vehicle, operator, permit and route data. Where your operation uses the warehouse mobile app, we make the stamped carta porte status visible so a load is not released without it.

Cancellation workflow

Cancellation is implemented as a controlled process: reason code, substituting UUID where required, submission to the PAC, and storage of the acceptance or rejection response. The related financial reversal in F&O stays tied to the fiscal outcome rather than running ahead of it.

Operations and data

A workspace shows unstamped invoices, payments missing complementos, pending cancellations and stamping errors with the PAC's message text. Batch jobs on the standard F&O batch framework drive retries with bounded, idempotent logic. Everything is exposed through data entities for OData and the Data management framework, so your Power BI or Power Platform layer reads one source of truth.

Who this is for

Companies operating one or more Mexican legal entities on F&O — particularly manufacturers, distributors and any business moving its own goods on public roads, where carta porte turns a finance obligation into a logistics one.

How delivery works

Nothing here is pre-built. We start with a scoping call covering your legal entities, PAC, document types, whether carta porte and complemento de pago are in scope, and how your shipments are structured. You receive a fixed quote against that written scope. ECOSIRE then builds against your F&O version, delivers a deployable package, and installs it in your test or sandbox environment, where we stamp real document shapes against your PAC's test environment with your team present. After sign-off it goes to production through your normal release process, followed by a support window for defects and for changes the SAT publishes to the schema or catalogues.

Lead time is typically two to four weeks from signed quote, longer where carta porte and multiple entities are all in scope.