<Government announces a:gusth will lead the way.
Features
Next generation interface for SAP
Direct API-access
NXTInterface supports secure access to external data sources via API (capture service provider, eMail inboxes, e-Invoice access points, InvoiceNxt, etc.)
SAP PI/PO and SAP BTP ready
NXTInterface prepared for SAP PO/PI and SAP BTP middleware
Storing of supplier invoice images via SAP ArchiveLink
All supporting documents and data are audit-proof stored and linked to all relevant SAP documents and reports. The images are linked to the SAP document upon creation, and can be retrieved from SAP
Storing of evidence files (e-Invoice) via SAP ArchiveLink
All supporting documents and data are audit-proof stored and linked to all relevant SAP documents and reports. The evidence files are linked to the SAP document, and can be retrieved from SAP
Matching of company code
NXTInterface uses invoice data to determine the relevant company code, minimizing the need of human intervention or the potential of human errors (not required if PO-based)
Matching of Supplier ID
NXTInterface uses current supplier master data to identify the supplier ID. Even suppliers that have been created moments ago, will be identified (not required if PO-based)
Matching of condition vendor ID
SAP allows to maintain so-called condition vendors. These are suppliers who contribute to the delivery of goods (like logistic partners) but are not the recipient of the purchase order. Often these condition vendors raise invoices directly with reference to the PO. In this case, it is important to compare the supplier ID as found per supplier master data matching with the PO-vendor, and in case of mismatch, validate the supplier ID found per supplier master data matching with any existing condition vendor, This can also help to identify certain PO line numbers (e.g., delivery costs)
Matching against PO line items
NXTInterface uses most current PO line item information to reliably identify and match PO line items. The matching is done based on current data (Mat Code, Unit price & quantity, line item description) and business rules (e.g. first in/first out). Even PO which have just been created can used for matching.
Matching of GR line items
NXTInterface uses most current GR data to match invoice line-items. The matching is done based on current data (Mat Code, Unit price & quantity, line item description) and business rules (e.g. first in/first out). Even PO which have just been created can used for matching.
Matching against Delivery Note
NXTInterface uses most current data to match the invoice line-items against DN line-items if a DN-reference can be found on the invoice. Matching agains a DN simplifies the matching process assuming that the DN-reference is kept as part of the GR posting. It simplifies also the accurate matching of invoices in case of deliveries and subsequent invoicing for multiple purchase orders.
Matching against the Bill of Lading (BOL)
NXTInterface uses most current data to match invoices against the Bill of Lading (document issued by the carrier or shipping company to confirm the receipt of goods for shipment). The matching is done based on current data (Mat Code, Unit price & quantity, line item description) and business rules (e.g. first in/first out). Even PO which have just been created can used for matching. The bill of lading often contains additional information used for matching (vessel name, port designation, container number, etc.).
Unplanned costs (delivery/material surcharges etc.)
Unplanned delivery costs, material surcharges create GL-lines in the SAP document
Coding proposals for Non-PO-invoices
NXTInterface proposes the line item coding for Non-PO-based invoices either based on supplier-specific templates (e.g. utility invoices) or historic postings. The former process is advisable for utility, telecom, or rent invoices which are regularly coded independently of their line-item structure. The mechanism for referencing historic postings are to search for past invoices of the same supplier in the past. If there are more than three past invoices, a proposal can be made if the latest and the third. fourth, or fiths invoice are coded identically. It is advisable to only make proposal in these cases, else the business user's experience will be more negative than positive.
Duplicate Check
NXTInterface provides a reliable, configurable duplicate check (default criteria: Supplier ID, Invoice Reference, Amount, and Document Date). It is especialy important to do the duplicate check in SAP to ensure that all invoices are considered (image-based, e-Invoices, portal invoices, and manual invoices).
Exception handling incl. image viewer
NXTInterface provides an intuitive exception handling process incl. access to all captured invoice-details incl. images allowing the verification of the captured data
One-time vendor
In case of Non PO-invoices, NXTInterface allows to select a one-time vendor if the supplier is not expected to raise any more invoices in the future.
Parking of all supplier invoices
NXTInterface parks all supplier invoices using standard SAP BAPIs, ensuring that all documents comply with the existing SAP customization and are reflected in standard SAP reports (…)
UserExits (SAP ABAP)
NXTInterface provides UserExits to add project-specific validations, substitution and or processing
Administrative monitoring
NXTInterface provides a detailed message log and exception handling for all API connectivity
Automatic confirmation (eMail)
NXTInterface creates personalized and specific email responses to suppliers in case invoices are received via email
Automatic rejection
NXTInterface creates personalized and specific email responses to suppliers in case invoices are received via email
[Creation of technical documents for legacy AP-automation solution]
NXTInterface can natively \create technical documents specific to legacy AP automation solutions via BAPI