ALPLA Werke Alwin Lehner GmbH & Co KG

Central processing of incoming invoices

Become a reseller

Network of partners

Stories

The Company

ALPLA is a global leader in the field of plastic packaging. Its core business involves the design development and manufacturing of plastic packaging. The company operates 190 facilities in 46 countries worldwide and employs over 23,300 people (as of 2022).

The Challenge

- Incoming invoices mostly in paper form

- Incoming invoices distributed across respective German facilities
- Central invoicing system (FIBU)
- Central document capture challenging

- Prescribed interfaces require reverse engineering

- Timely processing required

The
Solution

...is an automatic document capture system within the central in-house financial accounting (FIBU) system.

For this purpose, sermocore creates a specialized HTTP interface via reverse engineering, which sends OCR-scanned incoming invoices as booking entries to the in-house sermocore platform. This platform has been embedded in ALPLA's infrastructure since 2011 and is currently operational with multiple detached instances, each tailored to specific application areas. Acting as a central data hub within the company, the sermocore platform filters, processes, and converts document data, which is then transmitted to the central FIBU system via web service. The transmission operates fully automatically, monitored at system and process levels, and runs nearly in real-time.

ZITAT

"As a software developer, I was pleasantly surprised by how quickly and smoothly we were able to implement the solution despite the technically challenging requirements."

Stefan Müller,
Corporate IT Supply Chain Engineer ALPLA

weitere Partnerstories

This website uses cookies. Those have two functions: On the one hand they are providing basic functionality for this website. On the other hand they allow us to improve our content for you by saving and analyzing anonymized user data. You can redraw your consent to using these cookies at any time. Find more information regarding cookies on our Data Protection Declaration and regarding us on the Imprint.

Mandatory

These cookies are needed for a smooth operation of our website.

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your consent to using cookies.	1 year	HTML	Website
fe_typo_user	Assigns your browser to a session on the server.	session	HTTP	Website

Marketing

With the help of these cookies we strive to improve our offer for our users. By means of anonymized data of website users we can optimize the user flow. This enables us to improve ads and website content.

Name	Purpose	Lifetime	Type	Provider
_dc_gtm_--property-id--	Used by DoubleClick (Google Tag Manager) to help identify the visitors by either age, gender or interests.	1 minute	HTML	Google
_hjClosedSurveyInvites	Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.	1 year	HTML	Hotjar
_hjDonePolls	Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.	1 year	HTML	Hotjar
_hjMinimizedPolls	Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.	1 year	HTML	Hotjar
_hjShownFeedbackMessage	Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.	1 year	HTML	Hotjar
_hjid	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.	1 year	HTML	Hotjar
_hjRecordingLastActivity	This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).	1 session	HTML	Hotjar
_hjTLDTest	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	1 session	HTML	Hotjar
_hjUserAttributesHash	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.	1 session	HTML	Hotjar
_hjCachedUserAttributes	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.	1 session	HTML	Hotjar
_hjLocalStorageTest	missing translation: trackingobject._hjLocalStorageTest.desc	1 session	HTML	Hotjar
_hjIncludedInPageviewSample	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.	30 minutes	HTML	Hotjar
_hjIncludedInSessionSample	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.	30 minutes	HTML	Hotjar
_hjAbsoluteSessionInProgress	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.	30 minutes	HTML	Hotjar
_lfa	cookie to to store and track audience reach	2 year	HTML	Leadfeeder

ALPLA Werke Alwin Lehner GmbH & Co KG

The Challenge

PROJEKTTAGS

TheSolution

ZITAT

PROJEKT
TAGS

The
Solution