Direct answer: A procurement budget and unbudgeted-spend control page is not a line saying "no approval over budget". The page should state: budget dimensions (annual/quarterly/monthly, OPEX/CAPEX, category/cost centre/project/responsibility centre); preparation basis (sales/production plan, historical spend, price index, capacity/project schedule, FX/tax assumptions); approval (budget committee/management/board, by amount/category); execution and encumbrance (requisition/order commitment, incurred/not incurred, available balance, real-time control, tolerance); transfer/adjustment (reason, authority, limits on number/amount, records); unbudgeted/over-budget/emergency purchase (definition, approval tier, temporary budget, post-facto ratification, root-cause remediation); budget vs actual/variance analysis (price/volume/mix/timing/commitment not received); and what the website may and may not publish. On the rules: MOF Internal Control Application Guideline No. 15 (Comprehensive Budget) requires a comprehensive budget system covering preparation, approval, execution, adjustment and assessment; No. 7 (Procurement) requires controls over procurement planning, requisition, approval, acceptance and payment; No. 6 (Fund Activities) requires controls over cash budgeting and payment. This article is current to 2026-11-09 and is a summary of public rules and page method, not financial or management-accounting advice; company budget policy, authority matrix, contracts and system data control.
This article is for procurement, finance, budget, planning, internal-control, audit and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a procurement budget and unbudgeted-spend control page. The usual gap is "encumbrance, commitments not received, unbudgeted spend, emergency purchase, transfer/adjustment, variance analysis", ending with a page that only says "execute within budget", while procurement, finance, business and management blame each other when an overrun appears.
First fix the dimensions: annual/quarterly/monthly, category/cost centre/project/responsibility centre — if the basis differs, everything after is wrong. Then control encumbrance: requisition/order commitment, incurred/not incurred, available balance, real-time control and tolerance. Finally manage exceptions: unbudgeted/over-budget/emergency purchase needs approval, temporary budget, post-facto ratification and root-cause remediation. "No approval over budget" is not enough.
How does this page relate to PR→PO, material planning, three-way match, audit rights and management reporting?
The budget page answers "is there enough money, can we spend it, what if we exceed"; the PR→PO approval page answers "requisition/approval/authority/records"; the material-planning page answers "how much/when to buy"; the three-way-match page answers "order/receipt/invoice reconciliation"; the audit-right/books page answers "whether and how to audit"; management reporting answers "budget vs actual/variance/forecast". The budget page is the "limit—encumbrance—execution—exception—analysis" master control and cannot be replaced by a PR→PO or three-way-match page.
Common breaks: budget only annual/category; no monthly/quarterly rolling; requisition does not encumber; order commitment not counted; incurred/not incurred mixed; available balance calculated manually; unbudgeted spend relies on verbal leader approval; emergency purchase not ratified; adjustment/transfer without authority; variance only amount, not price/volume/mix/timing; the website publishes budget amounts. The page separates "dimensions—preparation—approval—encumbrance—adjustment—exceptions—analysis—public boundary" so procurement/finance/budget/business/management share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Budget/unbudgeted | Enough money/can spend/what if over | Dimensions, preparation, encumbrance, adjustment, exceptions, variance | PR→PO/three-way match |
| PR→PO approval | Requisition/approval/authority/records | Requisition, approval, authority, emergency purchase | Budget limit control |
| Material planning | How much/when to buy | Forecast, MRP, safety stock | Budget limit |
| Three-way match | Order/receipt/invoice reconciliation | Three-way, variance, credit note | Budget encumbrance |
| Audit right/books | Whether and how to audit | Scope, notice, access | Daily budget control |
| Management reporting | Budget vs actual/variance/forecast | Reports, variance, forecast | Budget approval |
Page relationships are editorial; company budget, procurement, finance and authority policies control.
How should budget dimensions and fields be set?
At least: period (annual/quarterly/monthly/rolling); nature (OPEX/CAPEX/project/R&D/tooling/service); category (material/outsourcing/equipment/spares/logistics/travel/service); organisation (company/plant/department/cost centre/responsibility centre); project/order/contract; currency/tax rate/VAT basis; version (initial/adjusted/rolling); status (draft/approved/effective/closed). The budget must roll down to "who is responsible, what to buy, when, how much" and map to procurement category, accounting category, cost centre and project number; if the dimensions differ, encumbrance and actuals will not reconcile. The public page explains "dimension categories, basis, responsibility", not specific amounts.
Acceptance checks: period; nature; category; organisation; project/contract; currency/tax; version; status; category mapping; owner. Common gaps: annual only; category too broad; cost centre unclear; project/contract not linked; VAT mixed; version unclear; status unclear.
| Dimension | What to write | Evidence | Common gap |
|---|---|---|---|
| Period | Annual/quarterly/monthly/rolling | Budget table | Annual only |
| Nature | OPEX/CAPEX/project/R&D/tooling/service | Budget table | Mixed |
| Category | Material/outsourcing/equipment/spares/logistics/service | Category table | Too broad |
| Organisation | Company/plant/department/cost centre/responsibility centre | Org table | Cost centre unclear |
| Project/contract | Project no./order/contract | System | Not linked |
| Currency/tax | Currency, VAT-inclusive/exclusive, rate | Budget table | VAT mixed |
| Version/status | Initial/adjusted/rolling; draft/effective/closed | Version record | Version unclear |
Budget dimensions are editorial; company budget, accounting and procurement policies control.
How should budget preparation basis and approval be accepted?
Preparation basis: strategy/business objectives; sales forecast/production plan/material plan; historical spend/unit price/usage; price index/FX/tax; capacity/project schedule/capex plan; headcount/organisation changes; one-off/recurring spend. Methods: top-down/bottom-up/combined; zero-based/incremental/rolling forecast; assumptions must be written and versions kept. Approval: budget committee/management/board by amount/nature/category; in-budget/unbudgeted/over-budget authority separated; approval needs basis/opinion/date; budget release must be formal and traceable. Do not "finance makes up a number" or "last year plus 10%" without assumptions.
Acceptance checks: basis; method; assumptions; version; approval tier; authority matrix; release; records. Common gaps: guessed; last year + %; no assumptions; approval beyond authority; not released; version chaos.
| Step | What to do | Evidence | Common gap |
|---|---|---|---|
| Business objectives | Strategy/sales/production/project plan | Plan document | No basis |
| History/unit price | Historical spend, unit price, usage, price index | Analysis | Guessed |
| Assumptions | FX/tax/capacity/schedule | Assumption table | Not written |
| Method | Top-down/bottom-up/zero-based/incremental/rolling | Preparation note | Unclear |
| Approval | Budget committee/management/board by tier | Approval record | Beyond authority |
| Authority matrix | In-budget/unbudgeted/over-budget separated | Matrix | One approval |
| Release | Formal release, version, owner | Release document | Not released |
Budget preparation/approval is editorial; company budget policy and authority matrix control.
How should budget execution and encumbrance be controlled?
Separate: budget limit; encumbered (requisition/order commitment/contract); incurred (receipt/invoice/payment); not incurred/not received; available balance = limit − encumbrance − incurred (basis defined by the company). Control points: requisition encumbrance, order commitment, contract signing, receipt/invoice, payment; over-tolerance needs approval; freeze/release/carry-forward rules; cross-period/cross-project restrictions; manual ledger must reconcile with ERP/budget system. Do not look only at "payment": if requisition/order commitment does not encumber, you get "budget looks enough but cash is not" or "overrun discovered late".
Acceptance checks: limit; encumbrance; incurred; not incurred; available balance; control points; tolerance; freeze/release; cross-period/project; system reconciliation. Common gaps: payment only; requisition not encumbered; order not encumbered; manual balance; no tolerance; no freeze/release rule; two ledgers.
| Concept | How to control | Evidence | Common gap |
|---|---|---|---|
| Limit | Annual/quarterly/monthly release | Budget table | Total only |
| Encumbrance | Requisition/order/contract commitment | System | Not encumbered |
| Incurred | Receipt/invoice/payment | System | Payment only |
| Not incurred/not received | Open commitment, in transit | Order/ASN | Not counted |
| Available balance | Limit − encumbrance − incurred | Report | Manual |
| Tolerance | Amount/ratio, approval | Policy | Not stated |
| Freeze/release | Rule, approval, record | Record | No rule |
| Cross-period/project | Restriction, approval | Record | Free movement |
Budget execution/encumbrance is editorial; company budget, procurement and finance policies control.
How should budget adjustment/transfer and unbudgeted/over-budget spend be managed?
Adjustment/transfer: reason (plan change/price/project/organisation); authority (category/amount/percentage); limits on number/amount; in-budget/cross-category/cross-department/cross-period; approval/records; updated version/release; not a way to "wash an overrun". Unbudgeted/over-budget: definition (no budget/over limit/over tolerance); approval tier (department/finance/GM/board by amount); temporary budget/prior approval; emergency purchase may be ratified after the fact, but with time limit/evidence/root cause; overrun needs cause/responsibility/remediation; rolling forecast updated. Do not treat "unbudgeted" as "leader's verbal approval", or "adjustment" as "after-the-fact ticketing".
Acceptance checks: reason; authority; number/amount; cross-category/department/period; approval; version; unbudgeted definition; temporary budget; emergency ratification; root-cause remediation; rolling forecast. Common gaps: no authority; unlimited adjustment; wash overrun; verbal unbudgeted; no ratification; no analysis; forecast not updated.
| Scenario | How to manage | Evidence | Common gap |
|---|---|---|---|
| Budget adjustment | Reason, authority, amount/number limit, approval | Adjustment form | No authority |
| Budget transfer | Cross-category/department/period limits | Transfer form | Free transfer |
| Unbudgeted | Definition, approval tier, temporary budget | Approval | Verbal approval |
| Over budget | Tolerance, approval, cause, remediation | Analysis | No analysis |
| Emergency purchase | Prior/post-facto ratification, time limit, evidence | Record | No ratification |
| Rolling forecast | Update, version, variance | Forecast | Not updated |
Adjustment/unbudgeted control is editorial; company budget policy and authority matrix control.
How should budget vs actual/variance analysis be accepted?
At least: budget, encumbrance, actual, variance, variance rate, forecast; cause (price/volume/mix/timing/FX/tax/commitment not received/budget error); responsibility centre/category/project; monthly/quarterly review; rolling forecast update; follow-up actions for overrun/savings. Variance analysis is not "explain it away"; it should guide next year/quarter budget, procurement strategy, price negotiation and supplier selection; budget assessment should distinguish controllable/uncontrollable and not rely on a single execution-rate metric. Public metrics must be true with clear basis; do not publish specific amounts/suppliers/prices.
Acceptance checks: basis; budget/encumbrance/actual/variance/forecast; cause; responsibility; review; rolling forecast; assessment; public basis. Common gaps: amount only; no price/volume/mix/timing; no controllable split; no review; forecast not updated; single metric.
| Analysis item | What to do | Evidence | Common gap |
|---|---|---|---|
| Basis | Budget/encumbrance/actual/forecast definitions | Policy | Mixed basis |
| Variance | Amount/rate, price/volume/mix/timing | Analysis | Amount only |
| Cause | Price/usage/mix/timing/FX/commitment | Analysis | No analysis |
| Responsibility | Responsibility centre/category/project | Org table | Unclear |
| Review | Monthly/quarterly, action items | Minutes | No review |
| Rolling forecast | Update, version, variance | Forecast | Not updated |
| Assessment | Controllable/uncontrollable, multiple metrics | Scorecard | Single execution rate |
Variance analysis is editorial; company management-accounting, budget and assessment policies control.
How should the website page be written, and what must not be published?
Suggested sections: (1) budget dimensions/basis; (2) preparation/approval; (3) execution/encumbrance/available balance; (4) adjustment/transfer; (5) unbudgeted/over-budget/emergency purchase; (6) variance analysis/rolling forecast; (7) contact/update date. The public page explains "principles, process, responsibility and boundaries" and does not publish specific budget amounts/category details, cost-centre/project amounts, suppliers/prices, unbudgeted/overrun details, approvers/signatures or system screenshots; specifics are handled in budget/finance/procurement controlled systems. Do not write "budget never exceeded/no overrun approved/unbudgeted never allowed" if you cannot prove or deliver it.
The English page should use consistent terms (budget, budget dimension, cost centre, responsibility centre, encumbrance, commitment, available balance, budget transfer, unbudgeted spend, over-budget, emergency purchase, variance analysis, rolling forecast) and state the cut-off date. It can link to PR→PO, material planning, three-way match, audit-right and management-reporting pages, but must not become a "no approval over budget" line.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Dimensions/basis | Period/category/organisation/project/currency | Budget table | Annual only |
| Preparation/approval | Basis/assumptions/authority | Preparation note | Guessed |
| Execution/encumbrance | Requisition/order/incurred/available | System | Payment only |
| Adjustment/transfer | Reason/authority/limit/record | Adjustment form | Wash overrun |
| Unbudgeted/overrun | Definition/approval/temporary/ratification | Record | Verbal approval |
| Variance/forecast | Price/volume/mix/timing, rolling | Analysis | Amount only |
| Public boundary | No amounts/categories/suppliers | Permissions | Publish all |
The page structure is editorial; public statements must be true and verifiable, and company budget, finance and procurement policies control.
Go-live acceptance checklist
Ten checks: budget dimensions/basis; preparation basis/assumptions; approval/authority matrix; execution/encumbrance/available balance; adjustment/transfer; unbudgeted/over-budget/emergency purchase; variance analysis/rolling forecast; system/ledger reconciliation; public boundary; review/remediation. Each needs evidence and a review date. The pass standard is not "the page says no approval over budget", but that procurement/finance/budget/business/management can judge whether the limit is enough, how encumbrance is calculated, who approves an overrun, how to adjust and how to analyse variance.
Before go-live, run a tabletop exercise with a real (redacted) procurement project: budget release → requisition → encumbrance → order → receipt/invoice → payment → variance → adjustment/unbudgeted → rolling forecast → review. Then simulate "requisition does not encumber", "order commitment not received", "unbudgeted emergency purchase" and "cross-category transfer" to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Dimensions/basis | Period/category/organisation/project/currency | Budget table | Add dimensions |
| Preparation/assumptions | Basis, assumptions, method, version | Preparation note | Add basis |
| Approval/authority | Tier, matrix, release | Approval record | Add approval |
| Execution/encumbrance | Requisition/order/incurred/available | System | Add encumbrance |
| Adjustment/transfer | Reason/authority/limit/record | Adjustment form | Add process |
| Unbudgeted/overrun | Definition/approval/temporary/ratification | Record | Add rule |
| Variance/forecast | Price/volume/mix/timing, rolling | Analysis | Add analysis |
| System/ledger | Budget system/ERP/manual reconcile | Reconciliation | Reconcile |
| Public boundary | No amounts/categories/suppliers | Page/permissions | Take down |
| Review/remediation | Monthly/quarterly, action items | Minutes | Add review |
The acceptance list is editorial; company budget, finance and procurement policies control.
Who should read it, who should not, and what decisions does it support?
For procurement, finance, budget, planning, internal-control, audit and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "budget only annual, requisition not encumbered, order commitment not counted, verbal unbudgeted approval, emergency purchase not ratified, adjustment washing overrun, variance only amount". Not for teams that do not involve procurement budgets, or that want one page to replace financial/management-accounting advice.
Read it if: building a budget page; only "no approval over budget"; annual only; category too broad; requisition not encumbered; order not encumbered; manual balance; verbal unbudgeted; no emergency ratification; adjustment without authority; variance only amount. Not suitable if: treating "budget" as "payment"; treating "encumbrance" as "incurred"; treating "adjustment" as "ticketing"; treating "unbudgeted" as "leader's verbal approval". Supports: dimensions/basis, preparation/approval, execution/encumbrance, adjustment/transfer, unbudgeted/overrun, variance/forecast and public-boundary self-checks.
FAQ
What is the relationship between budget and payment?
Budget is the "can we spend/how much" limit control; payment is the actual cash out. Requisition/order commitment encumbers the budget; receipt/invoice/payment becomes incurred. If you look only at payment, you get "budget looks enough but cash is not" or "overrun discovered late". The page should state the basis for limit, encumbrance, incurred, not incurred/not received, available balance and control points, and how the budget system maps to ERP/payment.
How detailed should budget dimensions be?
At least period (annual/quarterly/monthly/rolling), nature (OPEX/CAPEX/project), category, organisation (cost centre/responsibility centre), project/contract and currency/tax. Too coarse cannot control; too detailed costs too much to manage. The key is to map to procurement category, accounting category, cost centre and project, and answer "who is responsible, what to buy, when, how much". The granularity depends on company size, business complexity and system capability.
Should requisitions/orders encumber the budget?
Recommended. If requisition/order commitment does not encumber, an overrun is only discovered at receipt/payment. Common practice: requisition encumbrance, order commitment, receipt/invoice to incurred, payment write-off; available balance = limit − encumbrance − incurred (basis defined by the company). Handle release on order cancellation/change/return, and cross-period/cross-project restrictions.
How should unbudgeted/over-budget spend be approved?
First define: no budget, over limit, over tolerance, category/project mismatch. Then set the approval tier (department/finance/GM/board by amount/nature); approve in advance where possible; emergency purchase may be ratified after the fact, but with a time limit, evidence, root cause and remediation; unbudgeted must not become "leader's verbal approval". Update the rolling forecast at the same time so the next month does not overrun again.
What are the risks of budget adjustment/transfer?
If authority, number and amount are not limited, adjustment/transfer can become "washing an overrun": moving another category/department/project limit to cover the gap and hiding the real variance. State the reason, authority, cross-category/department/period limits, approval and records; update the version/release after adjustment. Adjustment cannot replace root-cause analysis and remediation; audit should trace the full chain "original budget—adjustment—execution—variance".
Is amount-only variance analysis enough?
No. At least split price/volume/mix/timing/FX/tax/commitment not received/budget error; distinguish controllable/uncontrollable; review by responsibility centre/category/project; update the rolling forecast. Variance analysis should guide next year/quarter budget, procurement strategy, price negotiation and supplier selection, not just explain "why it overran".
Should the website publish budget amounts and execution rates?
Usually not specific budget amounts/category details, cost-centre/project amounts, suppliers/prices, unbudgeted/overrun details, approvers/signatures or system screenshots. The public page can explain budget dimensions/basis, preparation/approval principles, execution/encumbrance, adjustment/unbudgeted rules, variance analysis/rolling forecast and a contact window; specifics are handled in budget/finance/procurement controlled systems. Do not write "budget never exceeded/no overrun approved/unbudgeted never allowed".
One-sentence takeaway
The procurement budget and unbudgeted-spend control page on a Changzhou manufacturer's website is not about "no approval over budget"; it is about turning budget dimensions/basis, preparation basis/assumptions, approval/authority, execution/encumbrance/available balance, adjustment/transfer, unbudgeted/over-budget/emergency purchase, variance analysis/rolling forecast, system/ledger reconciliation and public boundaries into a checkable list, so procurement/finance/budget/business/management can judge whether the limit is enough, how encumbrance is calculated, who approves an overrun, how to adjust and how to analyse variance.
Research method and limitations
This article is a summary of public rules and page method, not financial or management-accounting advice. It uses no unpublished budget amounts, category details, cost-centre/project amounts, suppliers/prices, unbudgeted/overrun details, approvers/signatures or system screenshots; the tables and acceptance items are editorial and not financial conclusions. MOF Internal Control Application Guideline No. 15 (Comprehensive Budget), No. 7 (Procurement) and No. 6 (Fund Activities); company budget, finance and procurement policies, authority matrix and system data control. This article does not decide whether any specific budget dimension/approval authority/adjustment rule is reasonable, and does not promise zero overrun; companies should set them item by item based on size, business and system capability.
Sources and basis
Current to 2026-11-09; the official pages below control.
- MOF Internal Control Application Guideline No. 15 — Comprehensive Budget (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Budget preparation, approval, execution, adjustment and assessment.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Procurement planning, requisition, approval, acceptance and payment.
- MOF Internal Control Application Guideline No. 6 — Fund Activities (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Cash budgeting and payment controls.