PSG Grant Rejection: 7 Reasons Why (& Fixes)

The PSG rejection email is almost always disappointing. A short paragraph, generic language, no specific reason. "Your application does not meet the eligibility criteria" or "the proposed solution does not align with the grant's intended scope." Nothing actionable.

There are usually 7 underlying reasons sitting behind that generic email. None of them are published. All of them are avoidable if you know what to check before you submit.

I see these from an angle most advisors don't: we're a PSG vendor ourselves, so I get the feedback loop directly from clients — what got approved, what bounced, and the reason the officer actually gave. Across 200+ PSG engagements we've advised on, the same handful of rejection causes come up again and again. Here they are.

This is the operator-level diagnostic.

---

TL;DR — the 7 reasons

1. You paid the vendor first. Any payment or deposit before submission disqualifies the whole application.
2. The vendor is not on the current pre-approved list. The list changes — yesterday's approved vendor may have been removed.
3. The solution category does not match your business need. PSG funds specific solution categories per sector.
4. You exceeded the S$30k cap with an oversized scope. PSG won't part-fund — over the cap means rescope or split.
5. You already claimed PSG on the same solution category recently. Cooling-off rules apply.
6. Your eligibility doesn't actually meet the SME thresholds. Local equity, sales, or headcount checks fail silently.
7. The vendor invoice or quote is structured wrong. Even right vendor + right solution can fail on documentation.

The detail follows.

---

Reason 1 — You paid the vendor before applying

This is the most common reason and the most painful one because it's completely avoidable.

PSG's rule is unambiguous: any payment, deposit, contract signing, or commitment to the vendor before the application is submitted disqualifies the entire application. This includes:

• Cash deposits
• Credit card pre-authorisations
• Signed purchase orders with payment terms
• "Reserved seat" payments for software subscriptions
• Pre-paid annual subscriptions you started before applying

The pattern I see: vendor pushes the owner to "secure the spot" or "lock in the pricing" before the application is filed. Owner pays a S$3k deposit thinking it's small. The entire S$30k application is then unfundable.

The fix: Submit first, sign and pay second. Any vendor that pressures you to pay before application submission is either inexperienced with PSG or actively misrepresenting the rules. Walk away.

---

Reason 2 — The vendor is no longer on the current pre-approved list

The PSG pre-approved vendor list is not static. Vendors get added, removed, paused, or moved between categories as IMDA's policy evolves. A vendor that was on the list six months ago may not be on it today.

The common mistakes:

• Owner reads a 2024 blog post recommending a vendor
• Owner copies a vendor reference from another company's case study
• Owner relies on a sales pitch that says "we're PSG-approved" without verifying the current status

The fix: Verify the vendor against the current GoBusiness PSG catalogue at the point of application. The PSG vendor directory on this site tracks the catalogue — but the canonical reference at submission time is GoBusiness itself.

Also, particularly with IMDA's Budget 2026 push to raise the AI-enabled proportion of the PSG catalogue from 30% to 50%, expect more turnover in 2026. Verify, don't assume.

---

Reason 3 — The solution category doesn't match your business need

PSG funds specific solution categories — accounting, CRM, HR, POS, inventory, marketing automation, cybersecurity, and so on — and the categories are mapped to relevant sectors. Not every solution is available to every business.

The mistakes:

• Owner picks a vendor solution that's "PSG approved" but in a category the owner's sector isn't eligible for
• Owner buys a solution that's eligible for a different role within the company (e.g. a clinic buys a retail-coded inventory solution)
• Owner combines two solutions in a single application — only one of which is PSG-eligible

The fix: Check the solution category against your sector before scoping. The PSG vendor directory shows category by category. If your sector isn't in the eligible list for that category, the application will be rejected on category-fit, not on vendor identity.

---

Reason 4 — The scope exceeds the S$30k cap

PSG's cap is S$30,000 per UEN per solution category, with the 50% subsidy applying up to S$60,000 of total project cost (which produces the S$30k cap).

The mistakes:

• Vendor pitches a S$80k–100k engagement and the owner expects PSG to part-fund it. PSG doesn't part-fund — over the cap means the application gets bounced or the funded portion is the cap-limited amount.
• Owner bundles multiple solutions into a single S$60k+ application, expecting it all to qualify.
• Owner includes non-PSG-eligible scope (custom development, integration work, training above standard) in the same quote.

The fix: Either scope to the cap, or split the project into a cap-sized PSG portion plus a separately-funded portion (often EDG for the custom layer). The clean approach is PSG for the catalogue-eligible scope, EDG for the IDP Stage 2/3 custom layer that wraps around it.

---

Reason 5 — You claimed PSG on the same solution category recently

PSG has cooling-off rules — broadly, you cannot keep claiming repeatedly within the same solution category at the same UEN. The exact mechanics vary by category and by IMDA's current policy, but the principle is consistent: PSG is for adoption, not for serial re-funding of the same category.

The mistakes:

• Same UEN that funded a CRM under PSG in 2024 tries to fund a different CRM under PSG in 2026
• A business that previously claimed PSG for accounting software tries to upgrade to a newer accounting platform

The fix: Check your PSG claim history before assuming a new application will land. If you've claimed in the same category recently, consider whether the new project is genuinely a new solution category (which is fine) or a refresh of the same category (which often is not).

---

Reason 6 — Your eligibility doesn't actually meet the SME thresholds

PSG eligibility looks simple on paper but the thresholds catch out more applications than owners realise.

The thresholds (standard SME):

• Registered and operating in Singapore
• At least 30% local equity (Singapore Citizen or PR shareholding)
• Group annual sales ≤ S$100 million OR ≤ 200 employees

The mistakes:

• Owner forgets that the 30% local equity test applies to all UENs in the group, not just the applying entity. A group with foreign-majority ownership somewhere up the structure can fail this test even if the applying entity looks compliant on its own.
• Owner is borderline on the 200-employee threshold and doesn't account for contractors or part-time staff
• Annual sales test is breached on a one-off year (large project, deferred revenue recognition) and the application is filed in that window

The fix: Run an honest eligibility check before scoping. The PSG eligibility checker on this site runs the standard rules. For edge cases — group structures, borderline thresholds, mixed local/foreign ownership — get a second look before submission.

---

Reason 7 — The vendor invoice or quote is structured wrong

Even when everything else is right — vendor is on the list, category matches, eligibility checks out — the application can fail on how the documentation is presented.

Common documentation failures:

• Lump-sum quotes that don't break down what is PSG-eligible vs what isn't
• Bundled invoices that include non-eligible items (delivery, installation, admin fees, customisation)
• Vague scope language in the quote that doesn't map to the PSG-listed solution
• Missing references to the specific PSG-listed solution code
• Pre-dated documents that look like the vendor was committed to before application

The fix: Ask the vendor for a quote structured specifically for the PSG application. A vendor experienced with PSG will know how to break it down. A vendor that resists or sends back a generic quote is probably new to PSG — which itself is a yellow flag worth investigating.

---

Three less obvious patterns I've seen

Beyond the 7 reasons above, a few situational patterns worth flagging:

Pattern A — Cross-claim with EDG that wasn't properly scoped

Owner has a parallel EDG application in scope. PSG officer sees overlap and rejects rather than untangle the scope separation. Fix: Scope EDG and PSG cleanly from the start. PSG funds the off-the-shelf tool; EDG funds the IDP Stage 2/3 custom layer. They never claim the same cost line.

Pattern B — Application submitted by the wrong role within the company

PSG applications submitted by junior admin staff sometimes lack the financial commitment language and signing authority that the officer expects. Fix: Application should be filed (or at minimum reviewed) by someone with signing authority — typically the owner, MD, or finance lead.

Pattern C — Sector reclassification at the UEN level

ACRA-registered SSIC code at the UEN level can differ from what the owner thinks their business does. A company that operates as F&B but is SSIC-coded as wholesale trade may face category mismatches. Fix: Check the SSIC against the PSG sector categorisation; update at ACRA if there's a genuine misclassification.

---

What to do if you've already been rejected

If the rejection has happened, the first move is to identify which of the 7 reasons (or 3 patterns) applies. Then:

1. If you paid before applying → start over with a new project. The current one is unfundable.
2. If the vendor wasn't on the list or the category was wrong → reselect the vendor and reapply.
3. If the scope exceeded the cap or your eligibility failed → rescope, split, or address the eligibility issue.
4. If documentation was wrong → request a properly-structured quote from the vendor and reapply.
5. If you genuinely don't know which reason applies → ask the officer for a more specific reason via the Business Grants Portal. They're often more forthcoming when asked directly than when sending the original templated rejection.

---

What to do before you apply (the prevention list)

The 5 pre-application checks that catch the vast majority of rejections:

1. Have you paid or signed anything with the vendor? If yes — don't apply, start over with a clean vendor relationship.
2. Is the vendor currently on the PSG list for your sector and solution category? Verify via GoBusiness on the day of application.
3. Is the total project cost within the S$60k limit that gives you the S$30k cap? If not, rescope or split.
4. Does the vendor quote isolate PSG-eligible items from non-eligible items? Get a clean quote.
5. Does your group structure meet the 30% local equity, ≤S$100M sales OR ≤200 headcount tests? Run the PSG eligibility checker.

That checklist catches almost every preventable rejection. The remaining edge cases usually need a 15-minute conversation, not a 2-week proposal.

---

A note on consultants

PSG genuinely does not need a paid consultant. The application is straightforward if the vendor relationship is clean and the eligibility checks are done honestly. Anyone charging S$3k+ for a PSG application alone is over-charging for something the EnterpriseSG website and the official BGP portal walk you through directly.

Where consultants are useful is the combined PSG + EDG + CTC scoping — where the strategic question is "which grants should this project actually use, and how do we sequence them." That's strategic work, not application form-filling.

For context: I don't charge for PSG application reviews because the time investment doesn't justify it. What I do charge for is the strategic stack design — figuring out the right grant combination for a multi-grant project. If you've been rejected on PSG and want a 15-minute call to figure out why, message me. No charge for that conversation.

---

Related reading

• PSG vs EDG vs CTC — which grant should you actually apply for? — the parent decision tree
• How to scope an EDG proposal that survives the templated rejection — the EDG-side companion
• IMDA Industry Digital Plan Stages explained — context for when to use PSG vs EDG
• PSG Vendors Directory (593 approved) — the current vendor list
• PSG Eligibility Check — 2-minute checker
• /grants/psg — the canonical PSG landing page

— Nick

Frequently Asked Questions

What is psg grant rejection?

Psg grant rejection refers to the approach described in this article. Singapore SMEs apply this practically to reduce cost and increase leverage without adding headcount.

Who should consider psg grant rejection?

Any Singapore SME owner, manager, or operator looking to streamline their business — especially those running PSG, EDG, or NTUC CTC grant-funded projects.

How long does it take to implement?

Most SMEs see meaningful results within 4-8 weeks of a focused implementation. The bottleneck is usually decision-making speed, not technical complexity.