web.iti
ID

// systems · savings & loan cooperative · automatic closing

A Savings & Loan Cooperative App that follows your own bylaws

Principal, mandatory and voluntary deposits, loans with tiered approval, interest and SHU calculation, right through to RAT reporting. Built to follow your cooperative's rules — not to force your cooperative to follow an app.

Free scoping call → (opens in new tab)Read the case study

A savings-and-loan cooperative app can follow the cooperative's bylaws, with modules for deposits, tiered loan approval, installments, service charges, SHU simulation, and RAT reporting. A composite narrative describes a 1,800-member cooperative and reports a six-day monthly close becoming four hours plus a 78% rise in applications. No consent reference, supporting artifacts, raw data, or public URL is available; the figures are not independently verified, are not a published client result, and are not a guarantee. Final scope and price are set in writing after discovery.

// modules built

What ships with every cooperative app

  • ✓A complete deposits module — pokok, wajib, sukarela — with per-member transaction history you can pull any time, as of any date
  • ✓Member login from a phone: deposit balance, remaining loan principal, installment schedule, and downloadable payment receipts
  • ✓Online loan applications with tiered approval — admin verification, board sign-off above the ceiling, supervisory council notes
  • ✓Automatic jasa pinjaman calculation: flat, declining balance, or annuity, following whichever method your cooperative uses
  • ✓Automatic installment schedules plus handling for arrears, late penalties, and early settlement
  • ✓SHU simulation and distribution based on the capital-share and transaction-share portions set by RAT
  • ✓Board dashboard: cash position per branch, loans outstanding, arrears ratio, monthly deposit growth
  • ✓Separate access rights for board, supervisory council, cashier, members, and associate members — role-based access down to menu and amount level
  • ✓The RAT reporting pack: balance sheet, income statement, deposit and loan recaps, list of members joining and leaving, Excel/PDF export
  • ✓A permanent audit trail — every transaction records who, when, the old value, and the new value
  • ✓WhatsApp notifications for installments falling due, loans approved, and deposits received
  • ✓Migration from your old Excel files, including per-member opening balances reconciled in both directions
  • ✓Daily database backup with a tested restore point, plus access logs in line with UU No 27/2022 tentang PDP (Indonesia's personal data protection law)
  • ✓Separate training for cashiers and board members, internal documentation, and 3 months of bug fixes at no charge

// why custom

When a subscription cooperative app stops being enough

Picture the 3rd of the month: the board is still lining up three Excel files whose numbers don't agree, while a member stands at the desk asking, "Sir, how much is left in my savings?" The answer exists — scattered across three places, and nobody dares say a figure out loud before reconciliation is done. A cooperative that keeps going this way loses three things at once. First, board time — six working days every month spent copying instead of deciding. Second, member trust, because members judge the cooperative's health by how fast a simple question gets answered. Third, RAT readiness, because a report thrown together at the last minute always leaves a discrepancy that has to be explained in front of the forum. The expensive thing isn't the app — it's the manual reconciliation you pay for every month and never book as a cost. We build the system once, and then the process runs itself.

// subscription vs custom

The maths changes as your membership grows

AspectSubscription appCustom app
Cost per member — 500 membersAssume a rate of Rp300rb/month = Rp3,6jt/year, roughly Rp7.200 per member per year. At this size a subscription genuinely is cheaper — we're not going to pretend otherwise.Rp 20jt amortised over five years is Rp 4jt/year, about Rp 8,000 per member per year before server costs. At 500 members, custom still may not be worthwhile.
Cost per member — 1,800 membersAbout Rp2.000 per member per year if the rate holds. The trouble is rates rarely hold — the tier almost always climbs once member count or transaction volume grows.Rp 35jt over five years is about Rp 3,900 per member per year. The difference is under Rp 160 per member per month — less than one lost working day spent reconciling records.
Cost per member — 5,000 membersIf it really is flat, about Rp720 per member per year. In practice a cooperative this size is already in the vendor's top tier, and the number gets renegotiated at every renewal.Rp 60jt over five years is about Rp 2,400 per member per year, and that figure does not rise with member count. At this scale, correcting unreliable reports can cost more than the licence comparison.
Data ownershipThe database sits on the vendor's server. Export is usually available in their format; the relational structure between tables rarely comes with it. Ending the subscription means losing read access to your members' transaction history.The database, source code, and the entire transaction history belong to the cooperative once it's paid off. It can move to your own server or to another developer any time, without anyone's permission.
Jasa pinjaman rules & SHU distributionThe method and formula follow whatever options the app offers. If RAT decides the capital-share portion changes, you wait in the feature request queue — assuming the vendor is willing at all.The formula, the portions, and the rounding become configuration the board can change itself. The AD/ART governs the system, not the other way round.
Multiple branches & other business unitsUsually one savings and loan unit, one location. Extra branches often count as separate accounts with separate bills — and then consolidation goes back to being done by hand in Excel.Cash is tracked separately per branch, the balance sheet consolidates automatically, and other business units (shop, rentals, services) attach to the same member base so SHU is calculated from total participation.
If the vendor changes pricing or shuts downPricing is set unilaterally at renewal. If the vendor stops operating, someone else decides your migration timetable — usually right in the middle of the accounting year.Running costs come down to the server and the maintenance you control yourself. No third party can raise the price of a system you've already paid off.
RAT reports & Permenkop formatsReports follow the built-in template. If your regional Dinas Koperasi (the local cooperatives office) asks for a different format, the adjustment joins the feature request list alongside hundreds of other users.Formats are built around what RAT needs and what your local Dinas Koperasi asks for, and they can be changed again later without queueing behind someone else's cooperative.

A savings and loan app isn't an ordinary CRUD app — it's a ledger. So we make transactions immutable: corrections are recorded as reversing entries, not as edits that overwrite the old figure, so every member's balance can always be reconstructed as of any date. Jasa pinjaman rounding is locked in one place under one rule, so rupiah discrepancies don't pile up across 24 installments. The calculation method — flat, declining balance, annuity, or sharia contracts like murabahah and mudharabah — is written as configuration, not as code that has to be torn open every time RAT changes the terms. Access rights are split by role down to menu and amount level, with an audit trail nobody can delete. Members' personal data is handled in line with UU No 27/2022 tentang PDP: encrypted at rest, access logged, retention agreed in writing. Installment reminders go out via the official WhatsApp API, and the final figures can be connected to the accounting software you already use.

// how it works

From your bylaws to members checking balances

01

Discovery & reading your AD/ART

We ask for the AD/ART, your latest RAT report, and the Excel files you're using now. One or two sessions to map out deposit types, loan ceilings per member class, the jasa pinjaman method, the approval path through board and supervisory council, and the SHU distribution formula. The output is a single scope document with modules split hard: what's mandatory in release one, and what can follow later.

02

Role flows & wireframes

Each role gets mapped on its own — what a member sees on their phone, what a cashier is allowed to enter, at what amount approval escalates to the board, and what the supervisory council can read. We test the wireframes on two or three actual members before a single line of code is written. This is the stage where internal terms we've misunderstood usually surface.

03

Two-week sprints & an audit of the old data

Build runs in two-week sprints with a demo at the end of each one. In parallel, we audit the old Excel data: duplicate members, member numbers reused, deposits with no matching counter-entry, installments that don't reconcile against remaining principal. This part almost always takes longer than the board expects — and we'd rather find it in week three than in the final week.

04

Parallel run across one full book cycle

For one accounting month, the system runs side by side with the old way. Deposits, withdrawals, and installments get entered in both, and then the closing figures are compared. The new system only passes if the difference is zero rupiah — not "close enough". If there's a gap, we chase the source until we find it before moving on.

05

Go-live, training, support through your first RAT

Handover of source code, database, and documentation. Separate training for cashiers, board, and supervisory council, plus a short guide for members. We stay alongside you until one close has been run entirely by your own team, and we're still there when the first RAT report after go-live gets put together. Three months of bug fixes at no charge.

// investment

Ranges, not packages

Compact system

Rp 15-30jt

Three to five core modules — deposits, loans, installments, basic reports. One to three user roles, one location. Fits an employee cooperative or a village cooperative whose processes are already tidy and just needs to get out of Excel.

Most common

Rp 30-60jt

Multi-module with tiered approval, many roles, integration to accounting or payments, and custom reports for RAT. This is the range cooperatives with a thousand members and up pick most often.

Large scale

Rp 60jt+

Multi-branch or multi-tenant, high daily transaction volume, years of historical data to migrate. The firm number and timeline come out after the initial data audit — not before.

These are ranges, not packages, and none can be locked before discovery. Modules, roles, branches, integrations, and the condition of legacy data determine the exact written quote. If the requirement falls below Rp 15jt, a lighter web app or a subscription product is usually the better fit.

// a good fit when

Which cooperatives benefit most

  • →Savings and loan cooperatives with 800 members and up whose month-end close still eats more than two working days
  • →Employee cooperatives where mandatory deposit deductions ride on company payroll and have to be reconciled every month
  • →Cooperatives with non-standard jasa pinjaman rules or SHU portions — the result of years of RAT decisions
  • →A KSP or USP with more than one branch or business unit whose reports still get merged by hand
  • →Boards that once used a subscription app and quit because there was one process the app couldn't follow

// not yet a fit when

When your cooperative should just buy off the shelf

  • ✕

    Cooperatives under 300 members with standard processes — buy a subscription app at Rp300-500rb/month, that's the right answer and far cheaper

  • ✕

    Cooperatives without a written AD/ART or agreed jasa pinjaman rules; a system will only make the confusion permanent

  • ✕

    Cooperatives that need it live next month; discovery to handover realistically runs 8-16 weeks, including the parallel run

  • ✕

    A budget below Rp 15jt — we would rather decline than cut modules until the records cannot be trusted

  • ✕

    Boards that haven't appointed one person accountable for the data — without that, setting opening balances never finishes

// questions

What cooperative boards usually ask.

Has any cooperative actually used this? What were the numbers?

There is one composite narrative about a Karanganyar savings-and-loan cooperative of roughly 1,800 members. It models member login, savings modules, loan approval, service-charge calculations, and a board dashboard; the six-days-to-four-hours and +78% figures are only reported within that narrative. No consent reference, supporting artifacts, raw data, or public URL is available, so the figures cannot be independently verified, are not a published client result, and are not a guarantee.

How is this different from a subscription cooperative app at around Rp300rb a month?

The difference isn't in the basic features — deposits, loans, and installments exist in both. The difference is who sets the rules. A subscription app offers the methods it already has; if your RAT decides on something outside those options, you wait. Then there are three things a subscription never resolves: your data lives on someone else's server, the rate gets renegotiated at every renewal, and a second branch often means a second bill with manual consolidation. If your cooperative is small and your processes are standard, none of that matters and a subscription is cheaper. The turning point usually shows up when membership passes a thousand, or when there's one process that can't be forced into an off-the-shelf app.

Does the system comply with UU No 25/1992 and Permenkop UKM reporting rules?

We build the system around the framework of UU No 25/1992 tentang Perkoperasian (Indonesia's cooperatives law) — members as both owners and users, RAT as the highest authority, and the separation between board and supervisory council, which we translate directly into different access rights in the app. For reporting, the system's output is structured so it can be used to prepare what Permenkop UKM and your local Dinas Koperasi ask for: balance sheet, income statement, deposit and loan recaps per member, and the list of members joining and leaving over the accounting year. One thing to be clear about from the start — we build tools, we don't give legal advice or audit services. The final format still needs checking by your supervisory council or your cooperative's accountant. If the format changes, we adjust it without you queueing on a vendor's feature request list.

Our cooperative uses sharia contracts. Can that be accommodated?

Yes, and it's best decided at discovery because it changes the data structure, not just the labels. For a KSPPS, deposits move to wadiah or mudharabah contracts, and loans move to financing under murabahah, mudharabah, or ijarah. What changes isn't only the terminology — a murabahah margin is calculated differently from a conventional jasa pinjaman, mudharabah profit-sharing needs a nisbah (the agreed profit-sharing ratio) and per-period results reporting, and sharia supervision has its own reporting path. We build contracts as separate entities each with their own parameters, so a cooperative running both patterns at once can still keep its books cleanly separated. If your cooperative is purely sharia, mention it in the first session — the scope and the numbers are different.

Our data is spread across several Excel files. How does migration work?

That's the part people underestimate most often, so we put it up front. We ask for all the files exactly as they are — including the ones whose sheets are already a mess — and then run an audit: duplicate members, member numbers reused, deposits recorded with no counter-entry, installments that don't reconcile against remaining principal. We hand the results back to the board as a list of discrepancies to decide on, because deciding which figure is correct isn't ours to make. After that, per-member opening balances get signed off by the board as the system's zero point. For a cooperative the size of 1,800 members, this stage realistically takes 2-3 weeks — and most of that time sits on your side, not ours.

Who owns the data and the source code, and what does the server cost each month?

The database and source code belong entirely to the cooperative once it's paid off. We hand over the repository, the database schema, and the documentation, and you're free to continue with any developer you like. We don't hold back any licence as a lock-in. Running costs after that come down to server and domain: for a cooperative in the 1,000-2,000 member range that's typically Rp300rb-1jt per month, depending on daily transaction volume and backup policy. That figure is paid to the server provider, not to us. If you'd like us to keep handling maintenance after the three months of bug fixes, that's a separate package you can take or leave — the system keeps running normally if you don't.

We have three branches and other business units. Can they be combined, and how long does it take?

Yes, and multi-branch requirements are one reason a cooperative may consider a custom system. Each branch can have its own cash account and cashier with transactions recorded separately, while the balance sheet and RAT reports are consolidated without re-keying. Other business units — shops, rentals, or services — can use the same member base, so SHU is calculated from members' total participation, not savings and loans alone. As an initial estimate, a single-location system with core modules may require 8-10 weeks, while a multi-branch system with historical data migration may require 12-16 weeks. Scope, data readiness, UAT, and parallel testing remain subject to the written project schedule.

// go next

Related pages

Composite narrative: a six-day close, done in four hours

A 1,800-member cooperative; no consent reference or public artifacts are stored in the repository, figures are not independently verified, and results are not guaranteed.

Custom Business System Development

If daily operations still run on spreadsheets that clash and a manual scramble every month-end, what you need isn't another website — it's a system that follows how you already work.

Web App for Your Customers

If what you're building is used by customers outside the company rather than your internal team, that's a different route.

// ready to start?

Build Your Business a Website
Right Now!

Free consultation via WhatsApp. We review your needs, give you a time & price estimate, then start together — no drama.

Free Consultation via WhatsApp → (opens in new tab)Check pricing

→ See examples of our workTerms & Conditions