---
name: payment-run-precheck
description: Checks a proposed payment run before release by reconciling payment rows to approved invoices, supplier master data, bank details, due dates, holds, currencies, and duplicate-payment controls. Use for payment run precheck, evidence review, management reporting, and decision support.
license: Apache-2.0
metadata:
  adlass.categories: "finance-accounting/accounts-payable"
  adlass.industries: ""
  adlass.tags: "payment-run,invoice,bank-details,holds,approval,duplicate"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Payment run precheck

## Purpose

Checks a proposed payment run before release by reconciling payment rows to approved invoices, supplier master data, bank details, due dates, holds, currencies, and duplicate-payment controls.

## Scope

Work only on the named source records and the deliverable fields described here. Preserve source wording, identifiers, dates, amounts, statuses, and citations. **Excluded:** contacting people, changing source systems, making approvals, or presenting a conclusion as a completed business action. The assessed object is a proposed payment batch, with invoice-level controls evaluated before any release status is stated.

## Data basis

- The process-specific documents, spreadsheets, and record tables in the skill scope.
- The company policy, rubric, control matrix, template, or prior-period output named by this process.
- Run-specific period, audience, project, or decision brief when supplied.
- The assessed object is a proposed payment batch, with invoice-level controls evaluated before any release status is stated.

## Result

Row-level precheck results with rule, amount, and evidence. Payment run control memo {date}

## Quality criteria

- Every material fact and finding cites its document section, page, timestamp, table row, or record ID.
- Counts, amounts, dates, and statuses reconcile to the named source population.
- Rule outcomes show the rule and preserve source values beside normalized values.
- Missing, conflicting, excluded, and estimated items have explicit statuses.
- The written result and structured output use the same row-level findings.
- The assessed object is a proposed payment batch, with invoice-level controls evaluated before any release status is stated.

## Instructions

A payment row cannot pass when invoice approval, beneficiary identity, bank details, hold status, or duplicate-control evidence is absent.

## Adapt before use
Keep a blocked payment’s amount and intended beneficiary in the exception row so the run total remains auditable without implying that the payment passed.
Reconcile run count and gross total to the payment batch header. Compare beneficiary account changes with the supplier master effective date and isolate blocked rows without altering the proposed payment amount.

- Add the company policy, rubric, control matrix, or approved format named in the Data basis.
- Map source column names, identifiers, status values, and date or currency conventions.
- Define the process threshold, escalation vocabulary, responsible review role, and retention rule.