Can I expense this? Answered from your own policy
Staff describe what they want to spend on and get the limit, the approver and whether a receipt is required, quoted from the policy line that sets it. Anything the policy doesn’t cover goes to finance rather than being reasoned into an allowance.
Finance · Someone asks · 7 steps · Reads your documentsA person is asked at “Ask a person”
QuestionQuestion
RetrieveRetrieve
AnswerAnswer
If / elseGrounded in the sources?
Answer shownAnswer shown
Ask a personAsk a person
Answer shownAnswer shown
7 steps in the flowDrag the canvas, or any step, to move it around.
Why teams run it
Finance teams answer the same spending questions all day, and staff who can’t get an answer either overspend or stall a purchase. The policy usually says what to do, but few people can find the clause that applies to their situation.
How it is governed
- Answers quote the policy line that sets the limit or approver.
- It is instructed not to reason its way to an allowance the policy lacks.
- Escalated questions wait for a finance approval before anything is shown.
- Every question and answer is kept in the run history.
- Who runs it
- Finance operations teams; Financial controllers; Budget holders and managers.
- What you supply
- Expense and procurement policy as knowledge sources.
From template to a live agent
The same builder, tests and release review apply to a template as to anything built from scratch.
- Open it as a working flow
- Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
- Prove it before it ships
- An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
- Keep a person on the decisions
- A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
- Publish where people work
- A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
- What teams usually change
- Load regional or entity-specific policies as separate knowledge sources; Name the finance queue or person who rules on escalations; Make the check stricter, so uncovered questions always reach finance.
Questions buyers ask
- Does it approve spending?
- No. It tells staff what the policy says, including who the approver is, and the approval itself happens in your existing process. Questions the policy doesn’t settle go to finance.
- How does it handle different policies per country or entity?
- Load each policy as its own knowledge source; answers cite the document they come from, so a reader can see which policy applied. Retrieval also respects each source’s own permissions.
- What if someone asks about something the policy ignores?
- The answer says the policy is silent rather than inferring a permission. Teams commonly tighten the check so those questions reach finance for a ruling.
Related templates
All 60 templates- Invoice readerReads an invoice and returns the fields your ledger needs, leaving anything absent blank rather than guessing it.FinanceA document or recording is attached5 stepsa person approvesa recorded run
- Grant matcherFinds the grants an organisation is actually eligible for, and says what would rule each one out.FinanceSomeone asks4 steps
- Statement reconciliationCompares a statement against your own records and lists only what does not agree.FinanceA document or recording is attached4 steps
- Budget questionsAnswers spend questions from an export — totals by cost centre, by month, over budget — with the arithmetic done in code rather than by a model.FinanceSomeone asks5 steps
See it run on your own data
We open it in the builder, point it at a sample of your documents and systems, and run it with you.