...
We need a way to be able to bill for Request Items that people need to pay for. The general idea is to mark those items as billable, set one-time and/or recurring pricing and frequency and send these transactions off to our billing system so money changes hands. We plan to interface with a system that can create billing hub or JSA files for us so that we can simply make a web service call during our recurring processcan either generate a billing file and transmit it via SFTP by ourselves or integrate with something like WebMethods to insert the data into the correct place.
Order and Billing Insert Process
...
Have the ability to split the charge across X number of PTAEOs. Not sure if there's an actual or practical limit we should apply. We would also use some real-time validation on this value.
Request items have options for whether or not they're billable, one-time and recurring pricing and frequency.
...
- Should we try and find some mechanism where people can request to cancel a service they're paying for on a recurring? Maybe something simple like a link to an incident against the business service that they have a charge against?
- What happens with exceptions.
- What about cancelling a recurring item?
Risks
- Workday changes. Shane Anderson has advised that the safest way to go is the file generation route.