Control scheduleRef 05Mitchell Finance & Technology Ltd

Delivery controls

The standards we apply to our own work, set out so you can check them.

Scope and acceptance

Every phase starts with written scope and acceptance criteria. For calculations, acceptance criteria include worked examples supplied or approved by your finance team, which become automated tests.

Calculation integrity

ArithmeticDecimal arithmetic for money, never floating point.
RoundingA single documented rounding rule, applied in one place.
CurrencyAmounts stored with their currency; conversion rates stored with their source and time.
TestsEvery rule covered by tests using your worked examples.

Audit trail

Records of who did what, when, and from which role. Approval steps record both the request and the decision. Audit records cannot be edited by ordinary users.

Access and security basics

Least-privilege roles, two-factor sign-in for staff, separate test and live environments, secrets outside the codebase, encrypted connections, dependency patching. For higher-risk systems we recommend independent penetration testing and help you act on its findings.

Cadence and visibility

Working demonstrations every two weeks. A shared decision log. You can stop after any stage with working code in your own repository.

Handover

An operating guide, architecture outline, data map of personal data, runbooks for routine tasks, and a list of known limitations.

Note. These controls describe our working practice. They do not replace your own regulatory obligations, which remain with your firm.