Quartz 4

Invoice

2 min read

Invoice

What is this?

An Invoice in SAP S/4HANA represents a request for payment from a supplier for goods or services provided.

It is the document that:

  • Confirms financial liability
  • Triggers accounting entries
  • Completes the procurement cycle

Why it exists?

After goods/services are received, the supplier demands payment.

The invoice ensures:

  • What was ordered = what was received = what is billed
  • Financial records are updated
  • Payments are controlled

Invoice verification is used to check the accuracy of supplier invoices in terms of quantity, price, and content. :contentReference[oaicite:0]{index=0}

Structure

An Invoice has:

1. Header (overall info)

  • Supplier (Business Partner)
  • Invoice date
  • Total amount
  • Currency

2. Line Items

  • Material / Service
  • Quantity
  • Price
  • Tax
  • Account assignment

Each item corresponds to PO / GR references.

Key Concept: Invoice Verification

Invoice is NOT blindly accepted.

SAP performs:

3-Way Match

  • Purchase Order (PO)
  • Goods Receipt (GR)
  • Invoice

System checks:

  • Quantity match
  • Price match
  • Supplier match

If mismatch: → Invoice is blocked
→ Payment cannot proceed

Invoice verification ensures accuracy and creates accounting postings automatically. :contentReference[oaicite:1]{index=1}

Types of Invoices

1. PO-Based Invoice

  • Linked to Purchase Order
  • Most common

2. GR-Based Invoice

  • Linked to Goods Receipt
  • Used for partial deliveries

SAP allows invoice reference directly to goods receipt in GR-based verification. :contentReference[oaicite:2]{index=2}

3. Non-PO Invoice

  • No purchase order
  • Used for one-off expenses

Example:

  • Services
  • Fees
  • Misc payments

In Oracle

Typical behavior:

  • Invoice loosely linked to PO/receipt
  • Matching may be optional
  • Finance often handles separately

In S/4HANA

  • Strong integration with MM + FI
  • Invoice posting creates:
    • MM document
    • FI accounting document

Invoice verification is the final step in the procure-to-pay cycle and updates financial records. :contentReference[oaicite:3]{index=3}

Mapping Logic

→ Invoice_Mapping

Core idea:

  • Oracle Invoice → SAP Invoice
  • But must align with:
    • PO
    • GR
    • BP
    • Material

Process Impact

→ P2P_Procure_to_Pay

Invoice:

  • Confirms liability
  • Enables payment
  • Updates accounting

Without valid invoice: → No payment
→ Financials incomplete

Validation

→ Transactional_Validation

Critical checks:

  • PO–GR–Invoice consistency
  • Supplier correctness
  • Price / quantity match
  • Tax accuracy

Common Issues

→ Cross_System_Issues

Typical failures:

  1. Price mismatch
  2. Quantity mismatch
  3. Missing GR
  4. Duplicate invoice
  5. Incorrect tax

Key Takeaway

Invoice is NOT:

→ Just a bill

It is:

→ The financial truth of a transaction

If invoice is wrong:

  • Payments are wrong
  • Financial statements are wrong
  • Audit will find you

Backlinks