Card data handling
Consensus complies with PCI DSS for card data handling in its reconciliation and settlement processes.
Consensus · Airlines
Centralize your airline's sales, payment and settlement records. Consensus prepares information, applies reconciliation rules and organizes exceptions against banks, processors, gateways and IATA/BSP information, with evidence for your finance team.
Result achieved in one airline implementation. Savings depend on the scope and conditions of each operation.
Security and trust
Consensus complies with PCI DSS for card data handling in its reconciliation and settlement processes.
BYTE holds ISO 27001 certification for information security management.
The Consensus engine, applied to your airline
Prepare inputs and define each match between independent sources. Consensus links records through configurable rules and delivers results for exception review.
01 · Configurable sources
02 · Processing with Consensus
03 · Result of each match
Sales, banks, processors, gateways and IATA/BSP.
Keys, groupings, 1:1 and 1:N matches and tolerances.
Missing records, amounts, assigned owners and history.
01 · Configurable sources
02 · Processing with Consensus
03 · Result of each match
Sources, fields, rules and frequencies are configured according to the airline's processes and interfaces.
Automation and operational tools
Consensus capabilities support the complete process: from receiving files to reviewing exceptions and delivering results to other departments.
Extract, load, transform and standardize inputs in multiple formats. Schedule their receipt and retain source information.
Sales, banks, processors, gateways and IATA/BSP.Define primary and secondary keys, 1:1 and 1:N reconciliation, groupings and tolerances for each process.
Criteria adapted to each source's information.Review record details, match transactions manually and track exceptions with assigned owners and notifications.
An organized review process for the reconciliation team.Identify and analyze these transactions within reconciliation, comparing amounts and transactions reported by the parties.
Exception control over received records.Generate on-demand reports and scheduled outputs, with configurable formats and interfaces for other departments or systems.
Summary or detailed information according to the process.Retain inputs, results and exceptions for later inquiries and reconciliation process reviews.
Evidence from the source to the matching result.Extract, load, transform and standardize inputs in multiple formats. Schedule their receipt and retain source information.
Sales, banks, processors, gateways and IATA/BSP.Define primary and secondary keys, 1:1 and 1:N reconciliation, groupings and tolerances for each process.
Criteria adapted to each source's information.Review record details, match transactions manually and track exceptions with assigned owners and notifications.
An organized review process for the reconciliation team.Identify and analyze these transactions within reconciliation, comparing amounts and transactions reported by the parties.
Exception control over received records.Generate on-demand reports and scheduled outputs, with configurable formats and interfaces for other departments or systems.
Summary or detailed information according to the process.Retain inputs, results and exceptions for later inquiries and reconciliation process reviews.
Evidence from the source to the matching result.Cases your team needs to review
These examples illustrate comparisons between sources. Amounts are fictional and show how an exception can be organized for review.
The record appears only in the sales source. The team reviews payment inputs, the period and available references.
Only in source AThe linked records show a $5 difference. Its acceptance or review depends on configured rules and tolerances.
Amount differenceWith matching references and amounts according to the matching rules, the refund is linked across sources.
Matched according to rulesThe record appears only in the sales source. The team reviews payment inputs, the period and available references.
Only in source AThe linked records show a $5 difference. Its acceptance or review depends on configured rules and tolerances.
Amount differenceWith matching references and amounts according to the matching rules, the refund is linked across sources.
Matched according to rulesConsensus reconciles records: executing a refund or handling a chargeback remains part of the airline's processes and systems.
Reconciliation Manager
Gather the context needed to investigate each exception, rather than reconstructing it from scattered files.
Review source records and process results to identify information that needs attention.
Match records when appropriate, document the review and follow up with the responsible team.
Review results and history and share reports for internal control and audit.
Review source records and process results to identify information that needs attention.
Match records when appropriate, document the review and follow up with the responsible team.
Review results and history and share reports for internal control and audit.
Accounting integration
Journal entry generation complements payment and settlement control. Consensus prepares the information; the airline's ERP performs the accounting posting.
Source matching and exception control.
Generated from configured accounting flows.
Process validation before delivery to the financial system.
Information for posting in the airline's system.
Source matching and exception control.
Generated from configured accounting flows.
Process validation before delivery to the financial system.
Information for posting in the airline's system.
YOUR NEXT PROJECT
Tell us what you need to improve. Our team will help you identify the right solutions for your project.
ventas@bytesw.com