Accounts Payable and Receivable
Keywords:HRMS, submodule, agile methodology
The hotel and restaurant management has a submodule called finance management wherein accounts payable and receivable are located. Accounts payable and receivable are recorded at the time in a transaction that occurs in a day. Payables focus on trade payables, payables for the purchase of physical goods that are recorded in inventory, and receivables focusing on the data shown in a balance sheet. As an asset, it is one of a series of accounting transaction dealings with the billing of a customer for goods and services. In this research, we used agile method, which has a series of sprints; every sprint has multiple tasks with restricted duration to develop a functional system. The scrum team analyzed the whole business process and its connection from other module to create a design plan. After the initial planning for the system, the developers started to create and design the proposed system. After creating and designing the system, the developers will upgrade and develop a functional system. The developer will identify and start trial runs for the system to identify some errors or bugs to prevent discrepancies and redundant data or information inside the system. After the initial quality assurance for the system, the developers pushed out the final product after removing bugs and repairing defects, providing additional support for product users. This research already achieved the expected goals of the researchers. The user may experience a flexible and user-friendly system process. The system also makes sure that the data are accurate, and the real-time daily transaction will reflect to avoid discrepancy and money conflict. The proposed system created a receivable and payable list and journal entry. While creating the journal entry, the researchers made sure that the account titles will be placed according to the designated identity. The researchers suggested that the user must undergo the same seminars to understand the process thoroughly to avoid user risk and other difficulties in the system. User, technical, and security risks are some of the factors that must be solved. Thus, the proposed system may be adjusted or expanded its system functions that can be flexible toward how the client wants it to operate. The researchers ensured that the system can be fully functional and trusted.