Ostrakoninvoice agentὄστρακον
Package leaflet: information for the user
Concept. Not a product.
Issue: concept A | Date: 2026-11-03
Read this whole leaflet carefully before you use Ostrakon. Keep it, you may want to read it again. If you have further questions, ask the person who is responsible for Ostrakon at your organisation.
The leaflet unfolds column by column as you read.
1What is Ostrakon and what is it used for?
Ostrakon reads incoming invoices, matches them to suppliers and accounts, and prepares postings. Ostrakon proposes. A person approves.
Areas of use
- Preparing postings
- Spotting duplicates
- Reminding about missing receipts
Ostrakon is not used for
- Triggering payments
- Changing master data
- Assessing contracts
- Decisions about people
2What should you know before using it?
Contraindication
Do not use Ostrakon if
- nobody carries responsibility for approval,
- the steps before Ostrakon are not clarified (see Hermeneia),
- you cannot or do not want to check the result (see Zählprobe),
- the receipts need special handling that is not written down (for example foreign-country cases, special cases of VAT).
Take particular care
If your process changes (a new mailbox, new accounting software, a new template from the supplier), pause Ostrakon and check again.
3How is Ostrakon to be used?
Scope
Start with a trial run on a small selection and read every posting against the source. Widen the scope only when the cross-check is clean. Write down beforehand what Ostrakon may do itself, what it may only propose, and when it asks back.
If you forget to approve Ostrakon
Nothing happens. Ostrakon does not post without approval.
4What side effects are possible?
As with any tool, side effects can occur. We give no frequencies because we have measured none. We sort them by when you notice them.
Visible at once
- A receipt is rejected or not read
- Ostrakon asks back
- A match is missing
Visible only at reconciliation
- An amount is misread
- A receipt is matched to the wrong account
- A duplicate is not spotted
Warning: visible only with a cross-check
- A “Done” message although nothing arrived
- Errors that settle in through even repetition
What you can do
- Plan a cross-check
- Have a person take a sample
- Report deviations
5Which other tools affect the result?
- Accounting software
- Interfaces change.
- Mailbox rules
- Rules move receipts before Ostrakon sees them.
- Approval chains
- Who is covered when someone is on leave?
- Other agents
- Two tools post the same receipt.
If you introduce another tool, check how they work together before you run both.
6Oversight and keeping the logs
Ostrakon writes a log for every action: what was read, what was proposed, who approved.
A person reads the log regularly, not only when something fails.
Keep it for the retention periods that apply, which your tax adviser knows. Ostrakon does not delete logs.
Who is responsible?
Name:
Deputy:
7If something goes wrong
Emergency stop
Do you know how to stop Ostrakon?
- Stop it.
- Secure the log.
- Have a person correct the affected postings.
- Clarify the cause.
- Only then start again.
Ostrakon does not correct on its own.