Portfolio case study

FreightLens: Logistics revenue audit web platform

A logistics revenue audit and freight operations platform that helps teams review bills of lading, recover balance dues, manage research queues, generate client reports, and control analyst workflows from one role-aware web workspace.

Name changed to respect NDA.

Logistics revenue audit dashboard visual with invoice variance cards, bill of lading review, research queue, report export, and analyst controls

Project scope

Web application engineering across ASP.NET MVC operations screens, role-based administration, freight audit workflows, reporting, import mapping, PDF generation, and data-access integration

operator roles and workspaces

BOL

bill of lading audit flows

PDF

client-ready reporting output

Import

mapping and data intake tools

Timeline

Enterprise freight audit platform build and operational workflow expansion

Freight audit work needed more structure than spreadsheets could provide

Operations teams needed to review shipment records, identify balance dues and overcharges, manage analyst research, track collection and invoice statuses, and produce client-facing reports without losing context across separate files and manual handoffs.

Bill of lading, booking, customer, invoice, balance due, payment, and collection data needed to stay connected
Analysts and managers needed filtered work queues, status updates, research notes, and playbook comments
Client reporting required management summaries, overcharge reports, PDF output, and region/date filtering
Administrators needed role-aware menus, permissions, clients, groups, users, settings, templates, and import configuration

A role-aware freight audit workspace for revenue recovery

FreightLens brings audit review, balance due recovery, research handling, import mapping, reporting, and administration into one web platform built for logistics finance and operations teams.

Audit workflows for bills of lading, bookings, balance dues, invoices, payments, collection comments, and research pull requests
Manager, analyst, client, and administrator workspaces with permission-aware navigation and scoped actions
PDF and management-report generation for client summaries, overcharge findings, invoice detail, and balance due packages
Import mapping and table-setting tools that help operations teams bring structured shipment and finance data into the system

Product surfaces

What the platform brought together

The work spanned core product operations, daily user workflows, data-heavy coordination, and resilient platform management.

Bill of lading audit review

Shipment records become searchable audit cases with filters, statistics, table views, document review, and exception handling.

BOL and booking screens support customer, region, shipper, origin, destination, port, date, and saved-query filtering
Audit result views expose statistics by origin, port, shipper, grouped tables, and drill-down detail
Document image, message viewer, and viewed-state workflows help reviewers keep source evidence tied to the case

Balance due and invoice recovery

Revenue recovery work moves through balance due details, payment capture, collection comments, invoice statuses, and generated invoice output.

Balance due records include descriptions, close reasons, invoice status, client general-ledger status, revenue analyst assignment, and payment details
Bulk invoice status updates and add-to-invoice flows support operational processing across multiple recovery items
PDF invoice generation, invoice payment detail, commission detail, and SMTP/template options support client communication

Research queue and analyst performance

Questions that need human investigation can be pulled into research workflows and tracked through status changes.

Pull-for-research forms connect audit items to reason codes, notes, and status transitions
Research index, save, delete, status detail, and update-status actions support queue management
Analyst performance views summarize activity and help managers understand productivity across review work

Client reporting and management controls

Managers and client-facing teams can package audit outcomes into reusable reports and control who sees which workflows.

Management report screens support client, region, date, report-type, print, PDF, overcharge, and combined-output workflows
Admin modules manage clients, companies, users, roles, permissions, menus, regions, settings, templates, SMTP accounts, and reason codes
Import mapping and table-setting tools let operators configure how external data columns feed the platform

Module depth

Dedicated product blocks for the highest-value workflows

For large platforms, the conversion story depends on showing how each major module solves a specific operating problem, not only listing features.

Revenue recovery

Balance Due Workbench

A focused operations module for turning audit findings into trackable revenue recovery items.

Source review found balance due screens for status detail, payment amount detail, collection comments, invoice status updates, close reason codes, client general-ledger status, and generated invoice PDFs.

Operators can review one recovery item in detail or process groups of items through invoice status updates
Collection comments and payment details keep finance follow-up attached to the recovery record
Generated invoice outputs help teams package claims for client or customer communication

Audit operations

BOL Review And Research Loop

A shipment audit loop for filtering, reviewing, investigating, and escalating records that need more human judgment.

Source review found BOL audit result screens, stats views, document viewers, pull-for-research actions, saved SQL query support, playbook comments, and viewed-state tracking.

Audit records can be filtered by shipment attributes and reviewed in both statistical and table formats
Reviewers can pull records into research when reason codes, comments, or additional validation are needed
Playbook comments support shared handling patterns for recurring audit scenarios

Client operations

Management Reporting Layer

A reporting module that converts audit activity into client-ready summaries and operational views.

Source review found management report, print report, generated report PDF, overcharge report PDF, invoice PDF, and combined report views.

Managers can select client, date, region, and report type to prepare focused summaries
PDF outputs support client-facing communication without recreating reports outside the platform
Separate report templates help distinguish overcharge, invoice, and management-summary contexts

Buyer priorities

What mattered most to the people evaluating the platform

Prospective buyers want to know whether the work solved real workflow, adoption, reliability, data, and operations problems. These priorities shaped the product decisions.

Recoverable revenue visibility

Finance and operations teams needed a clear way to find, classify, invoice, and follow up on freight discrepancies.

Balance due records connect audit findings to invoice and collection status
Payment and comment workflows preserve follow-up context
Client-ready PDFs reduce manual report assembly outside the system

Operational control

A multi-role logistics workflow needs controls for users, permissions, clients, regions, templates, and menu access.

Role-aware menus separate admin, manager, analyst, and client-facing workflows
Permission, group, menu, setting, and template screens support controlled configuration
Import mappings give operations teams a way to adapt structured data intake without hard-coding every source

Audit traceability

Audit teams needed a defensible trail from shipment data and source documents through research, balance due creation, reporting, and invoice communication.

BOL, booking, customer, invoice, cargo, container, payment, and comment models keep the domain connected
Research and playbook workflows support exception handling and repeatable review practices
Document/image and PDF paths keep source evidence and output artifacts close to the workflow

System model

How the platform connects roles, workflows, and product surfaces

The product architecture brings every role into the same operating model, with shared data moving cleanly between web, mobile, media, and notification layers.

Audit to recovery workflow

Shipment records move from BOL review into research, balance due creation, invoice status updates, payment tracking, and client reporting.

Role-aware operations model

Administrators, managers, analysts, client managers, and client users share one platform with different controls and visibility.

Web app, data, documents, and reports

MVC screens, SQL-backed domain models, import mappings, document evidence, generated PDFs, and email/report workflows operate together.

Technology

The Stack We Used And Why

The stack section is written for buyers who need to understand the product architecture, operational trade-offs, and long-term maintainability of the system.

Web application

Used to deliver a server-rendered operations workspace with role-specific pages, forms, filters, and report views.

ASP.NET MVCC#Razor viewsjQueryBootstrapChart.js

Data and domain layer

Used to model shipment, billing, customer, audit, balance due, commission, research, permission, and reporting data.

Entity FrameworkSQL ServerRepository-style data accessTyped C# models

Reporting and documents

Used to generate operational reports, invoices, spreadsheets, PDFs, and source-document review surfaces.

RotativawkhtmltopdfNPOIEPPlusSpire PDFDocument image models

Operations integrations

Used for email delivery, Google file workflows, authentication, logs, caching, and configurable imports.

ASP.NET IdentityMailKitGoogle Drive APIGoogle Sheets APINLogCacheManager

Why Server-Rendered MVC

The product needed dense operational forms, reports, filters, and role-gated screens for internal teams more than a consumer-style app shell.

Razor views kept reports, tables, and forms close to the C# domain model
MVC controllers made review, save, update-status, and generated-output actions explicit
Role-aware layouts and menus let different operators share one application without sharing every control

Why Document And PDF Tooling

Freight audit work depends on evidence, invoice packages, and client communication artifacts.

PDF generation turned audit findings into client-ready deliverables
Spreadsheet libraries supported structured import/export workflows
Document image models connected source evidence with review and reporting paths

Why Configurable Imports

Logistics finance data can arrive from different client, carrier, and shipment systems, so the app needed mapping controls.

Import mapping screens reduced the need to hard-code every incoming column structure
Table-setting controls helped operators align source data with the platform model
Progress and column-list APIs supported longer-running operational imports

Delivery

How the product came together

The work moved from domain modeling to core platform delivery, mobile adoption, and operational hardening.

Map the freight audit domain

Translate logistics finance operations into connected records for clients, customers, BOLs, bookings, invoices, balance dues, payments, comments, and research.

Build role-specific operations screens

Create workflows for administrators, managers, analysts, and client-facing users with separate navigation, permissions, and action surfaces.

Add recovery and reporting outputs

Connect balance due handling, invoice status changes, payment details, comments, management reports, overcharge reports, and generated PDFs.

Support data intake and configuration

Add import mapping, table settings, menu configuration, templates, regions, SMTP accounts, and settings so operations teams can keep the platform adaptable.

Operational depth

What made the platform usable after launch

The strongest case studies are not only feature lists. They show how the system is operated, monitored, governed, and improved when real users depend on it.

Dense status management

The platform supports many status transitions because freight audit recovery depends on knowing exactly where every disputed or recoverable item sits.

Collection status, invoice status, client general-ledger status, close reason, analyst assignment, and paid-state handling are tracked separately
Bulk update actions help operators move groups of records without losing audit context
Comments and payment detail surfaces keep finance follow-up visible

Report generation inside the workflow

Reports are generated from the operational records themselves, reducing hand-built summaries and detached spreadsheets.

Management, overcharge, combined, invoice, and balance due PDF views are available from the app
Region, client, date, and report-type options support focused reporting
Generated artifacts can support both internal review and client communication

Configurable administration

Administrative modules let the platform adapt to new clients, permissions, menus, settings, templates, regions, and import structures.

Client, user, company, role, group, permission, menu, and setting screens support operating control
Template and SMTP account modules support repeatable outbound communication
Import mapping tools support new data sources without redesigning the whole workflow

Results

The measurable and observable lift from the work

The strongest improvements are the ones a buyer can connect to daily work: fewer disconnected tools, safer operations, clearer workflows, and more reliable product behavior.

Connected

Audit Records

BOL, booking, customer, invoice, balance due, payment, collection, research, and report data stay in one operational model.

Controlled

Role Access

Admin, manager, analyst, client manager, and client-facing flows are separated through role-aware navigation and permission patterns.

Reportable

Recovery Work

Management reports, invoice PDFs, overcharge reports, and balance due packages can be generated from the workflow.

Configurable

Data Intake

Import mapping and table setting screens help operations teams adapt incoming data structures to the platform.

Outcome

A stronger operating system for logistics revenue audit and freight operations platform

The platform reduced tool fragmentation and gave each role a clearer path from live activity to day-to-day action.

A role-aware ASP.NET MVC freight audit platform with admin, manager, analyst, client, and finance operations workflows

A connected audit model spanning bills of lading, bookings, customers, invoices, balance dues, payments, comments, research items, commissions, regions, and reports

Operational reporting surfaces for management reports, overcharge reports, invoice PDFs, balance due packages, and printable summaries

Configuration tools for users, roles, permissions, menus, settings, templates, SMTP accounts, import mappings, table settings, clients, companies, and regions

FAQ

Frequently Asked Questions About FreightLens

Answers about the logistics revenue audit and freight operations platform scope, platform model, technology choices, operational workflows, and related build patterns.

What Kind Of Platform Does FreightLens Represent?

FreightLens represents a logistics revenue audit web platform for reviewing bills of lading, identifying recoverable balance dues, managing research queues, tracking invoice and collection statuses, and generating client-ready reports.

Why Build A Custom Freight Audit Platform Instead Of Using Spreadsheets?

A custom platform keeps shipment records, audit findings, balance due recovery, status history, comments, payments, documents, and reports connected so teams can manage revenue recovery with less manual reconciliation.

Which Workflows Were Most Important For Operations Teams?

The highest-value workflows were BOL review, balance due creation, invoice status management, collection comments, research escalation, analyst performance visibility, client reporting, and role-based administration.

Can This Pattern Support Other Logistics Finance Products?

Yes. The same architecture pattern can support carrier invoice auditing, freight claims, demurrage review, customer billing operations, shipment exception management, and logistics finance reporting systems.

Related services

Build a similarly ambitious product without starting from a blank page.

We can help scope the web, mobile, AI, media, and operating layers needed for your own platform.

Start a project inquiry

Custom software development Web app development Enterprise software development SaaS development