Skip to content
← Blog

From a critical spreadsheet to a calculation API

· 3 min read · Sertoria

A spreadsheet can support bids, projects or purchasing decisions for years. Over time, it accumulates formulas, exceptions and dependencies. Producing results does not prove that its rules are current or that changes can be audited.

A spreadsheet is useful for developing and checking calculations. When other processes depend on it, it needs controls suited to that use. The aim is not automatic replacement. Assess whether you can maintain it with sufficient security and traceability.

Signs to review

  • There is only one person who “understands it,” and their vacations show up in your timelines.
  • Several copies circulate with names like calc_v7_FINAL_good.xlsx, and nobody can say for certain which one was used in that bid back in March.
  • A change in the standards or in a rate forces you to review formulas by hand, cell by cell, with no guarantee that none was missed.
  • Results are copied into other documents by hand — and at some point they have been copied wrong.
  • Nobody can answer “who calculated this, when, and with what data?” without a laborious search.

Any of these signs warrants review. Risk depends on the consequences of an error, not on reaching a fixed number of signs.

What turning it into a service means

A service separates calculation rules from the interface each team uses. An API lets other applications query those rules. The service needs three controls. A spreadsheet can also have them, but those controls require configuration and maintenance.

  • Validated inputs. The service checks types, units, ranges and required fields before calculating. It rejects data that fails the defined rules. It cannot detect every incorrect value that appears valid.
  • Version control. The system records each rule change and the version used for each calculation. Changes to standards need review and tests before another version is published.
  • Traceability. Each run records who requested it, when, which data it used and what result it produced. This record lets a reviewer reconstruct the calculation.

Other tools can connect to the service. A document generator can request a result without manual copying. This removes that transcription step, although the integration also needs tests. This is how the “Expert knowledge as an API” case is built, with the technical memos generated from that same engine.

The path is incremental

You do not need to migrate everything. Select a calculation with a scope you can verify. Compare the service with historical spreadsheet cases and calculation requirements. Review differences: reproducing an old error does not validate the system. Keep the spreadsheet as a reference and backup during the transition. Then assess which other calculations need migration. You can commission that first scope at a fixed price. Our process automation page shows how this approach fits into your operations.

Keep the spreadsheet if its controls meet the requirements. Consider a service when you need shared rules, execution records or integration with other systems.

We can review your case in a free 30-minute call. We then propose a starting point in writing.

Let’s talk