Skip to main content
Applications move through a defined lifecycle from creation to final decision. Each stage determines which actions you can take on the application.

​
Lifecycle states

An underwriting application typically moves through the following states as defined in the UnderwritingApplicationStatus enum:

​
Created

The application has been created but hasn’t been submitted for underwriting review.
  • You can create the application with partial or complete data
  • Underwriting hasn’t evaluated it yet
  • You can update it freely using updateUnderwritingApplication
ScenarioBen creates an application for his mechanical keyboard business with basic business information but is still finalizing which business partner to include as a stakeholder. The application remains in Created status while he gathers this information.

​
Submitted

The application has been submitted and queued for automated underwriting processing.
  • Tesouro validates required fields at submission time
  • Automated and manual underwriting review begins
  • You can no longer update the application

​
Processing

Automated checks and decision components are run on the application.
  • Automated verification includes identity verification, TIN match, bank account verification, and other system-driven checks
  • No manual review is needed during this state
  • Applications stay in Processing until automated checks complete
If automated checks surface discrepancies or risk concerns, the application transitions to Pending for manual review.
Most applications that pass automated verification will transition directly from Processing to Decisioned without requiring manual review.

​
Pending

Manual underwriting review is required.
  • Automated processing flagged a discrepancy, missing data, or risk concern that needs human review
  • Underwriters can create one or more information requests while the application stays in Pending
  • Each information request moves independently through Requested and Fulfilled statuses
ScenarioBen’s address doesn’t match the credit bureau’s records. The application moves to Pending, and an underwriter creates an information request asking for proof of his current address.

​
Decisioned

Underwriting has reached a final outcome for the application. Final outcomes are:
  • Approved – The application meets underwriting requirements
  • Declined – The application doesn’t meet underwriting requirements
  • Withdrawn – The application was withdrawn before a final decision
Final application status is communicated via API responses and webhook events. For a complete list of all application statuses, see UnderwritingApplicationStatus.

​
Status transitions

Applications move forward through the lifecycle:
  • Created → Submitted
  • Submitted → Processing
  • Processing → Pending (if manual review is required)
  • Processing → Decisioned (if automated checks pass)
  • Pending → Decisioned
Timing depends on how complete the application is and what underwriting requires. While an application is in Pending, underwriters can create information requests. These don’t change the application status.

​
Typical flow diagram

Created → Submitted → Processing → Pending → Decisioned Processing can skip Pending and go straight to Decisioned if automated checks pass.

​
Status visibility

Query the current status using the underwritingApplications query and accessing the applicationStatus field on the UnderwritingApplication type.