SAP AP Automation that posts via BAPI — and keeps the audit trail

What it does

• Email and manual upload intake
• Azure Document Intelligence and Google Gemini OCR — per-tenant model pick
• Configurable approval workflow engine with SLA tracking
• 3-way match (PO, GR, invoice)
• Duplicate detection
• Tax-code determination
• BAPI_INCOMINGINVOICE_CREATE for the SAP posting itself
• 10-year retention with SHA-256 PDF hashing
• IP-stamped audit log per action
• SOX-grade audit reports exported as PDF

How invoices flow

A vendor emails a PDF invoice to your dedicated Fin4Sight inbox, or your AP clerk uploads one manually.

Fin4Sight extracts header, line items, tax codes, and PO references using Azure Document Intelligence or Gemini — your choice per tenant. Duplicates and bad data fail the validation pass before they reach an approver.

The approval workflow you configured routes the invoice through the right people. SLAs track delays. Once the last approver clicks approve, Fin4Sight posts the invoice to SAP via BAPI_INCOMINGINVOICE_CREATE.

Every step gets logged: who, when, from which IP. The PDF is SHA-256 hashed at intake and at posting. The whole trail is retained for 10 years and available as a SOX-grade PDF report.

The audit trail

Inside Fin4Sight: a complete state machine per invoice from intake to posting, with user, timestamp, IP, and prior-state on every transition. PDF hashes prove the file at posting matches the file you received. Reports export to PDF and XLSX.

Inside SAP: postings arrive via BAPI_INCOMINGINVOICE_CREATE — standard, traceable, and indistinguishable from any other BAPI-posted invoice. Your existing SAP audit and reconciliation processes don't change.

AI choice and accuracy

OCR is multi-provider: Azure Document Intelligence and Google Gemini both run as live adapters. Pick per tenant; switch when needed.

Numeric values extracted from the OCR pass are validated against the underlying document. Narrative summaries (if you ask the platform to explain why a particular invoice was flagged) are checked against the source data — a >5% drift gets the narrative rejected before it shows up in the UI.

What's coming on the AP roadmap

Coming soon: Vendor Portal, expanded Expense Management, Sales Order Automation, Tender, and Dunning module polish. Ask us about pilot access if any of these are on your timeline.

Frequently asked questions

Does the AP module work with SAP ECC and S/4HANA equally?

Yes. The web app talks to both via OData and BAPI; the posting transaction (BAPI_INCOMINGINVOICE_CREATE) exists in ECC and S/4HANA.

Can I customize the approval workflow per CompanyCode?

Yes. Approval workflow is configurable per CompanyCode. SLAs are tracked per workflow step.

What OCR providers are supported?

Azure Document Intelligence and Google Gemini, with per-tenant selection.

How long is invoice data retained?

10 years. Every PDF is SHA-256 hashed; every action is IP-stamped in the audit log. Exports include SOX-grade PDF reports.