Catalog item billing

Owned by Dan Franko (Unlicensed)
Last updated: Jun 23, 2016
3 min read

What?

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 can 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

Recurring Billing process

Request Item

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.

Billing Table

Populate this based on a business rule that fires on insert or update of a requested item where the state is closed complete.

Probably Store the batch number in a property and increment when the job runs?

Scheduled Billing(Admin View)

Scheduled Billing(User View)

 

We could also relatively easily give the ability to update the PTAEO information for future billings.  All changes could be tracked as well.

Note : Buttons would need to be removed.

Billing Menu under Self-Service

JSA Transmissions

File to be generated based on unprocessed billing records.  Sent to billing hub via file generated on the mid server and also stored in the instance for research purposes.

Questions

  1. 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?
  2. What happens with exceptions.
  3. What about cancelling a recurring item?

Risks

  1. Workday changes.  Shane Anderson has advised that the safest way to go is the file generation route.