April 2026
Release Notes
In this release, we introduced Business History APIs to calculate business cash flow analytics, added Authenticity Status in Ocrolus Detect to simplify document integrity evaluation, added support for shared Book labels in Encore, introduced new analytics update webhook events, and expanded Classify and Classify + Capture document support.
What's new?
SMB
Business history APIs
We’ve introduced business history APIs, a new set of endpoints that provide a unified, business-level view of financial data across all Books submitted by your organization.
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.
AvailabilityThis feature is currently available via API and will be added to the Ocrolus Dashboard in a future release.
Instead of manually combining data from multiple applications, you can now retrieve deduplicated transaction history, longitudinal cash flow metrics, and business metadata through API calls. These endpoints enable underwriters and risk teams to evaluate borrower behavior over time, rather than relying on a single application snapshot.
APIs
- Business identifier [GET]
/v2/book/{book_uuid}/business: Resolves abook_uuidto its associated business entity and returns abusiness_idthat can be cached and used with all other business-scoped endpoints. - Business overview [GET]
/v1/businesses/{business_id}: Retrieves the full metadata profile for a business entity, including industry classification, loan inquiry history, and addresses derived from bank account holder information. - Business transactions [GET]
/v1/businesses/{business_id}/transactions: Retrieves paginated, deduplicated enriched transactions across all of the requesting org's Books for a given business. - Business summary [GET]
/v1/businesses/{business_id}/summary: Retrieves the chronological financial summary for a business entity, computed from deduplicated, org-enriched transactions across all of the requesting org's Books.
Key highlights
Business History APIs provide a unified borrower view across all submissions, with deduplicated transactions to prevent double-counting. They enable longitudinal cash flow analysis for better underwriting decisions, support incremental data sync using updated_since, and include loan inquiry velocity to help identify potential stacking risk early.
To learn more, see the business history API documentation and recipe.
Detect
Enhanced Ocrolus Detect with Authenticity Status for document integrity assessment
We’ve introduced Authenticity Status, a new categorical outcome that helps you quickly interpret document integrity results while continuing to use the existing Authenticity Score (0–100).
Authenticity Status works alongside the Authenticity Score and uses the same underlying detection signals. It provides a clear, policy-friendly result that helps fraud analysts, underwriters, and operations teams quickly assess document risk and route documents for approval, review, or escalation while preserving the detailed signals needed for automation and risk workflows.
Key highlights:
- Dual outputs: Detect now returns both an Authenticity Score (0–100) and an Authenticity Status.
- Operational clarity: Authenticity Status provides a clear categorical result for routing and review workflows.
- Flexible configuration: You can configure ternary mode (High, Medium, Low) or binary mode (High, Low) depending on their workflow needs.
- Explainability: Results include reason codes, structured fraud flags, and supporting evidence to help reviewers understand why a document was flagged.
- Consistent availability: Authenticity Status results are available in both the Ocrolus dashboard and API responses.
For details, see the Authenticity Status guide.
Classify and Capture
New Classify and Capture supported documents
The Classify and Capture supports are enabled for the following newly onboarded document:
Legal
To learn more, see the All Supported Documents page.
Webhook
Analytics update events
We have introduced the following webhook events to help you keep your cached analytics in sync with Ocrolus:
analytics.config_updated: It is an organization-level event. It triggeres when analytics configuration changes such as tag updates or revenue formula changes. It indicates that cached analytics for all Books in the org may be need to be refreshed to get the latest data.book.analytics_v2.updated: It is account-level event. It triggers when transaction tag overrides modify analytics for a specific Book. It indicates that cached analytics for that Book should be refreshed.
These events act as signals (not data payloads) and enable near real-time refresh of analytics using the Analytics APIs. To learn more, see the Org-level webhook and Account-level webhook pages..
Enhancements
SMB
Encore - shared Book label usage
Encore now treats every copy job request with a new shared Book label (Deal ID) as a new parent copy job and creates a distinct Ocrolus Book for the receiver upon acceptance. Subsequent requests using the same shared Book label are treated as child copy jobs, appending documents to the existing parent job and receiver Book instead of creating a new one.
This update supports renewal and re-engagement workflows, where a new Deal ID always produces a new receiver Book, as well as application update workflows, where brokers can reshare additional or missing documents under the same Deal ID without creating duplicate Books.
The List Copy Jobs API reflects this structure by representing each unique shared Book label as a parent copy job, with associated child jobs and their document UUIDs included in the response.
To learn more, see the Sender's guide.
Classify
New Classify supported document
The Classify supports are enabled for the following newly onboarded document:
Mortgage-specific forms
- RD 1924-19 - Builder's Warranty
- RD 1924-25 - Plan Certification
- RD 1980-11 - Guaranteed Rural Housing Lender Record Change
- RD 400-1 - Equal Opportunity Agreement
- RD 400-6 - Compliance Statement
- Undisclosed Debt Monitoring (UDM) Details Report
Property
- Condo Project Advisor Feedback Certificate
- Property/Plat Survey
To learn more, see the All Supported Documents page.
Classify and Capture
Additional attribute support
Ocrolus now offers support for the following attribute within the existing document type:
divorce_decree-Part2-DateAndAmount:isPlaintiffPayerOrReceiverOfSpousalMaintenancedivorce_decree-Part2-DateAndAmount:spousalMaintenancePaymentFrequencydivorce_decree-Part2-DateAndAmount:isPlaintiffPayerOrReceiverOfChildSupportdivorce_decree-Part2-DateAndAmount:childSupportPaymentFrequency
To learn more, see the All supported documents page.