Platform
Everything intake needs before a queue can run itself
The landing page shows four things. This is all of it — the extraction layer, the routing rules that decide where an item goes, the reporting that explains a rising exception rate, and the controls a security team will ask about before your supplier mail lands here.
01
Extraction
Reading what actually arrived, in the format the sender felt like using.
Format-agnostic intake
Scanned PDFs, spreadsheets, portal exports, EDI files and the body of an email that says "see below". One pipeline reads all of them and produces the same typed record, so a downstream rule never has to care how something arrived.
Field-level confidence
Every extracted field carries its own score and the region of the source it came from. A total the model is unsure about routes for review; the ninety percent of the document it read cleanly does not need re-keying.
Layout drift tolerance
A supplier who redesigns their invoice does not break a template, because there is no template. Extraction is anchored on what a field means rather than on where it sat last quarter.
Duplicate and near-duplicate detection
The same invoice sent twice, once as a PDF and once as a chased reminder, is one item. Caught before routing, which is the difference between a suppressed duplicate and a duplicate payment.
02
Routing
The part that decides where an item goes, and when it goes to a person instead.
Rules as configuration
Routing written against properties of the item — amount, supplier, entity, contract status, confidence — rather than against a canvas of boxes and arrows. Version-controlled, reviewable, and testable against historical intake before it ships.
Shadow routing
Switchyard decides but does not act. Run a fortnight beside your existing process and compare its decisions against what your team actually did, one queue at a time.
Exceptions that arrive with a reason
An item held for review says why — low confidence on a field, a supplier not on file, an amount above a threshold, two rules in conflict. A queue of unexplained exceptions is just an inbox with extra steps.
Straight-through thresholds
Set, per queue, the confidence above which an item posts without a human. Raise it on the queues that matter and lower it where the cost of being wrong is a correction rather than a payment.
03
Reporting
Explaining a rising exception rate before it becomes a hiring plan.
Exception rate by reason
The one number that governs how many people this work needs, broken down by the cause. Most teams find two or three suppliers account for most of it.
Full item history
The source document, the extracted fields, the rule that fired, the person who overrode it and where it finally landed — stored together, searchable, and exportable.
Cost and handling time
Processing cost and human minutes attributed per queue and per supplier, so an expensive intake stream is traceable to the specific step making it expensive.
Drift alerts
Alert on the distribution of outcomes rather than on errors. A supplier whose format changed subtly does not throw an exception; it quietly moves the confidence curve, and that is visible here.
04
Security & compliance
What the review board asks for, answered before they ask.
Tamper-evident audit trail
Append-only, hash-chained, exportable, and legible to an auditor who does not work in your operations team. Written for the room where a posting has to be explained.
SSO, SCIM and RBAC
SAML and OIDC single sign-on, directory-synced provisioning, and role-based access down to individual queues and intake channels.
Data residency
Pin extraction and storage to a region, or run the extraction plane inside your own account with the control plane hosted. Supplier documents contain more personal data than most teams expect.
Configurable retention
Retention windows per queue with a hard floor, explicit legal hold that suspends deletion, and a surviving record of anything deleted on schedule.
Forward one mailbox and watch.
Let it route in the background for a week and compare its decisions against your team's. If they match, you have your afternoons back.
Free for 14 days · No card required