ormuz
Home/Integrations/Mondu/Nodes/Get invoice (Mondu)
MonduRouteurStable

Get invoice (Mondu)

Retrieves the Mondu state of an Ormuz invoice and routes the process to the corresponding branch.

Vue d’ensemble

Get invoice (Mondu) tracks a specific invoice from the Ormuz invoice already submitted to Mondu.

Routes allow handling an open, overdue, complete, canceled, reopened, or unexpected invoice state.

  • The designer supplies only the Ormuz invoice.
  • Retrieval does not alter the Ormuz invoice.
  • A new or unknown state is routed to other.

Typical scenario

After the due date, a process retrieves an invoice. The late route opens operational follow-up, while complete closes the check.

Quick start

Link an Ormuz invoice already submitted to Mondu.

Prerequisites

  • Persisted invoice
  • Invoice already submitted with Create invoice (Mondu)
Configuration example
ParameterBindingRole
invoiceinvoiceTracked Ormuz invoice
Key point This node expects a regular type = invoice invoice, not a credit note.

Decision routes

open

Invoice open

The Mondu invoice is active and remains payable by the buyer.

Recommended actionContinue due-date tracking and reconciliation.
late

Invoice overdue

The due date has passed and the invoice remains open in Mondu.

Recommended actionStart the configured overdue-receivable follow-up and monitor Mondu events.
complete

Invoice complete

The invoice is considered complete in the Mondu lifecycle.

Recommended actionClose operational tracking and retain the result for reconciliation.
canceled

Invoice canceled

The Mondu invoice was canceled.

Recommended actionCheck that the Ormuz invoice state and any credit notes correctly reflect this cancellation.
reopened

Invoice reopened

A previously completed invoice is active again in Mondu.

Recommended actionReactivate tracking and analyze why it reopened.
other

Unknown state

The invoice state returned by Mondu does not match known routes.

Recommended actionDo not close automatically. Analyze the returned Mondu state before adapting the process.
Attention Never treat other as complete by default.

Data resolution

The node automatically derives required data from linked Ormuz objects.

DataSource or rule
Retrieved Mondu invoiceinvoice.id identifies the invoice concerned
RouteCurrent Mondu result

Parameters 2

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.

Outputs 2

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.

selected_routeenum
Route chosen from the business result returned by Mondu.

Behavior

Identify the invoice

The node starts from the already-submitted Ormuz invoice.

Retrieve its Mondu state

Mondu returns the invoice state, amounts, and dates.

Route the process

The result selects one of the six documented routes.

Limits and responsibilities

  • The node does not create a missing Mondu invoice.
  • It does not modify the status or balance of the Ormuz invoice.
  • It does not automatically retrieve associated payouts.

Troubleshooting

Mondu invoice not found

Submit the invoice first with Create invoice (Mondu).

Invalid document type

Use a regular invoice; credit notes have their own node.

Route `other`

Analyze the returned Mondu state before changing your logic.