liveBook · Manning

Money calculation

As explained in Software Architecture Decision-Making

A financial calculation is a computation that determines monetary amounts, prices, balances, charges, or other financially significant values.

Money calculation is a high-consequence architectural concern. Compromise may be acceptable around interfaces or workflows, but price and charge calculations demand stronger rigor because failures can cause financial loss, data corruption, or difficult-to-reverse outcomes. section 3.5

Calibrate rigor against the consequences of failure:

  • Protect calculation correctness, data integrity, audit trails, access control, and reconciliation with financial systems. section 3.5
  • Allow more flexibility in user interfaces, reporting screens, and internal approval workflows when their failures remain contained and reversible. section 3.5
  • Increase rigor when failures are hard to detect, difficult to reverse, or capable of affecting money, compliance, customers, or core operations. section 3.5
Table 3.5 Decision rigor rubric
Factor
Lower rigor may be acceptable when...
Higher rigor is justified when...
Reversibility
The decision can be changed, rolled back, or replaced without major disruption.
The decision is hard to reverse once data, users, integrations, or operational processes depend on it.
Detectability
Failure is visible quickly through tests, monitoring, user feedback, or operational signals.
Failure can remain hidden, appear later, or silently corrupt data, calculations, permissions, or business outcomes.
Blast radius
Failure affects a small internal group, a temporary workflow, or a non-critical capability.
Failure affects customers, money, safety, compliance, sensitive data, or core operations.
Cost of failure
The consequence is inconvenience, rework, delay, or local operational pain.
The consequence is legal exposure, financial loss, security breach, regulatory failure, physical harm, or major reputational damage.
Recovery
The team can recover through rollback, retry, correction, or a known manual process.
Recovery requires coordinated incident response, data repair, customer communication, regulatory reporting, or complex restoration.

Use the decision-rigor rubric to assess calculation choices by reversibility, detectability, blast radius, and cost of failure. section 3.5

How Software Architecture Decision-Making covers it

How deep it goes
Frames rigor through consequences, reversibility, detectability, blast radius, and cost of failure without specifying implementation techniques.
Examples
Uses internal pricing or billing support, including price calculation and reconciliation with financial systems.
What it assumes
Assumes risk assessment and distinguishes reversible inconvenience from financial loss, legal exposure, or data corruption.
What you can do after
Evaluate which calculation-related decisions require exceptional rigor instead of applying uniform perfection across a system.
How it connects
Connects money calculation to pricing, billing, data integrity, audit trails, access control, regulatory compliance, and reconciliation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.