From Spreadsheets to Scalable Decisions with QBO Scoring

Every financial services operation has a few spreadsheets it can’t live without. A pricing model, a loss-mitigation waterfall, an eligibility calculator, a net present value analysis. The formulas have been refined over years and reviewed by the people who understand the business best. They’re trusted.

They’re also fragile. The model lives in one file on one drive. Someone copies data in by hand, reads the answer out, and keys it somewhere else. Copies drift, and when an auditor asks which version produced a decision six months ago, the honest answer is often “probably this one.”

QBO scoring is built to keep the model and lose the fragility.

Keep the formulas, change where they run

A score in QBO is a named set of data points calculated for a record and saved with it. A score template defines what to calculate; its engine decides how. One of those engines is Excel.

With the Excel engine, your workbook stays the source of the logic. You don’t rewrite its formulas in another language. Instead, you name the cells that take input and the cells that hold results:

• Inputs are injected into named cells from the record being scored, from a query, or from parameters passed on the call. A named cell can even receive the best-matching output of a rules matrix.
• The workbook recalculates exactly as it would on a desktop.
• Results are read back from named cells, one per score item, plus an overall score value and, optionally, a confidence for each item.

QBO then saves the completed workbook with the score, so the exact inputs and outputs behind every result are preserved.

What teams gain

Consistency. The model becomes a service that every workflow, form, and API call uses, always at the current version. Every decision follows the same business logic, whether it was triggered by an import, a workflow step, or a person.

Transparency. Each score is stored on the record with typed values, so it can be filtered, sorted, and reported on. Because the completed workbook is saved alongside it, you can show exactly how a given number was produced.

Efficiency. Scoring runs on demand inside the process, with no copy-and-paste in either direction. Workflows branch on the result, documents merge it into letters and reports, and reports analyze it across records.

More than spreadsheets

Excel is one engine among several. The same score template structure works with rules matrices, SQL queries, XSLT transforms, text-parsing patterns, and AI engines that extract values from documents with a confidence for each one. A composite engine can run several and keep the most confident answer for each item. Choosing the engine that matches where your logic already lives means you can bring existing models in without starting over.

From one file to enterprise automation

What once lived in a single file can now drive decisions across the operation, with the governance and audit trail regulated work requires. Read how scoring works in QBO, including Excel models, or see where it fits in QBO’s data and insight capabilities.