AI back-office automation built around one rule: AI interprets, rules decide
Sullivam provides digital workers for repetitive back-office operations. The first one, Invoice Worker, handles supplier invoices from inbox to prepared payable.
What a digital worker is
A digital worker owns one repetitive operation end to end: it receives the work where it arrives, understands it, checks it against your rules, does it when it is safe, asks a person when it is not, and writes down everything it did. You give it a job, not a flowchart.
| Digital worker | RPA bot | Chatbot | |
|---|---|---|---|
| Handles unstructured documents | Yes, with AI | Poorly | Answers questions about them |
| Who decides | Deterministic rules | The script | The model |
| When unsure | Stops and asks a person | Breaks or guesses | Improvises |
| Record of what happened | Full audit trail | Logs | Conversation |
Why AI should not make the decision
Language models are excellent at reading messy documents and poor at being accountable. So Sullivam splits the job: the model proposes values with a confidence level and a quote; deterministic checks decide whether anything happens automatically. The model can add a reason for review, but it can never approve or reject on its own.
Human in the loop, by design
- Uncertainty always leads to review, never to rejection.
- Reviewers see the document, the extracted values, the quote and the exact reason.
- Approving re-runs every check on the corrected values, so a person cannot approve past a real error.
- Every decision is recorded with who made it and when.
Choosing the first process to hand over
Not every back-office task is a good first job for a digital worker. The best candidates share a few traits:
- It repeats every day with the same shape: supplier invoices, not one-off negotiations.
- It arrives in one place, such as a shared mailbox, so the worker can pick it up without anyone forwarding it.
- The rules can be written down: totals must add up, duplicates are not paid twice, new vendors get a second look.
- Mistakes are visible and recoverable: a person can review the exceptions before anything irreversible happens.
- Someone owns the exceptions: automation concentrates judgement on fewer cases; it does not remove the need for it.
Supplier invoices tick every box, which is why Invoice Worker came first. Processes that move money, sign contracts or talk to customers on your behalf deserve a much more careful design before any of it runs on its own.
Where it starts, and what comes next
Invoice Worker is available today for supplier invoices arriving in Microsoft 365: invoice automation. Other back-office processes — contract review, request triage, vendor onboarding — are examples of where the same platform can go, not shipped products.
Sullivam serves companies in Latin America first: the application, onboarding and support are in Spanish today, with a partial English interface.
Frequently asked questions
Is Sullivam an RPA tool?
No. There is no screen scripting and no workflow builder. A digital worker owns a whole operation and uses AI only to read, never to decide.
Which processes can it automate today?
Supplier invoices received by email in Microsoft 365. Other processes are on the roadmap.
Put Invoice Worker to work on your invoices
We are onboarding a small group of founding companies. Applications are reviewed personally; the form is in Spanish.