xbert-anomaly-review

{
  "name": "xbert-anomaly-review",
  "displayName": "XBert Anomaly Review",
  "description": "Surface every anomaly XBert that fired across the period as a flat ranked list with per-firing verification and recommended action. Checks the Anomaly Review agent is configured with linked XBerts before reviewing. No invented pattern labels, no user attribution, no Journal data.",
  "author": {
    "name": "XBert Intelligence",
    "email": "[email protected]"
  },
  "homepage": "https://intelligence.xbert.io/plugins/xbert-anomaly-review",
  "license": "MIT",
  "keywords": [
    "anomaly",
    "review",
    "audit",
    "evidence-pack",
    "xbert"
  ],
  "x-xbert": {
    "displayName": "XBert Anomaly Review",
    "tagline": "Every anomaly XBert that fired for the period — ranked, with the underlying transaction and a per-firing recommended action.",
    "audience": [
      "accountants",
      "principals"
    ],
    "categories": [
      "review",
      "anomaly",
      "audit"
    ],
    "prerequisites": [
      "XBert account",
      "Client connected to a ledger",
      "Anomaly Review agent added via Automation → Agents → Browse Agents in the Connect portal",
      "Anomaly XBerts linked to the Anomaly Review agent (Agent → Linked XBerts)",
      "XBert Working Paper, the companion render plugin that writes the Word document — install it from this same catalogue (it needs Python 3.10+)"
    ],
    "screenshots": [],
    "demoVideo": null,
    "includes": {
      "skills": 1,
      "commands": 1,
      "mcpTools": 0
    },
    "longDescription": "Anomalies in the ledger are detected deterministically by Custom XBerts on the data XBert MCP exposes today — same vendor + amount + date duplicates on Bill or BankTransaction, period-over-period balance jumps, same vendor coded to a different account than its recurring pattern, round-number-recurring postings, volume spikes per vendor or account. The XBerts do the detection; this plugin does not.\n\nBefore reviewing, the plugin verifies the Anomaly Review agent is set up in your Connect portal with linked Custom XBerts — if it isn't, the review stops and walks you through the setup instead of presenting generic worklist data as an anomaly review.\n\nXBert Anomaly Review surfaces what the linked anomaly XBerts caught for the period as a flat ranked list, verifying each firing against the underlying records before recommending an action (ABN/address comparison on duplicate-contact firings, current outstanding amount on overdue-invoice firings). Per firing: posting date, doc number, vendor, amount, account, the XBert that fired and its detection reason, the verification result, the count of prior firings on the same vendor or same account in the period (a deterministic fact, not a pattern label), and the recommended next action. XBerts whose firings contradict their intent are flagged with a suggested prompt refinement to apply in the XBert portal. Optional sub-grouping by deterministic facets (vendor, account, period bucket) keeps a long list scannable — never under invented pattern labels.\n\nWhat the plugin explicitly does NOT do (no backing data in MCP today): identify the posting user, detect after-hours patterns or time-of-day attribution, infer intent (round-tripping), name pattern clusters across firings, track cluster-level resolution status, or claim Journal data. Duplicate-journals, reversal-pair and round-tripping detection all need Journal data which is not exposed today. If the user wants those, the answer is the same in every case: it needs a deterministic Custom XBert sitting on a data surface MCP exposes, and that surface doesn't exist yet.",
    "useCases": [
      {
        "title": "Monthly anomaly review during close",
        "description": "Before signing off the month, walk every anomaly XBert that fired with the underlying transaction and the recommended action — per firing."
      },
      {
        "title": "Pre-audit anomaly sweep",
        "description": "Ahead of an external audit, surface and resolve per-firing anomalies so the auditor sees a clean ledger with documented evidence."
      },
      {
        "title": "New-client first-month sanity check",
        "description": "First month on a newly onboarded client surfaces the firings the linked anomaly XBerts caught on legacy data."
      },
      {
        "title": "Recurring-issue investigation",
        "description": "When the same vendor or account keeps appearing in firings, the per-vendor / per-account recurrence count surfaces the pattern without inventing a label."
      }
    ],
    "benefits": [
      {
        "icon": "ShieldCheck",
        "title": "XBerts detect, plugin surfaces",
        "description": "Detection is owned by the Custom XBerts deterministically; the plugin reasons only over what fired. No invented pattern labels, no user attribution, no Journal data claims."
      },
      {
        "icon": "Search",
        "title": "Deterministic facets, not invented clusters",
        "description": "If sub-grouping helps, the label IS the data facet — '5 firings on Vendor X', '3 firings on Account Y', '8 firings in the last week of the period'. Never a name the XBerts cannot independently confirm."
      },
      {
        "icon": "FileText",
        "title": "Audit-ready evidence pack",
        "description": "Word working paper carrying every firing with its source XBert reference and the underlying Bill / BankTransaction / Invoice — filable straight into the client folder."
      }
    ],
    "workflow": [
      "Type /anomaly-review in Claude Code or Claude Desktop",
      "Plugin checks the Anomaly Review agent is set up in your Connect portal with linked Custom XBerts — if not, it stops and walks you through the setup instead of reviewing generic worklist data",
      "Confirm the client and the review period",
      "Plugin pulls the period's firings from the linked anomaly XBerts and verifies each one against the underlying records (e.g. ABN/address on duplicate contacts, current outstanding amount on overdue invoices)",
      "Every firing is presented as a row in a ranked list with the underlying transaction, the XBert reason, the verification result, and a recommended next action",
      "XBerts whose firings contradict their intent are flagged with a suggested prompt refinement to apply in the XBert portal",
      "Optional sub-grouping by vendor / account / period bucket if the list is long (deterministic facets, never invented pattern labels)",
      "Build the working-paper payload (stamped with the plugin version), render via xbert-working-paper:render-docx, and report the saved path"
    ]
  }
}