Skip to content
GODJI TECH
All products

ERP · Mobile

ADA Finanças

The mobile side of the church's ERP. Approvals, balances and payroll figures in the hands of leaders who are rarely at a desk — on the same back end, and the same permission rules, as the finance office.

Type
Client app
Platform
Web · Mobile
Backend
Django API · JWT + RBAC
Data
PostgreSQL

The brief

Figures that only existed at a desk.

The Financial & HR Intelligence ERP gives the organisation one source of truth for its money and its people. But the leaders who approve spending and keep an eye on the figures are rarely in the office — and an approval that waits for someone to get back to a desk holds everything behind it.

ADA Finanças is the ERP's mobile surface: the same figures and the same approvals, on a phone, for the people who need them between meetings and on the road.

What we built

The ERP, in the pocket of the people who run the money.

  • Approvals on the move

    Purchase orders and expenses reviewed and approved between meetings, not saved up for the next day in the office.

  • Balances and flows

    Jurisdictional balances and monetary flows checked on the road, from the same figures the finance team works with.

  • Payroll and HR figures

    Payroll and HR numbers reviewed without opening a laptop.

Design decision

Not a second system

ADA Finanças talks to the Financial & HR Intelligence API with the ERP's own role-based access control, so a person sees on the phone exactly what they are allowed to see in the office — and nothing ever needs reconciling between the two.

The harder parts

Where the real work went.

Who may see what

Church money is sensitive, and the access rules are layered: an assembly sees its own figures, a district its district, headquarters everything. Reusing the ERP's permission model meant one set of rules for desk and phone, enforced on the server rather than in the app.

One infrastructure, two apps

ADA Finanças and My ADA are separate apps for different people — leaders and finance staff on one side, members on the other — running on the same infrastructure, so a contribution declared in one is the same record the other reports on.

Stack

What it runs on.

  • Mobile
  • Django
  • DRF
  • JWT
  • Role-based access
  • PostgreSQL
  • AWS RDS · S3