Hire an AI accounts payable reviewer
Paste invoices, approved vendors and your approval rule. Get each invoice checked for duplicates and mismatches, plus a payment proposal to approve.
What you give
- Your approved vendor list, with names only. Do not paste full bank account numbers
- Your past payments for the period, so it can spot duplicates
- Your approval rule, such as the amount above which a person must sign off, and who that person is
What you get
- An invoice check table that shows each invoice as fine, on hold or needing approval, with the reason
- Checks still needed before anyone pays
An example
You pay a stack of supplier or contractor invoices each week and want them checked before you pay.
You ask: “Paste invoices, approved vendors and your approval rule. Use the material I attach and ask for anything essential that is missing.”
You get back:
- Invoice check. Each invoice with vendor, duplicate and order checks, a status and the reason.
- Payment proposal. The invoices that pass, with payee, amount, reference and approver, for a person to approve.
- Holds and escalations. Invoices that cannot be paid yet, the problem and what clears it.
An example, not your task.
Hire this specialist
It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.
Related specialists
- Supplier invoice and receipt checker
- Supplier invoice exception reviewer
- Basic and diluted earnings per share checker
- Inventory accounting comparison reviewer
Skills and workflows for this job: Reconcile accounts and close the books
Details
Everything it can hand back
Your task sets the actual outputs. The specialist picks the methods that cover them.
- An invoice check table that shows each invoice as fine, on hold or needing approval, with the reason.
- A payment proposal for the invoices that pass, with payee, amount, currency, reference and approver.
- A list of holds and escalations, such as duplicates, vendors not on your list and amounts that do not match.
- A reconciliation gap list and a paid, pending and unmatched summary, with each currency kept separate.
- Checks still needed before anyone pays.
How it does the job well
- Never send, schedule, approve or release a payment, transfer or crypto transaction. State that a person must approve and pay in their own accounting or bank software.
- Do not state a fact about a vendor, an amount or a balance that the user did not give you.
- Tax, audit and legal treatment of payments needs the user's accountant. Say so when it comes up.
- Reconcile to source documents, such as bank statements, ledgers and invoices, before reporting.
- Show the calculation, inputs and period for every figure.
- Label actuals, estimates and forecasts clearly.
- Send tax, legal and regulatory questions to a qualified professional.
Mistakes it avoids
- Mixing cash and accrual figures, or different periods, in one comparison.
- Rounding or formula errors that do not tie back to totals.
- Giving personal investment advice.
What a good result looks like
An example, not your task: You pay a stack of supplier or contractor invoices each week and want them checked before you pay.
- Invoice check. Each invoice with vendor, duplicate and order checks, a status and the reason.
- Payment proposal. The invoices that pass, with payee, amount, reference and approver, for a person to approve.
- Holds and escalations. Invoices that cannot be paid yet, the problem and what clears it.
- Reconciliation gaps. Differences between invoiced, paid and posted amounts.
- Period summary. Paid, pending and unmatched items, with each currency kept separate.
- Checks still needed. Facts it could not confirm and steps to take before anyone pays.
How the work is checked
- Totals tie out, and differences are explained line by line.
- Forecast assumptions are listed and easy to change.
- Anything not checked by a qualified person is marked as needing review.
- States which checks passed, failed or could not run, and names missing inputs.
These checks have not been run against a model yet. Your AI uses them to check its own work.
Capabilities
- Read the facts. It lists the invoices, vendors, history and approval rule it was given, and marks what is missing.
- Check each invoice. It checks vendor, duplicates, amount against the order or contract, and the approval rule.
- Sort the invoices. Each invoice goes to fine to propose, hold, or needs approval, with a plain reason.
- Write the proposal. For passing invoices it lists payee, amount, currency, reference and approver, and suggests a payment method to confirm with your bank.
- Find the gaps. It compares what was invoiced, paid and posted, and lists differences, with currencies kept apart.
- Summarise the period. It lists paid, pending and unmatched items and what must be checked before anyone pays.
How the role works
- Checks your task, context and available tools.
- Picks the methods needed and prepares a work plan.
- Carries out supported tasks, with each method's limits and review gates.
- Checks the real deliverables and corrects supported faults.
- Hands back files, evidence and unresolved gaps.
Your specialist's working setup
Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.
Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.
Use this specialist through MCP or the API
Call prepare_specialist with role_id accounts-payable-agent only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.
For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.
Complete ZIP: Download base specialist. API: GET /api/v1/specialists/accounts-payable-agent/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.
Inputs and helpful context
The specialist starts from the task brief. Only active methods require their inputs.
For the primary method, when used
- The invoices to check, with vendor, invoice number, date, amount, currency and any order or contract reference.
- Your approved vendor list, with names only. Do not paste full bank account numbers.
- Your past payments for the period, so it can spot duplicates.
- Your approval rule, such as the amount above which a person must sign off, and who that person is.
- The orders or contracts the invoices should match, and ledger or bank lines to reconcile against (optional).
Helpful context (optional)
- A bank or card statement for the same period, with account numbers masked.
- Your purchase orders or signed contracts for the larger invoices.
- A short note on vendors whose details changed this period.
Tools and access
- A spreadsheet such as Google Sheets or Excel: Paste invoices and past payments as a table, so duplicate and amount checks are exact.
- Your accounting software, such as QuickBooks or Xero: Export your bills and payments as a file or table to paste in. The agent cannot connect to it in a plain chat.
Functions and deliverables
- Accounts payable reviewer: Paste invoices, approved vendors and your approval rule. Get each invoice checked for duplicates and mismatches, plus a payment proposal to approve.
- An invoice check table that shows each invoice as fine, on hold or needing approval, with the reason.
- A payment proposal for the invoices that pass, with payee, amount, currency, reference and approver.
- A list of holds and escalations, such as duplicates, vendors not on your list and amounts that do not match.
- A reconciliation gap list and a paid, pending and unmatched summary, with each currency kept separate.
- Checks still needed before anyone pays.
- Invoice checker: Check invoices against purchase orders, spot math errors and code each line to an account. Paste text or a CSV and get a flagged, coded record.
- Structured fields for each invoice
- A purchase order match result
- Account codes per line
- A flag list sorted by severity
- A batch summary
- Clinic payment reconciliation reviewer: Share total claims, payment records and bank receipts. Find gaps between amounts billed, paid and received.
- The closing claims receivable, rolled forward from the opening balance
- Expected bank cash, the actual deposit and the difference between them
- Every gap named, with what explains it or a note that it is unexplained
- A list of sources with dates for each figure
- An editable workbook, if your AI can make spreadsheet files
- Unpaid invoice chaser: Share overdue invoices and available payment records. Get one tone-matched reminder per customer, for your review and approval before sending.
- A table of overdue invoices
- A payment history score per customer
- Tone-matched reminder drafts
- Drafts queued for your approval
- me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
- One me.md file with up to ten dated sections
- A list of facts taken from memory, for you to check
- A short note of what it removed for privacy
- The two next steps, to save it and set it up
Tasks you can use it for
- You pay a stack of supplier or contractor invoices each week and want them checked before you pay.
- An invoice looks a little different from the last one and you want to know if it is a duplicate or a mismatch.
- You need a clean list of what is due, who must approve it and what is on hold.
- Month end is close and you want a paid, pending and unmatched summary to give your accountant.
Limits to check before starting
- You want it to approve or send real payments. It will not. Use your accounting or bank software, with a person approving.
- You are chasing invoices that customers owe you. Use the Late invoice and cash forecast reviewer.
- You only want to find duplicates, wrong sums and missing receipts in a supplier batch. Use the Supplier invoice exception reviewer.
- You need a full match of your ledger against a bank statement. Use the Account reconciler.
- You are building payment software. Use the Payments and billing engineer agent.
Best way to use this role
Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.
- Download the pack from this page and add it to your AI as a skill. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.
- Paste your invoices, approved vendors, past payments and approval rule. Mask any bank account numbers to the last four digits.
- Answer the questions it asks once. Anything missing is marked MISSING. It will not assume a vendor is approved.
- Read the holds first. Fix or explain each one, such as a duplicate or an amount that does not match.
- Check new or changed bank details with the vendor by a contact method you already trust. Do this before any payment.
- Pay through your own accounting or bank software, with your approver signing off. Record the payment there.
Read it as data
Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/accounts-payable-agent for its role instructions and pinned sources.
This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.