Combining Sage, Tiime and DATEV data

Start with the real extraction method

Do not assume that naming an accounting system guarantees a native connector. For each Sage, Tiime or DATEV installation, confirm the edition, permissions, available export or API and refresh frequency with the team.

A minimum import contract

Agree entity identifier, period, account code, account name, signed amounts, currency and stable source identifiers. Keep a sample file and document how adjustments and reversals appear.

Mapping before automation

Map local accounts to group reporting lines. Test unmapped accounts, duplicate records, missing periods and rounding differences. A source total and the imported total should reconcile before transformation.

Acceptance criteria

A finance reviewer should be able to choose a reporting line, see the contributing source records and explain the transformation. Repeat the same import to confirm it does not duplicate data. Agree data retention and access separately.

Run one import acceptance exercise

1. Keep an unchanged source export and record its entity, period, extraction date and format version.
2. Agree a stable source identifier and how corrected or reversed entries are represented.
3. Compare row counts and signed totals at the same entity, period and currency scope. Investigate differences before mapping.
4. Reimport the same sample, then a corrected sample. Verify the intended duplicate and correction behaviour with the reviewer.

Evidence to keep

Input field	Why it matters
Entity and period	Keep submissions within the agreed reporting scope
Account code - account name	Preserve the original account beside its group mapping
Signed amounts and currency	Keep units and sign conventions explicit
Stable source identifier	Trace corrections and detect repeated records