Imports

Imports bring documents or master data into centraQuest.

Typical imports include e-mails, bank data, daily rates, ERP master data, scanned documents, and integration payloads.

Import Categories

Import	Purpose	Typical target
E-mail import	Collects messages and attachments from configured mailboxes.	Invoice inbox, e-mail archive, processing queue.
Scan/import folder	Imports files from watched folders or scan output.	Document archive or invoice processing.
SIX bank data	Updates bank master data used for IBAN and bank lookup.	Bank master table.
Daily rates	Imports exchange rates for configured currencies.	Daily rate table.
ERP master data	Imports accounts, cost centers, addresses, currencies, tax codes, payment terms, and banks.	Invoice master data tables.
Integration payload	Imports data from an external connector or API.	Module-specific objects or tables.

E-Mail Import

For e-mail import issues, check:

• mailbox configuration,
• authentication and network access,
• folder/filter configuration,
• whether messages were already processed,
• attachment handling,
• duplicate detection,
• target document profile and lifecycle,
• downstream processing logs.

Typical symptoms:

Symptom	Likely cause
No messages imported	Mailbox access, folder, filter, or schedule problem.
Message imported but no invoice created	Attachment filter, unsupported file type, or processing job issue.
Duplicate messages	Missing message ID tracking or changed mailbox behavior.
Attachments missing	Attachment transformation or filtering issue.

Bank Data Import

Bank data imports update the bank directory used for IBAN and bank lookup.

Check:

• source availability,
• import job permissions,
• mapping to the target bank table,
• whether existing bank records are updated or duplicated,
• whether inactive or obsolete bank records are handled correctly.

Daily Rates Import

Daily rates are used for foreign currency invoices and reporting.

Check:

• configured source URL,
• selected date range,
• selected currencies,
• whether the target daily-rate table receives records,
• whether ERP export uses the imported rate or lets the ERP determine the rate.

ERP Master Data Import

ERP master data imports are sensitive because they affect later invoice processing and exports.

Typical master data:

• accounts,
• cost centers,
• accounting areas,
• addresses,
• bank connections,
• currencies,
• tax codes,
• payment terms,
• internal banks.

Before troubleshooting mapping, always capture the raw source field, the mapped centraQuest field, and one example record.

Import Validation Checklist

After an import, verify:

• expected number of records,
• newly created records,
• updated records,
• inactive records,
• duplicate keys,
• mandatory fields,
• client/accounting assignment,
• technical IDs used for later exports,
• visible result in the relevant admin table.

Safe Retry

A good import can usually be rerun safely. If rerunning creates duplicates, the import key or update logic should be reviewed.

For customer support, document whether a specific import is safe to rerun before asking an administrator to repeat it in production.