GoldenSource H1 2026 Platform Enhancement Update Details

Data Quality & Privacy:

Consistent PII handling across every screen and every downstream system, a defensible audit trail for regulators, and cleaner data at the point of capture instead of expensive remediation later. For teams under GDPR or similar regimes, this materially reduces your compliance risk surface.

• Automated address, email, and phone number validation via Loqate now runs at the point of entry across UI, API, and batch file loads alike, rather than being caught downstream or missed entirely.
• A new PII Configuration screen lets you mark any GSO attribute as PII and assign sensitivity levels (P2, P3, P4), with full audit trails of configuration changes over time.
• PII display is now consistent and access-controlled everywhere it can appear: maker-checker screens, search exports (sync and async), multi-edit functions, event buttons, CHAL screens, and audit panels. This closes gaps where sensitive data could previously leak into the wrong view.
• A new API lets downstream systems (like OMNI) query PII configuration directly, so encryption and masking can be applied automatically and consistently as data moves through your ecosystem.
• Entity Master data distribution to OMNI now guarantees PII fields are encrypted in transit, covering create, update, and delete/end-date operations.

Visibility & Self-Service Tools: See Your Data Without Leaving the Platform

Less time context-switching between tools, faster root-cause analysis when data looks wrong, and a genuinely better day-to-day experience for the analysts and operations staff in the platform.

• Vendor data is now visible directly on the UI, with dynamic publishing and side-by-side data quality comparison. No more exporting to separate tools just to spot-check vendor feed quality.
• A new Curve Master UI, built out across four development phases, brings full curve lifecycle management plus visual comparison of curves by contributor and price type, letting your quants and market data teams spot discrepancies visually instead of hunting through raw tables.
• A new Price Master UI centralizes price configuration, with personalized user settings so individual analysts can tailor their own views and workflows.
• Enhanced audit and lineage visibility throughout, supporting faster troubleshooting when something looks off.

Vendor Feed Integration: Fewer Manual Fixes, More Reliable Feeds

Each of these gives time back to your operations team by automating work that was previously handled manually: duplicate securities to clean up, failed loads to investigate, custom code to maintain. Enhancements mean fewer tickets for your operations team and more confidence in the accuracy of your security master.

• New splitter support for ICE Apex IDFP descriptive files, plus extended security/issuer creation logic and missing domain value mappings.
• Full GSO support added for FactSet’s BDF Index, Constituent, and Symbology modules, closing a longstanding integration gap for FactSet clients.
• Corrected Bloomberg match key configurations (including the LMST segment) that were previously causing duplicate securities, plus fixed EDMV mappings for mortgage-related fields (PROP_TYP, MTGE_RTE_CHG_FQ_TYP) that were blocking loads.
• Corporate action entity resolution for Bloomberg now uses a standard ID Uniqueness process based on Bloomberg’s own unique identifier, replacing custom rules with a supportable, consistent approach.
• Enhanced GSO support for mortgage securities, broadening field coverage for MBS/ABS portfolios.

Platform & Developer Experience: Faster Implementation, Fewer Surprises

For your implementation and technical teams, these enhancements translate directly into faster configuration cycles, fewer environment-promotion headaches, and less time lost to workarounds for known UI friction points.

• Dynamic API Integration: Enable API interfacing through configurable search templates, allowing flexible and reusable data access.
• Expanded Data Processing: Enhanced the Java engine to support Bloomberg Corporate Actions and Product Taxonomy data ingestion and processing.
• Modernization & Performance: Upgrade the technology stack to Jakarta to address critical vulnerabilities and optimize the entity-based engine for improved performance and scalability.

Entity & Institution Management – Model Your Real-World Complexity

Your data model can now reflect your actual organisation charts and counterparty networks, not a simplified approximation of them. This reduces reconciliation effort, improves the accuracy of regulatory and counterparty reporting, and shortens the time it takes to onboard new complex client structures.

• Full Institution API (v1) with complete CRUD operations, so your integration and data teams can create, read, update, and retire institution records programmatically instead of relying solely on UI-driven processes.
• New Institution Group support for financial institution groups that include other financial institution groups as participants, not just individual institutions, enabling true multi-level group hierarchies (parent groups, sub-groups, nested treasury structures).
• New Enterprise/Financial Institution Role (ENFR) relationships, letting you formally link enterprises to financial institutions with defined roles, participation amounts, and effective dates. Useful for corporate actions, treasury relationships, and counterparty tracking.
• Bidirectional Party Contact Assignment, so relationship managers can now navigate and maintain contact/customer relationships from either the Institution or the Party screen, cutting duplicate data entry.
• Natural Person Party support for non-employee contacts and customers, closing a long-standing gap in CRM-style relationship tracking.

Performance & Reliability: Less Downtime, Faster Cycles

Shorter maintenance windows mean more uptime for your operations teams. Accurate exception counts mean your SLA monitoring and management reporting are trustworthy. And modernized matching logic means fewer false positives landing in your data quality teams’ queues, giving them time back for higher-value work.

• FINS cache rebuild times, previously 12+ hours and a major driver of extended maintenance windows, were significantly reduced through memory management improvements, query optimization, and parallel processing.
• GSDM filtering performance was overhauled for large datasets, along with corrected status tracking in the JBLG and TRID tables, so filtered batch runs no longer degrade as data volume grows.
• Exception management improved to make sure exceptions that should close were incorrectly staying in open state, and dashboard exception counts were inaccurate. Both are now corrected, restoring trust in your operational dashboards.
• Core matching and merge engine rules (entity match key link creation, merged-data end-dating, timeseries overlap validation) were improved, fixing duplicate RISS/IPDF records and eliminating false timeseries overlap errors that previously required manual investigation.
• NoSQL cache service startup issues that caused publishing workflow failures were resolved, along with Generic Maker-Checker workflow execution errors.