When extracting documents using OpenText Intelligent Capture for SAP Solutions (IC4S) or OpenText Core Capture for SAP Solutions (CC4S), the standard setup determines the company code based on document content.

This is typically done via the staging table /OTX/PS00_T_STG3, which contains company-code–specific master data such as addresses, bank details, and tax IDs.

This approach makes sense when there is a joint inbox for all company codes and in case you want to detect documents sent to the wrong inbox. In that case, content-based determination is both logical and necessary.

VIM Authoirzation can play against this logic as users assigned to company code 1000 might not be able to see an invoice sent to company code 1000 but is actually for another company code.

A cleaner approach: fixed company code per inbox

In a setup where you are using one email address per entity you can remove the determination from the process and assign a fixed company code per ArchiveLink Document Type or E-Mail Address.

In this scenario a invoice sent to the wrong company code would be rejected and sent again to the correct inbox.

How to configure a fixed company code in Capture

Go to T-Code /otx/pf00_img

Navigate to OpenText Vendor Invoice Management Foundation > Inbound Configuration > Capture > Information Extraction Service > Capture Profile Maintenance.

Navigate to Entity Key Assignment, ignore any messages saying that the client is not modifiable:

Add your Capture Profile, the field ‘CompanyCode‘, the Company Code value (e. g. 2000) in Entity Key and other determination factors in the table:

In scenarios where one company code has one ArchiveLink Document Type it is possible to use a wildcard (*) for both email address of sender and recipient.

In many systems, this configuration:

• Works without a transport request
• Can be maintained directly in QA and Production

(As always: follow your internal governance rules.)

Official Documentation

For official documentation please refer to chapter Maintaining entity key assignment in OpenText Vendor Invoice Management for SAP Solutions: Configuration Guide for Foundation.

Final thought

Content-based company code determination is powerful – but not universally the best path.

If your organizational structure already guarantees the correct legal entity at the inbox level, removing unnecessary “intelligence” can actually make the process more stable, more transparent, and easier to support.

Sometimes the best optimization is knowing when not to optimize.