---
name: payables-preparation
description: "Prepare coded import draft, match exceptions and proposed payment schedule. Use for this workflow with supplied business information."
---

# Payables preparation

## Inputs and purpose

Use this workflow to prepare: Coded import draft, match exceptions and proposed payment schedule.

Start with: Invoice/receipt files, account list, POs and receiving records.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Read supplied bills, purchase commitments, receiving evidence and accounting categories. Assign a stable record identifier and preserve source references.

2. Check vendor identity, billed quantities, price, tax treatment supplied by the business, duplicates and due dates. Flag differences rather than silently correcting them.

3. Prepare coding and a proposed payment schedule constrained by actual approvals and available cash assumptions.

4. Return a review table and exceptions. A prepared record is not an approved bill or payment; changes to payment details require the business's verification process.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Complete receipts and reduce duplicate or mismatched bills.

Possible success measures: Missing receipts, duplicate exceptions, cost per bill. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).