true For the OCR Adapter the following minimal options should be set: * X-Tika-PDFocrStrategy=OCR_AND_TEXT_EXTRACTION * X-Tika-OCRLanguage=eng+deu These options allow OCR and text extraction suporting English and German language. Additional Tika Options can be set but are NOT needed in most cases: * X-Tika-PDFOcrImageType=RGB (setting the RGB color mode) * X-Tika-PDFOcrDPI=400 (setting DPI) Setting the OcrDPI is only recommended if the DPI is know! Possible ImageTypes are: * ARGB Alpha, Red, Green, Blue * BINARY Black or white. * GRAY Shades of gray * RGB Red, Green, Blue BoundaryEvent_1 Task_4 IntermediateCatchEvent_2 Task_2 IntermediateCatchEvent_3 StartEvent_1 EndEvent_1 dataObject_FS1r0Q task_uB6BGQ textAnnotation_CtU05A task_PsBytg dataObject_CRa7xA event_bYlo0w event_za0KnA event_Zxhr0w dataObject_vVKXIg event_yQLmNA task_0YaQ2w dataObject_HHM58Q event_xOeBKg event_pDFoXg dataObject_ZhBiZg event_4DNGzg dataObject_KPUiiw event_wmNwPA event_tFxV0w _subject]]> _amount (Brutto € _amount_brutto) _description]]> home ]]> false sequenceFlow_fRPOrw sequenceFlow_4gpPgw sequenceFlow_fRPOrw true Rechnungseingangskontrolle

Der Workflow 'Rechnungseingang' beschreibt beispielhaft einen Ablauf zur Prüfung von Eingangsrechnungen.

  • Nach Erhalt einer Rechnung (z.B. Post, E-Mail, Fax,...) wird diese in das Workflowsystem übertragen und der Prozess Rechnungseingang gestartet.
  • Die Rechnung wird wahlweise eingescannt und über den Abschnitt 'Dokumente' an den Vorgang hinzugefügt.
  • In diesem Beispiel wird die Rechnung einem zuvor ausgewählten Mitarbeiter zur Prüfung vorgelegt.
  • Nach positiver Prüfung werden die Rechnungsdaten (Zahlungsziel, Bankverbindung) vom Controlling im System erfasst und auf das Zahlungsziel gewartet.
  • Nach Erreichen des Zahlungsziels wird der Vorgang automatisch dem Controlling erneut zur abschließenden Bearbeitung vorgelegt.

Der Workflow

Eingangsrechnungen können über eine E-Mailschnittstelle oder das Filesystem automatisch eingelesen werden. Eine Eingangsrechnung wird in diesem Beispiel vom zugewiesenen Mitarbeiter sowie den Prozessverantworltichen (Controlling) bearbeitet.

]]> SequenceFlow_9 sequenceFlow_4gpPgw X-Tika-OCRLanguage=eng+deu X-Tika-PDFocrStrategy=OCR_ONLY (PDF|pdf)$ 10]]> false SequenceFlow_9 SequenceFlow_2 DataOutput_1 DataOutput_1 sequenceFlow_VlPVJg txtlastcomment]]> cdtr.name (invoice.language)]]> $workflowgroup - $workflowstatus]]> SequenceFlow_12 sequenceFlow_gXJm0w SequenceFlow_12 SequenceFlow_2 1000 ]]> true sequenceFlow_VlPVJg sequenceFlow_0N8cOQ sequenceFlow_fN22Gg cdtr.name (invoice.language)]]> true document.type
Company: document.company
]]> sequenceFlow_JpNUKg sequenceFlow_lmU9IA sequenceFlow_naZnAA sequenceFlow_8SpIiA ]]> _subject]]> _amount (Brutto € _amount_brutto) _description]]> home]]> false sequenceFlow_lmU9IA sequenceFlow_Od65ZQ sequenceFlow_Od65ZQ sequenceFlow_0N8cOQ ]]> false https://llama.cpp.imixs.com/ XML true cdtr.name,invoice.number,invoice.date,invoice.total,payment.date,cdtr.iban,cdtr.bic,total ON false ]]> DataOutput_2 DataOutput_2 sequenceFlow_aC0skQ sequenceFlow_YMtfiw cdtr.name (invoice.language)]]> true sequenceFlow_JpNUKg sequenceFlow_lmU9IA sequenceFlow_aC0skQ sequenceFlow_A62nqQ sequenceFlow_z8jotQ {"max_tokens": 4096, "temperature": 0 } invoice.summary [INST]Transfer the invoice data into an XML object with the following structure: ... ... 2024-12-31 2024-12-31 1234.00 ... ... Create only the XML object. Use only the XML structure specified in this example and do not create any other XML tags. Don't create explanations or comments. Format date values (invoice.date, payment.date) into the ISO 8601 format (YYYY-MM-DD). Format numbers and amounts (type="double") according to ISO 4217. Transfer the individual invoice data to the XML tags, taking into account the following suggestions for mapping: - Company name ==> "cdtr.name" - Invoice number ==> "invoice.number" - Invoice Date ==> "invoice.date" - Total ==> "invoice.total" (in EUR or if not available in USD or PLN) - IBAN ==> "cdtr.iban" - BIC or SWIFT ==> "cdtr.bic" - Payment date / Due date ==> "payment.date" <> [/INST] ]]]]> ]]> false rechnungseingang-dwc-1.0 5000 990 ]]> DataOutput_2 DataOutput_2 sequenceFlow_YMtfiw sequenceFlow_gXJm0w false false https://llama.cpp.imixs.com/ XML ]]> DataOutput_2 DataOutput_2 sequenceFlow_fN22Gg sequenceFlow_naZnAA {"n_predict": 2048, "temperature": 0 } ^.+\.([pP][dD][fF])$ [INST] Assign the invoice to one of the following categories: - Cargo-Invoice - in case the invoice is about cargo and logistic services - Credit - in case of a credit note - Invoice - in all other cases Extract also the company name and the language the invoice is written in. Note: The company name is the name of the company that issued the invoice document, not the recipient. The company name is usually at the beginning or end of the invoice document. Output the infromation as an XML object that has the following structure: Type Kraxi GmbH German Note: Do not generate any other information instead of the XML object. [/INST] ]]]]> ]]> false https://llama.cpp.imixs.com/ invoice.summary false ]]> DataOutput_2 DataOutput_2 sequenceFlow_8SpIiA sequenceFlow_A62nqQ {"max_tokens": 4096, "temperature": 0 } ^.+\.([pP][dD][fF])$ [INST] Summarize the data from this invoice document: - Company information - General Billing data - Invoice total information - Payment summary - Invoice items The company name is the name of the company that issued the invoice document, not the recipient. The company name is usually at the beginning or end of the invoice document. Summarize the invoice lines in a table. Use only the default values and do not perform any calculations, summing or changes to these values yourself. Format numbers and amounts according to ISO 4217. [/INST] ]]]]> ]]> _subject]]> _amount (Brutto € _amount_brutto) _description]]> home]]> false sequenceFlow_z8jotQ sequenceFlow_7ywCdA sequenceFlow_7ywCdA