Author: kenneth

Outside Hong Kong, “bank feed” is taken for granted. In the US, UK and Australia, almost every business bank account streams transactions automatically into the accounting software, often with same-day matching. In Hong Kong, the picture is much less clean. Some banks offer a real API, others rely on monthly statement uploads, and most SMEs end up with a hybrid setup that is neither fully automated nor fully manual.

This guide is for HK SME owners and bookkeepers trying to figure out the actual state of bank feeds in 2026 — which banks support what, how FPS reconciliation works, where Open API HK has and has not delivered, and what to ask a software vendor before signing a contract that promises “automatic bank reconciliation.”

---

Why HK is harder than other markets

Three things make Hong Kong bank reconciliation more involved than the marketing brochures suggest:

• Fragmented banking landscape. The big four (HSBC, Hang Seng, BOC, Standard Chartered) each have different SME products and different API maturity. Throw in eight virtual banks, plus DBS, Citi, Bank of East Asia and several second-tier banks that many SMEs use, and software vendors have to integrate with a long tail.
• HKMA Open API is voluntary in Phase III/IV. The framework exists, but participation is uneven. A vendor can claim “Open API HK ready” and still only support read-only access to one bank.
• FPS is fast but the reconciliation reference field is short. A 35-character payment reference is not a lot of room for an invoice number plus a customer code. Half the auto-matching failures we see come from FPS payments missing or mangling the reference.

Add the fact that many HK SMEs run two or three bank accounts deliberately (HKD operating, USD operating, HKD payroll) and the auto-reconciliation problem multiplies.

---

The current state in 2026: which banks actually have a feed

The picture changes faster than this article can keep up with — confirm directly with any bank before relying on these notes — but as of 2026:

• HSBC. The most mature SME API offering. HSBC Connect and the HSBCnet API let approved third-party software pull transactions on a daily basis. Most major HK accounting platforms have a direct integration. Onboarding takes a couple of weeks because HSBC’s authorisation process is real KYC, not click-to-approve.
• Hang Seng. HSBC’s local subsidiary has its own SME banking platform with selective API availability. Coverage is improving but still patchier than HSBC proper.
• Bank of China (HK). Statement download is reliable; live API for SMEs is limited. Most users still operate on a monthly upload cycle.
• Standard Chartered. Straight2Bank is robust for larger corporates; the SME-tier API offering is more limited.
• Virtual banks (ZA Bank, Mox, WeLab, Airstar, livi, Fusion, PAObank, Ant Bank). Variable. Some have published Open API HK endpoints; others still expect users to download CSVs manually. The picture is genuinely moving — what was true twelve months ago is often stale.
• DBS, Citi, BEA. Mid-tier coverage. CSV export is universal; live feeds depend on the SME tier and the software integration.

The practical rule of thumb: if you bank with HSBC, ask whether your accounting software has the direct integration switched on. If you bank with anyone else, expect at least some monthly statement upload work for the foreseeable future.

---

FPS reconciliation: faster, but messier

Faster Payment System has changed the cash-handling rhythm of HK SMEs. A customer can FPS HK$50,000 to your account at 11pm on a Sunday and the transaction lands instantly. The reconciliation challenge is matching that incoming transfer to the right invoice when the reference field is short, often missing, and sometimes used for a memo rather than an invoice number.

Three habits keep FPS reconciliation under control:

• Standardise the reference format you ask customers to use. Something like INV12345 or ACR0042-INV12345 if you have a customer code. Print it on every invoice in the same format.
• Configure the software with reconciliation rules that recognise common reference patterns and auto-suggest the matching invoice.
• Keep an unmatched-receipts queue visible to whoever sends invoice reminders. If a customer paid but the reference was wrong, the reminder needs to stop.

---

What “auto-reconciliation” actually means

Software vendors use “auto-reconciliation” to describe a spectrum that ranges from “we import the statement for you” to “we automatically apply payments to invoices with no human intervention.” It is worth being precise about what each layer actually does:

1. Import. Transactions come in from the bank — via API, CSV, or MT940 file. This is the easy part.
2. Categorisation. Each transaction is suggested a GL account based on payee, narrative, or rules you set up. Still requires a human to confirm.
3. Matching. Incoming receipts are auto-matched to outstanding invoices based on amount, customer, date, and reference. The match rate depends heavily on how disciplined your customers are with reference fields.
4. Reconciliation closure. Confirmed transactions are tied to GL entries and the bank balance per the system equals the bank balance per the statement. This is the actual “reconciled” state — and it still needs a person to take responsibility for it.

“Fully automatic” is rarely a useful goal. The realistic target is to compress what used to be a four-day month-end exercise into a 30-minute review session.

---

The CSV / MT940 fallback

For banks without a live API, the fallback is statement upload. CSV is universal but inconsistent — every bank uses slightly different column names and date formats. MT940 is more standardised (it is the SWIFT format) and most professional accounting software can ingest it cleanly. If you bank with a smaller institution, ask whether they support MT940 export; it usually saves the bookkeeper from manual reformatting.

---

What to ask the software vendor

Before committing to a platform on the strength of “automatic bank reconciliation,” ask:

• Which HK banks do you have a live API integration with, by name?
• Is the integration read-only (transaction download) or two-way (payment initiation)?
• How often does the feed refresh — same-day, end-of-day, or T+1?
• How do you handle CSV upload for non-API banks? Is it bank-template-aware or does the user have to map columns manually?
• Do you support MT940?
• What is the matching engine like — pure rule-based, or does it learn from confirmed matches over time?
• How are FPS payments handled, especially when the reference field is non-standard?
• Is bank feed included in the standard licence, or gated behind a higher tier? (See our accounting software pricing guide — bank feed is one of the most common upgrade triggers.)

The answers will sort the serious vendors from the marketing-led ones in about ten minutes.

---

Why this matters for audit

Bank reconciliation is the spine of audit preparation. If the bank balance per the system does not tie to the bank statement at year-end, the auditor’s first task is to figure out why — and the meter is running. A clean monthly reconciliation rhythm, even when partially manual, is worth far more than an aspirational “fully automatic” claim that quietly leaves three months unreconciled. We covered this from the audit-prep side in our piece on the first-time audit for a HK company.

---

How Giga Accounting handles bank feeds in HK

Giga Accounting by 凌峰會計 supports direct bank feed integration with the major HK banks where APIs are available, MT940 import for the rest, configurable matching rules, and an FPS-aware reconciliation queue. Bank feed is included in the standard licence — not a paid upgrade.

If you would like a walkthrough of how reconciliation looks in practice, start at the cloud accounting page or compare against alternatives in our free accounting software guide — the bank feed limitations of free tools are usually the first reason businesses move on. For the broader 2026 picture, our HK accounting software buyers guide compares feed coverage across the main platforms.

For most Hong Kong SMEs, the two-tier profits tax regime is the single biggest tax saving available — and also one of the most misunderstood. The rule sounds simple: the first HKD 2 million of profits is taxed at a reduced rate, and everything above is taxed at the standard rate. In practice, the connected-entity rules, the nomination requirement, and a few edge cases around partnerships and sole proprietors catch a lot of businesses out.

This guide explains how the two-tier profits tax in Hong Kong actually works, how much you can really save, and how to avoid the single most common mistake that causes groups of companies to lose the benefit altogether.

---

How the two-tier regime works

Hong Kong’s two-tier profits tax regime came into effect from the year of assessment 2018/19 and is still in force in 2026. The rates depend on whether you operate as a corporation (limited company) or an unincorporated business (sole proprietor or partnership).

• Corporations: first HKD 2 million of assessable profits at 8.25%; remainder at 16.5%.
• Unincorporated businesses: first HKD 2 million of assessable profits at 7.5%; remainder at 15%.

If a limited company earns exactly HKD 2 million in a year, its tax bill is HKD 165,000 under the two-tier rate rather than HKD 330,000 under the flat 16.5% rate — a saving of HKD 165,000. This is why qualifying matters.

---

The connected-entity rule: the single biggest pitfall

Only one entity within a group of connected entities can benefit from the two-tier rate in any given year. This is not optional; it is the law, and it catches many HK founders off guard.

Two entities are “connected” if one controls the other, or both are controlled by the same person. “Control” is defined broadly and includes holding more than 50% of the shares, voting rights, or income. Connected entities can include:

• Parent companies and their subsidiaries. Any subsidiary owned more than 50%.
• Sister companies owned by the same individual or holding company.
• A limited company and a partnership that share a common controlling person or entity.
• Two sole proprietorships run by the same person counting as connected.

So if you incorporated three companies to split your operating business, your property holding, and your consultancy, only one of those three can enjoy the reduced rate in any given year — the other two will be taxed at the full 16.5% from the first dollar of profit. The choice is yours, but you must nominate which one.

---

How to elect: the nomination mechanism

Electing into the two-tier rate is done when filing the annual profits tax return (BIR51 for corporations, BIR52 for partnerships). The election is made on a year-by-year basis, meaning you can switch which entity gets the benefit each year to match which one has the highest expected taxable profits.

Practical steps your accountant will take:

1. Identify every connected entity as at the end of the year of assessment. Include any dormant companies — they count.
2. Project the taxable profit for each entity. Before-tax profit is not the same as taxable profit (add-backs for entertainment, depreciation, etc.).
3. Nominate the entity with the highest expected profit up to HKD 2M. Beyond HKD 2M the rate equalises, so the saving is maximised by picking the entity that will use the full HKD 2M bracket.
4. Tick the election box on the nominated entity’s BIR return and leave it unticked on the others.
5. Document the reasoning. If the IRD ever queries the nomination, a simple file note saves a lot of explanation later.

There is no pre-approval required — the IRD sees your election when the returns arrive. But the onus is on you to get it right; claiming the rate on two connected entities in the same year will trigger a reassessment.

---

When the two-tier rate does NOT help

A few situations where electing in is either pointless or actively harmful:

• Group with losses. If the profitable entity is already below HKD 2M and the loss-making entity is connected, the loss-maker cannot benefit from the rate (no profit to tax). This is usually fine — nominate the profitable one.
• Entities already enjoying other tax concessions. Ship operators and certain fund managers have their own concessionary regimes. The two-tier rate cannot stack.
• Start-ups planning a quick sale or group reorganisation. Consider which entity the benefit is worth most to under your planned structure.

---

Common misunderstandings

“Every HK company gets 8.25% on the first HKD 2M.” No. Only one entity per group. A solo company with no connected entities gets it automatically by electing.

“The election carries over year to year.” No. It is made on each year’s return. You can (and sometimes should) nominate a different entity next year.

“Dormant companies don’t count.” They do. A dormant HK company owned by the same shareholders is still a connected entity.

“The rate applies to revenue under HKD 2M.” No — it applies to assessable profits under HKD 2M. A company with HKD 10M in revenue and HKD 1.5M in profits still qualifies for the full reduced rate.

“I can split my business into two companies to double the benefit.” No. Connected-entity rules exist precisely to stop this. Two connected companies still share one HKD 2M bracket between them.

---

Worked example: a three-company HK group

Imagine a founder owns three HK limited companies: a trading arm with HKD 3M profit, a consultancy with HKD 1M profit, and a property holding with HKD 200K profit. All three are owned 100% by the same individual.

Only one can elect the two-tier rate. The best nomination is the trading arm, because it fully uses the HKD 2M reduced-rate bracket. Its tax under two-tier: HKD 2M × 8.25% + HKD 1M × 16.5% = HKD 330,000. Compared to a flat 16.5% on HKD 3M (HKD 495,000), the saving is HKD 165,000.

The consultancy and property holding are taxed at 16.5% flat. In a later year, if the consultancy’s profit grows and the trading arm’s shrinks, the founder can re-nominate.

---

Let us help you nominate correctly

Giga Accounting by 凌峰會計 helps HK SME groups map their connected entities, project annual profits, and nominate the right company each year. If you run more than one HK entity — even if one is dormant or just an investment-holding shell — it is worth a 20-minute conversation before you sign this year’s BIR51.

Read our companion guide to Hong Kong profits tax for small businesses, or head to the Giga Accounting by 凌峰會計 homepage to see our full range of bookkeeping and accounting services. We will review your group structure, nominate the right entity, and make sure nothing is left on the table.

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.

Running an online store in Hong Kong looks simple from the outside: an order comes in, a payment lands, a parcel ships. But anyone who has tried to close the books on a Shopify or Shopline business knows the truth — order counts never match payout amounts, marketplace fees eat the margin invisibly, and the bank statement looks nothing like the sales report.

This guide is for HK e-commerce sellers who have outgrown spreadsheets and want accounting software that actually understands how online stores get paid. We cover what makes e-commerce accounting different, the reconciliation problems that trip up most sellers, and what to look for in a system that handles Shopify, Shopline and HKTVmall in one place.

---

Why E-commerce Accounting Is Different

Generic accounting software was designed for businesses that send invoices and receive payments — one transaction, one customer, one entry. E-commerce flips this on its head:

• One sale becomes many entries. A HK$500 Shopify order arriving in your bank as a HK$478.65 Stripe payout has at least four moving parts: the gross sale, the gateway fee, the platform commission, and the FX adjustment.
• Payouts are batched, not per-order. Stripe might send one weekly deposit covering 240 orders, refunds and disputes. Your accounting system has to break that single bank line back into hundreds of revenue and fee entries.
• Inventory lives in multiple places. The same SKU sits on Shopify, Shopline and HKTVmall — and in your physical warehouse. Stock decrements have to flow into the books from each channel without double-counting.
• Returns and chargebacks happen days or weeks later. Revenue you booked in March can disappear in May. Generic software assumes a sale, once entered, stays entered.

None of this is impossible to handle manually — sellers do it every month with Excel exports and patience. The question is whether software can do it for you in less time than you spend now.

---

The Payout Reconciliation Problem

This is the single biggest e-commerce accounting headache in Hong Kong. Stripe, PayPal, Shopify Payments, AlipayHK, WeChat Pay HK and FPS all aggregate dozens or hundreds of transactions into a single deposit, after fees, after refunds, after currency conversion. The deposit hits your HSBC or Hang Seng account looking nothing like the order list.

Good e-commerce accounting software solves this by:

1. Pulling the daily payout report from the gateway via API.
2. Matching the bank deposit to the payout total.
3. Splitting the payout into its components — gross sales, refunds, gateway fees, chargebacks, currency conversion adjustments.
4. Posting each component to the right account in your ledger.

If a system can’t do this — if you still have to download a CSV and parse it yourself — you haven’t bought e-commerce accounting software. You’ve bought a glorified ledger.

---

Marketplace Fees, Gateway Fees, and the Gross-vs-Net Trap

HK e-commerce sellers commonly book revenue at the net amount that lands in the bank. This is wrong, and it costs you in two ways. First, your top-line revenue looks lower than it actually is, which matters when you apply for credit, take on investors, or compare against competitors. Second, you lose visibility on what each sales channel is really costing you.

The right approach is to book revenue gross — the full HK$500 of the order — and post the fees separately as expense lines:

• Gateway processing fees (Stripe roughly 3.4% + HK$2.35, PayPal varies by region, AlipayHK around 1.2–2%) — these go to a “Payment Processing Fees” expense account.
• Marketplace commissions (HKTVmall takes 15–25% depending on category, Shopline charges per-plan) — these go to a “Marketplace Fees” expense account.
• Platform subscription (Shopify Basic at US$32/month, Shopline at HK$300+/month) — separate “Software Subscriptions” line.
• Refund fees — some gateways keep their cut even on refunded transactions.

Booked correctly, you can finally answer the question “which channel is most profitable?” — often with surprising results.

---

Multi-Currency Payouts: What to Know

If you sell to overseas customers — and most HK e-commerce sellers do — your gateway will collect in USD, RMB, EUR or GBP and convert to HKD on payout. Each conversion creates a foreign exchange gain or loss that has to be recognised separately under HKFRS.

The mechanics of multi-currency accounting (realised vs unrealised FX, period-end revaluation, rate tables) deserve a guide of their own — see our multi-currency accounting guide for Hong Kong businesses for the full treatment. For e-commerce specifically, the must-haves are:

• Multi-currency invoicing so overseas customers see prices in their currency.
• Automatic FX gain/loss posting when payouts convert to HKD.
• HKD reporting with HKFRS-compliant disclosure of FX exposure.

---

Returns, Refunds, and Chargebacks

HK consumer protection rules and platform policies mean returns are a fact of life — especially in fashion, electronics and skincare. Your accounting system needs to handle three cases distinctly:

• Same-period refund. Customer cancels in week 1, refund processed in week 1 — net out in the same accounting period.
• Cross-period refund. Customer returns in April for an order paid in March — March books closed; the refund hits April. You need a contra-revenue entry, not a deletion.
• Chargeback. Bank disputes the transaction. Gateway claws back funds plus a penalty fee. Treat as a separate “chargeback” expense, not a refund.

Inventory needs to flow back the same way: returned stock is restocked (or written off if damaged), not just “deleted” from the order.

---

Inventory Across Shopify, Shopline, HKTVmall, and Your Own Warehouse

Multi-channel sellers face a real risk: oversell. The same SKU shown as in-stock on three platforms can sell three times before any platform updates its count. From an accounting view, this matters because:

• Inventory valuation methods (FIFO, weighted average) need consistent input across channels.
• Cost of goods sold must reflect actual stock movements, not platform-reported sales.
• Stock write-offs (damage, expiry, theft) need a documented IRD-friendly trail.

For sellers who also run a physical store or warehouse, integration with your retail accounting setup matters as much as the e-commerce side.

---

What to Look For When Choosing E-commerce Accounting Software

A practical checklist for HK e-commerce sellers in 2026:

• Native or app-based connector to your platform(s) — Shopify, Shopline, HKTVmall, WooCommerce. If the connector is “via Zapier with manual mapping”, expect breakage.
• Gateway-level payout reconciliation — not just bank import.
• Multi-currency with HKFRS disclosure.
• Gross-revenue accounting with separate fee lines.
• Inventory that handles multi-channel writebacks.
• Storage and data retention for at least 7 years — IRD requires it, and e-commerce volumes pile up fast. Giga Accounting includes 10 GB with no need to purge old transactions, which matters when a single year produces 50,000+ order lines.
• Multi-user access with role separation — the warehouse team should see fulfilment without seeing margin; the bookkeeper should reconcile without changing prices.

---

Talk to Us About Your E-commerce Stack

Every HK e-commerce business is a slightly different combination of platforms, payment methods and fulfilment models. There’s no single “right” software — only one that fits your stack. Giga Accounting by 凌峰會計 handles HK gateway reconciliation, multi-currency payouts, and multi-channel inventory in one place, with both desktop and cloud options depending on how your team works.

Have a look at our cloud accounting setup if your team works across locations, or our Windows desktop version if data sovereignty matters more than remote access. For comparison shopping, start with our 2026 buyers guide for HK SMEs.

Accounting software is rarely the only system in a Hong Kong SME’s stack. A typical 2026 SME runs a sales tool (e-commerce platform, retail POS or CRM), a payment processor (Stripe, FPS, payment gateway), a payroll system (sometimes inside accounting, sometimes a separate platform), and an accounting system that everything else feeds into. Whether all those pieces work together smoothly or generate a constant manual reconciliation chore comes down to the quality of each system’s API and the integrations that ride on top of them.

This guide is a vendor-neutral walk through accounting-software API and integration questions for HK SMEs — what a good vendor API actually looks like, the common stacks SMEs build, the webhook-vs-polling pattern question, security considerations including authentication and data residency, when an integration partner is worth more than DIY, and the demo questions that surface real API quality. The framing is the SME selecting accounting software with integration in mind, not the developer building integrations from scratch.

---

What a good vendor API looks like

Most accounting software vendors in 2026 advertise an API. The label hides large differences in actual capability. A good vendor API for SME-scale integration has these properties:

• RESTful design with predictable URLs and HTTP verbs. A developer should be able to read the documentation and predict the endpoint for any operation. Inconsistent or RPC-style endpoints multiply integration cost.
• OAuth 2.0 authentication with refresh tokens, supporting the standard “user authorises, app gets long-lived access” flow. API-key-only authentication still exists but is harder to manage at scale.
• Rate limits that allow real workloads — typically 60–120 requests per minute per app, with 429 responses and Retry-After headers when limits hit. Vendors with rate limits below 30/minute force throttled integrations and complex backoff logic.
• Webhook support for event notifications (new invoice paid, transaction posted, customer updated) so integrations can react in near-real-time without polling.
• Pagination on list endpoints with cursors or stable offsets — important once a customer has thousands of transactions.
• Versioning so the vendor can evolve the API without breaking existing integrations. Sudden breaking changes destroy trust.
• Test / sandbox environment separate from production, with the same API surface but isolated data — essential for development and CI testing.
• Useful documentation — request/response examples, error code lists, common integration patterns. Bad documentation is the single biggest hidden integration cost.

Two additional points specific to HK accounting software: HKD as the base currency must be properly handled (some vendors built around USD or AUD treat HKD as a “minor currency” with edge-case bugs in tax / reporting endpoints), and bilingual data — TC merchant names, TC customer addresses — must round-trip cleanly through the API without encoding loss.

---

Common HK SME integration stacks

Three typical stacks cover most HK SME integration patterns in 2026:

The e-commerce stack: Shopify (or Shopline or HKTVmall) → payment gateway (Stripe, AsiaPay, eWAY) → accounting. The integration challenge is reconciling Shopify orders to Stripe payouts to the bank deposit, with platform fees, payment processor fees, refunds and FX adjustments correctly attributed. The accounting integration usually pulls daily order summaries, books revenue at gross with separate fee deductions, and matches the resulting net to the actual bank deposit. See our e-commerce accounting software guide for the deeper vertical view.

The professional services stack: CRM or project management (HubSpot, Pipedrive, Asana) → time-tracking tool (Toggl, Harvest) → invoicing → accounting → payment processor. The integration pulls timesheet data into invoices, posts the invoice to AR in accounting, then reconciles incoming customer payments to AR closure. The biggest pain point is making sure project codes flow consistently from time entry through to revenue recognition.

The retail / multi-channel stack: POS (Square, FlexiBar, Storehub) → inventory management → accounting → bank feed. The POS posts daily sales by category to accounting; inventory movements are recorded; bank feeds match deposits to expected cash. Multi-location complications add to the integration surface — each store’s POS feeding the same set of accounting books with location tagging.

For each pattern, the right question to ask the accounting vendor is “show me a customer running exactly this stack.” Vendors that have multiple HK customers on a given pattern have proven the integration works at scale; vendors that have one or two are still de-risking.

---

Webhook patterns vs polling

Two integration patterns transfer data between systems. Polling means the consumer system asks the producer system “what’s new?” at a regular interval (every 5 minutes, every hour). Webhooks mean the producer system pushes a notification to the consumer when something changes.

The difference matters in three ways:

• Latency. A webhook delivers the change in seconds; polling at 1-hour intervals introduces up to 1 hour of staleness.
• API call efficiency. Polling generates many “nothing has changed” calls; webhooks only fire when there’s actually news.
• Reliability. Webhooks can be lost in transit (network issues, consumer downtime); polling will eventually catch up. Mature integrations use webhooks for the fast path and a daily poll as a backup catch-up.

For HK SME accounting integrations, the workloads where webhooks earn their keep are: incoming payment notifications (so the AR is closed in real time), inventory movements (so stock levels are accurate for sales), and customer-data updates (so address changes flow through to invoicing). For workloads that don’t need to be real-time — month-end reporting feeds, annual data extracts — polling is fine.

The vendor’s webhook offering is a useful capability test: vendors with mature webhook support tend to have mature APIs in general; vendors that offer “webhooks coming soon” or webhooks only on the most expensive tier are signalling that their integration foundations are weaker.

---

Security considerations — auth, rate limits, data residency

Three security questions matter for any accounting-software integration in HK:

Authentication and authorisation. OAuth 2.0 with scoped permissions is the standard — the integration requests “read invoices, read customers, write transactions” and the user grants exactly that scope rather than full access. API-key-only auth gives the integration full access by default, which is a larger blast radius if the key leaks. Long-lived API keys stored in a partner system are a real risk profile.

Rate limits and abuse prevention. A poorly-designed integration that hits the API in a tight loop can degrade the accounting system for all users. Mature vendors enforce rate limits both per-app and per-account; check that the vendor’s rate limits accommodate the actual workload you’ll run, not just the marketing number.

Data residency. Some HK SMEs and most HK regulated entities have data-residency requirements (data must be stored in HK or specified jurisdictions). Cloud accounting vendors store data in their own datacentres, which may be in Singapore, Sydney, US, EU. Verify the vendor’s data residency policy and whether HK-resident storage is available — particularly important for regulated entities and those with HK government contracts.

For most general SMEs, data residency is a less binding constraint, but it’s worth knowing where the data lives. Cross-border data transfer rules under the HK Personal Data (Privacy) Ordinance apply when personal data crosses borders — typically not a blocker but a disclosure obligation.

---

When integration partners beat DIY

For most HK SMEs, the right approach to integration is to use either the vendor’s native pre-built integrations (when they exist for the specific tools you use) or an integration partner platform like Zapier, Make, n8n, or HK-specific consultancies that pre-build and maintain integrations for the local stack. DIY integration code is rarely the right answer for an SME — the upfront cost is moderate but the maintenance cost over years (vendor API changes, edge-case bug fixes, reliability monitoring) substantially exceeds what a managed integration partner charges.

The exception: SMEs whose competitive advantage involves a unique data flow that no off-the-shelf integration handles. A logistics company with proprietary route-optimisation that needs to push trip-level cost data into the accounting GL has no off-the-shelf option and a custom integration is justified. For the typical “Shopify → accounting” or “Stripe → accounting” integration, the off-the-shelf options are good enough and cost less than maintaining custom code.

Two things to verify on any third-party integration:

• Who owns the integration when something breaks? If the vendor changes the API and the integration breaks at month-end, who fixes it on what timeline?
• What does the integration cost over 3 years, including any per-transaction or per-record fees? Some integration platforms charge per API call, which compounds with volume.

---

What to test before buying

For an SME selecting accounting software with integration in mind, the demo should include:

• “Show me a customer with my stack.” Vendor should be able to point to at least one HK customer running the same set of tools you plan to integrate.
• API documentation walk-through. The documentation should be readable and complete — if the vendor can’t show it, the integration story is weaker than the marketing implies.
• Webhook reliability claim. Ask for the SLA on webhook delivery and what happens when delivery fails. Vague answers are warning signs.
• Rate-limit reality check. “What’s your rate limit on the invoice creation endpoint?” If the answer is below 30/minute the integration scope is constrained.
• Pre-built integration list. Pull the list of pre-built integrations and check that the tools in your stack actually appear. Generic statements like “we integrate with everything via our API” without specific names are not the same as having ready integrations.
• Sandbox availability. A sandbox environment for testing before going live should be standard. If only production is available, integration debugging risks corrupting real data.

---

How Giga Accounting by 凌峰會計 can help

Giga Accounting by 凌峰會計 exposes a RESTful API with OAuth 2.0 authentication, sandbox environment, full webhook support for invoice / payment / inventory events, HKD-native handling, bilingual TC/EN data round-tripping, and a published integration catalogue covering the common HK SME stack (Shopify, Shopline, HKTVmall, Stripe, AsiaPay, common HK POS systems). For HK customers with bespoke integration needs, our team works alongside our integration partners on scoping and ongoing support.

Get in touch for a 30-minute scoping call against your specific stack — bring the names of the systems you currently run and we can map what’s pre-built vs what would need a partner integration — or see our flat per-company pricing. For the e-commerce vertical-deep view (often the highest-value integration question), see our e-commerce accounting software guide; for the bank-feed integration that’s the largest single integration in any SME stack, see bank feed and auto-reconciliation in HK; and for the broader pricing context where API access often gates a tier, see accounting software pricing in HK.

“Multi-user accounting software” was once a simple feature — could two people log in at the same time without crashing each other’s session? In 2026 the question is more useful than that. Multi-user really means: who can see what, who can change what, who approves what, how do you audit who did what, and how does the software keep an accountant working from another office (or another country) productive without giving them keys to the kingdom. The headline “supports multi-user” tells you almost nothing about whether the product actually solves these problems.

This guide covers what HK accounting software’s multi-user features actually need to handle for a typical SME — what concurrent multi-user means in 2026, role-based access control as the central mechanic, the remote-accountant access pattern that’s almost universal in HK, the audit trail that makes “who did what” answerable, security and authentication considerations, and the demo questions that surface real capability. The framing is the SME with 2–10 people touching the books, not the listed-company finance department with 50 seats.

---

What “multi-user” actually means in 2026

Three structurally different things hide under the “multi-user” label in vendor marketing.

Concurrent logins. Multiple users can be authenticated and active in the software at the same time. The minimum viable multi-user. By 2026 every cloud accounting product handles this well; some on-premise legacy products still struggle, particularly with concurrent edits to the same record.

Per-user identity and audit trail. The software knows which user did each transaction. Postings, edits and deletes are stamped with the user’s identity and timestamp. This is what lets the auditor — or you, when investigating an error — answer “who entered this and when?” Identity is the prerequisite for any meaningful permission control.

For an SME owner-operator, the per-user-identity check is the single most important multi-user feature. A common pattern is that everyone shares a generic “admin” login because it’s simpler — and then when something goes wrong, no one can tell who did what. The fix is uncomfortable but cheap: every regular user gets their own login.

Role-based access control. Different users see different parts of the software, and can do different things, based on the role assigned to them. The bookkeeper can post invoices but not edit master data; the director can see all reports but not enter day-to-day transactions; the external accountant has read-only on the master data with full access for journal entries during month-end. This is where the productivity gain actually lives.

---

Role-based access control

The standard role set that most HK SMEs end up with after some experience:

• Director / Owner — full read access to all reports, ability to approve high-value transactions, ability to manage user permissions. Often does not enter day-to-day transactions; the value of the role is oversight, not operations.
• Bookkeeper — full posting access (invoices, payments, expenses, journals), read access to most reports, no ability to change user permissions or modify GL chart of accounts. The day-to-day operator.
• Sales / AR clerk — invoice creation and AR-side workflows, read access to customer records, no access to bank or supplier-side data. Useful when sales and finance are separate teams.
• Approver / Manager — read-only on most data, with the ability to approve or reject pending transactions above a threshold. Useful for SMEs that have implemented purchase-approval workflows.
• External accountant / auditor — read-only on most data, plus the ability to post journals to a defined set of accounts (typically year-end accruals, depreciation, deferred tax). The pattern that lets your accountant work without you handing over the master password.
• System admin — manages user accounts and permissions but doesn’t see transaction-level data. For larger SMEs that separate IT administration from finance.

The accounting software requirement is that these roles can be configured (not just chosen from a fixed list), that permissions can be set at a useful level of granularity (per-module is fine; per-transaction is overkill), and that changing a user’s role is straightforward. SMEs whose software offers only “all access” or “read-only” are forced to over-share or under-share.

---

Remote accountant access — the standard HK pattern

The single most common multi-user pattern in HK SMEs is the “external accountant” arrangement. The SME has its own books in its accounting software; the external CPA firm or bookkeeper accesses the software to do month-end work, year-end audit prep, and tax-return preparation, without anyone shipping data files back and forth.

The three approaches in 2026:

• Cloud accounting native multi-user. The cleanest option. SME pays for the seats; accountant logs in with their own credentials; the access is logged and revocable. Default for Xero, QBO, Giga and most modern cloud products.
• On-premise with VPN access. Legacy desktop products where the accountant connects to the SME’s network via VPN and runs the software remotely. Workable but creates security and version-management headaches.
• Email-attached data files. The “send me your QuickBooks file” approach. Common for older sole-practitioner accountants. Manageable for small workloads but breaks down at any scale, and loses the audit-trail benefit because changes happen in different file copies.

For an SME choosing accounting software in 2026, native cloud multi-user with role-based access is the default to look for. The marginal cost of an additional accountant seat (typically HK$50–200/month) is trivial compared to the operational benefits.

The HK-specific consideration: the external accountant may be working from a different jurisdiction (mainland China, Singapore, UK, etc.) for an HK-incorporated SME. Geographic restrictions on the software’s access — some products geo-block by IP — can be a real problem. Verify in the demo.

---

Audit trail — what “who did what” actually requires

Multi-user without audit trail is worse than single-user with no audit trail, because the dispersion of who-did-what creates the illusion of accountability without the substance.

The audit-trail features to verify:

• Every transaction has a created-by + created-at stamp that cannot be edited.
• Edits are versioned — the original transaction is preserved, the edit is shown as a new version with edited-by + edited-at, and a third party can reconstruct the original.
• Deletes are soft, not hard — a deleted transaction is marked deleted but retained, with a deleted-by + deleted-at stamp, so the record exists for audit even when the live ledger doesn’t show it.
• User access logs — who logged in, from where, when, and what they viewed. Often a separate log from transactional audit trail.
• Reports cannot be silently edited — a report run today and again tomorrow on the same period should produce identical numbers unless the underlying data has changed (in which case the change is documented).

For Section 51C records-retention purposes (see our profits tax guide for the underlying obligation), the audit trail itself is part of the records that must be preserved for 7 years. Software that allows transactions to be edited without retaining the original edit history is technically at risk on this point.

---

Security and authentication

Multi-user expands the attack surface compared to single-user; the security model has to compensate.

The security features to verify:

• Mandatory or optional two-factor authentication (2FA). By 2026 mandatory 2FA on at least the admin role is the expected standard. Software that doesn’t offer 2FA is genuinely behind.
• Password policy. Minimum length, complexity, expiry, can-be-reset-by-self-or-admin. SMEs often want central admin control over password resets to avoid the support load of users locked out.
• Session timeout. Idle session times out and re-authentication is required. Typically configurable (15 min for high-security shared computers, longer for trusted personal devices).
• IP whitelist / geo-blocking. Some SMEs want access restricted to office IP ranges or HK / a specific list of jurisdictions. Useful for high-sensitivity engagements but can become a friction source if remote work is normal.
• Single sign-on (SSO). For SMEs already using Microsoft 365 or Google Workspace, SSO via SAML or OAuth removes a credential to manage and centralises access control. Increasingly common in 2026.
• Data residency. Where the data is physically stored. PDPO compliance for personal data; some HK regulated entities have stricter residency requirements. See our API and integrations guide for the broader data-residency framing.

---

Demo questions to surface real capability

A 30-minute demo with the following test set surfaces real multi-user capability:

• “Set up three users with three different roles.” Create a director (full access), bookkeeper (posting access), and external accountant (read-only with journal access). Watch how granular the permissions actually are.
• “Show me the audit trail on a transaction that’s been edited.” Vendor should produce both the current state and the edit history with user stamps. If only the current state is available, the audit trail is thin.
• “Walk me through the 2FA setup.” Mandatory or optional? How does the recovery flow work if a user loses their authenticator?
• “Show me a deleted transaction.” Vendor should be able to retrieve a soft-deleted record. If “delete” is permanent, audit trail is incomplete.
• “What’s the access pattern for an accountant working from Mainland China?” Geo-blocking, VPN requirement, performance over slower connections.
• “Show me the user-access log.” Last 30 days of logins, successful and failed, with IP and timestamp.

---

How Giga Accounting by 凌峰會計 can help

Giga Accounting by 凌峰會計 ships role-based access control with configurable role definitions, per-user identity with full audit trail (created/edited/deleted stamps with user + timestamp, version history on edits, soft-delete preservation), mandatory 2FA on admin roles, optional 2FA on standard roles, configurable session timeouts and IP whitelist, SSO integration via SAML, HK-resident data storage as standard, and the external-accountant role pre-configured for the typical CPA-firm engagement pattern. Multi-user is included in the standard licence — the calculation is that an accounting product that gates its security and access model behind a higher tier is letting the wrong constraint drive an SME’s compliance posture.

Get in touch for a 30-minute demo focused on multi-user setup against your team structure, or see our flat per-company pricing. For the related mobile-UX feature where multi-user identity matters across devices, see our mobile apps for HK accounting software guide; for the broader API + data-residency context that frames remote-access security, see accounting software API and integrations; and for the features-checklist hub where role-based access sits as a 7th-modern-feature must-have, see essential features of accounting software for HK SMEs.

Running a restaurant in Hong Kong is a margin-hunt from the moment you sign the lease. Rent is high, rents change, ingredient prices move weekly, staff rotate in and out, and every takeaway order on Deliveroo, Keeta, or foodpanda eats a different slice of the top line. An accounting system that cannot keep up with all of that is not saving you time — it is quietly hiding the margin you should be defending.

This guide covers what accounting software for Hong Kong restaurants actually needs to do, where generic accounting packages fall short for F&B, and how to shortlist a system that fits a real HK café, bar, or multi-outlet group.

---

Why restaurant accounting is different

Most accounting software is built with a trading or services business in mind: a handful of customers, a steady flow of invoices, inventory that sits still. A restaurant looks nothing like that. Revenue comes in hundreds of tiny transactions a day through multiple channels; costs hinge on ingredients that expire; staffing is weekly and partly casual; and margin lives in the 1–2 percentage points that come from watching food cost ratios every single week.

The implication for software is concrete: your accounting tool has to talk to your POS, understand recipes and ingredient costs, handle MPF for part-time staff, and reconcile multiple delivery platforms that each take a different cut and settle on different days.

---

Four things HK restaurants need that generic software misses

1. Daily POS sales import. A restaurant might ring up 200 transactions a day. Typing those into a sales ledger is a non-starter. Your accounting software needs to import a daily sales summary — gross sales, discounts, service charge, tax if any, and a settlement split by payment method (cash, EPS, Visa, Mastercard, AlipayHK, WeChat Pay HK, Octopus, FPS).
2. Delivery-platform reconciliation. Deliveroo, Keeta, and foodpanda each send a different settlement report on different schedules. Your system should let you book the gross order value as revenue, the commission as an expense, and the net payout as the bank receipt — all reconcilable back to the platform’s statement.
3. Ingredient-level cost and stock control. Generic accounting software can track “stock” at SKU level but rarely at recipe level. A decent F&B module lets you define a menu item as a set of ingredients, update ingredient costs, and get a current food cost % per dish.
4. Shift-worker payroll with MPF. Most HK restaurants run a mix of full-time, part-time, and casual staff. Payroll needs to handle daily rates, overtime, service charge distribution, and MPF contributions for anyone who qualifies.

---

POS integration: the HK reality

POS is where most restaurant accounting projects succeed or fail. The HK market is fragmented: you might be running BindoPOS, iCHEF, Eats365, Square, Shopify POS, or a legacy cash register that only exports a PDF. The integration path depends entirely on which POS you use.

• Direct API integration: Modern cloud POS products can push a daily sales summary straight into a cloud accounting system. Least effort, cleanest audit trail.
• CSV import: POS exports a daily CSV, accounting software imports it on a schedule. Works well, but needs a consistent file format and someone to run the import.
• Manual summary entry: A human enters a Z-report total each day. Cheap, but easy to miss or fudge — and reconciling against bank deposits becomes painful.

Before shortlisting any accounting tool, write down your current POS and ask each vendor: “Can you show me the daily sales import from my POS running end to end?” If the answer is vague, assume manual entry — and budget the labour.

---

Food cost management: the metric that pays for the software

Food cost percentage (cost of ingredients ÷ food revenue) is the single most important operating metric in a restaurant. HK casual-dining targets typically sit around 28–35%; anything creeping into the 40s quietly kills profit.

An accounting system that tracks food cost properly gives you three things a manual spreadsheet cannot:

• Recipe-based costing. Define every menu item once with ingredient quantities; software auto-updates dish cost when ingredient prices change.
• Daily or weekly food cost reporting. Instead of finding out at month-end that food cost jumped to 38%, you find out on Tuesday of week two — in time to act.
• Variance between theoretical and actual. Theoretical food cost (from recipes × sales mix) compared to actual food cost (from purchases and stock movements) flags waste, theft, or portion drift before they show up as lost profit.

---

Shift-worker payroll and MPF for HK restaurants

Restaurant payroll in HK rarely fits a tidy “25th of the month, 22 working days” template. Typical issues the software has to handle:

• Hourly or daily rates that vary by role (kitchen, bar, front-of-house, weekend).
• Overtime calculations that reflect actual hours worked rather than a flat monthly salary.
• Service charge distribution. If you pool the 10% service charge, the software needs to allocate it by shifts or hours worked.
• MPF for part-timers. Anyone employed 60 days or more, even part-time, is an MPF member. Software that calculates contributions per pay cycle — not just a flat monthly assumption — saves audit headaches later.
• Autopay file export. HK bank autopay format (.txt) for monthly wages is still the fastest settlement method; the system should produce it.

See our broader guide on payroll and MPF features in HK accounting software for how to test each vendor’s payroll module properly.

---

How to shortlist a system for a HK F&B business

A straight-line shortlist in five steps:

1. List your channels. Dine-in (via which POS), delivery (Deliveroo / Keeta / foodpanda / your own), takeaway, catering. Each one is a data source.
2. List your cost categories. Food, beverage, staff, rent, utilities, platform commissions. Build the chart of accounts around them.
3. Ask for a demo using your real POS. Not a canned demo data file. Bring a week of your actual sales export and watch it import.
4. Check multi-outlet support if relevant. If you plan to open a second site in the next year, make sure the software handles multi-location from day one — consolidation, inter-company transfers, per-outlet P&L.
5. Review the total 3-year cost. Per-user fees stack up fast when outlets have multiple managers. Flat-fee unlimited-user products usually win on TCO once you are past one site.

---

Worth knowing: storage and data retention

A restaurant can generate tens of thousands of POS line items per month. Any accounting system that caps storage or forces you to purge old data will hit its ceiling fast — and the IRD still expects you to keep records for seven years. Giga Accounting by 凌峰會計 includes 10 GB per company with no need to purge, which is the difference between a system that grows with your restaurant group and one you have to replace in year three.

---

Let us set up your F&B stack

Giga Accounting by 凌峰會計 is built for HK SMEs across retail, trading, and F&B. We can sit with you through the POS mapping, delivery-platform reconciliation, recipe cost setup, and shift-worker payroll — all in one system, priced flat per company with unlimited users and 10 GB of storage that never gets purged.

If you are comparing across verticals, read our sister pieces on accounting software for HK retail businesses and managing accounts for multiple HK companies. Or go straight to the Giga Accounting by 凌峰會計 homepage to see the full product and cloud accounting overview.

For a first-time Hong Kong director, “how long does an audit take” and “how much does it cost” are usually the first two questions. And they’re harder to answer than they look, because both depend heavily on factors under your own control — not just on the auditor’s schedule or price list.

This guide gives a realistic view of Hong Kong company audit timelines and costs: typical durations for different business sizes, what really drives the fee, and the specific things that push both time and cost up. The aim is to let you plan — and, where possible, keep both numbers down.

---

What Determines How Long an Audit Takes

Audit duration is not mainly about size; it’s about record quality and complexity. Five factors do most of the work:

• Quality of monthly bookkeeping. Clean trial balance vs reconstruction — the single biggest variable.
• Completeness of supporting documents. Invoices, contracts, bank statements, payroll records all available vs scattered across email, drawers, and hard drives.
• Complexity of the business. Multi-currency, multi-entity, inventory-heavy, and related-party transactions each add time.
• Responsiveness to auditor queries. A 24-hour response keeps momentum; a week’s delay at each query can double the calendar time.
• Whether it’s a first-year audit. First audits always take longer because the auditor has to validate opening balances and understand the business.

Two companies of identical revenue can end up with timelines that differ by weeks based on these factors alone.

---

Typical Audit Timelines for Different Business Sizes

As a broad guide for HK SMEs with reasonable records:

• Dormant or shell company — 1 to 2 weeks of elapsed time from handover to signed report.
• Small operating SME, well-kept books — typically 3 to 5 weeks.
• Mid-size SME with modest complexity — 5 to 8 weeks.
• Trading / inventory-heavy / multi-currency business — 6 to 10 weeks.
• Company with unclean prior-year audit or reconstruction required — 10 to 16+ weeks.

These are elapsed times, not fieldwork hours. The fieldwork itself is typically shorter — much of the duration is queries, responses, and sign-off iteration.

---

What Makes an Audit Take Longer (and Cost More)

The specific things that extend timelines — and therefore add to the fee — include:

• Incomplete bank reconciliations. Auditors can’t progress without reconciled cash.
• Missing invoices or contracts. Every missing document triggers a chase.
• Inventory not physically counted. Forces alternative procedures, which are slower and more expensive.
• Related-party transactions not disclosed upfront. Surfacing mid-fieldwork requires restatement.
• Multiple email chains with different team members. Every handover is friction.
• Year-end close dragging on. If accruals, prepayments, and depreciation are still in motion, the audit stops.
• Weak documentation of revenue. Especially problematic for service businesses without clean billing records.

Audit firms bill for hours. More hours required = higher fee. There’s no mystery to the relationship.

---

The Link Between Your Bookkeeping Quality and Your Audit Fee

For a given HK SME, the audit fee can vary by 50% to 100% between “clean records” and “reconstruction required.” The reason is simple: the auditor isn’t going to accept records they can’t verify, so if the trial balance doesn’t hang together, the auditor has to build one. That’s audit work, billed at audit rates.

The practical implication: the cheapest way to lower your audit fee is not to negotiate with your auditor. It’s to raise your monthly bookkeeping standard so the auditor has less to build. A few hundred dollars a month on competent bookkeeping regularly saves several thousand at year-end — and that’s before counting the risk reduction.

---

What’s Included in a Typical Audit Fee in Hong Kong

A standard audit engagement usually covers:

• Planning and risk assessment.
• Fieldwork and testing — sampling transactions, confirmations with banks and major debtors/creditors, year-end cut-off procedures.
• Review of the draft financial statements against HKFRS.
• Audit report issuance (the signed opinion).
• Management letter, where material observations are documented.

Usually not included, and billed separately:

• Bookkeeping or trial balance preparation.
• Preparation and filing of the Profits Tax Return (often done by a separate tax services team).
• Ad-hoc advisory work during the year.

Check each quote for exactly what’s in and out — the differences between firms at the same headline price are often substantial.

---

How to Reduce Your Audit Costs Without Cutting Corners

Practical levers that work for most HK SMEs:

1. Reconcile every bank account every month. Year-end should be a quick confirmation, not a rebuild.
2. Keep digital copies of every supporting document, filed against the relevant transaction.
3. Finalise your year-end close before handover. Accruals, prepayments, depreciation, tax provisions all posted.
4. Run a proper physical stock count at year-end if you carry inventory.
5. Disclose related-party transactions upfront. Don’t let them surface mid-fieldwork.
6. Designate one point of contact for the audit so queries don’t scatter across the team.
7. Use accounting software your auditor can receive data from directly. Exports they don’t have to reshape save real time.

Each of these shaves time from the audit. Together they can cut the fee meaningfully — and make the whole process noticeably less stressful for your team.

---

Plan Your Next Audit With a Clean Lead-up

If you’d rather arrive at year-end with books already in audit-ready shape, Giga Accounting by 凌峰會計 produces monthly reports auditors can use with no reformatting. Many of our clients cut their audit fee substantially in the first year simply by starting the year with cleaner books.

Want to talk through your specific audit or quote? We offer certified auditing services and year-round bookkeeping support, and can give you a realistic fee range for your business. Get in touch or review our transparent pricing. If you want the month-by-month audit calendar, see our companion guide on the Hong Kong audit timeline.

For most Hong Kong SMEs, the annual audit is the single most concentrated piece of compliance work in the year. And yet the real timeline — what needs to be ready, by when — is rarely explained clearly. Directors often discover the deadlines only when they’re already in trouble.

This guide lays out the realistic Hong Kong audit timeline: what happens when, what your auditor needs at each stage, and where the bottlenecks usually appear. The goal is simple — so you can plan the year rather than react to it.

---

The Audit Calendar — What Happens and When

Every HK company has its own financial year, but the sequence of events is the same:

• Year-end cut-off. Typically 31 December or 31 March, though any date is allowed. This is the snapshot date for the financial statements.
• Bookkeeping close. The first 4–6 weeks after year-end: bank reconciliations, accruals, stock count adjustments, AR/AP cut-off, and the draft trial balance.
• Audit fieldwork. The auditor’s detailed testing and evidence gathering.
• Audit finalisation. Draft report reviewed, amendments posted, management letter discussed, final report signed.
• Profits tax return (PTR) filing. Filed with the Inland Revenue Department along with a copy of the audited accounts.
• Companies Registry filing. Annual Return filed separately at the Companies Registry (this is not the same deadline as the tax filing).

Missing any of these steps — or running them out of sequence — is what produces last-minute scrambles and late-filing penalties.

---

How Your Financial Year End Determines Your Deadlines

The IRD’s profits tax filing deadlines depend on your year-end date and whether your tax representative participates in the Block Extension Scheme:

• Year-end 1 April to 30 November (“N” code): normal filing deadline is 2 May of the following year; extended to around 15 August under block extension.
• Year-end 1 December to 31 December (“D” code): normal deadline is 2 May; extended to around 15 November under block extension — but the extension is conditional, and loss-making companies benefit from an earlier extension.
• Year-end 1 January to 31 March (“M” code): normal deadline is 2 May; extended to around 15 November under block extension.

Specific dates shift slightly year to year. Confirm the current year’s dates with your tax representative — but the structure above doesn’t change. The point is that a 31 December year-end company ultimately has the longest practical runway to a filed PTR, while a company with a mid-year end has the tightest.

---

What Your Auditor Needs — and When

Audit fieldwork runs smoothly or badly largely based on how complete the handover package is. A normal request list includes:

• Trial balance and general ledger for the financial year, reconciled and finalised.
• Bank statements and bank reconciliations for every account, for every month of the year.
• AR and AP listings at year-end, aged, with supporting invoices available.
• Fixed asset register with additions, disposals, and depreciation.
• Stock listing at year-end with valuations.
• Revenue documentation — customer invoices, sales contracts, major agreements.
• Expense documentation — supplier bills, payroll summaries, MPF records, lease agreements.
• Bank confirmations — requested via the auditor, returned directly to the auditor from the bank.
• Minutes, shareholder registers, and corporate documents.
• Related-party details — full listing of transactions and balances.

Most of this should exist already, in clean form, if monthly bookkeeping has been done properly. If it doesn’t, that reconstruction work is usually what makes the audit late and expensive.

---

Common Bottlenecks That Delay Audits

Audits rarely run late because the auditor is slow. They run late because one of these chokepoints:

• Year-end bookkeeping isn’t finalised. The auditor receives a trial balance that’s still moving.
• Bank reconciliations are incomplete. Several months of unexplained items.
• Supporting documents are missing. Invoices that can’t be located, or receipts for major expenses that never made it into the filing.
• Inventory was never counted at year-end. Auditors either qualify the opinion or rely on procedures that take far longer.
• Related-party transactions surface late. Discovering a previously unrecorded director loan mid-fieldwork causes restatement work.
• Directors’ sign-off is slow. Everything is ready except the last signature.

Every one of these is a bookkeeping or records issue, not an audit issue. Which is why the real leverage on audit timing sits with how well the books are kept during the year.

---

How Bookkeeping Throughout the Year Determines Your Audit Bill

Audit pricing in Hong Kong isn’t really about the scope of the business — it’s about the state of the records. Two companies of identical size can produce audit quotes that differ by 50–100% based on how clean their bookkeeping is.

The reason is simple: the auditor isn’t going to accept records they can’t verify. When records are clean, the work is sampling and confirmation. When records are messy, the work is reconstruction — building the trial balance the bookkeeper should have built. That’s billed at audit rates, which are substantially higher than bookkeeping rates.

A modest investment in monthly bookkeeping typically pays back several times over in audit fees alone.

---

Your Audit Preparation Checklist

A practical month-by-month view for a company with a 31 December year-end:

1. December: physical stock count, bank balances confirmed, AR/AP cut-off sharp.
2. January: finalise bank reconciliations, accruals, prepayments, depreciation, tax provisions. Trial balance locked.
3. February–March: auditor fieldwork. Respond to queries within 2–3 days to keep momentum.
4. April–May: final review, management letter, signed accounts.
5. Profits tax return: filed by the applicable deadline for your year-end code.
6. Annual Return: filed at Companies Registry within 42 days of the incorporation anniversary (separate from tax filing).

---

Want Your Next Audit to Be Easier?

The fastest way to shorten the audit is to arrive at year-end with books already in shape. Giga Accounting by 凌峰會計 produces month-end reports in exactly the format auditors want, and its monthly close tools make reconciliation routine rather than a year-end scramble.

Need hands-on help? We also offer certified auditing services and bookkeeping support for companies that want a cleaner lead-up to audit season. Get in touch if you want to discuss your specific timeline, or review our transparent pricing.

Retail is one of Hong Kong’s most visible SME sectors — from Causeway Bay fashion boutiques to Mong Kok electronics stores, Sham Shui Po gadget shops, and multi-branch F&B operators across the city. All of them share one thing: the accounting needs are nothing like a services business.

Retail runs on high-volume daily transactions, physical inventory that moves constantly, and cash flow patterns that swing with seasons and promotions. Generic accounting software wasn’t built for this. This guide covers what makes retail accounting different in Hong Kong, and what to look for in software that can keep pace.

---

The Unique Accounting Needs of Retail Businesses

A retail business has a specific accounting shape:

• Hundreds to thousands of small transactions per day, each with cost of goods sold attached.
• Physical inventory that constantly changes — incoming stock, sold stock, returned stock, damaged stock, promotional giveaways.
• Mixed payment methods — cash, Octopus, credit card, Alipay, WeChat Pay, FPS, Apple Pay, store credit — each settling on different timelines.
• Multiple sales channels — physical store, online store, delivery platforms — which must roll up into one set of books.
• Promotional complexity — discounts, bundles, BOGO, loyalty points, gift cards — each with its own accounting treatment.

If any of these are currently handled in spreadsheets outside your accounting system, the risk of year-end misstatement is high.

---

Inventory Valuation Methods (FIFO, Weighted Average)

For retailers, how you value inventory isn’t a technicality — it directly determines reported profit. The two methods most commonly used in Hong Kong are:

• First-In-First-Out (FIFO). Assumes the oldest stock sells first. Typically gives higher reported profits in rising-cost environments, which can be a double-edged sword — more tax payable in good years.
• Weighted Average Cost. Blends costs across batches. Smooths out margin volatility, simpler to compute at scale, and commonly used in fashion, electronics, and F&B retail.

The method isn’t something you flip back and forth on. Once chosen, it should be applied consistently, with the rationale documented — your auditor will ask. Good retail accounting software lets you choose at the outset and automates the calculation from then on.

---

Managing Cash Sales and Point-of-Sale Reconciliation

Cash handling is where retail accounting often breaks down. Every day produces a takings figure — cash in the till, card settlements, digital wallet reports, Octopus reports — and that total has to agree with sales recorded in the accounts. When it doesn’t, the difference is either a bookkeeping error, a missed refund, or a cash shrinkage issue. You want to know which, quickly.

Proper retail accounting software supports:

• Daily Z-report integration from the POS into the accounts, not manual re-keying.
• Separate tracking of cash, card, and digital wallet settlements, each reconciled against its own clearing account.
• Documented over/short reporting by till and by shift, so variances are investigated before they compound.

Without this, the gap between the POS total and the accounting total grows steadily, and the annual audit becomes a reconstruction exercise.

---

Handling Returns, Discounts, and Promotional Pricing

Promotions are not decorations on the P&L — they have real accounting consequences:

• Returns need to reduce both revenue and COGS, and restore inventory if the item is resalable.
• Discounts should be recorded against revenue, not buried in COGS, so gross margin stays meaningful.
• Bundles and BOGO require revenue to be allocated across items proportionally, not stuffed into one line.
• Loyalty points and gift cards are liabilities until redeemed — not revenue when issued.

Retailers who treat all of the above as “just discount off the top” end up with revenue figures that don’t match what the business actually earned — and margin analysis that gives the wrong signal.

---

Seasonal Stock and Cash Flow Planning

Retail cash flow is rarely flat. Chinese New Year, Mid-Autumn, Christmas, back-to-school, rainy summer weekends — all of these create sharp peaks and troughs. Good retail accounting software gives you what a spreadsheet can’t:

• Rolling cash flow forecasts based on historical seasonal patterns.
• Inventory days-on-hand by category so you can see where cash is tied up.
• Supplier lead time awareness — if your supplier needs six weeks and you carry eight, you know when to reorder.
• Markdown tracking so the impact of end-of-season discounts on gross margin is visible in the same period it happens.

---

What to Look for in Retail Accounting Software

When evaluating options for a Hong Kong retail business, check specifically for:

• Integrated inventory and accounts on a single platform — not two systems you reconcile manually.
• POS integration, ideally with daily automated sync rather than manual import.
• Traditional Chinese interface for frontline staff who may not be comfortable with English-only tools.
• Multi-branch reporting if you have more than one location.
• Multi-currency if you source overseas.
• Clear handling of digital wallet settlements — Octopus, Alipay, WeChat Pay, FPS — each has its own timing and fee structure.
• HKFRS-formatted reports your auditor will accept without manual reformatting.

---

Ready to Upgrade Your Retail Accounts?

If your current setup is a POS system on one side, an accounting tool on the other, and a weekly Excel to join them — the year-end audit will cost more than it should, and your day-to-day visibility into margin and inventory is probably weaker than it could be. Giga Accounting by 凌峰會計 was built with retail complexity in mind: integrated inventory, flexible valuation methods, and HKFRS-ready reports out of the box. The 10GB-per-company storage allowance accommodates the higher document volume retail businesses generate — POS daily-Z reports, supplier invoices, stock-take sheets, consignment dockets — without forcing year-end purge of supporting documents.

Both the Windows desktop edition and the cloud edition are available for trial. Get in touch for a walkthrough against your specific retail workflow, or review our transparent pricing. If cash flow is your immediate concern, our earlier guide to the best accounting software for HK SMEs in 2026 has additional context.