The notice establishes a filing route, documentary requirements, and a district review step. It does not, by itself, establish final approval, confirm that a later application window is open, or supply fixed funding terms.
The boundaries are transactional
The compute voucher category covers rented intelligent-computing resources from a non-affiliated provider while excluding storage, network, security, and other services. The model or Token voucher category covers third-party model API costs on a non-affiliated cloud platform or private deployment of a third-party model. The corpus voucher category covers high-quality corpora purchased from a non-affiliated provider.
Across all three categories, resource use, provider relationship, and cost category shape what a company can present. Eligibility to file and approval to receive support remain separate determinations.
Storage, network, security, and other bundled services sit outside the stated core category.
The provider and platform relationship is part of the claim, not incidental metadata.
The supported object is a documented purchase for model or agent work, not a general data budget.
The distinctions matter because one invoice can contain several things at once. A compute contract may also include storage and security; a cloud bill may combine model calls with unrelated platform services; a data purchase may include work that the notice does not identify as corpus expenditure. The filing logic requires the claimed amount to remain traceable to the supported object.
The applicant must clear threshold conditions before the ledger matters
The notice requires the applicant to operate legally in Shanghai, bear civil liability independently, remain in normal operating status, maintain good credit and sound financial systems, and avoid claiming another Shanghai municipal fiscal subsidy for the same project. source ↓
These are threshold conditions, not a scoring promise. Passing them does not convert a filing into an award. It only means the company has not failed one of the explicit entry conditions before the municipal review process begins.
The filing burden is a record-matching exercise
Every uploaded application file must carry the electronic seal in the “Legal Person One Certificate” digital certificate. An unsealed submission is treated as unsuccessful. source ↓
The attached audit templates point to accounting books, contracts, bank flows, payment records, and service-provider settlement documents. Before filing, a company should reconcile claimed use to contract, accounting, payment, and provider records rather than treat the application form as a self-contained narrative.
The route is specified; later timing is not
Applications pass through the commission’s special-funds project platform. District departments conduct an initial review of the truthfulness and completeness of the materials and submit their opinions to the municipal commission. Final approval remains beyond those steps.
The notice plans four application batches in 2026, gives the first window as 8 May at 10:00 to 27 May at 16:00, and says later batches accept applications in the first month of each quarter. source ↓
The captured package gives no exact opening and closing times for the later batches. “First month of each quarter” is therefore a monitoring cue, not evidence that a later batch is open now.
What a company should assemble before filing
The notice turns the application into a controlled reconciliation exercise. A useful internal file should be able to answer the same questions in the same order every time:
- 01Identify the supported object.
Separate eligible compute, model or API, private-deployment, or corpus expenditure from adjacent services that the notice does not name.
- 02Prove the provider relationship.
Record whether the provider is non-affiliated and whether the route is a direct filing or a filing coordinated through an approved platform or AI-town operator.
- 03Reconcile the money trail.
Match the claimed use to contract, invoice, accounting entry, bank flow, payment record, and provider settlement document.
- 04Validate the filing state.
Confirm the exact active window, district requirements, platform submission, and electronic seal before treating the packet as successfully filed.
This preparation is useful even before the next batch opens. It exposes ineligible bundled services, missing counterparty evidence, inconsistent accounting, and unsupported reimbursement assumptions while those problems can still be corrected.
Limit
Across the 30-page package, no fixed subsidy amount, cap, or percentage is supplied for any voucher category. One template contains an unfilled rate placeholder. This packet alone cannot support a reimbursement forecast.
What would change this assessment
A separate official rule specifying fixed funding terms, or a newly checked official batch notice with exact opening and closing times.
Editorial explanation based on the cited source; not a certified translation, legal advice, or confirmation of programme eligibility.