Skip to main content

Back-office invoicing: customer orders and delivery notes (Faktura: Aufträge, Lieferscheine)

1. Purpose and scope​

The Faktura module is the pharmacy's back-office sales-on-account system. It serves customers who are not paying at the counter but are supplied and billed later: care homes and their residents, doctors' practices, hospitals (clinics) and their wards, companies, other pharmacies (as a wholesaler), branch or partner pharmacies, and individual patients with an account. In a pharmacy group it is also used to settle value-voucher (Wertgutschein) redemptions with the partner pharmacy that issued them.

What the module does, end to end:

  • collect the requested items in an order (Auftrag), possibly for several customers at once;
  • reserve stock, order missing goods and track backorders;
  • pick and pack the goods (manually, with a picking robot, or through Delivery management);
  • issue delivery notes (Lieferscheine), which are the point at which stock is booked out;
  • print labels, packing lists, pickup slips, backorder slips and prescriptions;
  • create invoices and credit notes, including immediate invoices, VAT-free invoices and cross-branch invoices;
  • dun customers for unpaid invoices (dunning itself is in another chapter).

The module sits under the Sales menu and opens on the order overview. Its tabs are Orders, Delivery notes (hidden unless enabled), Invoices/Credits, and Dunning.

This chapter covers the general Faktura pages, the order lifecycle, delivery notes, collective slips, advance deliveries, backorders, picking, courier delivery from orders, stock-neutral delivery, VAT-free and foreign invoicing, cross-branch invoicing, the pharmacy-as-wholesaler business, hospital (clinic) supply, cross-system stock withdrawal and the clinic-specific reports. Invoice/credit overview details, dunning, Delivery management, Open Items, purchasing, goods receipt, securPharm administration and Reports are separate chapters; this chapter notes where it depends on them.

2. Key concepts and terms​

German termEnglishMeaning
Fakturaback-office invoicingThe module for selling on account: orders, delivery notes, invoices, dunning.
AuftragorderThe central document. A sale transaction for one or more customers holding delivered and undelivered items. Every Faktura process starts with an order.
Auftragsversion (e.g. 234/1)order versionEach edit of an order creates a new version with the same number plus a "/n" suffix; the previous version becomes "superseded".
FakturakasseFaktura tillThe order-editing screen. Same interface and most functions as the point-of-sale till.
ZwischensummesubtotalA block of positions within an order with one customer and one sale type. An order may hold many subtotals and many customers.
Verkaufsartsale typeNormal sale, statutory-insurance prescription, private prescription, "green" prescription, narcotic prescription, care aids. Determines pricing and prescription printing.
Lieferschein (LS)delivery note (DN)Document evidencing that goods were delivered. Created from an order; stock is booked out when it is created.
Stornolieferscheincancellation delivery noteNegative DN produced when an order is cancelled or goods are taken back.
Sammelschein / Sammellieferschein (SL)collective slip / collective delivery noteOne document combining several DNs (or several invoices/credits) of one customer or one care home.
Nachlieferung (NL)backorderQuantity sold but not yet delivered, because it is out of stock or deliberately reserved.
Abholscheinpickup slipCustomer-facing slip for backorder items; its barcode is scanned to resolve the backorder.
Nachlieferscheinbackorder slipAccompanying slip listing what is still to come for a partly delivered order.
Packlistepacking listPharmacy-internal list used to assemble goods for an order.
Packwannepacking tubPhysical container that an order is packed into; it has a number of up to 20 characters.
Kommissioniersystem (KS)picking robotAutomated storage and dispensing system.
Kommissionieren / Auslagernpicking / dispensing (from robot)Assembling the goods of an order, including automatic dispensing from the robot.
Vorablieferung (VA)advance deliveryGoods handed over before a prescription exists. Priced and settled later.
Rezeptschuld / Rezept fehltprescription debt / prescription missingGoods dispensed against a prescription still to be presented.
Sofortrechnungimmediate invoiceInvoice created directly when an order is closed.
Rückkaufauftragreturn (buy-back) orderOrder capturing goods brought back by a customer, needed before a credit note can be issued.
Gutschriftcredit noteNegative invoice.
Lagerneutrale Lieferungstock-neutral deliveryCustomer supply that never touches shelf stock: a dedicated purchase order is placed and the goods go straight out after goods receipt.
Virtuelle Reservierungvirtual reservationReservation that only exists to trigger a dedicated order for stock-neutral delivery.
Warenkorbermittlungsmodellbasket determination modelRule set deciding which supplier a shortfall is ordered from.
Umlagerung / Umlagerungsauftragstock transfer / transfer orderMoving goods between branch or partner pharmacies, handled as an order.
Filialübergreifende Fakturierungcross-branch invoicingOne branch invoices the customers of the other branches and takes over their receivables.
Forderungsübertragreceivable transferHanding a receivable (an order) from one branch to the invoicing branch.
IW (interner Warenverkehr)internal goods exchangeDocument-number prefix for transferred receivables.
Interne Verrechnunginternal settlementNet, VAT-free invoicing between branches of the same company.
Auslandsfakturaforeign / VAT-free invoicingInvoices without VAT to EU businesses, ships and similar recipients.
USt-Ausweisung a.R.VAT display on invoiceCustomer setting that controls how VAT appears on the invoice.
Großhandelspartnerwholesale partnerA company customer that the pharmacy supplies as a wholesaler.
Vereinbartes Sortimentagreed assortmentThe article set agreed with a wholesale or clinic customer through a price scheme.
Sonderanforderung (Kz "S")special requestAn item ordered outside the agreed assortment.
Preisschema / Verwendungsmodellprice scheme / usage modelRules that pick which price list applies in which context and for which customers.
Klinik / Klinikeinheit / Stationclinic / clinic unit / wardA hospital customer and its hierarchical sub-units.
Kostenstellecost centreClinic accounting unit used in reports.
Bündelpackung / Teilpackung / Klinikpackungbundle pack / partial pack / clinic packA hospital-size pack, its individually dispensable sub-packs, and a hospital-only order unit.
Übergreifende Lagerentnahmecross-system stock withdrawalAutomatic withdrawal of shortfalls from a sister warehouse running on a separate system at the same site.
Fakturamodell / FakturierungsmodellFaktura modelA reusable bundle of Faktura settings for a contact (print counts, options, forms).
Eigener EK / Apo-EK / Buchungs-EKown purchase price / list pharmacy purchase price / booking purchase priceAlternative cost bases for pricing.
Wertbuchungvalue bookingPosting the monetary value of a goods receipt.
Botenbon / Botenetikettcourier slip / courier labelPrintouts for courier deliveries.
Laufkundewalk-in customerAnonymous customer whose data are deleted automatically each night.

3. Data model​

3.1 Order (Auftrag)​

  • Identity. An order number is assigned automatically once the order is bindingly confirmed. It is unique and stays constant across versions. The version suffix "/n" is added on each edit, for example 234, then 234/1. Transferred receivables carry the origin-branch abbreviation plus "IW" before the order number. In wholesale-pharmacy mode an external transaction number is also stored.
  • Header fields:
    • customer or customers;
    • creation date, binding-closure date, and an optional manually backdated order/delivery date (all three are kept and shown);
    • clerk, meaning the creator;
    • order type;
    • order status and invoicing status;
    • advance-delivery status, for advance-delivery orders;
    • order total;
    • calculation basis: gross, net, or "gross/net" when both kinds of subtotal are present;
    • courier-delivery flag and delivery conditions;
    • picking state (pending or started) and packing-tub numbers;
    • external transaction number and external order date;
    • info text plus a "designation" search term;
    • opening and closing texts (Anfangs-/Endbeschreibung) printed on its DNs and invoices;
    • any advance payment made at the till.
  • Order types: standard; advance delivery; stock transfer (internal, between pharmacies with the same tax number, or external, with a different tax number); webshop order (captured automatically); receivable transferred from a branch (cross-branch invoicing); clinic order (captured automatically through Klinik.connect or WiSL); home order (captured automatically); receivable transferred from SteriBase; MSV3.connect incoming order; PHBEST order.
  • Subtotals. Each subtotal has one customer, one sale type, and optionally a payer and a doctor (these do not apply to a normal sale). It may be a cancellation subtotal for returns.
  • Positions (General tab):
    • sale-type icon, or a cancelled variant;
    • article and article code (PZN, 7 digits);
    • dosage form and unit;
    • quantity (negative means a cancellation or return);
    • settled quantity (advance deliveries only);
    • backorder quantity (NL);
    • standard retail price (or a reference price if one exists);
    • customer price, which is the amount actually payable for the whole position including discounts;
    • total price;
    • VAT rate class (full, reduced or none);
    • flags for "substitute delivered" (naming the delivered article), position note printed on DN/invoice, split-priced, split-dispensed, blistered and split-blistered;
    • the customer the position is assigned to.
  • Supply view per position (Belieferung tab):
    • supplier and ordered quantity;
    • quantity not yet delivered;
    • quantity passed to purchasing as a shortfall;
    • purchase order status: open, sent, not deliverable (defect), open return, returned, scheduled, in backorder order, or in dispo order;
    • in-stock quantity available for packing or a DN, which comes from goods receipt or from a non-delivered stock reservation;
    • assigned packs (batch, expiry, quantity);
    • a warning when goods receipt booked a substitute article, which means the order needs post-processing.
    • Cancelled positions are highlighted.
  • Cross-system withdrawal data. For each article: the quantity requested from the sister pharmacy and the quantity actually withdrawn.
  • History. Every operation is logged with operation type, clerk, date and time, and a remark, oldest first. Printing an order is also logged.

Order status (Auftragsstatus)

StatusMeaning
Vorerfasst (pre-captured / draft)Saved with "continue later", or created automatically from an external channel. Not binding. No reservation, no purchase order. Only status in which an order can be deleted.
Auf Lager (in stock)Binding. All backorder quantities are in stock, because the ordered goods have been booked in goods receipt. Special positions (compounded preparations, generic or free items) and fees always count as in stock.
Teilw. auf Lager (partly in stock)Binding. Some backorder quantity is in stock and some is still on order.
In Bestellung (on order)Binding. No backorder quantity is in stock yet. Covers both "nothing delivered yet" and "stock items already delivered on a DN, backorder items still on order".
Geliefert (delivered)Confirmed, and every position's full quantity is on a delivery note.
Übertragen (superseded)An older version replaced by an edited version. Shown greyed and italic.
Storniert (cancelled)Cancelled. Shown greyed and italic.
Aktuell in Bearbeitung (currently being edited)Locked by a user. Others cannot edit it.
Erstellt (created)Appears when an immediate invoice could not be produced because no SEPA mandate was stored. The order is created and waits. Not otherwise defined in the source.

Default sort order: pre-captured, in stock, partly in stock, on order, delivered, superseded, cancelled, being edited; then creation date, newest first. Advance-delivery orders are shown in a distinct colour, and fully delivered and settled ones are additionally in italics.

Invoicing status: not invoiced (also set when a branch receivable transfer was cancelled), partly invoiced, fully invoiced. An advance-delivery order has no invoicing status.

Advance-delivery status: not settled, partly settled, fully settled.

3.2 Delivery note (Lieferschein)​

  • Fields:
    • recipient customer (or the deviating delivery recipient);
    • delivery date, which is the DN creation date;
    • document number (internal DNs, for example for webshop mail order, are numbered "I/xx"; collective DNs have the prefix "SL");
    • document kind: delivery note, collective delivery note, or cancellation delivery note;
    • order type of the source order;
    • advance-delivery flag and stock-transfer flag;
    • printed flag and courier flag;
    • status;
    • total, currency, calculation basis (gross/net) and assigned print form;
    • source order number (plain DNs only);
    • packing-tub numbers;
    • external order number;
    • positions, structured as on the order. Return positions are highlighted.
  • DN status: Erstellt (created), Fakturiert (invoiced: its invoice exists), Storniert (cancelled: the underlying order was cancelled).
  • A DN can be the original or a reprinted copy marked "KOPIE".
  • Every edit of an order that creates DNs issues new DNs with a new number and the current date.

3.3 Collective slip (Sammelschein)​

  • Has one recipient: a customer, a home, or a separately billed home unit.
  • Contains a set of DNs, or a set of invoices/credits.
  • Holds a single calculation type (gross or net).
  • Each DN records whether it has already been included in a collective slip (column "SL").
  • A collective DN can carry its own courier flag. Its contained DNs then lose their own courier flags and are removed from any tour assignment.

3.4 Invoice / credit (as seen from an order)​

Fields: addressee; date (the creation date while being processed, otherwise the document date); due date; number; kind (invoice or credit); direct-debit flag; printed flag; cash-discount price (the total minus cash discount, using the discount valid at the last payment date if payments exist, and blank once the discount period has expired); total; paid; open (cash-discount price minus payments).

Status values:

  • In Bearbeitung (in processing)
  • Erstellt (created)
  • Teilbezahlt (partly paid)
  • Bezahlt (paid)
  • Storniert (cancelled)
  • In Mahnung (in dunning)
  • Freigabe zur Mahnung (released for dunning)
  • Forderungsausfall (bad debt)
  • Intern (internal)
  • Übertragen (transferred)

3.5 Receivable transfer (cross-branch)​

An order in the invoicing pharmacy that represents a receivable taken over from another branch. Its document number has the "IW" prefix. Its status follows the invoicing statuses, plus a transient "In Stornierung" (cancellation in progress) until the cancellation reaches the origin branch. Each one links to the customer invoice and to the pharmacy-internal invoice.

3.6 Advance delivery​

An advance-delivery order holds per customer the advance-delivered items with delivered and settled quantities. A separate settlement order cross-references the original. The original survives if the settlement is cancelled.

3.7 Customer / contact data used by Faktura (owned by Contacts)​

  • Faktura settings (contact > payment page). These are required before an order can be created.
  • Address data. Mandatory for invoicing.
  • Contact role: person, company, home, home unit, clinic, ward/unit, doctor, employee, branch or partner pharmacy.
  • Billing and print options:
    • billing mode, for example immediate invoice;
    • number of DNs, number of backorder slips and number of labels;
    • label printing on or off;
    • assigned print forms;
    • an assigned Faktura model.
  • Delivery data: stored delivery addresses; preferred tour; preferred delivery type (for clinic units).
  • Flags:
    • "stock-neutral delivery";
    • "separate statistics";
    • "wholesale partner" (which auto-enables "cooperation partner", "batch documentation for medicines" and "stock-neutral delivery");
    • "settlement from internal goods exchange".
  • Pricing and tax:
    • VAT display on invoice: net unit prices; VAT-free EU business; VAT-exempt seagoing ship; VAT-free for other reasons;
    • VAT ID with its verification status;
    • price scheme assignment;
    • discount model or instant discount.
  • Interfaces and robot:
    • e-data-exchange (EDI) partner;
    • MSV3.connect or Klinik.connect access data;
    • robot output chute.
  • Clinic structure: units and wards with their own master data, invoicing defaults, contact persons, delivery agreements (including "separate delivery") and price scheme.
  • Customer mapping. Remembered mapping between SteriBase invoice recipients and IXOS customers.
  • Customer classification and group: home, doctor, employee, other.

3.8 Articles (owned by Article administration), as used here​

  • Agreed-assortment membership via a price scheme, which can carry a date, time or customer reference.
  • Bundle pack / partial pack / clinic pack relations, plus the number of partial packs.
  • Own purchase price, list purchase price and booking purchase price.
  • securPharm verification obligation.
  • ATC code (German and WHO).
  • Active substances.

4. Features​

4.1 Order overview [GENERIC]​

  • Purpose. Central worklist of all Faktura orders. It is the start screen of the module.
  • What it shows:
    • Active filter. The full criteria are available on hover.
    • Staleness indicator. It turns on when another workstation or an automatic process created, edited, cancelled or deleted an order since the list was loaded. The list is deliberately not refreshed automatically, so it does not jump under the user; refreshing is manual.
    • Unfinished orders. A marker shows when there are orders in "currently being edited" status. Optionally, a reminder task in the Notes module flags open orders (system parameter under Sales > Faktura > "general sales").
    • Columns:
      • multi-customer marker;
      • customer (all customers if there are several; the customer may belong to another branch under cross-branch invoicing);
      • date (creation day, with the sequence of state changes and their dates on hover);
      • document number;
      • order-type marker;
      • clerk;
      • order status and invoicing status;
      • total;
      • info marker (note present, Connect data, free-text positions done or not done).
    • Detail area: calculation basis; any advance payment taken at the till; and position and supply tabs (see 3.1).
  • Functions:
    • search/filter, new, delete (pre-captured only), edit, cancel;
    • resolve backorder (or scan a pickup slip directly);
    • details, print, customer info / customer info at a glance;
    • pick goods, create delivery notes, create complete DNs, order with date, create collective DN slip;
    • info text, print settings (per workstation, print form and printer), history.
  • Create complete DNs (Vollständige LS erstellen). Creates DNs only for those customers (subtotals) whose items are all completely in stock.

4.2 Order filters [GENERIC]​

  • Shipped filter "IXOS" (it cannot be renamed, deleted or edited). Shows pre-captured, in-stock, partly-in-stock and on-order orders, plus orders that are not or only partly invoiced, plus advance deliveries not or only partly settled. Hides superseded and cancelled orders, orders that are delivered and fully invoiced, and fully settled advance deliveries.
  • Criteria:
    • saved filter;
    • customer (search includes inactive and deceased contacts);
    • customer group: home, doctor, employee, other ("other" means every contact that is neither home, doctor nor employee);
    • customer classification (classifications defined for "all" contact types are ignored);
    • order number;
    • external transaction number (prefilled for webshop orders, or entered manually, for example for EDI clinic orders);
    • date range and total range;
    • picking: started or pending;
    • packing-tub number (prefix match, up to 20 characters, no leading wildcard);
    • article contained;
    • supplier/manufacturer;
    • order type: all; advance only; external transfers; internal transfers; all transfers; transferred branch receivables; webshop (licence); MSV3 (licence); PHBEST; automatically created clinic orders; automatically created home orders;
    • DN number (finds the order that produced the DN);
    • statuses: order statuses, invoicing statuses, advance-delivery statuses.
  • Logic.
    • All non-status criteria are combined with AND, and the result is ANDed with the status result.
    • Within one status kind, the ticked values are ORed.
    • Between order status and invoicing/advance status, the user chooses AND or OR (default OR).
  • Persistence.
    • An unsaved change lasts until Faktura is closed. Fields that differ from the saved filter are highlighted, and a "clear" action reverts them.
    • Saving stores a name plus the column sort. The primary sort is the clicked column; after it comes the default order: order status, invoicing status, date, document number. Saving under an existing name asks whether to replace it or save as new.
    • Filters can be reordered, renamed, deleted (with confirmation) and edited, and one can be set as the default applied when the overview opens.
  • Recommended saved filters:
    • research (everything);
    • pre-captured (used for transfer orders not created automatically and for incoming clinic orders);
    • still to deliver (in stock, partly in stock, on order);
    • fully deliverable, so create a DN (in stock);
    • still to invoice (delivered AND not or partly invoiced);
    • open advance deliveries (advance type with status not or partly settled).

4.3 Create and edit an order (Faktura till) [GENERIC]​

  • Trigger. "New" in the order overview.
  • Where orders are edited. In the Faktura till, which offers the till's functions plus Faktura-specific ones.
  • Inputs and validations:
    • A customer is mandatory. No subtotal can exist without a customer.
    • Invoicing needs complete address data. If they are missing, the user must complete them or abort. The contact's Faktura settings can be adjusted on the spot.
    • The starting sale type comes from the configuration parameter "default sale type".
  • Customer and subtotal handling:
    • Add another customer, create a new customer, open a new subtotal for another customer, and view or edit contact details. Customer capture offers suggestions as the user types.
    • Add a new subtotal with the same or a different sale type, or change the sale type of the current subtotal at any time.
  • Closing options:
    1. Continue later. Saved as pre-captured; nothing reserved, nothing ordered. Later, "create order" confirms it bindingly without printing a DN, packing list or pickup slip. Alternatively, "edit" continues editing and the user may then create DNs.
    2. Create delivery notes.
      • DNs are created and printed. The format (A4 or receipt roll) is set per workstation; the default is A4.
      • A reminder slip for missing prescriptions prints if configured.
      • For backorder quantities, a pickup slip and a packing list are printed. Their counts and format are configurable.
      • Every prescription subtotal opens the prescription-print window.
    3. Create without DN. The sale is closed bindingly without DNs, and a packing list of all articles is printed. Used to reserve the whole sale.
    4. Immediate invoice. See 4.8.
  • Resulting status:
    • pre-captured (option 1);
    • on order or partly in stock if backorders exist (pickup slip and packing list are printed);
    • in stock once all backorder items have been booked in goods receipt;
    • delivered if everything went onto DNs.
  • Effects on stock:
    • While a new order is open, each position is reserved temporarily.
    • "Continue later" releases that reservation.
    • Binding closure, through either "create DNs" or "create without DN", reserves every position, orders missing items and sets backorders.
    • Stock is booked out only when a DN is created. A picking robot dispenses only at DN creation.
  • Editing an existing order:
    • It reopens in the Faktura till.
    • Saving creates a new version, and the old version becomes superseded.
    • Finishing with "create DNs" produces new DNs with a new number and the current date, even for a mere quantity change.
    • The creation date is kept. The date tooltip shows the creation date, the binding-closure date and any manual backdating.
    • The advance-delivery flag cannot be set or removed later.
    • A pre-captured order can again be saved with "continue later".
    • Two users cannot edit the same order at once; the second gets a message.
    • If parts are already being delivered by courier through Delivery management, only parts whose DN has not yet been handed to the courier can change (with a warning).
  • Walk-in customers. An order for a walk-in customer must be closed with an immediate invoice. Walk-in data are deleted every night for data protection, so a later invoice would be impossible.
  • Narcotics in a normal sale. Allowed in Faktura when the customer is a company, doctor, home or clinic (for example, a clinic presenting a requisition form instead of a prescription). The system asks whether to remove the narcotic from the normal sale; the user answers No. This prompt is not shown for clinic customers. Not available at the counter till.
  • Shortfall correction. The "basket" function changes the quantity ordered from suppliers (more or less than the computed backorder) and the supplier, for backorder and stock items.
  • Line-by-line review. For orders captured externally that arrive as pre-captured (transfer orders, Connect clinic or home orders), staff check each position before confirming. Navigation jumps between the editable fields of each line (quantity, or the text of a cash or fee position).

4.4 Faktura till functions [GENERIC unless noted]​

  • Basic editing:
    • Save (only while the order is being edited).
    • Article search, advanced search, and comparable-article search.
    • Delete a position, a subtotal or a whole new order (with confirmation; an empty new order is discarded silently).
    • Change a position, for example co-payment or extra costs.
  • Prescription-related:
    • Mark "aut idem" exclusion: the prescriber excluded substitution. Prescription sales only.
    • Change the payer or doctor of a subtotal (not for normal sales).
    • Prescription debt: pulls advance deliveries and missing-prescription items into the current order for settlement.
  • Quantities and packs:
    • Basket: edit ordered quantities and suppliers.
    • Splitting (Stückelung): split a pack. Not allowed for orders originating from a transfer.
    • Pack info: capture batch and expiry for packs not subject to securPharm verification.
  • Clinical checks:
    • Article information database.
    • Risk check: problem documentation, interactions, and contraindication (CAVE) check when a customer is assigned.
  • Pricing:
    • Discount or surcharge per article, as a percentage or an absolute amount. Not for prescription sale types.
    • Price info: explains how a price was calculated.
    • Current prices: price update, see 4.12.
  • Order handling:
    • Advance-delivery mode on or off.
    • Create DNs: DNs are generated per customer, calculation type and document kind; if not everything is in stock, only deliverable quantities are used.
    • Create without DN; immediate invoice.
    • Cancellation/return.
    • Change sale type (no new subtotal); new subtotal with a chosen sale type.
  • Data, texts and lookups:
    • External transaction data: external number and order date.
    • Compounded formulas: take a formula into the order.
    • Online availability query at wholesalers with ordering.
    • Insert texts: header and/or footer text stored with the order and printed on its DNs.

4.5 Backdated order [GENERIC]​

  • Purpose. Record goods that were already handed over, so they can be invoiced for the month of delivery.
  • Flow. Choose "order with date", then the contact, then enter an order/delivery date, which must lie in the past. The Faktura till opens.
  • Rules:
    • Prescriptions captured in the order print with that date.
    • Prices and discount contracts are still taken as of today, so the user must adjust them by hand to those valid on the backdated date.
    • Dates before 1 July 2020 are rejected. That was the date of a temporary German VAT-rate change, so this is a system cut-off.

4.6 Order from file [GENERIC]​

  • Purpose. Import a CSV/TXT file of article codes and quantities (for example a webshop export) as an order for one customer.
  • Licence. Requires the paid "Faktura Profi" licence.
  • Restriction. Only for customers set up as wholesale partner or branch/partner pharmacy, because prescription and non-prescription items alike land in one normal-sale subtotal.
  • Flow. Choose or create the customer, choose the file, create the order. If no customer is chosen or the file is bad, an error is shown.
  • Behaviour. The import itself neither reserves nor orders anything. The order gets an info marker stating it came from a file import, and the user can add their own info.

4.7 Reserve a whole Faktura sale [GENERIC]​

  • Purpose. Mark a complete sale as backorder regardless of stock, so the full quantity is held for later pickup or delivery.
  • Typical cases: courier delivery; a prescription dropped in the letterbox; a phone order picked up later.
  • Trigger. "Create without DN", applied to the whole sale including all subtotals.
  • Effects:
    • the order is listed;
    • a pickup slip is printed;
    • no DNs are created;
    • all captured quantity except cash-sale positions becomes backorder quantity;
    • missing quantities are ordered.
  • Use for full reservation. Also used for stock-keeping setups in which every position's backorder quantity must equal the sale quantity.
  • Till sales. A till sale with reserved items may also be closed with payment type Faktura or immediate invoice.
  • Workstation parameter. "Order closure prefers 'create without DN'" swaps the default closing button. With it, the default reserves everything, creates no DN and prints the complete packing list. The alternative button creates a DN when everything is in stock. For clinic packing lists, this parameter also means the DN is created only once all ordered articles are in stock.
  • Resolving a reserved order. Recommended: "resolve backorder", which goes to the Open Items backorders tab, then "take over", then the resolve dialog. Alternatively "create delivery notes", following the rules in 4.9.

4.8 Immediate invoice (Sofortrechnung) [GENERIC]​

  • Trigger. A function in the Faktura till after capturing items. Also the customer billing mode "immediate invoice", in which case the invoice prints together with the DN.
  • Prerequisite. The order must not originate from a stock transfer.
  • Rule. If a SEPA direct-debit mandate is stored, the invoice is generated at once. Otherwise the order is created and appears in the overview with status "created".
  • Effects:
    • prescriptions are printed for prescription subtotals;
    • DNs are generated automatically for the available quantities but not printed;
    • the invoice is generated and printed over all items in the quantity to invoice;
    • if not everything is in stock, the user decides whether the invoice covers only the deliverable items or all items.
  • Texts. Opening and closing texts matter for VAT-free invoices "for other reasons", where the reason must be printed. Two parameters apply, both off by default:
    • "show invoice total at immediate invoice" (workstation scope) opens the invoice-total dialog, where the texts can be typed;
    • "take order texts into immediate invoice" (system-wide) carries over the texts entered in the order.
    • With both on, the order's text is shown pre-filled and can be edited.
  • Without the VAT-free licence. An immediate invoice from the till shows a notice in the invoice total, and a delivery note is created instead.

4.9 Creating delivery notes [GENERIC]​

  • Rules by order status:
    • All backorders in stock (status "in stock"): a full DN is created immediately without a prompt, offered for printing, and the backorders are resolved.
    • Partly in stock: the user chooses DNs only for the in-stock backorder items, or for all backorder items. Creating the DN resolves the backorders for the items printed.
    • None in stock (on order): the user chooses whether to create DNs for all items, which resolves the backorder, or not.
  • Contents of a DN:
    • Only articles actually in stock appear. Backorder items never appear on a DN; they are on the backorder slip or pickup slip.
    • Prices are shown or hidden according to the print-form configuration.
    • Settlements of advance deliveries do not appear.
    • A sale-type letter column "Kz" shows G (green prescription), P (private prescription), R (statutory-insurance prescription) or blank (normal sale).
    • Order number, packing-tub numbers, external order number and opening/closing texts are printed where applicable.
  • Printing. The number of DNs printed automatically comes from the customer's print options or Faktura model. If automatic printing is off, the user prints manually from the order or DN overview.
  • Invoice without delivery. An invoice created over items not yet delivered carries no DN number and no delivery date.
  • Backorder slip (Nachlieferschein).
    • Prints right after the DN when an order is bindingly closed but not fully delivered. It lists the backorders of partly delivered positions and all undelivered positions.
    • It refers to the order number, which is then also printed on the DN (standard form only).
    • The count is set per customer, or per clinic in the clinic structure; the default is none. It can be reprinted on A4 from the order overview or sales administration.
    • When backorder slips are used, the print-form option "do not print notes on backorders" can suppress the DN's own backorder hints, which print by default.
  • Substitute articles.
    • If goods receipt booked a substitute for an ordered item, the order shows a warning. At DN creation the user chooses whether to adopt the substitute or print the DN with the ordered article.
    • Adopting it opens a "substitute delivered" window, which notes that no substitution check against discount contracts is done for the substitute. For statutory prescriptions the pharmacist must check this manually (German social-code rule).
    • The substitute is taken into the sale and onto the DN.
  • Labels. If labels were not yet printed automatically, they print when backorders are resolved.

4.10 Resolving backorders [GENERIC]​

  • Trigger. "Resolve backorder" in the order overview, scanning the pickup-slip barcode, or the till's pickup resolution.
  • Where. The Open Items module, backorders tab. It is pre-filtered by the order's pickup number; with a delivered order selected, it shows all Faktura orders.
  • Constraints:
    • Backorders of an already invoiced order cannot be resolved. The invoice must be discarded first.
    • A Faktura pickup can also be resolved at the counter till.
  • Dialog. The pickup slip is always resolved, combined with either (A) create DN or (B) open the order for editing.
Order statusOption A (create DN)Option B (edit order)
On orderPickup slip resolved and DN created, even though goods are not yet booked in.Order opens with the backorder quantities removed.
In stockResolved and DN created.Order opens.
Partly in stock, "only available quantities" (default)DN for the available quantities; quantities still on order stay; status changes to "on order".Order opens; ordered backorder quantities stay; DN only for available quantities.
Partly in stock, "all backorder quantities"DN for everything, including items still on order without stock.Order opens with all backorders resolved, then DN for all.
  • Scan shortcut. Scanning the pickup-slip barcode in the Faktura order overview, in the till sale window, in the till pickup resolution, or in sales administration when editing or cancelling a sale finds the backorder and opens the resolve dialog directly.
  • With prescription debt. When printing a prescription from Faktura for a sale that contains (or contained) a backorder and was flagged "prescription missing", the user chooses between:
    • editing the transaction at the till: the missing-prescription flag is removed (and can be set again), and a special code must be set if prices or discount contracts change; or
    • printing the prescription: the print window is flagged "missing prescription".
  • Substitute delivered. The Open Items detail shows a warning, and the user must choose "resolve pickup and edit order". From there the rules in 4.9 apply.

4.11 Delivery-note correction and partial deliveries [GENERIC]​

  • Purpose. The wholesaler delivered only part of a backorder. The pharmacy delivers that part now and the rest later.
  • First partial DN. Preferred route: edit the order (or "resolve pickup slip and edit order"). In the basket/backorder window, enter as shortfall the quantity that cannot be delivered. The backorder and dispensed quantities adjust. Then create DNs: the DN covers the quantity being dispensed and the remaining backorder is listed. Repeat this for each further partial delivery.
  • Remainder. Preferred: "resolve pickup slip and create DN". Alternatively edit the order, set the shortfall to 0 and create DNs.
  • Batch-documentation rule. When batch documentation is active, and always for transfer orders between branch or partner pharmacies, the remainder does not get its own DN. Instead a DN over the complete quantity with all batch details is issued, so the batch trail is seamless. The earlier partial DNs become obsolete.

4.12 Price update (current prices) [GENERIC]​

  • Trigger. "Current prices" in the Faktura till while editing an order.
  • Prerequisite. The customer is a wholesale partner or a clinic, or the pharmacy works in a branch/partner network.
  • Purpose. Goods are bought from the wholesaler on favourable terms, so the customer is billed at the latest purchase-based prices. For example, a branch order initially carries the prices of the last delivery, and when new goods arrive at new prices, the order is updated.
  • Effect:
    • All positions are repriced from goods-receipt prices, regardless of partial delivery and regardless of stock. Only the not-yet-invoiced quantity is affected.
    • DNs already created are cancelled and re-created at the current prices. Because invoices are based on current DNs, the invoice shows the updated prices.
  • Best practice when in-stock goods should be billed at the old prices:
    1. Create DNs for the in-stock items at capture and invoice them immediately.
    2. After goods receipt of the backorder items, edit the order, update prices, resolve the backorder, create a DN for those items and invoice them.

4.13 Cancel an order; return (buy-back) order [GENERIC]​

  • Cancel.
    • Allowed only if the order is not partly or fully invoiced.
    • Existing DNs automatically get cancellation DNs.
    • Delete is a different action: it is possible only for pre-captured orders, both own and transfer orders.
  • Return order.
    • Purpose. Capture unused items a Faktura customer brings back, without reference to the original sale. It is the prerequisite for a credit note.
    • Flow:
      1. Create a new order and choose the customer.
      2. Choose cancellation/return and pick the return type (same choices as the sale types). A cancellation subtotal opens.
      3. Capture the items. The "to dispense" quantity is negative, for example quantity 1 and to dispense −1.
      4. Create DN. A cancellation DN is produced and offered for printing.
    • Afterwards. The order appears in the order overview, and the cancellation DN can be found in the DN overview. The credit note is then created in the Invoices/Credits overview (covered in another chapter).

4.14 Advance delivery (Vorablieferung) [GENERIC idea; motivated by DE prescription practice]​

  • Purpose. Hand over goods, typically prescription-only items, before a prescription exists, when the billing route and therefore the price are not yet known.
    • Classic case: supplying a doctor's practice with practice stock for a quarter and later receiving the practice-supply prescriptions (Sprechstundenbedarf). Care homes are another case.
    • Discount agreements are checked both at capture and at settlement. Pricing happens at settlement.
    • Not for non-prescription goods, whose price is fixed; use a normal DN or a credit instead.
    • Not when the specific patient's insurance is known or a faxed prescription exists; use "prescription missing" instead.
  • Create:
    1. New order, then choose the customer and the sale type if known (else normal).
    2. Turn on advance-delivery mode.
    3. Capture the items and create DNs. The DNs are printed and stock is booked out at that point.
    • One order may hold advance deliveries for several customers, but advance and non-advance items cannot be mixed in one order.
    • Blocked in advance mode: cancellation/return; printing prescriptions after the subtotal or total; resolving pickup or credit slips; cash sales; fees (these are added at settlement). If items were captured before the mode was switched on, disallowed actions are removed from the total after a warning and confirmation.
  • Edit:
    • Possible while not all of the order's advance deliveries are settled. The advance flag cannot be removed.
    • The order reopens in the till. Reducing unsettled positions to quantity 0 cancels them, and the changes are applied by creating DNs.
    • Reachable from the order overview or Open Items > advance-deliveries tab.
  • Find. Fully settled advance orders are hidden by default. Use order type "advance only" with status "all", optionally narrowed by customer.
  • Settle. Done at the till or Faktura till through "prescription debt", or more comfortably from Open Items.
    • A new order is created for the settlement. The original and the settlement order cross-reference each other.
    • Steps:
      1. Create the new order, choose the customer and the sale type.
      2. Open the list of the customer's advance deliveries and choose items.
      3. Enter the quantity "to settle". By default it is distributed over the original subtotals, oldest first; it can also be entered per subtotal.
      4. Take over. The packs enter the order and pricing runs, for example the prescription markup calculation and narcotic fees.
    • Sale type. The current order's sale type is used. Exception: if the current order is a normal sale and the advance delivery was captured with a prescription status, that prescription status and payer are taken from the advance delivery.
    • Delivery notes. Further items may be added. Creating DNs produces DNs only for the newly added items, because advance items already had their DN. A prescription print preview is offered.
    • Result. Status "delivered", ready for invoicing. No stock is booked at settlement.
    • Multi-selection. Several items can be selected at once, except advance-delivered compounded preparations.
    • Preset quantity. Pre-entering a quantity (for example 25) before opening the list proposes that quantity for every article, capped at the delivered quantity. A quantity larger than the advance quantity settles the advance fully and takes the rest from stock; a field shows how many packs come from the advance delivery. Example: a home normally gets 200 packs per week and 50 were advanced; settling 200 takes 50 from the advance and 150 from stock.
    • Preset article name. Pre-entering an article name positions the cursor on that article.
  • Cancel the settlement. Cancelling the settlement order makes the original advance order visible again; it is not deleted. To cancel the original, cancel it directly.
  • Invoice date rule. The advance-delivery date is carried onto the invoice only if the recipient of the advance delivery is also the recipient of the settlement (for example, the practice with its practice-supply prescription). If the settlement goes to another customer (for example, a patient who brings the prescription), the settlement date is printed.

4.15 Order details [GENERIC]​

The order details window has four sections: order, delivery notes, invoices, and cross-system withdrawal.

  • Order:
    • Header: customer, date, number (with the external number on hover for wholesale pharmacies), type, clerk, status, courier flag and total.
    • Positions: sale type, article, code, dosage form, unit, quantity (for advance deliveries, the quantity not yet settled) and customer.
    • Detail area: for example, the documents in which advance deliveries were settled.
    • Functions: print; open Sales administration for the original and settlement transactions; toggle courier delivery.
  • Delivery notes. All DNs of the order with the fields in 3.2. Courier delivery can be toggled per DN until the tour has been handed to the courier.
  • Invoices. All invoices and credits of the order with the fields and statuses in 3.4.
  • Cross-system withdrawal. Per article, the quantity requested from the sister pharmacy and the quantity withdrawn.

4.16 Order information and notes [GENERIC]​

  • What can carry it. Every order, cost estimate (Kostenvoranschlag) and quote (Angebot) can carry a free info text plus a "designation" search term. A marker shows that one exists.
  • Where to open it. From the overview or from inside the open order.
  • Created automatically for: file import; cross-branch sales; webshop orders with a customer note; cross-system stock withdrawal.
  • Clinic and shop orders. Orders from Klinik.connect or MediShop get a distinct info marker with two tabs:
    • Note: the notes the clinic transmitted;
    • Connect data: article data, approval data, and the approver's phone number if it was entered.
  • Follow-on searches. From the info window the user can run an article search, active-substance search, compounded-formula search or parenteral-formula search, using the designation as the search term (or a wildcard). A selected hit is taken into the order. This is how clinic free-text positions are turned into real articles; the overview's "free-text positions done/not done" marker tracks progress.

4.17 Picking goods for an order (with or without robot) [GENERIC]​

  • Purpose. Start and track the physical assembly of an order's goods.
  • When it is available. For all orders except pre-captured and delivered ones.
  • Without a robot:
    • Print a packing list and optionally record packing-tub numbers.
    • Assigned tub number is printed on the current DN.
    • Further tub numbers are entered manually: up to 20 characters, or several comma-separated values totalling 20 characters. They print on the next DN.
    • The "print packing list" checkbox defaults from a configuration parameter.
    • Confirming prints the list with the tub number. The order then counts as "picking started", which the order filter can select (for example a saved filter "to pack").
  • With a robot:
    • What it does. Packs held in the robot are dispensed automatically, and an optional packing list covers the rest. This suits large orders, clinic and home supply, and transfers between branch or partner pharmacies.
    • What the robot automates. It handles batch documentation, and over the WWKS2 protocol it handles securPharm verification and deactivation.
    • Tub numbers from the robot. Some robots have a tub system at the output chute and report the tub number over WWKS2, where it is stored.
    • Window contents: order number, customers, output chute (default per customer from the contact's "robot output chute"), robot tub number (manual or reported), manual tub number (used for the subsequent DN of manually picked goods), and "print packing list". The list shows article, requested quantity, dispensed quantity and tub.
    • Dispensing. "Start dispensing" checks availability in the robot and lowers the requested quantity if the robot cannot supply all of it. Then "create delivery note" creates a DN over all dispensed articles. That DN contains only robot goods, so its tub can be finished at once.
    • Continue automatically. A workstation parameter ("continue automatically", robot page) creates the DN without a prompt and returns to the overview.
    • Reset dispensing. Resets the order-side record of dispensing. A running robot job can be stopped only if the robot supports this over WWKS2. Any items already dispensed must be put back into stock as returns.
    • Status markers: dispensed OK, or queued.
    • When dispensing is refused. The order has no robot items, everything available has already been dispensed, or the items are no longer in the robot. The source also lists the statuses "partly in stock", "on order" and "in stock" here, which contradicts the general availability rule (see Open questions). In these cases a message offers to print the packing list instead.
    • Recommended robot settings. "Use WWKS2 pack information for securPharm" set to "always" or "only items without documentation duty", and "dispense on scan" off. Without these, manual counter-scanning is needed.
  • Tub numbers on printouts. They print only on the vendor's standard A4 DN and A4 packing-list forms, not on customised forms. Robot and manual tub numbers appear comma-separated. The order overview can search by tub-number prefix, and the order detail shows the tub number.
  • Recommended flow for large orders:
    1. Close the order without a DN and without a packing list.
    2. Dispense from the robot, which produces a DN for the robot goods plus a packing list for the rest.
    3. Pack the rest manually from the list.
    4. Add the goods that arrive from the supplier.
    5. Print a DN for the manually packed and ordered goods, then check and scan.
    6. Deliver.
  • Clinic variant "dispense order" (Auftrag auslagern). Used only when Delivery management is not in use. It is the same function reached from the order overview. The dialog allows changing the chute, entering a tub number, and enabling a packing list for the items not dispensed. After dispensing, a delivery list containing only the dispensed items is produced, so that tub needs no further checks.

4.18 Courier delivery of Faktura orders [GENERIC]​

  • Ways to flag a delivery:
    1. The whole sale in the Faktura till ("as delivery/courier").
    2. In order details, for the order or for individual DNs.
    3. When compiling a collective DN.
    4. Automatically, when a home resident with a preferred tour buys stock items at the till and the sale is closed with "Faktura".
    5. Per DN in the DN overview.
  • Delivery conditions dialog:
    • Delivery time: none; "from" a date and time; or "until" a date and time (latest delivery). The desired date adjusts the tour suggestion, is printed on the pickup slip, and tells goods-receipt staff whether a later supplier delivery is still acceptable.
    • Notification:
      • automatic SMS or e-mail for "expected arrival" and for "customer not met" (German mobile numbers only); or
      • "call customer", choosing among the stored numbers or another person's name and number.
      • The numbers appear in the courier's digital delivery list.
    • Address:
      • The customer's standard or stored delivery address (that of the first or only subtotal), or a deviating address for this delivery: another subtotal's customer, another stored delivery address, a contact chosen by browsing, or manual entry.
      • Delivery addresses must be stored in Contacts. The list is empty for an unsaved customer.
      • For home residents, the home's address is offered first, as a deviating address.
      • The address is printed on the courier slip.
    • Plan for tour: only for courier delivery of backorder items with the Delivery management module. Tours are suggested automatically or picked by hand. Tours past their preparation time are shown dimmed but can still be chosen.
    • Free text: shown in the digital delivery list when the tour is called up.
    • Multi-customer sales. With two subtotals for two different customers, no notification is offered and a deviating address must be chosen to pick the right customer's address. If a home customer is included, the deviating-address option is preselected.
  • Effect of flagging:
    • Flagging an order flags its header, and every DN subsequently created for the order is flagged "by courier" and offered in the delivery list.
    • If there are no backorder items, the DN already exists, so the flag is set on the DN instead.
    • Flagged DNs appear in Delivery management.
  • Locking. Once a tour has been handed to the courier, its conditions cannot change.
  • Removing the flag. Possible only before the handover: choose "do not deliver" in the conditions dialog, or remove it in Delivery management.
  • Collective DN by courier. Tick "deliver collective DN by courier" when selecting documents. The whole collective DN is flagged regardless of its contents. The conditions dialog opens, and the collective DN and courier label print. The contained DNs lose their courier flags and are removed from any tour assignment.
  • Home residents at the till:
    • A home resident with a preferred tour buys stock items and the sale is closed with "Faktura": the conditions dialog opens by default with the home address. "Do not deliver" hands the goods over directly with no delivery created.
    • If backorder items are captured for a home customer, a pickup/delivery dialog appears at the total.
    • A resident with no preferred tour gets a normal order, which can be flagged later.
    • Faktura customers who are not home residents never get an automatic delivery.
  • Mobile tour optimisation. The tour is optimised on the courier's tablet by a separate mobile delivery app, which needs the contact data to be complete.

4.19 Stock-neutral delivery (Lagerneutrale Lieferung) [GENERIC]​

  • Purpose. Supply certain customers (typically care homes and their residents) without touching shelf stock. A dedicated purchase order is placed, and the goods go straight out after goods receipt. Walk-in customers are then always served from full shelves, and no reservations block stock.
  • Configuration:
    • Contact flag. "Stock-neutral delivery" in the contact's specific data. For a home it applies to all of its residents.
    • Separate statistics. These sales are left out of the normal sales statistics and recorded in separate statistics automatically, regardless of the contact's "separate statistics" option.
    • Basket determination model. For the chosen customer circle (for example active home residents), backorder items are ordered from a virtual supplier. Before real ordering, the basket is rebooked to a real supplier.
  • Behaviour:
    • The flag applies automatically to the whole sale or order at the till and in the Faktura till, where an indicator shows it.
    • No explicit reservation is made and no order or pickup slips are printed. Instead a "virtual reservation" triggers the dedicated purchase order. Partial quantities can be processed.
    • At the till: payment type Faktura is preselected at the total; closing offers prescription printing and creates an order; no pickup slip.
    • In Faktura: the closing defaults are swapped, so "create without DN" becomes the default, because the DN is created automatically at goods receipt and offered for printing. The user may decline printing and instead make collective DNs for all orders of the home.
    • Sales administration shows the flag.
    • Article administration. These sales appear under "other" and are excluded from order-quantity optimisation. Stock control creates a basket position at sale time, so optimisation sees no further stock need. Closing in Faktura makes a virtual reservation of one pack; the source states this without explaining it.
    • Purchasing. Create the virtual baskets via the model, rebook them to a real supplier, and order.
    • Goods receipt:
      • Booked as normal. A message says that DNs for all stock-neutral items will be created from goods receipt.
      • Counter-scan windows then follow for batch documentation and securPharm verification. Only the partial quantities actually delivered are offered.
      • The packs are decommissioned in securPharm at the same time.
      • After booking, a DN with the actually delivered quantities, including batch numbers, is printed.
  • Substitute booked in goods receipt. The original article is not put on the DN. The user must:
    1. resolve the pickup manually and edit the order (a message names the substitute);
    2. close with "create without DN", which creates no DN yet;
    3. resolve again, which puts the article on the DN.
  • Bypass. If a customer in the shop wants the item now, clicking the indicator resets the backorder quantity for stock items and dispenses them from stock immediately.
  • Between branches:
    • Works the same way, with the basket model selecting branch pharmacies.
    • Separate crates are forwarded after goods receipt.
    • These movements show under article details > sales > transfers and are excluded from optimisation.
    • It is enabled in the branch pharmacy's specific data.

4.20 Delivery-note overview and search [GENERIC]​

  • Visibility. The tab is hidden by default and enabled per workstation ("show delivery note overview").
  • Purpose. View DNs from orders, reprint them, build collective DNs for customers, homes and home units, and arrange courier delivery.
  • Default view. Only DNs in status "created" are listed. Collective DNs, cancellation DNs and other statuses are reached through search.
  • Columns:
    • recipient (the deviating recipient if there is one);
    • delivery date;
    • number ("SL" prefix for collective DNs);
    • kind: DN, collective DN or cancellation DN;
    • order type: standard, advance, transfer, webshop or clinic;
    • status;
    • printed and courier markers;
    • total.
  • Detail area. Advance-delivery DNs are highlighted. The detail shows the calculation basis, the order number (plain DNs only) and the positions; return positions are highlighted.
  • Status "created". Arises from a supplied order, from closing a sale with an immediate invoice for all items, from building a collective DN, or from a return order (cancellation DN).
  • Order versus DN. The source stresses that these are separate documents. The order is the sale transaction holding delivered and undelivered items; the DN only evidences a delivery.
  • Functions: collective DN, print, customer info, courier toggle (with the conditions dialog; "do not deliver" undoes it), history.
  • Search criteria:
    • document kinds (DN, cancellation DN, collective DN);
    • customer, home or separately billed home unit (inactive and deceased contacts included);
    • include home residents (only when a home or unit is chosen);
    • also separately supplied home units;
    • customer group and classification;
    • delivery addressee;
    • number;
    • date range and amount range;
    • article;
    • printed: all, yes or no;
    • status: all, created, invoiced or cancelled.
  • Residents of homes. If the user searches for a home resident without separate delivery, the system asks whether to search for the home (and the unit, if its parent unit has separate delivery) or for the resident. DNs were issued to the home or unit, so a search on the resident alone would find nothing.

4.21 Collective slips (Sammelschein) [GENERIC]​

  • Purpose. Combine many DNs of one customer, or of a home including its residents, into one document.
    • A doctor supplied for a month or quarter wants one list of everything delivered.
    • A home wants one daily or per-delivery document for all patients instead of per-patient DNs.
    • Separately supplied home units get their own slip.
  • Same mechanism for invoices. Collective slips also exist for invoices and credits.
  • Triggers. From the order overview (prefilled with the selected order's customer) or from the DN overview.
  • Criteria:
    • customer, home or separately billed home unit;
    • include home residents;
    • also for separately supplied home units (creates an extra slip for them);
    • document date range (no earlier than the installation date; only DNs printed in the range count);
    • document time range;
    • exclude DNs already on a collective slip (default on);
    • exclude fully invoiced DNs;
    • exclude DNs of separately delivered (blistered) goods.
  • Choosing a home resident. The system asks whether the slip should cover the whole home, the separately supplied unit, or only that customer.
  • Selection window:
    • Column SL shows whether a document is already on a collective slip; there is also a courier marker.
    • The detail shows currency, calculation type and positions.
    • For DNs nothing is pre-selected; for invoices and credits everything is pre-selected and the user deselects.
    • Confirming merges the documents and shows a print preview.
  • Splitting rules:
    • One slip holds only one calculation type (gross or net).
    • Advance deliveries are listed without prices and never together with normal deliveries.
    • So one run may produce several slips: advance deliveries, then net DNs, then gross DNs, then separately supplied home units, previewed in that order.
  • Home slips show the amount per DN and a total per customer.
  • External order numbers of each DN print in a supplementary line and are listed again at the end. Printing of packing-tub numbers is configurable.

4.22 Document history (Beleghistorie) [GENERIC]​

  • Available in the order, DN, invoice/credit and dunning overviews.
  • Lists the changes and follow-up processing of the selected document: operation type, clerk, date and time, and remark, oldest first.

4.23 Labels for orders: dosage, customer, home and clinic labels [GENERIC]​

  • Automatic prompt. If label printing is enabled for the customer (also a home, home unit, clinic or ward), directly or through a Faktura model, the number of labels is asked for automatically when a sale closes, both at the till and in Faktura.
  • Manual print or reprint. From the order overview or sales administration ("labels for all articles"), for any sale, even one without a customer. The count is prefilled with the number of packs sold.
  • Count rule. A parameter decides the default count: "total sale quantity including backorders" (default) or "only dispensed packs". With the second option, labels for backorder items print when the backorder is resolved, and only for the quantity then delivered.
  • Label-count window:
    • Shows every customer of the sale with its positions, the label sum per customer and the count per position.
    • Articles can be hidden or shown; they are hidden by default when there are several customers.
    • Buttons set counts to the total quantity, to the dispensed quantity, or to 0.
    • "Missing labels" offers only labels not yet printed, or positions where fewer labels were printed than packs.
    • Counts can be lowered for articles counted as single units but sold bundled (10, 20 or 50 per bundle).
  • Dosage labels for walk-in customers at the till total: customer name, dosage and count are entered manually. The count defaults to 0. Nothing is stored or passed to medication management. For customers under medication management, their stored dosages are shown.
  • Content:
    • pharmacy name and town;
    • customer name, plus home and home unit (so care staff know whose pack it is);
    • article name and code;
    • dispensing date;
    • intake notes;
    • dosage, if any (with medication management, the stored dosage; if it is too long, a reference to the medication plan);
    • optionally, national drug-database storage notes (on request to the vendor).
    • When the medication has pauses or discontinuations, the plan must be handed over.
  • Dispensing date printed:
    • Till: the capture date if printed immediately, even if the prescription print date was changed. If printed after resolving a backorder (including during packing in Delivery management), the resolution date on all labels.
    • Faktura: always the order capture date, or the manually backdated date.
  • Printers. Standard label printer, or a Dymo with 89×36 or 57×32 labels.
  • Robot with integrated label printer.
    • Setup: a vendor interface specification for robot label printing, the system parameter "integrated label printer", and label printing enabled for the customer.
    • When packs for home customers are dispensed, the home label is printed and applied automatically.
    • For items not held in the robot, the count window opens without the quantities already labelled, and those labels print on the normal printer.

4.24 Incoming B2B orders via MSV3.connect [DE-SPECIFIC protocol]​

  • General idea. An electronic order-intake API through which business customers order directly into back-office orders.
  • Prerequisites. The MSV3.connect licence, and a customer contact with role "company".
  • Setup in Contacts (access data page). Ticking "active" generates the credentials automatically, and a document with them can be printed for the customer.
  • Per-customer options:
    • Shortfalls:
      • "accept": backorder items are included in the order;
      • "reject": only the in-stock partial quantity is accepted, and the customer gets an automatic "not deliverable, backorder" response.
    • Order acceptance:
      • as a pre-captured order; or
      • as a confirmed order, which then appears as "on order". For this option the packing-list print option and the workstation must be set.
  • Downstream:
    • The order filter has an MSV3 type.
    • Backorder quantities appear in Open Items with a marker naming the order number and sales channel.
    • Sales administration shows the order type "MSV3 order intake".
    • Reports can filter on the sales-channel field and count customers per sales channel.

4.25 Import of receivables from SteriBase [GENERIC idea: import third-party invoices as orders]​

  • Purpose. SteriBase is a sterile-compounding (parenteral preparation) management program that creates its own invoices. That would mean capturing customers twice and invoicing separately. Instead, IXOS imports SteriBase invoices as orders, maps them to IXOS customers, and invoices them, possibly combined with other orders.
  • Rule. Afterwards, invoicing happens only in IXOS; mixed operation is not sensible.
  • Prerequisites. The "Faktura Profi" licence, and an import directory configured by the vendor (system maintenance > network). SteriBase drops an XML file there.
  • Import tab:
    • Columns: name, SteriBase invoice date, external document number, total, and a validation state:
      • OK: importable;
      • warning: importable;
      • error: not importable;
      • error accepted: will not be imported.
    • Details show the articles and the validation messages.
  • Customer mapping:
    • The first import for a recipient needs a manual mapping to an existing customer, or "create customer", which creates a contact prefilled from SteriBase data and maps it.
    • The mapping is remembered for later imports.
  • Import all.
    • All listed receivables import at once. Error rows must be fixed or set to "accept error".
    • After the import the XML file is deleted. Invoices that were not imported (accepted errors) must be re-exported from SteriBase.
  • Archive tab:
    • Lists all imported invoices plus accepted erroneous ones, for which no receivable was transferred.
    • The default view covers the last three months; a filter is available.
    • The customer mapping can still be changed as long as no invoice has been created in Faktura.
  • In the order overview:
    • Imported receivables carry their own order-type marker.
    • An invoice whose positions have different delivery dates is split into separate entries.
    • The invoice number is versioned.

4.26 Electronic delivery-note data (e-delivery note) [DE-SPECIFIC partner]​

  • General idea. EDI despatch advice sent to a business customer.
  • Licence. "Arzt.connect". Used for a specific chain of eye clinics.
  • Behaviour. When an order for such a clinic is captured, the user enters the clinic's external transaction number and order date. When delivery is completed (DNs created), the DN data are sent electronically and automatically.
  • Setup:
    • In company master > e-data exchange, create an "external order partner" (general data plus the partner mapping).
    • A vendor technician configures the Connect instance: the order partner, the mapping, and an outbound DN folder on the clinic's remote server.
    • On the customer contact (preferably a company, but a person is possible), under specific data > general, set "e-data exchange (EDI)" to the partner.
  • Capture:
    • After choosing a contact with an EDI partner, the dialog for the external number and date opens directly. It can be reopened in the till ("external order data") and can also be used for customers without an EDI partner.
    • The data print on the DN above the articles, can be searched in the order filter and in sales administration's advanced search, and appear in the transaction details.

4.27 VAT-free and foreign invoicing (Auslandsfaktura) [DE-SPECIFIC]​

  • General idea. Each customer carries a tax treatment. A tax ID is validated against an official service. The legal reason for exemption is printed on the invoice. Each kind of exempt revenue is posted to its own ledger account, and a periodic report of cross-border supplies is produced.
  • Legal basis.
    • Supplies of goods to businesses in other EU states are exempt from German VAT (§6a UStG).
    • So are supplies to seagoing ships and aviation (§8 UStG).
    • Both require that the pharmacy's and the customer's VAT IDs are correctly registered.
  • Licence. "Faktura Profi". Under cross-branch invoicing, the pharmacy where the order originated needs the licence, whichever pharmacy issues the invoice.
  • Prices are unaffected. Calculated prices and discounts (discount models or manual) refer to net prices and do not change.
  • Statutory insurance excluded. Statutory-insurance prescription subtotals are never VAT-free, because the payer is German. They are never part of VAT-free invoices or tax refunds, and the co-payment is not reduced.
  • Pharmacy prerequisite. Company master data > finance must have "EU address set up" ticked, meaning the pharmacy's VAT ID is registered for EU trade. This is checked when invoicing foreign customers; without it there is no VAT-free invoice.
  • Customer field "VAT display on invoice":
    • "VAT-free: EU business supply". Requires contact role "company" and the licence.
    • "VAT-exempt: seagoing ship". Requires that the contact has a VAT ID used for invoicing, and the licence.
    • "VAT-free: other reasons".
    • "Invoice with net unit prices", which is normal VAT but with net unit prices; used for company, wholesale and clinic customers.
    • If prerequisites are missing, a warning lists them.
  • VAT ID check via an online service for EU IDs (German IDs cannot be checked). The rationale is that the pharmacist is liable for the VAT if the customer does not pay it.
    • States:
      • not checked (also set when name or ID changed after a check);
      • checked and invalid;
      • valid with qualified confirmation;
      • valid with simple confirmation (also set when a value changed after a qualified check).
    • The time of the last check is kept.
    • Country formats vary, for example a French ID of the form 92542014428 and a Belgian ID of the form 0540.659.588.
  • Invoicing:
    • VAT-free invoices are created like normal invoices.
    • The licence is checked in the invoice total. Without it the VAT-free option is shown struck through, with a notice.
    • The invoice shows net totals and a note on the kind of exemption. For EU business supplies, both VAT IDs are printed.
  • Foreign care homes. Homes are assumed to be in Germany, so receipts omit countries. For a foreign home, an editable copy of the receipt print form is assigned to the home.
  • Recapitulative statement (Zusammenfassende Meldung, ZM). A monthly electronic report of EU supplies to the tax office. It is generated in the Evaluations module for a chosen period, with one row per customer VAT ID and its sum, and exported as ZM-<YYYY-MM>.csv to a fixed folder.
  • "Other reasons".
    • Responsibility. Issued on the pharmacy's own responsibility.
    • Reason text. The reason is not printed automatically. The user must enter it as the closing text in the invoice total. Until then a red warning and a notice about the missing justification are shown.
    • Printout. The invoice always shows net prices, the remark "VAT-free invoice", and the opening and closing texts.
    • Posting. Records are flagged in the accounting and tax-audit exports and are posted by default to the "other tax-free turnover" account.
    • Immediate invoices. Turn on the two text parameters from 4.8.
  • Tax-refund ("Tax Free") slip.
    • When it is used. The sale is processed normally with VAT. The refund itself is handled outside the system, through the accounting or a tax-refund service company.
    • Where to print it. The slip "additional data Tax Free" can be printed for any till transaction or invoice: from sales administration, the sale total, or the invoices/credits overview.
    • Content. Document number, plus gross and net goods values in total and per VAT rate, plus VAT amounts.
    • Form options: print gross values (summed and per rate); print VAT amounts (summed and per rate); print the net value per VAT amount (helpful for the export-proof form).
    • Refund at the till. Alternatively, VAT can be refunded at the till when an export certificate is presented. The payout is booked to a dedicated ledger account agreed with the tax advisor.
  • Decision matrix (customer type: private customer / business customer):
    1. Seagoing ship. Private: not applicable. Business: VAT-free invoice.
    2. EU abroad. Private: normal invoice or receipt with VAT. Business: VAT-free invoice with both VAT IDs.
    3. Third country, customer exports after the sale. Private: invoice or receipt with VAT, then a refund after export or through a refund provider. Business: invoice with VAT, refund after export.
    4. Third country, export certificate already present before invoicing. Both: VAT-free invoice, or invoice/receipt with VAT plus refund.
    5. Third country, pharmacy exports itself. VAT-free invoice, plus accompanying documents, possibly an export declaration and possibly import VAT.
    6. NATO forces (no export). Private: VAT-free invoice, or invoice plus refund, with the forces' tax-relief forms. Business: not applicable.
    • The system supports cases 1–3 directly; case 4 can be handled through the case-3 route; the rest need work outside the system. Resellers are not covered.
  • Ledger accounts (German standard charts SKR03 / SKR04):
CaseSKR03SKR04
Ship, "other tax-free turnover" (also the default for "other reasons")81504150
EU business, VAT-free81254125
Cash payment of a ship invoice at the till (money in transit)13601460
Normal invoice to EU customer, with full VAT83154315
Third-country customer, invoice with VAT 19% / 7% / 0%8400 / 8300 / 82004400 / 4300 / 4200

Own account numbers (for example 8120 / 4120) can be assigned in the DATEV settings.

4.28 Cross-branch invoicing (Filialübergreifende Fakturierung) [GENERIC for pharmacy chains]​

  • Purpose. In a branch network, pharmacy A invoices the customers of all branches, sends the invoices and collects the money. The other branches assign their receivables to A and invoice A for them.
    • Benefits: a customer who bought in several branches receives one invoice; costs fall; invoice control is central.
  • Prerequisites:
    • Enabled centrally, either for the whole network or between specific pharmacies.
    • Contact exchange done for the customers; the customer must have explicitly consented in writing.
    • Exchange of customer discount and bonus models enabled.
    • Payment and dunning terms, and their assignment to customers, exchanged.
    • Only within one trading company (same VAT ID), meaning true branches.
    • A paid add-on, licensed per participating branch.
  • Flow:
    1. Invoices/Credits tab > New, then select customers.
    2. Tick "take over new positions from branches". The tick is visible only with the licence and central activation; its default comes from a system parameter, which is on by default.
    3. Optionally set a period or basis, then OK. All documents are collected into the invoice total.
    4. Create. Invoices for own customers are created, the receivables of customers from other pharmacies are transferred, and invoices are created from them where possible. The resulting invoices have status "created".
  • Faulty data transfer from another branch:
    • Continue: the correctly transferred receivables are offered; incomplete ones stay as non-invoiced orders in the other branches.
    • Cancel: the whole run is aborted.
  • How transferred receivables appear:
    • Their orders are hidden from the order overview when invoicing finished automatically (fully invoiced). They are shown if invoicing failed, or when searched for.
    • The number is the origin-branch abbreviation + "IW" + the order number.
    • Each customer invoice lists every DN number with the pharmacy that supplied it. The invoice details show the IW-prefixed number.
    • In the supplying branch, an invoice to the invoicing branch is created; the supplying branch collects from the invoicing branch.
  • Discarding a customer invoice built from transferred receivables.
    • The invoice becomes cancelled, and the user is asked whether to discard the transfer too (for several invoices, all at once).
    • Yes: the transfer goes to "In Stornierung" (cancellation in progress) until the origin branch confirms. Then the customer invoice, the transfer and the internal invoice are all cancelled. Precondition: the supplying branch has not booked a payment for the internal settlement. Cancelled transfers are found with invoicing status "not invoiced".
    • No: the transfer stays in the Orders tab as "not invoiced". It can then be cancelled, which lets the origin branch edit it again; it may revert from "In Stornierung" to "not invoiced" if cancellation is impossible. Or a new invoice can be built from it, for example with one order more or fewer.
  • Automatic cancellation. Transfers are cancelled automatically when invoice creation is aborted or when a transaction is unticked in the invoice total. This happens only if data sync with the origin succeeded and no payment has been booked. The order is then available again in the origin branch for editing and invoicing, also by a different branch.
  • When a pharmacy leaves the network or its licence lapses:
    • No further cross-branch invoices for receivables not yet transferred.
    • While customer data exist, existing customer invoices can be cancelled and re-invoiced from the resulting receivable orders.
    • Transfers already present can be invoiced but not cancelled, because no feedback to the origin is possible.
    • If an order was partly invoiced, only the originating pharmacy can invoice the remainder, and that order can no longer be edited or cancelled (to keep it traceable).
    • Transfers from pharmacies that have left cannot be discarded.
  • Accounting export (DATEV):
    • Included when "internal settlement and goods movement" is chosen for a new export batch. The archive column "internal settlement" sums settlements from goods transfers and from cross-branch invoicing.
    • In the supplying branch, internal invoices go to "revenue from internal settlement" (account 8001), with booking text prefixed "IV", not to normal revenue.
    • In the invoicing branch, transfers go to "receivable transfer from internal settlement" (account 3201), and customer invoices go to normal revenue (8400, full VAT).
    • Own account numbers can be assigned, and the accompanying document for the tax advisor is extended.

4.29 Pharmacy acting as wholesaler (Großhandelsgeschäft) [DE-SPECIFIC licensing, GENERIC mechanics]​

  • General idea. A dedicated B2B channel with these elements:
    • customer-specific agreed assortments and net price lists;
    • dedicated purchasing rules;
    • quarantine stock;
    • four-eyes release of goods receipts;
    • batch traceability on delivery documents.
  • Background.
    • Supplying other pharmacies as their wholesaler needs an official wholesale permit (German medicines law, since August 2004), except for customary supply to other businesses.
    • Licence package "IXOS.Großhandel".
    • Setting the securPharm status "Exported" additionally needs a wholesale certificate from the national verification organisation.
  • Functions in the package (most licensed):
    • packing in goods receipt for wholesale customers;
    • simplified article entry by manual code;
    • contact property "wholesale partner";
    • price schemes and wholesale price lists;
    • Faktura orders for wholesale partners;
    • MSV3.connect order intake;
    • a special warehouse (Sonderlager) for quarantine and blocked stock (parameter "use special warehouse");
    • stock booking only after release by an authorised person (4.30);
    • securPharm decommissioning with status "Exported" for non-EU customers;
    • verification when supplying wholesale partners;
    • the report "wholesale stock value losses";
    • batch evaluation.
  • Process:
    1. Intake. Orders arrive via MSV3.connect as pre-captured orders, which are checked and confirmed with "create order". Alternatively, orders received by fax or e-mail are captured manually.
    2. Order rules. An order for wholesale partners may contain only subtotals for wholesale-partner contacts. Because these contacts carry the stock-neutral flag, all positions become backorder quantities automatically.
    3. Agreed assortment (through price schemes). Till suggestion lists show only agreed-assortment articles, and the article search starts restricted to it. The user can toggle between stock articles, all articles and the agreed assortment. Articles captured from outside the assortment are marked.
    4. Purchasing. On confirmation, purchase orders go to manufacturers and suppliers according to the basket determination models.
    5. Goods receipt. Packs are scanned and the batch is asked for.
    6. Post-processing. Edit the order and add position discounts on top of the price list. The user can step between articles in the header. Percentage discounts with up to 2 decimals print on the invoice if the wholesale invoice form is configured for it.
    7. Invoicing. Optionally issue an immediate invoice from the edit window, with the text parameters from 4.8.
    • Cross-branch invoicing of wholesale partners is possible. Batch designations and the free texts of cash positions are printed.
    • Sales and purchase statistics are shown in article administration, with sales under "other".
  • securPharm with wholesale partners:
    • Verification happens when the customer contact is a wholesale partner.
    • Deactivation as "Exported" requires the wholesale licence plus the certificate, and applies to non-EU wholesale customers.
    • The pack-info window may ask only for batch and expiry; this requires the batch-documentation setting on the branch contacts.
    • Urgent supply to another pharmacy (permitted under the pharmacy operating regulations):
      • mark the receiving pharmacy as wholesale partner, which needs the wholesale or Faktura Profi licence; or
      • sell normally with verify and deactivate, then revoke the deactivation in securPharm administration, because the pack stays in the supply chain. The batch is then documented and stated on the DN.
  • Setting up a wholesale-partner contact:
    • Type and master data. Type company. In master data: Faktura permission on; VAT display "invoice with net unit prices"; separate statistics on.
    • Specific data. Set "wholesale partner", which auto-enables cooperation partner, batch documentation and stock-neutral delivery (recommended).
    • Restrictions.
      • Branch or partner pharmacies cannot be wholesale partners.
      • A missing licence shows a warning.
      • Wholesale partners are not findable at the counter till; wholesale is handled only in Faktura.
    • Faktura page. Remove the model and assign a prepared wholesale Faktura model, or set the options directly (for example, no automatic DN print when the customer is always invoiced immediately). Assign the wholesale invoice form.
    • Discount page. Recommended: no instant discount and no discount model.
    • Access data page. MSV3.connect.
  • Wholesale invoice form (a configured copy of the invoice form):
    • sort by DN number;
    • hide the flag column;
    • show discount, as a percentage, rounded;
    • print batch documentation;
    • a footer text about presenting the wholesale permit;
    • rename the retail/markup column (for example to show the list purchase price);
    • rename "customer price" (for example to "unit price").
  • Wholesale price lists (Faktura Profi licence):
    • Creation. May contain prescription and non-prescription articles. Created via "new wholesale", flagged "wholesale prices", with net prices preset and update mode "user-defined".
    • Articles and prices. Articles are added individually with prices and/or a calculation rule. The article selection is all articles from suppliers, or the agreed assortment per supplier. The rule is based on the list pharmacy purchase price.
    • Update. Preview, then adopt; the list can update automatically overnight.
    • Merging. A wholesale list cannot be merged into a normal list, but normal and wholesale lists can be merged into a wholesale list.
    • Filter. By prescription-only status.
  • Price scheme integration:
    • Option 1. Add a usage model to the standard scheme with context "Faktura only", sale type "normal sale", customer selection "report query: is wholesale partner", and the wholesale list assigned. Prioritise it above the standard list.
    • Option 2. A separate scheme with several usage models (for example "monthly offer" and "normal agreed assortment"), with the agreed assortment activated per model, plus a low-priority fallback model with a retail list covering all articles.
    • Assignment. The scheme is assigned in the contact (discount/prices page; the field is visible only with the licence).
    • Article view. Article administration shows, per scheme, the usage model, the price list, the price and the margin.
  • Basket determination model per supplier. Article selection "all articles of supplier X"; for backorders, customer selection "is wholesale partner" and rule "specific supplier X". It has a higher priority than the base model.

4.30 Goods-receipt release by authorised staff [GENERIC: four-eyes control]​

  • Purpose. A wholesaling pharmacy can require that only authorised staff release a completed goods receipt and book it into stock.
  • Scope. Local purchasing only.
  • Prerequisites:
    • the wholesale licence;
    • password protection active (also in restricted form);
    • the system parameter "wholesale" active;
    • the right "release goods receipt", held by default by the roles manager, pharmacist and assortment manager.
  • Flow:
    1. Any employee performs the receipt and chooses "complete goods receipt". The receipt is saved and locked (view only), with markers for "completed with invoice" and "completed without invoice".
    2. "Activate editing" unlocks it again if needed.
    3. An authorised person chooses "book and release", which books the stock. If the receipt was saved with "invoice to follow", the delivery stays open for later value booking.
  • Audit. Stock/order control shows who completed, re-activated, and booked and released each receipt.

4.31 Hospital (clinic) supply (Klinikversorgung) [GENERIC idea; DE regulatory framing]​

  • Purpose. Faktura is used for the wholesale-like business with hospitals.
    • Orders arrive by fax or e-mail, through WiSL (clinic ordering software), or through Klinik.connect (the vendor's web portal). They are processed and invoiced as Faktura orders.
    • Clinic customers have contact type "clinic", agreed assortments, special net price lists and special basket models.
  • Licences. IXOS.Klinik or IXOS.Klinik Profi. Both include Delivery management Pro XL features for packing.
  • German regulatory context:
    • A large hospital-supplying pharmacy often runs physically separately on its own system. Its clinic stock must be kept in a separate warehouse and must not be sold in the normal pharmacy business, hence a separate server.
    • A public pharmacy supplying a hospital under the pharmacy law does not need a separate securPharm registration.
  • Contact setup:
    • Role "clinic". This automatically sets Faktura permission, VAT display "invoice with net unit prices", and the wholesale-partner flag (so clinics cannot be found at the counter till).
    • Recommended: a clinic Faktura model or options (for example more backorder slips, and no automatic DN print if the clinic is always invoiced immediately); a clinic invoice form; no instant discount or discount model.
  • Clinic structure page. Units and wards, each with master data, invoicing defaults, contact persons, delivery agreements and a price scheme. Agreement options include "separate delivery" and "preferred delivery type: courier".
  • securPharm. The supplying pharmacy can take over verification and deactivation for the clinic. Timing is a company setting (see 4.33). With "at sale", deactivation happens at DN creation.
  • Web ordering:
    • Klinik.connect. Requires its licence; access is set on the contact's access-data page.
    • WiSL:
      • In company master > e-data exchange, create an external order partner with the WiSL mapping.
      • A technician sets up the Connect instance with the server URL and login.
      • A digital key pair is created and the public key is exported to WiSL.
  • Clinic price lists:
    • List type. Same mechanism as wholesale lists: "new clinic", flagged wholesale/clinic prices, net, user-defined update. The rule is, for example, based on the list purchase price. These lists cannot be merged into a normal list.
    • Usage model. Context Faktura only, sale type normal, customer selection "is wholesale partner".
    • Scheme per clinic or ward. A clinic or ward can have its own scheme (for example "clinic – dermatology") with an agreed assortment, plus a fallback usage model with the pharmacy retail list.
    • Licence. The price-scheme field requires the clinic licence.
  • Bundle packs (Bündelpackung):
    • The problem. Clinic packs (Klinikpackung) are hospital-size articles, for example 5×10, that are not dispensed to the hospital in that unit; they are only used to order from the supplier. More than 5,600 are flagged in the national article database, and only about 5% have partial packs with their own code.
    • The solution. Assigning partial packs (Teilpackung, also called "clinic building block") turns a clinic pack into a bundle pack that can be dispensed as n partial packs.
    • Markers: clinic pack with an unused component; bundle with n partial packs; partial pack.
    • Creating one. Via "bundle pack" in article administration, either from a clinic pack with components or from a normal article (search for or create the partial-pack article). The number of partial packs is calculated automatically.
    • Search. Standard search shows only partial packs (filter "without large/bundle packs"); advanced search with "all articles" shows bundles.
  • Processing Klinik.connect or WiSL orders:
    1. Ordering. The clinic orders articles. It can enter free-text positions, which staff may need to convert into real positions, and an order note; compounded preparations are ordered this way.
    2. Intake. IXOS creates a pre-captured Faktura order automatically.
    3. Agreed assortment. Suggestion lists show only agreed-assortment articles (to avoid dispensing outside it by accident), and the search starts restricted to it.
      • Markers distinguish agreed-assortment articles; variants carry a date, time or customer reference, and the plain variant means net prices without any such reference.
      • Toggles switch to all own-stock articles, all articles, or back to the agreed assortment.
      • Articles from outside the assortment are marked "outside agreed assortment".
      • With cross-system withdrawal configured, the toggles change (see 4.36).
    4. Purchasing and receipt. After closing, purchasing follows the basket models. Goods receipt scans packs and asks for the batch.
    5. Post-processing. Edit the order, optionally add position discounts on top of the clinic list (percentages with up to 2 decimals print if the clinic invoice form is configured), and optionally issue an immediate invoice with the text parameters from 4.8.
    • Cross-branch invoicing of clinics is possible. Batch designations and cash-position free texts are printed.
    • On the invoice, column "Kz" shows S for a special request, meaning an article outside the agreed assortment.
    • Article administration shows the sales and purchase statistics.
  • Clinic packing list (without Delivery management). Clinic-supplying pharmacies assemble goods with the A4 packing list. A leading S marks special-request lines. With "order closure prefers 'create without DN'", the DN is created only once all ordered articles are in stock, and the packing list covers all articles.

4.32 Packing clinic deliveries in Delivery management and the staff app [GENERIC]​

  • With Delivery management Pro. The clinic licence includes it, so the pharmacy can pack either in Faktura or with Delivery management's home and clinic packing functions.
    • Setup:
      • Turn on the workstation parameter "order closure prefers 'create without DN'"; it is needed for packing in Delivery management.
      • Optionally, set the preferred delivery type "courier delivery" on the clinic or on separately supplied units (structure > agreements > delivery/packing). Orders captured for them then get a delivery created automatically with those settings.
    • Flow:
      1. Capture the order or edit an incoming Klinik.connect order. The delivery button is preset if a preferred delivery type exists; otherwise set the delivery conditions.
      2. Close with "create without DN".
      3. In Delivery management, clinic deliveries are grouped into stations served together.
      4. Pack the whole delivery, or pack one group without showing the other stations.
    • Dispense group. Dispensing a group from the robot packs its articles automatically, hands over the securPharm data and passes the batch to prescription management for billing. No counter-scan is needed.
  • With the IXOS.team smartphone app:
    • Purpose. Pack with counter-scan of containers (tubs, bags and similar) on a phone, optionally with a clip-on scanner sleeve (tested with two models of one vendor's sleeve line).
    • Prerequisites:
      • the employee right "packing via app";
      • the employee linked to the app;
      • counter-scan mode 4 set in Delivery management's packing parameters.
    • Flow:
      1. Delivery orders for clinics or units are created without a DN.
      2. When a delivery becomes packable, a packing job appears in the app.
      3. Each job shows the recipient, the tour and these totals: packs to pack manually (not in the robot), packs from the robot, backorder packs (not yet packable), and the total for the delivery. A storage-location filter shows its own count, which is not added to the total.
      4. Tap a job, scan a container, then scan the packs as prompted. With a sleeve, side buttons trigger the scan; without one, the camera scans automatically when a container label or the expected article barcode is in view.
    • Extra actions:
      • Continue without a container: scanning an article without a container prints a pack label automatically. This needs a workstation with a label printer chosen in the app.
      • Skip an article: it is offered again at the end.
      • Increase a quantity.
      • Show the job overview.
      • Scanning an article in the job list or job detail opens the article's details.
    • Shortfalls in the robot. Articles in stock but not available in sufficient quantity in the robot are offered for manual packing in the app after the robot has dispensed.

4.33 When serialised packs are verified and decommissioned (clinic context) [DE-SPECIFIC securPharm]​

  • General idea. A configurable point in the flow at which serialised packs are decommissioned.
  • Setting. Company master > securPharm > "deactivate packs" has three options:
    1. At sale (till/Faktura). Pack information is requested at sale for fully or partly verification-obligated articles. Goods receipt may still show the status window when a code is scanned, but it does not decommission. This setting does not apply to deliveries to clinics or wholesale partners.
    2. At goods-receipt booking. Pack information is requested at booking for codes not already verified when the receipt was captured, and the status window is shown if configured. Recommended for hospital pharmacies.
    3. Bundle packs at goods-receipt booking, everything else at sale.
      • After booking, only bundle packs that contain partial packs are verified and deactivated. Such a bundle is opened and only its partial packs, which need no verification, go to the clinic.
      • Bundles without partial packs are verified at dispensing.
      • The pack-info window lists only the "real" bundles.
      • Actual deactivation happens with "book" in goods receipt, not with "deactivate and close".
      • All other articles are handled at sale.
      • Recommended for clinic-supplying pharmacies.
  • Alternative. Decommission pack stacks in securPharm administration: scan the codes, then "deactivate all".

4.34 Purchase-price basis for supplier orders [GENERIC: configurable cost-basis cascade]​

  • Purpose. Clinic-supplying pharmacies often buy far below the list pharmacy purchase price, and used to correct prices by hand.
  • Parameters. Three ordered parameters, "price basis criterion 1/2/3" (goods logistics > General), each set to own purchase price, list purchase price or booking purchase price. The first one that exists is used.
  • When they apply:
    • only when the chosen direct supplier has no offer price for the article;
    • only before booking (no effect on the effective purchase price);
    • only for newly captured articles (existing orders are not repriced);
    • when a local or shared order proposal to a direct supplier is created, unless "only cheapest offers" is ticked under supplier (offers only).
  • Best practice:
    • Default: 1 booking purchase price, 2 own purchase price, 3 list purchase price. The own price is used only where no booking price exists.
    • If negotiated prices are entered before ordering: 1 own, 2 booking, 3 list.

4.35 Self-expiring manual purchase price [GENERIC]​

  • Parameters. "Take booking purchase price into own purchase price" (pricing), with the option "delete own purchase price on value booking".
  • Scenario. The user enters an own purchase price, which updates all price lists immediately, to override an outdated average or booking purchase price so that stock can be booked at a current price.
  • Effect. At value booking the manual price is deleted, so the retail price is again calculated from the booking purchase price through the price cascade of the calculation rule. This stops a manual price going stale when nobody maintains it.

4.36 Cross-system stock withdrawal (Übergreifende Lagerentnahme) [GENERIC for multi-warehouse sites]​

  • Purpose. One site runs several systems with separate warehouses, for example a hospital-supplying pharmacy next to a public pharmacy. When a Faktura order (or a till sale closed with Faktura) has a shortfall in its own warehouse that the sister warehouse can cover, the goods are rebooked and withdrawn from the sister automatically, with no user action there. Because it is the same site, the transfer needs no batch documentation.
  • Prerequisites:
    • The functions "cross withdraw stock", "transfer goods" and "exchange stock info and statistics" are set up centrally, directed from the hospital-supplying pharmacy towards the public one.
    • Both use the same stock-keeping mode.
    • Narcotic documentation is automatic in both (parameter "document narcotics automatically").
  • Exclusions. The source contradicts itself on narcotics. It first says narcotics can be withdrawn, with goods-in, goods-out and narcotic records booked automatically. Later it lists exclusions, which go into a basket in the hospital-supplying pharmacy instead: articles kept outside normal stock-keeping, narcotics, blood products, compounded preparations, and articles needing a special T-prescription.
  • Settings in the public pharmacy:
    • Processing workstation for the other pharmacy (contact > branches and partners > settings). The order arrives there, is booked automatically, and gets a DN and an invoice. With a robot, goods are output at that workstation's chute.
    • Internal settlement. "Settlement from internal goods exchange" is active in the contact, so internal settlements are net without VAT.
    • Batch documentation. Batch documentation for medicines must be off for that contact; otherwise manual batch capture blocks the automation.
  • Withdrawal dialog. For each article: shortfall quantity, expected available quantity in the sister (total stock minus reserved), and the quantity to withdraw. The last is editable, from 0 up to the lower of the available quantity and the shortfall.
  • Scenarios:
    • A, recommended: close with "create without DN".
      • Confirming the dialog triggers the automated transfer and booking.
      • The hospital-side order becomes "in stock" or "partly in stock". No DN is printed; the packing list and optionally the pickup slip are printed. Unavailable shortfalls are ordered through the normal basket models.
      • For withdrawn quantities, a purchase order is created automatically and booked into stock and value in the hospital pharmacy. The order info notes the withdrawal, and the order details show requested versus withdrawn.
      • In the public pharmacy, a transfer order is created with status "delivered" and "fully invoiced". Its DN and invoice are created but not printed, and stock is deducted.
      • Editing or cancelling that transfer order in the public pharmacy is not passed back automatically. Warnings appear, and staff must communicate otherwise.
      • Cancelling the dialog means the items are ordered through the pharmacy's own purchasing.
    • B: close with "create DNs". The order becomes "delivered" or "on order", and the DN shows both own-stock and withdrawn items.
    • C: save as pre-captured. To withdraw, edit the order and close with or without a DN. Choosing "create order" instead reserves everything and orders the shortfalls in the pharmacy's own purchasing, without showing the dialog or creating a DN.
  • Interim sales. If quantities are gone because of interim sales, a message lists the requested and still-withdrawable quantities. The rest is ordered by the pharmacy itself, and the DN covers what was actually withdrawn.
  • Article search toggles:
    • with an agreed assortment: agreed assortment (default), all stock articles, all articles;
    • without one: all (default), own stock only, stock of all branches and partners (own plus public), all.
    • Articles stocked in the public pharmacy are highlighted, with a marker when they are available there.

4.37 Blood-product documentation for clinic supply [DE-SPECIFIC]​

  • General idea. Traceability records at recipient-unit level for special product classes.
  • Context. Blood products are delivered directly to wards or departments, and documentation per patient is then the ward's job.
  • Setup for automatic ward-level records:
    • the parameter "automatic documentation of blood products and T-prescriptions" is on;
    • the clinic structure has a sub-unit with the exact ward and clinic name (ward names may repeat across clinics);
    • the sub-unit has the agreement "separate delivery".
  • Flow:
    1. Create a Faktura order for the ward, capture the blood product and close.
    2. A "blood product dispensing" dialog opens. "Dispensed to" is the clinic (set automatically), with the ward as recipient.
    3. Enter the batch data, choose the doctor and save. The entry goes into the blood-product documentation.

4.38 Antibiotic-consumption evaluation for clinics [DE-SPECIFIC]​

  • General idea. A consumption-density reporting service for institutional customers.
  • Purpose. Offered as a service to clinic customers, who must report at least once a year to the national public-health institute under infection-protection law.
  • Content.
    • Consumption densities per route of administration and per ATC group, as daily doses per 100 patient-days or per 100 cases. Only certain ATC groups are included.
    • Exported to Excel.
    • Occupancy data and defined daily doses, which cannot be derived automatically, are entered by the user.
  • Details. In the Evaluations module.

5. Workflows​

5.1 Standard order to a customer on account​

  1. Make sure the contact has Faktura settings and complete address data.
  2. In the order overview choose New, then select the customer. The Faktura till opens with the default sale type.
  3. Capture items. Add subtotals and customers as needed, and set sale types, payer or doctor.
  4. Close the order:
    • Create DNs. DNs are created for the stock items and stock is booked out. Prescriptions print per prescription subtotal. For backorders, a pickup slip, packing list and backorder slip (if configured) print, and a missing-prescription reminder slip prints if relevant. Labels are asked for if enabled.
    • Or create without DN. Everything is reserved and the packing list prints.
    • Or continue later. The order is saved as pre-captured.
  5. The missing items are ordered through the basket models. When goods receipt books them, the order moves to "partly in stock" or "in stock".
  6. Resolve the backorder by scanning the pickup slip or using "resolve backorder", and create the DN for the delivered items. The order becomes "delivered".
  7. Optionally deliver by courier (4.18) and/or build a collective DN (4.21).
  8. Invoice the DNs from the Invoices/Credits tab (in another chapter). The DN status becomes "invoiced" and the order becomes "fully invoiced".

5.2 Order with immediate invoice​

  1. Capture the order in the Faktura till.
  2. Choose immediate invoice. If there is no SEPA mandate, the order waits in status "created".
  3. Prescriptions print, DNs are generated without printing, and the invoice is created and printed. If items are missing, the user chooses whether to invoice the deliverable items only or all items.

5.3 Advance delivery and settlement​

  1. New order, choose the customer and switch to advance-delivery mode.
  2. Capture the items and create DNs. Stock is booked out and the items are recorded as advance deliveries.
  3. Later, when the prescriptions arrive, create a new order for the customer through "prescription debt" or Open Items.
  4. Choose the advance items and quantities to settle, which are taken oldest first. Pricing runs.
  5. Add other items if needed and create DNs (only for the new items). Prescriptions print.
  6. The settlement order is "delivered" and goes to invoicing. The invoice date follows the rule in 4.14.

5.4 Partial delivery from the wholesaler​

  1. Edit the order and enter the undeliverable quantity as a shortfall in the basket window.
  2. Create DNs for the partial quantity.
  3. When the rest arrives, "resolve pickup slip and create DN". With batch documentation, or for transfer orders, a full-quantity DN replaces the partial ones instead.

5.5 Return and credit​

  1. New order for the customer, then cancellation/return, then choose the return type.
  2. Capture the returned items with a negative "to dispense" quantity.
  3. Create DN. The cancellation DN prints.
  4. Create the credit note in Invoices/Credits.

5.6 Large clinic order with robot (without Delivery management)​

  1. The Klinik.connect or WiSL order arrives as pre-captured.
  2. Review it line by line. Convert free-text positions using the info window's searches.
  3. Confirm with "create without DN", which skips the packing list.
  4. Pick or dispense the order. The robot dispenses into the tub, the DN for the robot goods prints, and a packing list prints for the rest.
  5. Pack the rest manually. Book the supplier deliveries in goods receipt (batch is asked for).
  6. Create the DN for the manually packed and ordered goods, then check and scan.
  7. Edit for discounts or a price update, then issue an immediate invoice or a normal invoice.

5.7 Clinic order with Delivery management or the app​

  1. Configure "order closure prefers 'create without DN'" and, optionally, the preferred delivery type "courier" on the clinic or its units.
  2. Capture or edit the clinic order (the delivery is preset) and close without a DN.
  3. In Delivery management, the deliveries are grouped by station. Pack the delivery or a group, or dispense a group from the robot (auto-packed, no counter-scan).
  4. Alternatively, pack in the staff app: scan a container, then scan the packs.

5.8 Wholesale order to another pharmacy​

  1. The order arrives via MSV3.connect (pre-captured or confirmed) or is captured manually. Only wholesale-partner subtotals are allowed, and all positions become backorders (stock-neutral).
  2. Confirm. Purchase orders go to the suppliers set by the wholesale basket model.
  3. Goods receipt: an employee completes the receipt, and an authorised person books and releases it. Batches are captured.
  4. Edit the order: add position discounts, update prices if needed.
  5. Issue an immediate invoice on the wholesale invoice form, with batch documentation printed.

5.9 Cross-branch invoicing run​

  1. In the invoicing branch: Invoices/Credits > New, select customers, tick "take over new positions from branches".
  2. The invoice total collects the own documents and the receivables transferred from other branches.
  3. Create. The customer invoices are created, and the other branches create internal invoices to the invoicing branch.
  4. Corrections: discard the customer invoice and optionally the transfer (4.28).

5.10 Stock-neutral home supply​

  1. A home resident's sale is closed with Faktura. It is flagged stock-neutral automatically, so there is no reservation and no pickup slip.
  2. The virtual basket is rebooked to a real supplier and ordered.
  3. At goods receipt, the counter-scan for batch and securPharm runs, the packs are decommissioned, and the DNs are created automatically with the delivered quantities and batches.
  4. Optionally, combine the home's DNs into a collective DN and deliver it by courier.

5.11 SteriBase receivable import​

  1. SteriBase drops the XML file in the import folder.
  2. In the import tab, check the validation states and map customers (or create them).
  3. Import all. The rows become orders of type "SteriBase receivable", and the XML file is deleted.
  4. Invoice them in Faktura, optionally together with other orders.

6. Business rules and calculations​

  • Stock booking. Stock is booked out only when a DN is created. Settling an advance delivery books no stock. Picking robots dispense only at DN creation.
  • Reservation.
    • A new order reserves temporarily.
    • "Continue later" releases the reservation.
    • Binding closure reserves everything and orders the shortfalls.
    • Stock-neutral customers get a virtual reservation instead.
  • Versioning. Every edit produces version "/n+1", and the previous version becomes "superseded". Each DN produced by an edit gets a new number and the current date.
  • Deletion and cancellation:
    • Delete is possible only for pre-captured orders.
    • Cancel is possible only if the order is not invoiced; it creates cancellation DNs automatically.
    • Backorders of an invoiced order cannot be resolved until the invoice is discarded.
  • Mixing rules.
    • Advance and non-advance items cannot share an order.
    • A wholesale-partner order may contain only wholesale-partner subtotals.
    • A collective slip holds a single calculation type and never mixes advance deliveries with normal ones.
  • Advance-delivery settlement:
    • The quantity to settle is distributed over the original subtotals, oldest first.
    • Any quantity above the advance quantity comes from stock.
    • The sale-type inheritance rule is in 4.14.
    • The invoice carries the advance date only if the recipient is the same.
  • Backdating.
    • Prices and contracts still come from the capture date.
    • The earliest allowed date is 1 July 2020.
  • Walk-in customers must be invoiced immediately, because their data are purged nightly.
  • Price update reprices the uninvoiced quantity of all positions from goods-receipt prices and re-creates the existing DNs.
  • Batch documentation. It requires a single DN over the full quantity: partial DNs are superseded by a complete DN.
  • Original and copy. A document may legally be in circulation only once.
    • A reprint the customer already holds is marked "KOPIE".
    • A new original may be printed only if the old original is still in the pharmacy and is destroyed.
  • Label count. The default is the total sale quantity including backorders; optionally only the dispensed quantity.
  • Label date. Faktura labels carry the order capture date (or the backdated date). Till labels carry the capture date, or the resolution date after a backorder.
  • Cash-discount price and open amount.
    • Cash-discount price = total − cash discount, using the discount valid at the last payment date; blank once the discount period has expired.
    • Open amount = cash-discount price − payments.
  • Filter logic.
    • Non-status criteria are combined with AND.
    • Values within one status kind are ORed.
    • Order status versus invoicing or advance status is joined by AND or OR (default OR).
  • Order status derivation:
    • partly in stock: some backorder quantity is in stock;
    • in stock: all backorder quantity is in stock;
    • on order: none is in stock;
    • delivered: everything is on DNs;
    • special positions and fees always count as in stock.
  • Create complete DNs. Only subtotals whose items are 100% in stock get a DN.
  • Cross-system withdrawal quantity. Available = sister's total stock − reserved. Quantity to withdraw ≤ min(available, shortfall).
  • Purchase-price basis. The first existing value in the configured order (booking, own, list) is used. It applies only when there is no supplier offer price, and only to newly captured articles.
  • VAT-free invoicing:
    • Statutory-insurance subtotals are always excluded.
    • The pharmacy's EU registration flag and the customer's role or VAT ID are required.
    • For "other reasons", the justification must be entered as invoice text.
  • Cross-branch transfer cancellation. Allowed only if data sync succeeded and the supplying branch has booked no payment for the internal settlement. Impossible once the origin pharmacy has left the network.
  • Narcotics in a normal sale. Allowed in Faktura only for company, doctor, home or clinic customers.
  • Packing-tub number. At most 20 characters in total, including comma-separated lists. Search uses a prefix match.
  • Bulk printing. At most 100 orders per print run.
  • Notifications. SMS notification only for German mobile numbers.
  • Discount display. Percentage discounts can have 2 decimals and are printed on wholesale or clinic invoices if the form allows it.

7. Configuration and settings​

ParameterScopeEffectDefault
Faktura settings on contact (payment page)contactMust be set before an order can be created for the contact.—
Default sale type (Vorbelegung Verkaufsart)Faktura system settingsStarting sale type in the Faktura till.not stated
Reminder for open orders (general sales)systemCreates a Notes task reminding about open orders.not stated
Show delivery note overviewworkstationShows the DN tab.off (hidden)
Format of delivery note from FakturaworkstationA4 or receipt roll.A4
Reminder slip "missing prescription"systemPrints a reminder slip for missing prescriptions. In Faktura only one is ever printed.not stated
Print count pickup slipsworkstation (Faktura)Number of pickup slips.not stated
Print count packing listsystem-wide, shared with the tillNumber of packing lists; may be 0 (reprint is possible).not stated
Print format packing listsystemReceipt printer or A4.not stated
Print packing list (picking dialog)systemDefault of the checkbox.not stated
Order closure prefers "create without DN"workstation (general sales)Swaps the default closing button. For clinics, the DN is created only when everything is in stock. Required for packing in Delivery management.off
Show invoice total at immediate invoiceworkstation (invoice creation)Opens the invoice-total dialog for immediate invoices, so texts can be entered.off
Take order texts into immediate invoicesystem (invoice creation)Copies the order's opening and closing texts onto immediate invoices.off
Take over new positions from branchessystem (invoice creation)Default of the cross-branch checkbox.on
Print count customer labeltill system parameters (print options)Total sale quantity including backorders, or only dispensed packs.total sale quantity
Integrated label printersystem maintenance (robot page)Robot applies home labels.off
Continue automaticallyworkstation (robot page)Auto-creates the DN after robot dispensing.not stated
Use WWKS2 pack information for securPharmrobotRecommended: "always" or "only items without documentation duty".not stated
Dispense on scanrobotRecommended off.not stated
Automatic order on transfer receiptsystemCreates transfer orders automatically; otherwise they arrive pre-captured.not stated
Contact: number of DNs / backorder slips / labels, label print on/off, print forms, Faktura modelcontact or clinic structureAutomatic print counts and forms.backorder slips: none
Contact: billing mode "immediate invoice"contactPrints the invoice together with the DN.—
Contact: stock-neutral deliverycontact or homeStock-neutral handling and separate statistics.off
Contact: wholesale partnercompany contactEnables cooperation partner, batch documentation and stock-neutral delivery; hides the contact at the till. Requires licence.off
Contact: VAT display on invoicecontactNet unit prices / EU business VAT-free / ship VAT-exempt / VAT-free other.normal
Contact: e-data exchange (EDI) partnercontactOpens the external-order-data dialog and sends DNs electronically.none
Contact: robot output chutecontactDefault chute for dispensing.—
Contact: settlement from internal goods exchangebranch contactNet internal settlement without VAT.—
Contact: preferred tour / preferred delivery typecontact or clinic unitAutomatic courier delivery.—
Contact: MSV3.connect active, shortfall handling (accept/reject), order acceptance (pre-captured/confirmed) with packing-list print and workstationcontactMSV3 order intake behaviour.—
Company master: EU address set upcompanyPrerequisite for VAT-free invoices.off
Company master: securPharm "deactivate packs"companyAt sale / at goods-receipt booking / bundle packs at booking, otherwise at sale.not stated
Company master: external order partner (WiSL, EDI)companyElectronic order and DN exchange.—
Use special warehousesystemQuarantine and blocked stock for wholesale.off
Wholesale (system parameter)systemEnables goods-receipt release by an authorised person.off
Automatic documentation of blood products and T-prescriptionssystemWard-level blood-product records.off
Document narcotics automaticallyboth pharmaciesNeeded for cross-system withdrawal.—
Purchase-price basis criteria 1/2/3goods logistics > GeneralCost-basis cascade for supplier orders.best practice: booking, own, list
Take booking purchase price into own purchase price, with "delete own purchase price on value booking"pricingThe manual purchase price expires at value booking.not stated
Print-form options (order overview / DN / invoice)print formAlternate row shading; hide clerk's first name (printed by default); prices on DN; "do not print notes on backorders"; tax-free slip options; wholesale invoice options (sort by DN number, show discount %, print batch, rename columns, footer text).various
Saved order filters, default filteruser/systemInitial list content.vendor filter "IXOS"

8. Roles and permissions​

  • Delete an order. Only in status pre-captured.
  • Edit locking. Concurrent editing is blocked; an order "currently being edited" is locked for others.
  • Release goods receipt. This right is needed to book and release goods receipts in wholesale mode. It is granted by default to the roles manager (Leiter), pharmacist (Apotheker) and assortment manager (Sortimentsverantwortlicher). Password protection, at least in restricted form, must be active.
  • Packing via app. Employee right needed to pack in the IXOS.team app.
  • Customer consent. Cross-branch invoicing requires the customer's explicit written consent before contact data are exchanged.
  • Licences gating features:
    • Faktura Profi: VAT-free invoices, order from file, SteriBase import, wholesale price lists.
    • MSV3.connect.
    • Webshop.
    • Klinik.connect.
    • Arzt.connect: e-delivery note.
    • IXOS.Großhandel: wholesale.
    • IXOS.Klinik / Klinik Profi: clinic features, Delivery management Pro XL, clinic reports, price-scheme field for clinics.
    • Cross-branch invoicing: per branch.
    • Reports Profi or MMR-Standard: active-substance field.
  • Wholesale and clinic contacts are not reachable at the counter till, so staff there cannot sell to them by mistake.
  • Vendor technicians configure import directories (SteriBase) and Connect instances (WiSL, EDI).

9. Integrations, hardware and external services​

  • Picking robot (Kommissioniersystem):
    • Dispensing at DN creation or through the picking function.
    • The WWKS2 protocol carries pack data for securPharm, reports tub numbers, and allows stopping a running job (if supported).
    • Integrated label printers are supported (vendor interface specification).
  • Label printers. Standard label printer, and Dymo with 89×36 and 57×32 labels.
  • Smartphone app (IXOS.team) for packing, optionally with a clip-on barcode scanner sleeve. It prints pack labels through a workstation with a label printer.
  • Courier tablet app for tour optimisation, plus a digital delivery list. SMS and e-mail notifications are sent to customers.
  • MSV3.connect. German wholesaler order protocol, used here to receive B2B orders.
  • Klinik.connect / MediShop. The vendor's clinic and shop ordering portal. It transmits orders, notes, approval data and approver phone numbers.
  • WiSL. Third-party clinic ordering software, connected through a Connect instance with a key pair.
  • EDI / e-delivery note. DN data sent to a clinic partner's remote folder.
  • SteriBase. Sterile-compounding software; its XML invoice files are imported.
  • Webshop. Orders imported automatically, with an external transaction number.
  • SEPA direct debit. A stored mandate is needed for an immediate invoice to be produced at once.
  • securPharm. The national medicine-verification system: verification and decommissioning at sale or at goods receipt, the "Exported" status for non-EU wholesale customers, revoking a deactivation, and the per-order securPharm log.
  • VAT ID validation service. EU online check with simple or qualified confirmation.
  • DATEV. Accounting export, with specific accounts for VAT-free, internal-settlement and receivable-transfer postings. There is also a tax-audit (GDPdU) export.
  • Tax office. Monthly recapitulative statement as a CSV export.
  • Branch network data exchange. Contacts, discount models, payment and dunning terms, receivable transfers, stock information, and cross-system withdrawal between servers.
  • National drug database (ABDA). Article information, storage notes for labels, ATC codes, active substances, and the flags for clinic packs and partial packs.

10. Printouts, reports and exports​

10.1 From the order overview / order details​

  • Labels: for all articles; missing labels only; selected articles.
  • Delivery notes on A4 or receipt roll.
  • Prescriptions. Prescription forms for the order's prescription positions. A prescription with an active deferral (Rückstellung) is not printed; the user is told the deferral number and must resolve the deferral first.
  • Backorder slip on A4. Can be reprinted even when the default count is 0.
  • Packing lists:
    • for backorder items, on receipt roll or A4;
    • packing list A4 for all displayed orders (overview only), sorted by customer, as one common list or one per customer.
  • Pickup slip for backorder items. Only while the order is not yet "delivered".
  • Order overview list. All filtered orders without articles, for example "all uninvoiced orders" for the tax advisor. It can be saved as PDF, with optional alternating row shading.
  • Selected order:
    • Shows order number, date, clerk and article details.
    • The print is logged in the order history.
    • The header can be configured, and the clerk's first name can be hidden.
    • It can also be saved as PDF under documents/year/month, with the order number and date in the file name.
  • securPharm log. The current verification status of every captured pack, useful as proof in wholesale. Offered only if at least one pack has securPharm data.
  • Care-aids settlement (Abrechnung Hilfsmittel).
  • Reminder slip for missing prescriptions. Only one is printed in Faktura. Content: pharmacy address, customer name, and per subtotal the items without a prescription (dispensed quantity, name, dosage form, quantity, unit, supplier, standard pack size).
  • Courier slip and courier label. Only when the order is "delivered" (no backorders and the DN has been printed).
  • Limits. At most 100 orders per print run. A print preview is shown first, and documents can be printed or sent.

10.2 From the DN overview​

  • Courier slip and courier label (courier deliveries only).
  • Selected DNs on A4, on receipt roll, or as PDF. PDFs are stored under documents/year/month, with the DN number and DN date in the file name and a "-Kopie" suffix for copies. Several customers can be selected at once.
  • Original or copy. Asked for when the DN was already printed. A copy carries the "KOPIE" imprint.
  • Output. Print preview, then print, e-mail, or another printer.
  • DN overview list. All supplied but uninvoiced DNs, in landscape. The header shows the filter criteria. Columns: customer, date, number and kind, order status and type, print status, courier flag, total per DN, and grand total. Optional alternating row shading.

10.3 Other documents​

  • Collective slips for DNs and for invoices/credits (4.21).
  • Pickup slip (with barcode), packing list (with tub numbers on the standard forms; "S" marks special requests on clinic lists) and backorder slip.
  • Labels (4.23).
  • VAT-free invoice wording, the tax-free additional-data slip, and the recapitulative statement CSV ZM-<YYYY-MM>.csv (4.27).
  • Wholesale and clinic invoice form (4.29). Its "Kz" column shows S for special requests and, on DNs, G/P/R for the prescription sale types.
  • Invoice positions as Excel (clinic use).
    • From Invoices/Credits > print > "invoice positions as Excel document", for checking.
    • Saved under the documents drive/year/invoice month, with the invoice number and date in the file name. The source shows a ".pdf" extension in the path, which looks like a documentation error.
    • Sorted by DN recipient, then by DN number ascending. "Kz" = S for special requests.

10.4 Clinic report queries (IXOS.Klinik / Klinik Profi, Reports module)​

Most of these queries need the "Standard" price scheme adapted for customer-specific agreed-assortment values and retail prices.

Article result category

QueryContentVariables
Dispensing statistics (supplier)Articles of chosen suppliers dispensed in the period.supplier, customer, agreed assortment (current / at dispensing), period, packs dispensed, net-net turnover
Dispensing statistics (ATC code)Dispensed articles grouped by ATC therapeutic subgroup.customer, agreed assortment (current / at dispensing), period
Dispensing statistics (cost centre)Articles dispensed to a chosen cost centre.customer, packs dispensed, agreed assortment (current / at dispensing), period
Article list (alphabetical)Agreed-assortment articles.is bundle pack
Article list (supplier)Grouped by supplier.supplier, is bundle pack
Article list (ATC code)Grouped by ATC subgroup.ATC level (WHO), is bundle pack
Article list (most frequent)Most-dispensed articles in the period.period, number of packs
Article list (pieces per pack)Includes the computed piece count per pack.is bundle pack
Fast moversSales in a period compared with a comparison period.customer, period, comparison period
Drug listAgreed assortment by ATC subgroup with retail price. IXOS.Klinik only.retail price (price scheme)
Order listSales of agreed-assortment articles in the period.customer, agreed assortment (current), packs dispensed, period

Customer result category

QueryContentVariables
Total clinic turnover per monthTotal turnover of the chosen clinics per month.clinic assignment, period, packs, net-net turnover, gross turnover
Monthly turnover per clinic unitMonthly turnover of the chosen clinics per unit.clinic assignment, period, packs, gross turnover, net-net turnover
Turnover by cost centreTurnover of the chosen cost centres per month.cost centre, clinic assignment, period, comparison period
Clinic-unit turnover per monthTurnover of the clinic units per month.clinic assignment, period, packs, gross turnover, net-net turnover

Goods-receipt result category

QueryContentVariables
Purchase overviewValue-booked receipts of the chosen suppliers.booking supplier, value-booking date

Additional report fields and filters

  • ATC level (German) and ATC level (WHO) of the assigned finished medicine, including sub-levels.
  • The clinic licence also allows editing the predefined queries.
  • The sum filter "clinic assignment" selects a clinic together with all its sub-units.
  • The "active-substance selection" field (needs Reports Profi or MMR-Standard) restricts an article report to chosen active substances, including their amounts. This gives a consumption view by substance rather than by article.

10.5 Other evaluations​

  • Antibiotic-consumption export to Excel (4.38).
  • Wholesale stock value losses and batch evaluation (wholesale package).
  • Reports per sales channel (MSV3.connect).

11. Dependencies on other modules​

  • Till / POS. The Faktura till shares the till's user interface and functions. Till sales can be closed with "Faktura", and Faktura pickups can be resolved at the till.
  • Open Items. Backorder resolution, advance-delivery settlement, and pickup slips.
  • Invoices/Credits and Dunning (Faktura tabs, covered in another chapter). Invoice creation, credit notes, invoice collective slips, dunning.
  • Contacts. Faktura settings, roles (home, clinic, company, branch), clinic structure, delivery addresses, print options, VAT settings, access data, employee rights.
  • Purchasing / basket determination models. Ordering shortfalls, virtual suppliers for stock-neutral delivery, wholesale and clinic supplier rules, order proposals.
  • Goods receipt. Brings backorders into stock, books substitutes, triggers automatic DNs for stock-neutral delivery, release by authorised staff, batch capture, securPharm.
  • Delivery management (incl. Pro / Pro XL). Tours, packing, counter-scan, the delivery list, clinic station grouping.
  • Article administration. Price lists, price schemes, agreed assortments, bundle packs, statistics, purchase prices.
  • securPharm administration and the company securPharm settings.
  • Print forms. DN, invoice, packing list and label form configuration.
  • Sales administration. Viewing the transactions behind orders, reprinting, the tax-free slip.
  • Prescription management. Prescription printing, deferrals, batch transfer for billing.
  • Medication management. Dosages on labels, medication plan.
  • Notes. Reminder tasks for open orders.
  • Evaluations / Reports. Recapitulative statement, antibiotic consumption, clinic queries.
  • DATEV / accounting export.
  • Branch / partner network. Transfers, cross-branch invoicing, cross-system withdrawal.
  • Blood-product documentation and narcotics documentation.
  • Company master data. EU VAT registration, e-data-exchange partners, securPharm.

12. Portability notes​

Generic and directly useful for Shefa:

  • Order-centric sales on account. Orders hold multiple customers and subtotals and are explicitly versioned; delivery notes are separate documents and the point of stock booking; invoices are built from DNs.
  • Order status model: draft, in stock, partly in stock, on order, delivered, superseded, cancelled, locked. It is driven by reservation and backorder state and kept separate from invoicing status.
  • Backorders with pickup slips (scannable barcode), packing lists and backorder slips, and a resolve dialog with "all" versus "only available" choices.
  • Reserving a whole sale, immediate invoicing, return orders as the basis of credits, price update before invoicing, and the walk-in customer rule (invoice immediately because the data are transient).
  • Advance delivery and later settlement. This fits doctor or clinic consignment and any case where the payer is decided later.
  • Collective slips per customer or institution, with the split rules by calculation type.
  • Courier delivery flags with delivery windows, notification and deviating addresses.
  • Stock-neutral (cross-dock) supply for institutional customers, so shelf stock stays available for walk-in customers.
  • Picking with packing-tub numbers and an automated dispensing robot.
  • Saved filters with AND/OR semantics; document history; original-versus-copy reprint control.
  • Wholesale and clinic B2B channel: agreed assortments, customer-specific net price lists via price schemes, special-request marking, bundle and partial packs, cost centres and unit hierarchies, four-eyes goods-receipt release, quarantine warehouse.
  • Cost-basis cascade and self-expiring manual purchase price.
  • Cross-system stock withdrawal between co-located warehouses, and cross-branch central invoicing with internal settlement (both fit Syrian pharmacy chains or a warehouse with retail outlets).
  • Import of third-party invoices as orders (SteriBase pattern); order import from file; electronic order intake (MSV3 pattern) and electronic despatch advice (EDI pattern).

Germany-specific, with the idea underneath:

German featureIdea that carries over
§6a/§8 UStG VAT-free invoices, recapitulative statement, DATEV accountsPer-customer tax treatment with a printed legal reason, validated tax IDs, separate ledger accounts per exemption type, periodic report of cross-border supplies.
Tax-free refund slipPrintable VAT breakdown per rate for export refund claims.
securPharm verification and deactivation timing, "Exported" statusConfigurable point at which serialised packs are decommissioned; a distinct status for exported packs.
Wholesale permit and NGDA certificateLicence-gated B2B channel.
MSV3, Klinik.connect, WiSL, Arzt.connectStandard B2B order-intake APIs and despatch advice.
Practice-supply (Sprechstundenbedarf) prescriptions behind advance deliveryGoods released before the payer or pricing is known, settled later.
Substitution check under the social code (§129 SGB V) when a substitute is deliveredPayer-specific substitution rules must be re-checked whenever a substitute replaces the ordered item.
Blood-product documentation, antibiotic-consumption reporting under infection-protection lawUnit-level traceability for special product classes; consumption-density reporting service for institutional customers.
1 July 2020 backdating cut-offDate-effective tax rates; backdated documents must not cross a tax-rate change.
Narcotic documentationControlled-substance records that update automatically on internal transfers.
Separate clinic warehouse ruleLegally segregated inventory per business line.

13. Open questions​

  • Status "Erstellt" for orders. It appears only on the immediate-invoice page, when no SEPA mandate exists. The source does not say how such an order proceeds.
  • Delete and "create DNs" availability. The function-key page says delete and "create DNs" are possible only in status "In Bearbeitung", while other pages say delete works only for pre-captured orders and DNs can be created from several statuses. The exact rules are unclear.
  • Robot dispensing statuses. The robot picking page says dispensing is impossible for orders in "partly in stock", "on order" or "in stock", but also that picking works for all orders except pre-captured and delivered ones.
  • Narcotics in cross-system withdrawal. The page both allows narcotics and lists them as excluded.
  • Stock-neutral delivery. The "virtual reservation of one pack" at Faktura closing is not explained.
  • Default values. Defaults for many print-count parameters, the default sale type, and the securPharm deactivation setting are not stated.
  • Excel export extension. The invoice-position Excel export path is shown with a ".pdf" extension.
  • Invoice creation, credit notes and dunning detail. Not covered by these pages: due-date calculation, cash-discount terms and dunning levels are in another chapter.
  • "A+V" pricing. The pricing rule used when advance deliveries are settled (taxed per the German drug price ordinance) is named but not explained.
  • Interface formats. The format of the "order from file" import beyond "code plus quantity" (column order, separators) is not specified, and neither is the XML schema for SteriBase.
  • Agreed-assortment icon variants. The variants with a date, time or customer reference are referred to another help topic and are not explained here.

14. Source pages​