Reviewing Belege in the review queue

The finance review queue is where you find Belege (receipt/expense documents) that are waiting for attention and act on them. This article shows how to filter the queue, read its warning and blocker counts, review a single Beleg, and run bulk actions. Viewing the queue requires the belege:view permission; acting on items requires belege:transition.

Opening and filtering the review queue

The review queue lists Belege with summary information and lets you narrow the list by several dimensions:

• Status — e.g. Submitted, In Review, Approved.
• Beleg type — for example fuel, service, or another configured type.
• Vehicle or driver, or the unassigned vehicle / unassigned driver flags to surface receipts that are missing a link.
• Cost center (Kostenstelle) referenced by any line item.
• Has warning and has blocker — show only Belege that currently carry unresolved rule outcomes.

Results are ordered by Beleg date (newest first) and then by creation time. The queue is paginated; each page returns up to 100 items.

Reading the queue columns

Each row summarizes one Beleg: its type, status, Beleg date, linked vehicle and driver, line-item count, total gross amount, and two governance counters — warning count and blocker count. These counters only include rule outcomes that have not been overridden, so a row's badges reflect what still needs resolving. Flags also mark a missing vehicle or missing driver.

Above the list, a summary shows the total number of matching Belege, how many carry at least one warning, and how many carry at least one blocker — a quick read on the health of the current filter.

Reviewing a single Beleg

Open a Beleg from the queue to see its header, line items, and rule outcomes, then drive it through the workflow:

1. From Submitted, move the Beleg to In Review to pick it up. Blocking rule outcomes (for example a missing cost center or tax rate) must be resolved first.
2. While In Review, resolve any data problems, override warnings where justified, or apply a financial correction.
3. Finish the review by choosing Approve, Reject, or Request clarification. A clarification request requires a note.

Tip: Use the has blocker filter to clear hard stops first, then the has warning filter to work through items that need a judgement call before approval.

Acting on several Belege at once

Bulk actions let you apply the same transition to multiple selected Belege. The supported actions are approve, reject, request clarification, and mark paid.

All selected Belege must be in the same state, and that state must be eligible for the chosen action — otherwise the whole batch is rejected before anything changes. Each item is then processed through the same governed transition service used for single actions, so every per-item rule gate, maker-checker check, and permission still applies. The result reports how many items were processed and lists any per-item errors.

Related

• Understanding the Beleg approval workflow and states
• Approving a Beleg and how approval locks the record
• Rule warnings, blockers, and override governance
• Making a financial correction during review