HisabERP integrations

Know what works today, what needs configuration and what is still planned.

The directory uses explicit statuses so an authentication button, callback route or roadmap item is never presented as a fully activated production integration without the required provider setup.

Discuss an integration Review security controls

Connection operations workspace

Integrations

Available3Production-ready paths

Configuration3Provider setup required

Roadmap6Beta + planned

Reference	Date	Record	Branch	Amount	Status
INT-26-0891	31 Aug 2026	Supabase platformCloud foundation	Addis HQ	ETB 126,500	Paid
INT-26-0890	30 Aug 2026	Email and magic-link accessIdentity	Adama	ETB 89,760	Approved
INT-26-0889	29 Aug 2026	Google sign-inIdentity	Hawassa	ETB 45,600	Partial
INT-26-0888	28 Aug 2026	Supabase platformCloud foundation	Addis HQ	ETB 73,200	Posted
INT-26-0887	27 Aug 2026	Email and magic-link accessIdentity	Mekelle	ETB 18,975	Review

Connection directory

A transparent register of the current integration surface.

Provider credentials, commercial agreements and production validation remain separate from the existence of an application path.

Cloud foundationAvailable

Supabase platform

HisabERP uses Supabase for authenticated application access and its PostgreSQL data foundation.

Supported scope

Session-based authentication
PostgreSQL application data
Organization-scoped access model

Configured as the core application platform.

IdentityAvailable

Email and magic-link access

Users can access HisabERP with email and password or request a password-free magic sign-in link.

Supported scope

Email sign-in
Email registration
Password reset
Magic-link authentication

Requires the deployment email and Supabase authentication settings to remain configured.

IdentityConfiguration required

Google sign-in

The application includes the Google OAuth sign-in path for organizations that prefer managed identity access.

Supported scope

Google OAuth entry
Redirect back to the requested workspace
Existing-account authentication flow

Google OAuth credentials and callback settings must be enabled in Supabase.

IdentityConfiguration required

Apple sign-in

The application includes an Apple OAuth sign-in path for deployments that configure the provider.

Supported scope

Apple OAuth entry
Redirect back to the requested workspace
Existing-account authentication flow

Apple developer credentials and callback settings must be enabled in Supabase.

Payments and reconciliationBeta

telebirr reconciliation callbacks

HisabERP can receive token-protected telebirr callback events and normalize them into the reconciliation workflow.

Supported scope

Provider callback endpoint
ETB transaction normalization
Transaction, order and payer references
Organization source mapping

Requires a callback token, source reference and provider-specific implementation validation before production rollout.

Payments and reconciliationBeta

M-PESA Daraja reconciliation callbacks

HisabERP can receive M-PESA Daraja callback events and normalize receipt, amount, phone and order references for reconciliation.

Supported scope

Daraja callback endpoint
Receipt and checkout references
Amount and phone normalization
Token validation

Requires Daraja credentials, callback token configuration and controlled provider testing.

Data exchangeAvailable

Audit CSV export

MFA-verified administrators can export enabled business, authentication and security-alert evidence as spreadsheet-safe CSV.

Supported scope

Business audit export
Authentication audit export
Security-alert evidence
Defined reporting window

Audit export must be enabled in production controls and the administrator session must be AAL2 verified.

OperationsConfiguration required

External monitoring webhook

Structured server errors can be forwarded from the deployment to an external monitoring endpoint.

Supported scope

Structured error forwarding
Deployment-level logging
Operational alert integration

Requires the monitoring webhook environment variable and an external receiving service.

Developer platformPlanned

Public REST API

A documented customer-facing API for approved business records is planned for a future platform phase.

Supported scope

Scoped API access
Documented resources
Token and permission model

Not currently offered as a public production API.

Developer platformPlanned

Business event webhooks

General outbound events for invoices, payments, inventory and customer records are planned.

Supported scope

Signed event delivery
Retry handling
Subscription management

Not currently offered as a general customer webhook platform.

FinancePlanned

Bank feeds

Direct institution feeds are a roadmap item and will depend on supported bank interfaces and commercial agreements.

Supported scope

Statement ingestion
Transaction matching
Reconciliation assistance

No direct bank-feed availability is claimed today.

CommercePlanned

Ecommerce connectors

Connectors for online storefront orders, products and customer records are planned for a later integration phase.

Supported scope

Order import
Product synchronization
Customer mapping

No ecommerce connector is presented as active today.

Production readiness path

An integration becomes “Available” only after the complete path is verified.

Confirm the business use case

Define the exact records, provider events, teams and reconciliation outcome required.

Configure credentials safely

Store provider secrets in deployment configuration rather than source code or browser-visible settings.

Validate provider behavior

Test signatures, tokens, payload variations, duplicate events, failures and recovery handling.

Control production rollout

Document ownership, monitoring, support escalation and the status shown to customers.

Need another connection?

Describe the workflow—not only the provider name.

Share the source system, records involved, expected direction, update frequency, authentication method and business outcome. HisabTech can then assess whether the work belongs in configuration, a controlled beta or the product roadmap.

Submit an integration request