Private Beta

Audit-ready
trade files.

Transform messy trade documents into structured, traceable files. Every field extracted. Every decision logged. Every exception searchable.

Letters of Credit Bills of Lading Commercial Invoices Packing Lists Certificates

Trade runs on PDFs.
Risk hides in the details.

Teams spend hours re-keying fields, reconciling mismatches, and chasing missing pages. When auditors ask questions, there's no trace of what was reviewed or why exceptions were approved.

Before

Manual intake, unclear packets

Mixed scans, duplicates, version confusion. Teams reconstruct the packet before they can even start review.

During

Re-keying, reconciliation, exceptions

Small inconsistencies across LC terms, invoice, and transport docs create delays and disputes. Decision context lives in Slack.

After

Audit pressure, zero traceability

When questions come later, it's hard to prove what was reviewed, what was flagged, and what was decided.

Standardize the packet.
Review the exceptions.

LUCAS creates a consistent trade file from messy inputs, extracts fields with source traceability, and highlights mismatches for human review.

Case Preview LC-2025-0312
Document Packet ✓ Complete

LC, invoice, B/L, packing list, certificate of origin grouped into one case.

Extracted Fields 27 fields
amount beneficiary ports dates incoterms
Exceptions 2 flagged

Port name mismatch detected. Similar precedent found from May 2024.

01

Ingest

Upload scans and PDFs. We classify, split, and group documents into cases automatically.

02

Extract

Key fields are captured with links back to source pages for instant verification.

03

Compare

Cross-reference LC terms against invoice, B/L, and certificates. Flag discrepancies for review.

04

Export

Generate an audit-ready decision pack plus structured data for downstream systems.

Not just what happened.
Why it was allowed.

Every approval, exception, and override is logged with full context. Turn precedent into searchable institutional knowledge instead of losing it in Slack.



The context graph: a queryable record of how decisions were made—what signals were consulted, what policy applied, who approved, and what action was taken.

Decision Trace Searchable
⚠️
Port name mismatch detected
Doc: "Jebel Ali" · LC: "Dubai Port"
📋
Precedent found
LC-2024-892 · Same issue · Accepted
Exception approved
jane.smith@ · Policy v2.3 · 14:32 UTC

One standardized file.
Two exports.

A human-friendly decision pack for review, plus structured data for downstream workflows and systems.

Audit-ready decision pack

PDF
  • Cover sheet with key fields and document checklist
  • Exceptions list with reviewer notes and sign-off
  • Source references for fast verification
  • Complete activity log for audit trail

Structured data export

API · JSON · CSV

Machine-readable output for your existing systems.

lc_number
amount
beneficiary
shipment_date
ports[]
exceptions[]

Built for accountability.

The point is not magic. It's a standardized workflow, traceable extraction, and clear human sign-off.

Traceability

Every field links back to its source page for instant verification.

Activity log

Reviews, notes, edits, approvals, and exports are timestamped and recorded.

Role separation

Uploader, reviewer, approver, and auditor paths can be separated.

Exception workflow

Discrepancies are reviewed, edited, and signed off by humans—not auto-decided.

Request a pilot.

Share a sample packet type and your review flow. We'll show you what structured output looks like.