Browse the guide›

VedronERP · Financial Statements

Importing Bank & Platform Data

M1 data can come from two sources: automatic API imports (for marketplaces) and manual CSV/Excel uploads (for banks).

API Platforms (Marketplaces)

  1. Go to Financial Statements and find the platform in the "API Platforms" list.
  2. Click "Sync" on the platform's row (or "Update All APIs" at the top to update every platform).
  3. The system fetches new transactions from the platform API.
  4. After the sync, the next stages (M2 normalize, M3 enrich) run automatically in the background.

Bank CSV Upload

For your configured bank accounts, export your transaction history from your online banking portal and upload the CSV or Excel file.

  1. Find your bank account in the "Banks (CSV upload)" list.
  2. Click "Upload CSV" and select the exported file.
  3. The ERP parses and stores the transactions as M1 raw data and shows the result: rows imported, duplicates skipped, balance checks and the first rows it read.
  4. M2 (which matches transactions to orders and invoices), M3 and M4 then run automatically in the background. Give it a minute, then check the stage tabs.
  5. Bank accounts are posted to the journal (M5) automatically every hour; click "Post to ledger (M5)" on the Journal tab to post right away.

Supported Bank File Formats

The system recognises specific CSV and Excel export formats for each supported bank. When you add a bank account in the Payout Banks setup, the system automatically knows which format to expect for that bank. The available bank options are shown in the bank account selector when you add an account.

Tip: You can upload overlapping date ranges safely — rows that are already stored are skipped as duplicates, so duplicate rows are never created.

Checking that everything was processed

After an upload the rows move through M2, M3 and M4 on their own. To check, click "Pipeline" on the bank account's row: it shows how many rows each stage holds and how many are waiting.

  1. On the bank account's row, click "Pipeline".
  2. Compare the stages. If a stage holds fewer rows than the one before, the difference is "Waiting". (A file that was uploaded twice can show one waiting row that is really a duplicate.)
  3. Click "Process now" to run the missing steps again. Each step shows ✓ or ✗; a ✗ names what is missing, for example an account mapping that has to be set in Accounting Configuration. Running it again is safe.

Reviewing the automatically assigned values

Accounts, tax keys and transaction types on bank and platform rows are assigned automatically. In Statements, open the Review tab to see the rows that deserve a second look. Nothing is changed there, and rows in closed periods are never listed.

  1. Open Statements and click the Review tab. The table shows, for each bank or platform that has rows, how many rows are flagged in each list.
  2. Placeholder account lists rows booked to the temporary account 10000, either because an incoming payment is not matched yet or because no account mapping exists.
  3. Rare combination lists rows whose counterparty, type, accounts and tax key together occur only a few times. Differs from usual lists rows booked differently from how the same counterparty is usually booked.
  4. Click a number to see the rows, then click a row to see what it was based on: the raw line, the matching, the classification, the booking, the journal entries and the linked invoices. A panel also shows where the account, counter-account and tax key most likely come from (your account map, a vendor rule or a linked invoice).
  5. If a row is fine, click Mark as reviewed (with an optional note). It leaves the list, and comes back on its own if its account, counter-account or tax key changes later.
  6. To correct a row, use Bank Review (account, tax key, booking text), the M2 view (type, order or invoice link) or the vendor rules.

Use the Review tab after each upload. A flagged row is not necessarily wrong; it only means the automatic assignment has little history to back it up.

Removing a wrong upload

If you uploaded the wrong file or selected the wrong company, you can remove the upload yourself (administrators only), as long as nothing in the accounting depends on it yet.

  1. On the bank account's row, click "History".
  2. Select the company. The list shows every file imported for this account with its rows, period and import time.
  3. Click "Remove" next to the file. The system shows exactly what would be deleted: the rows in every pipeline stage, pending journal entries and invoice links (and how many of those links you set manually).
  4. Tick "I understand this cannot be undone" (if some invoice links were set manually, a second confirmation also appears) and click "Remove upload". Then upload the correct file.

A file cannot be removed while confirmed or exported journal entries, entries in a closed period, linked payments or contract installments depend on it. The dialog lists what blocks it: unlink the payments or reopen the period, then try again. If other files were imported after it, the dialog lists them: rows that both files contained were stored only with the removed file, so upload the correct file again with "Force reimport" (and the later files too if their dates overlap).

Tip: Everything removed is archived. If you removed the wrong file, open "History" again and click "Restore" under "Removed uploads" to bring it back exactly as it was. Because removing an upload also removes its period confirmation, confirm the period again after uploading the replacement file.