Skip to content
ISIS Consultancy

MM · FI · e-FaturaECC · S/4HANA

ISIS OMU – Automatic e-Invoice Posting

Pulls incoming e-invoices from the integrator, parses the UBL content, matches them by rules and posts them automatically as goods or service invoices in SAP.

Request a demo
Modules
MM · FI · e-Fatura
Platform
ECC · S/4HANA
Outcome
Incoming e-invoices are matched by rules and posted automatically

Overview

ISIS OMU (Automatic Posting) removes manual processing of incoming e-invoices in SAP. The invoice is retrieved from the integrator, its content is parsed, the accounting path is determined according to your company’s rules, and it is posted as a standard SAP document. The accounting team only deals with invoices that do not match a rule or are waiting for approval.

The solution runs inside SAP: there is no separate application, no second database and no invoice copy kept outside. The posting result consists of standard MM and FI documents; your existing reports, payment processes and audit trails remain unchanged.

How it works

  • Retrieval: Invoices from the integrator system are pulled with a status filter; re-reading a single invoice and direct import from a UBL file are also supported.
  • Parsing: UBL-TR header, line, tax, withholding, order and delivery references are mapped to SAP fields; unit conversions use defined tables.
  • Posting code determination: Rules are tried in order based on sender tax number, company code and invoice content; the first matching rule selects the posting code and accounting path.
  • Field engine: Tax code, cost centre, account and date fields are filled by rules; SQL-based and conditional rules can be defined.
  • Reference matching: The purchase order and goods receipt are found, reference amounts are calculated and differences are reported.
  • Approval and posting: If an approval process is defined, the invoice goes to approval; approved invoices and those not requiring approval are posted automatically.

Posting paths

  • Order-related goods and service invoices (MM logistics invoice verification)
  • Non-order expense invoices (FI vendor invoice)
  • Invoices with withholding tax and exemption codes
  • Blocking and warnings for invoices with price and quantity differences
  • Return and correction invoices

Configuration and rules

  • Posting code rules per company code, priority order and default paths
  • Field-level fill rules: fixed value, lookup table, SQL query, conditional expression
  • Manual change protection: user corrections are not overwritten in the next automatic run
  • Approval limits and approver assignment rules
  • Unit, currency and tax code conversion tables

Reports and monitoring

  • Incoming invoice list: status, posting code, accounting document, error reason
  • Status log: which step each invoice passed through and who changed it
  • Unmatched and pending-approval invoices
  • Automatic posting rate and number of manual interventions per period

Integrations

  • E-invoice integrators (adapter structure)
  • File-based matching of import invoices with the ISIS Foreign Trade Solution
  • Payment and reconciliation tracking with ISIS Bank Integrations
  • Standard SAP approval workflow

Frequently asked questions

Which e-invoice integrators does it work with?
The solution is built on an integrator-independent adapter structure; the retrieval adapter for your integrator is activated within the project. Because incoming invoices are read from the UBL-TR schema, the product side does not depend on the integrator.
Does it replace standard SAP invoice entry?
No, it produces standard SAP accounting documents. OMU retrieves and matches the invoice and applies posting rules; the result is still a standard MM/FI document visible in standard reports.
What happens to unmatched invoices?
Invoices without a matching rule or requiring approval wait in the list; the user selects the posting code or corrects the fields. Manually changed fields are preserved in subsequent automatic runs.
Is it compatible with S/4HANA?
The solution runs on SAP ECC and S/4HANA; because it uses standard document interfaces, version upgrades do not require a rewrite.

Let's talk about your SAP project.

Tell us what you need and we will map a path that fits your existing system. The first meeting and demo are free.

Contact us +90 (216) 740 02 61