H2ALL / FastLink
Enterprise ERP/logistics experience focused on reporting, reconciliation, finance-related logic, import workflows, and backend-oriented tracing in a large modular WinForms + services environment.
Supported outcomes in key areas include ~40% faster report runtime, ~30% lower query cost, and safer handling of 30k+ rows in heavy report/search flows.
Overview
H2ALL / FastLink is a large, long-lived enterprise logistics ERP/platform supporting end-to-end operations. My work was not ownership of the full platform. I worked on assigned finance, import, reporting, and reconciliation workflows inside that broader system, with emphasis on correctness, maintainability, and enterprise code tracing.
Assigned Scope
Finance-related workflows, import operations, reporting, reconciliation, and workflow-heavy business modules.
System Direction
WinForms/WPF client work tied to WCF, Web API, internal wrappers, business logic, and SQL-heavy persistence.
Representative Outcomes
Faster reporting, lower query cost, stronger reconciliation accuracy, and safer large-result handling in supported areas.
My role in this environment
I worked on business-rule-heavy modules and reporting flows where correctness, maintainability, and cross-layer tracing mattered. A large part of the job was following production logic from WinForms screens into service wrappers, handlers, business logic, data access, and SQL queries to validate or improve the result.
Business Context
The platform supports operational, finance, and reporting workflows across multiple parts of the logistics business. It is not a simple CRUD application; it is a workflow-heavy enterprise system with long-lived modules, legacy logic, and integration-heavy operations.
What the Platform Is
Large Enterprise ERP / Platform
A long-lived logistics platform supporting operations, finance, dispatch, reporting, and internal support processes across multiple business areas.
Modular Client-Server System
Heavily WinForms-based on the client side, with modular backend/service flows, reporting logic, hybrid communication, and multiple persistence sources.
Architecture Direction
The system followed a layered, modular enterprise direction often described internally through MessageTier / NetworkTier / DataTier style boundaries. In practice, work moved through WinForms clients, hybrid WCF/Web API/internal wrappers, business logic, data logic, and SQL-heavy persistence/reporting layers.
WinForms / WPF UI
Service Wrapper / Network Layer
Handler / Validation
Business Logic
Data Layer / DB
My Scope
Finance-related logic and reporting flows
Import operations and import fee workflows
Receivables / debt / revenue reporting
Customs-clearance bulk mail workflows
International statement handover approval workflow
End-to-end tracing from WinForms form to BL / DL / DB
Key Problems I Worked On
Import Finance & Reporting
Detailed import debt reports, beginning-balance logic, and revenue/report validation in finance-related flows.
Workflow-Heavy Operations
Import fee workflows, debt handoff, approval flows, and customs-clearance bulk mail processing.
Data Correctness
Reconciliation rules, multi-source aggregation, and validation of legacy reporting/business logic.
Cross-Layer Tracing
Following production logic from UI into wrappers, handlers, BL, DL, and SQL to find the real source of issues.
Representative Contribution: Import Debt Reporting Reconciliation
One representative contribution was improving detailed import debt reporting and beginning-balance reconciliation logic in a legacy reporting flow.
- Identified the correct business-key relationship between legacy debt-balance data and shipment/reference data.
- Refined beginning-balance handling so prior balances were carried into the report correctly.
- Filtered incomplete keys and reconciliation edge cases to reduce incorrect matches across data sources.
- Made the reporting logic easier to validate and maintain, which improved confidence in finance-facing outputs.
The low-level mapping details stayed important during implementation, but the public takeaway is stronger cross-source consistency, better beginning-balance correctness, and more maintainable reporting logic.
Performance & Data Handling
30k+ Rows
Worked on heavy search/report flows where batching and result-set handling were needed to keep production usage stable.
~40% Faster Reports
Contributed to performance improvements in critical reporting paths used by finance and operations teams.
~30% Lower Query Cost
Helped reduce expensive query paths through execution plan review, SQL adjustments, and targeted optimization.
Why This Experience Matters for Backend Roles
- Comfortable tracing enterprise request flows from client UI to service wrappers, handlers, business logic, data logic, and database queries.
- Strong fit for backend roles that require workflow-heavy business rules, reporting correctness, and SQL-heavy investigation.
- Production experience with hybrid service environments where WCF, Web API, wrappers, DTOs, and data validation all matter.
- Legacy/desktop background becomes a strength because it comes with real enterprise complexity, not only CRUD examples.