Skip to main content
Use an AI client to help interpret a DATEV Kontenblatt (account-ledger export) and prepare the postings for Control. Review the source, account mappings, and totals before approving any changes.

​
Watch the example

The recording illustrates one export and chart of accounts. Its exclusions and accounting choices are not rules for every DATEV file. The narration has no captions; its transcript is available below. Follow the review and approval steps on this page rather than treating the recording as authorization to write.
  1. DATEV, or any legacy system, into Control with any AI assistant via MCP.
  2. The raw Kontenblatt export. Drop it in the chat: upload this to the German entity.
  3. It checks the granularity, full posting detail, then posts every line through Control’s MCP tools.
  4. Seven hundred seventy-two postings, January to August. Booking text, document numbers, counter-accounts.
  5. Open Control: the German entity’s P&L is live, mapped to the group chart of accounts, down to every line.
  6. Control.dev. Any ledger, any format, with any AI assistant.
In the example, the assistant interprets general-ledger postings and opening balances, maps local accounts to group accounts, and checks the resulting profit and loss statement. The source uses SKR04, a DATEV standard chart of accounts.

​
Before you start

  • Connect your AI client and confirm that the tools needed for the import are available in your session.
  • Identify the destination company, reporting period, currency, and local chart of accounts.
  • Agree with your finance team which source rows represent postings, opening balances, and summaries.
  • Confirm the local-to-group account mappings. Do not create or change accounts without reviewing the proposed changes.
  • If using manual transaction proposals, ensure that another Owner or Admin can review and approve them.

​
Prepare and review the import

1

Inspect the source file

Ask the assistant to explain the file structure before preparing an import. Check dates, debit and credit amounts, account codes, and opening balances against the original export.An account-ledger export can show the same posting under both its account and counteraccount. Confirm how the file represents these entries so the import does not count them twice.
2

Agree on which rows to include

Review any proposed exclusions with your finance team. In the recorded example, customer and supplier subaccounts duplicate the accounts receivable and accounts payable control-account entries. Other exports may require a different treatment.Preserve the opening balances needed to reconcile the balance sheet. Do not remove tax accounts, subaccounts, or summary rows merely because their names resemble those in the demo.
3

Review accounts and totals

Resolve missing local accounts and group mappings before saving. Compare the proposed monthly account totals and opening balances with the source, and investigate differences.A strict manual import fails if an account is missing. A non-strict import can skip rows with missing accounts while saving the others. Review skipped rows rather than treating a completed import as proof that every row was saved.
4

Approve the intended changes

For manual transaction proposals, review batches of no more than 100 rows. Approval must come from an Owner or Admin other than the requester. Review the company, period, currency, accounts, amounts, and explanation for every proposal.If you use a file upload instead, check the replacement behavior first: resubmitting the same file replaces the rows from its previous submission. Choose one import method deliberately; do not upload the file and also approve manual entries for the same postings.
5

Verify the saved results

Read back the saved entries and compare account and monthly totals with the source. Check the profit and loss statement and balance sheet for the same company, dates, and currency. Keep a record of excluded or skipped rows and unresolved differences.

​
Example request

Inspect this DATEV account-ledger export for Example Corp for January through August 2026. Explain its structure, identify repeated postings and opening balances, and propose local-to-group account mappings. Show the proposed monthly account totals and any exclusions before saving anything. Do not create accounts or submit entries until I have reviewed the proposal.

​
If something looks wrong

  • Missing accounts: resolve the mapping or account setup, then recheck the skipped rows and totals before importing again.
  • No confirmation after saving: inspect saved entries and pending proposals before retrying. For manual transaction proposals, reuse the same idempotencyKey in the same agent run: a new run creates a separate proposal, and approving both can duplicate postings. If you cannot resume the original run, have the reviewer check the existing proposal before submitting another. For file uploads, retry with the same fileUploadId to replace that file’s previous rows, rather than creating a second upload.
  • Unexpected doubled totals: check whether the same postings were imported twice or represented twice in the source. Do not assume duplicates are the only possible cause.
  • An incorrect proposal: reject it while it is still pending. For accepted entries, agree on a correction or reversal with your finance team before changing financial data.

Connect your AI client

Set up access to Control from your preferred AI client.

Propose a financial adjustment

Use reviewable instructions for manual financial entries.