Glomidco puzzle pieces logo GLOMIDCO Middleware Consultancy

Glomidco / XBRL

XBRL, as a message in flight.

Overview

An integration take on a regulatory standard.

XBRL — eXtensible Business Reporting Language — is hard to comprehend, hard to create, hard to validate and hard to use. It is also unavoidable: regulators across financial and sustainability reporting keep choosing it, and the data has to move.

Glomidco has worked on XBRL since around 2010. From the start the angle has been an integration angle: treat XBRL as a message in flight — one that can be parsed, validated, generated and routed by standard middleware components, with the calculations and taxonomy crunching done up front so the runtime path stays measured in milliseconds.

The result is a complete commercial product line for straight-through XBRL processing, sitting alongside our open-source initiatives and our consultancy work.

The engine

The Glomidco XBRL Processor.

At the core of every product is a single Java-based XBRL processor. It is the same engine across every plugin, every adapter and every connector — one library, one behaviour, one place to keep up with the standard.

  • Built for straight-through processing (STP) — thousands of XBRL messages per second on a sufficiently provisioned server.
  • Heavy taxonomy work happens at start-up; runtime per-message cost is in the milliseconds.
  • Full validation, error handling and reporting on the output side.
  • Both Financial Reporting (FR) and Global Ledger (XBRL GL) are supported.
  • XBRL merge support — map partial instances separately (e.g. COREP / FINREP tables) and combine them into a single submission.
  • Taxonomy Package standard support, with a built-in Taxonomy Package editor.

Plugins & connectors

One processor, every middleware platform.

Each platform integration is a thin shell on top of the same Java engine. That keeps behaviour consistent across stacks — pick the platform your organisation already runs, not the one a vendor wants to sell you.

Plugin

Tibco BW 5.x

Drag-and-drop XBRL handling for any taxonomy, with XBRL router, XBRL2XML / XML2XBRL activities and XBRL GL support.

Adapter

webMethods IS

An XBRL adapter for IBM (formerly Software AG) webMethods Integration Server — drop a .tax package straight into a project.

Certified connector

MuleSoft

A MuleSoft Certified Connector originally published in the official MuleSoft store; an updated build for the current version is available on request.

In development

SAP CPI

An SAP Cloud Platform Integration adapter is on the roadmap, embedding the same processor inside SAP integration flows.

Approach

STP first. DPM second.

Most XBRL solutions on the market are built around a Data Point Model: users fill in spreadsheets or databases, and an instance is generated at the end. That works — but it is the wrong shape for systems that need to push XBRL through a pipeline.

The Glomidco approach is the other way round: XBRL as a flowing message, generated and validated as data moves through your integration platform, fed by mappings from whatever source systems you already operate.

Mapping into and out of XBRL is the natural companion to the processor. Through Glomidco’s open-source UTL-X language, the same XBRL processor can be driven without any commercial middleware in the picture — useful for teams who want STP without a vendor licence underneath it.

Read on

The full story.

This page is the short version. The XBRL product line has its own dedicated home, with the processor documentation, plugin details, taxonomy notes and the full STP-vs-DPM argument.

External · Product site

The XBRL Company

The product home for the Glomidco XBRL Processor — product overview, STP approach, jurisdictional notes, processor documentation, and contact for licensing and support.

thexbrlcompany.com

Talk to us about XBRL