ZTABS modernizes legacy applications for Barcelona enterprises in banking, insurance, pharmaceutical and manufacturing. Barcelona hosts major Spanish banking operations with legacy systems from multiple merger predecessors. Insurance carriers operate legacy policy administration serving Iberian markets. Pharma and biotech companies run validated manufacturing systems. ZTABS is remote-first by design from our Houston, Texas office.
Barcelona legacy modernization demand spans post-merger banking system consolidation, insurance platform modernization for DGSFP-supervised entities, pharma and biotech manufacturing upgrades and industrial manufacturing ERP modernization.
Legacy app modernization in Barcelona at a glance
| Need | What we build | Key requirement |
|---|
| Banking | Post-merger consolidation | BdE, ECB, DORA, SII |
| Insurance | Platform modernization | DGSFP, Solvency II |
| Pharma | MES and ERP upgrades | AEMPS, GMP, ICH CTD |
| Manufacturing | ERP modernization | SAP S/4HANA |
| Technology | Platform decomposition | GDPR, APDCAT |
Post-merger banking system consolidation
Barcelona banks operate legacy systems inherited from multiple merger predecessors. Actual predecessor count and system inventory vary by customer; consolidation of separate core banking, payment, lending and channel systems into unified modern platforms is scoped per engagement.
Core banking consolidation. Multiple COBOL mainframe cores from predecessor banks consolidated. Account management, transaction processing, general ledger and customer information unified. BdE and ECB supervisory expectations addressed at each migration phase.
Payment system unification. Multiple payment processing platforms consolidated. SEPA Instant, Bizum and card payment processing unified. Redsys actual merchant and acquirer permissions maintained.
Customer data consolidation. Customer records from predecessor banks deduplicated, merged and unified. Multiple customer identifiers resolved. Golden record established with data quality verification.
Branch network systems. Legacy branch systems from predecessor banks modernized and unified. Teller, advisor and back-office workstation systems consolidated.
Modernizing Barcelona banking or insurance systems?
Tell us about your legacy platforms, BdE requirements and consolidation scope. We start with assessment covering application archaeology, data analysis and modernization strategy.
Insurance platform modernization
Barcelona insurers operate legacy policy administration, claims and actuarial systems serving Spanish and Iberian markets.
Policy administration. Life, health, auto and P&C insurance policy lifecycle modernized. Actuarial calculations preserved. DGSFP and Solvency II reporting addressed. Spanish mandatory auto insurance requirements preserved.
Claims processing. Claims workflow modernized for digital submission, automated assessment and faster settlement. Consorcio de Compensacion de Seguros requirements for catastrophic and extraordinary risk claims maintained.
Multi-language support. Catalan and Spanish language requirements addressed per actual public-sector and consumer obligations. Agreed and tested Catalan and Spanish customer journeys implemented per engagement scope.
Pharma and biotech manufacturing modernization
Barcelona pharma and biotech companies operate validated MES and ERP systems requiring modernization while maintaining regulatory compliance.
MES modernization. Manufacturing execution systems modernized for real-time production monitoring, batch record management and quality analytics. AEMPS and EU GMP requirements addressed. GAMP 5 risk-based approach.
Biotech manufacturing. Cell therapy, biological and biosimilar manufacturing systems modernized. Cold chain monitoring and traceability. Clinical trial data management with EudraVigilance and SUSAR reporting.
ICH CTD. Common Technical Document format for regulatory submissions. AEMPS specific requirements for Spanish market authorisation.
Spanish and Catalan regulation
GDPR and LOPDGDD. GDPR directly applicable with LOPDGDD supplementary. Multiple actual processing bases available.
AEPD versus APDCAT. AEPD supervises private controllers nationally. APDCAT supervises actual Catalan public sector and legally scoped services, not all Barcelona SaaS. Assessment per actual data controller scope.
LSSI. Article 21 electronic marketing requires consent or request, or prior contract own similar products with opposition at collection and each message. Spanish law does not provide a separate B2B professional-relevance exemption comparable to the French route. Spanish-specific electronic commerce law requirements.
SII. Issued invoice reporting within 4 days of issue date. Invoices issued by recipient or third party within 8 days. Received invoices within 4 days of accounting entry into the accounting system, not 8 days from receipt. Both 4 and 8 day periods exclude Saturdays, Sundays and national holidays. Accrual and deduction period caps apply before the 16th of the following month with non-working day adjustments per AEAT calendar. Not generic immediate real-time filing.
B2B e-invoicing. Order HAC/1028/2026 effective October 6 2026. In-scope entities with more than EUR 8M previous calendar year from October 6 2027; others from October 6 2028. Status and payment reporting distinct for 2029 for certain individuals. Structured electronic invoice generation, transmission and archiving.
Workers Statute. Section 20bis privacy and disconnection distinct from Section 64(4)d algorithm information for worker representatives. Section 41 individual substantial modification requires minimum 15-day advance notice; collective modification requires consultation for a maximum period of 15 days under applicable conditions. Not every modernization modifies employment conditions.
Generalitat language. Generalitat public service language requirements apply to actual public-sector and consumer jurisdictions, not blanket all private applications. Actual agreed and tested Catalan and Spanish customer journeys.
Strangler fig for banking consolidation
Seam selection. Banking seams: accounts, payments, lending, regulatory reporting from each predecessor bank. Insurance seams: policy administration, claims, actuarial, regulatory reporting. Pharma seams: production, quality, distribution, regulatory. Each function consolidated and extracted independently.
Single authoritative write. One system authoritative for each transaction type and period during consolidation. Banking dual-write across predecessor systems dangerous for regulatory reporting and customer balances. CDC with versioning and conflict detection.
Reconciliation. Idempotency keys enforced by receiving side. Finite retries with DLQ. Unknown outcomes require reconciliation before replay, especially for SEPA payments, Bizum transactions, insurance premium settlements and pharma batch records. Predecessor bank reconciliation critical during consolidation.
Data migration methodology
Banking data. Account records, transaction history, lending portfolios and regulatory reporting data from multiple predecessor banks migrated with reconciliation against agreed record totals, tolerances and exception register with owner acceptance. Customer deduplication and golden record creation across predecessor banks.
Insurance data. Policy records, claims history, actuarial data and regulatory reporting data migrated with actuarial verification.
Pharma data. Batch records, quality data, validation documentation and regulatory submission data migrated with GMP compliance.
Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. Spanish-specific: DNI and NIE handling per data protection requirements, predecessor bank account number mapping, SII invoice identifiers, AEMPS product registration codes. EUR currency precision. Multiple predecessor bank customer identifier crosswalks.
Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover per predecessor bank starting with smallest operation. Insurance cutover timed for renewal cycles. Pharma cutover planned for production schedule gaps.
Inventory and discovery
Barcelona enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and EDI dependencies, vendor contracts, supported versus end-of-life versions. Banking consolidation requires inventory across all predecessor bank systems.
Business rules discovered with users through representative transaction analysis. Banking rules validated against BdE and ECB requirements. Insurance rules validated against DGSFP requirements. Pharma rules validated against AEMPS and GMP requirements.
Illustrative Example
Hypothetical: Barcelona bank consolidating post-merger legacy systems into unified platform
A Barcelona bank operates legacy core banking systems from five predecessor banks merged over the past decade. Each predecessor maintains separate COBOL mainframe cores with different account structures, payment processing and regulatory reporting. Customer deduplication incomplete. Regulatory reporting assembled manually from multiple sources.
Strangler fig consolidation would create unified API layer for customer services first while predecessor systems continue processing. Unified account view enabled through master data management. Each predecessor core migrated independently starting with smallest portfolio. Payment processing unified through modern gateway. Regulatory reporting automated from unified data layer.
Assumptions: predecessor COBOL code accessible for analysis, banking staff from each predecessor available for rule validation, BdE and ECB notification requirements understood, and parallel processing feasible for validation periods. Residual risks include undiscovered business rules across five predecessor systems, customer deduplication complexity, SII compliance during transition, predecessor-specific payment conventions and staff from multiple predecessor organisations. No guarantee of specific processing speed, cost reduction or regulatory outcome.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Integration and dependency management
Banking integrations. BdE and ECB regulatory reporting, SEPA payment networks, card scheme connections, Bizum, Redsys actual merchant and acquirer permissions.
Insurance integrations. DGSFP regulatory reporting, Consorcio de Compensacion de Seguros, reinsurance connections.
Pharma integrations. AEMPS reporting, EudraVigilance pharmacovigilance, supply chain connections.
Logs and retention
Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. SII invoice records with statutory retention. Spanish statutory accounting records per Codigo de Comercio. Not all logs same retention period. DNI and NIE minimised where full identifier unnecessary.
Cutover rehearsal detail
Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover per predecessor bank starting with smallest portfolio. Predecessor-specific payment, settlement and regulatory reporting timelines respected.
Rollback feasibility assessed after schema, data and contract changes. Banking payments, Bizum transactions, insurance premium settlements and pharma batch records may not be automatically reversible. Compensations can require regulatory, actuarial or quality review.
Regression and testing
Representative business-critical paths: banking transaction lifecycle with Bizum and Redsys, insurance policy lifecycle with claims and Consorcio, pharma production batch record with AEMPS compliance. Meaningful integration, performance and manual UAT with domain expert approval from each predecessor bank.
Cost and timeline
Legacy system modernization follows the published cost guide.
| Tier | Range | Timeline | Example |
|---|
| UI Modernization | $40K to $100K | 8 to 16 weeks | New frontend, API wrapper, improved UX |
| Re-Platforming | $100K to $250K | 16 to 32 weeks | Modern stack, containerization, cloud, data migration |
| Re-Architecture | $250K to $400K | 8 to 14 months | Decompose monolith, event-driven, modern data layer |
| Full Rebuild | $400K to $500K+ | 12 to 18+ months | Ground-up rebuild, agreed availability target, rehearsed staged cutover |
Vendor comparison
Ranges are 2026 US-buyer guide-based estimates for re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness.
| Vendor type | Typical cost | Timeline |
|---|
| Freelance or dev collective | $40K to $130K | 5 to 12 months |
| Offshore systems integrator | $60K to $200K | 8 to 14 months |
| ZTABS | $100K to $280K | 6 to 12 months |
| Big 4 consultancy | $300K to $1M+ | 10 to 18 months |
| SaaS replacement vendor | $50K to $200K implementation | 4 to 9 months |
Parallel-running infrastructure, senior knowledge-transfer time and where applicable compliance revalidation can add a combined scope-dependent $100K to $500K+ planning allowance. The guide's examples are SOX, HIPAA and FDA; actual applicable regime depends on the engagement.
Proposal evaluation criteria
Evaluate any vendor proposal against these six criteria regardless of price tier.
| Criterion | What to verify |
|---|
| Strategy, deliverables and acceptance | Defined modernization phases with measurable acceptance criteria at each stage |
| Data source-of-truth and reconciliation | Which system is authoritative per object and period, agreed reconciliation tolerances and exception register |
| Rehearsal, cutover and rollback | Rehearsed cutover with RTO and RPO targets, documented rollback feasibility after schema and data changes |
| Security, privacy, compliance and approval scope | Applicable regulations identified with actual approval authority and scope |
| Full recurring costs | Licensing, parallel-run infrastructure, support, monitoring and decommission costs beyond initial build |
| Human roles and responsibilities | Provider and customer trainer-validator-support split, agreed working languages, translated materials review and on-site responsibilities where needed |
Need help modernizing Barcelona enterprise systems?
Share your legacy system landscape, BdE requirements and consolidation scope. We provide a scoped estimate based on system complexity.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Overlap with Barcelona business hours for coordination and review.
When ZTABS is not the right fit
- The system still works and nobody is asking for changes. Wait for a real forcing function.
- Core banking platform vendor selection. Core banking platform licence selection and vendor-led configuration are the licensed vendor's and customer's scope. This engagement modernizes the surrounding integration, data migration and BdE/ECB reporting connections.
- On-site programme office and multi-vendor coordination. This engagement delivers application modernization. Separately contracted programme governance, on-site management and advisory retainers have different scope and responsibilities.
- On-site embedded team. ZTABS is remote-first by design. On-site staffing, training and support retainers for this engagement are separately agreed.
- BdE or AEPD regulatory advisory. This engagement builds platforms, not regulatory advice. Regulatory advisory is separately engaged.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Barcelona technology companies can commission white-label AI platforms for distribution under their own brand.
Assessment methodology
Application archaeology for Barcelona systems covers COBOL programme analysis across multiple predecessor banks for business rule extraction, insurance legacy platform analysis, pharma MES analysis for GMP compliance and regulatory reporting analysis for BdE and ECB compliance verification.
Data type mapping for Barcelona industries
Barcelona industry data has unique types requiring careful migration planning. Banking: predecessor bank account numbers with differing formats, SEPA payment identifiers, BdE regulatory reporting fields, customer deduplication keys across predecessor systems. Insurance: Spanish policy identifiers, DGSFP regulatory reporting fields, actuarial valuation dates with Iberian market conventions. Pharma: batch record identifiers, AEMPS product registration codes, GMP validation record identifiers.
Modernization approach selection
Barcelona enterprises need clear criteria for choosing between approaches.
Targeted remediation. Adding specific capabilities. Example: adding digital channel API layer to one predecessor bank system while planning full consolidation.
Re-platforming. Moving to modern infrastructure while preserving logic. Example: migrating predecessor bank billing to cloud while preserving product pricing rules.
Re-architecture. Decomposing and consolidating. Example: extracting unified payment processing from multiple predecessor bank payment engines.
Full rebuild. Ground-up development for systems where multiple legacy systems cannot be incrementally consolidated.
Technology platform modernization
Barcelona hosts technology companies and startups operating legacy platforms requiring modernization for scale.
SaaS platform modernization. Legacy SaaS architectures modernized for multi-tenant isolation, API-first design and real-time processing. GDPR requirements addressed; APDCAT scope applies to actual Catalan public-sector and legally scoped services, not all Barcelona SaaS.
E-commerce platform modernization. Legacy e-commerce systems modernized for mobile-first Spanish consumers. Redsys and Bizum payment integrations maintained. SII invoicing compliance enabled.
Tourism and hospitality systems. Barcelona tourism sector operates legacy booking, revenue management and property management systems requiring modernization for digital customer experience and real-time availability.
Risks and mitigations
Multi-predecessor banking complexity. Each predecessor bank system documented and migrated independently with consolidation verified at each stage.
SII compliance during transition. Invoice reporting obligations addressed at each migration phase with validation, monitoring and fallback. Residual filing risk documented.
Catalan language requirements. Generalitat language requirements apply to actual public-sector and consumer-facing obligations; private SaaS platforms implement agreed and tested Catalan and Spanish journeys per actual customer and regulatory scope.
Integration dependency detail
Authentication versus authorisation. Authentication identity distinct from account-level, policy-level and role-level authorisation. Predecessor bank identities mapped to unified identity during consolidation with appropriate role-level authorisation granularity.
Government system integrations. Agencia Tributaria SII, Social Security electronic filing, Generalitat of Catalonia digital services. Each integration documented and migration coordinated.
Bizum integration. Bizum actual capabilities, merchant and acquirer permissions. Mobile payment system integration maintained in modernized banking systems. Not all predecessor bank Bizum integrations identical.
Handover
Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Banking handover includes BdE compliance documentation, predecessor bank data lineage, customer deduplication methodology and DORA resilience evidence. Pharma handover includes validation documentation and AEMPS compliance records.
Ready to modernize your Barcelona legacy systems?
Share your legacy system landscape, BdE requirements and consolidation scope. We start with assessment covering application archaeology, compliance mapping and modernization strategy.