Skip to main content

Interactive guide

Follow the document from upload to export

Select any step to see what happens, what data is created, and which control keeps the flow safe.

Step 1

Upload

A PDF or DOCX credit agreement is added through the browser or API.

Data created
Original document file and basic upload metadata.
Control
File type, size, and access checks run before processing starts.
If something fails
Invalid or oversized files are rejected so the user can upload a corrected copy.

Data Flow Diagram

This page shows how a loan document moves through Smartflow, from upload to reviewed data and LoanIQ export.


High-Level Flow

Smartflow follows a controlled path:

  1. The user uploads a loan document.
  2. Smartflow ingests and prepares the file.
  3. AI extraction identifies loan fields and evidence.
  4. Confidence scoring routes fields for review.
  5. A human reviewer confirms or corrects the output.
  6. Verified data is prepared for LoanIQ export.
  7. Export status and audit history are recorded.

Detailed Flow

The website version of this page includes a clickable flow. If you are reading the Markdown file directly, use this summary:

  1. Document upload - A PDF or DOCX credit agreement is uploaded through the browser or API.
  2. Document ingestion - Smartflow validates the format, reads scanned pages when needed, and detects document structure.
  3. AI extraction - Loan-specific extraction models identify structured fields and evidence.
  4. Confidence scoring - Each field is scored and routed according to confidence and review rules.
  5. Human review - Operations users review flagged fields and confirm or correct values.
  6. Verification complete - Required fields are checked before export.
  7. Export to LoanIQ - Approved data is mapped into the configured integration payload.
  8. Confirmation - Export status and audit history are recorded.

Data at Each Stage

  • Upload - Creates the original PDF or DOCX record in encrypted document storage. Retention follows your institution policy.
  • Ingestion - Creates OCR text and page structure in the processing cache. Temporary processing data is cleared after extraction.
  • Extraction - Creates structured field values and evidence links in the extraction database.
  • Review - Captures review decisions, corrections, and timestamps in the audit log.
  • Export - Stores the export payload and reconciliation record in export history.
info

All data resides within the bank's infrastructure. No document content is transmitted externally at any stage.


Error Handling

Smartflow keeps errors visible so users can recover without losing the audit trail:

  • Upload errors - The user re-uploads a corrected file when the format or size is invalid.
  • Extraction errors - Processing is retried. Unresolved issues move to manual handling.
  • Export errors - Integration failures stay visible while retry or manual export is completed.