Kế toán doanh nghiệp - Chapter 6: Purchase and payments business process

Chapter 6Purchase and Payments Business ProcessCopyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.Learning Objectives6-2LO#1 Describe the business activities that comprise the purchase and payment processLO#2 Develop an activity model of the purchase and payment process using BPMNLO#3 Understand and apply different activity modeling optionsLO#4 Develop business rules to implement controls for the purchase and payment processLO#5 Develop structure models for the purchase and payment process using UML class diagramsLO#6 Implement a relational database from the UML Class Diagram of the purchase and payment processReview of Purchases and Payments Accounting6-3LO# 1Sunset Graphics Purchases ProcessResearch prices and product availability Select the best price and availability combination and send a purchase order to the supplierReceive the items from the supplier (and record the purchase and accounts payable)Pay the supplier according to the credit terms6-4LO# 2Basic Purchases BPMN Activity Model6-5The basic activity model implements the process steps.LO# 2Collaboration Model of the Purchases Process6-6The collaboration model focuses on the message flows between the pools.LO# 3Adding Swimlanes to Show Functional Responsibility6-7Swimlanesshow functional responsibilitiesLO# 3Business Rules Examples for Purchases Process6-8LO# 4Process StepsIntentionPartner Authority/ActionAccess ControlsApplication ControlsPlace OrderOrder products from reliable suppliers at the best available prices to meet required delivery timeManager approval required for orders > $5,000; Partner ordering products must not manage inventoryPartners preparing purchase orders cannot modify product inventory records, receive items, or pay suppliersSystem must provide purchase order number control, default values, range and limit checks, and create audit trailReceive ItemsRecord receipt of items promptly and accuratelyPartner receiving items must not be same partner that ordered the itemsPartners receiving items cannot modify purchase orders or inventory records; they cannot view purchase order quantity ordered informationSystem must only allow partner to enter the number of items received, subject to range and limit checks on quantities received; date of receipt defaults to current dateSunset’s Basic Purchases UML Class Models6-9LO# 5Purchase Orders are commitments to purchase from the supplier.Receipts document the receipt of items from the supplier (when purchases recognized).Cash disbursements pay for one or more receiptsRevised Purchases UML Class Diagram6-10LO# 5Purchase Orders and Receipts collapsed into one Purchases eventsAdded Product Categories type image as defined in Chapter 5Added Supplier Categories type image to show Sunset Partner responsibility for CategoriesImplementing UML Diagram in a Database6-11LO# 6Database will contain 8 tables to implement classes and 1 linking table for the relationship between Purchases and Products.Posting Foreign Keys Example6-12Foreign keys implement links for one-to-many relationships. Post towards the * and away from the 1Database Relationships6-13Which relationship is missing? How would you implement that?Did you notice the similarity between the sales process and the purchase process?6-14