Skip to main content

Find the Perfect Expense Automation Recipe for Your Company (Best 6)

Updated today

Starting from a blank screen to create automation rules can feel overwhelming — where do you even begin? We\'ve carefully selected the 6 essential automation policies that companies find most useful and organized them like \'recipes\'!

Without any complex deliberation, simply follow the configuration values in the guide below and you\'ll have a complete, airtight expense management system.

You can zoom in using your browser\'s zoom settings, or click on the images below to view them larger.

🚕 Late-Night Overtime Taxi Expense Control

  • Why is this needed?

    • Prevents careless expenses such as claiming taxi rides paid before 10 PM as overtime transportation costs.

  • How it works

    • When claiming overtime transportation expenses, if the payment was not made with a corporate card or was not used between 10 PM and 6 AM, the receipt will be flagged as \'Review Required\' so an administrator can check it again.

(Click) Follow Along

  • Start

    • Trigger: When a receipt is submitted

    • Start condition: Purpose is one of Overtime Transportation

  • Rule

    • Condition

      • Payment method does not include Corporate card

      • Or Transaction date/time outside range of 22:00 ~ 06:00

    • Action

      • Flag receipt as \'Review Required\'

You can zoom in using your browser\'s zoom settings, or click on the image to view it larger.

📝 Mandatory Documentation for High-Value Payments

  • Why is this needed?

    • Enforces detailed supporting documentation such as attachments and memos for high-value corporate card or tax invoice payments exceeding 1,000,000 KRW.

  • How it works

    • For high-value transactions over 1,000,000 KRW paid by corporate card or tax invoice, users must fill in the \'Attachment\' and \'Memo\' fields before they can submit the receipt, ensuring detailed supporting documentation is provided.

(Click) Follow Along

  • Start

    • Trigger: When a receipt is submitted

    • Start condition: Payment method is one of Corporate card, Tax invoice

  • Rule

    • Condition: Total amount · full exceeds 1,000,000 KRW

    • Action: Add required fields to receipt (Required fields: Attachment, Memo)

You can zoom in using your browser\'s zoom settings, or click on the image to view it larger.

🏖️ Preventing Personal Use of Corporate Cards on Weekends

  • Why is this needed?

    • Makes weekend corporate card transactions without prior approval clearly visible to administrators and allows them to verify the reason.

  • How it works

    • If a corporate card is used on Saturday or Sunday, instead of allowing direct submission, the system automatically prompts the user to complete a \'Weekend Use Authorization Form\' explaining the reason for the expense.

(Click) Follow Along

  • Start

    • Trigger: When a receipt is submitted

    • Start condition: Payment method is one of Corporate card

  • Rule

    • Condition: Transaction date · day of week is one of Sat, Sun

    • Action: Expense report required (Recommended form: Weekend Use Authorization Form)

You can zoom in using your browser\'s zoom settings, or click on the image to view it larger.

💼 Preventing Business Trip Expense Claims Without Actual Travel

  • Why is this needed?

    • Integrated with HR attendance data, this catches errors where someone claims business trip expenses when they are not actually on a business trip.

  • How it works

    • When business trip expenses are submitted, if even one person included in the claim does not have a \'business trip\' status in their work records for that date, the receipt is flagged as \'Review Required\' since it may have been claimed incorrectly.

(Click) Follow Along

  • Start

    • Trigger: When a receipt is submitted

    • Start condition: Purpose is one of Business trip expenses

  • Rule

    • Condition: User · work policy one or more does not include Business trip

    • Action: Flag receipt as \'Review Required\'

You can zoom in using your browser\'s zoom settings, or click on the image to view it larger.

🍱 Tiered Lunch Expense Limits by Department

  • Why is this needed?

    • Even for the same lunch expense category, different limits are applied — 30,000 KRW for the Sales team and 15,000 KRW for all other departments — managed under a single unified policy.

  • How it works

    • When lunch expenses are submitted, different limits are checked based on the department. If the Sales team exceeds 30,000 KRW, or if any other department exceeds 15,000 KRW, the receipt is flagged as \'Review Required\' so an administrator can check it again.

(Click) Follow Along

  • Start

    • Trigger: When a receipt is submitted

    • Start condition: (None)

  • Rule

    • Condition: Purpose is one of Lunch expenses

      • Sub-rule 1

        • Condition

          • User · organization all is one of Sales team

          • And Total amount · full exceeds 30,000 KRW

        • Action

          • Flag receipt as \'Review Required\'

      • Sub-rule 2

        • Condition

          • User · organization all is one of Sales team

          • And Total amount · full is 15,000 KRW or less

        • Action

          • Flag receipt as \'Review Required\'

You can zoom in using your browser\'s zoom settings, or click on the image to view it larger.

👥 Per-Person Entertainment Expense Limit Management

  • Why is this needed?

    • Automatically checks whether entertainment expenses exceed the per-person limit (30,000 KRW) as required by internal policies such as the Kim Young-ran Act.

  • How it works

    • When entertainment expenses are submitted, if the amount per person exceeds 30,000 KRW, it is flagged as \'Review Required\'. Additionally, when someone outside the Sales team submits entertainment expenses, they are required to fill in companion information (who they dined with) as a \'mandatory field\', blocking submission until it is completed.

(Click) Follow Along

  • Start

    • Trigger: When a receipt is submitted

    • Start condition: (None)

  • Rule

    • Condition: Purpose is one of Entertainment expenses

      • Sub-rule 1

        • Condition

          • Total amount · amount per user exceeds 30,000 KRW

        • Action

          • Flag receipt as \'Review Required\'

      • Sub-rule 2

        • Condition

          • User · organization one or more does not include Sales team

        • Action

          • Add required fields to receipt

Could not display content

You can zoom in using your browser\'s zoom settings, or click on the image to view it larger.

Did this answer your question?