The Integration Roadmap: What Connects Today, What Is Next
The list vendors do not publish. Direct bank feeds, other mobile money rails, other tax authorities, other accounting packages, inbound email, marketplaces, scheduled record syncs — with the reason for each and what to do instead.
An integrations page is a list of what exists. The list that would actually help you decide is the other one, and no vendor publishes it — partly because it reads badly, and partly because writing it down requires knowing your own product better than a logo grid demands. This is ours. It exists so that nothing on it can be discovered in month four.
Banking
Bank reconciliation is built; a live connection to your bank is not. You import the statement your bank already gives you — CSV with a column mapping saved per bank, or OFX — and a re-imported or overlapping file adds nothing twice. Lines are auto-matched to ledger entries where they agree, suggested where they nearly do, and completing a reconciliation records it and locks every line it cleared. What is absent is an open-banking style connection that pulls lines from the bank on its own.
What to do instead: download the statement and import it, weekly or monthly. M-Pesa collections also auto-match on the invoice number, which covers most receipts for most Kenyan SMEs. Bank reconciliation explained sets out the process itself.
Payment rails
What moves money and what does not
M-Pesa via Daraja
Collections and disbursements both directions, on your own credentials.
Paystack
Card collection, on your own keys.
Airtel Money, T-Kash
Not integrated. Payments are recorded manually like any other receipt.
MTN MoMo, Orange Money, Wave, Moov
Not integrated. This is the constraint that makes the francophone and West African markets harder for us than the marketing suggests, and we say so on those pages.
Bulk payment files
An approved supplier payment run produces a CSV of its bank-transfer lines in the format most Kenyan bank portals accept for bulk payments.
Bank transfer initiation
Sending a transfer straight to a bank from here, rather than uploading the bulk file to the bank’s portal.
Card present / terminals
No integration with any physical card terminal. A POS sale settled by card is recorded as settled by card.
Tax authorities
eTIMS in Kenya is the only fiscal integration. Nothing transmits to FIRS in Nigeria, ETA in Egypt, EFRIS in Uganda, EBM in Rwanda, EFD in Tanzania, GRA in Ghana or SARS in South Africa. In each of those markets figures can be produced and reconciled against, and somebody files them.
Within Kenya, reversals transmit as well as sales. A cancelled invoice, a POS return and a credit note applied to an invoice each file a refund receipt to KRA that names the original document, so the output VAT a credit note reduces is reduced at KRA too.
Accounting packages
QuickBooks Online only, one direction, on a button. Vendors, items and purchase orders pushed out; nothing read back; no schedule. No Sage, no Xero, no Tally, no Zoho Books, no Pastel, no SunSystems. Also nothing that reads a competing product's export format for migration purposes — there is no QuickBooks reader, no Tally importer.
What to do instead: the boundary between operational record and statutory book is real and worth designing deliberately rather than hoping a connector removes it. Agreed reports, in an agreed format, on an agreed day of the month. What the QuickBooks sync does has the full shape of it.
Messaging and support channels
Direction matters more than presence
| Channel | Out | In |
|---|---|---|
| Yes | Yes | |
| SMS — three providers | Yes | No |
| Teams, Slack, Google Chat, Discord, Telegram | Yes | No |
| Yes | No | |
| A ticket created from a customer’s WhatsApp message | No | Yes |
Built and maintained Configurable by you, not maintained by us Not built
WhatsApp is the one channel that receives: an inbound message opens a helpdesk ticket, through each workspace’s own Meta app. Every other channel is outbound only, so there is no email-to-ticket and a reply to an SMS or a chat alert is not read.
E-commerce and marketplaces
No Shopify, WooCommerce, Magento, Jumia, Kilimall or Amazon integration. No order poller, no stock publisher, no listing sync.
What to do instead: two real routes exist and both work. The API can be read for stock and price to feed your own storefront; writing orders back through it is being built. Or a no-code platform such as Zapier or Make can sit between the storefront and the inbound webhook, which starts your workflows from a storefront event, needs no developer and covers the notification case well. What neither gives you is a maintained, tested marketplace connector, and pretending otherwise would be the kind of claim this page exists to prevent.
Scheduling, feeds and the shape of what is missing
Two structural absences that matter more than any individual logo:
- No scheduled record sync. Salesforce, Notion, Airtable, Mailchimp and calendar pushes run when somebody presses "sync now". Document archiving to your own storage is the exception and is event-driven. Nothing else runs nightly.
- Nothing is pulled in on a schedule from any external business system. Inbound is push-only, through one authenticated webhook. If your plan depends on something being fetched hourly, whoever owns the other end has to push it.
- No change feed and no per-record webhooks on the API, so a continuous two-way sync is polling, which will drift and will hit rate limits. Do not architect around it.
- No OpenAPI specification, no sandbox, no version guarantee on the API. It is real and it is not a platform.
- No SQL access or query workbench. Reporting is the reports, plus exports, plus the API.
Hardware and identity
Barcode scanners work because they behave as keyboards, which is the correct and boring answer — there is no scanner driver or device SDK. Label printing goes through generated label output rather than a printer integration. No temperature or sensor integration, so cold-chain breaches are invisible to the system. On identity, Google and Microsoft sign-in exist, with the deliberate rule that a user must link their account after a password login first; there is no SAML, no SCIM user provisioning, and no directory sync.
Why publish this
Because every item on it is something a prospect would otherwise find out after signing, and because the alternative — a logo wall — transfers the discovery cost from us to you. If something here is a condition of your buying, say so. Several of these exist as gaps we know about and would build for a client who asked in writing; none of them will be built because a page implied they were already there.
Our take
The absence most likely to change your decision is inbound email: WhatsApp messages arrive as tickets, but a message to your support address lands nowhere. Check that against your own process before anything else on this page. Bank reconciliation runs from imported statements rather than a live feed, which is a weekly habit rather than a gap; everything else here is a workaround away.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsTell us which of these matters
If something on this list is a condition of your buying, that is a useful conversation rather than an awkward one — several of these are gaps we know about and would scope for a client who asked.
See the integrationsFrequently asked questions
Do you integrate with bank feeds?
Not as a live connection to the bank. Bank reconciliation itself is built: import the statement as CSV or OFX, let the lines auto-match to the ledger where they agree, resolve the rest, and complete the reconciliation, which locks every line it cleared. Re-importing an overlapping statement adds nothing twice.
Which mobile money providers are supported?
M-Pesa through Daraja only, both directions, on your own credentials — plus Paystack for cards. Airtel Money, T-Kash, MTN MoMo, Orange Money, Wave and Moov are not integrated, which is the constraint that makes the francophone and West African markets genuinely harder for us than a marketing page would suggest.
Can customers reach us over WhatsApp through the system?
Yes. A workspace connects its own Meta app, and an inbound WhatsApp message opens a helpdesk ticket or threads onto the sender’s open WhatsApp ticket; agents reply over WhatsApp inside Meta’s 24-hour window. SMS, chat tools and email are outbound only, so email-to-ticket is a channel we can add.
Is there an e-commerce integration?
No maintained connector for Shopify, WooCommerce, Magento, Jumia, Kilimall or Amazon. Two real routes exist: read stock and price from the API to feed your own storefront (writing orders back through it is being built); or put a no-code platform between the storefront and the inbound webhook, which needs no developer. Neither is a tested marketplace connector and we will not describe them as one.
Which accounting packages connect?
QuickBooks Online only — one direction, on a button, pushing vendors, items and purchase orders. No Sage, Xero, Tally, Zoho Books or Pastel, and no reader for any competing product's export format for migration purposes. The boundary between operational record and statutory book is real and worth designing rather than hoping a connector removes.
Why publish a list of what you do not do?
Because every item on it would otherwise be discovered after signing, and a logo wall transfers that discovery cost from us to you. Several of these are gaps we know about and would scope for a client who asked in writing. None of them gets built because a page implied it already existed.
