All selected work

Enterprise software · Bensaude Group

Frotas

Fleet reporting with access shaped around the organisation

A web application connecting fuel-card transactions, reporting and administration across companies, business units and departments.

Next.jsTypeScriptPostgreSQLReact

System overview

  1. External transactions

    Synchronised operational records

  2. Application & access

    Next.js · organisation hierarchy

  3. Client reporting

    Dashboards · PDF · Excel · CSV

Simplified application flow. This diagram describes the system without displaying internal business records.

Context

Fleet information has different audiences. Clients need to consult their transactions and reports, while administrators manage cards, organisations and approvals. The application needs to reflect that structure when deciding which information each person can access.

My contribution

  • Built and deployed the Next.js, React and TypeScript application backed by PostgreSQL.
  • Implemented access by company, business unit and department, alongside card and organisation administration.
  • Connected external transaction synchronisation to dashboards and PDF, Excel and CSV reporting.

Engineering decisions

Make the organisation part of the data model

Companies contain business units, which contain departments. Users and cards relate to that hierarchy. This gives access rules a concrete business context, with the additional responsibility of keeping filtering consistent across views and reports.

Connect operational data to reporting

External transaction synchronisation feeds the application used for consultation and reporting. The integration and the presentation of that data are separate concerns: a readable dashboard still depends on correct imported records.

Support different reporting formats

PDF, Excel and CSV serve different tasks, from reading a report to working with its data. Each format needs its own output checks; a correctly rendered table alone does not establish that its export is usable.

Validation

  • Changes are reviewed in the application UI and on GitHub.
  • Reporting iterations have been checked with the automated transaction-export test suite.
  • The company, business-unit and department model makes the access boundaries explicit when reviewing reporting changes.

Outcome

Delivered a platform where clients can consult fuel-card transactions and generate reports, while administrators manage cards, organisations and approvals. My current work at Bensaude also includes application support, issue investigation, and data structuring and validation.

Discuss the project

Get in touch about the work or a full-stack role.

Next: DayFlow