UI/UX
Balcão
Year
2026


Project Overview
An application for managing payment requests, account reporting, financial information, and budget data. It allows users to create and manage requests, supported by dedicated areas for user administration, entity management, and documentation.
I designed the application to bring these interconnected tasks into a cohesive experience, with a focus on clear information and consistent navigation.
An application for managing payment requests, account reporting, financial information, and budget data. It allows users to create and manage requests, supported by dedicated areas for user administration, entity management, and documentation.
I designed the application to bring these interconnected tasks into a cohesive experience, with a focus on clear information and consistent navigation.
Technology
Figma, Outsystems




Objective
My goal was to create a clear, organised interface that supports both financial workflows and administrative tasks. The experience needed to help users create and manage requests, consult financial and budget information, and access the entities and documentation relevant to their work.
My goal was to create a clear, organised interface that supports both financial workflows and administrative tasks. The experience needed to help users create and manage requests, consult financial and budget information, and access the entities and documentation relevant to their work.
Problem and Solution
Problem
The main design challenge was to connect several related areas without making the application difficult to navigate. Payment requests and account reporting needed to sit alongside financial and budget information, while user, entity, and document management introduced additional layers of complexity.
Each area served a different purpose, but users needed to understand how they related to one another. The interface had to accommodate detailed information while keeping the current task and available actions clear, particularly when moving between a request and its supporting records.
Solution
I structured the application around its core workflows, giving request creation and management a clear place within the wider experience. Dedicated areas for financial information, budget data, users, entities, and documentation helped organise the scope into manageable sections.
My design approach focused on a consistent visual hierarchy and interaction patterns across these areas. The aim was to make detailed records easier to read, keep relevant actions easy to identify, and give users a familiar experience as they moved between financial and administrative tasks.
Together, these decisions established a cohesive interface designed to support the management of requests and the information surrounding them.
Problem
The main design challenge was to connect several related areas without making the application difficult to navigate. Payment requests and account reporting needed to sit alongside financial and budget information, while user, entity, and document management introduced additional layers of complexity.
Each area served a different purpose, but users needed to understand how they related to one another. The interface had to accommodate detailed information while keeping the current task and available actions clear, particularly when moving between a request and its supporting records.
Solution
I structured the application around its core workflows, giving request creation and management a clear place within the wider experience. Dedicated areas for financial information, budget data, users, entities, and documentation helped organise the scope into manageable sections.
My design approach focused on a consistent visual hierarchy and interaction patterns across these areas. The aim was to make detailed records easier to read, keep relevant actions easy to identify, and give users a familiar experience as they moved between financial and administrative tasks.
Together, these decisions established a cohesive interface designed to support the management of requests and the information surrounding them.
Gonçalo Perdigão
Gonçalo Perdigão
Gonçalo Perdigão