Getting Started

Sifterra helps you turn incoming business documents into usable records without retyping everything by hand. New users usually need three things first: a clear idea of which documents Sifterra can handle, a simple picture of the workflow, and a fast path into setup and day-to-day processing.

Use this section as a short orientation before you move into setup, analyzer creation, and live processing.

In this section

• Supported documents explains which document types fit Sifterra best and shows common examples.
• Workflow overview walks through the normal queue path from upload through review and completion.
• What you’ll see introduces the main pages and early concepts such as confidence scores.
• First-day path gives new users a practical reading order and a few early details that matter on day one.

What Sifterra does

Most teams use Sifterra to bring incoming files into a document queue, process them automatically, correct anything uncertain, and then create the final Business Central record.

That workflow applies across purchasing, sales, warehouse-style documents, and expense receipts, but the exact finish step depends on the document type you choose.

Recommended reading order

If you are brand new, use this order:

1. Read Supported documents so you know which files are a good fit.
2. Read Workflow overview to understand the normal queue path.
3. Continue to Setup to install the extension and connect the required services.
4. Read Creating document types before you upload live documents.
5. Move on to Field mapping, Processing documents, and Review and approval for daily work.

Quick example

A typical new-user path looks like this:

1. You create a purchase invoice document type for vendor invoices.
2. You upload April Office Supplies Invoice.pdf to the queue.
3. Sifterra reads the supplier name, invoice date, invoice number, total, and lines.
4. One line is highlighted because the confidence score is low.
5. You open the review page, correct that line, and approve the document.
6. Sifterra creates the purchase invoice record and shows its document number in the queue.

That same pattern applies to most document types: bring it in, process it, review only what needs attention, and approve it.