Travel & supplier sources
Travel management companies (TMCs), online booking tools (OBTs) and global distribution systems (GDSs)
Airlines, hotels, car rental and rail
Publicly approved partner APIs
Trip Logging and other off-channel data
Travel & enterprise integrations
Connect travel and enterprise systems.
Connect travel providers and enterprise systems with NP4. Explore external data sources, target systems and possible connection methods. Whether a connection can be used depends on the contract, region and technical access.
INTEGRATION LANDSCAPE
Which systems NP4 connects — and under which conditions.
NP4 connects travel sources and enterprise context with the processes that need this information. Data contracts govern delivery to recipients such as Finance, BI or Corporate Security. The connection that can be used depends on the provider, contract, region, technical access and target system.
Enterprise & finance context
HR and traveller master data
Entities, cost centres and projects
Finance, card, payment and expense data
Security, policy and approval rules
Destination systems & business processes
Reporting, performance management and analytics
Corporate Security and duty of care
Approvals and traveller communications
ERP, Expense, suppliers and other destination systems
Travel outside connected booking channels
Trip Logging can capture trips that do not arrive automatically through connected booking channels and pass them to TD pool. It extends the data foundation when included in your setup. Completeness and freshness depend on the sources and on trips actually being recorded.
Trip LoggingInterface methods
The appropriate method follows the actual access and operating model.
APIs & webhooks
For available interfaces, direct hand-offs and event-driven data flows.
SFTP / FTPS & batch
For secure file transfer, structured formats and scheduled import or export runs.
Direct source connections
For approved direct links to suppliers, OBTs, finance or other customer systems.
Customer-specific adapters
For justified formats, transformations, middleware and specific operating requirements.
Detailed connector configurations and technical specifics are available on request.
More about technical connectivity: Connectors & APIsTechnology & content ecosystem
An open ecosystem for data, content and delivery.
The technology or content partners used depend on product scope, region, contract and customer configuration.
Travel security & risk
Country risk, advisories, incident feeds and security content.
RisklineOptional integration for companies that automate their own travel-security processes: country risk levels across the Travel Data Suite, Real-Time Alerts in TD care, and automated creation, updating and deletion of outdated Advisories and Country Reports in the TD doc CMS.
Finance & payment
Corporate card, virtual card, billing and settlement data.
CO₂ & sustainability
Emission factors, trip-level CO₂ values and sustainability reporting.
Travel supply & booking
GDS, OBTs plus airlines, hotels, car rental, rail and other direct sources.
Communication
Email, SMS and push gateways for documented traveller communications.
Hosting & monitoring
Data centre, platform operations, monitoring and operational analytics.
Geospatial & mapping
Geocoding, points of interest, mapping and location services.
Connector assessment
Four inputs for assessing your connection.
Which systems should supply or receive data? Specify the provider, product and relevant countries.
Which travel and enterprise data is needed, and for which process?
Which interfaces, file formats and access permissions are available?
How often is data needed, and who is responsible for access, operations and resolving errors?
Which systems need to communicate in your landscape?
In a technical discussion, we review data sources, interfaces, architecture, security and the potential implementation approach.