Integration & APIs

Your systems work. What gets lost is between them.

Core, ERP, digital channels, business partners, payments and the SAT: the layer that connects them, with every operation confirmed and traceable, and the ability to change one with the least impact on the others.

Let's talk about your case

Prefer email? Write to us at hola@habil.mx

Trusted by organizations where continuity and security are non-negotiable

  • BanCoppel
  • Zurich
  • Allianz
  • GNP Seguros
  • MetLife
  • Costco
  • Seguros Multiva
  • Aserta
  • Bx+
  • Veolia
  • Truper
  • Argos

An integration that fails doesn't warn you: it leaves a gap that someone fills by hand

A payment that left the channel and never reached accounting. A policy that was issued and the CRM doesn't know about. A partner who can't collect from their own system and emails you a file. Every system says everything is fine, and your people absorb the difference, with spreadsheets, at close. When connections grow without a map, manual work becomes part of the operation.

Example illustration: several channels ending up in a single conversation, in four steps.

Symptoms your organization already recognizes

  • “Every system reconciles on its own; together, they don't.”

    What the core says, what the ERP recorded and what the bank collected don't match, and it gets reconciled by hand.

    Financecloses that get reopened and differences nobody can explain.

  • “If we change that system, everything else breaks.”

    The connections live inside each system and nobody knows how many there are.

    IT managementreplacing the ERP or the core gets put off year after year.

  • “Only one person knows how they connect.”

    Knowledge of the interfaces sits in a few heads and in no document.

    IT managementevery staff rotation is an operational risk.

  • “Our partners can't connect.”

    Banks, retailers, brokers or distributors who want to sell or collect from their own system receive files by email.

    Saleschannels that grow more slowly than they could.

  • “We don't know whether that operation arrived.”

    A message sent without confirmation gets retried by hand or duplicated.

    Operationsdouble charges, policies with no record and customer complaints.

Why now?

The SAT receives every tax receipt before it even exists and audits more and more online; when the payment, the CFDI and the accounting don't match, clearing it up costs time and evidence. Banks have until December 14, 2026 to standardize the mobile transfers that Banxico requested. And the AI agents your company wants to use only work if they find connected data. All of it runs through the same layer.

What we offer

  • Change one system with the least impact on the others.

    When you replace your ERP or your core, we design the coexistence in stages: your channels and your operation keep feeding the right system, with confirmation of every transmission. You migrate in segments, not all at once over a weekend.

  • Every transmission with its response and its reason.

    Every operation between systems is recorded with its response, its time and the reason if it failed. Exceptions stay in plain view of your team, instead of surfacing at close or in a complaint.

  • Your core, connected to everything around it.

    Insurance cores —Acsel/X, SIVI, SABE, SIS/SISnet, Guidewire, Duck Creek or another— and banking cores —Temenos, FLEXCUBE, Bantotal or another— with your CRM, your ERP, your channels and your partners, through the interfaces they already expose: Guidewire's set of SOAP services, the services and tables of SIVI, SABE or SIS/SISnet, or whatever your core offers. If your system runs on IBM i (AS/400), its RPG programs become services that your channels and partners can call, without rewriting them. And if your systems live on Oracle —Siebel, E-Business Suite, Acsel/X, SIS/SISnet or another—, we connect through their stored procedures or exchange tables, without touching their logic or their screens, even if they are desktop applications from twenty years ago. When your policy allows it, your queries on the core's tables become read-only REST services, with permissions and a record of every call. And if your integration lives in IBM's WebSphere family —application server, MQ, ESB or Business Integration—, we know it from the inside: we have worked with it for more than twenty years. Your data, wherever it is: Oracle, DB2 (also on IBM i), Informix, SQL Server, PostgreSQL, MySQL, MariaDB, MongoDB or another. And your documents, in your document manager —Alfresco, SharePoint or another—, linked to the operation that originated them.

  • Your ERP, through its standard interfaces.

    SAP (S/4HANA, Business One), Oracle, Microsoft Dynamics 365, Odoo, CONTPAQi or another: we prioritize the interfaces the manufacturer itself supports —in SAP, for example, JCo, OData, IDoc or REST—, so we don't leave you with custom developments that get in the way of upgrades. If some extension is unavoidable, we tell you in the assessment.

  • APIs for your partners.

    Banks, retailers, brokers and distributors quote, issue or collect from their own system, with their own identity, permissions and audit trail, in REST or GraphQL depending on what the consumer needs.

  • A single front door for your APIs.

    Identity, permissions and a record of every call in one place, with whichever gateway fits —Apigee, Azure API Management, Amazon API Gateway, Kong, WSO2, APISIX or another—, without putting business rules there that nobody can test later. Behind it can sit your long-standing services or cloud functions that only charge when used.

  • Events between systems, without duplicate effects.

    When one system needs to find out what happened in another, it is notified through queues or events —IBM MQ, Kafka, RabbitMQ, ActiveMQ or another—. A notice can arrive twice; the design makes the operation affect your business and your accounting only once.

  • Billing, invoicing and the SAT in the same flow.

    Payment gateways and banks, reconciliation of every collection, CFDI with its payment complement and cancellations, orchestrated toward your stamping provider.

  • Your personal data, protected along the way.

    It travels encrypted between systems, comes out masked in the logs, and each system receives only what it needs. The rules are defined with your team, against your policies.

  • Leave your legacy bus without switching it off all at once.

    If your integrations live in WebSphere ESB, IBM Integration Bus, MuleSoft, WSO2 or Pentaho processes that nobody wants to touch anymore, we know them because we built them over the years. We keep them running while we move them, segment by segment, to a layer your team can operate and change.

Further reading

Quoting, sales, payment collection and invoicing on a single base, connected to your core systems and your ERP?

Explore Retícula

If the pain is tax-related: your received CFDI, in one place.

Explore Cuadre

And if you want AI to work with your systems: the same layer is what gives AI access to your data, with the permissions and audit trail your regulator requires.

Hábil AI

What your Compliance team receives

Every operation between systems is recorded with its response, its time and its reason if it failed; partner and system access, by credential and with a log; personal data, masked in the logs. Evidence your auditor can consult, without hunting for it in emails.

How we work

In stages and with operations running. First we measure which connections exist and which fail without warning; then we replace one at a time, with the old one kept alive until the new one proves it reconciles. In your infrastructure or in your cloud, depending on your regulation; and when the two coexist, connected through private links that don't go over the internet, designed by architects trained in the AWS cloud who have operated it in banking and insurance. Your Compliance team receives the technical evidence it needs for your regulator.

What we've already built

  • From the core to the accounting ERP, while the ERP was changing.

    A global insurer replaced its financial ERP; the layer we built kept its operation feeding it —accounts receivable and payable, ledger, payments, cancellations and exchange rates— with the ERP's confirmation for every transmission.

  • Two core systems synchronized without duplicate data entry

    over the insurer's integration bus.

  • Partners and brokers collecting through their own channels

    services for third parties and an online payment gateway routing to two banks.

  • Foreign exchange and remittances at the price agreed at that moment

    the middleware between a financial company's commercial system and its currency purchasing, with the exchange rate live.

  • The core connected to the commercial CRM

    so sales could see what operations were issuing.

  • Direct-debit collection, reconciled

    against the payment processor, remittance by remittance.

  • A bank's digital account opening

    with cloud functions exposed as an API behind its cloud's gateway, managed cloud databases and private connections —not over the internet— between the cloud and its data center.

  • Intelyvale

    single sign-on with its client's corporate identity in its business voucher portal, in just over three months.
    See the case

We have integrated enterprise systems since 2012: we know how to coexist with legacy platforms and how to evolve toward APIs and events.

The assessment, in two levels

  1. First conversation, at no cost.

    A map of the connections between your systems and the three points where money, time or traceability are most likely being lost.

  2. In-depth assessment, with an agreed scope.

    Which discrepancies are still live, which tax risk to address first, and a roadmap in stages.

Who reviews your assessment: We work with a small number of clients at a time: whoever reviews your assessment stays with your project to the end.

Frequently asked questions

Do we have to change our systems?
No. We work on the layer that connects them, through the interfaces they already expose.
Do you use a commercial integration platform or build the layer?
It depends on where it has to run and who operates it. A vendor's cloud platform speeds up connections between cloud applications; a layer in your own infrastructure gives you control over the data your regulator watches. We compare operating cost, vendor dependency and obligations toward third parties, and recommend one before we start.
What does the regulator require when a third party touches our data?
It varies by entity, service, data and where it is processed, and your Compliance and Legal teams determine it. We prepare the technical evidence that those notices, authorizations or case files require.
Can you connect to our ERP or core even if it's old?
Yes: practically anything that has a door. Through the interfaces the manufacturer supports (services, native connectors); through files or queues; or through its database, with exchange tables or stored procedures agreed with your team, never writing blindly into its tables. We choose together during the assessment.

Start by finding out what gets lost between your systems

Message us on WhatsApp. In the first conversation we identify where money, time or traceability are slipping away between your systems.

Let's talk about your case

Prefer email? Write to us at hola@habil.mx