Integrations
One exchange contract for 1C, for A3.Accounting and for any other accounting system. The only difference is the data delivery mode.
Contract rules
The contract is designed for an external accounting system first and only then implemented in A3.Accounting. The reverse order would produce a contract that mirrors the internal model of one product, and the 1C integration would become second-class.
- 01
Source of truth
The source owns the accounting data. Imported transactions are read-only, and there is no write-back.
- 02
Idempotency
Transactions are matched by source identifier. A repeated export of a period creates no duplicates.
- 03
Reversal instead of deletion
Deletions and reversals in the source are reflected by a reversing entry. The history stays complete.
- 04
Period closing
A period closed in the source is closed in the projection too. The product follows the accounting calendar instead of keeping its own.
- 05
Recoverability
A full resynchronization from the source must give an identical result.
- 06
Reconciliation
A report on discrepancies in turnovers and balances by account is mandatory: without it, there is no way to prove that analytics matches the accounts.
Two delivery modes
One contract, different speed. This is a difference in delivery mode, not a separate integration.
Export on request
External accounting systems send data in scheduled batches, usually once a day.
- Suitable for 1C and other on-premises systems
- The exchange schedule is set per legal entity
- A separate frequent request is used for balances
Event subscription
A3.Accounting publishes events as transactions are posted, so analytics is close to real time.
- An entry appears in the report on the day it is posted
- The cash gap forecast is built on fresh balances
- The same contract as for external systems
Mapping is implementation, not development
The chart of accounts and analytics of the source are mapped to the product model. Two companies on the same 1C configuration structure analytics differently, so mapping is set up for each customer.
- Mapping interface for accounts, subconto and analytics dimensions
- Bundled templates for standard configurations and for A3.Accounting
- Report on accounts and subconto left unmapped
- An alert when new accounts appear after the next synchronization
Delivery from on-premises 1C
At a large share of companies, 1C is installed on premises and is not reachable from the internet. Connecting it requires human involvement, and this affects the cost of implementation.
Direct database access is not considered: it breaks the external system’s support terms and fails when the system is updated.
Exchange with products and services
Personal data is exchanged between products within the organization’s storage region. Cross-region transfer requires a separate legal basis.
- Inbound flow
A3.Accounting
Entries, taxes, payroll, assets, loans and bank statements.
- Inbound flow
A3.Sales
Orders: deal amount and payment flag for profitability calculation.
- Outbound flow
A3.Lawyer
Overdue receivables are handed over to claims handling, and the case status returns to the record.
- Two-way
A3.Trust
Counterparty check before payment, receivables as a scoring factor.
- Sign-in and subscription
A3.ID
The organization, users, roles and module subscription are shared by all ecosystem products.
- Outbound flow
A3.Drive
Exported reports in XLSX, PDF and CSV are saved to storage so they can be found later.
- Outbound flow
Bank client
The register of approved payments is exported as one file in the 1CClientBankExchange format.
- Outbound flow
BI systems
Power BI, Metabase and Excel receive selected reporting datasets using the BI channel key.
Need the contract description?
We will send the exchange specification and a sample export for your accounting system configuration.