Skip to main content
connic

Agents do the paperwork.
You handle the exceptions.

Agents read the emails, PDFs and scans that arrive, check them against your own systems and enter the result. Unclear or costly cases go to a person.

Halvard TMS · Incoming documents
Incoming documents
Today · orders@, invoices@ and driver uploads
2 need you
Transport order TO-88412.pdfPellworm FoodsEntered as order 2611-0457
Invoice BL-20931.pdfBaltic Line HaulageBooked, matches the agreed rate
Invoice MRC-7718.pdfMoravia Road CargoWaiting for approval, €184 above rate
Delivery note DN-55120-scan.pdfDriver uploadAttached to shipment 2610-0398
Invoice TFL-0391.pdfTatra Freight LinesNeeds review, shipment number missing

Each document type gets its own agent.

Four agents at a freight forwarder. Each reads one kind of document and writes the result into the systems the team already uses.

A shipper emails a transport order as a PDF. The agent reads pickup, delivery, dates and goods and creates the order in the transport system.

Order 2611-0457
tms.halvard.internal/orders/2611-0457
Halvard TMSOrdersShipmentsCarriersDispatch
Source
orders@pellworm-foods.example.com
Transport order TO-88412 · 08:14
TO-88412.pdf
PELLWORM FOODSTransport order
Order no.
TO-88412
Loading
Bremerhaven, Am Kai 4 · 13 Nov, 07:00–10:00
Unloading
Poznań, ul. Portowa 11 · 14 Nov, by 12:00
Goods
18 pallets chilled food, 9,450 kg
Temperature
2–6 °C
Order 2611-0457Created from email
Customer
Pellworm Foods · C-1042
Customer ref.
TO-88412
Pickup
Bremerhaven, Am Kai 4
Pickup window
Nov 13, 07:00–10:00
Delivery
Poznań, ul. Portowa 11
Deliver by
Nov 14, 12:00
Goods
18 pallets, chilled food
Weight
9,450 kg
Temperature
2–6 °C, reefer
  • Shipper found in customer list
  • Pickup before delivery, both in the future
  • Reefer required for 2–6 °C

The agent compares each invoice with the rate agreed for the shipment. Matching invoices are booked, and a deviation above the limit waits for approval.

Carrier invoices
erp.halvard.internal/payables/carriers
Halvard ERPPayablesCarriersReports
Carrier invoices, todayDeviation limit €50.00
CarrierInvoiceShipmentInvoicedAgreedStatus
Baltic Line HaulageBL-209312611-0371860.00860.00Booked
Moravia Road CargoMRC-77182611-03881,424.001,240.00Waiting for approval · +184.00
Elbe Valley TransportEVT-55202611-0402615.50615.50Booked
Baltic Line HaulageBL-209442611-0410905.00880.00Booked · +25.00 within limit
Tatra Freight LinesTFL-0391–1,100.00–Needs review · shipment missing
Elbe Valley TransportEVT-55272611-0415540.00540.00Booked

Amounts in EUR. Invoices within the limit are booked with the agreed rate saved on the entry.

Drivers upload signed delivery notes as scans. The agent attaches each scan to its shipment and records any damage noted on the paper.

Shipment 2610-0398
tms.halvard.internal/shipments/2610-0398
Halvard TMSOrdersShipmentsCarriers
Proof of delivery
DELIVERY NOTEDN-55120
Consignee: Saale Fresh Markets, Leipzig
Pallets: 24 · Weight: 11,200 kg
2 pallets damaged, corners crushed
Received, signature
DN-55120-scan.pdf · uploaded by driver
Shipment 2610-0398Delivered
Hamburg → Leipzig · Saale Fresh Markets · 24 pallets
  1. Nov 12, 06:10Loaded in Hamburg
  2. Nov 12, 15:20Delivered in Leipzig
  3. Nov 12, 15:41Delivery note DN-55120 scanned by driver
Scan attached as proof of delivery
Damage noted by recipient: 2 of 24 pallets, corners crushed. Added to the exceptions list.

At 7:00 an agent collects every case that waited for a person yesterday and posts the list with reasons to the dispatch channel.

#dispatch
chat.example.com/halvard/dispatch
dispatch
PaperworkBot07:00

Open exceptions from yesterday:

  • TFL-0391Tatra Freight Lines invoice has no shipment number, not booked
  • 2610-03982 of 24 pallets damaged, noted on delivery note DN-55120
  • TO-88420Kessel Paper order PDF is password-protected, not entered

Approved yesterday: MRC-7718, €184.00 above the agreed rate, by J. Okafor.

1 reply in thread
LM
Lena M.07:12
I'll call Tatra about TFL-0391 and ask Kessel for an open PDF.
Message #dispatch

From typing documents to deciding on exceptions.

Today your team opens, types and files every document. With agents, people see only the cases an agent puts in front of them.

Today, by hand
The documents that arrive each day
With agents on connic
The documents that arrive each day
connic

Sorting the inbox

Today, by hand: Someone opens every email, works out what the attachment is and passes it on

With agents on connic: Every new email starts an agent, and the agent reads the attachments itself

See how much paperwork the agents take off your team.

Every document is recorded with its input, result, duration and cost, so these figures need no extra tracking.

  • Share without a person

    Compare the cases a person approved or flagged for review with all documents in the period.

  • Cost per document

    Each run shows its model cost, broken down per agent, so you see what one invoice or one order costs.

  • Failed checks

    Failed runs show the full error first, and attachments that couldn't be read are listed with the reason.

  • Processing time

    Each agent's page shows how long its runs take. Time spent waiting for an approval shows separately in the run.

Every entry is checked, approved where it matters and on record.

The agent returns only the fields you define and uses only the tools you give it. Above your limits, a person decides.

Results in your format
You define the fields, types and allowed values of a result, and connic checks every result against them.
Costly cases wait for a person
A booking waits, for example when an invoice is more than your limit above the agreed rate. The reviewer sees the values the agent wants to enter and approves or rejects them.
A record of every document
Each run keeps the document, its result and every value the agent sent. The audit log shows who approved what.
Tested before every change
Sample documents become test cases that run before every release. A failing case stops it.
Invoice MRC-7718
erp.halvard.internal/payables/MRC-7718
Halvard ERP
Carrier invoice MRC-7718
Received by email, Nov 12
Booked
Carrier
Moravia Road Cargo
Shipment
2611-0388 · Hamburg → Brno
Invoiced
€1,424.00
Agreed rate
€1,240.00 · contract C-2026-14
Deviation
+€184.00 · limit €50.00
History
  1. 08:02Received from billing@moravia-cargo.example.com
  2. 08:02Read by agent carrier-invoice-check
  3. 08:03Agreed rate looked up: €1,240.00
  4. 08:03Held for approval: €184.00 above the agreed rate
  5. 09:41Approved by J. Okafor: waiting time at unloading confirmed
  6. 09:41Booked to 4730 Freight costs
Entered by connic run 3f9c2a1e, with the PDF the agent read

The rules live in two files your engineers can review.

The agent file names the output schema and the approval rule. The schema file lists every field the agent may return.

Output schema
Fields under required must be present, enum limits a field to fixed values, and additionalProperties: false rejects anything else.
Approval rule
The booking pauses when deviation_eur is above 50. Below that, the agent books the invoice on its own.
Flag for review
The prompt says when to set needs_review, and the run filter output.needs_review == true lists those documents.
agents/carrier-invoice-check.yaml
version: "1.0"
name: carrier-invoice-check
type: llm
model: connic/gemini-3.8-flash
description: "Checks carrier invoices against the agreed rate"
system_prompt: |
  Read the carrier invoice attached to the email.
  Look up the agreed rate for its shipment, then book it.
  If a field is unreadable, set needs_review and don't book.
tools:
  - tms.get_agreed_rate
  - erp.book_carrier_invoice
output_schema: carrier-invoice
approval:
  tools:
    - erp.book_carrier_invoice: param.deviation_eur > 50
  timeout: 86400
  on_rejection: continue
schemas/carrier-invoice.json
{
  "type": "object",
  "properties": {
    "invoice_number": { "type": "string" },
    "shipment_id": { "type": "string" },
    "amount_eur": { "type": "number", "minimum": 0 },
    "deviation_eur": { "type": "number" },
    "status": {
      "type": "string",
      "enum": ["booked", "held", "rejected"]
    },
    "needs_review": { "type": "boolean" }
  },
  "required": ["invoice_number", "amount_eur", "status"],
  "additionalProperties": false
}

Frequently Asked Questions

Email attachments arrive as PDF, images, Word, Excel, CSV, XML and other common formats, up to 50 per email. connic/* models with the Files label read PDFs, including tables and scanned pages, and some also read Word and Excel. Text formats reach every model as text. Files can also come from an upload bucket or a web form.

In one of two ways. A tool in your code writes through the system's API or database during the run, through a connic bridge if the system sits in your network. Or the agent returns the checked result, and an outbound webhook or queue hands it to your own integration.

You decide what counts as unclear, for example an unreadable field or a value that doesn't match your records. The agent flags those documents for a person instead of entering them. Attachments that can't be passed to the model, such as an unsupported file type, are listed in the run with the reason.

connic is hosted in the EU, and every connic/* model call runs in the EU. Managed inference isn't used to train models. Runs keep the documents for the retention you set per environment. If you use your own key for a model provider instead, that provider processes the model calls.

You can connect a mailbox and try a first agent on sample documents yourself, with free credit to start. If you want connic's team to build it with you, connic solutions start with 1 to 2 weeks of scoping, followed by a pilot on your data that takes 4 to 6 weeks.

Usage is paid from your Project credit, and the plans and rates are on the pricing page. Each run shows its token cost, so you can work out the cost per document from your own samples.