Example workflows
Altaris builds automations for the processes finance, accounting, IT and operations teams repeat by hand: invoice processing, bank reconciliation, service desk triage and management reporting. Each example below is a sequence somebody currently does manually. They show the shape of the work rather than case studies - no figures appear, because none have been measured yet.
Every one of these is a sequence somebody repeats. None of them needs new software - they need the systems already in use to talk to each other.
Finance — accounts payable
An invoice that files itself
Invoices arrive in a shared inbox as PDFs from fifty different suppliers in fifty different layouts. Someone opens each one, keys the supplier, date and total into the ledger, matches it against the purchase order and codes it. Connected, the invoice is read on arrival and only the exceptions reach a person.
Before
- Invoice arrives in the shared inbox
- Someone opens the PDF and reads it
- Supplier, date and total keyed into the ledger
- Line items matched against the purchase order
- Coded to a cost centre
- Chased if it is already overdue
6 steps, every one by hand
After
- Fields extracted
- Matched to the PO
- Posted to the ledger
- Exception flagged
1 step, the rest unattended
Accounting — reconciliation
The spreadsheet rebuilt every month end
Statements are exported from the bank, the ledger is exported from the accounting system, and somebody spends two days in a spreadsheet matching them line by line. Connected, the matching runs daily and the only thing a person sees is what did not match.
Before
- Export the bank statement
- Export the ledger
- Paste both into a spreadsheet
- Match line by line
- Investigate the differences
- Write up the variance
6 steps, every one by hand
After
- Matched automatically
- Variances listed
- Ledger updated
- Exceptions assigned
1 step, the rest unattended
IT — service desk
Tickets that route themselves
Requests arrive by email, chat and a form, and somebody reads each one to decide whose queue it belongs in. Priority is guessed from the wording, duplicates are spotted late, and the clock on the SLA started before anyone looked. Connected, the ticket is classified, enriched and assigned on arrival.
Before
- Request arrives by email, chat or form
- Someone reads it and decides the queue
- Priority set by hand
- Checked against open tickets for duplicates
- Assigned to an engineer
- Asset and licence details looked up separately
6 steps, every one by hand
After
- Classified
- Enriched with asset data
- Assigned to a queue
- Duplicate merged
1 step, the rest unattended
Operations — reporting
The Monday report nobody has time to build
Numbers are pulled from three systems, pasted into a template, checked against last week and sent out. It takes an operations manager a morning, it is late whenever somebody is on leave, and the figures are stale by the time the meeting reads them. Connected, the report is built on a schedule, the anomalies are flagged rather than hunted, and it is waiting before anyone sits down.
Before
- Export from each system in turn
- Paste into the template
- Fix the formatting
- Check against last week
- Email it round
5 steps, every one by hand
After
- Figures consolidated
- Report generated
- Distributed
- Anomalies flagged
1 step, the rest unattended
No hours-saved figure appears on this page. Every one would be an estimate, and an estimate dressed as a measurement is the thing that makes buyers stop believing the rest. Real numbers go up when a real client's before and after has been measured.
Questions we get asked
Are these real client results?
No, and we are not going to present them as such. These are the shapes of processes we build automations for. The moment a real before and after has been measured on a client system, it gets published with its numbers and the client named - and this page will point at it.
Our process is not any of these. Does that matter?
No. These are examples of a shape, not a menu. Most of the work is a variation nobody has written down yet, and some of it is not an integration at all but an internal tool that does not exist. If information is being moved between systems by a person, it is worth a conversation.
Tell us what you need built.
Describe the process you repeat and we will tell you whether it is worth automating - including when it is not. A fixed price for the build, quoted before anything starts.