Skip to main content

Invoice: Review and Approval

In Review and Approval, users work on individual invoices in detail. The dialog combines invoice data, original document, workflow status, comments, warnings, errors, and approval actions in one workspace.

Users check recognized header data and amounts, complete missing information, compare the document, clarify open issues, and perform the next process step.

Invoice detail dialog with numbered legend

Detail Dialog Legend

No.AreaFunction
1Main actionsSave, save and close, navigate between records, and delete.
2StatusShows the current invoice status. The status controls available actions and mandatory checks.
3Approval barShows current and possible approval levels.
4Process actionsStarts business steps such as Start, Reviewed, Approve, Invalid, or Export.
5Additional actionsOpens supporting functions such as templates or AI rules.
6TabsSwitch between header data, accounting, tasks, attachments, relations, and other areas.
7Header and master dataContains invoice type, title, invoice number, date, supplier, address, currency, and amount.
8NotesAllows internal notes about the invoice.
9PDF toolbarProvides navigation, zoom, display, mark-up, print, and other document functions.
10Document previewShows the original invoice document.
11Activity areaContains feed, differences, notes, and errors.
12Errors and warningsShows missing values, rule deviations, or technical errors.
13History and commentsDocuments changes, automated actions, and user comments.
14Document actionsProvides download and document-specific actions.

Visible buttons, tabs, and mandatory fields can differ by client, role, approval authority, status, and configuration.

Process Overview

Invoice review and approval

The creditor workflow combines invoice intake, review, approval, accounting, export, and archiving into a traceable process.

Typical Flow

  1. Open the invoice from the dashboard or task list.
  2. Compare the original document with recognized header data.
  3. Check supplier, invoice number, date, amount, and currency.
  4. Check accounting assignment and mandatory fields.
  5. Review attachments, comments, feed, and error messages.
  6. Correct values or ask for clarification if needed.
  7. Forward, approve, reject, or return the invoice for correction.
  8. After the action, verify that status and responsibility changed as expected.

Review vs. Approval

Review and approval can be separate steps.

StepMeaning
ReviewBusiness or accounting check of the invoice.
ApprovalFormal approval by a responsible person or role.
AccountingBookkeeping allocation of the invoice.
ExportTransfer to ERP, accounting, or payment process.

Depending on the organization, one person may perform several steps or only be responsible for one specific step.

Responsibilities

An invoice can be assigned to a user or group. Invoice installations often support several responsibility fields, such as first approval, second approval, or further approval levels.

Responsibilities can come from:

  • AI rules,
  • orders,
  • purchase orders,
  • accounting references,
  • creditor master data,
  • workflow matrix,
  • manual assignment,
  • customer-specific rules.

If an invoice does not appear for the expected user, check client, status, assignment, role, object permission, and possible substitution.

Questions and Corrections

If information is missing or unclear, the invoice should not be approved without review.

Possible actions:

  • add a comment,
  • return the invoice to accounting,
  • forward the invoice to the responsible person,
  • complete missing accounting data,
  • request supplier or master-data clarification,
  • mark the invoice as invalid if it should not be processed.

Good comments describe exactly what is missing or why a decision was made.

Why a Button Is Missing

An expected button can be missing or disabled when:

  • the invoice is in the wrong status,
  • the user is not responsible,
  • write permission is missing,
  • mandatory fields are missing,
  • accounting assignment is invalid,
  • client or role does not match,
  • the workflow expects another next step,
  • the invoice is already completed.

If the invoice is visible but cannot be approved, the cause is usually permission, workflow, or validation rather than display.

Substitution

Depending on configuration, substitutes can receive notifications, see tasks, or perform actions.

Important points:

  • Substitution must be valid today.
  • The substitute user must be active.
  • Client and permissions must match.
  • Not every installation allows approval by substitutes.
  • The audit trail should show the actual acting user.

If a substitute can see an invoice but cannot approve it, write permission or workflow permission is often missing.

Audit Trail and Feed

Workflow actions, automated rules, comments, warnings, and status changes are documented in the feed or audit trail.

This is important for:

  • traceability,
  • audit,
  • support,
  • approvals,
  • export control,
  • error analysis.

If it is unclear why an invoice is in a certain status, check feed, workflow history, and audit trail first.

Typical Special Cases

SituationWhat to check
Invoice stays newSupplier, client, first approver, accounting assignment, or auto-approval rule.
Invoice cannot be approvedStatus, responsibility, mandatory fields, accounting assignment, and permission.
Invoice is in error statusError area, feed, and processing logs.
Wrong person is responsibleAI rule, workflow matrix, accounting reference, or master data.
Approval happened but invoice remains openNext approval level, export status, or follow-up task.