---
name: invoice-approval-routing
description: Invoice Approval Routing converts invoice_id, supplier_id, invoice_number, currency into approval queue and control report with required approver role, threshold basis, match result, duplicate flags, and blocked reasons, with cited evidence, explicit rules, and unresolved exceptions. Use for invoice approval routing, recurring review, and decision preparation.
license: Apache-2.0
metadata:
  adlass.categories: "finance-accounting/accounts-payable"
  adlass.industries: ""
  adlass.tags: "process-review,evidence,exceptions,decision-support,source-traceability"
  adlass.adaptation: "mapping"
  adlass.source: "original"
  adlass.version: "1"
---

# Invoice Approval Routing

## Purpose

Invoice Approval Routing turns the supplied records into approval queue and control report with required approver role, threshold basis, match result, duplicate flags, and blocked reasons. It keeps source facts, derived values, recommendations, and limitations separate so each conclusion can be checked.

## Scope

Cover invoice_id, supplier_id, invoice_number, currency, gross_amount, entity, cost_center, PO, receipt, coding, authority band, effective date. Preserve source identifiers, dates, units, and wording needed to trace every result.

**Excluded for accounts-payable route control:** changing source records, taking external actions, making a human approval or employment decision, and asserting facts absent from the corpus.

## Data basis

- Process documents and tables containing invoice_id, supplier_id, invoice_number, currency, gross_amount, entity, cost_center, PO, receipt, coding, authority band, effective date.
- Company policy, rubric, schema, templates, and reference tables in scope.
- Run input for period, audience, entity, or threshold when it changes this run.

## Result

Produce approval queue and control report with required approver role, threshold basis, match result, duplicate flags, and blocked reasons. Each material row and conclusion cites a document, section, page, row, field, or run input.

## Quality criteria

- Every invoice totals, delegation bands, and match exceptions record is included or has an exclusion reason.
- Calculations state fields, units, denominator, and rule.
- Missing, contradictory, stale, and ambiguous values stay labelled rather than guessed.
- Facts, interpretations, and proposed next actions use separate fields.
- Supplied terminology, thresholds, and status values are used consistently.
- The final limitations section states what the corpus could not establish.

## Instructions

Apply the authority matrix effective on the processing date. Use the policy amount basis and currency rule. Missing delegation, PO, receipt, or coding evidence blocks routing and never authorizes a lower route. Preserve original values beside normalized values, cite every material finding, and use “not assessed” when required evidence or a rule is absent. When sources disagree, show both citations and explain the conflict. Keep row-level evidence in the supporting sheet and summarize only supported conclusions in the document.

## Adapt before use

- Map the invoice and authority-matrix mapping fields and row citation convention.
- Add the governing policy, rubric, schema, or reference tables to the scope.
- Define thresholds, status values, units, and exception severity.