CSV transactions headers to columns matching - how?

Hi there.

I am tying to correctly import CSV transactions into IN, but I do not know how. Tried many different combinations but none of them works.

These are my bank CSV columns:
Posting date,Value date,Amount,Currency,Type,Preffix,Account Number,Bank Code,IBAN,Variable symbol,Specific symbol,Constant symbol,“Payer¥s reference”,Information for beneficiary,Description

As an example, how to match Credit/Debit to Deposit/Withdrowal when columns in IN are like bellow. There are Credit/Debit in one Header, but IN has two separate columns Credit and Debit.

Amount hader is the same as column Amount, but the results after import are always 0.00 EUR.

After import all amounts columns are 0.00 EUR as shown bellow.

The problem with imported amount 0,00 EUR is that, CSV export amount is in format “24,53”. When I changed it to clear 24.53 imported amount was OK.

So how to deal with this?

After changing CSV amount values to negative (-) and positive, CSV amounts are imported correctly into deposit and withdrawal columns. Is this the only way how to import it?

Hi,

If you’d like to see this changed feel free to create an issue on GitHub.

Except for +/- amount values, how to match one header (contains both credit and debit type) in csv with two columns (on for credit, one for debit) in IN?

I’m not sure if that’s supported

So do you have exact definitions of what columns with what data type are supported?

You may find the API docs helpful

https://api-docs.invoicing.co/#put-/api/v1/bank_transactions/-id-

Thank you for the link, but this made more mess. See bellow:

There are 12 items in API

But there are 14 items in IN webgui

So how to correctly match these:

  • user_id - is Participant in gui?
  • ??? - is Participant name in gui?
  • base_type - is Credit or Debit in gui?
  • base_type - how to match this if the rule during CSV import is +/- amanout
  • is it possible to import DEBIT and CREDIT in one CSV?

I suggest creating a discussion on GitHub to get feedback from the. backend developers