Customer story · Aviation
A regional airline
Reservation-to-ERP invoice export for a regional airline
Deterministic data plumbing between systems that were never designed to talk. No AI in the money path.
Executive summary
The situation
Reservation exports, ancillary-service records and online-payment CSVs had to be reconciled before finance could use them as ERP invoices. Their different structures made the handoff the central task.
What was built
Nexus ingests all three sources, normalises and reconciles them, then generates ERP-compatible XML batches. Reconciliation spreadsheets and reports accompany the output for finance verification.
Why it matters
Makes the system handoff easier to inspect. Rules produce the financial output, and finance can compare input with output; there is no AI in the money path.
- Primary users
- Airline finance staff
- Core systems/data
- Reservation, ancillary and payment files; ERP
- Human control point
- Finance verifies batches against reports
- Nexus role
- Deterministic reconciliation and XML export
The challenge
Revenue data in three shapes.
Reservation exports, ancillary-service records and online-payment CSVs bring different structures to the same finance task. They need to be normalised and reconciled before invoice batches can enter the ERP.
An export alone is not enough. Finance also needs to compare what entered the process with what came out. This calls for defined transformations and a verifiable system handoff, not model interpretation of monetary values.
What we built
A deterministic revenue pipeline.
Nexus ingests the three revenue sources, maps them to a common structure and reconciles them before generating XML invoice batches in the ERP-compatible format. The pipeline is fully deterministic. AI is not used to decide the monetary output, because this task calls for defined transformations rather than model interpretation.
Each batch comes with reconciliation spreadsheets and reports so finance can verify input against output. Verification is part of the handoff, not a separate effort to explain the file afterwards. The ERP remains the destination for the invoices; Nexus does the data plumbing between systems that were never designed to talk.
How the workflow runs
Step by step.
01
Ingest
Reservation exports, ancillary records and payment CSVs are collected. Each source is mapped to a common structure.
02
Reconcile
Sources are reconciled against each other. ERP-compatible XML invoice batches are produced.
03
Report
Reconciliation reports let finance verify input versus output.
What the business team sees
Reports finance can check.
Finance receives the invoice batch together with the reconciliation reports. The useful question is not merely whether a file was generated, but how its source records relate to the output. The reports make the batch a reviewable handoff rather than an unexplained transformation of three formats.
- Source files ingested
- Reconciliation summary
- XML invoice batch
- Input versus output report
- Run history
How Nexus works underneath
No model judgement in the financial transformation.
Rules + Code steps handle ingestion, normalisation, reconciliation and XML generation. Nexus connects those steps while keeping the source systems and ERP in their existing roles. There is no AI in the money path, and the accompanying spreadsheets keep the finance verification task visible.
Architecture
How the layers fit together.
Business team
Finance reports
Reconciliation spreadsheets · input versus output
Nexus orchestration
- 01Ingest sources
- 02Normalise
- 03Reconcile
- 04Generate XML batches
- 05Reconciliation reports
Connected systems and data
- Reservation exports
- Ancillary records
- Payment CSVs
- ERP
Human control and audit
No AI where money moves.
Invoice amounts are produced by deterministic logic only. Finance can verify every batch against its sources using the reports generated with it.
What this changes
A defined route into ERP. Three source formats feed one deterministic generation process.
Output comes with verification. Reports give finance a way to compare source records with the batch.
A clear financial boundary. Rules, not AI judgement, determine invoice output.
Your process
Discuss a similar workflow
Tell us about the documents, systems and decisions involved. We will discuss where Nexus orchestration fits and where your team stays in control.