Customers · Software companies

Reporting your customers expect to be included

Core banking platforms, payment and e-money processors, treasury and ERP vendors whose customers keep asking whether supervisory reporting comes with the software they already bought.

The question is rarely whether you could build it. It is whether you want to own the EBA taxonomy permanently, for a feature that never differentiates your product.

What is hard today

  • Building reporting in-house means adopting the EBA taxonomy treadmill permanently: new DPM releases, retired rules, overlapping module versions, changing filing rules — forever, for every framework you touch.
  • None of that work differentiates your product. Your customers do not choose you for your xBRL handling; they simply refuse to choose you without it.
  • xBRL and Arelle expertise is scarce and expensive to keep on staff for what is, to you, a supporting feature.
  • When a generated report is rejected by the supervisor, it arrives as your support ticket regardless of whose rule it was.

What changes

  • Your systems already hold the figures. Deliver them as datapoints and get back a validated, sealed package built to the filing rules.
  • The taxonomy treadmill becomes ours. A new EBA release is our release note, not your sprint.
  • The same engine covers the national returns each market adds, so entering a new country is not a new reporting project.
  • One integration, one contract, priced per end institution rather than renegotiated per customer.

Where this stands. The API is in development and partner integrations are shaped together rather than picked off a page. If reporting is on your roadmap, the useful conversation is now — while the interface can still be influenced by what your systems actually hold.

Licensed per end institution

Renegotiating per customer does not scale for either of us. Vendor licensing is priced on the number of end institutions reporting through your integration and the returns they owe — not on seats, and not on data volume. One integration and one contract cover them all, and the price moves only when your own customer base does.

Pricing is being set now and we would rather shape it with the first vendors than announce it at them. Tell us which of your customers are asking for reporting and what your systems already hold — that is the conversation.

Talk to us about an integration

Bring one customer's reporting period and the shape of the data you hold. We will show you the engine on a real return before anything is agreed.

Start the conversation