Business history

When a borrower submits multiple bank statements over time, their financial data is spread across separate Books. This makes it difficult to understand the complete financial picture.

🚧

This feature is in beta!

This page discusses functionality that is in beta. You may occasionally experience unannounced changes or bugs. We'd greatly appreciate your feedback on this feature and its accompanying documentation.

Business History feature bring this data together into a single, unified view. They allow you to analyze a business’s cash flow and transaction history across all submissions your organization has processed, instead of reviewing each application in isolation. This supports better underwriting decisions by enabling analysis of trends over time rather than relying on a single snapshot of application at a time.

📘

Availability

This feature is currently available via API and will be added to the Ocrolus Dashboard in a future release.

It helps underwriters understand:

• Visibility into cash flow across all submitted statements
• Understanding of changes in financial behavior over time
• Number of times the business has applied for financing across the Ocrolus network

Key benefits

This feature has the following capabilities:

• Unified financial view: Access revenue, expenses, balances, and transactions across all Books in a single API call, without manual reconciliation.
• Deduplicated transaction data: Transactions appearing in multiple Books are deduplicated to ensure accurate totals without double-counting.
• Loan inquiry velocity: View how often a business has applied for financing across the Ocrolus network, segmented into rolling time windows (30, 60, 90, 180, 270, and 365 days). This provides a quick indicator of potential stacking activity.

Usage scenarios

This feature is useful when:

• A borrower has submitted multiple Books and a combined view is required.
• Analysis is needed at the business level rather than per application.
• Preparing a credit memo with longitudinal cash flow data.
• Syncing only newly ingested transactions to downstream systems.

API workflow

Use the Business Identifier endpoint to retrieve the business_id, which is required for all other Business History endpoints. To learn more, see the access the business history of your borrower recipe. It helps you understand the end-to-end workflow, from resolving a book_uuid to accessing transactions, summaries, and risk signals.

📘

Scope and data considerations

• Transactions and summaries are scoped to Books submitted by your organization.
• Loan inquiry data is cross-organization (market-wide) but is computed relative to the latest Book your organization has submitted for that business