Skip to the content

Integrations

Your ledger stays the ledger.

Hysaab does not replace your accounting system. It does the work inside it.

Accounting systems

Six ledgers ready.
Anything else, connected for you.

One system is connected at a time. Each card says how the connection is made and what passes across it. What is listed for one system is not implied for the others.

OAuth consent

Zoho Books

Authorise once on Zoho’s own consent screen, with no keys to copy. Hysaab discovers your organisation, maps your chart of accounts and posts approved journals back.

  • Two-way journal sync
  • Chart-of-accounts mapping with review
  • Data-centre aware: works with each Zoho region

OAuth consent

Xero

The standard Xero consent flow. Hysaab reads the ledger for reconciliation and can import your history so reports have context from the start.

  • Two-way journal sync
  • Legacy-history import, clearly marked and not re-exported
  • Attachment sync for evidence

OAuth · Intuit flow

QuickBooks

Connect through Intuit’s official authorisation. Hysaab posts approved journals into your QuickBooks company and keeps the account mapping under your review.

  • Two-way journal sync
  • Realm-aware connection
  • Mapped-account gate: journals wait until the accounts are mapped

API key · guided

Odoo

A step-by-step panel shows where to create the API key inside your own Odoo instance. Hysaab authenticates with the key before storing anything, so a mistyped key does not become a connection.

  • Works with self-hosted Odoo and Odoo.sh
  • Legacy-history import
  • Attachment sync

API key · guided

Wafeq

A ledger built for the Gulf. Generate a key in Wafeq and paste it once. Hysaab verifies it, then posts approved journals.

  • Journal posting
  • AED and SAR native
  • Revoke at any time from Wafeq’s side

API key and secret · guided

ERPNext

Point Hysaab at your ERPNext instance with an API key pair. The connection is tested before it is saved, and your general ledger history can come in as clearly marked legacy data.

  • Two-way journal sync
  • Legacy-history import
  • Suits self-hosted instances

Custom connection · scoped with you

Your system

Using something else? We connect Hysaab to your accounting software, whatever it is. The connection is scoped with you in writing before any commitment, and works to the same approval rules as every ledger above.

  • Any accounting software
  • Scoped in writing first
  • Same approval rules

How a connection works

Connect once.
Approve what posts.

The connection gives Hysaab a place to post prepared work. What gets posted is still decided by your approval rules.

01

Connect once.

Authorise on your ledger’s own consent screen, or create an API key with the guided steps. The connection is verified before anything is stored.

02

Agree the approval rules.

You set the thresholds. Anything above your journal-value threshold, any low-confidence coding and any suspected duplicate waits for a person. Account mapping stays under your review.

03

Hysaab posts into your ledger.

Approved journals are posted to the accounting system you already use, with their commentary and evidence kept in Hysaab. Your ledger stays the system of record.

Documents in

No ledger needed
to start.

The screen below is a capture of the Hysaab workspace running its sample dataset. Select it to see it in full.

WhatsApp, Telegram and email

A verified channel is all Hysaab needs.

Send a photo by WhatsApp, forward an email or drop a PDF on Telegram. Every document is read, coded, tax-tested and filed with its evidence, whether or not a ledger is connected.

  • Each document filed with the channel it came by
  • Duplicates are held, not booked twice
  • Anything uncertain comes to a person with the reason
The intake ledger, sample data: each document with its category, channel and outcome.
Hysaab intake ledger: documents received by WhatsApp, email and bank feed, each with a category and an outcome. One email address is redacted.

The intake ledger, sample data: each document with its category, channel and outcome.

Missing your system?

If your accounting system is not among the six above, request an integration and tell us what you run. We do not promise a date until the work is scoped.

Boundaries of a connection

Your system.
Your switch.

A connection is something you grant and can take back. It does not move your books out of the system you chose.

01

One ledger at a time.

Hysaab connects to a single accounting system for each set of books, so there is one source of truth and not two that drift apart.

02

Credentials stay server-side.

Ledger credentials are stored server-side, encrypted, and are not sent to a browser.

03

Revoke when you choose.

Your ledger connection can be revoked at any time, from Hysaab or from the ledger’s side.

Let’s talk

Tell us what you run today.

Bring the accounting system you use and one process that takes too long. We will walk it through the workspace with you, then confirm the scope and fees before any commitment.

Request access Book a demo (opens in a new tab)

Hysaab is opening by invitation. Requests are admitted in the order they arrive.