Skip to main content

Statutory registers, document management, accounting export and fiscal audit export (Büro: Dokumentationsverwaltung, DMS ORBIZ, DATEV, GDPdU und Kassen-Nachschau)

1. Purpose and scope​

This chapter covers four back-office areas of IXOS (all reached from the Office menu, Büro):

  1. Documentation management (Dokumentationsverwaltung): the legally required registers and quality records of a German pharmacy:

    • controlled-drug register (BtM)
    • blood and haemophilia product register (TFG-Produkte)
    • thalidomide-class prescription register (T-Rezepte)
    • incoming-QC test protocols for starting materials used in compounding (Ausgangsprodukte / Ausgangsstoffe)
    • random-sample quality checks of finished medicines and medical devices (FAM & MP)

    Entries come from POS sales, goods receipts and supplier returns, or are typed in by hand. Each area then has its own rules for completing, checking, signing off, printing, archiving and deleting entries, and for removing personal data after the retention period.

  2. Document management system (DMS, product name ORBIZ): an audit-proof archive for documents IXOS prints, paper it scans and e-documents it receives (PDF, e-invoices, email). It covers:

    • document types that drive classification, folder placement, retention, tax relevance and signature need
    • keywording (metadata) and full-text search
    • versions and history
    • per-folder access rights
    • per-document encryption, with keys destroyed when retention ends
    • qualified e-signature with the pharmacist's health professional card (HBA)
    • signed, verifiable exports
  3. Accounting export (DATEV): builds batches of postings from till closings, invoicing, goods receipts, inter-branch clearing and DMS receipts. Accounts follow the SKR03 or SKR04 standard chart, with user overrides. Batches are exported as encrypted or plain files or pushed directly to the accountant's data centre. A re-import file of matched bank payments auto-settles open invoices and customer credits.

  4. Tax audit and till inspection (GDPdU und Kassen-Nachschau):

    • regulator exports: a full GDPdU/GoBD audit export and a till-inspection export in GDPdU or DSFinV-K format
    • a printable protocol of system settings and their change history
    • the procedure documentation
    • management of the fiscal security device (TSE): commissioning, decommissioning, PIN/PUK, swap, failure log, weekly TAR backup and export, and reporting recording systems to the tax office

Most of these are paid add-ons. They are listed in section 8.

2. Key concepts and terms​

German termEnglishMeaning
DokumentationsverwaltungDocumentation managementModule that holds all statutory registers and test protocols
BtM (Betäubungsmittel)Controlled drug / narcoticSubstance under the German narcotics law; every receipt and outflow must be recorded
BtMVVNarcotics prescription ordinance§13/§14 set the record-keeping duty and the monthly check
KarteikarteRegister cardOne controlled-drug record (one product, or one active substance across several products) with a running balance
wirkstoffbasierte DokumentationSubstance-based documentationSeveral articles (pack sizes, imports, suppliers) share one card
Warenbewegung / Ab-/ZugangStock movement / issue-receiptOne line on a register card
BerichtReportThe open set of movements on a card since the last monthly printout. It is closed by the monthly printout
MonatsausdruckMonthly printoutLegally valid, signed printout that closes reports. It can be filed in the DMS and signed electronically
InventurlisteStocktaking listList of controlled drugs in stock, used to check the safe
VernichtungsprotokollDestruction protocolPrintout for a destruction or loss, signed by two witnesses and the manager
ÜbertragCarry-overOpening-balance movement, also used when cards are merged or split
ÜberfüllungOverfillExcess substance weight in a liquid preparation
Prüfkennzeichen / geprüftChecked flagPer-movement release flag, needed before the monthly printout
KorrektureintragCorrection entryKept original of a changed entry, shown when "incl. corrections" is on
AusschlusslisteExclusion listControlled drugs excluded from automatic documentation
TFG-Produkte (Blut- und Hämophilieprodukte)Blood and haemophilia productsProducts under the Transfusion Act. Batch-level records kept 30 years
T-Rezept / T-ArzneimittelT-prescription / T-drugSpecial prescription for thalidomide, lenalidomide and pomalidomide (teratogenic). The drugs are listed in the BfArM T-register
Ausgangsstoff / AusgangsproduktStarting materialRaw material (herbal drug, chemical) or packaging used in compounding
PrüfprotokollTest protocolRecord of a QC test with an overall release decision
PrüfkandidatTest candidateBooked goods-receipt line for a drug/chemical that has not been tested yet
MonografieMonographTemplate with product data and identity tests for a starting material
IdentitätsprüfungIdentity testSingle test (target property, method, source) inside a protocol
ZertifikatskontrolleCertificate checkCheck of the manufacturer's certificate of analysis
ZL-PrüfzeichenZL test markMark showing that the central pharmacists' laboratory spot-checked the certificate data
Freigabe / keine FreigabeRelease / no releaseOverall assessment that closes a test protocol
FAM (Fertigarzneimittel) / MP (Medizinprodukt)Finished medicinal product / medical deviceProducts subject to random-sample quality checks
StichprobeRandom sampleDaily QC sample
AMK / BfArMDrug commission of German pharmacists / federal drug instituteBodies to notify about quality defects
Löschfristen für Bezug zu personenbezogenen DatenDeletion periods for personal-data referencesSetting that controls when patient and prescriber data are irreversibly removed from registers
DMS / ORBIZDocument management systemThe integrated archive
DokumentenartDocument typeClassification that sets folder, grouping, contact role, retention, tax relevance, DATEV document type, signature need and allowed email senders
Verschlagwortung / SchlagwortKeywording / keywordDocument metadata, e.g. type, client, contact, document date, document number, value, tax-office flag
MandantClient (tenant)One pharmacy within a branch or partner group. Also the DATEV client number
Posteingang / EingangsordnerInboxUnclassified documents, the only ones that can be hard-deleted
StempelStampDated visual marker on a document, e.g. "Paid"
SuchordnerSearch folderFixed virtual folder, e.g. new, active, tax office, to-sign
Relevant für das FinanzamtTax-office relevantFlag for documents that go to the accountant or the auditor
HBA (Heilberufsausweis)Health professional cardSmart card used for qualified electronic signatures (QES)
E-Rechnung (ZUGFeRD, XRechnung)E-invoiceStructured XML invoice (EN 16931)
DATEVDATEVGerman accountants' cooperative and data centre. Its formats are the de-facto standard
SKR 03 / SKR 04Standard chart of accounts 03/04DATEV standard charts. 03 is organised by business process, 04 by financial-statement structure
Mandantennummer / BeraternummerClient number / adviser numberDATEV identifiers (max 5 and max 7 digits)
Sachkonto / PersonenkontoGeneral-ledger account / personal (debtor or creditor) accountAccount categories with configurable digit lengths
Debitor / KreditorDebtor (customer) / creditor (supplier)Personal accounts
SammelkontoCollective accountOne account shared by many customers or suppliers
Exportstapel / StapelExport batchBundle of posting records over one period
BuchungssatzPosting recordDate, debit/credit, account, contra account, amount, document number, text
S/H (Soll/Haben)Debit/creditPosting side
FestschreibekennzeichenLock flagColumn in the DATEV CSV. When set, the record cannot be edited in the accounting software
Postversandformat (KNE/SELF)Legacy DATEV mail-delivery formatOlder fixed-format interface (files ED00001, EV01)
Z-Bon / S-BonZ report / summary reportTill closing per register (Z) or summed over all registers (S)
KassenverrechnungskontoTill clearing account1369 (SKR03) / 1469 (SKR04), used for till postings that the Z report covers
GeldtransitMoney in transit account1360. Manual till cash-outs are posted here
KreditCustomer credit (tab)Amount a customer owes, settled only in full
FakturaInvoicing moduleCustomer invoices, delivery notes, dunning
DATEV-DatenserviceDATEV data serviceDirect online transfer of postings and document images
SmartLoginDATEV loginQR-code-based login used for the data service
GDPdU / GoBDPrinciples of data access and auditability / proper digital bookkeepingGerman tax-audit data rules
Z3-ZugriffZ3 accessAuditor receives the data on a data medium
Kassen-NachschauTill inspectionUnannounced check of cash recording (AO §146b)
DSFinV-KDigital interface of tax administration for till systemsMandatory till export taxonomy since 2020
KassenSichVTill security ordinanceRequires the TSE
TSETechnical security deviceBSI-certified signing module with a journal (USB on the server)
TAR-ExportTSE TAR exportRaw signed TSE journal archive
Systemeinstellungs- und ÄnderungsprotokollSystem settings and change protocolAudit printout of master data, rights, configuration parameters and updates, each with change history
VerfahrensdokumentationProcedure documentationGoBD description of how the system creates and stores business data
AufzeichnungssystemRecording systemTill or secondary workstation that must be reported to the tax office (AO §146a)
ELSTERTax authority online portalReceives the recording-system report (XML upload)
Leiter / UmsatzverantwortlicherManager / turnover-responsible personRoles needed for DATEV and for GDPdU/till inspection
ArbeitsplatzschutzWorkstation protectionIXOS permission concept, applied per workstation and per user
Notes / AufgabeIXOS internal tasksUsed for TSE failures, e-invoice validation failures and reminders

3. Data model​

3.1 Controlled-drug register​

RegisterCard (Karteikarte)

  • id; name (editable for substance-based cards); active substance, strength, finished-product type and unit (may be empty for self-created articles)
  • documentation unit: standard or an alternative unit
  • state: Active / In progress (has unclosed report) / Archived
  • predecessorCardId / successorCardId (created by merge or split)
  • assignedArticles 1..n: PZN, name, supplier, dosage form (DAR), pack size and unit. At least one is required.
  • current stock: summed over all assigned articles, in pieces, weight or volume, up to 9 digits
  • Article identity for standard database articles: PZN + pack size + unit + quantity. Self-created articles compare more properties.

Report (Bericht)

  • reportNo; from and to dates (first and last movement); position count
  • printedBy (user who made the monthly printout); printoutNo; closed flag
  • One open report per card. The monthly printout closes it, and the next movement opens a new report.

Movement (Warenbewegung)

  • runningNo (optional display), type, direction (receipt/issue), date, quantity (pieces, weight or volume), and resulting stock
  • type is one of: sale, goods receipt, return, destruction, carry-over, overfill, test, loss
  • article (for multi-article cards)
  • documentNo: controlled-drug prescription number, requisition form number, or delivery note / delivery receipt number. Mandatory for sales only.
  • customer or supplier name and address (free text or contact link)
  • doctor name and address: required for sales, hidden for sales to branch or partner pharmacies
  • remark: max 200 characters, printed only on the destruction protocol
  • origin text: carry-over only, default "Übertrag"
  • destruction reason and destruction method: destruction and loss only, both printed
  • checked flag
  • markers: corrected entry / correction entry (original)
  • source program (module), and a correction-booked-in-logistics marker
  • Partial quantities are shown for unit-dose splitting.

MovementChangeLog

  • timestamp, operator, program (module), action and action date
  • qty old / qty new / stock new (stock old optional)
  • detail: per-field current, old and new values

ExclusionEntry

  • article, plus two flags: exclude POS/invoicing movements; exclude goods-logistics movements

MonthlyPrintout

  • printoutNo, period, reports included
  • options: "incl. corrections", "DMS-filed", "signer for HBA signature"

3.2 Blood/haemophilia (TFG) and T-prescription registers​

RegisterEntry

  • movementType: receipt / dispensing / return
  • article: name, dosage form, unit, standard pack size (NP), PZN, supplier
  • packs total: not directly editable; it is taken over from the batch lines after the user confirms
  • delivery or return date (TFG receipts default to today)
  • dispensedTo type: patient / doctor / supplier / branch
  • recipient or supplier: name, first name (patient), street, postcode and town, date of birth (patient)
  • prescribing doctor: name and address. Mandatory to close a dispensing record, except a return to the supplier.
  • createdAt, lastChangedAt, editor
  • status: incomplete / complete-unprinted / printed
  • printed period reference

BatchLine

  • batch designation: up to 30 characters for TFG
  • packs, dispensing date
  • T-prescriptions only: shipping date of the prescription copy

ChangeLog

  • date, time, employee, field, old value, new value

PrintRun

  • period from–to, sort mode, "changed after print" warning flag

3.3 Starting-material test protocols​

Monograph

  • names and synonyms (first entry is the name)
  • hazard labels (EU symbols and GHS pictograms)
  • product types (e.g. substance), storage notes, general notes
  • primary test-specification source: abbreviation max 20 characters and name max 50 characters, split at a hyphen
  • flags: safety data sheet required, is a controlled drug, expiry check mandatory
  • identity tests; system-supplied vs user-created

IdentityTest

  • target property / test text, method (instrumental, wet-chemical, organoleptic, self-created), source, active flag

TestProtocol

  • testNo (sequential), testDate (creation date, not updated on later edits), internal batch, article, PZN, dosage form, supplier
  • purchase price, with basis: own / pharmacy / manual
  • supplier's batch (max 50 characters), quantity, expiry, weighing correction factor (3 decimals), delivery date, supplier name, editor
  • certificate check: analysis data conform, certificate date, ZL mark, remark, notes
  • identity test results: conforms yes/no and/or remark per test
  • closing remark
  • overall assessment: none / no release / release, with the assessment date
  • responsible pharmacist
  • state: candidate → open → closed
  • printed/DMS-filed flag and locked flag

3.4 FAM & MP test protocol​

  • testNo: sequential, never reused after deletion
  • testDate, article (with MP flag), batch, expiry (MM.YY)
  • sample origin: none / stock / goods receipt / return from doctor or patient
  • sample count, reason, destructive test (seal broken) yes/no, tester
  • result: proper quality / quality defects
  • notifications (defects only): competent authority; AMK (drugs) or BfArM (devices); supplier/manufacturer
  • remarks, printed flag (printed means locked)

3.5 DMS​

DocumentType

  • name (unique), abbreviation (mandatory), active flag, user-defined flag
  • grouping pattern, contact role, standard folder, group name
  • tax-office relevant (yes/no)
  • retention period: the legal minimum; may be extended or set to unlimited, never shortened (except types that ship as unlimited)
  • DATEV document type, HBA signature required
  • sender whitelist (email addresses)
  • stamps: name, colour, order

Keyword definition

  • built-in: document type, client, contact, document date, tax office (cannot be created)
  • custom: name, data type, column

Document

  • id/number, client (Mandant), document type, contact (with role), document date, document number, value (amount), tax-office flag
  • HBA signature state: not required / pending / done with date
  • custom keywords, note, stamps (type and date)
  • source: IXOS / manual / mailbox
  • link to the originating IXOS transaction
  • state: inbox → filed/active → archived (recently or long) ; deleted (soft) ; hard-deleted (inbox only)
  • expiry date = document date + retention period of the type
  • exported flag, exported-to-DATEV flag
  • attachments (e-invoice XML)
  • read-only properties: created date, creator, program, file name, path, exported, expiry
  • encryption: AES-256 with one key per document, keys held locally

DocumentVersion

  • Created by add, delete or rotate page, and by stamping (per the history text). Any version can be restored as the new current version.

HistoryEvent

  • timestamp, document, actor (editor or viewer), workstation
  • action: created / deleted / edited / new version / moved / read / exported / archived / reactivated / printed / permissions changed / deactivated / sent by email / validated
  • change before/after, email address, DATEV-export note

Folder

  • tree path: client / standard folder / initial letter / contact / group / year / month
  • protected flag, per-employee rights (read < process < change), inheritance

SavedFilter

  • name, criteria, default flag

3.6 DATEV​

Settings

  • client number (max 5 digits), adviser number (max 7 digits), chart (SKR03/SKR04)
  • closing basis: Z/S, default Z
  • G/L account length; personal account length = G/L length + 1
  • extend account numbers: default on
  • ignore postings: older than previous fiscal year (default) / none
  • fiscal year end (MMDD), date from which unreferenced DMS documents are exported
  • export directory: documents drive or pharmacy drive
  • debtor numbering: manual / automatic for invoicing customers, using either alphabetic collective accounts or consecutive individual accounts, plus a start value and spacing

AccountMapping

  • per standard account in six areas: till revenues, invoicing revenues, goods receipts, debtor/creditor collective accounts, cash-in/out, external payment receipts
  • each row: standard number and name, own number, own name, type (cash-in/cash-out), tax key 1–9, "offer at till" flag
  • self-defined accounts can be added. They can be deleted only while they have no postings.

ExportBatch

  • batchNo (sequential), from (oldest document) and to (newest document), exportedAt, status (exported marker)
  • counts: till, invoicing, goods receipt, internal clearing, unreferenced DMS documents
  • posting records:
    • document indicator: linked / expected but missing / none
    • transmitted-to-DATEV flag
    • date, S/H, account, contra account, amount, document number
    • text with a type code: K till, F invoicing, WE goods receipt, E/A cash in/out, IW internal goods movement, IV internal clearing
    • cancellations shown in red
  • protocol entries: workstation and result message

ImportBatch

  • batchNo, from/to, name, booked-on date, payment count
  • posting lines plus a match status (see 6.4)

MasterDataExport

  • scope: debtors and creditors, account names; format; password

3.7 Fiscal / TSE​

TSE

  • serial number, certificate ID, drive letter
  • start of operation, end of operation
  • overall state, validity, memory state, remaining transactions
  • assigned workstations (with assignment date)
  • PINs (Admin 5 digits, TimeAdmin 5 digits) and PUK (6 digits)

TSEProtocolEntry

  • timestamp, type (ready / error / manual entry), operator (manual entries only), text

Workstation

  • id following the scheme APL000/001/002–003/011–029/030–049/050–099/100+/KASxxx
  • serial number, start of operation, TSE assignment

AuditExport

  • kind: GDPdU / till inspection in GDPdU format / till inspection DSFinV-K / TSE TAR
  • period, password, extras (annual stocktaking, permanent inventory, cash-book postings), output folder

SettingsChangeLog

  • entries for master data, rights, configuration parameters and software updates, each with date, user and old/new values

4. Features​

4.1 Documentation management shell (Dokumentationsverwaltung) [GENERIC]​

  • Purpose: one place for all statutory registers and quality protocols.
  • Navigation: areas BtM, TFG products, T-prescriptions, starting materials and FAM & MP. The module opens on the controlled-drug area.
  • Search: a search field takes initial letters, a PZN or #batch (batch search in TFG and T-prescriptions). Active filter criteria are shown. Hits are sorted alphabetically by article into tabs.
  • Key rule: register stock is NOT linked to the stock in article management. Returns, write-offs and manual stock corrections can make them drift apart. The user reconciles by adding manual register entries.
  • Shared automation pattern across the registers: a configuration switch turns on automatic entries from POS dispensing, goods receipt and supplier returns. A second switch makes the sale prompt for the customer and the prescriber when a regulated product is sold. When a sale changes later (pickup, partial pickup, edit in sales administration), the register entry follows automatically.
  • Returns caveat: when a supplier-return line is changed later (quantity, line or order deleted, status change, supplier change), the register is NOT updated. A warning appears on save, and the user must fix and reprint by hand. For controlled drugs there is one extra rule: if the monthly printout is not yet made, the movement's "checked" flag is reset.
  • Contact fields: the contact fields in every register accept free text, so the person does not have to exist in contacts. Typing initial letters and then opening the contact picker pre-filters the picker. Without pre-typed letters the picker opens empty.
  • Personal-data deletion: after the legal minimum retention, the configuration parameter "deletion periods for personal-data references" irreversibly removes patient and prescriber references from movements and change logs. It applies to BtM, TFG and T-prescriptions. All pharmacies in a group should use the same value.

4.2 Controlled-drug register (BtM-Dokumentation) [DE-SPECIFIC]​

General idea: a perpetual, per-product controlled-substance ledger with running balance, per-line release, a period close that locks it, a destruction workflow and a full audit trail.

  • Purpose and legal basis:
    • Every receipt (delivery) and every outflow (dispensing on prescription, destruction, return) must be traceable without gaps.
    • The last documented balance must always equal the physical content of the controlled-drug safe.
    • The record must be printable at any time and at least at the end of each month. At each month end it must be checked and, if stock changed, confirmed with initials and the check date.
    • Paid add-on. Subject to workstation protection.
  • Cards:
    • One card per controlled drug. "New BtM" (F3) opens the article search. Its extended search (active-substance search) is also used for exempted preparations: codeine or dihydrocodeine preparations for addicted persons that fall under controlled-drug rules.
    • Substance-based cards group different pack sizes, parallel imports or compounding substances from different suppliers. Total stock is computed from the movements of all assigned articles.
    • The overview omits supplier, PZN and unit for multi-article cards. An expandable detail area lists the assigned articles. Icons show "multiple articles" and "alternative unit possible / selected".
  • Overview tabs:
    • Active: non-archived cards, alphabetical.
    • In progress: cards with unclosed documentation.
    • Archive: archived cards and predecessor cards created by merge or split.
    • Columns: to-do icon (its tooltip lists missing fields or a wrong order), card name, supplier, dosage form, PZN, pack size, stock.
    • The display refreshes promptly when the POS or goods logistics book controlled-drug movements.
  • Automatic documentation:
    • Covers: dispensing at POS, substitution therapy dispensing, unit-dose splitting and weekly blisters, resolution of a pickup slip, goods receipt, return.
    • Parameters: "document BtM automatically", "document compounding ingredients", "document substitution therapy".
    • Exclusion list (4.2.6) per article and per source (POS/invoicing vs goods logistics).
    • Compounding and parenteral compounding are ALWAYS entered manually, because preparation and billing happen at different times.
    • BtM components are also picked up from the external Dr. Lennartz lab program.
  • Prompts in feeding modules:
    • "Ask customer and doctor at BtM sale": prompts for customer, prescriber and the controlled-drug prescription number when missing. The data is mandatory for the register, but it can be added later as free text or via a walk-in customer contact.
    • "Ask delivery-receipt number at BtM goods receipt" (workstation scope): an optional discrepancy prompt in goods receipt. It appears only when the module is licensed and auto-documentation is on.
    • "Ask delivery-receipt number at BtM return" (workstation scope): optional. The number is passed to the register.
  • Release: every movement, automatic or manual, must be checked and explicitly set to "checked" by a user.

4.2.1 Reports window (BtM-Berichte)​

  • Header: article name, dosage form, pack size, PZN, stock in packs. A selector switches between drugs.
  • Reports tab: from, to, report number, number of positions, printed by, printout number, closed icon.
  • Detail grid: the movements of the selected report. Optional columns: running number, article, supplier, PZN (needed for substance-based cards). Option: include correction entries.

4.2.2 Receipts/issues window (BtM-Ab-/Zugänge) — record, correct, release​

  • Creating entries:
    • New sale (F10), New goods receipt (F11), or New issue/receipt (F12, which asks for the type).
    • Types: sale, goods receipt, return, destruction, carry-over (first transfer of existing paper records into the system), overfill (excess weight in liquid preparations, BtMVV §14), test (quantity used for starting-material testing; per the regional chamber, no destruction protocol or witness is needed), loss (lost during filling or compounding).
    • Multi-article cards first ask which article.
    • A new movement stays unsaved until Save. Cancelling asks whether to save; "No" discards it.
  • Fields: see the data model. Mandatory fields are marked. The doctor fields are hidden for sales to branch or partner pharmacies.
  • Refresh indicator: shows whether other modules booked movements for this drug while the user was editing. Refreshing with unsaved edits asks first. Yes and No both refresh; only Cancel does not.
  • Leaving the window with problems: if movements produce negative stock or a quantity of 0, a warning offers:
    • "clean up now": re-sort chronologically
    • "leave anyway": keep the negative stock or zero quantity for now
  • Ordering:
    • Movements may be entered in any order. The list is auto-sorted by date, newest first.
    • Within one day the user must put movements in the right sequence (Move up F6 / Move down F7, available only with "incl. corrections" ticked).
    • A movement can be marked checked only when the order is consistent.
  • Checking:
    • Clicking "Checked" (or Ctrl+F5) validates the movement and lists any missing mandatory fields.
    • The check mark can be removed at any time until the monthly printout.
    • The system changes checked movements only when resolving a pickup slip changes a quantity.
  • Correction:
    • Allowed only while the movement is unchecked (untick first) and before the monthly printout.
    • If the edit changes stock, the check marks on neighbouring movements are removed so they are re-checked.
  • Deletion: F4 with confirmation. Deleting an already checked movement is logged.
  • Cancellations from other modules: sale cancellations in sales administration, and goods-receipt corrections (correction booking in the goods-logistics archive), are applied automatically when auto-documentation is on:
    • Before the monthly printout, the original movement is simply deleted.
    • After the monthly printout, an opposite movement is added: an issue for a cancelled receipt, a receipt for a cancelled sale. The original is not modified.
  • Destruction protocol: for a checked destruction or loss movement, "print destruction" (F9) produces a protocol for two witnesses and the pharmacy manager to sign. It includes the reason, the method and the remark.
  • Running number: an optional column (list settings) numbers every movement of an article, which makes changes easier to trace.

4.2.3 Change history (Änderungshistorie, Ctrl+F10)​

  • Available from the overview, the reports window and the receipts/issues window.
  • Filters: date range; "stock changes only".
  • Columns: quantity old/new, stock new (stock old and a running number can be added), change timestamp, action, action date, originating program, operator.
  • Detail: each changed property with current, old and new value.
  • Purpose: proves that the documented data and stock agree.

4.2.4 Printing (Druckauswahl BtM)​

  • Stocktaking list:
    • Only articles with stock.
    • Substance-based cards show card name, dosage form and total stock, then the assigned articles (name, supplier, PZN, unit).
  • Monthly printout draft:
    • Any time; does not lock anything.
    • Contains everything changed since the last monthly printout. Unfinished or unchecked entries carry an icon.
    • Shows the pending report number; the header printout number stays empty.
    • Marked DRAFT and not valid as legal proof.
  • Monthly printout:
    • Period: defaults from the last monthly printout to the end of the following month (capped at today). It can be changed, but the law expects one at each month end.
    • Preconditions: all mandatory fields filled; no negative stock at any point, not only at month end; every movement checked.
    • If unchecked movements exist, the user can only print a draft. If all are checked, the user chooses "print and close reports" or a draft.
    • Printing closes the included reports permanently.
    • The header carries the printout number, and each drug shows its last printed report number. Substance-based cards show unit, PZN and supplier per movement line.
    • The user signs and enters the check date at the bottom.
    • With a DMS licence it is filed in the DMS by default and signed there with QES/HBA. A field "employee for later HBA signature" names the signer. Paper printing comes back if the DMS document type "BtM monthly printout" is deactivated.
    • Option: include correction entries.
    • Layout parameter: all drugs continuous (default) or each drug on its own page.
  • Reprint: from the print archive. Pick a past monthly printout, optionally with corrections.
  • Print preview is the default and allows saving as PDF.

4.2.5 Archive​

  • Preconditions: all monthly reports printed (the card is no longer "In progress") and the remaining stock of the latest report is 0.
  • Archive one card: F4 with the card selected.
  • Mass archiving: "all cards whose last entry is older than N years", N = 1–5. The system reports how many cards qualified.
  • Archive tab: card name, multi-article icon, supplier, dosage form, PZN, pack size, date of last movement. Read-only view of reports.
  • Search lists every card on which an article was ever documented.
  • A new movement for an archived card's article reactivates the card automatically.

4.2.6 Exclusion list (Ausschlussliste)​

  • Articles to keep out of automatic documentation. Each article has two checkboxes: from POS/invoicing, and from goods logistics.
  • Insert from article search, or delete.

4.2.7 Extended search (Ctrl+F2)​

  • Top filters: card names (multi-select; archived cards shown greyed), period, customer, doctor, document number, supplier.
  • More filters: movement type (all eight types), checked/unchecked, running-number range, include corrections.
  • Results: card view (cards, then their movements; stock as it was at movement time; green icon = checked) and transaction view (chronological across cards).
  • Printing results: each row has a tickbox to include or exclude it. The print omits carry-overs and report numbers.

4.2.8 Card editing: merge, split, unit (Ctrl+F5)​

  • Rename: only the card name is editable.
  • Merge:
    • Candidates share active substance, strength and dosage form. For compounding substances, different dosage forms (e.g. substance and powder) are allowed when the pack-size unit is identical.
    • When substance or strength data is missing, the user decides. Legal admissibility is the user's responsibility (ask the state authority if unsure).
    • If any card has printed reports and stock at the last printout: predecessor and successor cards are created. The computed stock per article is shown and confirmed ("Checked & take over"). Stock moves to the successor as a carry-over. A closing report of the predecessor is printed automatically, and the predecessor is archived. Unprinted movements go to the successor.
    • If there are only unprinted movements: the cards are simply combined under the source card's name.
  • Split out an article:
    • Same printed-report and stock check. The old card is archived, the stock is carried over and a predecessor report is printed automatically.
    • With unprinted data only, the article gets a new card with its movements.
    • The last remaining article cannot be split out.
  • Choose unit: when an alternative unit exists besides the supplier's unit, the user can switch to it, but only while the current report holds only unchecked movements. Otherwise the user must print first.

4.3 Blood and haemophilia product register (TFG-Produkte) [DE-SPECIFIC]​

General idea: batch-level traceability register for biologicals, from supplier to patient and prescriber, with 30-year retention and recall lookup by batch.

  • Purpose: record acquisition and dispensing per ApBetrO §17. Keep at least 30 years. Paid add-on.
  • Tabs:
    • All
    • Current: not printed yet, or changed after printing
    • Goods receipt, Dispensing, Return
  • Columns: status icon (incomplete / closed and printed / none = complete but unprinted), date (dispensing or delivery date; creation date if none given), movement-type icon (in All/Current), article, quantity, batch, recipient and/or supplier. Sorted by date.
  • Search: article name, initial letters, PZN, or #batch. Batch search traces a recalled batch to the patient and the supplier so both can be notified.
  • Automatic creation (parameter "TFG products and T-prescriptions – automatic documentation", default OFF):
    • The entry window opens during the sale, goods receipt or return with known data pre-filled. The user adds batch(es) and confirms with Take over (F12).
    • Incomplete entries may be saved.
    • "Ask customer and doctor at sale" (default ON) prompts for both.
    • Optional: at goods receipt, a discrepancy prompt asks for batch numbers.
  • Manual creation:
    • Only from the Goods receipt / Dispensing / Return tabs (not from All or Current).
    • New (F3) opens an article search restricted to blood and haemophilia products, then the entry window.
    • For dispensing and return, batches are picked from the list of batches already documented for that article. New batch (F3) adds a line.
    • The system asks whether to take the batch-line pack total as the record's pack count. Only "Yes" fills the non-editable pack field, and only then can the record be saved. For manual records it also asks whether to raise the total by each newly added batch quantity.
    • Save lists every field still missing for completion.
    • From POS/invoicing, Take over or Esc returns to the sale.
  • Doctor printout: from a dispensing record, F9 prints the notice the pharmacy must send to the prescriber.
  • Change: Details (F8). Changing a printed record, or completing an incomplete one inside an already printed period, raises a warning to reprint that period from the print archive. There are separate warnings for the documentation print and the doctor print.
  • Delete batch line: F4. Deleting the last batch asks whether to delete the whole record.
  • Change log (Alt+F11 in the detail window): date, time, employee, field, old value, new value. The header shows the last change date and user.
  • Record deletion:
    • F4 with confirmation.
    • Records older than 30 years may be removed.
    • Younger records may also be deleted (e.g. entered wrongly), but the deletion is logged internally and the responsibility is the user's.

4.4 T-prescription register (T-Rezepte) [DE-SPECIFIC]​

General idea: special register for high-risk teratogenic drugs, with batch-level receipt and dispensing records and a dispatch date for the prescription copy sent to the regulator.

  • Purpose: thalidomide, lenalidomide and pomalidomide need a T-prescription. Movements (purchase, dispensing) of drugs in the BfArM T-register must be documented (ApBetrO §17). Paid add-on.

  • Automation and returns caveat: the same as TFG.

  • Change log: every change is logged and viewable.

  • Search: article or #batch, for recall tracing.

  • Overview columns: status icon, movement date, type icon, article, dosage form, unit, PZN, quantity, recipient/supplier.

  • Default sort: date descending; within a date by article A–Z; then by type (dispensing, return, receipt).

  • Column-click sorting:

    Clicked columnSort order
    Status iconincomplete, then printed, then none; then date descending; then article
    Type icondispensing, return, receipt; then date descending; then article
    ArticleA–Z; then date descending; then type
    PZNascending; then date descending; then type
    Quantitynumeric ascending; then date descending; then article
    Recipient/supplierA–Z; then date descending; then article
    Dosage formnot sortable (all show HKP)
    Unitnot sortable
  • Entry window:

    • Header: edit status, creation date, movement type, article.
    • Fields: delivery or return date; packs; last edit and editor; supplier / recipient (customer, or supplier returned to) / doctor (for dispensing).
    • Batch table: batch, quantity, shipping date of the prescription copy (dispensing only). Add and delete rows.
  • Manual creation:

    • New (F3) asks for the movement type, then opens an article search limited to T-drugs.
    • On creation the pack total is computed from the batch rows.
    • Deleting a batch row is undoable with Esc and becomes final on OK. Adding batches later shows a notice.
    • Incomplete data produces a list of missing fields but can still be saved.
  • Edit: F5. Editing a printed record resets its printed status, so it is included again in the next default print.

  • Delete: F4 with confirmation.

4.5 Starting-material test protocols (Prüfprotokolle Ausgangsprodukte) [DE-SPECIFIC]​

General idea: incoming QC of compounding raw materials and packaging. A test record built from a monograph template, with identity tests, a certificate check and an overall release or reject decision, plus container labels.

  • Legal basis: ApBetrO §6(3) and §11(2). Packaging tests are documented by analogy, following the chamber's guideline on primary packaging. Paid add-on.
  • Tabs:
    • Test candidates: booked goods-receipt lines flagged drug/chemical that are not yet tested. Controlled by the parameter "propose test candidates" (system scope; default on).
    • Open protocols: no overall assessment yet.
    • Closed protocols: assessment set.
  • Columns: test number, test date (creation date), article, PZN, monograph name/synonyms, editor.
  • Functions:
    • Search (F2)
    • Check candidate (F12)
    • New without candidate (F3, via article search)
    • Continue test (F12, open protocols)
    • Details (F8, closed protocols; editable)
    • Copy (F7, closed protocol → new editable copy)
    • Delete (F4; asks for confirmation if not printed)
    • Delete all candidates (Ctrl+F4)
  • Monograph selection:
    • Shows the article. Esc returns to the article search. Filter by product type.
    • The search uses the article's short name, shortened step by step (minimum 4 characters) until at least one monograph matches.
    • Take over (F12) copies the monograph's product data and tests into the protocol.
  • Protocol pages: header data, product data (read-only from the monograph), certificate check, identity test, closing. Save each page with F1. Mandatory fields are marked but validated only at release.
  • Identity test page:
    • Grid of target property/test (shown truncated to 4 lines), a conforms icon and a remark.
    • In the detail area the user sets "conforms" yes/no and/or a remark. At least one of the two is needed to count as a result.
    • "Select tests" (F5) ticks which tests apply to this protocol. Each test shows its method and source.
    • Tests with no result are hidden at closing and are left off the printout.
  • Certificate check page: analysis data conform, certificate date, ZL mark, remark, notes. Target analysis values are shown but not printed.
  • Closing page:
    • Closing remark. Avoid line breaks: the print form has a fixed number of lines and truncates.
    • Overall assessment: none / no release / release; date (default today); responsible pharmacist (free text).
    • Release or no-release moves the protocol to Closed after validation. If validation fails, a message appears and focus jumps to the first faulty field.
    • Resetting the assessment to none moves it back to Open.
  • Monographs:
    • Supplied by the vendor and kept current; users can create their own.
    • In supplied monographs a user can only add tests and activate or deactivate tests (e.g. tests the lab cannot perform; deactivated tests no longer appear).
    • In own monographs a user can edit everything: add (F6), edit (F5), delete tests; delete the monograph (F4).
    • Source fields are split at "-" into an abbreviation (≤20 characters) and a name (≤50 characters). Spaces are trimmed and excess text is cut.
    • Hazard labelling lists:
      • EU symbols: Xn harmful, Xi irritant, T+ very toxic, T toxic, O oxidising, N dangerous for environment, F+ extremely flammable, F highly flammable, E explosive, C corrosive
      • GHS01–GHS09: exploding bomb, flame, flame over circle, gas cylinder, corrosion, skull and crossbones, exclamation mark, health hazard, environment
  • Printing: the print-selection window opens automatically after a release, or after editing a released protocol. Any number of copies.
    • Test protocol: closed protocols only. With a DMS licence it is filed in the DMS (folder "Documentation" and search folder "for HBA signature") instead of printed. Switch back to paper by deactivating the document type "starting-product test protocol".
    • Draft protocol: open protocols, e.g. to take to a lab without a workstation.
    • Labels for storage containers: given quantity.
  • Lock: a closed protocol that has been printed or DMS-filed is marked and locked for editing, unless the parameter "lock printed test protocols" is switched off.
  • Legal rule: only the signed printout counts. A protocol changed later must be reprinted, re-signed, and the old printout destroyed. Alternative: DMS filing with QES, with the supervisory authority's prior consent.

4.6 FAM & MP random-sample test protocols [DE-SPECIFIC]​

General idea: daily spot checks of finished stock, with defect escalation tracking and quota counters.

  • Purpose and legal basis: ApBetrO §12. The chamber guideline expects one check per day, or six per week. Protocols are kept at least 5 years and must carry initials, so they are printed. Paid add-on.
  • Overview:
    • Columns: result icon (proper quality / defects), test number (never reused), test date, article, medical-device tick, dosage form, unit, PZN, supplier, printed icon.
    • Counters under the table: tests in the current and previous calendar week and in the current and previous month. They are computed independently of any filter, so they show quota fulfilment.
  • New protocol:
    • New (F3) opens an article search by name or PZN.
    • Fields: batch, expiry (MM.YY), sample origin, sample count, reason, destructive test, test date, tester, result, remarks.
    • "Proper quality" completes the protocol. "Quality defects" enables tickboxes for: competent authority notified; AMK (drugs) or BfArM (devices) notified via report form; supplier or manufacturer notified.
    • The info button opens the test-criteria checklist (guideline-based, with a hyperlinked table of contents, e.g. folding box). The checklist is printable.
  • Edit: Details (F8), only while unprinted.
  • Print:
    • A collected list over a period (week or month). Available whenever unprinted protocols exist, regardless of the current filter.
    • A warning appears; "Print and close" locks the protocols.
    • The pharmacist signs each line in the "responsible pharmacist" column. Fine print explains what "proper quality" means.
    • Print forms can be copied and customised ("expert copies").
  • Extended search: article, batch, category (drug/device/any), relative period (N days/weeks/months/years back) or absolute from–to. Default: two months, today included.

4.7 Digital customer signature (Digitale Kundenunterschrift) [GENERIC]​

General idea: a QR-code hand-off to a phone or tablet for e-signing consents and other forms, filed automatically.

  • Trigger: "Digital signature" (F8) inside a process that needs a customer signature (e.g. consent to data storage).
  • QR code: IXOS shows a QR code with the document type and customer name. The customer display shows the same with an instruction. Either the customer scans it from the customer display with their own phone, or staff scan it from the IXOS screen with the pharmacy's tablet.
  • Signing: a web page shows the document with Next/Back paging. The customer signs with a finger or stylus and presses Save.
  • Filing: the signed document is stored automatically in the DMS, or without a DMS in the documents directory under "Kundenunterschriften".
  • Progress view in IXOS: three steps (QR scanned, signed, filed). Green ticks mean success. Red means the customer aborted on the web page; press OK and restart.
  • Copy to the customer: after signing the customer can email the document to themselves or download it (download only when scanned from the customer display). When scanned from the IXOS screen, staff can email it using a prewritten email text.
  • Retrieval: a DMS or PDF icon on the transaction opens the signed document.

4.8 Document management system (DMS / ORBIZ) [GENERIC]​

General idea: an integrated, audit-proof archive tied to business transactions and contacts.

4.8.1 Main window​

  • Folder tree:

    • Folders with documents show the count of active documents.
    • Sort order: numeric folders descending, letter folders ascending.
    • Create, rename and delete folders; expand or collapse one or all levels; drag documents between folders, but only when their keywords fit the target.
    • Context menu: export the folder's documents (with or without subfolders); activate, manage or view permissions.
  • Search bar:

    • Full-text search over names, numbers and document content. * is a wildcard.
    • Scope: all folders / current folder / including subfolders.
    • In a group: own client only, or all folders across clients.
    • A bin icon resets the search.
  • Hit list: newest first. Shows date, contact, other metadata, and icons for note, stamp and e-invoice.

  • Details area (can be hidden):

    • Keywording tab: document type, client, contact, document date, HBA signature, tax-office checkbox, plus type-specific and custom keywords.
    • Note tab.
    • Properties tab (read-only): created, creator, program, file name, path, exported, expiry.
  • PDF view:

    • Add pages by scan or import; set stamps; rotate pages left or right; move pages; delete a page (not the last one); zoom; page navigation; thumbnails; attachments.
    • Show version; restore a displayed version as the new current version.
    • The e-invoice XML appears as an attachment.
    • Context-menu actions copy recognised text into keywords: as contact, as document date, as document number, as value. Copy line to clipboard. Show/hide all stamps for printing. E-invoice reading view (ZUGFeRD).
  • Function keys:

    KeyFunction
    F1Save
    F2Search
    F3New (scan)
    F4Delete
    F5Email selected documents
    F6Filter
    F7Jump to originating transaction
    F8Details on/off
    F9Print
    F10Document history
    F11Select all
    F12Archive
    Ctrl+F3Import file
    Ctrl+F4Reactivate deleted document
    Ctrl+F6Contact details
    Ctrl+F8Hide/show tree
    Ctrl+F9Export
    Ctrl+F10Global history
    Ctrl+F12Reset archiving
  • Licence and setup: the module is booked in the company master under add-on modules, and is also included in the "IXOS for DATEV" licence. On first start a notice lists the defaults it switched on:

    • scanning of documents after goods receipt or return booking, and at POS on cash-in and cash-out
    • summary receipt (Summenbon) printed additionally into the DMS
    • automatic DMS filing of: return slips and return advices, A4 delivery notes, invoices, dunning letters, credit slips

4.8.2 Capture​

  • Scan: New (F3) opens the scan dialog: choose document type, add keywords (F6), OK.
  • File import: Ctrl+F3 or drag-and-drop. Accepts PDF, ZUGFeRD PDF and XRechnung XML, several files at once. Choose "determine document type automatically" or a fixed type for all files.
  • Email import: see 4.8.6.
  • Duplicate check: per client. An already-imported document is not filed again, and a notice appears.
  • Scans from other modules: scans made in goods logistics, sales administration, invoicing or the cash book carry the IXOS metadata and land in the right folder automatically.
  • Recommendation: create the contact before scanning or importing, to improve recognition.

4.8.3 Classification and filing​

  • Auto-filing: a document is filed into the folder tree automatically once all its mandatory keywords are set.
  • Path pattern: standard folder / initial letter of contact / contact / document type (group) / year / month. Example: Goods logistics / M / Meier / delivery note / 2020 / 09.
  • Re-filing: changing the contact or the type re-files the document automatically, even inside protected folders.
  • Contact lookup from document text: when a contact is taken over from the text, a smart search opens a picker with similar contacts. The user can also create a new contact there.

4.8.4 Document types (DMS administration) [GENERIC]​

  • The vendor ships a standard set. Users can edit types, add new ones (unique name), deactivate or activate them, and reset predefined types to the delivery state. Only user-created types can be deleted.
  • Edited or new types show "(user-defined)".
  • Per-type settings:
    • grouping pattern
    • default contact role (e.g. a consent belongs to a customer or an address-book entry)
    • standard folder; typing a new name creates a custom folder
    • preset standard folders: Customer, Goods logistics, Employee, Till, Payers, Documentation
    • tax-office relevant yes/no
    • retention period: preset to the legal minimum; can be extended or set to unlimited but never shortened. Consent declaration, employment contract and appliance approval ship as unlimited and may be set to a chosen period.
    • group name: defaults to the type name; empty means no folder level
    • abbreviation (mandatory)
    • DATEV document type
    • HBA signature required
    • sender whitelist for email import
  • Inactive types: if IXOS files a document of an inactive type, the type reactivates automatically. Exception: when "Email customer" or "Email supplier" is inactive, such mails are filed as type "Email".
  • Stamps per type: add, delete, reorder, rename, colour.
  • Custom keywords: name, data type, column. The built-in five cannot be recreated.

4.8.5 E-invoices [DE/EU-SPECIFIC]​

General idea: ingest structured invoices, validate them, extract metadata and match the supplier.

  • Formats: ZUGFeRD profiles Basic, Comfort (EN 16931) and Extended; XRechnung. Each e-invoice is one document, even when several are imported together.

  • Sources: IXOS's own invoicing, manual upload, mailbox.

  • On import: auto type and keywords from the XML; filed; metadata imported; visualised as PDF with the XML attached; validated.

  • Validation outcomes:

    ResultDisplayFiling
    SuccessGreenXML filed
    Success with notesGreenFiled; notes in the document history
    FailureRed; message at the top of IXOS; automatic task createdStays in the inbox; accepting the invoice is not recommended

    On failure: check the "document validated" history entry, test the XML with an online validator, and ask the issuer for a new invoice.

  • Contact matching order:

    1. exact address match in IXOS contacts
    2. otherwise, the contact of an existing invoice with identical invoice data
    3. otherwise, the contact whose email equals the sender's
    4. if several contacts match, none is assigned
  • Other fields: document date, number and value come from the XML.

  • Document type: "supplier invoice" if the contact is a goods-logistics supplier, otherwise "cost invoice".

  • The user should always verify auto-filled metadata.

4.8.6 Mailbox import​

  • Setup: a dedicated mailbox (e.g. erechnung@…) configured in DMS settings.

  • Polling: every 5 minutes. Mails are imported as copies; the original stays in the mailbox. Imported mails are not visible in IXOS Notes and cannot be answered from IXOS.

  • Server side: imported mails are moved into a new IMAP subfolder "IXOS Orbiz". Some mail clients need it subscribed manually.

  • Processing by mail content:

    Mail contentResult
    No attachmentStays in the inbox as PDF of type "Email", or is redirected to another mailbox (setting)
    Ordinary PDF invoiceType assigned, no contact; stays in the inbox with the mail attached until a contact is assigned
    Valid e-invoiceValidated, keyworded, filed as XML+PDF
    Several e-invoicesSplit into separate documents
    Invalid XMLStays in the inbox
  • Other document types by subject:

    • Each type has a sender whitelist; mails from other senders stay in the inbox.
    • Subject format: type | document date | further keyword values, separated by "|". Example: a user-created type "blister batch certificate" with date, batch, employee and number.
    • If every value can be mapped, the mail and its attachments are filed. Otherwise the mail stays in the inbox.
  • Every action is recorded in the document history.

4.8.7 Lifecycle: archive, delete, retention​

  • Archive (F12): for fully processed documents with all mandatory fields. They are greyed out and leave the active count. Reset with Ctrl+F12.
  • Delete (F4):
    • Only documents still in the inbox can be hard-deleted, and that cannot be undone.
    • Filed documents with complete metadata can only be soft-deleted (hidden). Hidden documents are shown in red with the "deleted" filter, and Ctrl+F4 reactivates them.
  • Automatic deletion: happens when the expiry date (document date + retention of the type) is reached. Per the data-protection FAQ, retention is defined per folder (user-defined for new folders). At expiry the document's key is destroyed, making the data unreadable.

4.8.8 Versions and history​

  • Versions: adding pages, deleting pages, rotating (and stamping, per the history text) creates a new version. Older versions can be viewed and restored as the current one. Pure keyword changes, archiving and stamping are classed as "process" operations, which by the permission text do not create a version.
  • Document history (F10): requires the right "manage DMS". Lists every action on the document: created, read, edited, new version, moved, exported, archived, reactivated, printed, permissions changed, deactivated, emailed, deleted, validated. Shows who did it, which process triggered it, and before/after values. A note appears if the document was exported to DATEV.
  • Filtering the history: by date range and action type, e.g. find all deletions on a day. "Show document" requires the deleted filter to be on.
  • Global history (Ctrl+F10): today's actions on all documents. Columns: date, type, contact, document, action, change, changed by. The detail adds file name, creator, path, client, workstation, keywords, stamps and email address.
  • Filter dialog (F6):
    • document types (multi-select; default all)
    • document date range (default 2 years back to today)
    • expiry range, amount range, contact
    • tax-office relevant yes / no / any
    • exported yes / no
    • state: active / recently archived (≤2 weeks) / archived (>2 weeks) / deleted
    • source: mailbox vs IXOS/manual
    • stamp: with / without / specific stamp + stamp date range
    • HBA signature: signed / pending / not required
    • client (all or a specific one)
  • The filter applies to the selected folder only.
  • Saved filters: name, set as default, rename, delete.
  • Results only include documents the user may at least read.
  • Fixed search folders (not editable, no drag-and-drop):
    • new: last 48 hours
    • active: not archived
    • with stamp: active documents with a stamp
    • tax office (year/month): tax-relevant documents of the last closed month
    • for HBA signature: documents with a pending signature

4.8.10 Permissions​

  • Module rights (granted to the Leiter role on activation; assignable per employee): manage DMS (document types, folder permissions, document history), delete documents, DMS print settings, start module, bulk export.
  • Folder rights:
    • Levels: read < process (keywords, archive, stamp, without a new version) < change (page edits that create a version).
    • Can be set on the client folder, the inbox, and any folder or subfolder, per employee or for all at once. The employee search covers own, branch and partner pharmacies, with a filter "only employees with rights here".
    • As soon as protection is activated on a folder, nobody has rights until rights are granted.
    • Protected folders show a lock. Subfolders inherit protection unless they get their own rights (separate key icon).
    • Switching off "folder protected by rights" deletes all its rights.
  • Data-protection facts (FAQ):
    • Access control by role is always on for the DMS; workstation-only protection is not possible.
    • A separate "DMS configuration" role stops staff from granting themselves rights.
    • Login uses password and/or fingerprint.
    • Every access and every change to documents and rights is logged (time, document, editor or viewer). Access to these logs can itself be restricted.
    • Documents leave the network only through print or export. Transfer to mobile devices happens only inside the pharmacy network. Transfer between group pharmacies uses the same protection as health-data transfer.
    • Per-document AES-256 keys are held locally; the cloud copy is encrypted and anonymised with a German provider (ISO 27001, BSI C5).
    • A scan-release step supports scan integrity. Restoring data relies on the backup concept.
    • The pharmacy decides whether it needs its own data-protection impact assessment (the vendor has one for cloud processing).
    • Data minimisation: print settings per document type decide what gets filed.

4.8.11 Stamps​

  • Insert a stamp: choose a date and a stamp. The dated stamp appears on the document.
  • Remove by clicking the stamp. Change the date by removing and re-adding.
  • Stamps can be hidden for printing.

4.8.12 Qualified electronic signature (QES with HBA) [DE-SPECIFIC]​

General idea: a sign-off queue for regulated records using a personal qualified certificate.

  • Default signature-required types: test protocols; compounding manufacturing instruction, manufacturing protocol and plausibility check; controlled-drug monthly printout. Any other type can be switched to "HBA signature required".
  • Workflow:
    1. Open the search folder "HBA signature required". Pending documents show a red stamp "HBA signature pending".
    2. Multi-select, then Sign (Ctrl+F12).
    3. Optionally tick "own only" (documents assigned to me).
    4. Confirm, then run the card signature.
    5. The documents get a green stamp "HBA signature done (date)".
  • Supervisory authority consent is needed before replacing paper with electronic signature.

4.8.13 Export with integrity proof​

  • Ways to export: folder context menu (folder, or folder + subfolders with structure); selected hits via Ctrl+F9; select all with F11.
  • Options:
    • "Include document archive": all metadata (keywords, stamps, history, history details) plus index.html, index.json and index.sig.
    • "Pack into 7-Zip" with an optional password.
  • Output: the documents directory under "DMS-Export", one uniquely named folder per export.
  • Files:
    • <number-type-date>.pdf, inside the DMS folder structure
    • index.html: human-readable. Export date and time, document count, IXOS version, folder tree, and per-PDF details including a SHA-256 hash and an "open" link.
    • index.json: machine-readable metadata and history, e.g. for import into another DMS.
    • index.sig: a CMS signature by the vendor over index.json. It proves integrity (nothing changed, added or removed) and authenticity (signed with the private key matching the shipped certificate).
  • Optional verification: openssl cms -verify -in index.sig -inform DER -content index.json -noverify -binary. "Verification successful" means unchanged and genuine.
  • Typical use: filter "relevant for tax office", then export all hits for the tax adviser.

4.8.14 Navigation between DMS and transactions​

  • From the DMS: "transaction details" (F7) jumps to the originating invoice, goods receipt or cash-book entry. Precondition: automatic scanning is enabled in system settings. Till transactions and cash-in/out filed without a scan or print are the exception.
  • From IXOS: a DMS icon on contact master data (all contact types) and on POS sales opens that contact's documents.
  • Cash book: a cash-out (F12) opens the scan window. The receipt is filed under Till / year / month / "cash-out cash book". F7 and the DMS icon link the two both ways.

4.9 DATEV accounting export [DE-SPECIFIC]​

General idea: produce period batches of double-entry postings from the merchandise system for an external general ledger, with a configurable chart of accounts, then re-import bank-matched payments to settle receivables.

4.9.1 Access and licences​

  • Opening the module requires the Leiter or Umsatzverantwortlicher role, and is subject to workstation protection.
  • "IXOS for DATEV" (paid) = full scope including the data service, and includes the DMS.
  • Automatic posting of imported payments needs the paid "Faktura Profi" licence. Importing just to view is free.
  • Pages: Export, Import, Settings, Data service.

4.9.2 Settings​

See section 7 for values.

  • Automatic debtor numbering:
    • Periodically scans invoicing-permitted customers without a debtor number and assigns one. Existing numbers are never overwritten.
    • Mode "alphabetic collective accounts": one account per surname initial, from the start value with the given spacing. A preview shows the resulting numbers.
    • Mode "consecutive individual accounts": the next free number in the DATEV debtor range above the start value.
  • Manual debtor numbering: per contact (payments page), or via report result processing (one number per query).

4.9.3 Account configuration (Alt+F12)​

  • Own numbers override the SKR03/SKR04 defaults: G/L accounts up to 8 digits, personal accounts up to 9 (depending on settings). The window opens on till revenues.
  • Till revenues: own numbers for Z-report postings. A self-defined till clearing account 1369 (SKR03) / 1469 (SKR04) separates postings covered by the Z report from manual till cash-outs, which go to the money-in-transit account 1360 in the cash-in/out tab.
  • Invoicing revenues / goods receipts: "intra-community acquisition" (IgE) accounts are used when the bank connection is in an EU country, taken from the Country field of the customer or supplier.
  • Debtor/creditor collective accounts: used when a contact has no individual account.
  • Cash-in/out:
    • Filter all / in / out.
    • Each row: own number, own name (as shown at the till), type, tax key, and "till" checkbox. Only ticked accounts are offered at the till's cash-in/out when DATEV is in use.
    • Self-defined accounts are added in the top row. They can be deleted only while they have no postings (otherwise a message appears).
  • External payment receipts: the account for re-imported payments, default 1200 (SKR03) / 1800 (SKR04).

4.9.4 Export batches​

  • New batch (F3):
    • Shows the fiscal year (derived from the fiscal-year end in the company master). If the oldest exportable document lies before the current fiscal-year end, the previous fiscal year is shown.
    • Period "from" = oldest exportable document date (fixed). Period "to" = user-chosen, defaulting to the newest exportable document date. The period must stay inside the fiscal year.
    • Scope ticks: till (Z-report documents + cash in/out); invoicing (invoices, bad-debt write-offs); goods receipts; internal clearing and goods movements (branch and partner pharmacies); DMS documents without IXOS reference (scanned documents flagged tax-relevant; always a separate batch; needs the DMS).
    • Long-running, with confirmations.
  • Recommendation: set "to" to the last day of the previous month, because accounting software processes one month at a time. Also agree the format with the tax office, and whether it wants till and invoicing together or separately.
  • Exportable means not yet in a batch, or released again by deleting a batch (F4), e.g. to rebuild for another period.
  • Data limits: only IXOS-generated data from 01.08.2011 onwards (the new Z report). Migrated data is excluded. By default only the current and previous fiscal year are included.
  • Batch list: filter by creation date. Columns: batch number, from, to, exported on, counts per source.
  • Posting tab: document indicator (linked DMS document exported with the posting / expected but missing / not needed), transmitted-to-DATEV flag, date, S/H, account, contra account, amount, document number (invoice or Z number), text with a type code. Cancellations in red. Sortable.
  • Protocol tab: results per export with workstation.

4.9.5 Export formats and security​

  • Batch export (F12) dialog:
    • Format: DATEV CSV version 700 or 510 (described to the adviser as DATEV format V1.4 / V5.1), or Postversand KNE/SELF (files ED00001, EV01).
    • "Lock flag active" fills the CSV lock column with 1 (else 0), which makes the records uneditable in the accounting software. Agree this with the tax office.
    • Encrypted (recommended; password following the password policy) or unencrypted. Choices are remembered.
  • Encrypted output: a 7z file DATEV_Exportlauf_Nr_<n>_VON_<yyyymmdd>_BIS_<yyyymmdd>.7z in subfolder Exportlauf_<n> of the export directory, plus an accompanying explanatory document for the adviser.
  • Hand-over to the adviser: format, chart (SKR03/SKR04), G/L account length 4, personal account length 5, the 7z file and the password. Send the accompanying document and the 7-Zip program only with the first delivery. The file may be emailed. Keep the media and the passwords strictly separate.
  • Unencrypted output: readable files; at the user's own risk (unprotected against staff or others).
    • Direct path: "export unsecured" (F11) in the new-batch dialog creates the batch and writes ED00001 (asks before overwriting).
    • "Change unsecured export" (Ctrl+F11) clears a batch's export date and status tick so new batches can be included in a fresh unsecured export.
    • If a batch is only marked this way and not actually re-exported, it still shows the status tick.
    • A secured export can be made from any batch regardless of unsecured exports.
  • Format choice: DATEV has frozen the Postversand interface and sells only the CSV interface, but many accounting systems still read only Postversand. The help therefore insists that the format be agreed with the tax adviser.
  • Master-data export (Ctrl+F12): debtors and creditors, own account names, VAT ID, country code. Formats DATEV 700, DATEV 510 or Postversand. Password-protected.

4.9.6 DATEV data service​

  • Prerequisites:
    • The tax adviser registers the pharmacy at DATEV as a sub-licence, activates it and grants access rights.
    • The adviser requests DATEV SmartLogin and activates it with the pharmacy.
    • Client and adviser numbers are configured in IXOS.
    • Paperless work also needs a procedure documentation for substitutive scanning.
  • Connecting (F5): SmartLogin by QR code (recommended; can be set as always) or smart card (does not work over IXOS Remote). The connection stays until disconnected or revoked, and can be reconnected.
  • Use: create a batch, then "transfer data" (F12). Postings and linked document images (booking-data and document-image services) go to the DATEV data centre. Per-record transmitted flag; protocol tab.

4.9.7 Payment re-import (DATEV-Import)​

  • Purpose: the external accounting system matches bank statement lines to open invoices and customer credits, then returns a DATEV-CSV file. Importing it books the payments in invoicing automatically, replacing manual "payment receipt" bookings.
  • File requirements:
    • Payments must be DEBIT records on the configured receipt account; other records are ignored.
    • Field "Belegfeld 1" must hold the invoice or credit number.
    • Shortened records: if two consecutive rows share account, contra account and text and the second has no document number, it inherits the first's number. If they differ, it stays blank.
  • Steps:
    1. Import page, New batch (F3), pick the file. The file is renamed with the suffix _eingelesen_StapelNr_<n>. Parse errors point to the faulty location.
    2. "Transfer payments" (F12) matches the records and sets statuses (tooltips give detail).
    3. Review in invoicing (filter by period, show paid items).
    4. Book the exceptions by hand.
  • Import archive view:
    • Filter by creation period.
    • Status filter values: no restriction; payments only (records on the receipt account); needs rework only (failed, partial or overpaid); no assignment (no document-number match); full payment; partial payment; no payment; no open amount; payment higher than open amount; credit note not supported.
    • Batch table and detail table columns are listed in 3.6.
  • Print (F9) of the imported records honours the current filter, for filing.
  • Delete an import batch (F4): only for wrong imports. It resets invoice payments already booked, but NOT credit settlements.
  • If a payment is later removed in invoicing, the import record's status updates.

4.10 Tax audit and till inspection exports (GDPdU und Kassen-Nachschau) [DE-SPECIFIC]​

General idea: one-click, encrypted regulator exports of all fiscal records in the mandated schema, bundled with a settings change log and a system description.

  • Access: Leiter or Umsatzverantwortlicher; workstation protection.
  • Pages: GDPdU, Kassen-Nachschau (DSFinV-K), TSE-Tar. Print (F9) is available.
  • GDPdU page:
    • Choose "for GDPdU" (full audit, "Z3 access") or "for till inspection" (GDPdU format).
    • Period up to 1 year. GDPdU data runs up to yesterday; till-inspection data up to today. A shorter period than one year needs confirmation.
    • Password (AES-256; data cannot be recovered without it).
    • Extras: annual stocktaking and permanent inventory (GDPdU only); cash-book postings (cash-outs and add/deduct corrections).
    • Output: a folder named by the period start date under GDPdU-Daten or Kassen-Nachschau_Export. It contains the packed data, an entpacken.bat unpacker (asks for the password and a target directory, which it creates), the instructions for the auditor, the settings change protocol and the procedure documentation.
    • Unpacked: up to 15 CSV files, with index.xml / index.pdf describing the entities and fields.
    • Re-running with the same start date overwrites the folder.
  • Till-inspection content (AO §146b, Art. 97 §30 EGAO): Z reports, totals, invoices, delivery notes, cash in/out, number gaps, prescriptions without a transaction, optionally cash-book postings.
    • Required capability since 01.01.2018. The auditor may demand it unannounced and take the data away. The taxpayer supplies a USB stick.
    • Until 2019 the GDPdU format was usual; from 01.01.2020 the auditor can demand DSFinV-K.
  • Kassen-Nachschau page (DSFinV-K):
    • Period up to 1 year, usually today only. Password.
    • Output: Kassen-Nachschau-DSFinV.7z in Kassen-Nachschau_Export/Kassen-Nachschau_DSFinV_Export<start date>, with the auditor document, settings protocol and procedure documentation. Same unpack procedure. Same start date overwrites.
    • DSFinV-K is a uniform taxonomy that allows checking the correct booking of business events (e.g. tips), not just manipulation-free tills. It goes beyond the GoBD export.
  • Precondition for all exports: Z reports (or the S report) for all till and secondary workstations in the period. Draw a Z report now if today is included.
  • Only IXOS-generated data is exported (not migrated data).
  • Handling tips:
    • Export the previous (fiscal) year at the start of each year.
    • Store on two USB sticks at different places.
    • Keep passwords in sealed envelopes, separate from the media.
  • Settings change protocol and procedure documentation: automatically copied into each export folder; also printable separately via F9. The protocol opens in print preview and can go to a printer, the PDF printer or a postbox. The procedure documentation opens in a PDF reader. See 4.11 and section 10.

4.11 System settings and change protocol (Systemeinstellungs- und Änderungsprotokoll) [GENERIC idea, DE-motivated]​

General idea: an auditor-facing, versioned log of configuration and permissions with who and when.

  • Size: at least 50 pages.
  • Contents:
    • pharmacy master data (company master), with historic values shown in light grey
    • permissions:
      • only detailed if at least one workstation has active or restricted protection; otherwise an explicit statement that anyone can use everything without password or fingerprint
      • workstation rights (which workstation protects which right)
      • operator rights (which operator has which right)
      • change history of both
    • all configuration parameters with history:
      • workstation-scoped parameters are printed once if identical everywhere, otherwise per workstation
      • parameters whose names contain Kennwort, Passwort, Password or Code (secrets) are suppressed
      • picking-robot parameters appear only if a robot is configured
      • licence-bound parameters appear only when licensed: Payback, MCard, Pricer ESL, parenteral compounding, BtM documentation, blood/T-prescription documentation, pickup terminal, compounding, delivery management, CashGuard
    • software update list with exact install date and time
  • History rules:
    • Changes are listed with date and user, and the log shows whether a change came from vendor remote support or pharmacy staff.
    • Only changes made later than 24 hours after installation or data migration are logged individually; the first day is treated as setup.

4.12 Fiscal security device (TSE) management [DE-SPECIFIC]​

General idea: a hardware or cloud signing module that signs every till transaction in a tamper-evident journal, with lifecycle management, failure logging and regulator reporting.

  • What the TSE does: a BSI-certified device on the server's USB port, mounted as a drive, with workstations assigned to it. It records every relevant till event and signs the transaction data cryptographically, so it can always be shown that the data was not altered.

  • Receipts: a working TSE prints its TSE data and, if configured, a QR code on every receipt. Without a TSE the receipt prints "No TSE configured".

  • Licensing: commissioning and configuring a TSE in IXOS is paid; viewing TSEs and the DSFinV-K export are free.

  • Settings view (Alt+F12):

    • workstations without a TSE
    • configured TSEs (serial number, start and end of operation)
    • details: state, validity, memory, remaining transactions, assigned count, serial, certificate ID
    • assigned workstations (with assignment date)
    • protocol
    • "show TSEs" (F2) lists every plugged TSE, including unconfigured ones
  • Commission (New TSE, F3): the plugged TSE is detected and its drive letter pre-filled. After OK, check that the three status indicators are green. Then change the PINs and PUK, and report to the tax office.

  • Re-commission: New TSE (F3) recognises a known serial and offers "use existing credentials" or "enter credentials".

  • Decommission ("end TSE operation", F4):

    • Sales can continue meanwhile.
    • Open transactions are closed as "abort", visible in the TAR export. Workstations are deregistered and unassigned. TSE data is backed up into the database. The end-of-operation date is set.
    • If the TSE is unreachable: no TAR backup, IXOS-side unassignment only, and a protocol entry as proof.
    • Sales finished after decommissioning print "No TSE configured".
    • The old TSE must be retained by law; on an owner change it stays with the former owner.
  • Swap wizard: for owner change, defect or certificate expiry. Start it by scanning the QR code on the shipping envelope, or with F6. It shows progress. The old TSE may stay plugged.

  • Certificate expiry: a Notes task appears when the certificate expires in less than 3 months.

  • PIN/PUK:

    • Initial values are stored at first commissioning; the user should set their own and keep them apart from the TSE, so it can be reused with another system.
    • Admin PIN: 5 digits. TimeAdmin PIN: 5 digits; used automatically several times an hour to sync the TSE clock. Admin PUK: 6 digits; used only to unlock a PIN.
    • A first change needs only the new values; later changes also need the old ones.
    • Unlock (Alt+F8) after three wrong PIN entries: drive letter, PUK, which PIN (Admin or TimeAdmin), new PIN.
  • Failure handling:

    • A failure creates a "today's tasks" popup and a Notes task (with a hint to contact the hotline).
    • Automatic protocol entries: every server start; configured TSE not found at start; TSE failed (e.g. pulled out; it usually recovers about 3 minutes after re-plugging); TSE-interface licence revoked or expired.
    • The taxpayer must record their recovery actions with "add entry" (F10, manual entry with operator).
  • Reporting recording systems (AO §146a):

    • All tills and secondary workstations must be reported. The duty starts 01.07.2025. Existing systems must be reported by 31.07.2025; new systems within one month of acquisition; reporting has been possible since 01.01.2025.
    • Print a data sheet (F9), or export ELSTER XML (F12) to ELSTER-Datenexport/Aufzeichnung146a_<YYmmDD_HHMMSS>.xml and upload it into the online form, which pre-fills it. Taxpayer data must be added in the form.
    • A reminder appears before export.
    • Report-relevant actions create a Notes task: TSE registered; system assigned; system detached; TSE deregistered.
  • Workstation numbering:

    IdUse
    APL000Fallback, normally unused
    APL001Server console
    APL002–003Service and remote maintenance
    APL011–029Home access
    APL030–049Branch access
    APL050–099Vendor-supplied secondary workstations
    APL100+Secondary workstations on pharmacy hardware
    KASxxxVendor till workstations

    APL00x always exist; from APL011 on, only licensed workstations are created.

  • Number gaps: if an error hits after document-number assignment and TSE signing during the final booking of a total, IXOS still completes the transaction properly. The resulting gaps in TSE transaction numbers and receipt numbers are logged, exported, and explained in the auditor document.

  • Logging scope: every till event is logged, including aborted sales (price enquiries, prescription checks, "just looking") and technical aborts when a sale moves to invoicing.

4.13 TSE TAR export [DE-SPECIFIC]​

  • IXOS backs up the TSE journal to the server weekly as TAR files.
  • Export page: period up to 1 year, up to today (usually today). Password.
  • Choice: only the IXOS-held backups for the period, or also pull current data from the TSE.
  • Output: TSE-Tar-Export.7z in IXOS_Dokumente/TSE_Export/TSE_Export_<YYYY_MM_DD> (export date; a second export on the same day overwrites), plus the auditor document, 7z.exe and entpacken.bat.
  • After unpacking: TAR files named after the weekly backups, readable with external tools (the vendor offers no viewer).
  • TSE data holds only figures (turnover, amounts) and no IXOS cross-references (receipt or cash-in/out numbers). For those, use DSFinV-K.

5. Workflows​

5.1 Controlled drug: from sale to monthly close​

  1. At the POS a controlled drug is sold. If "ask customer and doctor at BtM sale" is on, the sale prompts for the customer, the prescriber and the controlled-drug prescription number.
  2. With auto-documentation on (and the article not on the exclusion list), a "sale" movement is written to the drug's card. The card shows the to-do icon if data is missing.
  3. Goods receipts (optionally with the delivery-receipt number) and returns add movements the same way. Compounding is entered manually.
  4. During the month the pharmacist opens the card (Details), completes missing fields and orders same-day movements correctly. Each movement is ticked "checked"; the system lists anything missing.
  5. Destructions are entered manually, checked, and a destruction protocol is printed and signed by two witnesses and the manager.
  6. At month end the pharmacist prints the stocktaking list to check the safe, and optionally a draft monthly printout.
  7. Monthly printout: the system checks that every movement is complete and checked and that stock is never negative. If not, it offers only a draft. Otherwise "print and close reports" closes the reports and gives them numbers.
  8. The printout is signed with initials and the check date, or filed in the DMS and signed with QES by the named employee.
  9. Later corrections to closed periods are impossible. Cancellations after the close create opposite movements.
  10. A card with zero stock and all reports printed can be archived. A new movement reactivates it.

5.2 Blood product or T-drug dispensing and recall​

  1. A goods receipt creates a receipt record (auto) and prompts for batch(es).
  2. At dispensing, the sale prompts for patient and doctor. The record window opens pre-filled. The user picks the batch from those received and confirms.
  3. Incomplete records stay "incomplete" in Current. The user completes them via Details.
  4. TFG: from the dispensing record, print the doctor notification (product, batch, quantity, date, patient name, first name, date of birth, residence).
  5. Periodically print the register:
    • TFG: start = day after the last print; whole days; incomplete records skipped with a prompt. Printing closes the period, and later changes are reprinted from the print archive.
    • T-prescriptions: by default unprinted records only.
  6. Recall: search #batch to find all patients and suppliers.
  7. After the retention period, personal references are erased per the deletion-period setting. TFG records older than 30 years may be deleted.

5.3 Starting-material incoming test​

  1. A goods receipt of a drug/chemical article creates a test candidate.
  2. Check candidate (or New + article), then pick a monograph (truncated-name search), then take it over.
  3. Fill header data: internal batch, supplier batch (auto-filled from goods receipt if batch maintenance is on), quantity, expiry, correction factor, delivery data, editor.
  4. Check the certificate: analysis data conform, date, ZL mark.
  5. Choose the applicable identity tests and record conforms and/or a remark for each.
  6. Closing: release or no release, date, responsible pharmacist. Validation runs; the protocol moves to Closed.
  7. The print selection opens: protocol (or DMS filing plus HBA signature), draft, container labels. A printed or filed protocol is locked (configurable).
  8. If a closed protocol changes, reprint, re-sign and destroy the old printout.

5.4 Daily FAM/MP spot check​

  1. New, then pick the article, then record batch, expiry, origin, count, reason, destructive test, tester and result. On defects, record the notifications.
  2. Watch the week and month counters against the quota (6 per week).
  3. At week or month end, "print and close", then sign each line.

5.5 Supplier invoice, e-invoice and document capture​

  1. A supplier emails an e-invoice to the dedicated mailbox. The DMS polls every 5 minutes.
  2. The invoice is validated, then keyworded from the XML (contact matched by address, previous invoice or email), typed as supplier invoice or cost invoice, filed under folder/letter/contact/type/year/month, and flagged tax-relevant per its type.
  3. Validation failure: it stays in the inbox, and a task and a message are raised.
  4. Paper documents are scanned (with a type and keywords). Values can be right-clicked into keywords. Once mandatory keywords are complete, the document auto-files.
  5. Staff stamp documents (e.g. "Paid" with a date), add notes, archive processed ones.
  6. Monthly, the "tax office (year/month)" search folder or a filter collects the tax-relevant documents. They are exported (with archive and signature) or flow to DATEV as unreferenced documents.
  7. Retention expiry deletes documents automatically through key destruction.

5.6 Monthly accounting export​

  1. Once: set the client and adviser numbers, chart, account lengths, closing basis and directory. Map own accounts. Tick the cash-in/out accounts offered at the till. Configure debtor numbering. Make sure the pharmacy IBAN is in the company master.
  2. Agree with the tax office: format (CSV 700/510 or Postversand), lock flag, separate or combined till/invoicing batches.
  3. New batch, "to" = last day of the previous month, choose the scope.
  4. Review the postings (account, contra account, amount, debit/credit, document number, type code; cancellations in red; missing-document indicators).
  5. Either:
    • export encrypted, then hand the 7z file + password (+ accompanying document and 7-Zip the first time) to the adviser; or
    • transfer through the DATEV data service; or
    • export unsecured for a local booking system.
  6. Separately, export master data (debtors and creditors) when it changes.
  7. The adviser books the data, matches bank payments and returns a DATEV-CSV.
  8. Import it, then "transfer payments". Fully paid invoices and credits are settled. Partial payments are booked for invoices only. Overpaid, dunned, credit-note, unmatched and wrong-sign records are listed for manual handling in invoicing. Print the import overview.

5.7 Till inspection visit​

  1. The inspector arrives. Draw a Z report now so that today is closed.
  2. GDPdU and till inspection → Kassen-Nachschau page → period today → password → export.
  3. Hand over a USB stick with the folder: data, unpacker, auditor document, settings protocol, procedure documentation. Give the password separately.
  4. If asked for raw TSE data: TSE-Tar page, export today, including current data pulled from the TSE.

5.8 Annual audit preparation​

  1. At the start of a (fiscal) year: GDPdU export of the previous year with extras (stocktaking, permanent inventory, cash book).
  2. Store it on two USB sticks in different places, with the password kept in a sealed envelope, separately.

5.9 TSE lifecycle​

  1. Commission (New TSE), check the three green indicators, set your own PINs and PUK, and report the recording systems to the tax office (data sheet or ELSTER XML).
  2. On failure: follow the task, re-plug (recovery ≈3 minutes), and add manual protocol entries describing the actions taken.
  3. Certificate expiry warning (<3 months), defect or owner change: run the swap wizard (or decommission + commission), keep the old TSE, and report the change.

6. Business rules and calculations​

6.1 Controlled-drug register​

  • Stock: stock after each movement = previous stock + receipt − issue. It is computed in the documentation unit and covers all articles on a card.
  • Monthly printout gate:
    • Every movement in scope is checked.
    • All mandatory fields are filled.
    • Stock never goes below 0 at any point of the sequence.
    • Same-day order is consistent.
  • Mandatory fields: document number is mandatory for sales only. Doctor fields are required for sales except to branch or partner pharmacies.
  • Closing: a closed report is immutable. A checked movement can be edited only after unchecking, and only before the close. Editing one movement unchecks the affected neighbours.
  • Cancellation: before the close the movement is deleted; after the close an opposite movement is posted.
  • Archive eligibility: all reports printed AND latest remaining stock = 0. A new movement reactivates the card.
  • Merge or split with printed history and stock: carry-over movements, an automatic closing report on the predecessor, archiving of the predecessor.
  • Unit change: allowed only while the open report has no checked movements.
  • Field limits: remark ≤ 200 characters; stock ≤ 9 digits.
  • Changed return lines: a later change to a return line resets "checked" only if the monthly printout has not yet happened.

6.2 TFG and T-prescription registers​

  • Completion: a record is complete when all mandatory fields are filled, including the prescribing doctor for dispensings (except returns to the supplier) and at least one batch line.
  • Pack total: equals the sum of the batch lines after the user confirms. It cannot be edited directly.
  • TFG print period: start = day after the last print (fixed); end defaults to today. A print covers whole days, so later movements on the same day fall into the printed period. A printed period counts as closed, and changes in it are reprinted via the archive.
  • T-prescription print: editing a printed record resets its printed status.
  • Retention: TFG ≥ 30 years. Deleting younger records is logged.
  • Field limits: TFG batch ≤ 30 characters.

6.3 Test protocols​

  • Starting materials:
    • Mandatory fields are validated at release.
    • Release or no release closes the protocol; resetting the assessment to none reopens it.
    • Printed or DMS-filed protocols lock (configurable).
    • Tests with no result are dropped from the printout.
    • Test date = creation date and is not updated on edits.
    • Weighing correction factor has 3 decimals. Supplier batch ≤ 50 characters. Source abbreviation ≤ 20 characters, name ≤ 50, split at the first hyphen.
    • Monograph search shortens the term down to a minimum of 4 characters.
  • FAM/MP:
    • Test numbers are sequential and never reused.
    • Printed protocols lock.
    • Week and month counters ignore filters.
    • Retention ≥ 5 years. Quota: 1 per day or 6 per week.

6.4 DATEV​

  • Account number padding: with "extend account numbers" on, an account shorter than the G/L length is right-padded with zeros to that length. In the master-data export it is padded to the personal length (G/L + 1).
  • Account lengths: G/L accounts up to 8 digits; personal accounts up to 9 (setting-dependent). The adviser hand-over states 4 and 5.
  • Closing basis: S-basis sums all tills under the S report's document ID. If closings were not done by S report, the export falls back to the Z basis.
  • Exportable records: not in any batch (or freed by deleting a batch); created by IXOS on or after 01.08.2011; not migrated; by default not older than the previous fiscal year.
  • Batch period: must stay inside one fiscal year. "From" is fixed to the oldest exportable document.
  • Fiscal year: derived from the fiscal-year end (MMDD). If the oldest exportable document predates the current fiscal-year end, the previous fiscal year applies.
  • Intra-community acquisition accounts: used when the counterparty's country is an EU country.
  • Collective accounts: used when the contact has no individual debtor or creditor number.
  • Debtor numbering:
    • Consecutive mode: next free number above the start value.
    • Alphabetic mode: one account per surname initial, start value + spacing steps.
    • Never overwrites an existing number; runs periodically.
  • Self-defined accounts: can be deleted only if they have no postings.
  • Tax keys and rates by period:
KeyMeaninguntil 30.06.202001.07.–31.12.2020from 01.01.2021
1VAT-exempt (with input-tax deduction)–––
2reduced output VAT7%5%7%
3full output VAT19%16%19%
4historic reduced output VAT–7%5%
5historic full output VAT16%19%16%
6historic reduced input VAT–7%5%
7historic full input VAT16%19%16%
8reduced input VAT7%5%7%
9full input VAT19%16%19%

(The "historic" keys carry the rate of the previous regime, so documents dated in the earlier period can be posted correctly.)

  • Payment import matching:
    • Only debit records on the receipt account are considered.
    • Match on "Belegfeld 1" against the invoice or credit number.
    • Full payment: amount = open amount, or open amount minus cash discount (Skonto). The invoice or credit is settled.
    • Partial payment: allowed for invoices only. Credits can only be settled in full; a partial credit payment is not booked.
    • Not booked: overpayment (always the case for dunned invoices that include a fee), no or unknown document number, wrong account, debit/credit swapped, credit notes (not supported), or "no open amount" (already set paid in invoicing).
    • Deleting an import batch resets the booked invoice payments but not the credit settlements.

6.5 DMS​

  • Delete: hard delete only from the inbox; filed documents are soft-deleted.
  • Expiry: document date + retention of the type; automatic deletion at expiry (key destruction).
  • Retention: cannot be shortened below the legal default (except the unlimited-by-default types).
  • Duplicates: checked per client on scan and import.
  • Auto-filing: happens when the mandatory keywords are complete. Changing keywords re-files.
  • Permission inheritance: down the tree unless overridden. Search hides documents without read right.
  • Versions: created by page operations and stamping. Restoring a version creates a new current version.
  • E-invoice contact match: exact address → identical earlier invoice → sender email → none if ambiguous.
  • Email import: subject parsing must map every pipe-separated value, otherwise the mail stays in the inbox. Senders must be on the type's whitelist.

6.6 Fiscal exports and TSE​

  • Periods: every export is ≤ 1 year. GDPdU runs up to yesterday; till inspection and TSE up to today.
  • Precondition: Z reports (or the S report) drawn for the period.
  • Overwrites: same start date (GDPdU and DSFinV-K) or same export date (TSE TAR) overwrites the output folder.
  • Encryption: AES-256, with no recovery without the password.
  • Settings log: only changes after the first 24 hours following installation are logged individually. Secret-bearing parameters are excluded.
  • PIN/PUK formats: PINs 5 digits, PUK 6 digits. Three wrong PIN entries lock the PIN; the PUK unlocks it.
  • Certificate warning: below 3 months to expiry.
  • TSE recovery: about 3 minutes after re-plugging.
  • Decommissioning: closes open transactions as "abort".

7. Configuration and settings​

ParameterScopeEffectDefault
BtM automatisch dokumentierenDocumentation mgmtAuto-create controlled-drug movements from POS, goods logistics, pickups, blisters(not stated)
Rezepturbestandteile dokumentierenDocumentation mgmtAuto-document controlled-drug components of compounding (where applicable)(not stated)
Substitutionstherapie dokumentierenDocumentation mgmtAuto-document substitution therapy dispensing(not stated)
Kunde und Arzt bei BtM-Verkauf abfragenDocumentation mgmtPrompt for customer, doctor and BtM prescription number in the sale(not stated)
Abgabebelegnummer bei BtM-Wareneingang abfragenWorkstation, page BtMOptional discrepancy prompt for the delivery-receipt number at goods receipt(not stated)
Abgabebelegnummer bei BtM-Retoure abfragenWorkstation, page BtMPrompt for the delivery-receipt number at return(not stated)
Monatsausdruck-DarstellungSystem, page BtMMonthly printout continuous or one page per drugcontinuous
BtM exclusion listDocumentation mgmtPer article: exclude POS/invoicing and/or goods logistics from auto-docempty
List settings (BtM)User/listShow running number, old stock, article, supplier, PZN columnsoff
TFG-Produkte und T-Rezepte – Automatische DokumentationDocumentation mgmtAuto-create TFG and T-prescription recordsOFF
Kunde und Arzt bei Verkauf abfragenDocumentation mgmtPrompt for customer and doctor when selling TFG or T-drugsON
(TFG) batch prompt at goods receiptGoods receiptOptional discrepancy asking for batch numbers(not stated)
Löschfristen für Bezug zu personenbezogenen DatenDocumentation mgmt (keep identical across group)When patient/doctor references are irreversibly erased from BtM, TFG and T-prescription records and logs(not stated)
Prüfkandidaten vorschlagenSystem, page Starting productsPropose drug/chemical goods-receipt lines as test candidatesON
Chargenpflege für Ausgangsstoffe(config)Copy supplier batch from goods receipt into the test protocol(not stated)
Ausgedruckte Prüfprotokolle sperren(config)Lock printed or DMS-filed starting-material protocolsON
TFG/T print "save as default"Print dialogRemembers sort and selection optionschronological (TFG) / by PZN, unprinted only (T)
DMS document type settingsDMS adminFolder, grouping, contact role, retention, tax relevance, DATEV document type, HBA required, sender whitelist, stampsvendor set
DMS document type "BtM Monatsausdruck" / "Ausgangsprodukte Prüfprotokoll" activeDMS adminWhen active (with DMS licence), these documents are filed in the DMS instead of printedactive
DMS custom keywordsDMS adminExtra metadata fieldsnone
DMS settings: automatic scanningSystem settings > Office > DMSScan prompts after goods receipt/returns and at POS cash in/out; needed for F7 back-navigationON after first start
DMS print settings per document typePrint settingsWhich printouts are also or only filed in the DMS (summary receipt, return slips, delivery note A4, invoice, dunning, credit slip)ON for those listed
DMS e-invoice mailbox / redirect mailboxDMS settingsMailbox to poll (5 min); where mails without attachments gonone
DMS folder permissionsPer folderRead / process / change per employeeunprotected; once activated, no rights
DMS saved filtersUserNamed filters, one defaultnone
DATEV Mandanten-NummerDATEV settingsClient ID (≤5 digits)–
DATEV Berater-NummerDATEV settingsAdviser ID (≤7 digits)–
KontenrahmenDATEV settings / company masterSKR03 or SKR04–
KassenabschlussDATEV settingsExport by Z report or S reportZ report
SachkontennummernlängeDATEV settingsG/L digits; personal = +1(adviser hand-over states 4/5)
Kontennummern erweiternDATEV settingsZero-pad account numbers to configured lengthON
Buchungen ignorierenDATEV settingsExclude postings older than previous fiscal year / noneolder than previous fiscal year
GeschäftsjahresendeCompany masterFiscal year end MMDD–
Belege ohne Referenz exportieren abDATEV settingsStart date for unreferenced DMS document export–
SpeicherortDATEV settingsDocuments drive (remote/branch access) or pharmacy drive (needed for automation)(not stated)
DebitorenkontenvergabeDATEV settingsManual or automatic for invoicing customers(not stated)
Methode / Startwert / AbstandDATEV settingsAlphabetic collective vs consecutive individual accounts; start; spacing(not stated)
Own account numbers (6 tabs)Account configurationOverride standard chart accountsstandard chart
"Kasse" flag per cash-in/out accountAccount configurationOffer the account at the tilloff
External receipt accountAccount configurationAccount for re-imported payments1200 (SKR03) / 1800 (SKR04)
Export format / lock flag / encryptionBatch export dialog (remembered)CSV 700/510 or Postversand; lock flag 0/1; passwordlast used
Immer mit DATEV SmartLogin anmeldenData serviceAlways use SmartLoginoff
IBANCompany master > FinanceRequired for DATEV export–
Debitoren-/KreditorennummerCustomer/supplier payment pageIndividual personal accountempty (collective)
GDPdU extrasExport dialogAnnual stocktaking, permanent inventory, cash-book postingsoff
TSE PINs/PUKTSE settingsAdmin PIN (5), TimeAdmin PIN (5), Admin PUK (6)vendor initial values
TSE QR code on receipt(till config, referenced)Print TSE QR code(not stated)

8. Roles and permissions​

  • DATEV module and GDPdU/till inspection module: role Leiter (manager) or Umsatzverantwortlicher (turnover-responsible). Also subject to workstation protection (per workstation and/or per user, with password or fingerprint).
  • Controlled-drug documentation: subject to workstation protection. Specific rights are not named in these pages.
  • DMS module rights (granted to Leiter on licence activation; Leiter assigns them to employees):
    • manage DMS: document types, permissions, document history
    • delete documents
    • DMS print settings
    • start module
    • bulk export
  • DMS folder rights: read / process / change, per employee, inherited down the tree. A separate "DMS configuration" role prevents self-granting. In the DMS, role-based protection is always active.
  • Signing:
    • Monthly controlled-drug printouts and test protocols are signed by a pharmacist (paper) or via HBA QES by a named employee ("own only" filter).
    • Destruction protocols need two witnesses plus the pharmacy manager.
    • FAM/MP lists need the responsible pharmacist's signature per line.
    • Starting-material protocols need the responsible pharmacist, who need not be a stored employee.
  • Supervisory authority: prior consent is needed for electronic filing with QES instead of paper.
  • Audit trail of permission changes: in the settings change protocol (with operator, including vendor remote support).

9. Integrations, hardware and external services​

  • DATEV:
    • file export: CSV formats 700/510, also called V1.4/V5.1, and legacy Postversand KNE/SELF (ED00001/EV01)
    • re-import of DATEV-CSV
    • DATEV data service (booking data + document images) via SmartLogin (QR code) or smart card
    • packing with 7-Zip (7z, AES)
  • Accounting systems other than DATEV that read the same formats.
  • Health professional card (HBA) reader for qualified electronic signatures.
  • Scanner (TWAIN-style scan dialog) for the DMS; article barcode scanner, also used to scan the TSE shipping-envelope QR code.
  • Email: IMAP mailbox polled by the DMS (subfolder "IXOS Orbiz"); outbound email for documents and signed forms.
  • E-invoice standards: ZUGFeRD (Basic, Comfort, Extended), XRechnung, with an XML validator.
  • Cloud storage: encrypted, anonymised, at a German ISO 27001 / BSI C5 provider.
  • Customer display and mobile web page for the digital signature (QR code).
  • TSE: BSI-certified USB device on the server, signs till transactions. Journal backed up weekly as TAR.
  • Tax authority: ELSTER (XML upload for §146a reporting); export formats GDPdU (CSV + index.xml) and DSFinV-K (CSV taxonomy).
  • OpenSSL: for verifying DMS export signatures (CMS).
  • External programs: Dr. Lennartz laboratory program (controlled-drug compounding components). Pricer ESL, Payback, MCard, CashGuard and pickup terminal are mentioned only as licence-gated parameters in the settings protocol.
  • Internal: IXOS Notes tasks (TSE failure, certificate expiry, reporting duty, e-invoice validation failure); the IXOS.eCall support channel.

10. Printouts, reports and exports​

OutputSourceContent / rules
BtM stocktaking listBtM printDrugs with stock. Substance cards: name, dosage form, total stock, plus assigned articles (name, supplier, PZN, unit)
BtM monthly printoutBtM printAll checked movements since the last printout. Printout number in header, per-drug report number, optional corrections. Continuous or page per drug. Signed (initials + check date) or DMS-filed + QES. Closes reports
BtM monthly printout draftBtM printSame, marked draft, with to-do icons and pending report numbers. Not legal proof
BtM monthly printout reprintPrint archiveAny earlier monthly printout, optionally with corrections
Destruction protocolBtM movement (destruction/loss)Movement data with reason, method and remark. Signed by two witnesses + manager
Closing report on merge/splitCard editingAutomatic predecessor report with carry-over
BtM extended search printExtended searchSelected cards or movements. No carry-overs or report numbers
TFG doctor documentation (A)TFG print / single dispensingProduct, batch and quantity, dispensing date, patient name, first name, date of birth, residence. Period with or without already-printed entries
TFG register (B)TFG printChronological, or grouped by PZN (groups A–Z, date ascending, receipts first), optional page per PZN. Since last print; incomplete records excluded
TFG print archive reprintTFG printWhole period reprinted. Warning icon if changed after print
T-prescription listT printUnprinted only, or all incl. printed (with period). By PZN (default, page-per-PZN option) or chronological
Starting-material test protocolProtocolClosed protocols. Printed or DMS-filed (default with DMS). Tests without result omitted
Starting-material draft protocolProtocolOpen protocol marked draft
Storage-container test labelProtocolGiven quantity
FAM/MP protocol listFAM printUnprinted protocols. Closes them. Signature column per line. Explanatory footnote
FAM/MP criteria checklistProtocol dialogGuideline checklist
DATEV export batchDATEV7z (encrypted) or plain CSV/Postversand, plus accompanying adviser document
DATEV master-data exportDATEVDebtors, creditors, own account names, VAT ID, country code
DATEV import overviewDATEV importImported records with status, honouring the filter
DMS exportDMSPDFs (+ folder tree), index.html with SHA-256 hashes, index.json, index.sig. Optional 7z + password
GDPdU exportGDPdU pageEncrypted package, up to 15 CSV files + index.xml/pdf, unpacker, auditor instructions, settings protocol, procedure documentation
Till inspection export (GDPdU format)GDPdU pageZ reports, totals, invoices, delivery notes, cash in/out, number gaps, prescriptions without transaction, optional cash book
Till inspection export (DSFinV-K)Kassen-Nachschau pageKassen-Nachschau-DSFinV.7z + auditor document + protocol + procedure documentation. Includes aborted and technical transactions and logged number gaps
TSE TAR exportTSE-Tar pageTSE-Tar-Export.7z (weekly TAR backups ± live TSE data) + auditor document + 7z.exe + unpacker
System settings and change protocolGDPdU print / export folderMaster data, rights, configuration parameters, updates, each with history
Procedure documentation (GoBD)GDPdU print / export folderPDF system description
TSE data sheet / ELSTER XMLTSE settingsRecording-system data for the §146a report

11. Dependencies on other modules​

  • POS (Kasse): source of controlled-drug, TFG and T-drug dispensing (with customer, doctor and prescription prompts), pickup resolution, cash-in/out (DATEV accounts offered at the till), Z and S closings (DATEV basis; precondition for fiscal exports), TSE signing and receipt printing, digital signature trigger, scan prompts at cash in/out.
  • Goods logistics (Warenlogistik):
    • goods receipt: register entries; discrepancy prompts for delivery-receipt number or batch; starting-material test candidates; supplier batch transfer
    • returns: register entries plus the warning on later changes
    • correction bookings: cancellation entries
    • DATEV goods-receipt postings
    • DMS scans of delivery notes and return slips
  • Sales administration: sale changes and cancellations update the registers.
  • Invoicing (Faktura): invoices, delivery notes, dunning, credits are filed in the DMS. DATEV invoicing postings and bad-debt write-offs. Payment receipts (manual F11 or via DATEV import). A POS sale handed to invoicing creates a technical abort in the till log.
  • Compounding (Rezeptur) and parenteral compounding: controlled-drug components entered manually. Manufacturing documents need QES in the DMS.
  • Unit-dose / weekly blister, substitution therapy: controlled-drug movements.
  • Contacts: customer, doctor and supplier pickers. Debtor and creditor numbers. Country (EU detection). DMS icon on contacts. Address-book entries.
  • Article management: article search; drug/chemical flag; controlled-drug, TFG and T-drug classification; alternative units; PZN / pack-size identity.
  • Company master (Firmenstamm): IBAN, chart, client and adviser numbers, fiscal-year end, add-on module ordering.
  • Cash book (Kassenbuch): cash-outs scanned into the DMS; cash-book postings in fiscal exports.
  • Stocktaking (annual, permanent): GDPdU extras.
  • Print settings / print forms: DMS filing per form; expert copies of forms.
  • System settings, user accounts, workstation protection, IXOS Notes tasks, branch/partner pharmacy group (internal clearing, cross-client DMS search, shared deletion periods).

12. Portability notes​

FeatureTagUnderlying idea for Shefa
Controlled-substance ledger (cards, running balance, per-line check, monthly close, destruction protocol with witnesses, change history, exclusion list, substance-based cards)DE-SPECIFIC (BtMVV)Any narcotics/psychotropic register. Syria has controlled-drug record duties. Model: per-product (or per-substance) ledger, auto-fed by POS and receiving, manual movement types, release flag, period close that locks entries, opposite-entry corrections after close, signed period report
Blood/haemophilia batch register (30 years)DE-SPECIFIC (TFG/ApBetrO §17)Lot-level traceability for high-risk biologicals with recall search by batch, prescriber notification, very long retention
T-prescription registerDE-SPECIFICSpecial registers for restricted drugs (teratogens, isotretinoin, etc.) with batch and prescription-copy tracking
Starting-material QC protocols with monographsDE-SPECIFIC (ApBetrO §6/11)Incoming QC for compounding raw materials: templated tests, certificate check, release/reject, container labels, locked after print
FAM/MP spot checks with quota countersDE-SPECIFIC (ApBetrO §12)Daily random QC checks with defect escalation tracking and quota dashboard
Personal-data deletion periodsGENERIC (GDPR-driven)Configurable anonymisation after statutory retention
Digital customer signature via QRGENERICConsent and e-signature on the customer's phone, auto-filed
DMS with document types, keywording, auto-filing, versions, history, folder ACLs, stamps, saved filters, search foldersGENERICCore of a pharmacy document archive. Per-type retention and tax flags. Crypto-shredding at retention end. Signed export bundle (JSON + signature + hash index)
E-invoice ingestion (ZUGFeRD/XRechnung)DE/EU-SPECIFICIngest structured supplier invoices (whatever e-invoice standard applies), validate, match supplier, auto-file
Mailbox import with subject parsing and sender whitelistGENERICEmail-to-archive pipeline
QES with HBADE-SPECIFICSign-off queue with qualified personal certificates (or any strong signature) for regulated records
DATEV export (SKR03/04, tax keys, Postversand/CSV, lock flag, data service)DE-SPECIFICAccounting export: configurable chart-of-accounts mapping, period batches with source scopes, debit/credit records with type codes, encrypted hand-off or API push, master-data export
DATEV payment re-importDE-SPECIFICBank reconciliation feedback loop: import matched payments, auto-settle receivables, exception list
Debtor auto-numberingGENERICAutomatic receivable sub-ledger account assignment
GDPdU / DSFinV-K / till inspectionDE-SPECIFICOne-click regulator export of all fiscal records in the mandated schema, encrypted, with schema description
TSE, TAR export, §146a reportingDE-SPECIFIC (KassenSichV)Tamper-evident fiscal log: sign every till event (including aborts), monotonic numbering, gap logging, device lifecycle, regulator registration of tills. Could be a software hash chain or an HSM in other markets
Settings and change protocol, procedure documentationGENERIC (audit-driven)Versioned configuration audit log with who and when, excluding secrets; maintained system description for auditors

13. Open questions​

  • Controlled-drug configuration defaults: defaults for "document BtM automatically", "document compounding ingredients", "document substitution therapy", "ask customer and doctor at BtM sale" and the two delivery-receipt prompts are not stated.
  • Deletion periods: the values (and units) of "deletion periods for personal-data references" are not given; only the TFG minimum (30 years) and FAM (5 years) are stated. Controlled-drug and T-prescription retention minimums are not stated in these pages.
  • "Rezepturbestandteile dokumentieren" vs manual compounding: the help says compounding must always be entered manually, yet a parameter for documenting compounding ingredients exists. Its exact scope is unclear.
  • Which document types exist: the full vendor list of DMS document types, their default retention periods, default tax relevance and DATEV document-type values is not listed. Only examples are given: supplier invoice, cost invoice, Email (customer/supplier), consent declaration, employment contract, appliance approval, BtM monthly printout, starting-product test protocol, invoicing invoice / delivery note / dunning, return slip, credit slip, cash-book cash-out.
  • Retention defined where: the FAQ says retention is per folder; the administration page says per document type. The exact model is ambiguous.
  • Whether stamping creates a version: the history page says yes; the permission page says "process" (stamping) does not.
  • Scan release process: the FAQ mentions an "integrated release process per document" for scans, but no page describes it.
  • DATEV data structures: the exact CSV columns, the default SKR03/SKR04 account numbers per revenue or receipt category (other than 1200/1800, 1360, 1369/1469), the posting logic per source (till, invoicing, goods receipt, internal clearing) and the cost-centre handling are NOT described. Cost centres are not mentioned at all.
  • DATEV account lengths: the adviser hand-over says 4/5 while the settings allow up to 8/9. The relation is not explained.
  • DATEV data service: error handling and retry are not described beyond the protocol tab.
  • DSFinV-K and GDPdU file lists: "up to 15 CSV files" but no list of the files or fields (left to the accompanying documents, which are not in this slice).
  • TSE in signing: how the TSE integrates with each till transaction (start/update/finish), the receipt fields printed, and the QR-code content are not covered here; probably documented in the POS chapters.
  • GDPdU export directory: inconsistent drive letters in the help (X: vs Z:) for the till-inspection export directory.
  • TSE decommissioning preconditions: the stated preconditions ("TSE plugged" and "TSE not reachable") read like two alternative cases rather than joint preconditions.
  • T-prescription prescription copy: the "shipping date of the prescription copy" (presumably the copy sent to BfArM) — the reporting process itself is not described.
  • Blister batch certificate email example: the meaning of its fields (batch, employee, number) is not explained.

14. Source pages​

All 98 pages of the manifest were read.