...
Code
The user enters the invoice interface code for a specific format (CCS, SHELL, OMV, Benzina)
A new invoice interface code must be entered for each format
Name
The user fills in the name
Business Type
Purchase - for processing data records from vendor
Source Code
The user selects the origin code. It can also be the same for all fuel formats.
Automatic Posting (Automatic Pousting)
Do Not Turn On for processing data records, because then the posting would be done immediately when imported.
In the system, the data record is only checked by import. You need to wait for the delivery of the vendor invoice before processing.
Default Invoice Interface Template No.
If the user does not set up mapping, the system will use the Standard Buy/Sales Code from the default template
Data Fieldname
You need to enter An asterisk and the end cap for Format Type (file extension).
Vendor No.
The user selects the fuel card vendor for the given fuel data record format
You need to enter an "Invoice Interface Code" for each vendor.
From there, the system takes the supplier when importing fuel when it creates a batch into the tank.
Service Fee (%))
If the user sets the fee percentage, the system will create a fee line for each card transaction. The fee line doesn't go to the buffer, it's used when the transaction is reinvoiced to the customer. For Shell, it is intrusive for the transaction "DC".
Standard Code (Service Fee)
User sets up a fee per customer for reinvoicing
Standard Code
User sets up for re-invoicing to the client.
Object Type
User Sets Report
Object ID
It is necessary to enter the report number for import of the given format
The SHELL format is a report 4026751
Type of processing
To process fuel card transactions, you need to set up "FUEL“
Automatic Release
If the field is checked, the system switches the created document of the unposted purchase invoice to the Released status
If Workflow is set to Purchase invoices, Automatic release = NO must remain, because the status of Released is not switched to the purchase invoice until it is approved.
...
No. (No.)
The user chooses the name of the template
Invoice Interface Code
The user selects the invoice interface code for which the template is being set up
Business Type
The system will set up according to the billing interface. In the case of processing a fuel data record, the Purchase is
Source Code
The system will set up according to the billing interface.
Document Type (Cocument Type)
User selects Invoice
Buy-from Vendor No.
The user can select the fuel card vendor
If the "Purchase from vendor" field is blank on the template. The system will take suppliers from the Invoicing Interface
Reason Code
The user selects the reason code
Standard Purchase Code
The user sets up the method of posting the purchase invoice line, which the system will use for posting a non-card transaction that does not go to TK transactions, but goes to a purchase invoice. For fuel card transactions, the setting is set to Template mapping, and there the user must enter "sales" anyway
Do not set to the post-group template, because then they would take precedence over the settings on the vendor and on the standard purchase code.
Insert Dimension 2 – NO YES (Insert Dimension 2)
If checked, the system creates dimension 2=contract if it has not found it in the table of dimension values. E.g. after migration, not all contracts were in the table, the system does not crash by error, but adds. The danger of weeding with bad data that doesn't belong there
If unchecked and the stack row contains a contract number that is not in the dimension values, an error will be reported. It's stricter, but it doesn't weed out the Dimension Values.
...