Skip to main content
Underwriting applications on the Tesouro platform progress through a defined lifecycle from initial creation to final decision. Each stage represents a distinct phase in the underwriting process and determines which actions are permitted on the application. Understanding the application lifecycle helps developers know when an application can be updated, when automated or manual underwriting occurs, and when a final decision is reached.

​
Lifecycle states

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

​
Created

The application has been created but has not yet been submitted for underwriting review.
  • The application can be created with partial or complete data
  • The application is not yet evaluated by underwriting
  • Updates can be made 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.
  • Required fields are validated at submission time
  • Automated and manual underwriting review may begin
  • The application can no longer be freely updated

​
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 underwriting action is required during this state
  • Applications remain in Processing until automated checks complete
If discrepancies or risk concerns are identified during automated checks, the application transitions to Pending for manual underwriting review.
Most applications that pass automated verification will transition directly from Processing to Decisioned without requiring manual review.

​
Pending

Manual underwriting review is required.
  • The application is flagged for human review due to a discrepancy, missing data, or risk concern identified during automated processing
  • Underwriters may create one or more information requests while the application remains in Pending
  • Each information request progresses independently through Requested and Fulfilled statuses
ScenarioDuring automated processing, the system detects that Ben’s address doesn’t match the address on file with the credit bureau. The application moves to Pending status, 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 does not meet underwriting requirements
  • Withdrawn – The application has been 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 generally move forward through the lifecycle, but certain transitions may occur based on underwriting actions:
  • Created → Submitted
  • Submitted → Processing
  • Processing → Pending (if manual review is required)
  • Processing → Decisioned (if automated checks pass)
  • Pending → Decisioned
The exact sequence and timing of transitions may vary depending on the completeness of the application and underwriting requirements. While an application is in Pending, underwriting may create information requests. These do not change the application status.

​
Typical flow diagram

Created → Submitted → Processing → Pending → Decisioned Processing can also transition directly 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.