Business Requirements for <Project Name>

Revision History Description

Revision

Date

Changed By

Intended audience Business Partners, Stakeholders and Sponsors Functional Resources Technical Resources

Also a custom page to go into a BDR and mark it specifically to not bill. Done in combination with pricing rules. if a recording lasted 10 seconds it would state that in the BDR. Thus.0 Dranginis. Dianne Process 2 Incorporated into the design.although would be included in the FTP.0 Dranginis.BUSINESS PROCESS Billing Requirements Ref# Requestor Priority Importance (Weight) Requirements Status Deliverables Acceptance Criteria Business Process Requirements Process 1 Short Term Medium Term Long Term Customer Trial: FTP the BDRs to the customer. (Record the Voyant subscriber ID on the contract definition page. 112. Need a way to 'mark' a BDR to not invoice . Voyant has an account . Will need to be part of contract definition page that is custom. 111.0 Dranginis.used for testing. These transactions should be filtered from the FTP and the invoicing. Dianne 5 4 1 114. but doing Bill Integration testing. 108. Will need to be part of contract definition page that is custom. the way that it is today) Will need to be part of contract definition page that is custom. etc. Dianne 113. Dianne Example: Customer in production.e.0 Dranginis. Dianne 63991417.xls CONFIDENTIAL 07/27/2011 2 of 16 . We round up BDRs to the nearest minute when we bill. but the customer and service provider should be billed for 1 minute. Dianne 109. Dianne Process N For each customer.0 Dranginis. 110.0 Dranginis. Will need to be part of contract definition page that is custom. Minimum Invoice Amount (able to defer when this minimum begins). We will need to identify the Subscriber ID that is tied to Voyant for each customer ('Provider ID'). Ability to customize daily FTP files for each customer Ability to have daily FTPs (from provisioned system to billing system) have different fields sent for each activity (i. BDR's marked to not invoice should include recording a reason as part of 'marking' the BDR to not invoice. Define if this should appear as part of the Bill and also credited or don't appear at all or show at $0.0 Dranginis. but billing (invoicing) is not enabled yet.

0 6.0 Accounting Standard posting process GEN 9. Mobile meeting requirements Need Mobile Meeting Requirements GEN GEN 10. Summarize for journal entry post. We anticipate consolidating BDR records of the same time and the same location.0 GEN 12. discount and tax amount line items Yes.0 Enhanced Services 11. The actual printing of the invoice (statement) would provide the approximately 20 line summary followed by printing the BDR details on subsequent pages.0 Ability to run the billing application on demand INT 4. possibly Future Release. INT 3. Yes GEN 7. Identify Service Provider internal usage of service and media orders. The solution is based on accumulating the BDR records and summarizing them to the invoicing and accounting processes. only those records with subscriber information. we would leverage the standard PS Price Rules to calculate prices.0 Scalable to large quantities of data General GEN GEN 5. Calculate Administration minutes Ability to address current product. In generating the sales order or invoice. but would summarize to approximately 20 invoice lines per customer per month. net. Functional CONFIDENTIAL 07/27/2011 3 of 16 .0 No. custom develop direct billing interface and standard invoice process will do these postings to GL.0 Requirements Status Deliverables Acceptance Criteria Configure new billable evenys from production system Billing usage data is sent to Avante without cost information already attached. Yes. and is not ready to post.0 Accounting Identify records in the database that have been processed for customer billing.0 Accounting Future Release: We will need a method for this indentification and then we can support separate sales/use tax per ship-to and by product classification.0 Enhanced Services Enhanced Services Identify and bill for recordings requiring multiple CDs Provide shipping and tax charges at an item level Function of BDR Susan Sowl to coordinate this issue with Sandra Hahn Future Release: This is a function of how the data is grouped. Need to define a process for getting new billing event messages into PS PeopleSoft custom table would accept the BDR records. Report G/L with gross. Define number of activities I think it won't be a problem. flag these records for sales and use taxing.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements Integration INT 1. only at the accumulated record. Produce one file at the service provider level to input all billing usage information into Avante for use in billing the service provider. but the billing run would be only for those BDR records received to date and pricing would be based on the group of BDR records processed at the same time. Admin: (offhook . contract billing and services billing functionality including Mobile Meeting requirements Link between Siebel and billing system GEN 8.toll free playback) where offhook are Custom process to develop. and for accrued billing. So the BDR records would consume about 3000 records per day (90000 records per month).0 INT 2.0 General Ledger G/L Reporting G/L 13. so that tax would not be at the BDR record.

Functional CONFIDENTIAL 07/27/2011 4 of 16 . These adjustments would have pricing fixed and would be included in the next invoicing cycle (but summarized with other BDR to an invoice line).0 G/L 15. Custom for adjustments to a specific BDR record (billed vs not billed yet).0 19.0 Automated adjustment approval not available.0 Support customer specific rates (prices/contracts) Ability to maintain different payment terms for customers Yes. the consolidation key for billing is only a single level. Adjustments would be made to the BDR record creating a new BDR record that is a credit and/or adjustment. Yes.0 Support for partial and full adjustment in percent or $ amounts Ability to calculate tax on adjustments Ability to tie an adjustment to a line item on a bill ADJ 20.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements G/L 14. A can have B and C as children and B can havd D as a child to it.functional design decision. However. Must be in $ amount. C. B.0 18. Standard. A customer record specifies it's parent.0 3.0 Standard capability for adjustments to an Invoice. and D can consolidate invoices to A. Text could define %.0 Ability to assign reason codes when applying credits. Customer ID will be used to track within PS. and D . ADJ 21. 1. ADJ ADJ ADJ 17. Yes Yes Future Release: This is not clear.0 Requirements Automated load of G/L data (in a JE format) from Billing System to Avante Automated filed upload from Billing System to Avante G/L with unbilled reversal information.B. Ability to store different bill to: and send to: addresses Ability to store customer's credit limit Ability to support a multi-level billing hierarchy and report differently for different customers 4. We can support a multi-level hierarchy of a customer definition.0 Ability to assign a meaningful service provider ID and use that to track customers throughout the system.0 5. Ability to manually enter adjustments Status Deliverables Acceptance Criteria Yes. So customers A.0 2. Credits might need to not be summarized so that they show on the summary page as well as the detail page . Yes Yes. Standard Functionality. Manage Credits/Adjustments ADJ 16. or freeform credits and not be forced to assign codes Ability to enforce an adjustment approval process (only certain user types can approve adjustments) Yes. but bill line items would be summarized BDR records. Will need to be procedural and Enhanced Services to work with Dave Nelson (Dir Credit & Collections) Customer Management Account Creation Custom development to associate service provider ID with internal to system customer ID. C. Yes. Standard. Standard Functionality.

then can be shown as backlog.5 Future Release: Web access by service provider to see current charges on-line. Yes Only to summarized BDR Level. Miscellaneous Adjustments 23.0 17.0 22.0 13. If created as an order and not fulfilled yet. Orders can also be entered in Pending status.0 Ability to store pending status CD/transcripts and dates for products for an account Future Release: BDR to carry status that it is 'pending'. each G/L Breaks account revenue balance down a duringby product. as adjustments to BDR are created in the BDR records on PS Side. The discount defintion would have all of the customers tied to it. and D. Greater detail is tracked in our RevFlash reporting soln.0 Ability to easily modify service information Ability to store contract number. by Includes geographical productsof location whether or accounts. So a discounting rule could apply to only A or also to A. adjustments product. Design of customization will determine how easily. and Crystal Reports Accounts Receivable 11.0 20.0 Requirements Ability to apply discounts throughout customer hierarchy Status Deliverables Acceptance Criteria Future Release: Sort of. B. Change pricing.0 21.0 15. 10. Yes Only to summarized BDR Level. PO number for VRAP contracts and associated PO's for Professional Services Ability to view current charges on-line by service provider Reporting out of PS. Yes 8. Order Management 7. If can be supplied. General Ledger . Reporting can be provided through: PS Query.Chart of Accounts General Ledger Summary General Ledger Detail Product Revenue Yes Yes Yes The level of detail that company is willing to track.0 9.0 General Ledger 19. then would want to include non-billable events so that all reporting from one place. not they have a G/L CONFIDENTIAL 07/27/2011 ID.0 Accounts Receivable Summary Accounts Receivable Detail Payments Summary Payments Detail Reversals Summary Reversals Detail Refunds Summary Refunds Detail Payments Summary Payments Detail Reversals Summary Reversals Detail Refunds Summary Refunds Detail Lists all the G/L Shows the accounts in summary the Infranet impact on database.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements 6. Yes Only to summarized BDR Level. Reqmt: Add new types of BDRs.0 Miscellaneous Adjustments Summary Yes.0 12. Functional 5 of 16 .0 14.0 16. Yes Only to summarized BDR Level.0 18. Business Objects.0 Reports 10. specified showing time period total debit by resource Shows revenue for and then by credit each G/L ID. C. but if these come from the BDR there is no support for this.

Monthly fee per site.0 27.0 31.0 34.0 35. current charges throughout the month Define details Define details Define details Need details Need details Fulfill through RevFlash reporting. shows the accounts. (Private numbers) Functional CONFIDENTIAL 07/27/2011 6 of 16 . as adjustments to BDR are created in the BDR records on PS Side.Multiple Periods New Account Lifetime Closed Account Lifetime Std Std Std Std Billing Billing Cycle 37. Account Changes . and closed accounts. monthlyfor service change in period. Deliverables Acceptance Criteria Yes. 41.g. Could force to replicate pricing functionality offline. Recurring Charge for Private#. shows Shows the event-level number of debit and accounts credit Shows the created or adjustments. separate invoices for different services if desired Ability to run billing application on demand 40. consolidated invoice per billing cycle for customers.0 Misc 33. annually. 38. Private# Dropped. Standard Can do both.0 36.0 26.) This can be setup.0 Enhanced Services Support minimum and maximum charge amounts verify that minimum charge has been met 1 Custom Development. (Perhaps pricing as if through this date. Mobile Meeting .Ability to view unbilled usage. serviceafor during the Shows and new shows weeklyof the net or length accounts. Site Decommissioned. If so. but would only obtain invoices for BDR records delivered to date and pricing will be based on the BDR records accumulated for a single invoice (not across invoices).Site Commissioned.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements 24.0 32.0 Tax 29. Possible to create such a report. monthly.0 39.0 Subscriber Accounts 25.Single Period Account Changes .0 Future: Yes. Need specific requirements of changes Need specific requirements of changes Part of setup of contract Part of maintenance of contract.0 30. net change in accounts by period.off current orders and long term forecast report Voyant Sales Report Pre-Billing Report .0 28.0 ? Support modifications to existing products / service 1 offerings/ prices and quote modifcations Produce single. quarterly. number of closed accounts during a Shows the created or specified length of closed time period. Examples: VRAP Private# Private# Provisioned. might as well pass directly to Billing Interface. Tax Jurisdiction Summary Tax Jurisdiction Detail Summary of all Taxes Tax Exempt Accounts Requirements Miscellaneous Adjustments Detail Status For each customer account.0 Orders Report Forecast report .0 Ability to manage and bill for recurring charges for various cycles e.

outstanding balances. Load BDR records can be configured for how frequently loaded.0 51. Ability to interface with Tax software 1 Future: Yes Support Lockbox (electronic bank file) for checks payment processing Support for credit card processing for payment 1 nice to have Yes Could Functional CONFIDENTIAL 07/27/2011 7 of 16 . 52. previous payments. Future: Need info on this.0 Taxes Calculation 49. but only one billing cycle per customer. Future: Yes Future: Tax is calculated at time of invoicing. Std is No. How to handle transition month of 16th through 31st? Don't expect to need this initially.. Standard through Taxware. and change 1 if needed Status Deliverables Acceptance Criteria Future: Explained under customer mgmt. but at the invoice level . Need to determine impact on volume discounts and prorating if change from a cycle of 16th through 15th to 1st through 31st.0 Ability to support FCC taxing ? 53.0 Enhanced Services Enhanced Services Ability to have multiple billing cycles Automatic bill back-out capabilities Ability to obtain usage from multiple collection points on a daily (configurable) basis System must store information that supports a service business: running total of charges.0 Manage Payments Payment Processing 56.0 44. Standard capability is a credit/rebill.0 Interface 55. payment due date.0 46. Only through the consolidation key. This is information in the AR system.0 1 Ability to automatically calculate tax based on jurisdiction and product or link to tax table product 1 Ability to automate tax calculations during bill generation or at time charge is assessed Ability to tax for sales/use taxes on products and recording/playback services on an individual item level. We will accumulate by type of BDR into a single invoice line item (scalability) and report details from the BDR custom data storage. 1 Yes. Future: Yes.not details.0 50. Standard.0 Ability to support tax exemptions Support Sales & Use Tax Reports 1 1 Yes.0 Enhanced Services Requirements Ability to support a multi-level billing hierarchy Ability to pull all open credits/adjustments into an invoice Ability to set the default billing frequency.0 54. etc. Future: No. Need explanation on multiple collection points.0 47. 45. 48. Reqmt is when and if service is sold directly to end users. We will build that into the contract definition page. Multiple means across multiple customer. No automatic back-out.0 57.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements 42.0 43.

and allocation purposes Ability to associate usage/transaction charges with products/services Ability to associate time and expenses for professional services Ability to assign start and end dates to pricing of products/services by contract basis Ability to have flag for renewal that can be managed Ability to assign start and end dates to product/service rates 1 1 Aggregation can be supported. 71.0 69. This is on the BDR record.0 64. Yes. calculation and allocation of 1 non-recurring and recurring charges based on customer's products/services Ability to assess shipping charges on an item 1 basis Ability to maintain and bill for services on a prorated basis .(specifically for private numbers) Support advanced customer account hierarchy processing for rate/discount aggregation.0 Functional CONFIDENTIAL 07/27/2011 8 of 16 . 67. but contracts won't suffice for these other requirements.0 Effective Dates 73.0 Accounting/ Enhanced Services 70.0 Price Plans Requirements Ability to receive payment via Electronic Fund Transfer 1 Support manual payment posting Support to apply business rules to assess penalties. Yes Custom development 1 Assuming that we generate statements.0 59.0 Enhanced Services 1 1 Yes Yes 1 Part of definition of custom contracts page (it is std in contracts. calculation.0 Support customer-specific rates 66. yes. Yes 68.0 Interface 63. but contracts won't suffice for these other requirements.0 See customer information and above.0 Late Payments 60.pre invoice creation. interest fees and cancellation fees Ability to determine if a customer underpaid or overpaid through statements Ability to post payment by bill number Ability to interface for EFT requests Ability to interface with lockbox 1 1 Status Deliverables Acceptance Criteria I don't think we are doing this yet.0 72.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements 58.0 1 Capability for tiered.0 75. threshold. but system does support it. Need examples to understand requirements. Yes Rate Application/Rating Rules 65. Standard in price rules. volume and headquarters discounting and view on the bill Support aggregation.0 Accounting/ Enhanced Services 1 Yes Need examples to understand requirement. Part of definition of custom contracts page (it is std in contracts. 74.0 Under/Over Payments 61. Calculation and allocation would need custom development . 1 1 1 Yes I don't think we are doing this yet. but system does support it.0 Additional Payments 62.

Recurring Charges.0 86. Yes Yes Yes Yes Through Notes Custom development. Support line item product name/description on invoice 1 Ability to send/not sendpaper copy of invoices to all customers regardless of payment method Ability to display $0 balances on invoice for free periods/promotions 1 97.0 88. but recommend varying formats on an exception basis.0 1 Yes Yes No. Yes. use of a GUI interface to accomplish this Ability to display previous amount due.0 93.not invoices. Services.0 Ability to produce different invoice formats for each customer.0 91. Through price rules. Custom 'Statement' Development 78. but we can do so.0 83.0 96.0 87. My definition of line item is the aggregated BDR by location.0 81. Qty breaks can be defined by a different discount.0 77.0 89. total current amount due Ability to display sub-totals and adjustments Ability to display discounts on the invoice Ability to display taxes on the invoice. not directly on order/invoice. previous payment.. Use Statements . but Yes 84.0 92. Products) by billable item Ability to display payment terms Ability to display the period-covered dates on the invoice Yes Not a GUI interface for invoice format creation.0 95. Different invoice formats can be supported. Don't Standard in price rules charge for a particular service withina period. suppress the record if the qty of the service is $0.0 79. This will take some thinking on how to setup so that existing contracts are not changed with price list changes.0 Ability to discount by a percentage On invoice. but include the record if the qty != 0 but the price/amount is $0.100% discount. Yes Usually not. Easily maintainable product and price list Modifications to price list do not change customers with pre-existing contracted prices 1 Manage/Administration 80.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements Requirements Status Deliverables Acceptance Criteria Promotions and Discounts 76. aggregated per bill and displayed by line item Ability to display the invoice date on the bill Ability to display customer id on the bill Ability to display contract number Ability to display PO number with associated invoice line items for professional services Ability to display variable messages on invoices Ability to sort the bill sections (i.e.0 1 1 You be the judge of how easy it is.0 Enhanced Services Accounting Accounting Accounting 1 1 1 1 1 1 1 Accounting 94.0 Yes Functional CONFIDENTIAL 07/27/2011 9 of 16 . not each BDR. Invoices Content 82. We can throw invoices away though.0 90.0 85.0 Ability to manage product and service discounts Ability to support promotions 1 1 Standard in price rules Example: 90 day free trial .

Yes. This will include the Subscriber Report with the operational billing information at various levels mentioned above.0 Not in whatever grouping is desired.0 Delivery Method 104.0 Enhanced Services Need specs on the Subscriber Report.0 Additional Requirements Content Support for perforated remittance slips 1 Future: No. recording id level and activity level. but 108. Done in combination with pricing rules. the way that it is today) Discount Periods Will need to be part of contract definition page that is custom.0 Dranginis. Status Deliverables Acceptance Criteria Need specs on the Subscriber Report (detailed pages of Invoice/Statement). Dianne billing (invoicing) is not enabled yet. Will need to be part of contract definition page that is custom. 99.0 Dranginis. Dianne Ability to customize daily FTP files for each customer Ability to have daily FTPs (from provisioned system to billing system) have different fields sent for each 114.0 Dranginis.0 Enhanced Services Requirements Ability to provide the Subscriber Report at top-line detail service provider. Yes. Incorporated into the design. subscriber detail level.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements 98. 101. but not using this yet. but not implemented yet. until volume warrants this.0 107. (detailed pages of Invoice/Statement).0 105. with the correct charges associated with it. with invoice dollars associated with it. depending on customer request. recording id level and activity level. 100. Ability to provide invoice support pages 2 . Invoices must provide information to support a service business: show a running total of charges.0 Acounting Through Statements 102. subscriber detail level. etc. Functional CONFIDENTIAL 07/27/2011 10 of 16 . previous payments. (detailed pages of Invoice/Statement). Minimum Invoice Amount (able to defer when this 109. In a specified grouping that gets defined.0 106. in whatever grouping desired.0 Dranginis. outstanding balances. 1 Customer Trial: FTP the BDRs to the customer. 103.\ Ability to produce paper invoices Ability to send electronic fund transfer with invoice amount Ability to web interface with query commands Ability to send e-mail of invoice 1 1 Yes Yes.e. Dianne minimum begins). Dianne activity (i. payment due date..500.0 Enhanced Services Need specs on the Subscriber Report. Ability to group services and products together. depending on customer request Ability to provide the Subscriber Report at top-line detail service provider. 113.

Need a way to 'mark' a BDR to not invoice . For each customer.FUNCTIONAL BUSINESS REQUIREMENTS Billing Requirements Ref# Requestor Functional Requirements Requirements Status Deliverables Acceptance Criteria Example: Customer in production. Thus.0 Dranginis.used for testing.although would be included in the FTP. (Record the Voyant subscriber ID on the 111. Define if this should appear as part of the Bill and also credited or don't appear at all or show at $0. Rounding We round up BDRs to the nearest minute when we bill. Dianne reason as part of 'marking' the BDR to not invoice.0 Dranginis. a Will need to be part of contract definition page that is custom. Voyant has an account . etc. These transactions should be filtered from the FTP and the invoicing. Functional CONFIDENTIAL 07/27/2011 11 of 16 . We will need to identify the Subscriber ID that is tied to Voyant for each customer ('Provider ID'). Dianne should be billed for 1 minute. BDR's marked to not invoice should include recording 110. but the customer and service provider 112. Dianne contract definition page.0 Dranginis. if a recording lasted 10 seconds it would state that in the BDR. Will need to be part of contract definition page that is custom. Also a custom page to go into a BDR and mark it specifically to not bill. but doing Bill Integration testing.

etc. 111. Dianne 109. but doing Bill Integration testing. the way that it is today) Will need to be part of contract definition page that is custom. We round up BDRs to the nearest minute when we bill. BDR's marked to not invoice should include recording a reason as part of 'marking' the BDR to not invoice. Minimum Invoice Amount (able to defer when this minimum begins). Thus. Done in combination with pricing rules. Define if this should appear as part of the Bill and also credited or don't appear at all or show at $0. Dianne Customer Trial: FTP the BDRs to the customer. Also a custom page to go into a BDR and mark it specifically to not bill. if a recording lasted 10 seconds it would state that in the BDR. Dianne Example: Customer in production. Dianne 113. 112. Dianne 63991417. but billing (invoicing) is not enabled yet. Need a way to 'mark' a BDR to not invoice .although would be included in the FTP.0 Dranginis. Dianne Discount Periods Incorporated into the design. Ability to customize daily FTP files for each customer Ability to have daily FTPs (from provisioned system to billing system) have different fields sent for each activity (i.used for testing.0 Dranginis. 110.0 Dranginis. Will need to be part of contract definition page that is custom.0 Dranginis. Will need to be part of contract definition page that is custom.e. but the customer and service provider should be billed for 1 minute. Voyant has an account .0 Dranginis. Dianne Rounding For each customer. These transactions should be filtered from the FTP and the invoicing.INTEGRATION Billing Requirements Ref# Requestor Integration Requirements Content Requirements Status Deliverables Acceptance Criteria 108. (Record the Voyant subscriber ID on the contract definition page.xls CONFIDENTIAL 07/27/2011 12 of 16 . Will need to be part of contract definition page that is custom. We will need to identify the Subscriber ID that is tied to Voyant for each customer ('Provider ID').0 Dranginis.0 Dranginis. 114.

0 Dranginis. Need a way to 'mark' a BDR to not invoice . Dianne 63991417. Will need to be part of contract definition page that is custom. Done in combination with pricing rules. Will need to be part of contract definition page that is custom. BDR's marked to not invoice should include recording a reason as part of 'marking' the BDR to not invoice. These transactions should be filtered from the FTP and the invoicing. Dianne 114.0 Dranginis. Voyant has an account used for testing. Dianne 113.xls CONFIDENTIAL 07/27/2011 13 of 16 . 109. Dianne Example: Customer in production. We round up BDRs to the nearest minute when we bill. Dianne Customer Trial: FTP the BDRs to the customer. but the customer and service provider should be billed for 1 minute. the way that it is today) Will need to be part of contract definition page that is custom. We will need to identify the Subscriber ID that is tied to Voyant for each customer ('Provider ID'). Define if this should appear as part of the Bill and also credited or don't appear at all or show at $0.e.0 Dranginis. etc. For each customer. Dianne Etc. Will need to be part of contract definition page that is custom. but doing Bill Integration testing.0 Dranginis. but billing (invoicing) is not enabled yet.although would be included in the FTP. 111.0 Dranginis. Minimum Invoice Amount (able to defer when this minimum begins). 112. if a recording lasted 10 seconds it would state that in the BDR. Dianne Schedule Frequency Incorporated into the design. Also a custom page to go into a BDR and mark it specifically to not bill. (Record the Voyant subscriber ID on the contract definition page.0 Dranginis.SYSTEM PERFORMANCE Billing Requirements Ref# Requestor System Performance Requirements On-Line Response Requirements Status Open Issue PeopleSoft Capability 108. 110. Ability to customize daily FTP files for each customer Ability to have daily FTPs (from provisioned system to billing system) have different fields sent for each activity (i. Thus.0 Dranginis.

Dianne Security Incorporated into the design. Will need to be part of contract definition page that is custom. We round up BDRs to the nearest minute when we bill.xls CONFIDENTIAL 07/27/2011 14 of 16 .0 Dranginis. BDR's marked to not invoice should include recording a reason as part of 'marking' the BDR to not invoice. We will need to identify the Subscriber ID that is tied to Voyant for each customer ('Provider ID'). Dianne 113. Also a custom page to go into a BDR and mark it specifically to not bill. (Record the Voyant subscriber ID on the contract definition page. Voyant has an account used for testing. but the customer and service provider should be billed for 1 minute. but doing Bill Integration testing. Define if this should appear as part of the Bill and also credited or don't appear at all or show at $0. For each customer. Minimum Invoice Amount (able to defer when this minimum begins).0 Dranginis.0 Dranginis. Dianne Customer Trial: FTP the BDRs to the customer. 111. Security. but billing (invoicing) is not enabled yet. if a recording lasted 10 seconds it would state that in the BDR. Thus. CONTROL Billing Requirements Ref# Requestor Audit. Will need to be part of contract definition page that is custom. 112.e. etc.0 Dranginis. 110.although would be included in the FTP. 109. Done in combination with pricing rules.0 Dranginis. Dianne 63991417.0 Dranginis.0 Dranginis. SECURITY. the way that it is today) Will need to be part of contract definition page that is custom. Need a way to 'mark' a BDR to not invoice . & Control Requirements Audit Requirements Status Open Issue PeopleSoft Capability 108. Dianne 114. Dianne Control Will need to be part of contract definition page that is custom. Dianne Example: Customer in production.AUDIT. These transactions should be filtered from the FTP and the invoicing. Ability to customize daily FTP files for each customer Ability to have daily FTPs (from provisioned system to billing system) have different fields sent for each activity (i.

Will need to be part of contract definition page that is custom. We will need to identify the Subscriber ID that is tied to Voyant for each customer ('Provider ID'). Will need to be part of contract definition page that is custom. Minimum Invoice Amount (able to defer when this minimum begins). Also a custom page to go into a BDR and mark it specifically to not bill. but doing Bill Integration testing. 110. Ability to customize daily FTP files for each customer Ability to have daily FTPs (from provisioned system to billing system) have different fields sent for each activity (i.0 Dranginis. Dianne 114. Voyant has an account used for testing. 63991417. BDR's marked to not invoice should include recording a reason as part of 'marking' the BDR to not invoice.e. For each customer. These transactions should be filtered from the FTP and the invoicing. Dianne Subsject Area 2 Incorporated into the design. Dianne Customer Trial: FTP the BDRs to the customer.0 Dranginis. Done in combination with pricing rules. 109. etc.0 Dranginis. Define if this should appear as part of the Bill and also credited or don't appear at all or show at $0. the way that it is today) Will need to be part of contract definition page that is custom.0 Dranginis. 111. Dianne 113.although would be included in the FTP. Dianne Example: Customer in production.xls CONFIDENTIAL 07/27/2011 15 of 16 .0 Dranginis. Need a way to 'mark' a BDR to not invoice . Dianne Will need to be part of contract definition page that is custom. (Record the Voyant subscriber ID on the contract definition page. but billing (invoicing) is not enabled yet.EXCLUSIONS Billing Requirements Ref# Exclusions Subject Area 1 Requestor Exclusions Status Open Issue PeopleSoft Capability 108.0 Dranginis.

Acceptance & Signoff Warren Baxley [Print] Sign Date John Duane [Print] Sign Date Robert Hagen [Print] Sign Date George Lantz [Print] Sign Date Randy Schultz [Print] Sign Date Paula Casey [Print] Sign Date Dave Nelson [Print] Sign Date Neil Dickson [Print] Sign Date Jeremy Anderson [Print] Sign Date 63991417.xls CONFIDENTIAL 07/27/2011 16 of 16 .

Sign up to vote on this title
UsefulNot useful