Skip to content
Our workFinanceApplication briefing

WIP, GRNI & Month-End Journals

From project data and cut-off rules to a controlled, traceable close.

Workflow illustration

Workflow illustration, not real projects or values. Accounting data by project and the period rules meet in a period check: each project is validated for completeness and every item is placed against the cut-off, so an item arriving after cut-off is flagged as late and its impact is raised for finance. Valuations, applications and GRNI or accrual lists feed the classification of items as work in progress, goods received not invoiced or accruals. Current-month and cumulative positions are calculated for each project, and journal instructions are prepared with reasons and project references. Finance reviews and approves, and the period is snapshotted and locked with an audit trail so closed positions do not change silently.

People stay in control

Allocation rules, period definitions and approval logic are governed. Finance reviews and approves before the period is locked, final journal posting remains an accountable finance decision and closed periods never change silently.

The challenge

At month end, project businesses often reconcile valuations, customer applications, invoiced values, costs and accruals across spreadsheets. Two positions need particular care: work in progress (WIP), the value of work carried out but not yet invoiced, and goods received not invoiced (GRNI), goods or services received before the supplier's invoice arrives. Cut-off decisions, late items and adjustments are then hard to reproduce or explain later.

What we built

The application makes project month-end a controlled allocation workflow. It combines accounting data with quantity surveying or project inputs, validates completeness and period alignment, classifies WIP, GRNI and accrual items, calculates current-month and cumulative positions and produces journal instructions with reasons and project references. Final periods can be snapshotted and locked so closed positions do not silently change.

The month-end workflow within a completed finance operations application.

What it connects

  • Accounting data by project
  • Internal valuations and external applications
  • GRNI and accrual lists and notes
  • Period rules, definitions and approval logic

The difference it makes

  • The same period rules, classifications and approval logic apply every month, instead of the close being rebuilt across spreadsheets.
  • Journal instructions carry reasons and project references, so finance can trace how each position was reached.
  • Late items and cut-off issues that affect the period are flagged rather than lost in reconciliation.
  • Approved periods are snapshotted and locked, preserving the decision history behind the close.

Business profile

Team
Finance
Workflow
Project month-end close

A reproducible project close with traceable adjustments, visible late items and locked, auditable periods.

Inputs and outputs

Inputs

  • Accounting data by project
  • Internal valuations and external applications
  • GRNI and accrual lists and notes
  • Period rules, definitions and approval logic

Outputs

  • Per-project allocation records
  • WIP and GRNI movements
  • Journal instruction pack
  • Period lock record and audit trail
  • Late-item impact flags