Plan the route, capture the receipt, approve in a tap
Field reps plan itineraries, log visits against CRM accounts, and snap expense receipts — approvals run through policy checks and land as structured lines for finance.
Revenue & Sales · Visits, itineraries & expense claims
Field visits and expenses on the record they belong to
Field sales runs on two artefacts that almost never meet: the visit, which lives in a rep's calendar and their memory, and the expense claim, which arrives as a photograph of a receipt at the end of the month. Neither is attached to the account the trip was actually for.
Dolfin360 Tour & Expense records the itinerary against CRM accounts, logs the visit with location and outcome, and captures the receipt at the moment it is issued. Approvals run through policy checks rather than a manager's judgement of a blurry image, and what reaches finance is a structured line with a cost centre, an account and a reason — not an email attachment.
Visits attached to accounts
An itinerary is built from CRM accounts, and each logged visit writes its outcome back to the record — so the trip has a business result, not just a date.
Receipts captured in the field
Snap the receipt when it is issued. The claim carries the visit, the account and the cost centre with it, so nothing is reconstructed a month later.
Policy checks before approval
Per-diem caps, category rules and distance limits are evaluated automatically, so a manager approves exceptions rather than re-checking every line.
Plan the route, log the outcome
Itineraries built from CRM accounts, with visit outcomes written back.
A rep plans the week as a set of accounts to visit, and the itinerary carries the CRM context for each stop — open deal, last quotation, unresolved ticket. Check-in is geo-stamped so a visit is recorded where it happened rather than where it was claimed.
After the visit the rep logs an outcome against the account, which advances the deal or opens a follow-up task. Route optimisation, currently in open beta, suggests visit order from the itinerary's own constraints.
- 01Account-based itineraries — each stop carries its CRM context
- 02Geo-stamped check-in — the visit is recorded where it happened
- 03Outcome written back — advances the deal or opens a task
What is inside Tour & Expense
Build a route from CRM accounts with their live context.
Check-in recorded at the location, with outcome capture.
Photograph and attach receipts at the point of spend.
Per-diem caps, category rules and distance limits enforced on entry.
Route by amount, category or department with a full audit trail.
Suggested visit order and timing from itinerary constraints.
Claims that arrive ready to post
Policy-checked, cost-coded and structured for finance.
The claim is assembled as the trip happens: receipt images attached to the expense, the expense attached to the visit, the visit attached to the account. Category rules, per-diem caps and distance limits are evaluated as the rep enters each line, so violations surface immediately rather than at approval.
Approved claims flow to payroll as structured reimbursement lines with the cost centre already set, which removes the month-end step where somebody types numbers from a PDF into a spreadsheet.
- 01Receipt capture — images attached to the expense line
- 02Automatic policy checks — caps, categories and distance limits
- 03Structured to payroll — cost-coded reimbursement lines
From planned route to reimbursed claim
Plan
Build the week's itinerary from CRM accounts and their open work.
Visit
Geo-stamped check-in; log the outcome against the account.
Claim
Capture receipts in the field; policy checks run as lines are entered.
Approve
Managers handle exceptions; approved lines flow to payroll cost-coded.
What the field team stops doing
Platform facts and published rates — not customer-measured outcomes.
“Expenses used to arrive as a folder of photographs. Now the claim knows which account the trip was for, and so does finance.”
Give your field team an itinerary that knows the account
Try Tour & Expense free for 14 days, including the route optimisation beta.
Tour & Expense questions
Check-in is geo-stamped, so a visit is recorded where it actually happened. The itinerary is built from CRM accounts, and the outcome logged after each visit writes back to the account — advancing the deal or opening a follow-up task.
Per-diem caps, category rules and distance limits are evaluated as each line is entered, so violations surface to the rep immediately instead of at approval. Managers then handle genuine exceptions rather than re-checking every claim.
It is in open beta for Tour & Expense customers and carries a Beta badge in-product. It suggests visit order and timing from your itinerary's own constraints; the rest of the module is generally available.
Try Tour & Expense free for 14 days
No credit card. It shares data with every other module the moment you turn it on.