Financias

The published overview separates the current balance, payments that need attention and the month’s spending rhythm. Income and spending charts sit below those immediate decisions, followed by shortcuts for the different kinds of record.

Recording a paid expense, planning a bill and moving money between accounts begin with distinct actions. This makes the product’s financial model visible before a person fills in a form.

The interface shown here was captured from the running product. Monetary amounts were concealed before capture, preserving the layout and controls while keeping personal values out of the case.

A paid expense reduces a balance. An upcoming bill represents a commitment, with its own due date, until payment is confirmed. A transfer moves money between the same person’s accounts and should not appear as new income or spending.

Those rules shape both the interface and the data model. Financias gives the actions distinct names and uses onboarding to explain them with short examples. The first-use flow starts with an account, introduces the four essential record types and leads into a real entry that the person reviews before saving.

Help remains available afterwards. Reopening it explains the product without creating financial records or resetting progress.

The payment flow records the effective date, paid amount and chosen account, then links the bill to the resulting transaction. Repeating the same confirmation must preserve one active payment and one effect on the balance.

That requirement connects a visible action to a software invariant. The interface can present a simple confirmation because the underlying operation is designed to keep the bill and its transaction consistent.

The same attention carries into the overview. Upcoming commitments remain separate from completed spending. Totals in different currencies remain separate as well, so a combined number does not imply that reais, dollars and euros are interchangeable.

Each financial record belongs to one account owner. Access management is separate from permission to inspect someone else’s financial information. The product does not introduce a shared family ledger or transfers between users.

This boundary gives the application a clear scope while allowing the interface to focus on the person’s own accounts, due dates and next action.

Financias connects everyday language to precise financial behaviour. Its strongest design decisions are visible in the distinctions the product preserves: paid and pending, transfer and expense, one currency and another, personal data and administrative access.