Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gliffy
nameNightly 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.

Image Added

Request items have options for whether or not they're billable, one-time and recurring pricing and frequency.

...

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

Image RemovedImage Added

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

Scheduled Billing(Admin View)

Image RemovedImage Added

 

Scheduled Billing(User View)

Image Removed 

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

Image Added

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.

Image Added

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?