Maker review
The analyst who owns the borrower opens the spread, sees what was extracted, what rules fired, and where the platform wasn't sure. Adjusts and approves.
Financial Spreading Solutions · Financial Spreading
Financial spreading as one workflow.
Public and private financials, multi-year, multi-standard, with the maker/checker review your credit team already runs. Customer-level rules captured the way your analysts apply them, posted into the rest of your credit stack.
What "spreading" means here
Statements in. Standardised lines out.
Spreading means turning a borrower's financial statements (income statement, balance sheet, cash flow, often three to five years of them, often across two accounting standards) into the standardised line items your credit team uses to test ratios, covenants, and risk. The platform extracts the figures, applies your accounting standard, runs the customer-level rules your analysts have built up over time, and posts a clean spread into your credit system. Where the document doesn't match a known template, or where a line item is ambiguous, a Task lands with the analyst who owns the relationship.
The Activity Plan that runs it
Maker and checker, built in.
Statements arrive multi-year · multi-standard
Activity
Intake
classify · version · pull customer rules
Activity
Extract financial fields
multi-year · GAAP · IFRS
Activity
Apply borrower-specific rules
from the Library
Task
Maker review
analyst adjusts · approves · captures rules
Task
Checker approval
senior analyst · same screen, same audit trail
Activity
Post to credit system
spread written to ledger and downstream APIs
Done
Maker/checker is built into the workflow, not bolted on. The audit trail covers both reviews and the steps that ran between them.
Where humans show up
Tasks land with maker, then checker. Judgment stays with the analyst.
Checker approval
A senior analyst signs off. Same screen, same audit trail.
Borrower-level rules
When the analyst makes a borrower-specific adjustment ("Borrower Y reports operating leases under Other Liabilities until 2024"), that adjustment becomes a rule the next quarter's spread picks up.
After the first build
The second use case is largely self-serve.
The Plan you build for one credit unit is the same Plan another unit binds. Borrower-level rules captured by one analyst apply automatically the next time the same borrower's statements come through. The accounting-standard handling (GAAP, IFRS, others) is configured in the Plan once, not per-borrower.
- New borrower at the same credit unit: rules captured at first spread apply to every following statement.
- Second credit unit: bind the existing Plan to the new project; configure inputs.
- New accounting standard: extend the Plan once; every bound project picks it up.
1.5M+
Activities a month, in production
SOC-2
Type II
Maker/Checker
Built into the workflow
Live in production at lending teams in regulated environments.
The platform can't do anything your credit team couldn't do. Same rules, same guardrails, same audit trail.
Mechanics
Want to see how spreading actually composes?
The authoring surface, the runtime, and the captured rules — Knowledge, Workflow, and Studio live on the Product page.
See spreading on your borrowers.
Send us a sample borrower's statements (sanitised is fine) and we'll run the spread end-to-end in a demo.