On November 10, the Zhuhai Municipal Bureau of Industry and Information Technology issued a notice of more than 200 Chinese characters. Its first sentence was: "The filing and preliminary application work for provincial-level manufacturing empowerment projects has begun."
This sentence is a bit strange. Because the "Guangdong Province Manufacturing Empowerment Reward Special Fund Scheme (2026–2028)" is still "about to be issued"—on October 10, the provincial Department of Industry and Information Technology publicly solicited comments, and the reward and subsidy amounts for five tiers were clearly written, but we have never been able to find the officially issued version on the provincial department's portal.
The file didn't appear, but the window opened first. This is not a typo.
Filing precedes the document—this is not a typo
The usual rhythm for funding-type policies is: issue the plan → provide supporting application guidelines → open the application window → review → disburse funds. This time the order has been split: filing opens first, and formal applications open after the plan is implemented.
The reason is not hard to guess. The review of this type of ex-post award and subsidy examines the expenditures already incurred and results already produced by the project, and the review cycle is long. If projects were collected only after the document is issued, there would not be enough time in the year. Filing in advance is equivalent to building the project pool first, so once the document arrives, projects can directly enter review.
So the nature of the filing step needs to be clarified: it is not an intent registration; it is the project working papers.
The project name, affiliated direction, service content, start and end time, and investment amount filled in at the time of filing will be checked item by item in subsequent formal applications and reviews. If filled in vaguely, later you will either be unable to change them, or if you change them, they will not match the original materials that were audited.
By the way, let us also lay out the other timeline: the selection for the third batch of manufacturing empowerment resources closes on November 19 (Guangdong Industry and Information Technology Digital Industry Letter [2026] No. 67). We wrote about this in both articles on November 3 and 6; it is the entry point for service providers to enter the resource pool. The two tracks share one platform, but they are not the same thing—one selects service providers, the other prepares projects.
Party A and Party B: two entry points, two sets of materials
This notice from Zhuhai clearly distinguishes between the two types of entities.
The requesting party, namely Party A—manufacturing enterprises and software information service enterprises. The action is to visit the project application entry point of the “Yuezhifu” platform and, in accordance with the “Yuezhifu Platform Project Filing and Application Guidelines,” complete project filing and pre-application.
The supplier, namely Party B—the service provider. They must first be selected to enter the platform, follow the "Guidelines for Declaration of Empowerment Resource Repository Entry", and complete it by November 19.
We are on both sides. As a service provider, November 19 is a hard deadline, and the materials are things like delivery records, project lists, and capability descriptions. As a consultant doing implementation for manufacturing enterprises, I am more concerned with what the client side needs to prepare.
What Party A needs to prepare, in the final analysis, is four types of documents along one chain: the service contract, invoice, payment voucher, and acceptance materials. Plus a set of performance data.
It sounds simple, but it isn't in practice. Last month we helped a client review a project intended for filing. The contract was signed in December 2025, implementation took seven months, three invoices were issued, payment was made in four installments, and the acceptance form had only one signature page and did not state the acceptance content. This kind of material is the hardest to explain during review—not that it is missing, but that it doesn't match up.
In Odoo, these four types of documents should naturally sit on the same chain. A contract is a purchase order, an invoice is a vendor bill, a payment is a payment order, and acceptance is a receipt or the completion record of a project task. As long as an independent analytic account is created for the project from the outset, the four types of documents will automatically be grouped together, and whatever is needed for review can be exported directly. Conversely, if the contract is recorded in the procurement department, the invoice in finance, and the acceptance in the project manager's WeChat, putting it together ad hoc will take at least three days—and still won't be accurate.
There is also a more preliminary judgment: whether the project has been completed.
The program is a post-event award/subsidy, and it supports “empowerment projects that have already been implemented.” For projects that are not yet completed, filing now will most likely not get them into the first batch. So first ask yourself one question: Can this project complete implementation, finish issuing all invoices, and obtain acceptance within 2026? If yes, file; if not, don’t hold a slot for now—wait for the next batch.
The numbers you fill in when filing must match up at review
This item is the core of the whole matter, and also the place where things are most likely to go wrong.
The draft for comments states five tiers of awards and subsidies: no more than 3 million, 6 million, 9 million, 12 million, and 15 million, and in principle the award or subsidy amount for each tier must not exceed 30% of the project's actual empowerment service expenditure. This sentence has two layers of meaning: the tier is determined by review, and the upper limit is constrained by actual expenditure.
Thus the figure of "actual expenditure" became the vital point. It must be verifiable expenditure that corresponds to the service content and is backed by invoices and payments; internal labor, travel, and portions that have already received other government fiscal funds must not be mixed in.
We have seen two typical mistakes.
One is calculating spending too broadly. They include all IT spending during the project implementation period, including ERP subscriptions that would have been renewed anyway, office computers, and network upgrades. Once reviewed, less than half is recognized, and the tier directly drops by two levels.
Another issue is that results are calculated too vaguely. Statements such as "efficiency improved by 30%" and "management is more standardized" lack both a baseline and a data measurement basis. Ex-post reward and subsidy reviews examine input-output; if the results cannot be clearly explained, no matter how solid the expenditure is, it still will not pass.
Outcome metrics must be set at the start of the project, not worked backwards at the end. If the reported direction is AI application, the metrics usually examined are those that can produce numbers, such as delivery cycle, output value per capita, yield rate, and order response time. These figures all have sources in Odoo: delivery cycle is the time difference from sales order confirmation to shipment; output value per capita is output value divided by registered headcount; yield rate is the ratio of qualified quantities in work orders. The premise is that these processes run in the system, not in Excel.
There is a boundary that must be clarified: as of November 13, we have not obtained the original attachment of the "Yuezhi Fu Platform Project Filing and Application Guidelines," nor have we found the officially issued draft of the funding plan or the application guidelines on the provincial department's portal. Therefore, which fields are mandatory on the filing form, whether there is a deadline for Party A's filing, and whether a contract must already exist at the time of filing are all subject to the actual platform page. The "application from November 5 to 30" circulated on third-party platforms is a secondhand account; we have not verified it on the official website and cannot use it as a basis.
Three things you can do this week
First, answer one question this week: whether the project proposed for filing has been completed. The criterion is that all three things are complete—implementation is finished, all invoices have been issued, and the acceptance form has content. If all are complete, file it; if not, wait for the next batch. November 19 is Party B's deadline. Party A's filing has no public deadline, but after the plan is officially issued, there will most likely be only a very short window, so it is best to prepare the materials package now.
Second, put the four types of documents on the same track. Create an independent project number or analytic account for the project to be filed, and attach all contracts, invoices, payments, and acceptance documents to it. Whichever category is missing, make it up this week. In particular, for acceptance forms that only have signatures and no acceptance content, ask the service provider to supplement one with a delivery checklist.
Third, define the boundary of “actual expenditure” first. List all expenditure items intended to be included, and ask three questions for each item: Is there a contract? Are there invoices and payment? Has it received other fiscal funds? Only if all three are “yes” is it included. Doing this list now is much less trouble than doing it before review—in the projects we have done, rework caused by unclear boundaries usually takes two weeks.
