job-automatic-statement
Scheduled console job that generates and sends periodic account statements to business customers per operating company, via a pipeline of back-office, documentation and mail-template service calls.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | TC.MaintainanceTools.SimpleJobs 4, TPL Dataflow |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2025-06-27 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Payments and finance (system generated; curate in repo-owners.json to override) |
| Product area | Phenix |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 2 release pipeline(s): \finance\jobs\job-automatic-statement Dev; \finance\jobs\job-automatic-statement Release |
| Integration | wcf, rest |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
kernel Bound into the core by 2 mechanism(s).
- Pinning dependency: mailtemplate-service
- Speaks WCF (client)
Detaches when its pinning dependencies are cut or multi-targeted (mailtemplate-service); and when its WCF surface gains a modern interface or its WCF calls move to one.
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
Ready with guardrailsClose: the deployment path exists, but specific checks are needed first, typically raising tests, auditing serialized data, or respecting a shared schema with expand and contract. Test coverage is thin; ZDD shifts the safety net onto automation.
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
job-automatic-statement
Purpose
Finance batch job that runs a statement pipeline per business customer: create statement, look up salesperson info, generate documents, and send them. Separate launcher scripts exist per operating company (UK, Ireland, NL, BE, Dubai, Australia, South Africa), each running the same exe with different settings.
Tech stack
C# on .NET 8 (console exe) split into a host project, a Core pipeline library using TPL Dataflow with retry decorators and step recording, and a test project. Built on the internal TC.MaintainanceTools.SimpleJobs framework with Microsoft DI and Scrutor.
Deployment
Two release pipelines (\finance\jobs\job-automatic-statement Dev and Release) fed by one build pipeline (build.yaml, shared templates v1.0; note the pipeline still requests the 6.0.x SDK while the project targets net8.0). Per-environment appsettings files for testqa through production.
Dependencies
Internal: TC ConnectionBroker incl. WCF broker (tc-connectionbroker), TC.Exceptions clients (tc-exceptions), mail template contract (mailtemplate-service), booking documentation contract (backoffice-documentation-booking), user account client (backoffice-useraccount-service), and back-office/contact-centre services via TC.Phenix.Services.Client (backoffice). No third-party service dependencies found.
Data stores
None directly; statements and customer data flow through the upstream services.
Integration points
WCF clients through ConnectionBroker.Wcf plus REST/API broker clients. No message bus.
Code health
Reasonable test suite for a job (pipeline tests, fakes for the WCF broker, dependency tests). CI in place. Last commit 2025-06-27 — maintained, though quieter than its invoice sibling.
Modernisation risks
Already on modern .NET 8, so runtime risk is low. Main risks are coupling to legacy WCF endpoints on upstream services (it can only be as modern as they are), the pipeline SDK-version mismatch (6.0.x vs net8.0), and per-company config sprawl across seven launcher scripts that makes onboarding new operating companies manual.