Import issues
SynkriaOps offers several import types to speed up data entry. This page covers the most common issues by import type.
Accepted file formats by import type
Section titled “Accepted file formats by import type”| Import type | Accepted formats | Max size |
|---|---|---|
| Bank statement | OFX, bank CSV, MT940 | 10 MB |
| Mobile Money statement | Operator CSV (MTN, Orange) | 10 MB |
| OCR invoice | PDF, JPEG, PNG | 50 MB |
| Contacts (customers/suppliers) | SynkriaOps CSV | 5 MB |
| Product catalogue | SynkriaOps CSV | 5 MB |
Bank statements
Section titled “Bank statements””Unsupported file format”
Section titled “”Unsupported file format””The uploaded file is not recognized by SynkriaOps.
Possible causes:
- File exported as XLS or XLSX instead of OFX or CSV
- CSV file with a semicolon separator when the bank uses a comma (or vice versa)
- Incomplete or truncated MT940 file from the banking software
Solution:
- Return to your online banking interface.
- Choose export in OFX format (recommended) or the bank’s native CSV.
- Avoid modifying the file after export.
- If your bank only offers XLS, contact support for an appropriate converter.
”Columns not recognized”
Section titled “”Columns not recognized””The parser cannot identify the Date, Amount, and Description columns.
Solution: Verify that the file has not been opened and re-saved in Excel (which silently modifies date formats and decimal separators). Re-export directly from the banking interface.
”Duplicate detected — X transactions”
Section titled “”Duplicate detected — X transactions””SynkriaOps has identified transactions that appear to already be present (same date, amount, and internal reference).
This is not a blocking error. A report appears listing probable duplicates.
- Review each line marked as a “duplicate.”
- Check if the transaction already exists in your bank journal.
- If it is indeed a duplicate: click Skip.
- If it is not a duplicate (identical transactions on different dates): click Import anyway.
”Closing balance does not match”
Section titled “”Closing balance does not match””The balance calculated from imported transactions does not match the closing balance stated in the statement.
This message is a non-blocking alert. It signals that some transactions may have been deleted from the statement before export (for example, a partial statement or an overlapping period).
Solution: Verify that the bank statement you are importing covers the complete period without overlap with a previous import.
Mobile Money (MTN, Orange)
Section titled “Mobile Money (MTN, Orange)”“Transaction direction reversed”
Section titled ““Transaction direction reversed””Money received appears as expenses, and vice versa.
Cause: The wallet account identifiers are misconfigured — SynkriaOps cannot determine whether your number is the sender or the recipient.
Solution:
- Go to Settings → Mobile Money.
- Check the Wallet account identifier field (the phone number associated with the company’s Mobile Money account).
- Correct if necessary and re-import the statement.
See also: Importing a Mobile Money statement
OCR — Invoice import
Section titled “OCR — Invoice import””PDF too large” (50 MB limit)
Section titled “”PDF too large” (50 MB limit)”The PDF file exceeds the maximum size accepted for OCR analysis.
Solutions:
Use an online compression tool (e.g. ilovepdf.com, smallpdf.com) to reduce the size without loss of readability. Aim for a file under 20 MB.
If the invoice is a large multi-page document, split it into several PDF files — one per invoice. Then import each file separately.
”OCR duplicate detected”
Section titled “”OCR duplicate detected””An invoice with the same invoice number, amount, or supplier and date has already been imported.
Solution:
- Check in Purchases → Supplier invoices whether the invoice already exists.
- If yes: skip the duplicate in the OCR report.
- If no (false positive): force import by clicking Import anyway and manually verify that the two invoices are truly distinct.
”Read failed — insufficient quality”
Section titled “”Read failed — insufficient quality””The OCR AI could not extract data from the invoice (scan too blurry, photo taken at an angle, text too small).
Solutions:
- Rescan the document at 300 dpi minimum, in black and white or grayscale
- Photograph the invoice straight on, with good lighting, without shadows
- If quality cannot be improved: enter the invoice manually in Purchases → Supplier invoices → New invoice
CSV import — Contacts and products
Section titled “CSV import — Contacts and products””Contact CSV import fails”
Section titled “”Contact CSV import fails””The CSV file of customers or suppliers is rejected on upload.
Checks to perform:
| Issue | Solution |
|---|---|
| Incorrect separator | The CSV must use a semicolon (;) as separator |
| Missing headers | The first line must contain the exact column names from the template |
| Incorrect encoding | The file must be UTF-8 (not ISO-8859-1 / Latin-1) |
Missing type column | The type column must contain CLIENT or FOURNISSEUR |
Expected contact CSV format:
nom;type;niu;email;telephone;adresseSARL Maison des Épices;CLIENT;M123456789012A;contact@example.com;+237691234567;BP 1234 DoualaPHARMACAM SA;FOURNISSEUR;;pharma@example.com;+237677890123;Rue de la Santé Yaoundé”Import report — X rows in error”
Section titled “”Import report — X rows in error””The import partially succeeded: some rows were imported, others failed.
Solution: Download the import report. It lists each row in error with the reason. Correct only the rows in error in a new CSV file and re-import.
Further reading
Section titled “Further reading”- Importing a bank statement — complete statement import guide
- Importing a Mobile Money statement — specific MTN and Orange procedure
- Importing an invoice via OCR — automatic PDF invoice recognition
- Contact support — if no solution resolves your issue