BUMDES (Village-Owned Enterprises) Application Development Service

Berita August 2022

The BUM Desa application should help managers track transactions from business activities to reports, not just display total receipts. The needs may differ between trade, rental, tourism and water services. Before choosing an application, map out the data source, recording officer, proof of transactions, and inspection method so that the combined report does not cover up problems with each activity.

Starting from business activities and recording limits

PP Number 11 of 2021 explains that BUM Desa is a legal entity established by a village and/or together with villages. The regulation also defines the BUM Desa Business Unit as a legal business entity. Therefore, the term operational unit in the application design does not automatically mean a Business Unit with that legal status.

This distinction is necessary when constructing data structures. A grouping of cashiers, sales locations, or rental activities may be used for operational analysis, but should not be directly considered as separate legal entities. Match the application structure to actual organizational documents and reporting needs.

Discussions with FourVM can start from a list of activities, officers, and examples of reports that have been used. Include problems that occur, for example proof of expenditure is difficult to find or receipts for an activity are mixed up with other activities. This information helps determine which modules need to be prioritized.

Link transactions with evidence and the person responsible

Every transaction needs to have an identity that can be referred to again. Design records of dates, related activities, types of transactions, amounts, payment methods, and supporting evidence as needed. For sales of goods, product and quantity details are required so that inventory changes can be checked.

Determine who takes notes and who checks. Receipt officers may be assigned transaction entry rights, while certain corrections require different authority. Avoid the habit of using a shared account if the organization requires tracking the responsibilities of each officer.

OWASP Authorization defines rights restrictions based on job requirements. In designing the BUM Desa application, this principle can be applied by differentiating access for cashiers, activity managers, inspectors and administrators. Such settings should be tested using real access scenarios, including attempts to view transactions outside the user's authority.

Distinguish between receipts, receivables and business results

The revenue dashboard is not enough to explain business results. Unpaid sales require different treatment than money already received. Asset purchases also need to be differentiated from operational expenses according to the recording policies and accounting standards used by the organization.

The application needs to follow the bookkeeping plan established with the party responsible for finances. This article does not establish a chart of accounts or profit sharing formula for all Village BUMs. Managers need to confirm accounting and reporting needs before having the system generate automated reports.

Also check the transfer of money between accounts or between activities. Without appropriate markers, internal displacement can be mistakenly read as new acceptance. Have examples of these types of transactions ready when testing reports, so that the combined numbers don't increase just because money is moved where it's stored.

Design reports that can be checked again

Start with the questions the manager must answer. How much is the receipt for each activity, what transactions do not have complete proof, and do the record balances match the audit results? Each summary figure should be traceable to relevant details, rather than stopping at a graph.

Transaction corrections also require rules. Determine whether corrections are made through cancellation, replacement listing, or other mechanisms in accordance with organizational policy. Save the reason, officer, time, and relationship to previous transactions so changes can be reviewed.

OWASP Logging addresses the context of events such as time, actors, actions, and outcomes. These principles can help design transaction change traces. However, the existence of logs does not prove the report is correct; examination of evidence, reconciliation, and assessment by authorized officers are still required.

Simulation case study: store sales and inventory

In this simulation, a Village BUM manages a daily necessities shop. Sales are recorded in the books, purchases of goods are on a separate sheet, and stock adjustments are often not accompanied by a reason. At the end of the period, managers know money is coming in but have difficulty explaining the difference in inventory.

The team prepared consistent product and unit data, then tested the flow of purchases, sales, returns, and damaged goods. Each stock change has a corresponding event type and evidence. Cash sales are distinguished from transactions for which payment has not been received.

The examiner compares several transactions with evidence and physical count results. If discrepancies arise, the team traces the movement of goods and authorizes corrections. The lesson is that cashier applications need to be accompanied by inventory and inspection rules; Just printing a note does not explain the position of goods or cash.

Simulation case study: water services and asset leasing

Another Village BUM in the simulation manages water services and equipment rental. Both records use the same format even though the basis of the bill is different. Managers ultimately find it difficult to distinguish unpaid service bills from rental deposits that must be returned.

The team separated the operational flow of the two activities. The water service records bill basis and payment status according to agreed service rules. Rentals record schedules, items, handover, costs and deposits in clear categories.

The report was then tested using partial payments, rental cancellations, as well as deposit returns. The officer checks whether the incident is presented according to its nature. The lesson is that combined reports require consistent categories, while the details of the work for each activity can still be different.

Create a form that suits the officer's abilities

W3C WAI recommends forms with clear labels, instructions, and correction messages. Apply it by writing column names that the officer understands and examples of filling in if necessary. If the transaction amount is rejected, display the reason without deleting all correct fields.

Test charging on a device that is actually used. Pay attention to connections, screen sizes, proof printing, and work processes when service is interrupted. If a temporary logging mechanism is required, determine how to re-enter data and prevent duplicate transactions after the system recovers.

Training should use examples of daily work, not just menu explanations. Ask officers to record transactions, correct errors according to their authority, and show evidence that supports the report. Exercise results help spot confusion before production data is used.

Prepare the scope and handover

Before requesting a quote from FourVM, compile a list of activities, number of user roles, sample transactions, export requirements, and reports to review. Website creation proposal guide can help formulate project objectives and outputs; Application details are then added according to the Village BUM process.

Set data migration limits. Beginning balances, customer lists, inventory, and past transactions need to have a source approved by the person in charge. Note discrepancies or incomplete data so that transfers do not give the impression that all historical records have been verified.

At handover, test backup, restore, export, and account manager replacement. Explain who handles disruptions as well as how changing requirements are requested. The document helps subsequent administrators continue using the application without relying on one person's memory.

Frequently asked questions

Do all activities have to use the same module? No. Uniformity is needed in identities, categories and data combination rules, while transaction flows can adapt to the type of activity. Listing agreements need to be established prior to development.

Does the application guarantee error-free reports? No. Accuracy remains dependent on data, logging policies, access settings, and checks. Automation helps carry out designed processes, but does not replace manager responsibilities.

What to bring to the initial consultation? Bring examples of disguised transactions, required reports, and a list of operational constraints. FourVM can use these materials to discuss testable scope before establishing further development requirements.

Source

  1. Government of the Republic of Indonesia — PP Number 11 of 2021 concerning Village-Owned Enterprises . Established February 2, 2021; accessed 14 November 2026. Article 1 as a reference for the terms BUM Village and Business Unit.
  2. OWASP — Authorization Cheat Sheet . Update date not listed; accessed 14 November 2026. Reference to restrictions on user rights.
  3. OWASP — Logging Cheat Sheet . Update date not listed; accessed 14 November 2026. Change note context reference.
  4. W3C WAI — Tutorial Forms . Updated March 27, 2026; accessed 14 November 2026. Form reference and error responses.
Share