Turn expense workflow friction into measurable improvements with targeted feedback
Responsly connects survey feedback to Abacus so finance teams hear directly from the people navigating expense workflows every day. Satisfaction scores, policy confusion flags, and reimbursement experience ratings land alongside the financial data Abacus already tracks — giving finance ops a complete picture of process health.
Expense management tools capture dollars and receipts. They don’t capture the frustration of a rejected report with no explanation, the confusion around a per diem policy that changed last quarter, or the relief when a reimbursement hits the bank account in three days instead of three weeks. Surveys fill that gap.
Why expense process feedback matters more than compliance data
Finance teams measure policy compliance rates, average approval times, and exception volumes. These numbers describe what happened but not why. A 92% compliance rate looks healthy until a survey reveals that 40% of employees find the policy confusing and simply avoid filing borderline expenses altogether.
Process metrics tell you the system is running. Feedback tells you whether people trust it:
- approval turnaround satisfaction identifies whether stated SLAs match perceived reality,
- policy clarity scores pinpoint which rules generate the most confusion and support tickets,
- and reimbursement experience ratings reveal whether the payout process feels reliable or unpredictable.
When finance teams combine Abacus operational data with Responsly feedback, they can prioritize process improvements that actually reduce friction — not just the ones that look good on a dashboard. For research strategies that surface hidden frustrations, see our guide on qualitative vs. quantitative research.
How the integration works
The Responsly–Abacus integration connects through Abacus webhooks and API credentials configured in the Responsly dashboard.
- Set up a webhook in Abacus — configure Abacus to fire a webhook when an expense report reaches a specific status (approved, reimbursed, rejected).
- Map event data to survey parameters — Responsly receives the webhook payload and uses the submitter email, department, and report ID to personalize and route the survey.
- Respondent matching — survey responses are linked back to the Abacus user by email, so feedback data associates with the correct employee profile.
- Attribute sync — satisfaction scores and category tags sync to the Abacus user record as custom attributes visible to finance admins.
All Responsly question types are supported: NPS, CSAT, star ratings, multiple choice, open-ended text, matrix, and ranking questions.
Expense report approval satisfaction tracking
A mid-size SaaS company with 400 employees sends a two-question survey after every expense report approval: “How satisfied are you with the approval speed?” (1–5 scale) and “Was the outcome clearly communicated?” (yes/no).
After three months of data collection:
- average approval satisfaction was 3.1 out of 5 — well below the finance team’s assumption of 4.0,
- 34% of respondents said the outcome was not clearly communicated, prompting the team to add automated status notifications at each approval stage,
- departments with delegated approvers scored 4.2 on average versus 2.7 for departments routing through a centralized queue.
The finance team restructured the approval chain for the three lowest-scoring departments. Within one quarter, company-wide approval satisfaction rose to 3.9. Explore population identification strategies for targeting the right survey audience.
Reimbursement turnaround time perception survey
A logistics company reimburses travel expenses weekly but receives consistent complaints about slow payouts. They deploy a survey after each reimbursement: “How would you rate the speed of this reimbursement?” and “Did the amount match your expectation?”
The data revealed a perception gap:
- actual average turnaround was 4.8 business days — within the stated 5-day SLA,
- but perceived turnaround averaged “7–10 days” in survey responses because employees counted from submission date, not approval date,
- 28% of respondents reported amount discrepancies, traced to unclear partial reimbursement rules for international per diems.
The company added a confirmation email showing the expected payment date immediately after approval and rewrote the international per diem section of the policy. Reimbursement satisfaction jumped from 2.6 to 4.1 within two months.
Policy comprehension checks for new hires
A financial services firm surveys new employees 30 days after onboarding: a 10-question quiz covering expense categories, receipt requirements, approval thresholds, and prohibited expenses. Scores sync to Abacus as a policy_score attribute.
Results after the first cohort:
- average score was 58% — meaning new hires misunderstood nearly half of the expense policy,
- the lowest-scoring topic was “entertainment expense pre-approval requirements” at 31% correct,
- employees who scored below 50% filed 3.2x more policy exceptions in their first quarter.
The finance team rebuilt the entertainment expense section of the onboarding materials with concrete examples and a decision flowchart. The next cohort scored 79% on the same quiz, and first-quarter exceptions dropped by 44%.
Finance team internal NPS
The CFO runs a quarterly internal NPS survey targeting all employees who filed at least one expense report that quarter: “How likely are you to recommend our expense process to a colleague at another company?” plus an open comment.
Tracking over four quarters:
- Q1 internal NPS was −12 (more detractors than promoters), with top complaints about mobile app crashes and receipt photo quality,
- after the mobile app was updated in Q2, NPS rose to +8,
- Q3 introduced a new international travel policy, and NPS dropped to −4 — the open comments pinpointed confusion about currency conversion rules,
- Q4, after a policy FAQ was published, NPS reached +18.
The quarterly trend gave the CFO a single metric to present to the executive team that summarized process health beyond compliance rates.
Setting up the integration
Configure the Abacus webhook — in Abacus, navigate to admin settings and create a webhook for the report status events you want to trigger surveys (approved, reimbursed, or rejected).
Connect Abacus in Responsly — open your survey’s Integrations tab, select Abacus, and enter your API credentials and webhook endpoint URL.
Map parameters — assign incoming webhook fields (email, department, report_id) to Responsly survey parameters for respondent matching and segmentation.
Design the survey — keep post-approval surveys to 2–3 questions for high completion. Use skip logic to show follow-up questions only when scores are low.
Activate and test — process a test expense report through Abacus, verify the survey is triggered, complete it, and confirm the response appears as a custom attribute on the user profile.
Best practices
Survey at the moment of experience. Send approval satisfaction surveys within hours of the status change, not at the end of the month. Fresh context produces accurate ratings.
Benchmark by department before optimizing. Satisfaction varies wildly across business units. A sales team filing weekly travel expenses has different needs than an engineering team filing occasional equipment purchases. Segment first, then improve.
Track policy changes against satisfaction shifts. Every policy update should have a pre/post satisfaction measurement. This creates accountability for changes that were supposed to help.
Share results with employees, not just leadership. Publishing “You told us the mobile app was frustrating — here’s what we fixed” closes the loop and increases future survey participation. Read more on structuring feedback collection in our guide on close-ended questions.
Start measuring expense process satisfaction
Connect Abacus to Responsly and send your first post-approval survey. Let every expense report generate a data point that helps finance teams build processes people actually trust.
