Import payment files

Payments reach Quiddly through the files you download from your bank. This page covers which files Quiddly accepts and what to check when a file does not behave. The routine around it (match, bookkeep, unplaced payments) is in the Daily Routines step-by-step guide.

Supported files

Format	File extension	Notes
BgMax (Bankgirot)	.txt	Version 01
camt.054 (ISO 20022 debit and credit notification)	.xml	For example camt.054.001.02
Either of the above	.nda	Read as camt when the start of the file names a camt schema, otherwise as BgMax

camt.053 is not supported

A camt.053 account statement is not imported, because Quiddly reads the notification structure of camt.054, which is what carries every transaction. A camt.053 file is accepted at upload but contains nothing Quiddly can read, so it imports with nothing in it. In the import dialog its Batches and Payments counts are 0.

To tell the types apart, open the file in a text editor: the XML namespace at the top of the file ends in camt.053 or camt.054. If your bank sends the wrong type, ask it to send camt.054.

Other formats, and other camt types, are not supported.

Import a file

1. Go to Daily Routines > Import Payments and click Import in the bottom-right action bar. The Import payment files dialog opens.

2. Drop your files in the upload area, one or several. A message tells you how many were uploaded. The file names have to be new: a file with the same name as one that is already stored is refused.

3. The files are listed under Uploaded. The Batches, Payments and Deductions columns show what Quiddly found in each file. Check them before you import.

4. Click the Import icon on the row. The file moves through Pending Import and Importing to Imported, and its batches appear under Imported in Payment Batches.

A file that is still Uploaded can be deleted with the trash icon. An imported file cannot.

Before you import, check that the file matches the environment. A production file is refused on a test environment, and a test file is refused in production.

camt.054 in detail

• Quiddly creates one payment batch per account and booking date in the file, and one payment per transaction.
• The payment references are read from the remittance information of each transaction: the unstructured text, and in structured remittance the creditor reference, the additional information and the referred document number. A payment can only be matched on a reference found there, so the OCR number has to be in one of them.
• The sender (name, account, identification number) comes from the debtor party of the transaction.
• Only booked credit entries are imported. An entry that does not have the status BOOK, or that is a debit, is skipped.
• A batch whose payment date is older than 90 days is refused.
• Bankgiro deposits in the file are skipped for an account where Ignore BgMax rows in CAMT file is ticked, which is the default for SEK accounts. The BgMax file is then the source for them. See Bankgiro payments in a CAMT file.

BgMax in detail

The first line of a BgMax file is the start record. Quiddly rejects the file if any of this is wrong:

Positions	Content
1 to 2	Transaction code 01
3 to 22	Layout name BGMAX
23 to 24	Version 01
25 to 44	Creation timestamp
45	P for a production file or T for a test file

A start record without the version fails. After the start record come the deposits (transaction code 05) and the end record (70). Any other transaction code at that level is rejected, and so is any data after the end record.

When a file does not import

When something goes wrong during import, the file goes back to Uploaded and the Message column names the reasons, for example “1 of 2 deposits failed to import: Payment account does not exist in our registry”. Hover the message to read all of it. Fix the cause and click Import again.

Message or symptom	Cause and fix
Payment account does not exist in our registry	No bank account matches the account in the file and its currency. For camt, the IBAN or account number must match a bank account in the registry. For BgMax, the Bankgiro number must be registered as the Account No of a bank account. Register the account under Accounting > Bank Accounts first, see Setup Bank Accounts, then import
No enabled bank account for …	The bank account exists but is switched off. Edit the account that should receive the payments and tick Enabled
Payment batch is already imported	A batch with the same serial number, account, currency and year already exists. See below
Payment file is older than 90 days.	The payment date of the batch is more than 90 days old
The file could not be read	The file is not valid BgMax or camt. Check the start record or the XML
The file imports, but nothing is imported	Look at the counts in the dialog before you import: 0 batches and 0 payments usually means a camt.053 statement, a file with only debit entries, or entries that are not booked

Importing the same file again

Quiddly recognises what it has already imported, so a file whose batches already exist is not imported twice. The batch is refused with “Payment batch is already imported”. A single payment that already exists inside a new batch is skipped without a message. The same payment arriving in a BgMax file and a camt file is recognised as one payment for Bankgiro deposits.

To import a file again on a test environment, change its contents so that the serial numbers of the batch and the payments are new.

Remove a batch that was imported by mistake

You can abort a batch that is still under Imported or Matched, before it is booked.

1. Open the batch list under Daily Routines > Import Payments and find the batch on the Imported or Matched tab.

2. Open the action menu on the row and choose Abort, then confirm.

Aborting reverses the accounting of the import and releases any invoice balance reserved by links in the batch. Aborting needs a right to delete payment batches, see the rights catalogue and Rights, roles and users.

If the duplicate has already been booked and its payments are unplaced, see Correcting a payment that was booked wrongly in Way of Working: Unplaced Payments.