Billing Transformation Program
Modernization initiative replacing manual, file-based billing with an automated API-driven billing architecture — improving accuracy, reducing cycle time, and strengthening financial controls.
Project scores, gaps, and coaching guidance.
Detect missing requirements and coverage holes.
Trace requirements to artifacts and tests.
Business Rules(25)
IF-THEN business rules governing pricing, validation, tax, credits, and security.
3 business rules are in OPEN status and require workshop resolution before architecture can be finalized.
| ID | Category | Rule | Status |
|---|---|---|---|
| BR-PRC-001 | Pricing | Active Contract Required for Billing A customer account shall be billed only when an active contract exists in Salesforce on the billing date. | Approved |
| BR-PRC-002 | Pricing | Use Most Recent Approved Pricing Pricing shall use the most recent approved price list effective on the billing date. | Approved |
| BR-PRC-003 | Pricing | Volume Tier Pricing Volume-tier pricing shall be calculated on aggregate monthly usage per contract. | Approved |
| BR-PRC-004 | Pricing | Proration for Mid-Period Activation Mid-period contract activations shall be prorated to the day. | Approved |
| BR-PRC-005 | Pricing | Currency Conversion at Billing Date Non-USD invoices shall use the FX rate published on the first business day of the billing period. | Approved |
| BR-THR-001 | Contract Threshold | Manual Review Above Threshold Invoice line items exceeding $TBD shall be flagged for manual review before invoice release. | Open |
| BR-THR-002 | Contract Threshold | Tier-Based Approval Required Invoices above $TBD per customer per month require Director-level approval. | Open |
| BR-THR-003 | Contract Threshold | Contract Cap Enforcement Cumulative billings shall not exceed the contract value cap without renewal. | Approved |
| BR-THR-004 | Contract Threshold | Minimum Commit Enforcement Customers below minimum monthly commit shall be billed the commit amount. | Approved |
| BR-TAX-001 | Tax | Tax Calculated by Customer Ship-To Jurisdiction Tax shall be calculated based on the customer ship-to address jurisdiction. | Approved |
| BR-TAX-002 | Tax | Tax Exemption Certificate Honored Customers with valid tax exemption certificates shall not be charged tax for applicable jurisdictions. | Approved |
| BR-TAX-003 | Tax | Composite Jurisdiction Resolution Where ship-to crosses multiple tax jurisdictions, the controlling jurisdiction shall be determined by [TBD method]. | Open |
| BR-TAX-004 | Tax | Tax Audit Trail Retention Every tax calculation shall be logged with engine version, rule version, jurisdiction, and timestamp. | Approved |
| BR-TAX-005 | Tax | Reverse Charge for Cross-Border B2B Cross-border B2B transactions shall apply reverse-charge mechanism per destination country rules. | Approved |
| BR-CRD-001 | Credits | Credit Memo Approval Required Credit memos shall require approval by a user with Billing Manager role or higher. | Approved |
| BR-CRD-002 | Credits | Credit Application Order Credits shall be applied to oldest open invoices first. | Approved |
| BR-CRD-003 | Credits | Write-Off Threshold Outstanding balances under $10 shall be auto-written off at fiscal year-end. | Approved |
| BR-VAL-001 | Validation | Mandatory Customer Data Invoice shall not generate unless customer record has name, billing address, and tax ID (where required). | Approved |
| BR-VAL-002 | Validation | Duplicate Invoice Prevention Duplicate invoices (same customer, period, amount) shall be blocked. | Approved |
| BR-VAL-003 | Validation | Negative Line Item Block Negative line items shall not appear on invoices — credits issued separately. | Approved |
| BR-VAL-004 | Validation | GL Account Mapping Required Every product code shall have a mapped GL account before invoicing. | Draft |
| BR-SEC-001 | Security | Role-Based Billing Modification Only users with Billing Editor role or higher may modify invoice amounts. | Approved |
| BR-SEC-002 | Security | Segregation of Duties for Release The user who modifies an invoice shall not be the user who releases it. | Approved |
| BR-SEC-003 | Security | Full Audit Logging Every invoice change shall be logged with user, timestamp, before/after values. | Approved |
| BR-SEC-004 | Security | Quarterly Access Review Billing system access shall be reviewed quarterly by IAM Governance. | Approved |