In travel, every sale creates a reconciliation.
Abstra automates the check between booking, supplier, acquirer and ERP, from the hotel invoice to commission payouts, so your back office grows with sales, not with headcount.
page blocks
Finance page
Booking reconciliation
Operational view to monitor, review, and trigger automations.
exceptions
8
prioritized for review
sources
4
logs and evidence
At BeFly, automation took hours out of the routine and opened room for analysis
A real example of what happens when rules, databases, and approvals stop depending only on manual execution.
Before: Reconciliations of 1–1.5 days, cash provisioning of 5–6h, and invoice issuance of 2–3 days. Everything scattered across databases, systems, and rules in the specialist's head.
After: Non-technical analysts building their own automations: cash provisioning in 5 min, reconciliations in 1–1.5h, invoice issuance in 30 min, a dashboard consolidating 16 tax IDs in seconds.
Result: BeFly (Belvitur + Flytour), Latin America's largest travel ecosystem (~40 companies, 16 tax IDs), brought AI into finance without waiting on a technical queue for every change.
BeFly video
How automation took hours out of operations and opened room for financial analysis.
From half a day to 5 minutes.
“I press a button, and Abstra does everything for me.”
The team stopped just hitting deadlines.
“Now I bring a period in for analysis, something that didn't exist in the team before.”
The rule left the specialist's head.
“Of all the tools we have been implementing, Abstra was the platform with the most user adoption, especially among people who are not programmers.”
Product in layers
First we connect the sources.Then we automate the checks.
Abstra organizes bookings, vouchers, invoices, banks, and ERP in three layers: data gathered, rules executed, and exceptions visible for the team to decide.
intake
Data layer
We gather locators, vouchers, invoices, statements, emails, and ERP entries before reconciliation starts.
For operations with many bookings, many teams, and many exceptions
TMCs and corporate travel
- Reconciling rental-company spreadsheets against the transactional base by booking code
- Corporate expenses, advances, and reimbursements
- Invoices and cards without line-by-line checking
Operators, agencies, and consolidators
- Payouts, commissions, and multi-supplier billing
- Accounts payable with Central Bank FX rates
- Multi-entity consolidation and tax close
Hospitality, OTAs, and receivables
- Hospitality NFS-e vs card/acquirer invoice
- NFS-e issuance at scale (individuals/businesses/white-label)
- Cancellations, chargebacks, and receivables reconciliation
Real examples
What we have already automated in the sector
Anonymized cases from the travel kit: from travel-tech to hotel chains.
Corporate travel management platform
Reconciles rental-company spreadsheets against the internal transactional base by booking code. From hours to minutes, ~90% less manual work.
Hotel chain
Reconciles hospitality NFS-e against the card/acquirer invoice. AI extracts the invoice and matches by authorization, tax ID, and guest.
Airline consolidator
Accounts payable: spreadsheet by email, converts currency with the Central Bank FX rate, and allocates by unit.
Ticketing OTA
Issues NFS-e at scale (issuance, cancellation, and lookup) for individuals, businesses, and white-label.
Consolidator group
Processes the bank statement and consolidates ~16 subsidiaries into a single flow.
From the operations floor
If your travel operation looks like this, we fix it.
Real voices from people who live the manual check every day.
“Checking bookings against what the supplier charges is done by hand, spreadsheet by spreadsheet, and it gets worse every month we sell more.”
“Every hotel, airline, and rental company sends the invoice in a different format; someone types it all in and posts it to the ERP.”
“We only find the discrepancy after we have already paid the supplier.”
“Closing the month means consolidating dozens of tax IDs into one giant spreadsheet.”
Finance routines
Bookings, vouchers, payouts, and invoices change fast. Finance has to keep up.
When each step lives in a different source, reconciling travel becomes hunting exceptions by hand.
Booking, voucher, and charge in different sources
The locator is in one system, the voucher in another, and payment arrives via bank or card.
Payouts that require line-by-line checking
Supplier, hotel, consolidator, and partner can have different rules, deadlines, and amounts.
Rebookings change the reservation after the sale
Changes, credits, penalties, and fare differences need to follow the finance team.
BSP/IATA and air tickets with exceptions
Tickets, fees, commissions, and discrepancies need to match before close.
Invoices arrive in different formats
PDF, email, portal, spreadsheet, and ERP need to become a single validation base.
Status scattered across teams
Operations, finance, and support ask in parallel channels to find out what got stuck.
Multi-entity and cost center without a standard
Tax IDs, units, projects, and corporate clients require consistent classification.
Close without visibility into pending items
Discrepancies only show up when someone matches booking, payout, invoice, and statement.
Less time hunting the error. More time deciding what to do with it.
Choose a routine
Before
Log into systems to extract reports
After
Reports collected without repetitive work
Automation pulls the right sources and leaves the team to review the result.
Control to automate without losing governance
AI for documents and exceptions
Reading invoices, emails, vouchers, and attachments when the data is not structured.
Configurable finance rules
Matching, approval limits, cost centers, and policies adjusted to the operation.
Human review where it matters
Sensitive discrepancies arrive with context for approval or adjustment.
Traceability of close
Logs, evidence, and status to know what was validated and by whom.
Connectors
We connect what already runs your operation
ERPs, banks, cards, gateways, operational databases, emails, internal tools, BI, alerts, and booking systems. A few examples below.
Travellink
Travel
Wooffice
Travel
Woopay
Payments
CRS 360
Travel
Safeguard
Travel
Sienge
ERP
Totvs
ERP
Bling
ERP
GRF/OFM
Travel
MXM
ERP
NetSuite
ERP
Omie
ERP
SAP
ERP
Travellink
Travel
Wooffice
Travel
Woopay
Payments
CRS 360
Travel
Safeguard
Travel
Sienge
ERP
Totvs
ERP
Bling
ERP
GRF/OFM
Travel
MXM
ERP
NetSuite
ERP
Omie
ERP
SAP
ERP
Conta Azul
ERP
Banco do Brasil
Banks
Bradesco
Banks
Banco Inter
Banks
Banrisul
Banks
Santander
Banks
Itaú
Banks
BTG
Banks
Sicredi
Banks
Cielo
Payments
Adyen
Payments
Pagar.me
Payments
Rede
Payments
Conta Azul
ERP
Banco do Brasil
Banks
Bradesco
Banks
Banco Inter
Banks
Banrisul
Banks
Santander
Banks
Itaú
Banks
BTG
Banks
Sicredi
Banks
Cielo
Payments
Adyen
Payments
Pagar.me
Payments
Rede
Payments
Stripe
Payments
PayPal
Payments
Google Sheets
Spreadsheets
Gmail
Google Drive
Files
Slack
Alerts
Microsoft Teams
Alerts
Alerts
Salesforce
CRM
HubSpot
CRM
Pipefy
Operations
Jira
Operations
Snowflake
Data
BigQuery
Data
PostgreSQL
Data
Stripe
Payments
PayPal
Payments
Google Sheets
Spreadsheets
Gmail
Google Drive
Files
Slack
Alerts
Microsoft Teams
Alerts
Alerts
Salesforce
CRM
HubSpot
CRM
Pipefy
Operations
Jira
Operations
Snowflake
Data
BigQuery
Data
PostgreSQL
Data
Want to know which manual routines are worth automating first?
In a short conversation, we map the most manual routines, data sources, systems involved, and ROI opportunities.
I want to map my automationsFrequently asked questions about financial automation for travel
How do you automate financial reconciliation in travel companies?+
Financial reconciliation in travel can connect booking systems, ERP, banks, cards, invoices, vouchers, locators, and supplier databases. We match those sources, apply matching rules, and leave discrepancies prioritized for review.
Do you replace my ERP or travel system?+
No. We do not replace ERP, OBT, booking systems, TMS, or internal tools. Abstra acts as an automation layer between those systems to reduce rework, reconcile data, and keep a trail of what was validated.
Which travel reconciliations can become automation?+
Bookings with payment, locator with voucher, supplier payouts, rebookings, cancellations, invoices, cards, accounts payable, ERP entries, and BSP/IATA reconciliation can become traceable flows with exceptions for the team to review.
How does AI help with invoices, vouchers, and supplier emails?+
AI reads PDFs, emails, invoices, receipts, and attachments to extract supplier, amount, due date, locator, voucher, cost center, and description. Then business rules validate that data against bookings, statements, cards, and ERP.
Can you automate rebookings, reimbursements, and advances?+
Yes. Automation can validate policy, receipt, fare difference, penalty, credit, approval, and discrepancy. Cases outside the rule go to owners with evidence, history, and context for what needs a decision.
Do you connect banks, ERP, booking systems, and internal databases?+
Yes. We can connect banks, ERPs, booking systems, emails, APIs, documents, operational databases, supplier databases, and internal tools. The integration depends on the company's stack and available permissions.
Does it work when the supplier sends invoices by PDF, portal, or email?+
Yes. We use AI to interpret documents and messages, combined with automations and rules for validation, matching, and system updates. When the information is incomplete or uncertain, the case goes to human review.
How do you keep an audit trail in AI reconciliations?+
Each step can keep logs, evidence, approvals, status, and an audit trail. AI supports reading and classification, but governance stays in the workflow: what was validated, what became an exception, and who approved it.
Where should a travel operation start?+
Start with the routine that has the highest checking volume and the clearest rule: bookings with payments, supplier payouts, invoices, or rebookings. The first step is to map sources, exceptions, and impact on close.
Are BSP/IATA and air tickets also in scope?+
Yes. Tickets, fees, commissions, differences, and BSP/IATA discrepancies can be treated as reconciliation cases, with their own rules and exception queues for review before close.
Bring us one month of your travel reconciliation. We'll reconcile it with you.
Travel is multi-system, multi-supplier, multi-entity: reconciling it takes real integration, deterministic rules, and an auditable write-back. It doesn't come out of a chat.
Talk to an expert