Automatic Processing Flow

Here is a common setup:

• SharePoint scan runs every 15 minutes.
• Document processing runs every 5 minutes.

Typical flow

1. A file is placed in an analyzer’s SharePoint Download folder.
2. The next SharePoint scan finds it and creates a new document queue entry with status Pending.
3. The next processing run picks up that Pending entry.
4. If file movement is enabled, the file moves to In Review.
5. Sifterra extracts values, applies mappings, and checks confidence and validation rules.
6. If the document qualifies for automatic creation, Sifterra creates the Business Central document and marks the queue entry Completed.
7. If SharePoint file movement is enabled, the file moves to Archive.
8. If deletion after archive is enabled, the archived file is deleted.

If the document needs a person to check it first, the queue entry changes to Review Required instead of completing automatically.

Recommended schedule

For most teams:

• SharePoint scan: every 15 minutes
• Document processing: every 5 minutes

That stagger keeps the queue moving without making both jobs compete on the same interval.

If your volume is low, longer intervals are fine. If your volume is high, shorten the intervals carefully and monitor the results.

Practical setup checklist

• Confirm manual processing works before turning on schedules.
• Leave both Job Queue entries on On Hold until setup is complete.
• Turn the SharePoint scan to Ready.
• Turn the processing job to Ready.
• Upload or drop in a test document.
• Confirm it appears in the document queue.
• Confirm it either completes automatically or clearly shows Review Required or Error.
• Check the Processing Log if anything stops unexpectedly.