YonSuiteFinanceIntermediateContent quality · 94/100

YonSuite Treasury Funding Plan: Control Versions, Gaps and Approvals

Combine operating cash and approved funding by account, currency and date to expose liquidity gaps with version control.

资金计划版本控制 / Treasury Funding Plan18 minUpdated 2026-08-21
01

Learning objective

Create a funding plan with traceable assumptions, approvals and actual feedback.

Roles

Finance, process owners, key users, IT, consultants and internal audit

Prerequisites

  • Confirm entity, period, currency, masters and access.
  • Prepare approved normal and exception data.
  • Define approvals, cut-off and change control.

Completion checks

  • Results trace to source and accountable role.
  • Quantity, amount, period and status are reviewable.
  • Exceptions retain cause, approval, action and closure evidence.

Common errors

  • Overwriting history and losing traceability.
  • No segregation of duties.
  • Testing only normal flow.

Thailand project note

Thai implementations should confirm Thai/English masters, THB and foreign currencies, Asia/Bangkok time, segregation, approvals and local retention. This covers ERP management controls only; VAT, WHT, BOI, customs and statutory-accounting conclusions require qualified Thai professional review.

Related modules

finance-governancemanagement-accountinginternal-control

03

Steps

01Confirm treasury entities, bank accounts, currencies and account owners.
02Collect approved receivables, payables, payroll, capital spending and funding arrangements.
03Record date, amount range, confidence and source for every cash event.
04Calculate account balances and minimum liquidity under base, stress and improvement scenarios.
05Link each funding gap to action, owner, approval and deadline.
06Weekly, compare bank actuals and publish a new version without overwriting history.
  1. 01

    Confirm treasury entities, bank accounts, currencies and account owners.

  2. 02

    Collect approved receivables, payables, payroll, capital spending and funding arrangements.

  3. 03

    Record date, amount range, confidence and source for every cash event.

  4. 04

    Calculate account balances and minimum liquidity under base, stress and improvement scenarios.

  5. 05

    Link each funding gap to action, owner, approval and deadline.

  6. 06

    Weekly, compare bank actuals and publish a new version without overwriting history.

04

Implementation notes

  • Pilot one entity and representative period.
  • Exceptions require source, owner and closure evidence.
  • Menus and fields depend on current release and blueprint.
05

References