ERP & ledgers

Make different ledger structures mean the same thing.

Definite maps the entities, charts of accounts, identifiers, and relationships a finance workflow needs into one ontology. The ledger remains the system of record.

Existing connections are used where they fit. Missing connections are built around the source structures that matter to the workflow.

Illustrative mapping

Two structures, one financial meaning

Ontology
Source structure A

account / subsidiary / department

Source structure B

ledger account / company / cost centre

Shared concepts
AccountEntityCost centrePeriod
Mapping workbench

Map source structure into shared financial meaning.

The implementation follows the fields and relationships the workflow actually uses, rather than forcing every source into a generic connector model.

  1. 01Identify the required records and fields
  2. 02Map them to the ontology
  3. 03Keep every source reference attached
Source structure
Primary ledger
Source field
account
Ontology concept
Account
Source structure
Primary ledger
Source field
entity
Ontology concept
Entity
Source structure
Subsidiary ledger
Source field
customer
Ontology concept
Counterparty
Source structure
Supporting schedule
Source field
close date
Ontology concept
Period
Lineage

Shared meaning without losing the source.

A result keeps the source system, record, and field behind each mapped concept attached throughout the workflow.

  1. 01Source system
  2. 02Record
  3. 03Field
  4. 04Ontology concept
  5. 05Workflow result
Representative ERP systems
NetSuite
Sage Intacct
Microsoft Dynamics 365 Finance
Oracle Fusion Cloud ERP
SAP S/4HANA
Workday Financial Management

This is a representative list. When a workflow depends on another system, Definite can build the scoped connection during implementation.

Show us the ledger structures your workflow crosses.

Show us the workflow