Conference Billing

Author(s)

• Bishwanath Jana
• Saptarshi Mukherjee

Last Updated Date

2024-10-01

---

Version History

Version	Date	Changes	Author
1.0	2024-10-01	Initial draft	Bishwanath Jana, Saptarshi Mukherjee

---

Feature Overview

Objective:
This feature introduce generation of conference billing, allowing users to efficiently select customers and streamline the invoice generation process for conference-related services. Currently, the system supports fixed, adhoc, and usage-based billing; this new addition will enhance user functionality by enabling invoice generation specifically for modules containing 'Conference' in their name. With this feature, users can generate and preview invoices, improving productivity and simplifying the management of conference billing operations.

Scope:
The scope of this feature includes identifying and filtering conference-related data based on the payload flag, modifying API responses to include only relevant data, and generating an invoice preview for the filtered data.

Dependencies:

• The isConferenceBilling flag must be included in the frontend payload.
• Data modules should have a naming convention that includes "Conference" for related items.
• Existing APIs should support filtering based on the isConferenceBilling flag.

---

Requirements

1. The feature must filter data based on the isConferenceBilling flag in the payload.
2. If isConferenceBilling is set to true and invoice type is fixed , the API should only return data where the module name contains the word "Conference".
3. The invoice preview should include a breakdown of only conference-related items.
4. If isConferenceBilling is set to false or not provided, the feature should return based on the invoice type.
5. The response must include metadata and detailed invoice information for conference-related items when filtered.

---

Design Specifications

• UI/UX Design:
  There are no direct UI/UX changes for this feature, as it is primarily backend-driven. However, the frontend should be aware of the isConferenceBilling filter and display the appropriate data accordingly. Additionally, an extra dropdown field labeled 'Conference Billing' will be introduced, guiding users to select this feature for generating conference-related invoices. Unlike the standard invoice generation process, where only the buildings tagged to a selected customer are displayed, the conference billing feature will display all available buildings, providing users with broader visibility and flexibility during invoice generation.

• Data Models:
  The feature leverages existing data models but applies filtering logic based on the isConferenceBilling flag.

  Development Tasks & Estimates

(Break down the development process into smaller tasks and provide time estimates for each.)

No	Task Name	Estimate (Hours)	Dependencies	Notes
1	Frontend development	3.5 to 4 hours	Biswanth Jana	This depedency for api needs allow the bool field
2	Check if the bool field is true or false	3 hours	NA	Send output based on the boolean value
Total		7 hours

Testing & Quality Assurance

(Outline the testing strategy and quality assurance measures for the feature.)

• Integration Tests:
  Need to list out the customers and building which will have conference billing feature . Then need to genereate the invoice for conference billing and check the amount . Make sure property only with conference billing will be shown .

• Acceptance Criteria:

• Testing Tools:

• Rollout Plan:
  This will be in test server until next release. After succesfully testing in test server it will be release (expected last week of october)

  Review & Approval

• Reviewer:
  Ayon Das

• Approval Date:
  2024-10-04