MonduConnecteurStable

Create invoice (Mondu)

Submits an issued Ormuz invoice with its PDF to Mondu and attaches it to the corresponding financed order.

Ormuz invoice

Mondu invoice

Vue d’ensemble

Create invoice (Mondu) materializes the receivable after invoice issuance. The designer supplies only the Ormuz invoice; the associated order, Mondu order, and primary document are derived automatically.

Submitting the invoice lets Mondu enter the merchant payout and buyer-collection lifecycle. Actual timing then depends on the Mondu contract.

The invoice must have type = invoice and an already-issued status: issued, sent, or received.
It must be linked to exactly one Ormuz order financed by Mondu.
The sum of non-canceled Mondu invoices cannot exceed the order amount.
An already-submitted invoice is not created a second time.

Typical scenario

A EUR 1,000 confirmed Mondu order ships in two parts. Two invoice.issued events submit invoices for EUR 600 and then EUR 400. A third invoice for EUR 100 would be rejected because the cumulative amount would exceed the Mondu order.

Quick start

Link only the issued invoice; the node automatically derives its order and primary document.

Required invoice

type = invoice
status ∈ {issued, sent, received}
Positive amount and consistent currency
PDF document_file present

Required relationships

Exactly one linked order
Order already financed by Mondu
Mondu order confirmed or in a compatible execution state

Configuration example

Parameter	Binding	Role
`invoice`	`issued_invoice`	Invoice issued
`proof_of_delivery`	`delivery_proof`	Optionnel

Key point An invoice linked to zero or multiple orders intentionally fails. The node never arbitrarily chooses one order from a many-to-many relationship.

Process example

invoice.issued event

Transmettre une facture (Mondu)

Invoice submitted to Mondu

At issuance, provide only the Ormuz invoice; the node derives the financed order and document to send.

Data resolution

The node automatically derives required data from linked Ormuz objects.

Data	Source or rule
Order Ormuz	invoice → orders relationship → exactly one result
Mondu order	`order.id` identifies the financed order
Invoice reference	`invoice.id` only
Document principal	`invoice.document_file`
Amount, tax, and currency	Invoice monetary fields
Lignes	Persisted invoice lines
Proof of delivery	`proof_of_delivery` parameter, when supplied

Parameters 4

Contexte principal

Objects and configuration that determine the Mondu operation.

extension_config_idRequisref(extension_config:mondu)

Active Mondu configuration used for the operation. It notably defines environment, default payment method, net term, language, and optional marketplace settings.

invoiceRequisInvoice

Persisted Ormuz Invoice. Depending on the node, it is used either to submit an issued invoice or retrieve the corresponding Mondu invoice.

Documents and shipping

Supporting documents and information used during invoicing.

proof_of_deliveryOptionnelFile

Optional delivery evidence attached to the invoice. The file must belong to the same merchant and be accessible to the process.

shipping_infoOptionnelobject

Optional shipping information sent with the invoice. Use only properties expected by your Mondu contract.

Outputs 3

Objet Mondu

Primary Mondu object produced or refreshed by the node.

invoiceMondu invoice

Mondu invoice including identifier, state, amount, currency, and associated order.

Decision and control

Information used to direct the next process step.

createdboolean

Whether the node created a new Mondu object. false means the existing object was found and reused.

Other outputs

extension_object_mappingextension object mapping

Durable mapping between the created or reused Mondu object and the Ormuz object forming its business anchor.

Behavior

Validate the invoice

Type, issued status, amount, tax, and currency must be valid.

Avoid duplicates

An already-submitted invoice is returned with created = false.

Identify the unique order

The invoice must be linked to exactly one Ormuz order.

Check Mondu terms

The order must be confirmed or in a compatible state, with the same currency.

Check the cumulative amount

The total of non-canceled invoices, including the new invoice, must not exceed the order.

Submit the invoice

The primary PDF, optional proof, and invoice lines are sent to Mondu.

Make the invoice available

The returned Mondu invoice can then be tracked or corrected by a credit note.

Limits and responsibilities

The node does not issue the invoice in the ERP or change its Ormuz status.
It does not support one invoice consolidating several Mondu orders.
It does not guarantee a precise payout date.
It does not automatically create a credit note when a correction is needed.

Troubleshooting

No linked order

Create the invoice → order relationship before retrying.

Multiple linked orders

Split the invoice or define a compatible business model; Mondu requires a single order.

Invoice not issued

The invoice must have reached issued, sent, or received in its normal lifecycle before submission to Mondu.

Document missing or not PDF

Attach a valid PDF in invoice.document_file.

Amount exceeds the order

Check invoices already submitted, cancellations, and the order amount.

Different currency

The invoice must use the same currency as the Mondu order.