Description

Today it is not possible to batch-send multiple records from Incoming Documents to an existing General Journal batch (e.g. “Sjálfgefið / Default”) unless each document is opened manually and fields like Vendor No., Document Date, or Amount have been filled in first.

When OCR or Document Service is not being used, this makes the Incoming Documents list effectively unusable for companies that simply want to move a stack of scanned invoices into a journal for manual posting.

The system hides the “Send to Journal / Create Journal Lines” action entirely if these fields are not pre-populated, making mass processing impossible.

This forces users to:

• open every single document manually
• fill out required fields one-by-one
• then return to the list and process them

For companies that receive many files per day or week, this becomes a massive productivity problem.

Impact

This limitation makes Incoming Documents impractical for organizations that:

• do not use OCR
• do not use external Document Service
• receive many scanned invoices
• want to manually classify invoices inside the journal later

Incoming Documents should support batch workflows regardless of OCR usage.

Steps to Reproduce (Repro steps)

1. Disable OCR and Document Capture (or use CRONUS IS where OCR is not configured).
2. Go to Incoming Documents.
3. Create or import multiple documents (PDF, image, email, etc.).
4. Select multiple items in the list.
5. Open menu Actions → Incoming Documents.

Observed Result:

The action “Send to Journal / Create Journal Lines” is missing completely.

You cannot batch-process items.

Expected Result:

Batch actions should be available regardless of missing Vendor No., Posting Date, Amount, etc., and the user should be able to send multiple documents directly to a selected journal batch.

Why this matters

1. Incoming Documents becomes unusable without OCR

The current design assumes all documents will be pre-processed by OCR.

Many users do not use OCR for cost, policy, or workflow reasons.

2. Mass processing should not require manual editing

Users should not need to open 30–300 documents individually just to enter placeholder values before batching.

3. General Journal lines can be edited later anyway

The user will review and edit lines in the journal after creation.

BC should not block creation of the journal lines.

4. This breaks standard BC simplicity

BC normally supports mass-processing everywhere else (vendors, purchase lines, journals, etc.).

Incoming Documents should behave the same way.

Proposed Solution

Enable batch “Send to Journal / Create Journal Lines” for Incoming Documents regardless of:

• Vendor No.
• Posting Date
• Amount
• Other OCR-derived fields

Allow BC to create draft journal lines with empty or default values, which can then be manually completed in the journal.

This is consistent with the behavior of other BC modules.