Bundle catalog

roles bundle

Accounts Payable / Accounts Receivable Specialist

A free, open-source set of 10 Markdown files that gives an AI assistant practical guidance for the Accounts Payable / Accounts Receivable Specialist role.

Use this bundle to plan and review Accounts Payable / Accounts Receivable Specialist work with evidence, assumptions, owners, and review points made explicit. The page previews a role guide, an overview, a workflow, and a template; the intended output is AP/AR operations brief. Start source review with O*NET OnLine — Summary / 43 3031.00.

Project-reviewed beta

10 Markdown files · 1,189 words · no signup · CC-BY-4.0

Professional review status

No professional domain review recorded

This bundle covers accounting, financial subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.

Review before reliance: A qualified accounting or financial professional appropriate to the question, decision, organization, and jurisdiction.

Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Is this bundle right for your task?

Who it is for

  • People performing or supporting Accounts Payable / Accounts Receivable Specialist work, plus teams reviewing its decisions and outputs
  • Teams working in Financial operations, Commerce, Professional services

When to use it

  • An Accounts Payable / Accounts Receivable Specialist task needs a structured plan, evidence checklist, or review-ready output.
  • A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.

What you need to provide

  • The task objective, intended audience, working context, constraints, source material, and decision owner.
  • Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.

Tasks and expected outputs

Questions it helps answer

  • Prepare an ap/ar operations brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce review-ready decisions with explicit verification and approval boundaries.

What it helps produce

  • AP/AR operations brief

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Accounts Payable / Accounts Receivable Specialist work by producing AP/AR operations brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 43 3031.00, then confirm that the reference is current and applicable. Inspect Accounts Payable / Accounts Receivable Specialist before drafting.

Context path: bundles/roles/accounts-payable-accounts-receivable-specialist

What the bundle includes

Frameworks

  • source-evidence matrix
  • accounts-payable-and-receivable-operations evidence matrix
  • qualified-review gate

Evaluations

  • Accounts Payable / Accounts Receivable Specialist source verification check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

Limitations and safe use

Do not use this for

  • Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.

Known limitations

  • Use official Accounts Payable / Accounts Receivable Specialist sources for general context; local accounts payable and receivable operations, configuration, records, values, states, and permissions require inspected evidence.
  • Task-specific work requires current evidence for approved vendor and customer master data, invoices, bills, credit notes, and purchase orders, receipts and acceptance evidence, payments, remittances, and bank evidence, aging and subledger reports, general-ledger balances, and approval and segregation-of-duties evidence.
  • Do not infer vendor identity, customer balance, invoice validity, payment status, bank details, aging, tax treatment, approval status.

Safety notes

  • Minimize personal, customer, employee, financial, credential, and other sensitive data.
  • Require explicit confirmation before creating or changing master data, releasing payments, applying cash, issuing credits, contacting counterparties, or posting entries.
  • Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.