<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeasson Oktavianus Gatur on Medium]]></title>
        <description><![CDATA[Stories by Jeasson Oktavianus Gatur on Medium]]></description>
        <link>https://medium.com/@jaexynn710?source=rss-edda8e4063c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FV3RYSk49_iMdvZQ</url>
            <title>Stories by Jeasson Oktavianus Gatur on Medium</title>
            <link>https://medium.com/@jaexynn710?source=rss-edda8e4063c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:01:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaexynn710/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Hidden Leakage: How Front of House Inefficiencies Erode Profitability in Luxury Resorts]]></title>
            <link>https://medium.com/@jaexynn710/the-hidden-leakage-how-front-of-house-inefficiencies-erode-profitability-in-luxury-resorts-417e6da93daf?source=rss-edda8e4063c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/417e6da93daf</guid>
            <category><![CDATA[hospitality]]></category>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[data-analyst]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jeasson Oktavianus Gatur]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 12:10:16 GMT</pubDate>
            <atom:updated>2026-11-13T12:10:16.238Z</atom:updated>
            <content:encoded><![CDATA[<h3>A data driven look into F&amp;B cost management, POS anomalies, and the gap between operational reality and financial reporting.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t0MHygvWFUxJN7pFidcMdQ.jpeg" /><figcaption>The frontline of revenue capture: A beachfront Point of Sale (POS) workstation where operational realities meet financial data. (Photo: Author’s Documentation)</figcaption></figure><p>Crystal clear waters, flawless service, and premium culinary experiences. To the average guest, a five-star resort in Koh Samui represents the pinnacle of operational perfection. But beneath that polished surface, revenue is often quietly hemorrhaging.</p><p>During my six-month tenure as a Food &amp; Beverage Cost Management Trainee at a luxury property in Thailand, I discovered a fundamental truth that accounting textbooks rarely emphasize: the biggest threat to a hospitality business’s bottom line isn’t the fluctuating cost of premium ingredients. It is the breakdown of data integrity at the Point of Sale (POS).</p><p>Accountants are trained to balance the books, analyze variances, and ensure internal controls are met. However, financial reports are only as accurate as the raw data fed into them. In a high-volume resort environment, that data is generated on the chaotic, fast-paced operational floor by the Front-of-House (FOH) staff.</p><h3>The Anatomy of Cost Leakage</h3><p>In theory, managing F&amp;B costs is a straightforward equation of comparing standard costs against actual expenses. In reality, the transaction log of a cloud POS system reveals a different story.</p><p>When conducting daily revenue audits, I identified several recurring blind spots where operational friction directly translated into financial loss:</p><ul><li><strong>Discretionary Discounts and Voids:</strong> Empowering staff to offer discounts for service recovery is standard in luxury hospitality. However, without strict parameter controls within the POS, unstructured discounts blur the line between guest satisfaction and revenue leakage. A simple 10% discount applied to the wrong sub-total category compounds significantly over a month.</li><li><strong>The Room Charge Disconnect:</strong> In an integrated resort, F&amp;B outlets must seamlessly sync with the Property Management System (PMS) at the Front Office. A mistyped room number, a delayed posting, or a failure to verify a guest’s credit limit at the restaurant level creates reconciliation nightmares the next morning, often resulting in written-off revenue.</li><li><strong>Manual Data Entry Errors:</strong> Fast-paced service environments breed manual input errors. Selecting the wrong modifier, bypassing inventory depletion protocols, or failing to record waste directly skews the Cost of Goods Sold (COGS) and inventory valuation.</li></ul><h3>Bridging the Gap Between Floor and Ledger</h3><p>The root cause of these issues is not a lack of accounting procedures, but a disconnect in cross-departmental integration. FOH staff often view the POS merely as a tool to fire orders to the kitchen and print receipts. They rarely see it as the primary data collection point for the resort’s financial ecosystem.</p><p>To mitigate this, cost control cannot be a reactive process confined to the back office. It requires a proactive, systems-thinking approach:</p><ol><li><strong>System Level Guardrails:</strong> Cloud POS systems must be configured with hard stops. Discount matrixes should require managerial override for specific thresholds, and voided items must automatically trigger a reason-code prompt that feeds directly into the daily audit report.</li><li><strong>Operational Financial Literacy:</strong> Front-line staff need to understand the financial weight of their keystrokes. Training should extend beyond menu knowledge to include the basic mechanics of revenue capture and inventory depletion.</li><li><strong>Real Time Data Reconciliation:</strong> Moving away from next-day manual audits to automated, real-time variance tracking allows cost controllers to spot anomalies — such as a sudden spike in open checks or unposted room charges — before the operational day closes.</li></ol><h3>The Modern Analyst Belongs on the Floor</h3><p>Sitting behind a spreadsheet analyzing historical data is no longer sufficient for modern financial management. True cost control requires understanding the operational behavior that generates the data.</p><p>My time in Koh Samui proved that whether you are an income auditor, a financial analyst, or a data scientist, your models and reports are useless if you do not understand the human element at the point of transaction. The numbers on the balance sheet are simply a reflection of the discipline on the restaurant floor. To fix the numbers, you must first fix the operation.</p><p><em>Disclaimer: The views, thoughts, and opinions expressed in this article are solely those of the author based on general industry observations. They do not reflect the specific financial data, operational policies, or confidential information of any past or present employer.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=417e6da93daf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Follow-Up Gap: Why Internal Audit Findings Fail to Drive Real Change]]></title>
            <link>https://medium.com/@jaexynn710/the-follow-up-gap-why-internal-audit-findings-fail-to-drive-real-change-8513e1c01cbd?source=rss-edda8e4063c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8513e1c01cbd</guid>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[internal-audit]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[Jeasson Oktavianus Gatur]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 09:00:01 GMT</pubDate>
            <atom:updated>2026-10-20T02:23:39.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wM1XI9CY5dd16vApCrGtOw.jpeg" /></figure><p><em>The report is issued, the applause is over, and a year later the same finding shows up again. What happened?</em></p><p>Written By Jeasson Oktavianus Gatur, Diya Christiyasari,Tita Refi Maret,Siti Amaliyah. Supervisor : Irda Agustin Kustiwi, S.A., M.A., CGAA.</p><p>Almost every internal auditor has lived this moment.</p><p>You open last year’s audit report to prepare for a new engagement. You reach finding number three: user access that isn’t reviewed on a regular basis. Then you look at this year’s draft, and your stomach drops. The wording is nearly identical. Only the date has changed.</p><p>The status of last year’s finding? <em>Closed.</em></p><p>At that point, the question isn’t “who dropped the ball?” It’s something far more uncomfortable: <strong>if the finding was closed, why is the problem still here?</strong></p><p>Welcome to the <em>follow-up gap</em>: the distance between what an audit reports and what actually changes.</p><h3>A good audit isn’t always an impactful one</h3><p>Our profession tends to take pride in what can be counted: engagements completed, findings raised, reports issued on schedule. All of that matters. But every one of those numbers measures <em>activity</em>, not <em>outcomes</em>.</p><p>A sharp, well-written report delivered on time means very little if the organization doesn’t change after reading it. The value of internal audit isn’t created when the report goes out. It’s created when someone on the front line changes the way they work.</p><blockquote><em>An audit report is just an invitation to change. Follow-up is where that invitation is either accepted or quietly declined.</em></blockquote><h3>Five reasons findings stall on paper</h3><p>After watching this pattern play out across many organizations, I’m convinced the cause is rarely bad intent. More often it’s a design problem: how we write findings, how we agree on actions, and how we track them.</p><h3>1. The finding is written for auditors, not for the people who have to fix it</h3><p>We’re trained to write in terms of criteria, condition, cause, and effect. The structure is sound. But the content is often too abstract for the person who has to act on it.</p><p>Compare these two sentences:</p><ul><li><em>“There is no adequate mechanism for user access review.”</em></li><li><em>“In March, 14 accounts belonging to former employees were still active, and two of them could still approve payments.”</em></li></ul><p>The first one earns a polite nod. The second one gets people moving.</p><h3>2. The action plan is too polite</h3><p>Ever seen an action plan like this? “Controls will be strengthened.” Due date: <em>Q4</em>. Owner: <em>Relevant department</em>.</p><p>That’s not a plan. That’s a good intention with a date attached. Without a specific action, a named owner, and evidence someone can actually check, a plan like this simply postpones the problem in a very tidy way.</p><h3>3. Nobody truly owns the fix</h3><p>Finding owners are often chosen because of their title, not because they have the authority or resources to make the fix happen. So they agree in the closing meeting, then return to the other 40 priorities that are louder and more visible to their boss.</p><p>Fixing an audit finding almost always competes with business targets. And in that contest, business targets usually win unless a senior sponsor makes it clear that this matters too.</p><h3>4. Closure is based on documents, not results</h3><p>This is the subtlest trap. New procedure written? <em>Closed.</em> Memo circulated? <em>Closed.</em> Training delivered? <em>Closed.</em></p><p>But the right question isn’t “does the document exist?” It’s “<strong>has the risk actually gone down?</strong>” A beautiful procedure in a shared folder doesn’t stop anyone from doing exactly what they did yesterday.</p><h3>5. The incentives don’t favor fixing things</h3><p>Who gets recognized for closing an audit finding? Almost no one. Meanwhile, the person whose area was audited often feels their reputation took a hit. In that environment, it’s natural to get defensive rather than open.</p><p>If an organization penalizes candor and ignores improvement, it shouldn’t be surprised when follow-up turns into an administrative game.</p><h3>The human side we tend to forget</h3><p>Here’s something textbooks rarely mention: <strong>the person receiving the finding is a human being who feels like they’re being judged.</strong></p><p>Picture a branch manager with 15 years of experience. The audit team arrives, stays two weeks, and leaves with a list of her team’s shortcomings. We call them “opportunities for improvement.” She may experience them as a verdict delivered in front of her boss.</p><p>No action plan will succeed if its owner feels cornered. Change rarely grows out of fear. It grows out of trust.</p><p>That doesn’t mean softening findings or avoiding uncomfortable facts. Independence and rigor are non-negotiable. What changes is how we show up: as a <em>critical partner</em>, not a <em>judge passing through</em>.</p><h3>What actually helps</h3><p>There’s no magic formula, but a few habits show up consistently in audit functions with strong follow-up.</p><p><strong>Write findings around impact.</strong> Start with what could happen to the business, not which standard was breached. Use numbers, real examples, and the language process owners use every day.</p><p><strong>Build the action plan together, don’t hand it over.</strong> Auditors don’t have to write the solution, but they do have to make sure it’s specific: what will be done, who will do it, by when, and what evidence will prove it.</p><p><strong>Break big fixes into small milestones.</strong> A twelve-month deadline with no checkpoints is a recipe for a surprise in month eleven. Quarterly milestones make progress visible and surface obstacles early.</p><p><strong>Verify outcomes, not just paperwork.</strong> Take a sample. Re-test the control. Ask people on the ground, “If this situation came up today, what would you do?” Their answer is more honest than any status report.</p><p><strong>Escalate with a clear path and without drama.</strong> Agree upfront on when a delayed finding will go to senior management or the audit committee. When the rules are transparent from day one, escalation feels like procedure, not an attack.</p><p><strong>Go after root causes, not symptoms.</strong> A repeat finding almost always points to a root cause nobody has touched: workload, systems that don’t support the control, or fuzzy ownership. Fixing the symptom over and over just drains everyone’s energy.</p><p><strong>Celebrate real closure.</strong> A sincere thank-you and recognition in front of leadership may sound minor, but it changes how people see audit: from a threat to a source of progress.</p><h3>Questions worth asking yourself</h3><p>Before you close this tab, here are a few questions every audit leader, and every manager who has ever received a finding, should consider:</p><ol><li>What percentage of our findings reappear in two consecutive audit cycles?</li><li>Of the findings marked <em>closed</em>, how many have we re-tested for effectiveness?</li><li>Do finding owners have the authority and resources to actually fix the issue?</li><li>Is there a senior sponsor who openly backs the remediation?</li><li>If someone rereads our report tomorrow, will they understand <em>why</em> it matters, not just <em>what</em> went wrong?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBUyhiC8cZ61cz2OWpth1g.jpeg" /></figure><p>Honest answers to these questions are often worth more than the entire audit KPI dashboard.</p><h3>Closing thought: a bridge, not a gap</h3><p>The follow-up gap isn’t fate. It’s the result of hundreds of small decisions: how we write, how we listen, how we hold people accountable, and how we celebrate.</p><p>Internal audit isn’t really about finding what’s wrong. That’s the easy part. The real work is helping an organization <strong>change in ways that last</strong>, and that only happens if we stay engaged after the report is published.</p><p>So the next time you see the word <em>closed</em> next to a finding, pause and ask one simple question:</p><blockquote>Is this truly resolved, or has it just stopped being asked about?</blockquote><p><em>What has your experience with audit follow-up been like? Share it in the comments. If you found this useful, give it a clap and follow for more on audit, risk, and governance.</em></p><p><em>#InternalAudit #Governance #RiskManagement #AuditFollowUp #Leadership</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8513e1c01cbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>