The decision in brief

Automation removes repetitive manual steps. Integration lets systems exchange data reliably. The two belong together: automation without integration just moves the manual copying somewhere else, and integration without a clear process spreads bad data faster. Start with one painful workflow, agree the data and the rules, connect only the systems it needs, and keep people in charge of approvals and exceptions.

Automation and integration are different jobs

  • Process automation handles triggers, rules, approvals, reminders, notifications and scheduled jobs, such as sending a request to the right approver and recording the decision.

  • Integration moves data between systems, through an API, a file transfer, a database link or a scheduled import.

  • Desktop robots that imitate a person's clicks and keystrokes can bridge a gap, but they break easily when a screen changes. Prefer documented interfaces where they exist. Watabe Digital's base packages exclude desktop robotic automation.

Choose the right first workflow

Good candidates are repeated, rule-based and painful: the same data typed into two systems, approvals that stall in email, monthly reports assembled by hand, or payments matched to records manually. Examples include SACCOS management reporting, donor reporting from several project sheets, invoices flowing into accounts, and mobile money reconciliation. Avoid starting with processes that have unclear rules, many rare exceptions or that depend on judgement.

Integration options

  • Documented API or connector. The most reliable option when the vendor supports it.

  • Secure file exchange. Scheduled export and import of CSV or spreadsheet files. Simple and often enough.

  • Events or webhooks. One system tells another when something happens.

  • Middleware or an integration platform. Useful when many systems must be connected.

  • Direct database access. Risky. Do not write into another system's database without the vendor's agreement.

  • Undocumented interfaces. Fragile, and a poor foundation for anything important.

Design rules for reliable integrations

  1. Name a system of record for each kind of data, such as customers, loans or invoices, so everyone knows which copy is correct.

  2. Agree a data contract: the fields, formats, identifiers and who owns them.

  3. Plan for failure. Use controlled retries and alerts, and make sure repeating a message cannot create a duplicate record.

  4. Reconcile automatically. Compare totals between systems and report differences.

  5. Keep logs and an audit trail of what moved, when and who approved it.

  6. Secure access. Give each connection only the permissions it needs, store credentials safely and change them when staff leave.

  7. Manage change. Decide what happens when a vendor changes its interface.

  8. Keep a manual fallback so work continues if an automated step fails.

Connection points specific to Tanzania

  • Mobile money. Payments usually connect through provider or aggregator interfaces, and reconciling settlements matters as much as accepting payments. See our guide to mobile app payment integration.

  • SMS and messaging. Notifications carry usage fees and involve personal data, so handle consent and contact details carefully.

  • GePG. The Government Electronic Payment Gateway is a centralised system connected to electronic revenue collection channels, used by public institutions and payment service providers. Its public site does not publish integration guidance, so obtain technical documentation through the responsible ministry or your payment provider.

  • Fiscal receipts. The Tanzania Revenue Authority requires many businesses to issue fiscal receipts using electronic fiscal devices or approved systems. Requirements and approved suppliers change, so confirm the current rules with TRA before designing billing integrations.

  • Patchy connectivity. Where connections drop, queue changes locally and sync later. See offline data synchronisation for NGOs.

  • Data protection. Personal data moving between systems must be protected and used only for its stated purpose. See our guide to ICT compliance in Tanzania.

Scope and budget

Watabe Digital's published planning guidance lists these packages, all excluding VAT:

  • Workflow Automation Sprint: TZS 6,000,000 over 3 to 4 weeks for one workflow across two applications.

  • Connected Workflow Programme: TZS 15,000,000 over 6 to 8 weeks for up to three workflows and three applications.

  • Business System Connector: TZS 7,500,000 over 3 to 5 weeks for two systems, a one-way exchange and up to three business objects.

  • Connected Systems Delivery: TZS 18,000,000 over 6 to 9 weeks for up to three systems, two-way flows and ten endpoints.

Each automated workflow is scoped at up to eight steps, two approval roles and three exception paths, and human approval remains mandatory. Custom connectors, AI agents, new software licences, message fees, process redesign beyond the chosen workflow, payment gateways, undocumented interfaces, historical data migration, new application development and vendor access fees are outside the base packages. A written proposal confirms scope. See the pricing guidance and our guide to integration requirements.

Measures of success

  • Staff hours spent on the process, before and after.

  • Error and rework rates.

  • Cycle time from request to completion.

  • Number of manual touches per case.

  • Failed transfers and time taken to fix them.

  • Differences found in reconciliation.

Record a baseline before you start, or you will not be able to prove the change.

Common mistakes

  • Automating a broken process.

  • Connecting many systems at once.

  • Removing human approval where accountability matters.

  • Building on undocumented interfaces.

  • No reconciliation, so errors go unnoticed.

  • No baseline, so benefits cannot be shown.

Questions to ask a supplier

Which workflow and systems are in scope, and which are excluded? How are failures, retries and duplicates handled? How will we reconcile totals? Who owns the credentials, code and documentation after handover? What are the recurring fees for messages, licences and support?

How Watabe Digital can help

Our automation service delivers workflow approvals with audit trails, automated data pipelines and notifications, and our integration service covers API layers, mobile money and database connections with retries, reconciliation and monitoring. See our business process automation service, our systems integration service or book a strategy session.

References

Requirements, prices and provider terms change; verify current details before you commit.