More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    πŸ“₯ Invoice Acceptance Evidence Gate

    1

    Verify customer-specific invoice fields, attachments, destination, submission receipt, acceptance status, correction version, and aging start.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    πŸ“₯ Invoice Acceptance Evidence Gate

    πŸ“₯ Invoice Acceptance Evidence Gate

    Example session with this skill installed

    An invoice was emailed although the customer profile requires Coupa, omits the PO field and timesheet attachment, and its latest submission is rejected without a verified receipt.

    • Read your context and instructions
    • Compiled the invoice acceptance evidence

    Gate: BLOCK. Wrong destination, missing field and attachment, rejection, and missing acceptance receipt prevent aging.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Invoice Acceptance Evidence Gate distinguishes sending an invoice from proving that the customer's accounts-payable workflow accepted it. It compares each invoice with a customer-specific submission profile, checks required fields and attachments, verifies the destination, selects the latest correction version, preserves portal or email receipt evidence, surfaces rejection reasons, and requires an acceptance timestamp before aging begins. It returns a ledger, findings, acceptance gate, and memo. It never submits invoices, contacts a customer, collects payment, or provides accounting or legal advice.

    The package uses owner-supplied customer requirements and does not connect to an AP portal, send an invoice, or contact a customer. A portal or email receipt does not prove legal delivery, correctness, approval, or eventual payment. Accepted-for-aging means the supplied evidence supports the recorded acceptance time; finance retains responsibility for follow-up and accounting treatment.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    invoice-acceptance.json
    invoice-acceptance-output/**

    The deterministic helper reads one supplied local JSON file and writes only the selected review output directory.

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill solves the 'black hole' problem in AR by distinguishing between a sent invoice and one that has been officially accepted by a customer's AP workflow, preventing payment delays caused by unknown rejections.

    The skill is designed to work with any LLM-based agent capable of processing structured data (JSON/CSV) and document text, making it compatible with most enterprise AI orchestration platforms.

    No, this skill is a non-intrusive verification layer; it analyzes submission evidence and field requirements but never directly contacts your customers or submits files to their portals.

    You receive the core logic gate, a set of customizable customer-specific submission profiles, and documentation on how to interpret the generated ledger and findings reports.

    Setup involves mapping your current invoice data and submission receipts to the skill's input schema and defining your specific customer requirements for attachments and mandatory fields.

    The gate identifies the most recent correction version of an invoice and ensures that the aging process only triggers based on the final acceptance timestamp rather than the initial (potentially flawed) submission date.