Review an underwriting result

Use Origination to review the underwriting your integration submits to Insights. Each record brings together the application inputs, processing state, risk package, documents and connected sources.

​

Find and open an origination

Open Origination in the left navigation. Use the status views, filters and search to locate the borrower or request. Check the selected workspace and environment before searching for an identifier from your application. Select a row to open its drawer. Confirm the borrower, origination identifier and environment in the header. The arrows move between records in the list; closing the drawer returns you to the table. Copy record ID helps you correlate the case with your own system or a support request.

​

Overview

Start here for a readable review of the result. The summary identifies the borrower, product, requested amount and risk policy when supplied. Scroll through the drawer to inspect:

• Risk package: the available underwriting result and its supporting dimensions. Expand nested sections to read their values, coverage and qualifications.
• Request information and Underwriting inputs: the application facts used for this run, such as requested financing and declared business information.
• Borrower information: the subject of the assessment and its recorded attributes.
• Published evidence and Activity: associated published records and recorded activity when available. Open an evidence row for further detail.

For example, review Evergreen Outdoor Supply’s requested amount alongside its policy result, then compare the declared application information with the evidence used. A missing risk package means there is no published result to review here; it is not a decline. An absent metric is not zero.

​

API request

Use this tab when investigating unexpected results or checking what your integration submitted. Inspect the captured payload for the borrower, application facts, document and connection identifiers, and lending-product and risk-policy version references. Captured record metadata can surround the submitted inputs. In this example, those inputs are under submitted_request. Do not use the entire displayed record as a new POST request: use Data Lookup to check the endpoint’s request fields and required structure. Use the copy control or Download JSON to inspect the payload locally. Related API requests lists linked request logs when available. If that list is empty, search Request logs using the identifiers you have; an empty relationship list does not prove that no request was sent. Opening or downloading the captured request does not submit it again.

​

API response

Use this tab to understand the returned origination record and compare it with your application’s handling of the result. Check the resource identifier, processing status, timestamps and record_version. Inspect failure or requirements when present, and follow the risk_package_id to the published result. The response can contain a reference to the risk package rather than the full package inline. Use Overview for the readable result and the risk package contract for programmatic retrieval. Copy or download the JSON to compare the fields with Data Lookup. For the original HTTP status and timing, open the corresponding request log. An accepted asynchronous request is not yet a completed assessment; a completed assessment is not necessarily a within-policy recommendation.

​

Documents

Use this tab to find the files associated with this origination. The table includes File, Type, Size, Status and Added (UTC). Search for a file or identifier and select its row to inspect the available metadata. Check the file’s identity and status before relying on it. A dash means metadata is not supplied in that view. A file being listed does not mean every verification check passed or every required document is present. In the file details, Download original file is available when an authorized download is provided. Download unavailable means there is no usable download for that record at that time. This is a read-only evidence view; submit or associate additional documents through your integration. See documents and evidence for the wider evidence workflow.

​

Integrations

Use this tab to identify the borrower connections associated with the origination, such as banking, payments, commerce or accounting sources. These are case-linked connections, not the catalog of providers enabled in your Integrations Hub. The table shows Integration, Provider, Status, Frequency and Last sync, where recorded. Select a row for its readable details and available source information. Owners and Developers can also inspect captured technical payloads when present. Check connection status and the available sync timestamps when a result has incomplete or stale evidence. A Connected status describes the connection; it does not guarantee that all expected data was retrieved. Missing frequency or sync information is not proof of a failed or successful refresh. Compare the connection with the risk package’s coverage and supporting evidence.

​

Interpret processing and recommendation separately

The risk package is decision support. Your institution owns the final lending decision. To investigate a case, compare Overview with the captured inputs, then check its documents, connections and request logs. Opening the drawer does not edit the application or rerun underwriting; submit corrections through the documented API workflow. Continue with underwriting dimensions or follow an enrolled deal in Portfolio.