Automated Supplier Invoice Synchronization via Pre-Validated Payment Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing e-procurement systems face security threats and inefficiencies due to manual processes in supplier invoice generation, particularly when supplier payment information changes, leading to potential unauthorized transactions and increased labor costs for verification.

Innovation Solution

An automated system that pre-populates supplier invoices with validated payment information by linking buyer and supplier accounts through a mapping table, ensuring secure and efficient transactions by verifying supplier payment information and updating it upon changes, thus reducing the need for manual entry and verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual verification of supplier payment information is performed, then security against unauthorized transactions is improved, but labor costs and processing time increase

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining pre-validated supplier payment information in a database before transactions occur. When an invoice is generated, the system automatically retrieves and verifies payment information from this pre-validated database, eliminating the need for manual verification during each transaction process while maintaining security standards.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If manual entry of supplier payment information is required, then accuracy of payment data is improved, but productivity and efficiency decrease

Engineering Contradiction:
ImproveaccuracyVSAvoidefficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system enables self-service by automatically retrieving validated payment information from its database and populating invoice documents without requiring manual data entry. The system serves itself by maintaining its own validated payment information repository and using it to automatically complete future invoices, thereby maintaining accuracy while dramatically improving efficiency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system creates and stores copies of validated supplier payment information in a database. These copied records are then reused across multiple invoice generations, eliminating the need to re-enter payment information manually for each transaction while ensuring consistency and accuracy through the use of pre-validated data.

Inventive Principle:
Principle #26Copying

3Productivity

If automated invoice generation is implemented, then productivity is improved, but security risks from unauthorized transactions increase

Engineering Contradiction:
ImproveproductivityVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback mechanisms by maintaining a database of pre-validated supplier payment information that is updated and verified through controlled processes. The automated invoice generation system continuously references this validated database, and the system includes procedures for updating validation information when changes occur, ensuring that automation maintains security through ongoing verification feedback.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11514488B1Automatic synchronization of payment data across distributed systems
Publication Date: 2022.11.29 COUPA SOFTWARE INC
  • US11514488B1 patent drawing
  • US11514488B1 patent drawing
  • US11514488B1 patent drawing

AI summary

In an embodiment, a computer-implemented method comprises receiving supplier invoice data comprising one or more supplier payment objects corresponding to a supplier to a customer of a supplier-customer transaction. A match determination is made between the supplier payment object and a verified payment object. In response to a no-match determination, a customer transaction system is queried to validate the supplier, and in response to the supplier validation, a validation payment object is created, validating the supplier. A match determination is made between the supplier payment object and the verified payment object, and the supplier invoice is automatically generated. In response to receiving subsequent supplier invoice data corresponding to the supplier of subsequent supplier-client transactions, for each subsequent supplier-client transaction, the subsequent supplier invoice is automatically generated with the verified payment object.