Inspiration
In small companies, finance and HR approve expense claims by eye: open the claim, open the policy, compare every line. It's slow and inconsistent, and the claimant often waits days just to hear a receipt is missing.
What it does
Claim Buddy reads your company's Claims Policy straight from a Confluence page and checks every claim raised in Jira against it. It flags:
- items over the per-claim, per-day, per-night or per-km limit
- missing receipts above the policy threshold (Jira attachments count as receipts)
- claims submitted after the deadline (e.g. 30 days) or with future dates
- categories that need pre-approval
- items that are never claimable (alcohol, fines, personal items)
It then recommends Approve, Approve partially, Needs info or Reject, with reasons the approver can paste straight back to the claimant. Finance changes the rules by editing the Confluence page; no code or admin screen needed.
How we built it
Forge app with:
- rovo:agent "Claim Buddy" with 4 actions: get-claims-policy, check-claim, list-pending-claims, post-claim-verdict
- jira:issuePanel showing the verdict, a line-item table and a one-tap "Post recommendation" button (comments on the issue and adds a claim-buddy-approve / -reject / -needs-info label)
- Confluence REST v2 to read the policy table (Category | Limit | Per | Receipt required above | Notes), with a built-in sample policy as fallback
- A pure-JS policy engine with unit tests, deployed via GitHub Actions and the Forge CLI
Challenges we ran into
Parsing free-text claims reliably (one item per line, flexible formats) and keeping the agent from inventing rules: every finding cites the policy row it came from.
Accomplishments that we're proud of
The policy lives where finance already writes documents, so Claim Buddy stays correct when the policy changes.
What we learned
Rovo actions work best when each one does one clear job and returns structured results the agent can explain.
What's next for Claim Buddy
Jira Service Management request types for claims, OCR of receipt photos, multi-currency, and per-department policies.
Built With
- confluence
- forge
- github-actions
- javascript
- jira
- react
- rovo
