Content Comparison

...

• Internal Doc. No.

  • Document number from the imported record (Shell format, it is the first entry on the line, see chapter Data Record form)

• Description

  • A description consisting of the data found during import, i.e.: the internal fuel card number (primary key) and the vendor number and item number from the data record

• Car Licence No.

  • The system fills when importing from a data record (this is column 3=C)

  • If a user has detected an incorrectly entered vehicle registration number in a data sentence, they can edit here. Then it searches for the object and, if successful, fills in the VIN, object number and contract number and performs checks according to the template.

• Financed Object No.

  • The system fills in during import when searching for the financed object

• Fuel Card No.

  • The system fills in when importing from an imported record

• VAT Date

  • The system completes the "Posting Date" that the user entered in the dialog window when starting the import

• External Document No.

  • The number assigned by the system when importing a dated sentence

• Standard Purchase Code

  • The system fills in the imported sentence based on the mapping of the item and country code

• Odometer Status

  • Odometer status and imported records (We do not fill into the buffer line, only into the TK transaction)

  • Invalid odometer check is not in progress

• Quantity

  •  (We do not fill into the stack line, only into the TK transaction)

• Amount

  • By Country Code in the Data Record and Country/Region Code in Company Information. E.g. a Czech company has Countries/Areas = "CZ"

    • If the data sentence contains "country code" = "CZ", the system will deduct tax from the total amount with VAT

    • In case the data sentence contains "country code" <> "CZ", "Amount" = Total price incl. VAT from the imported record

• Processing Status

  • New

    •  In case there was no error during the import

    • or the soft error has been accepted and the Update Rows function has been triggered

  • Processed

    • After you create a purchase invoice

  • Error

    • In case of an error during import or further processing

• Status Code

  • Status New corresponds to status code 100

  • Status Processed corresponds to status code 200

  • There are two codes for the error processing status

    • 400 is a soft bug

    • 300 is a hard mistake

• Error Accepted

  • A soft error can be flagged by the user and the system does not verify this line during further processing

• Error Message

  • The system uses to describe any errors

  • For a single line, several errors can be detected during checks. Therefore, the system uses multiple fields for the error message

• Assigned Document No. (Posted when Processed)

  • Fills in the system after the purchase document is created

• Assigned Document No.

  • Fills in the system after the purchase document is created

• Type of Processing

  • Filled in by the system during import according to the settings on the invoice interface – in the case of import, refueling = "Fuel card"

• File ID

  • Identification of the imported file is assigned during import

...