Reviewers (+ link to BA task):
- PM
- Dev
- QA
- PO
- TW
User Story
As a CSP, I want to store my business and payment details in PortaBilling, so that they can be automatically used in invoice templates and eInvoices without requiring manual updates to each template.
Example of use
A CSP has multiple invoice templates configured in PortaBilling. The CSP's bank account details are stored in PortaBilling and used in the invoice templates. The CSP changes its bank account and needs customers to make future payments to the new account. The CSP updates its bank account details once in PortaBilling. All invoice templates and eInvoices that use the CSP's payment details automatically use the updated information. The CSP does not need to manually update each invoice template, and customers receive invoices containing the new, correct payment details.
Business model
Any business model involving invoicing customer
Technology
Current Solution
Current process: The CSP's business identity and banking data are maintained only inside each invoice template's HTML/CSS body as static text (see PortaOne's "Creating an external invoice template" documentation — the template consists of boilerplate HTML plus Template Toolkit variables; there is no built-in variable for bank account or business registration number). Company-level data available today, via My Company > Company info, is limited to company name, base currency, address information, and — under Invoicing and taxation — a tax number and invoice numbering sequence. No field exists for a bank account (IBAN/SWIFT/routing) or a Business Registration Number, even though the same panel already supplies the Company name that appears on every invoice.
Pain points: When the CSP's bank account or registration number changes, an administrator must locate and manually edit every template that mentions it. Templates are easy to miss because there is no single source of truth; a stale account number left in one template can misdirect customer payments. Separately, since eInvoices are not built from a template at all, there is currently no way to include a Business Registration Number and a ban account number on an eInvoice — the field simply does not exist anywhere in PortaBilling today.
Stakeholders and their benefits
Who are the users / whom we bring value to?
| Benefit / Stakeholders | More Comfort | Increased Efficiency | Saves Time | Tighter Control | Replaces Human | Regulatory Requirement |
|---|---|---|---|---|---|---|
| CSP | ||||||
| Sales/marketing of CSP | ||||||
| Resellers / distributors | ||||||
| Network operations / Support of CSP | ||||||
| Developer | ||||||
| 3rd party | ||||||
| End user | ✓ |
Use Cases
Use case #:
Roles:
Preconditions:
Use scenario #
Use scenario #
Wireframes
- This is an optional section.
- Wireframe is a quick illustration of an idea not the prototype itself.
- Key point is that a final prototype might look completely different after the Solution Design stage.