LensReading which lens this session carries.
Every coverage statement

Function coverage

Finance

The platform observes 70.0% of the 12,480 items a week in scope here, reconstructs 20.0%, and estimates that 1,248 happen where it cannot read them.

The method behind this statement

Source system count · owned by Chief Financial Officer · Function head

Observed is the count the source systems return.

Observed comes straight from what the connected systems return. The remainder is split between what the platform can reconstruct and what it is told exists.

What is happening in the unseen share

Close adjustments prepared in workbooks and posted as a single journal.

Who has signed for it

Nobody. This figure rests on its method alone.

An attestation would not turn an estimate into a measurement.

Work filed here that the platform could not see

3 items have been filed by somebody who did the work off-platform.

Manual close adjustments, July periodDeclared · accepted
IN-0002 · Nils Andersen · Finance · period close
Controller checklist tasks for the July closeStructured claim · accepted
IN-0019 · Nils Andersen · Finance · period close
Tax question answered on a callRecalled · pending
IN-0021 · Fabien Aubert · Finance · indirect tax

Gaps raised against this function

2 gaps in a chain that something must have filled.

Sub-ledger closed → Group consolidation openedConfirmed by a filing · strong

Close adjustments are being prepared in a workbook and posted as one entry.

SP-0004 · 3 instances · median gap 26.0 hours
Payment proposed → Payment releasedBlocked · strong

Payment release is happening in the bank’s own portal because the gateway has never been connected.

SP-0016 · 12 instances · median gap 8.0 hours

What this statement is, and what it is not

Coverage can only ever be estimated from the outside.

A coverage statement is disputable by design.

Compare against every other statement