Skip to main content

Field visit to travel claim

Modules ATT, FFM, MOB, CLM, PAY, NTF · Release R3 · Specs Field Force & CRM, Claims, Attendance

Context​

The reference product records a photo punch, tracks GPS (point-to-point or continuous) with battery level, shows whether a visit matched the client location, and sends travel records through a separate path (Pending → Verified → Approved → Claimed) where the manager can edit "KM Revised" [Observed] (see Spryple analysis §11 and §21.7). Spyrl adds explicit consent and work-hours-only tracking, filtered distance computation, enforced visit verification and a single reimbursement pipeline in CLM.

Diagram​

Steps​

#ActorActionSystem responseModuleNotifications
1field_executiveFirst use: reads the disclosure and consents to trackingConsent recorded with purpose and retention; can be withdrawnEMP, MOB—
2field_executivePunches in with a selfiePunch stored with location and fence result (client sites allowed by policy)ATT—
3SystemStarts the track sessionSession in point-to-point or continuous mode; on-screen tracking indicatorFFM, MOB—
4Mobile appSends location batches (offline-tolerant)Points stored in monthly partitions with accuracy, speed, battery and mock flagFFM—
5field_executiveFollows the beat plan and checks in at an accountDistance from account computed; MATCHED, NOT_MATCHED or NOT_AVAILABLE; policy blocks, flags or allowsFFMManager alert when flagged
6field_executiveLogs activity, follow-up date, stage change, payment collectedOpportunity and activity updated; lead age resets on stage changeFFMFinance FYI on collections
7sales_managerWatches the live mapPositions, last ping, battery, visits so farFFM—
8field_executivePunches outSession closed; tracking stopsATT, FFM—
9SystemComputes the day's distanceAccuracy, speed and jitter filters; snap-to-road when enabled; gaps flagged; ffm.travel.day_closedFFMExecutive asked to review
10field_executiveReviews and submits (or auto-submit)Daily travel SubmittedFFMTask to manager
11sales_managerVerifies; may revise km with a mandatory reason; bulk verify with selected-records summaryDaily travel Verified; ffm.travel.verifiedFFM—
12SystemCreates a mileage claimClaim with MILEAGE line at the policy rate for the vehicle type; source FFM_TRAVELCLM—
13payroll_managerApproves (the verification step is already satisfied)Claim Approved; reimbursement scheduledCLM, PAY—
14SystemPays with salarySee claim to reimbursePAYEmployee informed

Exception paths​

SituationHandling
Consent withdrawnTracking stops; point-to-point distance from punches and visits only; mileage still possible with manager verification
Location permission off or GPS unavailableApp shows a warning; gap flagged; manager sees it in verification
Mock location detectedPoints dropped; event flagged to the manager
Phone battery diesGap bridged by straight-line distance and flagged
Executive forgets to punch outATT missed-punch rules; session closed at the policy default out-time
Visit outside radius with BLOCK policyCheck-in refused; executive can request an exception that the manager approves
Account has no locationFirst check-in sets it (as observed); manager can correct
Days below the minimum-visit filterTravel not eligible for a claim unless the manager overrides
New phoneDevice approval by manager before tracking and punching are allowed