NP4 links travel data with billing data and supports payment providers with invoice reconciliation.
A billing line does not necessarily contain the full travel context. Connecting it to a booked service requires booking information, transaction data and the relevant company details to agree. NP4 supports the connection between these data sets. The focus is on traceable links and appropriate data hand-offs for the payment provider’s existing invoice reconciliation process.
Connect booking, ticket and billing references across the available sources.
Distinguish trips, transactions and billing lines rather than looking only for equal amounts.
Include changes, refunds and ambiguous items when defining the reconciliation process.
NP4 links travel and billing data for payment providers and supports invoice reconciliation.
Compare anonymised travel and billing samples. Identify available references, data suppliers, formats and delivery timings.
Agree on the attributes that connect and the level being reconciled: for example, a ticket, an individual service or a billing line.
Define target fields, transfer methods and responsibilities. Also agree how missing information and ambiguous matches will be handled.
Test straightforward matches alongside booking changes, credits and discrepancies. Review results and limitations together before the production hand-off.
The fields needed depend on the source and the reconciliation objective. The following examples support the scoping discussion; they do not imply that every source contains every field.
A booking reference or ticket number, travel dates and service type help establish the travel context. The available booking version and any changes also matter.
A transaction or invoice reference, amount, currency and relevant dates describe the billing side. Charges and credits need to remain distinguishable.
The company entity, traveller reference and, where available, a cost centre or project code provide additional context. Availability and permitted use are agreed with the parties involved.
The connected data should make a match verifiable, not merely produce a record that looks similar.
These cases belong in the scoping discussion. The checks implemented are agreed based on the available data and the receiving system.
A shared booking or ticket reference can establish a link. It is also necessary to check that both records refer to the same service, the relevant version and the appropriate billing level.
A booking change, cancellation or credit can create several related entries. The original transaction and subsequent entries should not therefore be treated as separate trips without further checks.
Missing references, different delivery timings or differences in amounts need a defined response. For ambiguous cases, agree who investigates and which information is handed over to support that work.
NP4 links travel and billing data to support invoice reconciliation. Payment processing is not part of the offering described here.
Anonymised samples from travel and billing sources, with field descriptions, are helpful. Ideally, include a straightforward case, a change or refund and an item that is currently unresolved. Add the formats, delivery timings and receiving system.
No. Equal amounts alone do not demonstrate a shared travel transaction. An appropriate reference, supporting attributes and the right data level provide stronger evidence. The combination required is defined for the actual data set.
There is no blanket guarantee. Missing information or several possible matches may require investigation. The scope of technical matching and follow-up handling is agreed in the project and tested with examples.
TD pool brings travel and company data together and standardises it. TD hub provides the information needed for the agreed invoice reconciliation process in appropriate formats. TD chart can optionally add reporting. The combination is aligned with the available sources and the existing reconciliation process.
TD pool combines travel data from agreed booking sources, validating and standardising it as a traceable data foundation for invoice reconciliation.
View product
TD hub provides the travel data required for invoice reconciliation to the receiving billing systems in defined formats and through agreed hand-off methods.
View productBring travel and billing data samples. Together, we clarify references, reconciliation cases, responsibilities and appropriate hand-offs.
Necessary cookies keep this website running. Optional analytics, marketing or social-media trackers are not currently embedded. Your choice is stored for 6 months.
