Solutions · Financial services
A close you can hand to the auditor.
Finance Close runs nested functional teams over reconciliation and exception handling, producing structured workbooks and reports where every figure reconciles to its evidence and every exception carries a named decision with a reason.
The workflow.
Nested Pods per functional area, running in parallel where they are independent and sequencing where they are not, with exceptions routed rather than swallowed.
- Ingest and normalise
Ledger extracts, bank statements, subledger feeds and supporting schedules, typed and validated on entry. Anything that fails validation becomes a missing-input wait state, not a silent gap.
- Reconciliation Pods
One Pod per area — cash, receivables, payables, accruals, intercompany, fixed assets. Arithmetic is performed by deterministic nodes, never by the model.
Deterministic - Exception classification
Breaks are classified by cause and materiality, with the supporting evidence attached. Immaterial and explained breaks are cleared with a record; the rest are routed.
- Exception decisions
Each routed break becomes an exception-decision wait state owned by a named person with an SLA. Overrides require a mandatory reason.
Human - Dual approval
Configured high-risk actions require two distinct approvers with segregation of duties enforced by the runtime, not by convention.
Two approvers - Workbook and report artefacts
A structured workbook where every figure carries a link to its reconciliation and its evidence, plus a narrative report drafted from the same records.
Model arithmetic is not used anywhere in this crew. Calculations run in deterministic nodes with the inputs, the formula version and the result recorded. The model reads, classifies, explains and drafts; it does not add up.
Controls the CFO asks about.
| Control | How it is enforced | Evidence produced |
|---|---|---|
| Segregation of duties | Approver roles are distinct from preparer roles; the runtime refuses a second approval from the same identity. | Both approver identities on the record |
| Dual approval on high-risk actions | Configured per action class and per threshold; enforced as a workflow state, not a UI convention. | Two Correction Records, both timestamped |
| Calculation verification | Deterministic nodes with versioned formulas. Model output is never used as a figure. | Inputs, formula version, result |
| Budget enforcement | Hard limits fail closed before spend, per run and per project. | Budget decision recorded on the run |
| No duplicate external actions | Idempotency keys on every Action, with declared compensation behaviour. | Key and outcome per action call |
| Complete cost attribution | Every credit maps to a run, node and outcome unit. Unattributed spend is structurally impossible. | Per-node cost records |
| Immutable audit | Append-only records with configured retention; export is itself an audited event. | Signed export, scoped by period |
MAS Financial Compliance Pack.
Controls mapping, policy packs covering third-party and outsourcing considerations, reconciliation evaluation datasets and reporting dashboards — maintained with a dated currency assertion and a published update cadence.
Control mapping
Platform controls mapped against technology risk and outsourcing expectations, with the gaps stated rather than omitted.
Deterministic policy packs
Materiality thresholds, approval matrices and prohibited-action rules expressed as policy, versioned and evaluated outside the prompt.
Evaluation datasets
Reconciliation and exception cases with expected outcomes, used as the release gate. Extended by your own disputed cases over time.
Dashboards
Close progress, exception ageing, approval latency, cost per close and reviewer agreement, from the same records that drive the audit.
KrewOS is not certified, licensed or endorsed by the Monetary Authority of Singapore or any other regulator. Regulatory obligations remain those of the licensed entity. Read the sector alignment page →
Ask for the controls mapping and the pre-answered questionnaire pack before you book anything.
Request the security pack →- Close cycle
- 6 days from 11
- Group of four entities
- Exceptions auto-cleared
- 61%
- With evidence, not by suppression
- Cost per close
- S$182
- All entities, platform + model
- Unattributed spend
- 0
- Structural, not a target