12 to 18 September 2026
This week Automize added a supplier history ledger that catches changed bank accounts and duplicate invoices, made bot recordings run live with real-time approvals and progress, let triggers match Any, None or Exactly one filter row, surfaced the real reason a run failed so failures stop being a mystery, and extended remote control with scrolling, dragging and file transfer.
Catch a changed bank account or duplicate invoice the moment it arrives
Paying a supplier whose bank details just changed is one of the most common causes of fraud loss in accounts payable. Until now, spotting it meant someone manually comparing the new invoice against previous ones.
Automize now keeps a supplier history ledger. When a bot reads an invoice, credit note or supplier statement, it checks the document against everything the company has received from that supplier before - in the same step, with no extra work from your team.
Findings come back immediately: a bank account that changed since the last payment, an account that has never been approved, an invoice number that matches one already paid, a VAT or registration number that differs from the supplier's previous documents, a price that increased without notice, or a statement line for an invoice you never received.
The supplier ledger is available as a plan feature. Once switched on, suppliers appear in the Library with their invoices, findings, bank accounts and price history in one place. Old links to supplier pages redirect automatically, so nothing breaks for your team.
#AccountsPayable #Automation #SupplierManagement #Finance
Watch a bot record a process live, and approve each action as it goes
Handing a bot a standard operating procedure and asking it to build the automation used to mean waiting until it finished to find out what it had done. If something needed approval mid-way, there was no way to give it.
Now, when a bot records a process from an opportunity, you can watch it work in real time. An approvals box on the page updates every ten seconds and shows each action the bot is about to take - for example, "Create customer record" - with Approve and Decline buttons that actually work. The bot waits up to fifteen minutes for your answer before moving on.
The recording box stays still while you move your mouse to click Approve, so a page refresh mid-recording no longer causes a missed click. Progress lines show which stage the bot is in - reading documents, planning, recording, saving - and a step count ticks up as work happens.
For test or demo systems, there is an opt-in switch to approve actions automatically, with every auto-approval logged separately from human answers. The feature requires a bot on version 6.6.3 or later.
#DigitalWorkers #ProcessAutomation #RPA #Automation
Know exactly why a run failed, not just that it did
When a process failed repeatedly, the run history often said "Unrecognised failure" with no further detail. One process had 45 failures in two days and zero incidents raised, because the platform could not tell what the failures had in common.
Automize now records the cause of every failed run - which step failed, what class of error it was, and the specific code - and carries that through to the process page. A new "Why this keeps failing" panel reads those causes and spots patterns: failures bunched into certain hours of the day, the same step dying on every run, or work that only goes through on the third attempt.
Run History is now the single place for all failure information. It opens with a list of failing steps, most errors first, then the pattern analysis, then the individual runs. Clicking a finding in the panel scrolls the process map directly to the step in question.
Separately, when you click a process from the Launchpad, error messages from the server now reach you in plain words rather than a generic "An unexpected error occurred".
#ProcessAutomation #Operations #RPA #Automation
Start a process only when Any, None or Exactly one filter condition holds
Every trigger in Automize could already filter by conditions - start only when the sender matches, or only when the subject contains a keyword. But all the rows had to be true at once. There was no way to say "start when any one of these senders writes" or "start only when none of these words appear in the subject".
Triggers now have the same Match setting that decisions and loops already have: All of these, Any of these, None of these, or Exactly one of these. A trigger set to "Any of these" starts the process when at least one row holds; "None of these" starts it only when every row fails.
At the same time, a filter row that names a field the email or file does not actually have now fails the check and logs the mismatch, rather than silently treating the missing field as a match. The field suggestion list in the designer updates to show the right fields for each trigger type, so the most common mistakes are caught before saving.
Bots below version 6.6.8 will not receive triggers using Any, None or Exactly one, so existing automations are unaffected until the bot is updated.
#Automation #RPA #DigitalWorkers #Operations
Scroll, drag and copy files during a remote control session
Remote control let operators click and type on a bot's machine, but scrolling down a long page required a workaround, dragging was not possible at all, and moving a file to or from the machine meant a separate file-sharing tool.
Remote control now supports scrolling with the mouse wheel, dragging from one point to another, and copying files in both directions. Drop a file onto the remote screen to save it in the machine's Downloads folder; use Download selected to pull files that are highlighted in File Explorer or on the desktop. Files travel directly over the session and are never stored on Automize's side. Each transfer is limited to 50 MB and ten files, and every copy is written to the audit log - direction, size and a file fingerprint, never file names or paths.
Keyboard shortcuts that the operator's own computer would normally intercept - Alt+Tab, Win+R, Ctrl+Shift+Esc and others — are now available as buttons in the session toolbar. A notice appears on the machine's screen while someone has remote control, showing the operator's name.
Upload and download can each be switched on or off separately under Standards and compliance.
#RemoteControl #DigitalWorkers #Automation #Operations