Invoice Processing Bot
Simulate a real accounts payable workflow. Validate a batch of vendor invoices, apply business rules, and decide the correct action for each one.
Challenge Overview
You are an RPA bot working for the Accounts Payable team. A batch of 6 vendor invoices has arrived and needs to be processed before end of day.
For each invoice you must: validate all fields, cross-check against business rules, and decide whether to Approve, Reject, or Escalate it — then enter the correct reason code. Mistakes cost the company real money, so precision is everything.
Business Rules
Apply these rules in order of priority. The first matching rule wins.
Amount > $10,000
Escalate to managerMissing PO number
RejectVendor not in approved list
RejectDue date already passed
Flag as overdueDuplicate invoice number
RejectTax % outside 0–18%
Reject (flag for review)All fields valid + amount ≤ $10k
ApproveStep-by-step Instructions
1. Open the test system and read the invoice data shown on screen
2. Open the first invoice in the test system
3. Check every field: vendor, PO number, amount, tax %, due date, and duplicate status
4. Apply business rules in order — the first matching rule determines your action
5. Select the correct decision (Approve / Reject / Escalate)
6. Choose the reason code that matches your rule
7. Check if the due date has already passed and set the overdue flag accordingly
8. Submit and move to the next invoice
9. Complete all 6 invoices for the final score
What you will learn
✔ Applying conditional business rules with priority ordering
✔ Exception handling — recognising and correctly flagging edge cases
✔ Multi-document batch processing with consistent logic
✔ Audit trail thinking: selecting the right reason for every decision
✔ Date comparison logic (overdue detection)
✔ Duplicate detection across a batch
✔ Automation exposure: invoice automation, AP workflows, document validation bots, ERP data entry
Common mistakes
• Approving an invoice that has a missing PO number
• Escalating a duplicate instead of rejecting it
• Forgetting to set the overdue flag when the due date has passed
• Approving a high-value invoice instead of escalating
• Not checking tax % before deciding to approve
Complexity
Advanced
Real business logic, exception paths, and multi-rule evaluation.