Skip to content

Agent platform

AI agent templates: workflows by department

There are templates for finance, purchasing, engineering, administration, management and marketing that an agent works through. Each says where it runs and names its approval point.

In short

A template describes a flow for an agent: what starts it, which steps it takes, where a person approves and what comes out at the end. Each template runs in Documents, in ENGIVERITY or as a fixed flow in ERP and CRM, and the field 'Runs in' says which.

Updated: November 2026

Structure

How a template is built

All templates follow the same pattern. The table shows it using the incoming invoice.

Parts of a template
PartWhat it definesExample incoming invoice
Trigger What starts the flow. A document arrives through the mailbox, a folder, the interface or an upload.
Steps What the agent does, one after another. Read, check, propose an account assignment, open a clarification case.
Approval point Where a person decides. Confirmation of uncertain fields and approval of the posting.
Result What exists at the end. A checked document with account assignment and audit log.
Where it runs Runs in. Documents, ERP and CRM

Finance

These templates read documents, check them and prepare the posting before a person decides.

Check incoming invoices and prepare posting

An invoice is read and checked before anyone touches it.

Trigger. A document arrives through the mailbox, a folder, the interface or an upload.

Steps.

  1. A first reading and a second reading capture the document independently of each other.
  2. Totals, tax, IBAN and VAT ID are checked, and a possible duplicate is spotted.
  3. If the switch is on, the agent drafts an account assignment with a reason from master data and earlier confirmations.
  4. A deviation opens a clarification case.

Approval point. A person confirms every uncertain field against the scan excerpt and approves the posting. If you wish, the four-eyes principle and an approval chain with deputies apply.

Result. A checked document with its account assignment, handed over as a posting batch or file, with an entry in the audit log.

Runs in. Documents, ERP and CRM

Watch discount and contract deadlines

Nobody has to remember when a discount lapses or a notice period ends.

Trigger. A deadline comes up, such as a discount, notice, contract end or due date, or the daily run starts.

Steps.

  1. The deadline is read from the document.
  2. The condition is checked, for example whether a discount is about to lapse.
  3. A draft is prepared for the people responsible.

Approval point. The draft goes out only when a person sends it.

Result. A reminder with the document and the deadline.

Runs in. Documents

Prepare a query on a faulty document

The query to the sender is ready as a draft as soon as a document does not add up.

Trigger. A clarification case arises, for example through a mismatch in totals, a broken rule or a missing mandatory field. If it stays open for long, a reminder follows.

Steps.

  1. The reason for the clarification case is determined.
  2. The address comes from the business partner record.
  3. A draft with a clarification note is prepared.
  4. An open case triggers a reminder.

Approval point. A person sends the draft. Users without administrator rights can choose only addresses of the partner or its domains as recipients.

Result. The query that was sent is in the audit log, and the case stays open until it is resolved.

Runs in. Documents

Purchasing and warehouse

These templates match delivery notes, confirmations and master data against your records and present any deviations.

Post delivery notes and withdrawal lists

A photo of the delivery note is enough to start, and a person confirms uncertain fields before anything is posted.

Trigger. A photo, an upload, a scanner folder or an email.

Steps.

  1. The part number is checked against the master data.
  2. Order, job, unit, storage location and stock are matched.
  3. On handwritten slips a tick counts as withdrawn and a red circle as to be clarified.
  4. Only the ticked lines are posted.

Approval point. The warehouse role confirms in the screen. In shadow mode, the default, the agent reads real documents and hands over only a preview.

Result. A posting in the target format, at first marked as provisional.

Runs in. ENGIVERITY (target system: ERP and CRM)

Match order confirmations and quotes

Deviations from the order are spelled out in words, and every quote finds its enquiry.

Trigger. A document arrives.

Steps.

  1. For an order confirmation, quantity, price, date and unit of each line are checked against the order, within the tolerances of the profile.
  2. Every deviation is described in words.
  3. For a quote, supplier, lines and date count. The result is clear, ambiguous or no enquiry found.
  4. The order confirmation is filed under the naming scheme of the tenant.

Approval point. Purchasing confirms. If a match is ambiguous, a person chooses among candidates presented with a reason.

Result. A confirmed list of deviations, the filed order confirmation and the quote linked to its enquiry.

Runs in. ENGIVERITY (target system: ERP and CRM)

Clean up the article master

Duplicate parts and numbering errors show up as a list of proposals that you can work through quickly.

Trigger. By hand or on a schedule.

Steps.

  1. The master data is searched for duplicate parts and numbering errors.
  2. The agent proposes which number stays, based on stock, projects and bills of materials.
  3. Every proposal carries a reason in one sentence.

Approval point. The deciding role decides case by case or in bulk, including through an Excel return.

Result. A mapping from old to new numbers, import files marked as provisional and a control export.

Runs in. ENGIVERITY (target system: ERP and CRM)

Engineering and quality

These templates check bills of materials and data sheets and trace every answer back to its source.

Check and release incoming bills of materials

A new version of a bill of materials is checked before it goes to production.

Trigger. An upload, the event version created, or a start by hand.

Steps.

  1. The bill of materials is read in and checked.
  2. The flow branches by result, so blockers lead somewhere else than warnings.
  3. A report is written.
  4. The people who maintain the bills of materials receive a message.

Approval point. A reviewer confirms, then the project lead approves. A rejection requires a reason.

Result. A review report, an entry in the inbox and, after approval, a production package.

Runs in. ENGIVERITY

Check data sheets and query suppliers

Open points from data sheets reach the suppliers without anyone retyping values.

Trigger. A data sheet is uploaded.

Steps.

  1. The values are read.
  2. They are checked against the requirements.
  3. Open points are collected.
  4. A supplier query is prepared and a message is sent.

Approval point. Approval comes before the supplier query goes out. An agent creates open points only after that approval.

Result. Open points and supplier queries that were sent, every statement with a source reference.

Runs in. ENGIVERITY

Expert answers on a bill of materials

Anyone with a question about a bill of materials gets an answer with a source.

Trigger. A question in the chat.

Steps.

  1. The bill of materials, review results, drawing and knowledge are read.
  2. The answer carries a source marker for each statement.
  3. Every statement is rated as supported, contradicted or without a source.

Approval point. None needed, the agent writes nothing. A correction arrives only as a change proposal that the responsible role approves.

Result. A supported answer and, if wanted, a change proposal.

Runs in. ENGIVERITY

Sales and administration

These templates sort incoming emails and put together documents for third parties.

Sort the inbox, prepare drafts and tasks

The day starts with an overview instead of an overflowing inbox.

Trigger. An incoming email or the schedule for the daily overview.

Steps.

  1. The email is sorted.
  2. A task in the email is recognised and created.
  3. A reply is drafted.
  4. The personal daily overview pulls everything together.

Approval point. The person sends the draft themselves. This flow is built into the ERP and cannot be switched on or off per tenant.

Result. A draft, a task and the daily overview.

Runs in. ERP and CRM (fixed process)

Prepare and redact documents in a data room

Documents for third parties are ready, sorted and redacted, with time-limited access.

Trigger. An upload into a data room.

Steps.

  1. The document is split and classified.
  2. Fields are read out.
  3. Personal data is redacted.
  4. It is stored with a checksum and time-limited access.

Approval point. A second check verifies the redaction, and a person corrects it where needed. Access for third parties is time-limited.

Result. A classified, redacted document in the data room.

Runs in. ERP and CRM (fixed process), Documents

Management

These templates summarise key figures and answer questions about the document archive.

Daily and weekly report for management

Management reads a summary in the morning that nobody compiled by hand.

Trigger. The schedule, every morning or on Fridays.

Steps.

  1. The key figures of the previous day or the check run of the current version are gathered.
  2. The report is written from them.
  3. A notice goes out by email or into the inbox.

Approval point. None needed, the agent reads and reports. The report goes to the recipients you set.

Result. A report as an email or PDF.

Runs in. Documents, ENGIVERITY, ERP and CRM (fixed reports)

Ask your documents

The agent answers the question of what a partner invoiced last quarter, with source references.

Trigger. A question in the chat.

Steps.

  1. Documents and period of the partner are found through full-text search and a search by meaning.
  2. The answer names its sources.
  3. A possible action, such as sending a document to approval, appears only as a proposal.

Approval point. The same person confirms shortly afterwards. The chat runs with the permissions of the signed-in person.

Result. A supported answer and, once confirmed, a triggered action marked as coming from the chat.

Runs in. Documents

Marketing

This template prepares campaigns and bids and stops before every change.

This agent is built and set up on request. Ad Pilot reads and proposes. Writing back into the accounts is switched off today, so you carry out proposals yourself.

Propose campaigns and bids with a stop point

A brief becomes a campaign draft that stops at a checkpoint before any change.

Trigger. By hand or on a schedule.

Steps.

  1. Keywords are researched.
  2. Structure, ad copy and budget are drafted.
  3. Each product is matched to a landing page from the actual range.
  4. For bids and budgets the agent proposes only changes within fixed limits.
  5. The flow stops.

Approval point. The result sits as a bundle in the approval queue. A person decides, and a stop point separates approval from activation.

Result. A proposal checked in a dry run, with a log. Ad Pilot does not write back to the accounts today, so you carry out the proposal yourself.

Runs in. Ad Pilot

Adapting

Your own templates

In ENGIVERITY every template can be adapted in the flow workshop. Each save creates a new version, and you can return to the standard that ships with it at any time.

The templates that ship with Documents first sit switched off in the tenant. You can switch them on once all mandatory details are in place, and you can set up flows freely per tenant.

Building agents

Where to start

Which template to start with

It usually works best to begin with one narrowly defined routine that comes up often and follows clear rules. The incoming invoice is a good example.

Run the template in a dry run first and check every result until you trust the flow. For documents in ENGIVERITY, shadow mode comes first: the agent reads real documents and only hands over a preview. Live operation is off by default.

Dry run and shadow mode

Questions and answers

Questions about the templates

Can I change a template?

Yes. In ENGIVERITY you adapt templates in the flow workshop and save them as a new version. In Documents you set up flows per tenant yourself.

Which module runs which template?

Documents covers documents and deadlines, ENGIVERITY covers parts lists and warehouse documents. Mailbox and data room are fixed flows in ERP and CRM. Campaigns run in Ad Pilot, on request.

Who approves templates that send emails?

For templates that prepare emails to third parties, a person approves. The email starts out as a draft and goes out only when a person sends it. In Documents, users without administrator rights can change recipients only to addresses of the partner or its domains. Reports for management go to the recipients you set.

What if a template is missing?

Talk to us. Many flows can be assembled from building blocks, and we discuss the others in a project.

Is a template missing?

Describe the flow to us. We tell you whether an existing template fits or what can be built from it.