Invoice automation that knows when to stop and ask
Sullivam's Invoice Worker picks up supplier invoices from your Microsoft 365 mailbox, extracts the data, checks your business rules and prepares the payable. When something does not add up, it stops and tells you exactly why.
Beyond data capture
Reading a PDF is the easy part. What eats an accounts payable team's day is everything around it: opening the email, downloading the attachment, keying in vendor, number, dates and amounts, checking the total, searching for an earlier copy of the same invoice and deciding what to do with the odd one out.
Real invoice automation runs that whole path on its own and hands the exceptions to a person with the reason already written down. A tool that only extracts text saves typing but leaves you with the deciding.
What Invoice Worker does with each invoice
- Receives it the moment Microsoft 365 reports a new email in the connected inbox.
- Classifies it: invoice, credit note, receipt, unrelated email or unsupported document.
- Extracts vendor, tax ID, invoice number, issue and due dates, currency, subtotal, tax, discounts, withholdings, total and purchase order reference, each with a confidence level and the exact quote it came from.
- Validates with deterministic rules — no AI involved: totals add up, not a duplicate, known vendor, sensible dates, and a PO reference when you require one.
- Decides: it only continues on its own when the reading is confident and every check passes. Any doubt goes to review.
- Prepares the payable and records everything in an audit trail: what it read, what it checked, who approved and when.
Each step in detail: invoice processing automation.
What runs automatically and what goes to review
| Situation | What Invoice Worker does |
|---|---|
| Everything checks out, known vendor, confident reading | Prepares the payable automatically |
| Total does not match subtotal and tax | Review, showing the difference |
| Possible duplicate (same file, or same number and vendor) | Review |
| New vendor | Review (you can choose reject or allow) |
| Missing purchase order reference | Review |
| Amount above your automatic limit | Review |
| Scanned or unreadable document | Review — there is no OCR and no guessed reading |
| Not an invoice or credit note | Marked as unsupported |
Uncertainty leads to review, never to rejection. A person can approve a new vendor or an invoice without a PO; nobody can approve a duplicate or a total that does not add up, because every check runs again on approval.
What it does not do
- It does not pay invoices or touch bank accounts.
- It does not read scanned documents or photos; those go to a person.
- It does not connect to accounting software or ERPs yet — those integrations are on the roadmap.
- It works with Microsoft 365 and Outlook today; Google Workspace is on the roadmap.
Sullivam serves companies in Latin America first: the application, onboarding and support are in Spanish today, with a partial English interface.
Frequently asked questions
Does the AI decide whether an invoice is recorded?
No. The AI interprets the document and proposes values; deterministic rules make the decision. The model cannot approve or reject anything on its own.
What happens when the same invoice arrives twice?
Sullivam flags it as a possible duplicate — by file or by number and vendor — and never prepares a second payable.
Can I review everything at first?
Yes. Require review for any reading that is not confident enough and set a low automatic amount limit while you build trust.
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.