By 2026 every accounting software vendor pitching to a Hong Kong SME advertises a mobile app. The marketing convergence is striking — “manage your finances on the go,” “real-time visibility from anywhere,” “AI-powered mobile bookkeeping.” The on-the-ground reality is that “has a mobile app” covers a range from a glorified read-only dashboard to a fully-functional production system. The gap matters because for many SME owners — particularly the founders who are out of the office most of the day — the mobile app is the accounting software they actually use.
This guide breaks down what mobile capability for HK accounting software actually means in 2026, the four levels of functionality you’ll encounter, the workflows where mobile genuinely changes behaviour (receipt capture, invoicing, expense approval), the offline-mode question that matters more than vendors admit, and the demo questions that surface real capability through the marketing language. The aim is to make sure the app you’re buying is the one you’ll actually use, rather than the one that looks good in the App Store screenshot.
Four levels of mobile capability
Accounting-software mobile capability falls into one of four levels, and which level a given vendor offers materially shapes what the app is useful for.
Level 1 — Read-only dashboard. The app shows you balance, P&L summary, AR/AP totals, recent transactions. You cannot enter or edit anything. Useful for a quick glance during a meeting or a quick check while travelling, but it’s not bookkeeping. Many entry-tier products and some major vendors’ “lite” tiers stop here.
Level 2 — Read-only with capture. Add the ability to photograph receipts and forward them to the desktop application for processing later. The capture happens on mobile but the bookkeeping work happens elsewhere. This is the most common level among current “we have a mobile app” claims.
Level 3 — Mobile transaction entry. Create and send invoices, record cash payments, post simple expenses, mark invoices as paid. The mobile app is a functional subset of the desktop app for the workflows that matter on the road. This is the level at which a salesperson or a service provider can actually run their day from the phone.
Level 4 — Full functional parity with offline support. Everything the desktop app does, the mobile app does, with offline-first data entry that syncs when connectivity returns. Rare in 2026; mostly seen in cloud-native products designed for mobile from day one. This level is overkill for most SMEs but the right answer for businesses where the field staff are the primary system users.
For most HK SMEs, Level 3 is the realistic target — full enough that day-to-day work can happen on mobile without forcing a desktop session every evening, without paying for Level 4 capability that won’t be used.
Mobile receipt capture
Receipt capture is the single mobile workflow with the highest payoff because it intercepts the receipt at the moment of payment, before it disappears into a wallet to be lost. The accounting software’s mobile app activates the camera, edge-detects the receipt, perspective-corrects, OCR-extracts the merchant / amount / date, and either posts a draft transaction directly or queues the receipt for desktop processing.
The mobile-specific considerations beyond the OCR engine itself (covered in our receipt scanning and OCR guide):
- Capture latency. From “open app” to “receipt captured” should be under 10 seconds. Anything slower and the workflow loses ground to “I’ll do it tonight.”
- Bilingual handling. The mobile-side OCR has the same Chinese-English limitation as the desktop side; some apps tune mobile separately and surprisingly produce different accuracy. Test on real bilingual receipts.
- Multi-receipt batch. When a week’s worth of receipts get caught up at once, the ability to photograph 10 receipts in sequence without quitting the app matters.
- Storage handling. Receipts captured offline must hold reliably until network resumes. Apps that lose receipts during sync are unforgivable.
The right test: spend a week using only the mobile app to capture every business receipt, then check at the end of the week whether all of them are in the system, with reasonable extracted data, ready to post.
Mobile invoicing — when this matters and when it doesn’t
Mobile invoicing — generating an invoice from the phone and sending it to the customer — sounds attractive but matters only for a specific set of HK SMEs. The right question is whether your customers receive an invoice from you at the moment of service delivery, in which case mobile invoicing genuinely changes your working capital cycle.
Cases where mobile invoicing changes behaviour:
- Field service / on-site delivery — a tradesperson finishing a job, a freelance professional ending a session, a delivery driver completing a drop-off. The customer is right there; the invoice can be issued, signed and emailed before the engineer leaves.
- Project-based services — designers, consultants, photographers, who close a project on site and want the invoice to land before the customer’s attention drifts.
- Walk-in trade situations — a small retailer doing a one-off corporate sale, a market vendor processing a credit-card sale, where the customer needs an invoice for their accounting.
For these businesses mobile invoicing meaningfully shortens the receivables cycle. For an office-bound services firm where invoicing happens monthly from the desktop, mobile invoicing is a feature you’ll demo and never use.
The features that matter when mobile invoicing matters: customer search and selection from the phone; line-item entry without too many taps; tax / non-tax handling appropriate to the HK context; PDF generation; email or share-link delivery; signature capture if needed; and immediate posting back to the accounting system so AR is current.
Expense approval and director approval flows
For SMEs with a director who needs to approve expense claims or supplier payments above a threshold, mobile approval is one of the few features that genuinely accelerates the AP cycle. Without it, the bookkeeper waits for the director to be at their desk; with it, the approval happens during the director’s commute.
The workflow:
- Bookkeeper enters the supplier invoice or staff expense claim, attaching the supporting document.
- Software routes the item to the appropriate approver based on threshold rules.
- Approver receives a push notification on the mobile app.
- Approver reviews the item — supplier name, amount, attached document — and approves or rejects with a comment.
- Approved items become payable; rejected items return to the bookkeeper’s queue.
The features to verify on the demo: configurable approval rules (by amount, by expense type, by department); push notification reliability (apps that need the user to open them to see pending items don’t deliver the speed gain); document preview within the app (no need to re-open in PDF reader); and audit-trail logging of who approved what when.
For more complex approval flows — multi-level approvals, departmental routing, conditional escalation — most SME-tier accounting software is intentionally simple, and businesses that need rich workflow may end up integrating with a dedicated approvals tool. For most SMEs the simple “single approver above threshold” flow is the right level.
Offline mode — the real-world test
Most HK is well-connected, but accounting on mobile encounters offline scenarios more often than vendors acknowledge — in MTR tunnels, basement carparks, certain office buildings, on flights, and in mainland-China business travel where roaming is patchy. Apps that fall over when connectivity drops force users back to desktop-only workflows.
The offline behaviour to test:
- Reading existing data offline — can the user see prior invoices, customer balances, recent transactions without a connection?
- Capturing new data offline — can a receipt be photographed, an invoice be drafted, an approval be queued, with the changes syncing when network returns?
- Conflict handling — if two people make conflicting changes while one is offline, what happens at sync?
- Failure mode visibility — does the app clearly indicate when it’s offline and when sync has succeeded? Silent sync failures are the worst.
The simple test: turn on aeroplane mode, try to do a normal day’s bookkeeping work on the app, then turn aeroplane mode off and check that everything synced correctly. Cloud-only apps with no offline capability fail this test instantly; apps that claim “offline mode” with a thin local cache often fail it on the second day when the cache has expired.
What to test before buying
A 30-minute mobile demo with the following test set surfaces real capability:
- Open the app cold (closed in background) and time it from icon-tap to dashboard. Anything over 4 seconds will frustrate.
- Capture 5 receipts in sequence, including 2 TC-language ones. Check the OCR output and the time-per-capture.
- Create and send an invoice end-to-end from the phone. Count the taps required.
- Approve a queued expense item and check that the document attached to the original entry is actually viewable in the app.
- Test offline: turn aeroplane mode on, capture a receipt, draft an invoice, then go online and verify the sync.
- Check the bilingual UI — TC menu labels, TC date formatting, TC search inputs. Many vendors have English-first apps with TC translations that miss in places.
The demo question that often surfaces the most: “show me one of your real customers’ actual usage patterns” (anonymised). Vendors with strong mobile capability will show it; vendors with weak mobile will pivot to desktop features.
How Giga Accounting by 凌峰會計 can help
Giga Accounting by 凌峰會计 ships a mobile app at functional Level 3 — receipt capture, expense entry, customer-tagged invoicing, approval workflows for director sign-off, offline-resilient capture with sync-on-reconnect, and bilingual UI as standard. Mobile is included in the standard licence rather than gated behind a higher tier — the calculation is that a sales person or a tradesperson billing from the field shouldn’t be paying extra for the workflow that earns the company’s revenue.
Get in touch for a 20-minute hands-on mobile-app demo on real workflows, or see our flat per-company pricing. For the receipt-OCR side that mobile capture depends on, see our receipt scanning and OCR guide; for the bank-feed integration that makes mobile-captured transactions auto-match in the back office, see bank feed and auto-reconciliation in HK; and for the broader pricing context where mobile capability often gates a tier, see accounting software pricing in HK.
