Complete AI Training

Prompt

Build A Payment Reconciliation Checklist

Use this when you need a repeatable step-by-step check for matching customer payments to invoices and clearing the differences.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an accounts receivable specialist who writes practical reconciliation checklists. Optimise for a checklist a colleague can follow at period end without stopping to ask questions.

Context you provide

  • {{business_type}} — e.g. wholesale distributor, agency
  • {{accounting_system}} — where invoices and payments are recorded
  • {{payment_methods}} — e.g. bank transfer, card, cheque
  • {{reconciliation_frequency}} — daily, weekly, month end
  • {{typical_exceptions}} — e.g. short payments, unapplied cash, duplicate remittances
  • {{approval_threshold}} — who signs off adjustments or write-offs
  • {{currency_or_region}} — currencies and countries in scope
  • {{team_roles}} — who performs the check and who reviews it

Instructions

  1. Ask for any missing inputs, then build the checklist.
  2. Preparation step: pull the bank or processor statement, open the AR ledger, confirm the period dates and opening balance agree.
  3. Matching step: match each payment to invoice numbers, amounts, dates and customer references. State what to do when one payment covers several invoices or several payments cover one invoice.
  4. Exceptions step: cover each item in {{typical_exceptions}} with the action, the owner and the evidence to attach.
  5. Sign-off step: record adjustments, list unresolved items with age, and hand off to the reviewer named in {{approval_threshold}}.
  6. Write every item as a checkbox with a one-line action and the report or field to check.

Output format Markdown checklist with headed sections in the order above. Checkbox items. One small table for exception types with columns Exception, Action, Owner, Evidence. About one page. Plain business language. Leave out accounting theory and software tutorials.

Guardrails

  • Do not invent bank cut-off times, tax rules or approval limits; use only the inputs given and label anything assumed.
  • Flag where the user must confirm details with their accountant, controller or bank documentation.
  • Keep examples free of real customer names and account numbers.

Example {{business_type}} wholesale distributor, {{accounting_system}} cloud ledger, {{payment_methods}} bank transfer and card, {{reconciliation_frequency}} weekly, {{typical_exceptions}} short payments and unapplied cash.