How Sempi is building a European Business Governance Standard with Openapi APIs

Sempi srl is not simply developing a software suite: it is building a European Business Governance Standard. This is a model that allows businesses, accountants, consultants and professionals to work with the same language, the same data and the same decision-making criteria. At its core is the Sempi Method, structured in four phases: Assess, Plan, Execute, Reassess. The same principle is applied to governance, accounting, taxation, organisation and collaboration between companies and professionals.

The method takes shape in an ecosystem of three tools:
Sempix manages accounting, taxation and administrative processes.
SempiPlancia handles governance, control and management maturity.
Ribkom supports collaboration and communication between companies, consultants and professionals. For Sempi, these are not three separate products, but three parts of the same operating model. The goal is not to add yet another management software to a market that already offers plenty. Sempi wants to make business management simpler, more consistent, interoperable and measurable, without forcing companies and professionals to work across dozens of disconnected environments.

The challenge: integrating external services without fragmenting the experience

From the very beginning, Sempi chose an open, API-first architecture, with a clear rule: build what represents its own value and don't reinvent what others already do well. Sempi's value lies in its method, its processes, automation and the ability to turn different data into useful information for working and making decisions.

However, the processes managed by the platform constantly require information and services that don't originate within it. A company needs to be verified, a business register extract obtained, an official document retrieved, a document signed and given a certified date, or an e-invoicing flow managed. Building dedicated infrastructure every time would have meant months of development and maintenance, taken away from the real goal.

Sempi was therefore looking for a partner able to offer many different services within a single API infrastructure. One requirement was essential: the integration had to remain invisible to the user. Whoever works on the platform doesn't need to know which API was called, which register was consulted or which service generated the document. They simply need to be able to keep working.

The Openapi APIs used

Sempi uses, and is progressively integrating, several services from the Openapi ecosystem, each covering a different point of the same process:

• OAuth V2: to manage secure access to services and define permissions and limits in a granular way.
• Company: to quickly acquire and verify company information.
• Risk: to enrich analysis processes with information useful for assessing the reliability of individuals and companies.
• DocuEngine and Business Register Extracts: to retrieve official documents and information from the Italian Business Register and other institutional sources, directly within processes.
• eSignature: to integrate electronic signatures into document workflows, without users having to leave their working environment.
• Timestamps: to give documents a certified date and time when the process requires it.
• Invoice and SDI E-invoicing: to integrate e-invoicing flows and related services directly into Sempix processes.
• Trust: as an additional layer of protection against malicious use of the platform.
• Postcodes, Municipalities, Provinces and Regions: to standardise and verify geographic information, keeping it up to date.
• Land Registry: to retrieve cadastral or property information when the process requires it.
• Exchange Rates: to manage operations and documents involving different currencies automatically.
• Geocoding: to transform and standardise geographic information.
• PDF: to generate documents directly from the platform's processes.
• AI: to integrate language models and company data into increasingly automated and context-aware processes.

For Sempi, the value doesn't lie in any single API. It lies in what happens when these services stop being separate and become parts of the same process.

The solution: many services behind a single path

Sempix clearly shows how this approach works. Sempi is building a path that guides users step by step: from data to document, from accounting to control, all the way to compliance. Today Sempix manages, or is progressively integrating, many activities: e-invoicing, acquisition and classification of PDF and XML documents with OCR and AI, PSD2 banking flows, reconciliation, fixed assets, withholding taxes, ENASARCO, VAT, LIPE, F24, Intrastat, OSS, receipts and tax returns.

At each of these stages, Openapi APIs step into the process when needed. They can verify a company's data, obtain a business register extract, check risk information, produce a document, sign it, timestamp it or manage e-invoicing.

Operational benefits

The first benefit is development speed. Ready-made APIs save Sempi months spent building and maintaining individual infrastructure services. The second is scalability: the platform can add new services to existing processes without creating a new environment each time.

The third, which Sempi considers essential, is the quality of the user experience. Behind a single process, data from the Business Register, official documents, electronic signatures, SDI, risk services, Trust and AI may all be at work. Up front, however, the user finds one single path. The fourth benefit is strategic: the team's resources stay focused on the Sempi Method and process logic, instead of being spent on developing dozens of vertical infrastructures.

Results achieved

The most visible result is the speed with which Sempi now turns an operational need into an integrated feature. In recent months, Sempix has grown to cover a much broader path: from documents to bookkeeping, from bank transactions to compliance, all the way to tax returns and electronic filings. At the same time, SempiPlancia turns available data into governance and control indicators, while Ribkom connects companies and professionals within the same ecosystem. Openapi APIs enrich all these processes with external data and services, without fragmenting the experience.

Sempi's vision is clear. It doesn't want software with a hundred buttons: it wants users to be able to say "I need to do this" and let the system figure out which data, services, documents and checks are needed to get it done. In this model, APIs are one of the elements that make it possible, not just a technological link. Sempi builds the path, and Openapi connects it to the outside world. This is how, piece by piece, a European Business Governance Standard is taking shape: one that can truly be used every day.