Client: TelcoCore · Telecom & Manufacturing · EU telecom BSS provider (260 staff)
Reducing the Backlog on a Telecom Billing Platform
TechSupport Team maintained TelcoCore’s Java and Oracle telecom billing platform. Over four months, client Jira records show the backlog falling from 900 to 120 tickets and invoicing defects from 31 to 4 per quarter.
Client and engagement facts
- Client
- TelcoCore
- Industry
- Telecom & Manufacturing
- Business context
- EU telecom BSS provider (260 staff)
- Delivery model
- Software maintenance
- Application
- Telecom BSS with invoicing and batch
- Supplied geography
- EU
- Company size in source
- 260 staff
Related services: Software maintenance
Application stack and tools
Application stack
- Java
- Oracle
- Kubernetes
- Azure
Tools used
- Jira
- Azure DevOps
- Snyk
Why Support Was Needed
Slow batch runs caused cutoff errors, and rounding bugs contributed to invoice defects. The team handled both the batch redesign and regression coverage for invoice calculations.
Technical Work
- Fixed invoice rounding causing half of the defect count.
- Rewrote the batch to run parallel with a checkpoint pattern.
- Added a regression test for invoice rounding.
Representative Incident
Two tickets depended on an Oracle vendor patch. The engineers shipped workarounds and recorded the outstanding dependencies and accepted risks for review.
Results and how they were measured
| Metric | Baseline | Result | Units | Measurement window | Source and scope |
|---|---|---|---|---|---|
| Backlog | 900 | 120 | 4 months | Client Jira | |
| Invoice defects | 31/q | 4/q | /q | 4 months | Client Jira |
| Batch runtime | 7.5 h | 2.1 h | h | 4 months | Client Azure DevOps |
Evidence and Limitations
The four-month comparison excludes two vendor-patch tickets. Jira tracked backlog and defects. Azure DevOps supplied batch runtime.
Vendor Patch Dependencies
The team recorded accepted risks and workarounds for quarterly review.
Scope a Similar Engagement
Share the billing batch window, recurring invoice defects and vendor-owned dependencies. Request a support plan or explore software maintenance.
Get a technical support plan
Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.
- We reply by email.
- We agree a call about the roles, your stack and the hours.
- If there is a fit, we propose engineers after an assessment.