Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

  • Import folder - folder to store imported files
  • Folder after import - folder to store files after import
  • Export folder - folder to store files after export

    Path to import folders must be relative to Hansa server directory!
    Folders on server must be created manually! Don't forget to check the file permissions so that the user running the server process can read and write in those folders.
    If the folders won't be specified or created on server, exporting and importing won't work!

  • Encoding - encoding of the file exported from bank

    If encoding doesn't match then the language specific non-latin characters won't be recognised.

    If this field is left empty, then UTF-8 will be used by default.

  • Create:
    • Receipts - check if receipts should be created during import
  • If unrecognised, create prepayments:
    • Receipts - check if prepayments should be created in a case when customer is found, but specific invoice wasn't
  • Receipt import:
    • Create transaction - check if created receipts should be automatically OKed(which creates transaction)
    • Link if invoice sum matches - receipt will be created if FiDAViSta record's sum will be equal with customer's unpaid invoice sum
    • Link if full debt sum matches - receipt will be created if FiDAViSta record's sum will be equal with customer's total unpaid invoice sum
    • Allow currency mismatch - check if invoice should be recognised if invoice sum matches in other currency
    • Unrecognised payments covers invoices starting from oldest - receipt will be created that will cover those unpaid invoices(starting from the oldest ones) that can be paid by the payment sum in FiDAViSta record. If FiDAViSta record's sum ir greater than total debt, the created receipt will contain a prepayment row for the remaining amount.

      For creating rceipt records these checkboxes must be selected:

      • Create >> Receipts
      • If unrecognised, create prepayment >> Receipts

  • Payment import:
    • Create transaction - check if created payments should be automatically OKed(which creates transaction)
    • Link if invoice sum matches - payment will be created if FiDAViSta record's sum will be equal with supplier's unpaid invoice sum
    • Link if full debt sum matches - payments will be created if FiDAViSta record's sum will be equal with supplier's total unpaid invoice sum
    • Unrecognised payments covers invoices starting from oldest - payment will be created that will cover those unpaid invoices(starting from the oldest ones) that can be paid by the payment sum in FiDAViSta record. If FiDAViSta record's sum ir greater than total debt, the created receipt will contain a prepayment row for the remaining amount.
  • Create: - specify which records should be created during import
    • Payments
    • Personnel payments
  • If unrecognised, create prepayment:
    • Payments - prepayment payment record will be created if supplier was recognised, but specific invoice wasn't
  • Include in export file- specify what kind of information should be added to bank payment's description
    • Payment comment
    • Purchase invoice date

For creating payment records these checkboxes must be selected:

  • Create >> Payments
  • If unrecognised, create prepayment >> Payments

Contact creation:

  • Create contact if FV record doesn't contain Legal ID - if nonexisting contact was found, it will be stored in database even if reg.no. isn't in FV record
  • Create contact if FV record doesn't contain Bank account - if nonexisting contact was found, it will be stored in database even if bank account isn't in FV record
  • Open contact record after creation - the newly created contact record window will pop up for immediate editing or adding extra information
  • Allow attaching existing contact to FV record - if selected, it's possible to change the "Customer code" filed in FiDAViSta record

    If customer code is manually selected in FiDAViSta record in order to get then remaining information from contact the action "Link record with data from contact" must be run

  • Create:
  • Transaction
    • Don't create if exists record with the same Bank Ref. already
  • No labels