SAP-samples/btp-cap-dox-invoice-validation

Facilitate Invoice Validation — leveraging Document Information Extraction

Invoice validation is often an opaque, manual, and error-prone process. It involves editing invoice PDF files directly, or sending them back and forth via email between multiple parties— until the invoice can finally be approved for payment.

This sample tries to alleviate some of those pain points. It presupposes a clearly defined validation workflow. More importantly, it simplifies and accelerates validation, allowing you to: copy over entries from the original invoice; correct entries; and then forward the invoice to the next person in line in the workflow to validate it further. As a side effect, each correction and the rationale behind it is documented over time. To get an overview, please checkout the teaser video for this sample.

This invoice validation leverages Document Information Extraction (DOX) —a service on the Business Technology Platform (BTP)— and the Cloud Programming Model (CAP). The sample runs entirely on BTP. Think of it as a separate extension to SAP Central Invoice Management (CIM) or OpenText Vendor Invoice Management (VIM), rather than it trying to compete with the latter.

Important

The sample was built on AWS infrastructure on BTP. Therefore, we went with the Amazon S3 variant of the BTP Object Store service, while the CAP backend talks to the S3 via the AWS Client S3 SDK. Generally, the sample can also be run on GCP or Azure, if you slightly adjust the part of the code that talks to the Object Store, and use the corresponding store variant.

Sample architecture with DOX and CAP at its core

Getting started

Feel free to check out these links to get started working with the sample.

• Intro
  • Scenario
  • Improvements
  • Interaction
• Setup
  • Subaccount
  • Initial Deployment
  • Extensions
• Integration
  • Inbound
  • Outbound
  • Notifications

Known Issues

No known issues as of now.

How to obtain support

Create an issue in this repository if you find a bug or have questions about the content.

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2024 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.