Custom integration development in Barcelona addresses enterprises operating across Spain's hospitality sector, Catalan industrial base and Mediterranean logistics corridor where disconnected PMS platforms, AEAT SII real-time VAT reporting requirements, FACe public procurement e-invoicing and multi-channel distribution systems create integration demands that manual processes cannot sustain at scale.
ZTABS is remote-first by design with an office in Houston, Texas. Our custom integration development services for Barcelona buyers begin with a system inventory covering each platform's API capabilities, regulatory submission requirements and data exchange formats, then architecture design before development.
Barcelona integration landscape at a glance
| Sector | Integration scope | Key constraint |
|---|
| Hospitality | Multi-PMS channel management, revenue management, entity-scoped guest data, SII | PMS API access per property license; SII deadline per record type |
| Financial services | Core banking, Bizum via PSP/acquirer, PSD2 role registration, regulatory reporting | Banco de Espana reporting format; PSD2 role per applicable regulation |
| Logistics | Port customs (EU Single Window), warehouse management, freight forwarding | AEAT customs declaration format; EU customs integration |
| Manufacturing | ERP-to-e-commerce, supply chain EDI, Industry 4.0 connectivity | SAP or Oracle integration with Spanish-specific modules |
AEAT SII real-time VAT reporting integration
Spain's SII system requires obligated taxpayers to submit detailed invoice records electronically to AEAT within strict deadlines. Large enterprises with previous-year turnover above EUR 6,010,121.04, VAT groups and REDEME-registered entities are obligated. Voluntary enrollment is available for entities below the threshold.
Submission deadlines and calendar rules
Issued invoice records are generally sent within four calendar days of issuance, or eight when issued by the recipient or a third party. Received records are generally sent within four calendar days of entry in the accounting system. Saturdays, Sundays and national holidays are excluded from these four- and eight-day counts. Apply the separate before-the-16th backstop based on the applicable VAT accrual period for issued records and the return period of inclusion for received records, subject to applicable special cases. Regional and local holidays do not extend the calendar day count; only national designated holidays are excluded.
SII connector architecture
The integration extracts invoice data from the ERP or billing system, generates SII XML per the AEAT specification (Libro Registro de Facturas Expedidas and Recibidas), and submits via AEAT's SOAP web service. Message types include alta (registration), modificacion (modification) and baja (cancellation). The connector handles AEAT response processing: record-level validation tracks accepted status per invoice; rejected records route to an exception queue with the AEAT rejection reason code for authorized correction and resubmission. Voluntary SII participants follow the same submission rules; their voluntary return period is separate from the dispatch deadline. The connector scopes submissions to reportable records from in-SII legal entities per authorized finance release, not to all invoices across all properties or entities. Submission volume during accrual-period close is monitored with deadline proximity alerting.
SII and accounting system reconciliation
The integration reconciles SII submission status against the accounting system's invoice records. Invoices approaching their applicable deadline without successful submission trigger alerts. Monthly reconciliation compares submitted records against AEAT's Libro Registro to identify any gaps requiring corrective action.
Hospitality multi-PMS integration
Barcelona hotel groups operating multiple properties often run heterogeneous PMS platforms acquired through property additions over time. The integration normalizes data across PMS platforms into a unified data model.
PMS connectivity
Each PMS platform has its own API architecture: Oracle Hospitality OHIP for Opera installations where available, Protel API for Protel properties, Mews Connector API for Mews properties. Access to each API depends on the property's license, edition and the PMS vendor's API program terms. The integration connects through each platform's available interface, extracts reservations, room inventory and financial transactions, and normalizes them into a common data model. Data mapping between each PMS and the unified data model is documented per property; unmapped fields are flagged for the data owner's review rather than silently dropped or assumed.
Channel distribution
Centralized distribution connects the unified data layer with OTA platforms and GDS systems per each partner's documented API rights and update semantics. Rate and availability updates flow from revenue management through the integration to each distribution channel. Booking confirmations from each channel flow back for PMS processing. Documented stale/conflict handling specifies behavior when rates from different sources disagree; the integration alerts on discrepancies. Each channel connector tracks the last-acknowledged rate and availability state so that unacknowledged updates are identified and retried per documented partner retry policy. Overbooking risk from cross-channel lag is handled per the hotel group's documented policy rather than automatic resolution.
Guest data handling
Cross-property guest data uses entity-scoped approved identifiers (loyalty ID, email, phone) with an agreed guest ID scheme per the hotel group's data governance policy. The GDPR basis for guest data processing depends on the specific processing activity and is not always consent; legitimate interest or contract performance may apply depending on the purpose. Ambiguous matches (partial identifier overlap without confirmed identity) are held for manual review rather than automatically linked. Guest preferences and spend data are shared only within the scope authorized by the applicable lawful basis and the group's data policy.
FACe public procurement e-invoicing
Suppliers to applicable Spanish public sector recipients submit electronic invoices through FACe. The integration generates Facturae format invoices (supported version and profile per the recipient's requirements) from ERP or billing data, uses the supported Facturae signing and authorized submission mechanism for the recipient, and submits through the applicable channel per the receiving administration. Each public entity's DIR3 codes (accounting office, management body, processing unit) route the invoice to the correct recipient within the public administration. The integration tracks submission status and maps acceptance or rejection results back to the ERP record. PLACSP connectivity for procurement monitoring is a separate integration scope.
Scope your SII integration or hospitality platform
Tell us which ERP, PMS platforms and distribution channels are in scope. We document SII submission requirements, API capabilities and data mapping before development.
Delivery and testing
ZTABS delivers remote-first with CET timezone alignment. Testing covers: AEAT SII XML format validation and submission through AEAT's test environment; SII deadline compliance with calendar-day calculation per record type including national holiday exclusion; FACe Facturae format validation with DIR3 routing verification; multi-PMS data normalization accuracy; channel distribution rate and availability synchronization with stale/conflict alerting; guest data matching with ambiguous-case hold verification; Bizum payment reconciliation via PSP; and parallel running against existing processes before cutover.
Staffing languages, tested locales, integration protocols and documentation scope are listed in the proposal. Customer provides system access, hospitality operations expertise, Spanish regulatory knowledge, and owns all business and regulatory decisions.
Illustrative Example
Multi-property hospitality integration with SII compliance for a Barcelona hotel group
If a Barcelona hotel group operating 15 properties across Spain with three different PMS platforms (Opera, Protel and Mews) were to scope an integration platform, the problem would be that each property manages rates, availability and distribution independently with no group-level visibility, financial reporting requires manual data extraction from three PMS platforms, SII compliance is managed property-by-property, and guest data is siloed across properties.
Prerequisites would include: PMS API access for each platform (Oracle OHIP authorization, Protel API credentials, Mews Connector API keys); OTA platform API credentials per documented partner rights (Booking.com, Expedia); accounting system API access; SII submission credentials for each legal entity; electronic certificates for FACe where applicable; documented rate distribution policy; and agreed guest ID scheme and lawful basis per guest data processing activity.
The integration would create a unified data layer normalizing reservation, inventory and financial data from all three PMS platforms. SII submission would be centralized: invoice records from in-SII legal entities submitted to AEAT per authorized finance release with deadline tracking per record type (four-day for self-issued, eight-day for recipient or third-party issued, before-16th backstop per applicable accrual or return period) and correction routing for rejected records. Channel distribution would flow through the unified data layer with documented stale/conflict handling and discrepancy alerting. Guest matching would use entity-scoped agreed guest IDs with ambiguous cases held for manual review.
Held-out evaluation would include: an Opera property and a Mews property in the same city with conflicting rate updates testing documented stale/conflict alerting; SII submission for a Friday-issued invoice testing the four-day calendar calculation with weekend exclusion; SII for a recipient-issued invoice testing the eight-day window; a guest booking at a Protel property who previously stayed at an Opera property testing entity-scoped guest matching with ambiguous-case hold; FACe invoice submission with incorrect DIR3 codes testing rejection handling and correction routing; and a PMS API becoming temporarily unavailable testing queue-based recovery with known-effect reconciliation before replay.
If a PMS API becomes temporarily unavailable, the integration queues pending data synchronization. On recovery, it verifies current state using each record's durable sync reference before replaying, reconciling actual effect before retrying unknown outcomes. SII submissions approaching their deadline during a PMS outage trigger priority alerts so the finance team can take manual action if needed.
Residual risks: PMS vendor API changes or deprecations; AEAT SII specification changes; OTA API version changes; FACe format specification updates; national holiday calendar updates affecting SII deadline calculation; and peak booking periods testing synchronization throughput.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Project costs and planning benchmarks
Costs reference the API development cost guide. The four published tiers are:
| Tier | Range | Timeline | Scope |
|---|
| Simple REST API | $8K to $20K | 3 to 6 weeks | CRUD endpoints, basic authentication, database integration, simple validation |
| Mid-Complexity API | $20K to $50K | 6 to 14 weeks | OAuth/JWT auth, role-based access, webhook system, rate limiting, comprehensive docs |
| Enterprise API Platform | $50K to $100K | 14 to 24 weeks | API gateway, versioning, analytics, developer portal, SDKs, sandbox environment |
| Complex Integration API | $100K+ | 24 to 40 weeks | Microservices architecture, event-driven, real-time streaming, multi-region, compliance |
2026 US-buyer benchmark for a mid-complexity REST API
These planning references reflect a mid-complexity REST API with OAuth/JWT auth, webhook system, rate limiting, OpenAPI docs and monitoring.
| Vendor type | Typical cost | Timeline | What to check |
|---|
| Freelancer or solo backend developer | $5K to $25K | 3 to 8 weeks | Security (auth, rate limits, input validation) and documentation |
| Offshore agency | $12K to $40K | 5 to 12 weeks | Observability, OpenAPI discipline and gateway setup |
| Nearshore agency | $20K to $65K | 4 to 10 weeks | Timezone alignment and API pattern strength |
| US/EU agency (ZTABS tier) | $28K to $90K | 4 to 10 weeks | Contract-first (OpenAPI), production monitoring, SDK generation |
| Auto-generated API (Hasura, Supabase, or PostgREST) | $0 to $8K | 1 to 3 weeks | CRUD ceiling; migration cost when business logic outgrows the platform |
A managed API gateway may add $50 to $500 per month but can save $10K to $25K on custom rate-limiting and analytics work depending on scope. Barcelona hospitality integration scope depends on the number of PMS platforms, properties, distribution channels and regulatory connectors. SII integration alone is typically a mid-complexity connector; multi-PMS group integration with channel distribution involves enterprise-tier scope. These are guide-based planning estimates from the published cost guide, not engagement-specific quotes.
Budget your Barcelona hospitality or SII integration
Describe your PMS platforms, property count and distribution channels. We reference the published API development cost guide with per-connector and ongoing maintenance estimated separately.
When ZTABS is not the right fit
- The engagement requires only a standard SII connector that your ERP vendor already provides as a supported module. Check if your ERP's built-in SII module meets your needs.
- The project requires only single-PMS channel management that the PMS vendor or a dedicated channel manager handles natively. A pre-built connector may be faster.
- The project requires permanent on-site embedded staff at Barcelona properties. ZTABS is remote-first by design.
- The project requires Spanish public procurement registration or bidding. ZTABS builds the technical integration; procurement registration is the supplier's responsibility.
Risk register
| Risk | Mitigation approach |
|---|
| AEAT SII specification changes | Schema validation before submission; SII connector updated per published specification changes |
| PMS vendor API deprecation or changes | Versioned connectors with regression testing; monitor vendor release notes per platform |
| OTA API rate limits or format changes | Per-channel adapters with documented rate-limit handling; alert on unexpected throttling |
| FACe format or DIR3 code changes | Facturae format validation with DIR3 verification before submission; connector updated per published changes |
| SII deadline breach during system outage | Priority alerts when submissions approach the applicable deadline; documented manual fallback process |
Proposal evaluation criteria
| Criterion | What the proposal specifies |
|---|
| 1. Deliverables and IP | Integration hub with SII connector (record-level accepted/rejected tracking), multi-PMS normalizer, channel distribution layer with stale/conflict alerting, FACe connector with DIR3 routing, entity-scoped guest matching, monitoring dashboard, documentation. Ownership and licence terms specified. |
| 2. Validation and holdout method | SII XML format validation with AEAT test submission per record type (four-day and eight-day windows tested); FACe Facturae validation with DIR3 routing; multi-PMS normalization with stale/conflict handling; guest matching with ambiguous-case hold verified; durable dedup with no additional effect on retry; known-effect reconciliation before replay of unknown-outcome operations; parallel running before cutover. |
| 3. Deployment and data scope | PMS API access per property and vendor rights. SII submission credentials per legal entity. GDPR lawful basis documented per guest data processing activity. Compensation limited to authorized reversible known effects; irreversible steps route to named owner. Failure, retry and fallback procedures per integration. |
| 4. Cost structure | Total project cost with milestone payments. Per-connector development and ongoing maintenance estimated separately. API gateway, monitoring and platform-specific costs documented as client-side items. |
| 5. Acceptance and fallback | SII submission accuracy and deadline compliance per record type. Channel distribution consistency with documented conflict handling. Guest matching accuracy with ambiguous-case hold rate. FACe acceptance rate with DIR3 routing accuracy. Parallel running period. Documented fallback for system unavailability. Sign-off by named client staff. |
| 6. Roles, languages and handover | Provider delivers integration hub, connectors, distribution layer, guest matching, technical testing and operational documentation; provider validates connector reliability, SII deadline compliance and distribution conflict alerting; provider trains customer staff on integration operation and monitoring. Customer provides PMS access, hospitality operations expertise, Spanish regulatory knowledge, guest data governance decisions and owns all business and regulatory decisions; customer validates business-rule correctness and guest data lawful basis; customer trains own staff on business processes. Handover includes defined deliverables, acceptance criteria and transition support. Working languages for documentation, training and support agreed per project. |
Ready to connect your Barcelona hospitality or enterprise systems?
We assess your system landscape, document API capabilities and define the testing and parallel running scope in a focused initial call.