When setting automation conditions for the first time, you might feel lost wondering "How do I configure this?"
This guide is an example dictionary that shows exactly "Here's how to configure it" for each real-world situation.
Find the situation you're curious about and follow along!
📖 What Are Operators?
Operators are rules that define "what criteria to compare by." They sound technical, but they're actually the same expressions we use every day.
Tip: You don't need to memorize operators! When you select a condition item in the builder, the available operators for that item are displayed automatically. Use the table above as a reference when you're unsure "what does this mean?"
Operator | Simply put | Example |
Is one of | "If any one of these matches" | If the purpose is one of Lunch, Late-night meal, or Snack → Match! |
Is not | "If none of these match" | If the payment method is not corporate card → Match! |
At least (≥) | "From this amount and above" | If the amount is at least 15,000 KRW → Match! |
At most (≤) | "From this amount and below" | If the amount is at most 5,000 KRW → Match! |
In range | "If within this range" | If the amount is between 10,000 KRW and 50,000 KRW → Match! |
Out of range | "If outside this range" | If the amount is under 10,000 KRW or over 50,000 KRW → Match! |
Before | "If earlier than this point" | If the payment time is before 9 AM → Match! |
After | "If later than this point" | If the payment time is after 10 PM → Match! |
At least one matches | "If at least one of these people is present" | If the attendees include at least 1 member of the sales team → Match! |
All match | "If all of these people are present" | If all attendees belong to the sales team → Match! |
None match | "If none of these people are present" | If there are no sales team members among the attendees → Match! |
Is empty | "If nothing was entered" | If the memo field is empty → Match! |
Is not empty | "If something has been entered" | If there is at least 1 attachment → Match! |
🍔 Meal Expense Examples
Example 1. Warning when lunch expense exceeds 15,000 KRW per person
🗣️ Our company's situation: "Lunch expenses should be limited to 15,000 KRW per person, but we want to allow submission even when exceeded."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Purpose | Is one of = Lunch |
Rule > Condition | Requested amount > Total amount / number of users | At least (≥) 15,000 KRW |
Rule > Action | Action | Flag receipt for review |
Right panel | Automation description | "Lunch expenses are limited to 15,000 KRW per person. Exceeding this will flag the receipt for review." |
Result: If a member submits a lunch receipt for 3 people totaling 45,000 KRW (15,000 KRW per person) → Passes ✅
If a member pays 40,000 KRW for lunch alone (40,000 KRW per person) → Warning popup ⚠️
Example 2. Late-night meal — Sales team 30,000 KRW, others 15,000 KRW (condition-based actions)
🗣️ Our company's situation: "The late-night meal limit is different for the sales team vs. other departments. We want to manage this in one automation."
In this case, enable the [Condition-based actions] feature and separate condition groups.
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Purpose | Is one of = Late-night meal |
Group A: Sales team standard | ||
Group A > Condition 1 | User > Organization | At least one matches = Sales Team |
Group A > Condition 2 | Requested amount > Total amount / number of users | At least (≥) 30,000 KRW |
Group A > Action | Action | Flag receipt for review |
Group B: Other departments standard | ||
Group B > Condition 1 | User > Organization | None match = Sales Team |
Group B > Condition 2 | Requested amount > Total amount / number of users | At least (≥) 15,000 KRW |
Group B > Action | Action | Flag receipt for review |
Result:
Sales team member with 25,000 KRW per person for late-night meal → Passes ✅ (under 30,000 KRW)
Sales team member with 35,000 KRW per person for late-night meal → Warning ⚠️ (over 30,000 KRW)
Marketing team member with 20,000 KRW per person for late-night meal → Warning ⚠️ (over 15,000 KRW)
⏰ Time/Day Examples
Example 3. Warning for weekend payments
🗣️ Our company's situation: "Using corporate cards on Saturday or Sunday is generally not allowed, but it happens occasionally."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | (None) | Applies to all purposes |
Rule > Condition | Transaction date/time > Day of week | Is one of = Saturday, Sunday |
Rule > Action | Action | Flag receipt for review |
Result: Friday payment receipt → Passes ✅ / Saturday payment receipt → Warning ⚠️
Example 4. Memo required for late-night payments (after 10 PM)
🗣️ Our company's situation: "We want to require a reason for corporate card use after 10 PM."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Payment method | Is one of = Corporate card |
Rule > Condition | Transaction date/time > Time | After 22:00 |
Rule > Action | Action | Add required fields → Memo |
Result: Corporate card payment at 9 PM → Passes ✅ / Payment at 11 PM → Memo required ⛔
💼 Payment Method / Amount Examples
Example 5. Attachment required for non-corporate card payments
🗣️ Our company's situation: "We need to receive a receipt photo for items paid with a personal card or cash receipt."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Payment method | Is not = Corporate card |
Rule > Condition | (None — applies to all) | |
Rule > Action | Action | Add required fields → Attachment |
Note: "Is not = Corporate card" here means "all payment methods other than corporate card."
That is, it covers all non-corporate card methods: personal card, cash receipt, simple receipt, etc.
Example 6. Expense report required for payments of 500,000 KRW or more
🗣️ Our company's situation: "We need to receive an expense report for large payments. It would be great if the form is automatically linked."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | (None) | Applies to all purposes |
Rule > Condition | Total amount > Total amount | At least (≥) 500,000 KRW |
Rule > Action | Action | Require expense report → Link [Large Payment Expense Report] form |
Note: The difference between "Total amount" and "Requested amount" can be confusing.
Total amount: The total amount on the receipt (including VAT). Mainly used with the "receipt generated" trigger.
Requested amount: The requested amount the member entered when submitting. Mainly used with the "receipt submitted" trigger.
In general, it is recommended to use "Requested amount."
👥 User / Organization / Work Policy Examples
Example 7. Attendee entry required for entertainment expenses
🗣️ Our company's situation: "An attendee list is absolutely required for entertainment expenses for tax documentation purposes. It cannot be missing."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Purpose | Is one of = Entertainment |
Rule > Condition | (None — applies to all entertainment expenses) | |
Rule > Action | Action | Add required fields → Users (attendees), Memo |
Note: Leaving the rule's conditions empty means it applies to "all entertainment expense receipts."
Since the start condition already filters for "purpose = entertainment," you only need to add rule conditions when you want to narrow things down further.
Example 8. Business travel expense — work policy mismatch warning
🗣️ Our company's situation: "Sometimes expenses are submitted as travel expenses even though there's no actual travel scheduled."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Purpose | Is one of = Business travel |
Rule > Condition | User > Work policy | Is not = Business trip |
Rule > Action | Action | Flag receipt for review |
Result:
Travel expense submitted 2/9 + work policy on 2/9 is "Business trip" → Passes ✅
Travel expense submitted 2/9 + work policy on 2/9 is "Office work" → Warning ⚠️ "Work policy does not match"
Note: The work policy condition checks the work status registered in the HR system on the day of the receipt's transaction date. It is based on HR system data, not whether the member filed a travel request.
🔄 Combination Examples
Example 9. Warning for meal expenses outside lunchtime (AND combination)
🗣️ Our company's situation: "Lunch expenses should only be used during lunchtime, but occasionally they're used outside those hours."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Purpose | Is one of = Lunch |
Rule > Condition 1 | Transaction date/time > Time | Before 11:00 |
OR | ||
Rule > Condition 2 | Transaction date/time > Time | After 14:00 |
Rule > Action | Action | Flag receipt for review |
Caution: Conditions are AND (and) by default. No time can simultaneously satisfy "before 11 AM AND after 2 PM," so in this case you must create 2 separate automations.
Automation A: Lunch + time before 11:00 → Warning
Automation B: Lunch + time after 14:00 → Warning
Example 10. Attachment + memo required for online commerce payments
🗣️ Our company's situation: "For online commerce expenses, we need to receive both a detailed item receipt and the reason for purchase."
Screen location | Field | Setting value |
Start trigger | Start trigger | When a receipt is submitted |
Start condition | Purpose | Is one of = Online commerce, Office supplies |
Rule > Condition | (None — applies to all) | |
Rule > Action | Action | Add required fields → Attachment, Memo |
Note: You can select multiple purposes in the start condition. Setting "Is one of" means it applies to receipts submitted under either "Online commerce" or "Office supplies."
FAQ
I want to apply both "lunch expenses over 15,000 KRW" and "attachment required for lunch expenses" simultaneously.
I want to apply both "lunch expenses over 15,000 KRW" and "attachment required for lunch expenses" simultaneously.
Just create 2 separate automations!
Automation A: Lunch + at least 15,000 KRW per person → Flag for review
Automation B: Lunch → Attachment required
If a single receipt triggers both automations simultaneously, both actions are applied.
How do I set the start condition to apply to "all purposes"?
How do I set the start condition to apply to "all purposes"?
Simply leave the start condition empty! If nothing is added to the start condition, the automation works for all receipts that occur at that start trigger.
What is the difference between "at least" and "greater than"?
What is the difference between "at least" and "greater than"?
The builder uses "at least (≥)." This means including that amount and above.
At least (≥) 15,000 KRW = 15,000 KRW is included, 15,001 KRW is included
To express "greater than," set the amount 1 KRW higher. (At least 15,001 KRW = greater than 15,000 KRW)
What happens when I select multiple items in "Is one of"?
What happens when I select multiple items in "Is one of"?
It works as an OR (or) condition. It matches if any one of the selected items applies.
Example: Purpose = [Lunch, Late-night meal, Snack] → Triggers if any one of these three purposes matches
I'm confused between "At least one matches" and "All match."
I'm confused between "At least one matches" and "All match."
These are operators for comparing lists of people. For a receipt with attendees [Kim Chul-su, Lee Young-hee, Park Min-su]:
At least one matches = Sales team → Matches if at least one of them is on the sales team
All match = Sales team → Only matches if all three are on the sales team
None match = Sales team → Only matches if none of the three are on the sales team
If I add multiple conditions, is it AND or OR?
If I add multiple conditions, is it AND or OR?
Conditions in the rule area are basically AND (and) relationships. All conditions must be satisfied for the action to trigger.
If you need OR (or) conditions, you must create separate automations for each.
Example: "Amount over 15,000 KRW or weekend payment" → Automation A (amount condition) + Automation B (day condition)