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.

πŸ’‘ The one mental model that matters

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:

⚠️ Always confirm against the current circular

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:

StageWhat's dueWhat gets released
Kick-offSigned funding agreement, project team confirmed, bank account nominatedSometimes a small upfront tranche; otherwise reimbursement starts after Milestone 1
Milestone 1Defined deliverable (e.g. requirements spec, prototype) + progress report + expenditure evidenceReimbursement of approved spend to date, capped at the milestone's budget line
Milestone 2…NNext deliverable + progress report + expenditure evidenceReimbursement of approved spend for that period
Final milestoneCompleted deliverable, final report, full expenditure schedule, often an auditor's or accountant's certificationFinal 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:

βœ… The rule that saves the most time

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:

πŸ’‘ Why this matters more than the application itself

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.

8. FAQ

Can I claim costs incurred before the project was approved?οΌ‹
Generally no. Funding schemes of this type reimburse costs incurred inside the approved project period, starting from the date stated in your funding agreement. Any pre-approval spend is normally at your own risk unless the scheme explicitly allows a defined lead-in window β€” check your award letter, not general guidance.
What happens if I underspend one budget category and overspend another?οΌ‹
You typically cannot informally move approved funds between budget categories. Most schemes require prior written approval for any material re-allocation between categories (for example, moving unspent manpower budget into equipment). Raise it with your project officer before you spend, not after β€” retroactive requests are far harder to get approved.
Do I need an auditor's report, or is an accountant's letter enough?οΌ‹
It depends on the funding quantum and the specific scheme's requirements β€” larger awards more often require an independent auditor's report reconciling total claimed expenditure to the approved budget, while smaller awards may accept a simpler certified expenditure statement. Confirm the exact requirement in your funding agreement rather than assuming either way.
What's the single most common reason a milestone claim gets partially rejected?οΌ‹
Evidence that doesn't fully match the claim β€” an invoice without matching proof of payment, a cost booked to the wrong budget category, or a deliverable that doesn't clearly correspond to what was promised at that milestone. None of these are usually disputes about whether the work happened; they're gaps in the paper trail, which is exactly what disciplined project bookkeeping is designed to prevent.
Can Bookkeep help if I'm already mid-project and my records are messy?οΌ‹
Yes β€” you can create a project retroactively, import existing invoices and payment records, and tag them to the correct budget category and milestone. It won't recreate missing evidence, but it will show you exactly where the gaps are before your next report is due, which is the most useful thing to know early rather than at the final reconciliation.