accounts-payable

Automate accounts payable workflows with Stripe invoicing and Supabase audit logs.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill accounts-payable-coreymaypray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accounts-payable
Source: https://github.com/coreymaypray/sloth-skill-tree/tree/main/plugins/maycrest-ops/skills/accounts-payable
Command: npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill accounts-payable-coreymaypray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end accounts payable workflow for Maycrest and the Maycrest Group, handling invoice creation, approvals, and payments with full audit trails and idempotency.

Core Features & Use Cases

  • Automated invoicing: Create Stripe invoices for client engagements and recurring vendor payments with guardrails.
  • Payment orchestration: Execute vendor payments and contractor settlements with spend-limit checks and idempotent guarantees.
  • Auditability: Maintain a centralized ledger in Supabase with invoice and payment metadata for compliance reviews.

Quick Start

Initiate an autonomous accounts payable workflow by processing a vendor invoice through Stripe and recording the audit-ready payment in Supabase.

Frequently Asked Questions about accounts-payable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate accounts payable workflows with Stripe invoicing?

Automating accounts payable workflows with Stripe invoicing involves processing vendor invoices, applying spend-limit controls, and executing idempotent disbursements. This Skill orchestrates these actions while validating the vendor registry and logging audit-ready metadata in Supabase.

How do I ensure idempotency checks for vendor payments?

Idempotency checks for vendor payments prevent duplicate transaction execution. The Skill implements idempotent guarantees during Stripe-based disbursements, ensuring that repeated requests for the same contractor settlement or recurring bill do not result in multiple payouts.

What is the best way to maintain an audit-ready transaction log for accounts payable?

An audit-ready transaction log for accounts payable is maintained by centralizing invoice and payment metadata in a Supabase ledger. This Skill automatically records Stripe disbursement details and vendor registry validations to ensure compliance reviews have complete transaction histories.

Does this accounts payable automation support recurring bills and spend-limit controls?

Yes, this accounts payable automation supports recurring bills and spend-limit controls. It orchestrates vendor payments and contractor settlements by validating transactions against established spend limits before executing Stripe disbursements.

How do I validate a vendor registry before executing Stripe disbursements?

Validating a vendor registry before executing Stripe disbursements requires checking the vendor against approved records. This Skill performs vendor registry validation as a guardrail before processing invoice payments and logging the transaction in Supabase.

Why do I need centralized auditing in Supabase for vendor payments?

Centralized auditing in Supabase for vendor payments provides a unified ledger for compliance reviews. It captures invoice creation, payment metadata, and idempotency checks across entities, ensuring that all Stripe disbursements are fully traceable and audit-ready.