Full Product Detail
How each workflow runs step by step, who Gigva is built for, and the complete feature list updated as features ship.
Who Gigva Is For
Gigva is not a general-purpose accounting tool. It is designed specifically for Kenyan businesses where M-Pesa is the primary payment method and manual reconciliation is a daily operational cost.
High transaction volume. Zero time to reconcile manually.
The problem
A retail or wholesale shop collecting M-Pesa payments can process 50–300 transactions a day across Paybill and Till numbers. By Friday, someone on the team downloads the M-Pesa statement, opens Excel, and tries to match each line to a sale or outstanding customer balance. A single day's mismatch can take 2–3 hours to trace. Over a month, disputed payments and unposted credits accumulate into material accounting errors that are difficult and time-consuming to untangle.
How Gigva helps
Gigva ingests each payment as it arrives and checks it immediately against open customer invoices. A retail operator starting the day in Gigva sees which customers paid overnight, which invoices are still outstanding, and how yesterday's revenue compares to the same day last week. Daily and weekly reconciliation reports are available without any manual work ready to share with a bookkeeper or accountant at any time.
Outcomes
Match payments to deliveries. Eliminate payment disputes.
The problem
For a logistics or courier business, each delivery generates a payment instruction: the customer pays M-Pesa on receipt of goods. With 40–200 deliveries per day, tracking which payments have arrived and matching each to the correct delivery order becomes a full-time administrative task. Disputes arise when drivers report a delivery as complete but payment is unconfirmed, or when M-Pesa references do not match order numbers in the system.
How Gigva helps
Gigva lets logistics operators load delivery orders as invoices and match incoming M-Pesa payments to specific delivery references. When a payment arrives with the correct order reference, it is reconciled automatically. Unmatched or incorrectly referenced payments are flagged immediately, so dispatch teams can follow up with the driver or customer before the end of the day rather than discovering the discrepancy at week-end.
Outcomes
Multiple daily transactions. End-of-day accounts done automatically.
The problem
Restaurants and food service businesses collecting M-Pesa payments from dine-in customers, delivery orders, or wholesale distributors accumulate dozens to hundreds of transactions per day. Matching those payments to individual orders or customer accounts at day-end is time-consuming. Errors are easy to miss until month-end, when cash flow does not reconcile with the register and tracing the source takes significant time.
How Gigva helps
Gigva provides F&B operators a live dashboard of the day's M-Pesa receipts sorted by time and amount. For businesses with recurring distributor payments, Gigva tracks expected payment cycles and alerts staff when a regular payment is overdue. End-of-day totals are generated automatically with a breakdown by payment type, ready to hand directly to a bookkeeper without additional formatting.
Outcomes
Invoice-based payments. Know exactly who has paid and who has not.
The problem
Clinics, schools, professional services firms, and other invoice-based businesses issue payment instructions to clients and then wait for M-Pesa payments to arrive. Without an automated system, tracking which clients have paid and which invoices remain outstanding requires regularly cross-referencing M-Pesa statements against a debtor list. Unpaid invoices are easy to miss, particularly at month-end when chasing them becomes urgent and cash flow is under pressure.
How Gigva helps
Gigva tracks each issued invoice and matches incoming M-Pesa payments to the correct client account by reference. As payments arrive, invoices are marked settled automatically. Overdue invoices appear on the aging report, giving finance or admin staff a clear, current list of who to follow up with and exactly how much each client owes. Partial payments are tracked and the outstanding balance is updated in real time.
Outcomes
Not sure if Gigva fits your business? Book a 30-minute demo and describe your current payment workflow. We will walk you through a realistic scenario based on your transaction type and tell you honestly whether Gigva will solve your problem.
No marketing descriptions. Exactly how Gigva works, workflow by workflow, with the specific input and output at each step.
From payment received to reconciled invoice, for retail shops processing 50–500 daily M-Pesa transactions.
Customer pays your Paybill or Till
Your customer sends M-Pesa to your registered Paybill or Till number. Safaricom processes the payment and sends a C2B callback to Gigva within 3–5 seconds.
Transaction is recorded immediately
Gigva logs the full transaction: sender name, phone number, M-Pesa reference code, amount, and exact timestamp. This record is immutable: it cannot be edited, only supplemented.
System attempts to match to an open invoice
Gigva compares the payment amount and reference against your open invoices. If the amount matches an outstanding invoice exactly, the invoice is marked paid and the transaction is marked reconciled automatically.
Mismatches are flagged for review
Partial payments, unrecognised references, and amounts that do not match any open invoice are flagged in your dashboard, each with the full transaction detail and the closest matching open invoices.
You resolve flags with one action
For each flagged transaction you choose: match to a suggested invoice, match manually, split across multiple invoices, or mark as other income. Every action is logged.
Reports are available any time
Pull a reconciliation report for any date range: all transactions, their match status, outstanding invoices, and a cash summary. Download as CSV or PDF.
How Gigva surfaces payment anomalies for logistics firms and SMEs before they become problems.
Baseline established over 30 days
Gigva learns your payment patterns during the first 30 days: typical daily volume, average transaction amounts, and which customers pay regularly. This baseline is used for anomaly detection.
Every transaction is scored
Each incoming payment is compared against your baseline. Transactions with amounts significantly above or below your typical range for that customer are flagged for review.
Rule-based checks run in parallel
Alongside anomaly scoring, fixed rules run every time: duplicate reference detection, missing invoice check (no match after 24 hours), and configured revenue thresholds.
Alert created with context
When a score or rule triggers, Gigva creates an alert with the full transaction detail, the specific rule or score that triggered it, and a suggested action.
Alert delivered and resolved
Alerts appear in your dashboard notification panel and are sent to your registered email. You mark each alert resolved or take the suggested action. Resolved alerts are logged with a timestamp.
Updated when features ship. Every feature is available on every plan.