Vendor Onboarding
Runs on - click to open the live demo
What it does
A new supplier arrives as an email with a details packet, and someone keys it into the ERP across three tabs of general, payment and contact fields - including a bank account number that, if wrong, becomes a failed or misdirected payment down the line. This robot reads the request, fills all three tabs, and runs the IBAN through a mod-97 checksum before saving, so a bad account number is refused up front rather than discovered on a payment run.
Onboarding is data entry with a validation step, and that is an ideal hand-off for RPA: the robot does the re-keying no one enjoys and enforces the check no one should skip, turning a request in one system into a validated master record in another with nothing typed twice.
Related use cases
See allBank Reconciliation
Reconcile the payments finance could not tie out: read the ERP's exceptions, then check each one against the real bank statement and label every discrepancy - missing payment, transposed amount, double payment or unapplied cash.
Friday Payment Run
Prepare a weekly vendor payment run in the ERP: propose every bill due within seven days, and separately list the blocked bills with the reason each is on hold - a pending goods receipt, a price mismatch, or a missing PO.
Invoice Inbox to Ledger
Read vendor-invoice e-mails and post each as a bill in the ERP. Cancel a duplicate reference instead of paying twice, and post-but-block anything that fails the 3-way match against the purchase order.