For the same Odoo contract, Guangzhou includes the implementation fee, while Foshan and Shantou do not.

Guangzhou’s third batch closes on November 22; let’s put the award and subsidy base calculation methods of the three places side by side.

A client in Panyu that makes automotive interior parts sent me two contracts to review last month. One is in Guangzhou, the other in Nanhai; both use the same Odoo system, both are 400,000 for software, 300,000 for implementation, and 100,000 for customization, and the module lists are almost identical.

He was asking the same question: for these two contracts, how much can each of them be reimbursed.

I calculated it according to the standards of both places: the Guangzhou base figure is 700,000, and the Foshan one is 400,000. With the same system, the base differs by 300,000.

The difference lies in the implementation fee.

The qualification deadline for this batch in Guangzhou was November 15, and it has already passed

First, let's be clear about the timeline. On November 16, the Guangzhou Municipal Bureau of Industry and Information Technology issued the notice for the third batch of applications for inclusion in this year's digital transformation project database, which is also the last batch of the city's pilot program. The notice contains three hard dates.

By November 15, complete the transformation, complete the digitalization level evaluation (must reach Level 2 or above), and complete the project special audit. By November 22, submit the database entry application on the public service platform. From November 23 to 25, formal review will be conducted; those who fail must supplement and correct their materials by November 25.

Today is November 17. The first door has already closed.

What this means is that this batch is not one for "starting preparations now." The evaluation report is only issued after a third-party comprehensive service agency has completed an on-site visit; the special audit report is only issued after an accounting firm has completed an on-site visit. These two documents cannot be produced within five days. If you already have both reports in hand, five days is enough; if you are still waiting for evaluation scheduling, this batch has nothing to do with you.

To be honest, in the final work arrangement dated October 15, the renovation completion date was written as October 31. This notice pushes all three items—renovation, evaluation, and audit—uniformly to before November 15. The two documents do not match; the latest one is to be followed—but for enterprises that had previously scheduled according to October 31, it amounts to two extra weeks.

Implementation fee: Guangzhou is included in the base; Foshan and Shantou are not.

Back to those two contracts.

Guangzhou’s algorithm is written into the scope of awards and subsidies: software, cloud services, and necessary implementation service expenditures, plus gateways, routers, sensors, large-model all-in-one machines, industrial control systems, and firewalls—these data acquisition, transmission, and industrial control devices—are all tax-exclusive. It is followed by a restriction: the actual investment in implementation service fees shall not exceed the actual investment in the corresponding software products, calculated at a maximum of no more than 1:1.

400,000 in software paired with 300,000 in implementation; at 1:1, that's the 400,000 line, and 300,000 is within the line. Base 40 plus 30, 700,000.

What about the 100,000 customization? In the list in this Guangzhou document, the term “customization fee” is not listed separately, nor is it excluded. Whether it counts depends on how the contract is broken down and how the audit recognizes it. There is a pitfall here: whether the same sum of money is written as “customization development” or as “implementation services,” the result differs in the two cities.

Foshan's algorithm is different. The project-library filing notice, Foshan Industry and Information Technology Letter [2026] No. 333, states very directly: the approved project investment costs include expenditures on software and cloud services related to digital transformation, and necessary expenditures on data collection and transmission and industrial control equipment, all excluding tax, and do not include implementation fees, customization fees, training fees, maintenance fees, and other related expenditures.

For the same contract, the base in Foshan is only 400,000.

Shantou's application guidelines (revised version) for this year follow the same standard, and also do not include implementation fees, customization fees, training fees, or maintenance.

Multiply the three places by their respective incentive ratios and caps, and the figures separate out. Run through the calculation once using the configuration above—this is a calculation example, not a policy commitment:

CityApproved baseProportionUpper limitCalculation Results
Guangzhou700,000Cumulative no more than 50%Level 2 600,000 / Level 3 2,000,000 / Level 4 5,000,000350,000
Foshan400,000No more than 30%Levels 2 and 3: 500,000 / Level 4: 700,000120,000
Shantou400,000No more than 50%Benchmark 500,000 / Others 120,000120,000

That 50% in Guangzhou has a precondition: cumulative funds from the central, provincial, and municipal levels must not exceed 50% of the approved investment; the specific proportion is determined according to the funds allocated by the finance department. The 350,000 is a ceiling, not the amount actually received. The 120,000 in Foshan also depends on the funding pool; the document states "total amount control, acceptance in batches, first come first served," and applications are processed in order until the funds are used up.

Even so, for the same system, Guangzhou is 350,000, Foshan is 120,000, and Shantou is 120,000—a difference of 230,000. This is not a question of subsidy intensity, but of how the base is calculated.

Three orders minimum, and subscriptions monthly

There are two more details in this Guangzhou notice that are most easily miscalculated during financial reconciliation.

The first is the minimum of the three documents. The verified investment is taken as the minimum of the contract, the tax-exclusive invoice amount, and the payment voucher. We encountered a project: the contract was 800,000, invoices were issued for 720,000, actual payment was 600,000, and the balance was withheld and unpaid. In the end, the verified base was 600,000, not 800,000. Calculated at 50%, that was 100,000 less.

All three lines exist in the system: the purchase order amount is on a contract basis, the supplier invoice is on an invoice basis, and the payment voucher is on a funds basis. The problem is that many companies reconcile only two of them. Before filing, run all three lines by project number once; you can see at a glance which document the difference lies in.

The second is subscription-based products and cloud services. The notice states that the calculation is made month by month based on the actual number of months of use, and the accounting period runs from the contract start date within the policy period to the month in which the project application ends.

That means don't bill by whole years. A subscription contract beginning in September 2025 and running to November 2026 is 15 months, not 12 months, nor 24 months. Break it down by month, and the amount for each month must match the invoice.

One more reminder, related to group customers. The notice states: if there is an affiliated relationship between the two parties to the transaction, the reporting entity must provide supporting materials and fully explain the related-party transaction, including the reasons for product and service transactions with related parties and the fairness of prices, etc.

Put bluntly, when a sibling company sells a system to another, or a parent company charges its subsidiary a software usage fee, this type of transaction must be able to prove that the price is fair. Can the system flag related-party transactions by counterparty, and can it pull the price range for similar customers? That is when it becomes useful. If you do not flag them in normal times and have to dig through the accounts when filing, it is very troublesome.

In addition, after the review is passed, on-site acceptance inspections will be conducted for no less than 30% of the total number of projects submitted for inclusion in the database. The acceptance inspection content states that it is to verify whether the renovation content is consistent with the contract, whether it has actually been deployed, and the actual operation of the software system. The contract specifies eight modules, but only five have been implemented in the system; this item alone will not pass.

Three things you can do this week

1. Those who have evaluation reports and special audit reports issued before November 15 must complete submission by November 22. From November 23 to 25, log in to the public service platform once a day to check formal review feedback; November 25 is the last opportunity to make corrections, and no further submissions will be accepted after that.

II. For enterprises with factory sites in Guangzhou, Foshan, and Shantou, determine the base separately by locality. Do not apply Guangzhou's "implementation fee 1:1" approach to the contracts in Foshan and Shantou—in those two contracts, not a single cent of the implementation fee can be included in the base, and how the contract is split and how modules and implementation are quoted should also be adjusted accordingly.

III. For subscription contracts, extract the billing cycle table separately, verify the accounting periods by month, and confirm that each month's amount has a corresponding invoice. Finance cannot complete this alone; contracts, invoices, and payments must be reconciled together.

关于我们

​我们致力于帮助中小企业实现数字化转型,我们的团队由一群充满激情和创新思维的专业人士组成,他们具备丰富的行业经验和技术专长。

扫一扫获取顾问以及手册

Sign in to leave a comment
Place an order and get half off, but the equipment cannot be moved out of Longgang within three years.
Longgang robot vouchers launch on November 11, with a per-project cap of 5 million; the upfront subsidy comes in exchange for a three-year regulatory period