MICROEXTRACT DOCUMENTATION

MicroExtract Getting Started and Quick Start

Start with one representative document workflow, one approved mapping profile and a clear definition of trusted output.

1. Prepare the workflow

Before processing documents, confirm the document type, the fields the business needs, the target output format and the validation or review rules that determine whether the result is acceptable.

  • Use representative source PDFs, not only ideal examples.
  • Identify fields that are mandatory for the business process.
  • Decide whether Excel, XML, JSON or CSV is required by the downstream workflow.
  • Identify which exceptions require a person to review the source.

2. Create or select a workspace

Sign in to the MicroExtract application and select the correct tenant workspace. Free workspaces can be provisioned through the approved self-service flow when that option is enabled for the environment.

Workspace access is tenant scoped. Do not reuse another customer or business unit workspace for unrelated documents.

3. Choose the approved mapping profile and output templates

The current Template Builder workflow uses approved mapping profiles and validates the selected output templates before a document can be processed. Select only the output formats the workflow actually needs.

Template validation is separate from document extraction. A template must pass its format checks before it becomes the active revision for the job.

4. Upload and process a source PDF

Upload the source PDF, confirm the validated template revision and start processing. Live status shows progress, elapsed time, pages and confidence information while the job runs.

Processing can finish as completed, review required or failed. A review state is not treated as a silent success.

5. Review confidence and validation results

Confidence is a review signal, not a business approval. Use it together with completeness, deterministic validation and review reasons. When the current release exposes field-level confidence or Accuracy Coach guidance, use those signals to find the values that deserve attention first.

6. Download the approved outputs

When output generation completes, download only the selected customer formats. MicroExtract can produce approved Excel, XML, JSON and CSV outputs where the workspace plan and template allow them.

Keep the source file, job reference and review decision traceable when the output is used downstream.

7. Understand usage and plan limits

Usage is page based and plan limits are enforced server side. Current launch plans are Free, Pro, Business and Enterprise. The live pricing page is the source for current commercial pricing and allowances.

Do not rely on a locally saved price sheet when the public pricing page or approved commercial source has been updated.

Need help with a real document workflow?

Use representative samples, define the required output and validation rules, then test before production use.

First Extraction: Preparation and Acceptance

Before uploading, decide what the output must contain and who will approve it. This keeps the first processing run focused on a real business result.

Before the first upload

Choose the correct authorised workspace. Confirm that the source document may be processed under your organisation's policies. Use synthetic or properly redacted material for early evaluation.

Write down required fields, expected rows, desired output format and the business rules that would stop downstream use.

During processing

Choose an approved mapping and validate the selected output templates. Confirm actual account limits in the application. A locally saved plan table may be outdated.

Record the job reference. A submitted or queued job is not a completed extraction; a completed extraction is not necessarily a business approval.

Before using the export

Compare the required values and tables with the source. Check identifiers, date meanings, currency, units and page-spanning rows. Resolve or escalate the stated review reasons.

Record the reviewer decision and keep traceability. Do not repeat a submission merely because an email or a screen update is delayed; first inspect the existing job status.

Acceptance checklist

  • The correct workspace, source and template revision are recorded.
  • Mandatory fields and expected rows have been checked.
  • Unresolved exceptions remain visible.
  • Only permitted output formats are downloaded.
  • The receiving process accepts the reviewed format.