ZAYAZ Integration Brief — Xledger

How ZAYAZ integrates with Xledger

Overview

ZAYAZ integrates directly with Xledger to connect financial and operational accounting information with the wider ZAYAZ sustainability data environment.

Xledger provides modern integration capabilities including GraphQL APIs, SOAP web services and file-based exchange through formats such as CSV and XML. Its GraphQL interface uses administrator-managed access tokens, enabling controlled integration between Xledger and external systems.

Through the ZAYAZ Accounting Connectivity Framework, Xledger data can become part of a broader ESG information chain covering:

• financial transactions;
• suppliers and customers;
• invoices and procurement;
• projects and accounting dimensions;
• emissions analysis;
• supplier ESG information;
• VSME and ESRS reporting;
• evidence and assurance traceability.

The integration enables organizations to use information already managed in Xledger while progressively adding more specific ESG evidence where required.

---

1. Integration overview

Xledger operates as a live source system within the ZAYAZ architecture.

The standard integration flow is:

Xledger → ZAYAZ Accounting Connectivity Framework → ZAYAZ canonical data model → ESG classification and enrichment → Calculation and reporting → Traceability and assurance

Unlike a periodic accounting-file import, the Xledger connector can form part of an ongoing data process.

This allows ESG information to remain connected to the underlying financial activity as the source system changes over time.

---

2. Integration methods

GraphQL API

GraphQL is the preferred integration method for recurring Xledger connectivity.

The connection enables ZAYAZ to retrieve authorized data from the customer's Xledger environment and map it into the ZAYAZ data model.

Access is controlled through Xledger credentials and permissions established by the customer.

SOAP web services

SOAP provides an additional integration method for environments where existing Xledger configurations or specific integration requirements use web services.

File integration

CSV, XML and configured file exchange can support:

• initial onboarding;
• migration;
• historical information;
• reconciliation;
• fallback processes.

Scheduled synchronization

The integration can retrieve data on a defined schedule, allowing ESG processing to follow the organization's accounting cycle.

For example:

Daily

for operational ESG monitoring.

Monthly

for accounting-close and management reporting.

Quarterly

for formal sustainability review.

The appropriate schedule depends on the organization's reporting and control requirements.

---

3. Connection setup

Each Xledger integration begins with a controlled connection process.

Authorize Xledger
       ↓
Identify available data
       ↓
Map Xledger entities
       ↓
Validate mappings
       ↓
Activate synchronization

ZAYAZ establishes a connector profile for the customer's Xledger environment.

This profile records which data domains and fields are available to the authorized integration.

This is important because integrations can vary according to:

• customer configuration;
• Xledger modules in use;
• access permissions;
• legal entities;
• source data structures.

ZAYAZ therefore works from the actual authorized source environment rather than making generic assumptions about the customer's accounting data.

---

4. Data available to ZAYAZ

Xledger contains a broad range of accounting and operational information, including general accounting, invoicing, accounts payable and receivable, projects, purchasing, inventory and fixed assets.

The exact dataset used by ZAYAZ is determined by the organization's configuration and permissions.

General ledger

Financial accounts and transactions can support:

• ESG expenditure analysis;
• financial reconciliation;
• emissions screening;
• period analysis;
• linkage between financial and sustainability reporting.

Suppliers

Supplier information allows ZAYAZ to connect financial transactions with:

• supplier spend;
• Scope 3 analysis;
• supplier ESG information;
• supplier-specific emissions;
• supplier engagement.

Customers

Customer information can support customer-specific ESG requirements and downstream sustainability-data relationships.

Supplier invoices

Invoice information provides richer context than general-ledger transactions alone.

It can improve:

• supplier identification;
• expenditure classification;
• source evidence;
• calculation accuracy.

Invoice lines

Where line-level information is available, ZAYAZ can use details such as:

• product or service;
• quantity;
• unit;
• supplier;
• project;
• financial value;
• accounting treatment.

This can enable more precise ESG calculations than spend information alone.

Purchasing

Xledger's purchasing functionality connects purchase orders, goods receipt, inventory, supplier ledger, projects and general ledger.

Where this information is included in the authorized integration, ZAYAZ can use it to improve material, procurement and supplier analysis.

Projects

Xledger supports project accounting, project costs, time registration and detailed project reporting.

ZAYAZ can use project identifiers as an ESG allocation dimension.

This can support questions such as:

What is the carbon footprint of this project?

Which suppliers contribute most to this project's emissions?

How do environmental impacts differ between projects?

Accounting dimensions

Departments, projects and other accounting dimensions can be mapped into ZAYAZ to allocate ESG information across the organizational structure.

Fixed assets

Fixed-asset information can support analysis of:

• capital goods;
• investments;
• asset-related emissions;
• depreciation and financial reconciliation.

Currency and tax information

Financial metadata remains associated with the source transaction and can be used in calculations and reporting where relevant.

---

5. How ZAYAZ processes Xledger data

Ingestion

ZAYAZ retrieves authorized information from Xledger and records:

• source environment;
• legal entity;
• source record;
• retrieval time;
• integration method.

Mapping

Xledger objects are mapped into the ZAYAZ canonical data model.

For example:

Xledger supplier → ZAYAZ supplier

Xledger invoice → ZAYAZ procurement invoice

Xledger project → ZAYAZ project

This separates the ESG logic from the accounting-system-specific structure.

Normalization

ZAYAZ standardizes relevant information such as:

• accounts;
• dates;
• organizations;
• suppliers;
• projects;
• currencies;
• dimensions;
• measurement units.

The original source information remains linked to the normalized record.

Validation

Incoming data is checked for issues such as:

• missing relationships;
• duplicate records;
• inconsistent periods;
• missing identifiers;
• unsupported values;
• changes to previously processed source records.

ESG classification

Transactions and invoices can be classified into sustainability-relevant categories such as:

• electricity;
• fuel;
• transport;
• travel;
• waste;
• purchased materials;
• professional services;
• leasing;
• capital goods.

Classification can use multiple signals rather than relying on account codes alone.

Enrichment

Where Xledger identifies the financial activity but does not contain enough information for a more precise ESG result, ZAYAZ adds information from another authorized source.

Example:

Xledger

Electricity invoice: NOK 185,000

↓

Additional evidence

Electricity consumption: 142,000 kWh

↓

ZAYAZ

Activity-based electricity calculation

The financial record remains available for reconciliation.

---

6. ESG use cases

Emissions screening

Xledger financial data provides a strong starting point for identifying likely emissions exposure.

ZAYAZ can analyze:

• expenditure;
• suppliers;
• invoices;
• projects;
• procurement categories;

to identify sustainability hotspots.

Scope 1

Relevant financial activity can help identify:

• fuel;
• combustion;
• company vehicles;
• gas;
• refrigerant-related activity.

Where required, ZAYAZ combines this with physical activity information.

Scope 2

Energy-related invoices and financial transactions can be linked with:

• kWh;
• energy source;
• location;
• supplier;
• contractual energy information.

Scope 3

Xledger data is particularly relevant to categories connected to procurement and value-chain expenditure.

Examples include:

• purchased goods and services;
• capital goods;
• transportation;
• business travel;
• waste;
• leased assets.

Accounting information can provide the initial screening layer, while ZAYAZ progressively upgrades the underlying data.

Purchased goods and services

Supplier expenditure can be analyzed to identify:

• major suppliers;
• material procurement categories;
• emissions hotspots;
• priority suppliers for better data collection.

This allows the organization to focus supplier engagement where it matters most.

Project-level ESG

Project and cost allocation data can enable ESG reporting at project level.

For organizations with project-based operations, this can connect financial performance and sustainability performance within the same underlying structure.

Supplier analysis

Supplier information can support:

• spend analysis;
• supplier ESG prioritization;
• Scope 3 screening;
• supplier-specific data collection;
• supplier sustainability profiles.

---

7. Xledger's existing ESG information

Xledger also provides its own carbon-accounting and ESG functionality, including Scope 1, 2 and 3 reporting, climate activity data and supplier/category analysis.

ZAYAZ is designed to coexist with this information rather than assume that all emissions must be recalculated outside Xledger.

Where existing Xledger climate information is made available through the authorized integration, ZAYAZ can preserve it as a source dataset.

The origin remains explicit:

Xledger calculation → Xledger identified as calculation source → ZAYAZ evidence and reporting environment

If an independent ZAYAZ calculation is required for reconciliation or another methodology, both results remain separately traceable.

This avoids turning integration into duplicate or conflicting carbon accounting.

---

8. Data-quality hierarchy

ZAYAZ uses a progressive data-quality model.

Level 1 — Accounting-based estimate

Example:

NOK 1.2 million spent on freight

Useful for screening and initial estimation.

Level 2 — Invoice-level information

Example:

Specific logistics supplier + invoices + expenditure

Improves classification and attribution.

Level 3 — Activity data

Example:

Shipment weight + distance

or:

Electricity consumption in kWh

Enables more specific calculations.

Level 4 — Supplier-specific data

The supplier provides product- or service-specific sustainability information.

Level 5 — Verified primary data

Primary data is supported by defined validation or verification evidence.

ZAYAZ retains the relationship between calculation versions as data quality improves.

---

9. Traceability and audit trail

Each ESG result can remain connected to the original Xledger information.

A typical evidence chain is:

Reported ESG result

→ calculation → calculation method → emissions factor → ESG classification → normalized record → Xledger invoice or transaction → Xledger source identifier

Where additional evidence is used:

Xledger transaction

↕

invoice / activity data / supplier evidence

The combined chain is managed within the ZAYAZ evidence and traceability architecture.

This makes it possible to answer:

Where did this number come from?

Which Xledger transaction supports it?

What transformation was applied?

Which emission factor was used?

Has the source data changed?

Has the result been reviewed or verified?

---

10. Multi-entity and group structures

Xledger supports organizations with complex group and project structures.

ZAYAZ retains the legal-entity context of imported records and maps each source entity to the corresponding ZAYAZ organization.

This allows sustainability information to be analyzed at:

• entity level;
• business-unit level;
• project level;
• group level.

Consolidated ESG reporting can therefore retain visibility back to the underlying source entity.

---

11. Synchronization and change handling

Initial load

The connector establishes the relevant financial and master-data context.

Recurring synchronization

New and changed information is retrieved according to the configured integration schedule.

Accounting adjustments

When an accounting record changes after it has contributed to an ESG result, ZAYAZ identifies the affected sustainability data.

The previous result remains traceable.

Reconciliation

Historical or file-based data can be used alongside API data to validate completeness and resolve differences where appropriate.

---

12. Security and controls

Xledger supports secured integration through token-authenticated GraphQL and certificate-based SOAP services. Xledger also provides customer-specific test environments for integration development.

Within ZAYAZ, the integration applies controls including:

• encrypted credentials;
• encrypted data transfer;
• encrypted storage;
• role-based access;
• tenant isolation;
• legal-entity scoping;
• integration logging;
• credential rotation;
• connection monitoring.

For the Norwegian environment, Xledger publicly states ISO 27001 certification, ISAE 3402 compliance and data storage in Norway.

---

13. Implementation models

Direct Xledger integration

Xledger → GraphQL → ZAYAZ

Suitable for recurring financial and ESG operations.

Managed batch integration

Xledger → XML / CSV → ZAYAZ

Suitable for controlled periodic transfer, historical data and specific customer configurations.

Hybrid integration

Xledger financial data

• supplier ESG data
• invoice documents
• meter/activity data
• other business systems

↓

ZAYAZ

This model allows Xledger to remain the financial system of record while ZAYAZ combines the accounting data with the broader evidence required for sustainability management.

---

14. Integration outcome

The purpose of the Xledger integration is not to replicate the ERP system inside ZAYAZ.

Xledger remains the financial source system.

ZAYAZ adds the ESG interpretation, cross-source enrichment, value-chain data, regulatory mapping, evidence architecture and sustainability intelligence around that source.

The resulting flow is:

Xledger financial and operational data

↓

ZAYAZ canonical data environment

↓

ESG classification

↓

activity and supplier enrichment

↓

calculations and existing ESG-data integration

↓

VSME / ESRS / management reporting

↓

traceability and assurance

This gives organizations a path from existing financial operations to a broader sustainability information architecture without disconnecting ESG reporting from its underlying accounting evidence.

---

Integration principle

Xledger remains the financial system of record. ZAYAZ connects that financial foundation to the wider ESG, supplier, compliance and evidence environment.

---