Skip to content
2finity.com
2finity.com
2finity.devSign in

CORE layer 08 of 10

Finance

Invoices, payments, costs and financial records: the money side of every order, contract and relationship.

2finity CORE and the interfaces and participants connected to it
COREWebsiteApplicationsChatAgentsPeopleCompaniesPartnersEnterprise
CORE
The shared operating layer. Ten layers: Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication, Data.
Website (interface)
Public sites and portals that read content and catalog data and submit forms through CORE. Uses the Identity, Knowledge, Commerce and Data layers. Example capabilities: page.get, catalog.list, form.submit.
Applications (interface)
Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions. Uses the Identity, Organizations, People, Workflows and Data layers. Example capabilities: customer.get, workflow.start, approval.decide.
Chat (interface)
2finity.chat and other conversational interfaces: language resolved to capabilities, with approval. Uses the Identity, Knowledge, Workflows, Finance and Communication layers. Example capabilities: site.content.update, invoice.create, permission.grant.
Agents (interface)
Actors with their own identity, an owner and scoped permissions; every action leaves an audit event. Uses the Identity, Knowledge, Workflows and Communication layers. Example capabilities: site.publish, deployment.rollback, workflow.start.
People (participant)
Humans in any context: professional, employee, customer or supplier, with one identity throughout. Uses the Identity, People, Relationships and Communication layers. Example capabilities: customer.get, permission.grant, message.send.
Companies (participant)
Organizations that own their data, run their workflows and decide who and what may act inside them. Uses the Organizations, People, Relationships, Commerce and Finance layers. Example capabilities: organization.get, invoice.create, order.update.
Partners (participant)
Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants. Uses the Identity, Relationships, Commerce and Data layers. Example capabilities: catalog.product.get, order.update, permission.grant.
Enterprise (participant)
Large organizations running CORE in an isolated deployment with their own identity provider and policies. Uses the Identity, Organizations, Workflows, Finance and Data layers. Example capabilities: permission.grant, deployment.publish, workflow.start.

Scope

What it holds

What is owed and paid?

Finance records what is owed, paid and spent. Invoices reference orders and people, payments settle invoices, costs attach to projects and organizations. Nothing here moves money by itself: a payment provider or bank is an interface that reports into CORE, and a capability like invoice.create is subject to the same identity and permission checks as any other action.

Model

Example entities

  • Invoice
  • Invoice line
  • Payment
  • Credit note
  • Cost
  • Account
  • Ledger entry
  • Tax rate

Contract

Capabilities

Every action on this layer is a named capability with a permission check and, where something changes, an event.

  • invoice.create→ invoice.created

    Create an invoice from an order or by hand.

    Member of the organization
  • invoice.get

    Named in the layer model; not yet described in the catalogue.

  • invoice.send

    Named in the layer model; not yet described in the catalogue.

  • invoice.void

    Named in the layer model; not yet described in the catalogue.

  • payment.record

    Named in the layer model; not yet described in the catalogue.

  • payment.list

    Named in the layer model; not yet described in the catalogue.

  • cost.record

    Named in the layer model; not yet described in the catalogue.

  • ledger.export

    Named in the layer model; not yet described in the catalogue.

The full catalogue

Connections

Relationships

The layers Finance reads from and writes to most often.

  • 07

    Commerce

    What do we sell?

    Products, services, catalogs, quotes, carts and orders: what an organization sells and how it is bought.

    Open layer
  • 02

    Organizations

    Inside which boundary?

    Companies, teams, departments and business units: the boundaries inside which people, data and permissions live.

    Open layer
  • 06

    Workflows

    How does work move?

    Tasks, approvals, automations, processes, triggers and state transitions: how work moves and who signs off.

    Open layer

Consumers

How interfaces use it

The interfaces and participants on the CORE graph that read or write this layer, with the capabilities of this layer they name.

  • Chat interface

    2finity.chat and other conversational interfaces: language resolved to capabilities, with approval.

    invoice.create

  • Companies participant

    Organizations that own their data, run their workflows and decide who and what may act inside them.

    invoice.create

  • Enterprise participant

    Large organizations running CORE in an isolated deployment with their own identity provider and policies.

    Uses the layer; its featured capabilities belong to other layers.