← Back to catalogue
Published

Invoice, payment and reconciliation

EM-FIN-03 · em-fin-03

Settlement document, lines, due dates, payments and their allocation. The names invoice, bill and tax invoice require local profiles.

Enterprise profiles Enterprise subject EnterpriseFIN

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 5 findings · 10 questions

Documents Settlement documents and their local profiles.

Invoice

The invoice with lines, due dates and local profile.

Invoice identity

Number, issuer, recipient and profile.

  1. Which issuer, recipient and invoice number identify the document?
  2. Which local profile applies: invoice, bill or tax invoice?

Lines and due dates

Lines, amounts, taxes and due dates.

  1. Which lines, taxes and due dates does the invoice contain?
  2. Is this a cancellation or a credit adjustment of an earlier invoice?
Payments and allocation Money received or paid and how it is applied.

Payment

A payment with its own identifier, currency and amount.

Payment record

The payment, separate from the document it settles.

  1. Which payment identifier, amount and currency were received?
  2. How was the exchange difference recorded?

Allocation and reconciliation

Applying payments to documents.

Payment allocation

Amounts applied to each document.

  1. Which documents does the payment settle, and for which amounts?
  2. Does any allocation exceed the open amount, and is it explained?

Reconciliation result

Matched and open amounts with disputes.

  1. Which remainder stays open or disputed after allocation?
  2. Is reconciliation being read as proof of delivery?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseFIN
Industry
Cross-industry
Tags
EM-FIN-03W1subjectInvoiceInvoiceLinePaymentPaymentAllocationReconciliation

What it is Filled

Settlement document, lines, due dates, payments and their allocation. The names invoice, bill and tax invoice require local profiles.

Why it exists Filled

Settlement document, lines, due dates, payments and their allocation. The names invoice, bill and tax invoice require local profiles.

Distinguishing features Filled

  • A payment and the document it settles have separate identifiers.
  • Allocations never exceed the open amount without an explicit reason.
  • Reconciliation matches money to documents and does not confirm that goods or services were delivered.
  • Invoice, bill and tax invoice follow local profiles and are not assumed to be the same document.

What robots and AI may and may not do Filled

Must not

  • Use one payment to close two invoices for the full amount of each.
  • Treat a reconciled payment as proof of delivery.
  • Cancel an invoice where a credit note is required.
  • Initiate or release a payment.

Only with a human decision

  • Writing off a disputed remainder.
  • Releasing an outgoing payment.

May

  • Propose allocations of payments to open documents.
  • Report open, partly paid and disputed amounts per document.
  • Record exchange differences on foreign-currency payments.

Moral aspects Filled

  • Errors in invoicing and allocation can cause direct financial harm to customers and suppliers.
  • Payment data must be protected against fraud and misuse.

Who is affected

  • Customers
  • Suppliers
  • Accounts payable and receivable staff
  • Tax authorities

Owners Filled

Steward

The chief financial officer or finance lead who answers for books, budgets and reporting.

Master systems

  • ERP
  • Accounting system
  • Banking system
  • Billing system
  • FinOps platform

Links to other meta-models Filled

neighbor

  • EM-COM-03
  • EM-LEG-01
  • EM-OPS-02

references

  • WM-ECO-008 - conceptual-candidate
  • WM-ECO-009 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by issuer and invoice number, and payments by bank transaction or payment reference.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • An invoice record names an issuer, a recipient, lines, taxes and due dates.
  • Often confused with the order it bills or with the payment that settles it.

Capabilities and actions required Filled

  • Partial, combined and foreign-currency payments can be allocated and explained.
  • Disputed remainders stay visible until resolved.

Hazards and failure modes required Filled

  • Double settlement of documents by one payment.
  • Payment fraud through altered bank details.
  • Credit adjustments recorded as cancellations.

Standards and interfaces required Filled

  • EN 16931 from CEN for the semantic model of electronic invoices.
  • OASIS UBL Invoice and Credit Note documents.
  • ISO 20022 for payment and remittance messages.

Context of use required Filled

  • Used in accounts payable, accounts receivable and cash application.
  • E-invoicing and VAT rules differ by jurisdiction and drive local profiles.

Sources Filled

  1. FIBO: instruments, parties, transactions
  2. UBL/FOCUS: documents and costs; choose by contour
  3. XBRL and ERP/accounting-policy practice: books, periods, recognition and disclosure
  4. OASIS Universal Business Language Version 2.3 - Checked live (HTTP 200) on 2026-10-07.
  5. EDM Council Financial Industry Business Ontology (FIBO) - Checked live (HTTP 200) on 2026-10-07.
  6. XBRL Specifications - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to link partial and combined payments?
  • How to account for currency differences?
  • How to distinguish invoice cancellation from a credit adjustment?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-fin-03/brief.json, ver-cy/world-models/card-supplements/em-fin-03.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.