Choose the output

Supported output contracts include structured CSV, JSON/JSON Lines, metadata sidecars and ZIP packages. Preserve document/version/run/schema identities and available provenance so recipients can trace a result.

Cleared originals, approved processed/redacted copies and rendered page images are separate selections. Originals can expose unredacted information. A saved data-only configuration does not silently include source files.

Local product example · sample dataClick to enlarge ↗
Choose release rules and a delivery route

Set which documents are eligible, then choose browser download, authenticated API pull or a configured push destination. Manual delivery requires a preview. Automatic delivery depends on deployment support and release conditions; saving settings alone does not prove a transfer occurred.

Prepare a destination

An authorised administrator configures and tests the supported destination. SFTP requires the SSH host/port, account, pinned host-key fingerprint and an existing absolute directory visible to that account. Website-relative paths and FTP credentials are not interchangeable with SFTP settings.

S3 connections use their supported role, External ID, bucket-owner and approved-prefix controls. Put credentials in the protected connection workflow or approved secret store, never an article, chat or query string. Material connection changes require re-verification.

Preview and transfer

  1. Select the eligible job/output and required data mappings, file options and transfer-batch size.
  2. Create a fresh preview and inspect its document membership, destination, sensitive-file options and limits. Changed sources or settings require a new preview.
  3. Resolve review, indexing, QC, approval or connection blockers reported before release.
  4. Submit the permitted transfer action and monitor Delivery operations for queued, held, retrying, failed or storage-confirmed states.
  5. Inspect the receipt and verify the receiving system can unpack and use the output. A ZIP must be extracted if individual files are required.
Local product example · sample dataClick to enlarge ↗
Map extracted fields to the receiving system

The sample maps invoice_reference to invoice_id and invoice_total to amount, with fictional Finance metadata. Select the sidecar format and whether processing information or source evidence belongs in the package. Preview the manifest and check the receiver’s requirements before creating it.

Read the receipt honestly

A connection test alone does not prove write permission. A storage-confirmed receipt establishes its defined transport/storage checks, not downstream customer ingestion or business acceptance.

Inspect attempts before retrying a failed/uncertain transfer. Successful effects must not be duplicated. Automatic schedules require the relevant tenant policy and worker configuration.

Reconcile the receiving contract

  1. Agree field names, format, encoding and file/package selections with the receiver.
  2. Inspect transfer membership, destination, attempts and receipt.
  3. Confirm source/output versions match the approved preview.
  4. Verify the receiving team can unpack/read the package; report downstream ingestion separately from transport failure.