Integrations Library

Overview

The integrations library is the public-facing catalog and dashboard entry point for bringing booking data into VillaTax. It is designed for operators who do not work with a single source of reservations. In practice, villa businesses often combine Airbnb, Booking.com, niche OTA channels, direct inquiries, CSV exports, and manual records. VillaTax reflects that reality by supporting multiple ingestion paths instead of pretending every platform offers the same sync quality.

Inside Integrations, the library gives you a structured way to see what can be connected, how it connects, and what kind of sync behavior to expect.

Connection Methods

VillaTax does not treat every platform as a native real-time API partner. Instead, each integration is described honestly according to the available method. The platform library can surface connection patterns such as:

• iCal import
• CSV upload
• booking ingestion from structured exports
• support workflows for sources that need manual preparation

This matters because the operator experience depends on the method. A CSV workflow is not the same as an iCal feed. An email-forwarded statement is not the same as a structured booking export. The library helps users understand that before they connect a source.

Catalog and Filtering

The feature is not just a static grid of logos. It is meant to help users quickly answer:

• Is my OTA or PMS represented in the library?
• Does this source connect through iCal, CSV, or another workflow?
• Is the current sync status healthy?
• Which integrations are most relevant to my operating model?

The library becomes more useful when the account manages multiple properties or multiple booking sources. In that setup, the challenge is not just "can this connect?" but "which data path should I trust for this property, and how do I keep my booking imports consistent?"

iCal-Based Sync

iCal is one of the practical ways VillaTax can ingest booking availability and reservation timing from external systems. It is useful because many platforms expose it, even when they do not offer a clean accounting or tax API.

The tradeoff is that iCal is a polling-based sync model. It is not presented as instant or real-time. VillaTax should describe it as a recurring sync workflow with a delay window rather than as a live event stream. That is the correct operational expectation for teams relying on external calendar feeds.

When an integration uses iCal, the value is primarily:

• calendar visibility
• booking window visibility
• reservation timing alignment
• cross-checking occupancy against tax and revenue data

CSV and Structured Imports

Some platforms and internal processes are better handled through structured file imports. In those cases, the integrations library helps the user understand that VillaTax is not only for always-on syncs. It can also normalize imported records and turn them into usable booking, tax, and accounting data.

That matters for operators who receive:

• monthly OTA exports
• back-office CSVs
• statement files from finance teams
• legacy data moved in batches

The library should set expectations that these methods are valid operationally, but they depend on the quality and cadence of the source file.

Sync Health and Operational Visibility

An integration feature is only useful if the user can tell whether it is working. That is why the integrations area is not just about setup. It also supports operational checks such as:

• whether a source has been connected
• when the last sync or import occurred
• whether the input method is manual or recurring
• whether follow-up is needed for a stale feed

For finance and tax workflows, stale booking data is not a cosmetic issue. If reservations are incomplete or late, downstream revenue and tax calculations can lag behind reality. The integrations library reduces that risk by making the connection state visible.

Relationship to Other Modules

Integrations feed the rest of the product:

• bookings use imported reservation data
• calendar reflects imported occupancy windows
• analytics depends on complete reservation inputs
• the tax engine uses booking-linked revenue context

Because of that, the integrations library is one of the foundations of the product rather than a side utility. If the source data is bad, everything downstream is weaker. If the connection setup is clear and stable, the rest of the workflow becomes easier to trust.

Limits

VillaTax should not promise that every source is a real-time, bi-directional API integration. Some are libraries and connection guides rather than deep partner integrations. Some depend on iCal polling. Some depend on structured imports. Some may require operational review after connection.

That is not a weakness if communicated honestly. The point of the library is to give users a credible map of what can be connected today and how that connection behaves in practice.

Getting Started

Open Integrations to browse the available platform library, filter by source type, and choose the most appropriate connection workflow for your property stack. Start with the channels that generate the majority of your bookings, then expand once the first revenue and occupancy flows are stable inside VillaTax.