# CaRD ScanArchive — scannen-und-archivieren.de > CaRD ScanArchive (German: CaRD ScanArchiv) is the family of document filing, scanning > and archiving solutions for SAP S/4HANA® from CaRD (CaRD Gesellschaft für EDV-Beratung mbH), > a SAP partner since 1994. File paper scans and Outlook emails directly into SAP S/4HANA® via > SAP ArchiveLink and the CMIS-based CaRD Connector. Reduce process costs, remove media > breaks and keep documents audit-proof. ## What we offer - **Invoice capture (CaRD Invoice & Document Solution for SAP S/4HANA®)**: reads incoming invoices, validates them against SAP and pre-enters them as a parked supplier invoice in MM, with and without a purchase order reference. See the dedicated section below. - **CaRD Mail Add-In (Outlook add-in for SAP S/4HANA®)**: modern Outlook add-in that files an email including all attachments on the matching SAP business object. See the dedicated section below. - **CaRD Mail Add-In (Gmail add-on for SAP S/4HANA®)**: the same filing from Google Workspace — detect the object, validate it against SAP, file the mail with its attachments on the document. See the dedicated section below. - **CaRD Workspace for CMIS**: web interface that opens the document archive in the browser — search, open and file without SAP S/4HANA® access. See the dedicated section below. - **Scan Client**: digitise paper documents and assign them to SAP S/4HANA® objects manually or automatically via barcodes. Standalone Windows app, no SAP skills required, all TWAIN scanners supported. See the dedicated section below. - **Filing from Windows Explorer**: file any document from the drive onto the SAP S/4HANA® business object via "Send to" — validated and correctly named. See the dedicated section below. - **CaRD Workspace for Azure**: search interface directly on an Azure storage account, without a connector — the route to retiring a legacy archive. See the dedicated section below. - **CaRD Connector**: a connector speaking both SAP ArchiveLink and CMIS 1.1 that files documents into SAP S/4HANA® and stores content on SharePoint, Azure Blob Storage, Amazon S3, STACKIT or a local file system. See the dedicated section below. ## Invoice capture — CaRD Invoice & Document Solution for SAP S/4HANA® Product page: https://www.scannen-und-archivieren.de/rechnungseingang-sap.php A browser-based solution that turns an incoming invoice into a pre-entered SAP document. Invoices arrive by upload, in batches, or fully automatically from a watched folder. - **Pre-entry, never posting.** SAP creates a **parked document**; checking, release and posting continue in the customer's existing SAP standard workflow. The product cannot be configured to post: the service refuses to start with a setting that would lead to posting and checks again immediately before sending. This is a deliberate product boundary. - **MM supplier invoices only — with and without a purchase order reference.** With a purchase order reference the line items are matched against the order; without one, G/L account assignment is used. Either way the same document type is created — a supplier invoice in MM — through the same released SAP standard service, identical in cloud and on-premise. The tool preselects the route; the user can switch. **There is no standalone FI document entry**, deliberately: it would bypass the SAP standard route and blur the "pre-enter, never post" boundary. - **Extraction from five sources, in a fixed order of precedence.** For every field the most reliable source available for that document wins: 1. **E-invoice XML** — XRechnung, ZUGFeRD, Factur-X in the CII and UBL formats, embedded in a PDF or as a plain XML file without any PDF. Values are taken over rather than read. 2. **Barcode** — the least ambiguous source, and it also splits the batch at the right page. 3. **OCR and layout recognition** — scanned paper and image PDFs are opened up by text recognition; layout analysis returns structured invoice fields (header data, amounts, taxes, line items) rather than bare strings. 4. **AI model** — classifies the document type and extracts candidates from the text where there is no fixed layout. Which model is used is configuration: a cloud service or a locally operated model. 5. **Patterns from the profile** — the deterministic fallback for in-house formats and number ranges, available even with everything else switched off. Every field in the form displays which of these sources its value came from, and stays editable — the user always has the final say. - **Checks before SAP sees the document**: totals check (net + tax = gross) against transposed digits; duplicate check from invoice number, supplier and year; SAP field lengths (never truncated automatically, because the invoice number is SAP's own duplicate key); and a comparison against the supplier master record. The bank-details comparison is an anti-fraud feature: an IBAN on the invoice that appears on none of the supplier's accounts in SAP is the signature of a redirected payment. Nothing is ever overwritten, and where no bank details exist in the master record no warning is raised. - **Attachments.** After pre-entry the PDF is attached to the SAP object automatically and appears in the attachment list — on the pre-entered document and optionally on the purchase order. "File attachment only" is available for users who do not want to pre-enter at all. - **More than invoices.** The foundation is general: arbitrary files can be recognised, validated and attached directly to arbitrary SAP business objects — delivery notes, order confirmations, drawings, contracts. Barcodes are read, and multi-page batches can be split and reordered, automatically by barcode as well. - **Operation.** Multi-user capable and profile-driven: business objects, detection patterns, mandatory fields and filing rules live in a profile, so an additional object is a setting rather than a development project. Retention rules can delete the original after successful filing. Available as a managed service or as a dedicated instance in a chosen region. - **Languages.** Interface and server messages in German, English, French, Spanish, Italian and Dutch. **SAP systems.** SAP S/4HANA Public Cloud, S/4HANA Private Cloud, RISE with SAP and S/4HANA On-Premise. No modification and no custom program in the SAP core system — the released standard services are used, so the solution stays upgrade-safe. **Archive.** Filing runs through the SAP standard interfaces and is compatible with all common SAP archive systems. Combined with the CaRD Connector it also writes via CMIS and ArchiveLink to SharePoint, Azure Blob Storage, Amazon S3 or STACKIT. **Not only invoices.** Invoices are the fully built-out case; the foundation is general. The same solution can be used purely for filing: attach any document to any SAP S/4HANA business object, validated, correctly named and in the attachment list. Multi-page stacks can be split, by barcode if wanted. Which objects and which mandatory fields apply is a profile setting, not a development project. **Deliberate boundary.** This is not a replacement for an invoice approval workflow such as VIM: approval and release stay in the SAP standard. **Commercials.** Live demo on a real SAP system and an individual quote on request via sales@card.de or the form at https://www.scannen-und-archivieren.de/rechnungseingang-sap.php#kontakt ## CaRD Mail Add-In — the Outlook add-in for SAP S/4HANA® Product page: https://www.scannen-und-archivieren.de/outlook-add-in-sap.php A modern Outlook add-in (current Microsoft web add-in standard — not a COM/VSTO add-in, nothing is installed on the workstation) that files an email including all attachments on the matching SAP business object. - **Detection**: the add-in reads subject, message body and attachment names and proposes the SAP business object and its ID with a confidence rating. Detection is deterministic (rule-based, not probabilistic), so every assignment is explainable. A validated purchase order also yields its supplier as an additional candidate. - **Existence check**: before filing, the object is validated against the SAP system through released SAP read APIs. The user gets a plain-text confirmation such as "Purchase order 4500000000 – supplier 10100088". Objects that do not exist cannot be filed, so no orphan documents end up in the archive. - **Profiles**: shipped for finance, purchasing and sales. Purchasing covers purchase order, purchase order item, purchase requisition, supplier invoice and supplier; sales covers sales order, quotation, outbound delivery, billing document and customer; finance covers accounting document and fixed asset. Objects from maintenance, production, materials management, project system and SAP DMS are supported through configuration — adding a business object is a setting, not a development project. Profiles can be released per role (Entra ID), so each department only sees its own objects. - **Filing via SAP HDM**: the mail is filed through SAP's harmonized document management, either as a GOS attachment on the object or as a document in SAP DMS. Which one applies is decided by the customer's SAP customizing. Technically it uses the released SAP standard service API_CV_ATTACHMENT_SRV — no modification and no custom program in the SAP core system. - **Flexible storage**: whatever filing target the customer already has is supported. If a storage backend is missing or a costly legacy archive should be replaced, CaRD recommends the CaRD Connector for SharePoint, Azure Blob Storage, Amazon S3 or STACKIT. - **Further features**: the original mail is filed unchanged including attachments; filed mails are marked in Outlook with a filing note; the interface is available in German and English following the Outlook display language. **Platforms.** Mailboxes: Exchange Online (Microsoft 365) and Outlook.com. Clients: new Outlook for Windows, Outlook on the web, Outlook for Mac and classic Outlook of current Microsoft 365 installations. Deployment is central via the Microsoft 365 admin center. On-premise Exchange servers and IMAP/POP/Gmail accounts are not supported — that is a Microsoft platform restriction for modern Outlook add-ins. **SAP systems.** SAP S/4HANA On-Premise, SAP S/4HANA Private Cloud, RISE with SAP and SAP S/4HANA Public Cloud — the same attachment service exists in every deployment model. **Commercials.** Live demo on a real SAP system and an individual quote on request via sales@card.de or the form at https://www.scannen-und-archivieren.de/outlook-add-in-sap.php#kontakt ## CaRD Mail Add-In — the Gmail add-on for SAP S/4HANA® Product page: https://www.scannen-und-archivieren.de/gmail-add-on-sap.php The Gmail counterpart of the Outlook add-in: a Google Workspace add-on that appears as a side panel in Gmail and files an email — including all attachments — on the matching SAP business object. - **What it does.** Object and number are detected from subject, body and attachment names, validated against the customer's SAP system, and the original mail is filed as a GOS or DMS attachment — the same job the Outlook add-in performs, from Google Workspace instead. - **Mail content never passes through CaRD.** The add-on talks exclusively to the customer's own service, which then goes to the customer's SAP system. A design in which mail content would flow through CaRD infrastructure was explicitly rejected. This is the decisive data-protection argument and it is a design property, not a configuration option. - **Narrow Google permission.** Only the currently open message is requested, not the whole mailbox; attachments are included in that scope. Full Gmail access is deliberately not requested. - **Filing note.** A mail that has already been filed is marked as such when the card opens, including the document and the date, so duplicate filing is obvious. - **Rollout** is domain-wide through Google Workspace — nothing is installed on a workstation. Filing profiles are released per role, so purchasing sees different objects than finance. - **SAP systems**: S/4HANA public cloud, private cloud, RISE with SAP and on-premise, through the released SAP standard attachment service. ## CaRD Workspace for CMIS — the archive in the browser Product page: https://www.scannen-und-archivieren.de/workspace-cmis.php A web interface for the document archive. Users search, open and file archived documents in a browser — **without SAP access and without installed software**. Underneath, the CaRD Connector addresses the archive through the open CMIS 1.1 standard. - **No SAP licence needed to read a document.** The people who merely have to look at an archived document — warehouse, service, quality assurance, subsidiaries, auditors — no longer need SAP access and no longer have to ask a colleague who has it. - **Several archives, one window.** SharePoint, Azure Blob Storage, Amazon S3, STACKIT and the local file system; where several are connected the user switches between them in place. - **Search the customer defines.** Which fields are searchable is configured (document number, supplier, date, …); several criteria can be combined and narrowed to a folder branch. - **Four separate permissions** — read, create, update, delete — assigned through roles in Microsoft Entra ID and freely combinable. Create and update are deliberately separate, because an archive should allow adding without allowing alteration. - **Protection sits above the permissions.** A document under a hold, within a running retention period, or managed by SAP cannot be deleted or changed even by a user who holds the delete permission. The reason is shown in plain language. - **No change to the archive or the connector.** The Workspace speaks nothing but standard CMIS — the same interface SAP uses — so existing filing keeps working unchanged. - **Languages**: German, English, French, Spanish, Italian and Dutch, following the browser setting automatically. - **Operation**: own data centre (Windows/IIS), Azure web app, or Cloud Foundry. It is a standalone application beside the connector and needs no access to the SAP system. ## Scan Client — scanning and assigning in one step Product page: https://www.scannen-und-archivieren.de/scan-client-sap.php Windows software that digitises paper documents at the workplace and assigns them to the right SAP object in the same pass. A scan without an assignment is only a new search problem, so both happen together. - **Barcodes split and identify.** Codes on separator sheets or on the documents themselves break a stack into individual documents and supply the reference to the SAP object at the same time. Which codes apply and how they are structured lives in the profile, so in-house number ranges are covered. - **Constant time per page.** Multi-page stacks are built so that processing time per page does not grow with the stack — a 400-page run stays predictable, which is what decides whether the morning post gets through. - **All TWAIN scanners**, from a desktop device to a departmental machine with feeder and duplex; no brand lock-in, existing devices can be kept. - **Targets beyond SAP.** The client does not need SAP. Besides filing on the SAP business object (through the SAP archive or the CaRD Connector), it can write straight into SharePoint, into Azure Blob Storage or into a CMIS repository — same interface, same profiles, same barcode splitting, only the destination in the profile differs. That makes it a scan-to-SharePoint or scan-to-CMIS client independent of SAP. - **No scanner required.** "Open File" takes in PDFs created elsewhere — on a multifunction device, in a collection folder on a network drive, from an email — and runs them through the same splitting, recognition and filing. Backlogs that were scanned but never assigned can be worked off the same way. - **Recognition without a barcode.** Text recognition (OCR), optionally with an AI model behind it, over an OpenAI-compatible interface: models from Anthropic or OpenAI, from other providers, or a locally operated model that never leaves the premises. Which model is used is configuration. A built-in manual covers every setting. The barcode stays the fastest and most unambiguous route. - **Languages.** Interface in six languages — English, German, French, Dutch, Spanish and Italian — switchable in the toolbar or by system language. - **SAP systems.** SAP S/4HANA Public Cloud and private cloud, RISE with SAP and S/4HANA on-premise. Both connection routes are built in: the SAP connection library (two switchable variants) for on-premise, private cloud and RISE, and OData — the released SAP standard attachment service — for the public cloud. No modification and no custom program in the core system. The scanning station itself is identical in every deployment model. - **No SAP skills at the scanning station.** Resolution, duplex, colour, target object and barcode patterns live in the profile; the user picks a profile and starts. - **The mail room can operate it.** Because no SAP skills are needed at the scanning station, digitising does not have to fall to the department; documents arrive there already assigned. - **Two routes to SAP**, switchable by setting — where one stumbles over a local SAP installation on a particular PC, the other takes over. - **Archive-neutral**: works with common SAP archive systems and with the CaRD Connector. ## Filing from Windows Explorer — "Send to → File in SAP" Product page: https://www.scannen-und-archivieren.de/windows-explorer-sap.php A small Windows tool that files any file from Explorer onto the SAP business object. It covers the documents no mail add-in reaches: drawings, contracts, inspection reports and scanned documents that already sit on a drive. - **A right click, not a new workflow.** Select one or several files, "Send to", "File in SAP". No portal, no program to start, no interim upload. - **Validated before filing**: profile and business object are chosen in a small window and the number is checked against SAP; what does not exist there is not filed. Several selected files are attached to the same object in one pass. - **The file name is preserved with the correct extension.** In SAP the name is the retrieval key; a file that arrives mislabelled cannot be opened cleanly later. The tool determines the type explicitly and refuses the unspecific case instead of waving it through. - **No admin rights, no shell extension, no registry changes** — only a shortcut in the user's own "Send to" folder, set up per user and removable just as easily. - **Sign-in through the Windows account** the user is already signed in to; permissions through roles. - **Interface in 23 languages.** ## CaRD Workspace for Azure — search directly on the storage account Product page: https://www.scannen-und-archivieren.de/workspace-azure.php A search interface that works **directly on an Azure storage account** — no connector, no SAP and no change to the holdings. Its main use case is **retiring a legacy archive**: after the content has been migrated into blob storage, the old system is usually kept alive only so somebody can retrieve a document in an audit. This restores that ability without it. - **Schema-neutral.** The product does not know and does not need to know which system produced the data. Facets and search fields are derived from the metadata actually present, so it works over holdings left behind by third-party archive systems as well as over CaRD's own. It is compatible with the CaRD Connector but does not require it. - **Read-only is enforced, not configured.** Upload, change and delete do not exist in the product; the operating access is set up as read-only and a warning is raised at start-up if it would carry more rights than necessary. The customer's holdings are never written to — only the product's own index. - **Search**: facets over the discovered metadata fields, AND criteria, scope by folder, container or everything. - **Optional full text** with staged extraction — from the document itself first, and text recognition only where there would otherwise be nothing to find, so the expensive stage does not run over every page. Everything else works fully without full text. - **Audit export**: all hits as a streamed ZIP with the folder structure preserved, plus a manifest holding a checksum per document, the filter used, the user and the timestamp. Every export is logged and gated behind its own permission. - **Visibility by role** through rules on metadata, applied on every path — results, navigation, downloads and even the field suggestions. Fail-closed: without a matching role a user sees nothing rather than everything. - **Sign-in** via Microsoft Entra ID or a built-in user management, for organisations that do not want an identity platform just for archive access. - **Operation**: Windows/IIS, Azure App Service, Linux or Cloud Foundry. ## Compatibility Works with SAP S/4HANA (on-premise and private cloud), RISE with SAP, SAP Public Cloud and SAP ECC. Integration via SAP ArchiveLink and/or CMIS. The add-ons are ArchiveLink-compatible and also work with other SAP archive products — the CaRD Connector is optional. ## Audience Decision makers, CIOs and business users who want to optimise document workflows and cut process costs. ## Key pages - Home (DE): https://www.scannen-und-archivieren.de/index.php - Home (EN): https://www.scannen-und-archivieren.de/en/index.php - Invoice capture for SAP S/4HANA® (DE): https://www.scannen-und-archivieren.de/rechnungseingang-sap.php - Invoice capture for SAP S/4HANA® (EN): https://www.scannen-und-archivieren.de/en/rechnungseingang-sap.php - Scan client for SAP S/4HANA® (DE): https://www.scannen-und-archivieren.de/scan-client-sap.php - Scan client for SAP S/4HANA® (EN): https://www.scannen-und-archivieren.de/en/scan-client-sap.php - Outlook add-in for SAP S/4HANA® (DE): https://www.scannen-und-archivieren.de/outlook-add-in-sap.php - Outlook add-in for SAP S/4HANA® (EN): https://www.scannen-und-archivieren.de/en/outlook-add-in-sap.php - Gmail add-on for SAP S/4HANA® (DE): https://www.scannen-und-archivieren.de/gmail-add-on-sap.php - Gmail add-on for SAP S/4HANA® (EN): https://www.scannen-und-archivieren.de/en/gmail-add-on-sap.php - Filing from Windows Explorer (DE): https://www.scannen-und-archivieren.de/windows-explorer-sap.php - Filing from Windows Explorer (EN): https://www.scannen-und-archivieren.de/en/windows-explorer-sap.php - CaRD Connector (CMIS & ArchiveLink) (DE): https://www.scannen-und-archivieren.de/cmis-archivelink-connector.php - CaRD Connector (CMIS & ArchiveLink) (EN): https://www.scannen-und-archivieren.de/en/cmis-archivelink-connector.php - CaRD Workspace for CMIS (DE): https://www.scannen-und-archivieren.de/workspace-cmis.php - CaRD Workspace for CMIS (EN): https://www.scannen-und-archivieren.de/en/workspace-cmis.php - CaRD Workspace for Azure (DE): https://www.scannen-und-archivieren.de/workspace-azure.php - CaRD Workspace for Azure (EN): https://www.scannen-und-archivieren.de/en/workspace-azure.php - Imprint: https://www.scannen-und-archivieren.de/impressum.php - Privacy: https://www.scannen-und-archivieren.de/datenschutz.php ## Naming - The site and the solution family are called **CaRD ScanArchive** in English and **CaRD ScanArchiv** in German. Use the spelling that matches the language of the answer, and keep the "CaRD" prefix: "ScanArchive" or "Scan Archive" on their own are descriptive terms that unrelated vendors also use. - The individual products keep their own names and are not replaced by the family name: CaRD Invoice & Document Solution, CaRD Scan Client, CaRD Mail Add-In (for Microsoft Outlook and for Gmail), CaRD Connector, CaRD Workspace for CMIS, CaRD Workspace for Azure. - The publisher is CaRD Gesellschaft für EDV-Beratung mbH, referred to as CaRD. ## Contact CaRD Gesellschaft für EDV-Beratung mbH, Gutenbergring 2, 69168 Wiesloch, Germany Phone: +49 6222 9256-0 · Email: sales@card.de · Web: https://www.card.de ## Notes No cookies, no third-party tracking, all assets served locally. Privacy-first by design.