1 00:00:13,680 --> 00:00:16,960 We will now begin the lecture on purchase settlement and sales settlement 2 00:00:18,440 --> 00:00:20,020 The lecture agenda is as follows 3 00:00:20,240 --> 00:00:24,480 Purchase settlement, which is carried out between SERVEONE and suppliers for delivered orders, 4 00:00:24,760 --> 00:00:27,060 and sales settlement, which is carried out between SERVEONE and clients 5 00:00:27,060 --> 00:00:28,760 They are divided into these two categories 6 00:00:29,060 --> 00:00:31,740 We will go over each of these settlement processes 7 00:00:33,340 --> 00:00:36,340 Before we begin the lecture, let me introduce myself 8 00:00:36,660 --> 00:00:40,680 I joined the company in 2014 and have been working in purchasing for 10 years 9 00:00:40,940 --> 00:00:45,060 I am currently in the Purchasing Analysis Team, handling purchasing planning 10 00:00:45,240 --> 00:00:47,940 My name is Sungjin Cho, Manager of the Purchasing Analysis Team 11 00:00:50,740 --> 00:00:52,720 It is an honor to deliver this lecture, 12 00:00:52,720 --> 00:00:54,700 and I will do my best in presenting it 13 00:00:54,940 --> 00:00:57,160 First, an overview of purchase settlement 14 00:00:59,000 --> 00:01:01,160 By definition, purchase settlement means 15 00:01:01,160 --> 00:01:06,559 confirming as debt the purchase of product inventory supplied by a vendor 16 00:01:06,799 --> 00:01:11,559 In business terms, it means confirming the amount payable to the vendor 17 00:01:11,559 --> 00:01:14,059 and issuing a purchase tax invoice 18 00:01:14,939 --> 00:01:18,579 The timing of purchase settlement differs by delivery type 19 00:01:19,139 --> 00:01:23,259 You can think of the settlement point as the moment 20 00:01:23,259 --> 00:01:26,279 when product ownership and management authority are transferred to SERVEONE 21 00:01:26,779 --> 00:01:31,259 For direct delivery, the purchase settlement point is when the vendor completes delivery to the client 22 00:01:31,639 --> 00:01:35,659 For non-stock and center stock, it is when the goods are received at the hub 23 00:01:36,019 --> 00:01:40,019 For VMI, it is when the goods are shipped out 24 00:01:40,379 --> 00:01:45,019 For non-stock, center stock, and VMI, 25 00:01:45,019 --> 00:01:46,899 because they pass through our hub, 26 00:01:47,199 --> 00:01:49,559 no separate proof of receipt is required 27 00:01:49,799 --> 00:01:54,599 However, for direct delivery, SERVEONE must confirm the physical movement, 28 00:01:54,839 --> 00:01:59,219 and proof of delivery must be uploaded when the vendor marks delivery complete 29 00:01:59,599 --> 00:02:04,639 Later, at the purchase settlement stage, the validity of this document is reviewed 30 00:02:05,079 --> 00:02:10,939 Related processes will be explained later in delivery proof monitoring 31 00:02:11,699 --> 00:02:15,419 Next, let’s look at the business process of SERVEONE 32 00:02:15,419 --> 00:02:18,159 handling purchase settlement with vendors 33 00:02:20,339 --> 00:02:22,699 Here is the basic process of purchase settlement 34 00:02:22,999 --> 00:02:26,219 As mentioned earlier, direct delivery is settled at the delivery completion point, 35 00:02:26,539 --> 00:02:29,019 non-stock and center stock at the hub receipt point, 36 00:02:29,239 --> 00:02:33,459 and VMI at the hub shipment point 37 00:02:34,079 --> 00:02:36,020 Once the purchase settlement target is confirmed, 38 00:02:36,020 --> 00:02:40,081 settlement is carried out automatically or manually 39 00:02:40,259 --> 00:02:44,939 On D+1, the Business Management Team closes all purchases in bulk, 40 00:02:44,999 --> 00:02:47,519 and the purchase invoice is issued in reverse 41 00:02:48,079 --> 00:02:50,699 Although the process allows for manual settlement, 42 00:02:50,699 --> 00:02:54,419 99% of purchase settlements are processed automatically, 43 00:02:54,599 --> 00:02:58,199 so there is no need to focus much on manual cases 44 00:02:58,859 --> 00:03:03,379 Finally, when the vendor approves the reverse-issued invoice within the deadline, 45 00:03:03,379 --> 00:03:05,799 the purchase settlement process is complete 46 00:03:06,439 --> 00:03:08,239 Next is the settlement schedule 47 00:03:08,519 --> 00:03:12,959 Each month, the closing schedule is set so that all tasks by management unit 48 00:03:12,959 --> 00:03:17,239 must be finalized within three business days of the end of the month 49 00:03:17,679 --> 00:03:21,179 However, if the first business day of the following month falls on a public holiday, 50 00:03:21,359 --> 00:03:25,679 the Business Management Team will share the adjusted schedule in advance 51 00:03:25,679 --> 00:03:28,359 Please keep this in mind when carrying out your tasks 52 00:03:29,119 --> 00:03:32,459 For closing, the vendor must complete delivery 53 00:03:32,459 --> 00:03:36,079 for the customer’s SO by month-end, 54 00:03:36,079 --> 00:03:38,259 and all hub inbound and outbound processing must also be finalized 55 00:03:38,819 --> 00:03:44,199 Purchase settlement is automatically closed in the system by the first business day of the following month 56 00:03:44,839 --> 00:03:50,039 Next, the Business Management Team issues reverse-issued purchase tax invoices for each vendor 57 00:03:50,039 --> 00:03:52,439 on the second business day 58 00:03:54,579 --> 00:03:59,699 In principle, purchase settlement closing must follow the monthly closing schedule, 59 00:03:59,699 --> 00:04:01,459 and the Business Management Team 60 00:04:01,459 --> 00:04:05,359 automatically performs system-based purchase settlement for each vendor 61 00:04:07,839 --> 00:04:11,259 Unlike normal invoices, the tax invoice is reverse-issued not by the vendor (the seller) 62 00:04:11,259 --> 00:04:14,379 but by SERVEONE (the purchaser) 63 00:04:14,379 --> 00:04:19,419 They are issued individually depending on the tax code, settlement currency, and settlement type 64 00:04:19,859 --> 00:04:23,359 All reverse-issued tax invoices must be approved by the 10th of each month 65 00:04:23,819 --> 00:04:28,239 If the 10th is a public holiday, approval must be completed by the next business day 66 00:04:28,659 --> 00:04:31,779 If approval is not completed within the deadline, 67 00:04:31,779 --> 00:04:34,839 a 1% penalty will be charged equally to both parties 68 00:04:35,899 --> 00:04:38,739 The vendor’s primary contact, the purchasing manager, 69 00:04:38,739 --> 00:04:44,079 must encourage their vendors to approve invoices by the closing date 70 00:04:45,119 --> 00:04:48,079 Next is our payment terms 71 00:04:48,259 --> 00:04:51,059 This is one of the most frequently asked questions in the field 72 00:04:51,059 --> 00:04:53,599 and is a very important part of your work 73 00:04:54,059 --> 00:04:57,119 In fact, for purchase settlements, since orders that have been delivered 74 00:04:57,119 --> 00:04:59,479 are automatically processed in the system, 75 00:04:59,739 --> 00:05:02,979 there’s nothing you need to separately manage or worry about missing 76 00:05:03,279 --> 00:05:07,899 However, when it comes to payment terms, they involve company policy 77 00:05:07,899 --> 00:05:12,619 So it’s essential that you keep them in mind when communicating with our partners 78 00:05:12,719 --> 00:05:15,819 Our company makes payments to partners exclusively 79 00:05:15,819 --> 00:05:19,019 through the issuance of purchase card notes, without exception 80 00:05:19,019 --> 00:05:21,559 And depending on the type of settlement, 81 00:05:21,559 --> 00:05:25,159 the issue date of the tax invoice and the purchase card can differ 82 00:05:25,339 --> 00:05:28,379 Monthly settlement is done once a month at month-end, 83 00:05:28,379 --> 00:05:32,919 while bi-monthly settlement is carried out twice a month, on the 15th and at month-end 84 00:05:33,219 --> 00:05:37,479 In terms of tax classification, taxable and tax-exempt are grouped together, 85 00:05:37,479 --> 00:05:42,019 while zero-rated differs only in the invoice issue date depending on the settlement type 86 00:05:42,019 --> 00:05:45,739 Regardless of whether a supplier is subcontracted or not, 87 00:05:45,739 --> 00:05:50,439 a promissory note with a 14-day maturity from the invoice issue date is issued 88 00:05:50,919 --> 00:05:56,479 For taxable and tax-exempt cases, the maturity period differs depending on subcontract status 89 00:05:56,759 --> 00:06:00,499 For subcontractors, it is 60 days from the invoice issue date, 90 00:06:01,039 --> 00:06:04,839 while for non-subcontractors, it is 120 days 91 00:06:05,379 --> 00:06:09,059 These conditions can be mixed and somewhat complicated 92 00:06:09,059 --> 00:06:13,059 Therefore, purchasing managers must be able to distinguish 93 00:06:13,299 --> 00:06:16,819 the purchase card issue date and the invoice issue date 94 00:06:16,819 --> 00:06:19,759 based on whether it’s monthly settlement, taxable/exempt, and subcontracted or not 95 00:06:19,759 --> 00:06:22,979 You must also ensure that partners are clearly informed of these rules 96 00:06:23,499 --> 00:06:27,619 Since the same details are posted on the partner portal, 97 00:06:27,619 --> 00:06:31,619 please guide partners to refer to that information as well 98 00:06:32,259 --> 00:06:37,679 As mentioned earlier, this part is policy-based, 99 00:06:37,679 --> 00:06:39,399 so it may change in the future 100 00:06:39,659 --> 00:06:43,359 Therefore, purchasing managers must always keep themselves updated 101 00:06:43,359 --> 00:06:47,699 Therefore, purchasing managers must always keep themselves updated 102 00:06:48,419 --> 00:06:52,619 Now let’s look at common purchase settlement errors 103 00:06:53,119 --> 00:06:58,819 The first is when a purchasing manager misregisters the tax code, 104 00:06:58,819 --> 00:07:00,739 causing a mismatch between taxable and exempt items 105 00:07:01,139 --> 00:07:07,339 The second is when a sales manager changes the distribution route after the purchase settlement is closed, 106 00:07:07,339 --> 00:07:12,339 resulting in taxable or exempt status being misprocessed as zero-rated 107 00:07:12,939 --> 00:07:18,579 To prevent this, purchasing managers must register products 108 00:07:18,579 --> 00:07:22,659 with the correct tax status in their category, 109 00:07:22,659 --> 00:07:27,639 and sales managers must finalize any route changes 110 00:07:27,639 --> 00:07:31,699 before the settlement closing 111 00:07:31,699 --> 00:07:33,780 to prevent from the mismatch 112 00:07:36,659 --> 00:07:41,599 As you know, tax codes are taxable, exempt, and zero-rated 113 00:07:41,999 --> 00:07:44,240 General transactions are taxable, 114 00:07:44,240 --> 00:07:48,200 some products are exempt from VAT reporting, 115 00:07:48,200 --> 00:07:53,139 and exports are zero-rated where VAT is reported and refunded 116 00:07:54,259 --> 00:07:57,639 Taxable and zero-rated codes 117 00:07:57,640 --> 00:08:00,080 are straightforward, 118 00:08:00,080 --> 00:08:04,839 but exempt items must be handled carefully by purchasing managers 119 00:08:05,379 --> 00:08:11,919 Representative exempt items include books, flowers, salt, rice, kimchi, and honey 120 00:08:12,199 --> 00:08:15,359 When registering these products, 121 00:08:15,359 --> 00:08:20,499 managers must set the tax code as exempt 122 00:08:20,979 --> 00:08:24,479 Most purchasing managers in these categories 123 00:08:24,480 --> 00:08:26,383 already know this, 124 00:08:26,383 --> 00:08:31,919 but sales or operations managers may not, 125 00:08:31,919 --> 00:08:36,040 so errors can be discovered by clients 126 00:08:36,040 --> 00:08:39,400 at the settlement stage, 127 00:08:39,400 --> 00:08:41,709 leading to correction requests 128 00:08:42,260 --> 00:08:45,400 To avoid delays and losses, 129 00:08:45,401 --> 00:08:47,781 knowing the main exempt categories 130 00:08:47,781 --> 00:08:50,860 and applying correct tax codes is essential 131 00:08:52,040 --> 00:08:54,260 Next is Delivery Evidence Monitoring 132 00:08:56,560 --> 00:08:59,880 Currently, SERVEONE performs automatic purchase settlements 133 00:08:59,880 --> 00:09:03,760 for completed orders to improve efficiency through a system-based process 134 00:09:04,280 --> 00:09:06,760 However, since payments are being made, 135 00:09:06,761 --> 00:09:10,630 it is necessary to verify whether the transactions are real 136 00:09:10,630 --> 00:09:15,520 This task is called Delivery Evidence Monitoring, 137 00:09:18,120 --> 00:09:22,800 which involves checking the validity of delivery evidence uploaded by suppliers 138 00:09:22,800 --> 00:09:28,240 If any documents are found invalid, payment to the supplier is put on hold 139 00:09:28,880 --> 00:09:34,140 The detailed process will be explained in the following section, together with the Arena screens by task owner 140 00:09:35,200 --> 00:09:40,340 The eligibility of delivery evidence is reviewed, and it is either approved or rejected 141 00:09:40,880 --> 00:09:44,940 The purpose of monitoring is to check the validity of supporting documents 142 00:09:44,940 --> 00:09:48,101 and, based on this, either proceed with or withhold payment 143 00:09:48,101 --> 00:09:50,487 in order to ensure the authenticity of transactions 144 00:09:51,000 --> 00:09:55,120 In the next section, I will explain the key tasks by role 145 00:09:56,580 --> 00:09:58,941 Looking at the key tasks by role, 146 00:09:58,941 --> 00:10:03,459 the operations manager monitors eligibility for each order 147 00:10:03,459 --> 00:10:06,301 and, through correction and re-upload with the supplier, 148 00:10:06,301 --> 00:10:09,441 confirms the final list of payment-withheld orders 149 00:10:09,821 --> 00:10:15,060 Next, the division analyst submits the request for payment hold, 150 00:10:15,060 --> 00:10:17,680 after which the business management team withholds the payment 151 00:10:18,200 --> 00:10:21,921 After that, the purchasing manager reviews the withheld orders, 152 00:10:21,921 --> 00:10:25,093 guides the supplier, and checks for valid supporting evidence 153 00:10:25,093 --> 00:10:29,280 If proper delivery completion is confirmed, a release request is submitted, 154 00:10:29,280 --> 00:10:32,160 and if not, the order is processed as a return 155 00:10:33,180 --> 00:10:38,320 There are exceptions to monitoring, orders through hub delivery that guarantee authenticity 156 00:10:38,320 --> 00:10:40,960 such as non-stock, center stock, and VMI orders, 157 00:10:41,387 --> 00:10:46,127 orders from linked or overseas partners that do not use the partner front, 158 00:10:46,420 --> 00:10:52,220 first SSCS orders where purchase settlement follows sales settlement, 159 00:10:52,460 --> 00:10:58,180 and mobile delivery completed orders are not subject to delivery proof monitoring 160 00:11:01,440 --> 00:11:06,440 Here is a process map showing the workflow by each responsible party 161 00:11:06,820 --> 00:11:10,220 Being aware of this will help you in your tasks 162 00:11:10,900 --> 00:11:13,080 Lastly, the operations manager 163 00:11:13,081 --> 00:11:16,245 performs delivery proof monitoring according to the eligibility criteria 164 00:11:16,245 --> 00:11:18,840 based on the supplier’s shipping method 165 00:11:19,160 --> 00:11:21,221 They check whether the uploaded documents, such as transaction statements 166 00:11:21,221 --> 00:11:25,229 or other forms of proof, match the actual order 167 00:11:25,620 --> 00:11:28,980 If the uploaded proof differs from the order, 168 00:11:28,981 --> 00:11:31,275 or if receipt cannot be confirmed 169 00:11:31,580 --> 00:11:36,660 and authenticity is not verified, they request the supplier to provide new proof 170 00:11:37,100 --> 00:11:40,301 Since verification requirements vary depending on the type of documentation, 171 00:11:40,301 --> 00:11:43,280 please review them carefully and keep them in mind 172 00:11:43,960 --> 00:11:48,560 Next, let’s look at sales settlement between SERVEONE and its clients 173 00:11:48,860 --> 00:11:52,260 Unlike purchase settlement, which is automatically processed in the system, 174 00:11:52,520 --> 00:11:57,520 sales settlement involves more manual work, 175 00:11:57,520 --> 00:12:02,420 as operations managers handle much of the preparation and invoice issuance manually 176 00:12:02,840 --> 00:12:08,500 However, since each operations manager in charge of their respective unit already oversees this process in detail, 177 00:12:08,500 --> 00:12:11,240 they are far more knowledgeable about it than I am 178 00:12:11,440 --> 00:12:15,140 Therefore, for sales and purchasing managers, 179 00:12:15,140 --> 00:12:18,600 it’s sufficient to simply understand the overall flow of the process 180 00:12:20,240 --> 00:12:23,020 Looking at when sales settlement takes place, 181 00:12:23,020 --> 00:12:27,200 it comes at the very last stage of the overall flow I showed you at the beginning of this lecture 182 00:12:27,680 --> 00:12:30,560 By definition, sales settlement means 183 00:12:30,560 --> 00:12:34,560 recording and organizing SERVEONE’s sales 184 00:12:34,560 --> 00:12:39,080 In practice, it represents the final stage where SERVEONE’s revenue is actually realized, 185 00:12:39,080 --> 00:12:41,160 making it an extremely important process 186 00:12:41,400 --> 00:12:44,840 Now let me walk you through the sales settlement process 187 00:12:46,640 --> 00:12:49,640 The process goes as follows 188 00:12:50,080 --> 00:12:52,380 Managing undelivered orders 189 00:12:52,640 --> 00:12:56,280 Processing receipts in the system and prompting customers for settlement 190 00:12:56,580 --> 00:12:59,540 Preparing closing statements and coordinating with customers 191 00:12:59,840 --> 00:13:04,780 Finalizing mutual closing statements and managing the review month for system settlement 192 00:13:05,100 --> 00:13:08,620 Processing sales and issuing tax invoices 193 00:13:09,200 --> 00:13:11,280 The first step is managing undelivered orders 194 00:13:11,280 --> 00:13:15,340 This involves handling undelivered orders directed to both customers and suppliers, 195 00:13:15,340 --> 00:13:17,260 as well as internal follow-ups to ensure completion 196 00:13:17,800 --> 00:13:21,560 The operations manager encourages customers 197 00:13:21,560 --> 00:13:24,540 to complete pending pre-receipt orders, 198 00:13:24,540 --> 00:13:28,160 confirms delivery schedules with suppliers, 199 00:13:28,160 --> 00:13:30,260 and pushes for undelivered orders to be finalized 200 00:13:30,840 --> 00:13:35,100 Internally, the operations manager also reviews whether there are 201 00:13:35,100 --> 00:13:40,040 any unprocessed pre-receipt orders from either customer or supplier requests 202 00:13:41,300 --> 00:13:46,200 Along with clearing undelivered orders, they also check incomplete receipt items 203 00:13:46,200 --> 00:13:49,100 and urge customers to finalize receipt processing 204 00:13:49,620 --> 00:13:54,280 As shown in the table, in some cases sales settlement is possible 205 00:13:54,280 --> 00:13:58,120 when orders are automatically received at the supplier’s hub upon delivery completion 206 00:13:58,400 --> 00:14:02,160 However, in cases of semi-automatic or manual receipt types, 207 00:14:02,160 --> 00:14:06,960 where the customer must perform the receipt in the system, sales settlement can only proceed after customer confirmation 208 00:14:06,960 --> 00:14:09,640 For this reason, operations managers must actively check 209 00:14:09,641 --> 00:14:11,801 and follow up with customers on unprocessed receipt items 210 00:14:12,460 --> 00:14:15,280 In the case of semi-automatic or manual receipts, 211 00:14:15,280 --> 00:14:19,060 customers must complete the receipt process themselves through the customer front 212 00:14:19,720 --> 00:14:24,320 Once all receipts are finalized, the operations manager prepares the monthly closing details in the customer’s requested format 213 00:14:24,320 --> 00:14:29,420 and goes through a mutual confirmation process with the customer 214 00:14:30,560 --> 00:14:34,160 After the monthly closing list is confirmed, 215 00:14:34,160 --> 00:14:37,820 the next step is inspection month management for system-based sales settlement 216 00:14:38,040 --> 00:14:43,920 The inspection month refers to the settlement month automatically calculated based on the receipt date 217 00:14:43,920 --> 00:14:47,160 It is also called the expected settlement month 218 00:14:47,660 --> 00:14:51,101 For sales settlement to be processed in the system, 219 00:14:51,101 --> 00:14:53,421 the inspection month must match the current settlement month 220 00:14:53,421 --> 00:14:57,860 Handling previous and next month after closing confirmation 221 00:14:57,860 --> 00:15:00,160 means inspection month control 222 00:15:00,940 --> 00:15:03,480 There are two cases in inspection month management 223 00:15:04,080 --> 00:15:08,600 The first case is when the settlement date is the 25th 224 00:15:08,600 --> 00:15:12,320 For example, if an order is delivered on April 25, 225 00:15:12,320 --> 00:15:17,180 the inspection month is automatically set to April based on the unit’s settlement date 226 00:15:17,680 --> 00:15:22,580 On the other hand, if an order is delivered on May 25, 227 00:15:22,840 --> 00:15:27,360 the inspection month is automatically set to June based on the unit’s settlement date 228 00:15:28,040 --> 00:15:31,220 Therefore, in both cases, 229 00:15:31,220 --> 00:15:35,260 adjustments are required to process the settlement in May 230 00:15:35,640 --> 00:15:38,940 In the first case, for orders with an inspection month of April, 231 00:15:38,940 --> 00:15:41,780 you need to carry them over and change the inspection month to May 232 00:15:42,040 --> 00:15:45,280 For orders with an inspection month of June, you need to backdate them 233 00:15:45,280 --> 00:15:47,200 so the inspection month is adjusted to May 234 00:15:48,280 --> 00:15:52,100 Through inspection month management, once the orders for the current month’s sales settlement 235 00:15:52,100 --> 00:15:54,540 are ready for processing, 236 00:15:54,540 --> 00:15:58,440 you can check and process the sales settlement targets in SMRO 237 00:15:58,980 --> 00:16:02,960 You can also check incomplete sales settlement targets and process them, 238 00:16:03,320 --> 00:16:07,520 or check completed sales settlement targets and cancel them if needed 239 00:16:07,960 --> 00:16:13,140 However, canceling a sales settlement requires meeting the following conditions 240 00:16:14,120 --> 00:16:17,700 The sales settlement must have been completed for each order, 241 00:16:17,700 --> 00:16:21,160 and the sales settlement for the business unit must also be closed 242 00:16:21,920 --> 00:16:25,080 If a specific order has already been settled on the purchasing side, 243 00:16:25,080 --> 00:16:27,580 but not yet with the customer, 244 00:16:27,580 --> 00:16:30,520 it will result in unsettled sales and creat consignmen inventory 245 00:16:30,840 --> 00:16:35,080 Consignment inventory occurs when the purchase settlement is completed, meaning the liability is confirmed, 246 00:16:35,300 --> 00:16:39,980 but the sales settlement is incomplete, 247 00:16:40,500 --> 00:16:44,220 so the receivable is not confirmed 248 00:16:44,580 --> 00:16:48,560 Consignment inventory is tracked monthly across the Operations, Sales, and Business Management teams 249 00:16:48,560 --> 00:16:51,660 to monitor reasons and completion status 250 00:16:51,920 --> 00:16:54,240 The management process works as follows 251 00:16:54,840 --> 00:16:58,500 After unsettled cases are aggregated, settlement processing is blocked, 252 00:16:58,500 --> 00:17:00,940 and for Sales and Operations staff, 253 00:17:00,940 --> 00:17:03,600 a To-do list of unplanne settlements is generated 254 00:17:04,000 --> 00:17:08,419 The Operations team enters the reasons and plans for unsettled items into the system 255 00:17:08,419 --> 00:17:10,399 Once the Sales team gives final confirmation, 256 00:17:10,399 --> 00:17:13,679 the settlement block is released, and sales settlement can proceed 257 00:17:14,559 --> 00:17:19,399 Sales settlements that cannot be completed are carried over to the following month, 258 00:17:19,399 --> 00:17:21,191 and any orders still unsettled are cleared on a quarterly basis 259 00:17:22,207 --> 00:17:25,967 As shown in the reference data, reasons for unsettled cases are categorized, 260 00:17:25,967 --> 00:17:28,839 and to minimize consignment inventory and maintain accurate records, 261 00:17:28,839 --> 00:17:32,219 it is important to enter the actual cause precisely 262 00:17:34,719 --> 00:17:38,679 Once sales settlement is completed in SMRO, a tax invoice is issued 263 00:17:38,919 --> 00:17:43,479 When SERVEONE, as the seller, issues an invoice to the buyer, this is called standard issuance 264 00:17:43,739 --> 00:17:45,839 The opposite case is called reverse issuance 265 00:17:46,399 --> 00:17:50,599 Additionally, if a standard issuance is requested outside of SMRO by the customer 266 00:17:50,599 --> 00:17:54,259 and processed through UCESS DI or SmartBill, 267 00:17:54,259 --> 00:17:56,259 this is called external ASP issuance 268 00:17:57,139 --> 00:18:01,239 As shown in the table, while the buyer is involved in the issuance process, 269 00:18:01,239 --> 00:18:04,459 the final electronic signature on the tax invoice is made by the seller 270 00:18:04,459 --> 00:18:06,739 So, the seller holds ultimate responsibility, 271 00:18:07,099 --> 00:18:11,299 and even in cases of reverse issuance, SERVEONE must carefully review all details 272 00:18:11,639 --> 00:18:14,879 The ability to amend a tax invoice depends on the situation 273 00:18:15,199 --> 00:18:18,179 There are two common cases where amendments are required 274 00:18:18,539 --> 00:18:21,959 when details such as supply date, item name, 275 00:18:21,959 --> 00:18:24,339 or supply amount need to be corrected 276 00:18:24,339 --> 00:18:27,179 If the invoice is only in the registered state, amendments are possible 277 00:18:27,179 --> 00:18:30,099 However, once it has been fully issued, amendments are no longer allowed 278 00:18:30,819 --> 00:18:35,139 In that case, the issued tax invoice must first be canceled, and then a new one must be re-issued 279 00:18:35,499 --> 00:18:40,379 This applies to the registration and issuance process of a regular tax invoice 280 00:18:40,379 --> 00:18:44,759 For reverse-issued or third-party ASP-issued tax invoices, only cancellation is possible 281 00:18:45,639 --> 00:18:48,159 If a tax code change is required, 282 00:18:48,159 --> 00:18:50,959 first cancel the sales settlement, 283 00:18:50,959 --> 00:18:56,079 then update the tax code, and finally re-issue the sales settlement tax invoice 284 00:18:56,379 --> 00:18:59,539 It is therefore essential to strictly comply with this process 285 00:19:00,839 --> 00:19:04,859 Finally, let’s look at the Sales Settlement Discrepancy Handling Process 286 00:19:06,739 --> 00:19:10,399 In principle, once the monthly sales targets are processed, 287 00:19:10,399 --> 00:19:12,599 the corresponding tax invoices are issued 288 00:19:12,599 --> 00:19:16,619 So, the sales settlement targets and tax invoice targets should always match 289 00:19:17,059 --> 00:19:20,059 However, discrepancies can occur due to reasons such as 290 00:19:20,379 --> 00:19:25,639 delays in reconciliation with the client, retroactive price adjustments, or order production 291 00:19:25,639 --> 00:19:28,799 When these discrepancies occur, 292 00:19:28,799 --> 00:19:31,579 a process correction task must be carried out 293 00:19:32,159 --> 00:19:37,819 The process correction differs depending on whether it is handled on D+2 or D+3, 294 00:19:37,819 --> 00:19:40,819 so please follow the appropriate process when carrying out the task 295 00:19:41,499 --> 00:19:44,600 That concludes the lecture on SERVEONE\'s MRO Process, Purchase Settlement 296 00:19:44,600 --> 00:19:46,980 and Sales Settlement 297 00:19:47,199 --> 00:19:47,959 Thank you