Finance

Expense Evidence Checker

Expense Evidence Checker

Start with Expense export + receipts + policy. Uploaded files describe a snapshot. Supply new files for new private facts; prior cases remain available for comparison. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.

Watch it run for
  • 1/wkEvidence reports

FactoriesStart with your sources

IdleIllustrative run

Reading watched pages

    Related solutions

    See how teams in this category put agents to work.

    Integrations

    0 integrations

      Get started with Expense Evidence Checker

      Pick an example, connect your tools, and review the first run.

      Set up the Expense Evidence Checker agent template for this project. Follow /SKILL.md for the exact CLI commands. Goal: Investigate duplicates, arithmetic errors, missing support, and policy exceptions. Deliver an evidence-linked review queue and explicit corrections for each new batch. 1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project. 2. List the first-party workflow templates. If `expense-evidence-checker` is listed, instantiate it with `--path.slug expense-evidence-checker` and start the run; otherwise create a project from this template at /new?template=expense-evidence-checker&preset=trial. 3. Share the run id, follow the run until it finishes, and summarize its outputs and changes. Ask me before spending FTAI or changing anything outside this repository.

      Launch from Claude Code, Codex, Cursor, and other agents.