Skip to main content
Zemerc
BCMSDeliver · Project Delivery & Controls

Budget & Cost Management System

Every financial figure retains its defined source and ownership. against it.

The governed financial record for capital projects and programmes, connecting estimates, approved budgets, baselines, commitments, actual costs and forecasts with earned value, cash flow, funding, change, cost risk, commercial claims and approval history.

BCMS dashboard catalogue covering executive, portfolio, programme, project, financial, commercial, cost-risk, administrative, operational and AI-assisted views, with role-specific scope and figures derived from governed source records
0Report definitions
0Roles in the catalogue
0Governed datasets
0Role-targeted dashboards
The cost chain

Nine controlled steps in the financial chain

BCMS preserves the provenance of every figure through the financial chain, including who approved it, the authority applied and subsequent changes.

Estimate
Budget
Baseline
Commitment
Actual cost
Forecast
Earned value
Period close
Closeout
Plan
Spend
Project
Close
Stage 1 of 9 · Plan
Estimate

Estimated cost before commitment

In the application: Estimates
Record purpose

Four questions that governed cost records must answer

Cost-control workbooks perform arithmetic effectively, but provenance can become difficult to demonstrate when a figure is challenged. BCMS retains the source, approval history and relationship to the authorised baseline.

0
Report definitions
0
Roles in the catalogue
0
Governed datasets
0
Role-targeted dashboards
Approval history
Recorded against the person · Not the mailbox it passed through
Approval authority
Authority limit by role and value · Checked at the moment of approval
Current status
One record per figure · No second copy that disagrees
Change history
Append-only audit trail · Not amendable, including by an administrator
Checked on the server Segregation of duties Posted transactions are immutable
A financial figure with traceable provenance
Approvals

Approval authority configured as data rather than hard-coded

Each financial decision, including a baseline, budget revision, transfer, contingency drawdown or commercial claim, follows a versioned workflow with defined subjects, stages and approval authorities. Changing an approval route is controlled configuration, not a software release.

Versioned BCMS approval-workflow definitions covering baselines, budgets, transfers, cash flow, change, claims, commitments, contingency, cost risk, estimates and forecasts, each with a defined subject, version and active state

Each workflow definition is versioned, and an approval remains attached to the version under which it was granted.

  • Five kinds of authority limit
    Authority is a value as well as a role: what this person may approve, and up to what amount.
  • Segregation of duties as policy
    Prohibited combinations of actions on the same record are configured and enforced rather than left to convention.
  • Delegation is bounded
    by time and value. Expired delegations are surfaced rather than remaining active.
Independently operable

A complete, independently operable cost-management system

BCMS supports optional connectors through vendor-neutral integration ports. Connectors are disabled by default, and the application remains independently operable without them.

Application controls and limitations
  • No external system is required
    New integrations default to a disabled adapter until explicitly configured.
  • Credentials are not exposed
    They are resolved by the deployment at runtime and are not displayed through the application.
  • The finance system remains authoritative
    for accounting records. BCMS consumes those records where required and remains authoritative for budgets, forecasts, change and commercial-control records.
Capability architecture

Six functional groups drawn from the application's navigation

The application structure shown here reflects the functional navigation available to users.

  • Financial structure

    Regions, programmes, projects, fiscal calendars and reporting currencies provide the structure against which financial records are posted and reported.

    • Projects
    • Programmes
    • Regions
    • Fiscal calendars
    • Exchange rates
  • Cost management

    The financial chain links estimates, budgets, baselines, commitments, actual costs and forecasts while preserving the approved history of each movement.

    • Estimates
    • Estimate comparison
    • Budgets
    • Commitments
    • Commitment exceptions
    • Actual costs
    • Accruals
    • Project financials
    • Period close
    • Cost closeout
    • Benchmarks
  • Performance and funding

    Forecast outturn, funding position, earned value, trend, cash flow and payment milestones show what the project is expected to cost and whether funding is available when required.

    • Forecasts
    • Forecast comparison
    • EVM measurements
    • EVM trend
    • Cash flow plans
    • Funding
    • Payment milestones
    • Liquidity alerts
  • Change, risk and commercial

    Commercial exposure outside the approved budget includes pending change, cost risk, contingency, claims, variations and their combined financial impact.

    • Changes
    • Cost risks
    • Commercial claims
    • Contract variations
    • Commercial exposure
  • Reporting and analytics

    Eighty-five report definitions, ten role-targeted dashboards and advisory functions that explain figures without changing the underlying calculations.

    • Dashboards
    • Reporting
    • Search
    • Advisors
    • Knowledge
    • Documents
    • Data management
  • Administration

    Approval authority defines what may be approved, to what value and which conflicting actions one person may not perform on the same record. The rules are configured, versioned and enforced server-side.

    • Users
    • Roles and assignments
    • Delegations
    • Segregation-of-duties policies
    • Authority limits
    • Organisations
    • Configuration
    • Workflow definitions
    • Audit log
Administration

Administrative exceptions that require attention

The application identifies inactive role assignments, expired delegations and accounting periods left open beyond their intended close date, surfacing them for administrative review.

  • Roles, assignments and segregation-of-duties policies in one place
  • Authority limits by role and by value
  • A platform-operations layer that cannot access organisation financial data
  • Posted transactions are immutable

    Posted transactions cannot be edited. Database controls enforce immutability so a figure remains consistent after posting.

  • Authority is defined by role and value

    Five authority-limit types define what each role may approve and up to what value. Server-side checks enforce those limits at approval time.

  • Segregation of duties prevents self-approval

    Segregation of duties is configured as policy. Prohibited combinations of actions on the same record are defined and enforced.

  • Append-only audit history

    Every approval, change and posting is appended to the audit history. Audit records cannot be amended or removed through the application, including by administrators.

Governed data

Thirty-two datasets with explicit import and export boundaries

All datasets can be exported. Eleven support file import, eight support controlled round-trip exchange, and unavailable operations are reported explicitly.

Three registers are governed through controlled migration rather than direct write: proposed by one authorised user, released by another, and committed only after approval.

Who it is for

Designed for the teams responsible for explaining the financial position

Cost engineers and controllers, quantity surveyors, project-controls and planning teams, forecast analysts, commercial managers, contract administrators, finance teams and programme leadership.

  • Thirty-four roles organised into five groups
  • External roles for client, contractor and auditor
  • Read-only auditor access that does not alter viewed records
Also in BCMS

More of what the application covers

  • Estimate comparison allows two estimates to be compared within the same governed structure
  • Commitment exceptions identify commitments that no longer reconcile with their approved basis
  • Accruals for incurred cost not yet invoiced, maintained separately from posted actuals
  • Contingency drawdown is governed through a distinct approval so reserve usage remains visible and controlled
  • Liquidity alerts assessed against the funding position rather than budget alone
  • Benchmarks derived from completed projects and made available for future estimating
  • Eight advisory functions calculate underlying results deterministically and use language generation only to explain those results. Core calculations remain available when generative AI is disabled.
  • Delegations bounded by time and value, with expired authority surfaced explicitly
  • A platform-operations layer that cannot access an organisation’s financial data
BCMS

Bring one project’s cost report, and the supporting source records.

The demonstration will post the selected figures through the financial chain and show approval authority, decision history and audit changes.