Payment evidence
Receive or retrieve payment state from available payment and banking extensions.
Solution · Collection & reconciliation
Know what is paid. Act on what remains due.
Bring the invoice, observed payment and its application together. Operators can see what is settled, what remains due and whether the next step is a reminder, a review or resolution of a genuine exception.
INVOICEINV-1042€8,400
OBSERVED PAYMENT€5,000
APPLIED TO INVOICE€5,000
Remaining due€3,400
Partial payment · follow up
Reconcile
Keep payment observation separate from how it settles an obligation
A payment is an observed financial fact; a payment application explains how that amount is allocated to an invoice or other obligation. Keeping those concepts separate supports partial payments, multiple allocations and remaining-balance reasoning.
Extensions can bring provider payment evidence into the flow, while the canonical payment and reconciliation model stays stable for downstream processes.
Application
Relate observed money to the obligation it settles instead of treating a provider transaction as the invoice itself.
Remaining action
Route to close, follow-up, exception handling or human review from the reconciled business state.
Systems involved
One journey, several authorities.
Ormuz coordinates these boundaries rather than erasing them.
ERPInvoice
PAYMENTObserved funds
ORMUZAllocation
COMMSReminder channel
HUMANException
Use the channel that matches the stage of collection
The marketplace currently includes SMTP and Twilio for notifications, Maileva for postal mail and AR24 for registered communications. A process can escalate channels deliberately rather than embedding communication logic in the invoice system.
What this changes in the journey
A real “Payment reminder” process template is distributed in the repository. It uses an SMTP configuration and is a starting point to review and customise — not proof that every collection strategy is already packaged as a template.
Make disputes and ambiguous cases visible instead of retrying blindly
A failed collection action may mean missing data, a provider error, a partial settlement or a genuine commercial dispute. The process can distinguish those states and route the next action accordingly.
Handle a dispute as a distinct step: gather the supporting information, request a review and resume collection according to the outcome.
Measure during a pilot
Evaluate the change on your real operation.
Choose the measures that matter to your operation and compare them before and during your pilot.
Unallocated payment share
Measure how much observed money still lacks a clear application to an obligation.
Exception resolution time
Track how long partial payments, mismatches and disputes stay unresolved.
Manual follow-up share
Measure which collection actions still require operator intervention.