DATABASES / BILLING
Storage Charges Billing System
Turning operational storage data into structured billing output with customer-specific charge logic.
The problem
Operational inventory and storage data was not structured cleanly for billing. Customer records, storage quantities, charge rules, and minimum billing requirements had to be reconciled each cycle, creating manual work and opportunities for duplicate records and errors.
The approach
I designed and built a relational database in Microsoft Access, using SQL to organize and transform operational data into billing records. I defined the relationships connecting storage records to customers and applicable charges, with attention to data quality and duplicate records.
The solution
The system brings customer relationships, storage quantities, and charge rules into one billing workflow. Its logic includes minimum-charge handling and produces structured output for validation and invoicing.
The outcome
The database could produce billing output that was easier to validate and use for invoicing, reducing the need to manually work through the underlying operational data each billing cycle.
This overview describes the project at a high level. Diagrams are conceptual. Customer records, internal screenshots, rates, and confidential operational data are not shown.