If this, then that, for your paperwork.

Approve clean e-invoices on sight. Send anything over 5,000 to a manager. Push approved invoices into your own tools, and hear about failures the moment they happen. Set a rule once and Cribble applies it to every document that arrives.

Get started
An accounting professional checking a line on a flat paper invoice against extracted fields on a laptop

Conditions you actually think in

Document type, who sent it, amounts, currency, and Cribble's own confidence scores. A rule like “e-invoices under 500: approve” takes a minute to build, and you can preview it against your recent documents before switching it on.

Actions with guardrails

Auto-approve, route to a named colleague for sign-off, apply expense coding, email the right person, hand off to Zapier, Make or n8n, or post straight to your accounting software. Posting without a human has stricter guards than posting with one: a confirmed supplier and clean validation, or the rule stands down and a person decides.

Every run on the record

Each time a rule acts, it writes what it did into the document's history. Nothing approves, moves, or posts without a line that says which rule did it and why. Automating the work never means losing the audit trail.

Automation you can audit

A rule isn't there to remove people from the process. It's there to remove the routine. The invoice that arrives every week from the same supplier, correct every time, shouldn't cost a click, and the odd one out should get all of your attention. Rules draw that line exactly where you put it.

Confidence scores are what make the line trustworthy: a rule can require 95% extraction confidence before it approves anything, so automation only ever touches documents the system is genuinely sure about. Everything else lands in your inbox for review, the same as always. Automation rules are included in the Business plan.