Reimbursement requests should be this easy.
A government agency needed extensive documentation to provide cell phone reimbursements to on call personnel. Regulations tied the finance department to complex requirements.
Usually we can't change what kind of documentation is needed, but requirements without guidance result in wasted time and effort. Excel workbooks and PDF forms might make things explainable, but what if the process is just too difficult?
We needed copies of cell phone bills, and the information they contained, but each provider has a different lexicon and format.
Excel is great for math, but it's not a user friendly experience. Especially when you have to copy the results into another form.
This sounds like a job for a Service Portal!
They said this had been tried before, but the process and form requirements were too complex to be made user friendly with existing ERP and CRM tools.
More agile tools were clearly needed to meet the demand of this regulatory process.
It looks like you're building a Service Portal...
I built Routine Reimbursements as a scoped application, which handles complex business logic around reimbursement policies.
Presented to users as a custom Service Portal, Routine Reimbursements replaces complicated, multi-sheet Excel workbooks and PDF forms with an input-driven page.
Guided with real world samples of cell phone bills from Sprint, T-Mobile, AT&T, and Verizon, users no longer have to guess what carrier term translates to which form field.
With the math and checking done in ServiceNow, the finance team has a higher level of assurance in the reimbursements they provide, and a real audit history that scales with business.