Integrations

Operational records live in the platform. Integrations push and pull through a registry and an idempotent queue — so retries never duplicate and provider IDs never replace ours.

Accounting & GL

Push posted invoices, payments and adjustments to your accounting system (for example Manager.io or similar). The integration queue is idempotent, so retries never create duplicates.

  • Posted invoices & credit adjustments
  • Payments and allocations
  • Deposits held and settled
  • Branch expense categories

Notifications & messaging

Operational events — application received, offer issued, invoice posted, ticket resolved — can trigger messages through email and WhatsApp-class providers.

  • Email providers
  • WhatsApp-class messaging APIs
  • In-app notifications
  • Notice acknowledgements

Documents & storage

KYC documents, check-in photos, signatures and policies are stored in secure object storage, with metadata and access control held in the platform.

  • S3-compatible object storage
  • Document metadata & versioning
  • Signed, time-limited access
  • Retention configuration

Utilities & monitoring

Bring in meter, solar, generator and outage data where the provider exposes an API, feeding facility consumption and electricity billing periods.

  • Meter readings
  • Solar generation
  • Generator runtime
  • Outage logs

Connector availability depends on each provider’s API. Named providers are examples, not endorsements or partnerships.

Integration hub

How a record leaves the building.

  • Invoice posted
  • Queue entry (idempotency key)
  • Connector from registry
  • Provider accepts
  • External reference stored
  • Idempotent by design

    Retries after a timeout reuse the same key, so the accounting system never receives the same invoice twice.

  • External references

    Provider IDs are stored next to the record. Internal UUIDs and business numbers stay authoritative.

  • Operational source of truth

    If you use the GL integration, your accountant keeps the ledger; the platform keeps the operational facts behind it.

Tell us what you need to connect.

Book a 45-minute demo. Bring your hierarchy — cities, clusters, branch count — and we’ll walk through admissions, the bed map, billing and scoped access against it.