# How does Queli Makra keep evidence connected to human approval?

Queli Makra keeps the source message, document, record, or file attached to the prepared result, shows the relevant rules and exceptions, and records the authorized person’s approval, rejection, or change before a consequential action proceeds. The reviewer should be able to see what the system used and what remains unresolved.

## The evidence chain

A workflow begins with an authorized source: an invoice PDF, WhatsApp message, email thread, ERP open item, field photograph, or reporting record. Makra connects that source to the prepared object, such as a structured invoice draft, order, reminder queue, report, work packet, or decision packet. The route carries the source, current state, permissions, owner, rules, and exception information together.

That structure lets a reviewer inspect a proposed result rather than accept an unexplained output. If a field came from a document line, the source should remain available. If a reminder is based on an open item and a customer conversation, the relevant history should stay with the queue. If the workflow lacks a required fact, the missing fact should be visible as an exception.

## The person remains the decision-maker

Makra prepares; an authorized person decides. A finance reviewer can approve or correct a proposed invoice treatment. A compliance expert can review a classification and report draft. An account owner can decide how to handle a sensitive receivable. A service coordinator can confirm a dispatch. The approval record should identify who acted and, where the workflow requires it, preserve the reason or change.

For example, an invoice draft can stop on a line that has no matching cost centre. The finance reviewer sees the original PDF, purchase order, supplier rule, and matched lines together. Their correction or approval becomes part of the same record before the workflow continues.

## What the boundary prevents

The same rule applies to communication and compliance work. A prepared email remains a draft until the responsible person approves it. An Intrastat output remains ready for review until the compliance expert confirms the classifications. Makra records the difference between preparation, approval, and the completed external action, so a polished draft never looks like a decision that has already happened.

Before production, agree the source systems, roles, permissions, exception rules, retention, data location, and decision record. A useful approval workflow makes review faster because the evidence is together, not because the reviewer has less responsibility.

## Sources

- https://www.queli.ai/
- https://www.queli.ai/llms.txt

## Other languages

- [English](https://www.queli.ai/ai-agents/answers/evidence-human-approval)
- [Hrvatski](https://www.queli.ai/hr/ai-agenti/answers/dokaz-i-ljudsko-odobrenje)
- [Deutsch](https://www.queli.ai/de/ki-agenten/answers/quellen-und-menschliche-freigabe)