1. What TechUp / TechConnect actually funds
TechUp / TechConnect-style project funding sits in the same family as Hong Kong's other technology co-funding schemes: it is project-based, not a lump-sum grant. The government (or the intermediary body administering the scheme) agrees to reimburse a defined share of the approved cost of a specific technology project β not your general business expenses, and not costs incurred before the project's approved start date.
In practice this means the award letter comes with a project scope, an approved budget broken down by category, and a timeline broken into milestones. Everything you spend has to map back to one of those approved budget lines, inside the approved project period, or it simply won't be reimbursed.
Treat the approved budget as a contract, not a suggestion. Every category (manpower, equipment/software, outsourced services, consumables, overhead) has its own ceiling. Money you don't spend in one category cannot silently top up another without prior written approval from the funding body β that's the single most common reason claims get partially rejected.
2. Who is eligible
Eligibility criteria vary by the specific circular in force, but the pattern across Hong Kong's tech project-funding schemes is consistent enough to plan around:
-
A locally registered entityThe applicant is typically a Hong Kong-incorporated company (or a locally registered organisation) with an active Business Registration Certificate β not an individual and not an offshore entity applying directly.
-
Real operating historyMost schemes in this family expect some minimum trading history and evidence of genuine local operations (director activity, staff, an operating address) β the substance test that also applies to bank account opening and other HK grants.
-
A qualifying technology projectThe proposed project must fall inside the scheme's defined technology categories and have a clear, deliverable-based scope β not an open-ended R&D wish list.
-
No double fundingThe same cost item cannot be claimed under more than one government funding scheme at the same time β declare any other grants you hold when you apply.
Exact eligibility thresholds, funding caps and matching ratios are set out in the scheme's official guidance notes and change between funding rounds. Treat everything above as general orientation, not a substitute for reading the current official scheme document before you apply.
3. Milestone and budget structure
Funding is released against milestones, not against a calendar. A typical structure looks like this:
| Stage | What's due | What gets released |
|---|---|---|
| Kick-off | Signed funding agreement, project team confirmed, bank account nominated | Sometimes a small upfront tranche; otherwise reimbursement starts after Milestone 1 |
| Milestone 1 | Defined deliverable (e.g. requirements spec, prototype) + progress report + expenditure evidence | Reimbursement of approved spend to date, capped at the milestone's budget line |
| Milestone 2β¦N | Next deliverable + progress report + expenditure evidence | Reimbursement of approved spend for that period |
| Final milestone | Completed deliverable, final report, full expenditure schedule, often an auditor's or accountant's certification | Final tranche, subject to reconciliation against the whole approved budget |
The budget itself is usually split into categories such as manpower (with time-sheet evidence for staff working part-time on the project), equipment and software, outsourced/subcontracted services, consumables, and a capped overhead allowance. Each category has its own ceiling β this is why project bookkeeping has to be category-aware from day one, not reconstructed at the end from a single expense ledger.
4. The evidence regime: invoices, receipts, and the audit trail
This is where most funded projects lose money β not because the work wasn't done, but because the evidence doesn't hold up. The evidence regime funding bodies expect is consistent across HK tech schemes:
- An invoice or contract for every claimed cost β issued to the applicant company, dated inside the project period, itemised enough to map to a specific approved budget line.
- Proof of payment β bank transfer records or receipts showing the invoice was actually paid, not just issued. A claimed cost with an invoice but no matching payment is a red flag in review.
- Time records for manpower costs β timesheets or equivalent showing the hours a staff member spent on the funded project specifically, separate from their other duties.
- Procurement documentation for larger purchases β quotations from multiple vendors where the scheme requires competitive procurement above a threshold, plus the rationale for vendor selection.
- Deliverable evidence β the actual output tied to each milestone (a document, a working build, a signed acceptance note) that proves the milestone was substantively met, not just that money was spent.
File the evidence against the milestone, as you go β not in one scramble before the reporting deadline. A project that tags every invoice to its budget category and milestone in real time turns a two-week reporting crunch into a same-day export.
5. Reporting cadence and what triggers a clawback
Expect at minimum: a progress report at each milestone, a final report at project completion, and β for larger awards β an independent auditor's or accountant's report reconciling claimed expenditure to the approved budget. Funding bodies typically reserve the right to conduct site visits or spot-check original documents during the project and for a retention period after completion.
The most common triggers for a clawback (partial or full recovery of disbursed funds) are not fraud β they're process failures: spend that exceeds a category ceiling without prior approval, missing or unmatched payment evidence, a deliverable that doesn't match what was promised at that milestone, or a report submitted late without prior extension approval. All of these are avoidable with disciplined project bookkeeping.
6. A worked example: LinguaLeap
To make this concrete, here's an illustrative walk-through using LinguaLeap, one of the ventures in the CompanyForge founder network, as a worked pattern. (Figures below are illustrative examples only, not LinguaLeap's actual project numbers.)
LinguaLeap runs a language-learning product build as a funded project with three milestones over nine months. At kick-off, the finance lead sets up one project in Bookkeep with three budget categories β manpower, software/API costs, and outsourced localisation β each capped at its approved ceiling. Every invoice from that point is tagged to a category and a milestone the moment it's entered, not batched later. When Milestone 1 falls due, the progress report and the expenditure schedule are both generated straight from the tagged transactions, because the tagging happened continuously rather than retroactively.
7. How Bookkeep's Projects tab runs a TechUp project end to end
This is exactly the workflow Bookkeep's Projects tab is built for β turning the evidence regime above from a manual scramble into a running ledger:
-
One project, one budget envelopeCreate a project matching your approved award, with the exact budget categories and ceilings from your funding agreement β Bookkeep flags any entry that would push a category over its cap before you file it.
-
Invoice + receipt capture per line itemAttach the invoice, the proof of payment, and (for manpower) the timesheet directly to each transaction, tagged to its budget category and milestone as it's entered β not reconstructed later.
-
Milestones as a live checklistEach milestone tracks its required deliverable, its report due date, and its running spend against budget, so you can see months ahead whether you're on pace to hit a milestone or under-spending a category.
-
One-click reporting exportWhen a report is due, export the expenditure schedule for that milestone β category totals, invoice references, payment evidence β as a single reconciled package ready to hand to your accountant or auditor.
Winning the award is a one-time event. Running the project cleanly is a 9β18 month discipline. Most funded companies that lose money on a grant don't lose it at application stage β they lose it at reporting stage, when evidence can't be reconstructed fast enough or accurately enough. Bookkeep's Projects tab exists specifically to close that gap.