Integration and Data

Every company has more than one system: accounting, a bank client, a warehouse or production system, government portals, spreadsheets. While they are not connected, people retype the same data and the numbers disagree. We connect 1C to the systems around it and build reporting on data that is entered once.

What we connect

• Banks. Payment orders go out and statements come in without retyping.
• Government services. Electronic invoices (e-qaime) and reports are exchanged with state systems.
• Other enterprise systems. Production, warehouse, billing, customer management and payroll systems, online stores.
• Several 1C databases. Head office and branches, or the companies of a group, with one set of master data.

How the work goes

1. Map of data flows. Which system owns each kind of data, who needs it and how often.
2. Exchange rules. Formats, direction, schedule and what happens when an error occurs.
3. Trial on a copy. The exchange is run on a copy of your data before it touches the live systems.
4. Reconciliation. Totals and individual records are compared on both sides until no differences remain.
5. Monitoring. Every exchange writes a log. A failed exchange is reported to a responsible person the same day and is not discovered at the end of the month.

Reporting and analytics

Management reporting starts from agreed definitions: what counts as revenue, as an order, as an overdue debt. We agree them with the owners of the figures, bring data from the source systems into one model and build the reports and dashboards on it. Each figure can be traced down to the documents behind it.

When to talk to us

• The same document is entered in two systems.
• Month-end closing waits for data from another department.
• Two reports on the same subject show different numbers.
• A new system is being introduced and has to exchange data with 1C.

Questions clients ask

Our other system is not a 1C product. Can it be connected?

In most cases, yes. 1C:Enterprise exchanges data through web services, files and direct connections to external data sources. The method depends on what the other system offers.

What happens when an exchange fails?

The message is kept, the error is written to the log and the responsible person is notified. After the cause is removed, the exchange continues from the point where it stopped, without duplicates.

Who owns the integration afterwards?

You do. The exchange rules and their description are handed over together with the system.

Result

Data is entered once and reaches every system that needs it without manual re-entry.