Change Log

Supplier Settlement

The functionality of Midoco Supplier Settlement has been significantly enhanced. This manual thus replaces the previously available manual „Leistungsträgerabstimmung – Benutzeranweisung" from 2006. 

Terms used in this document are explained in the Abbreviations/Definitions section.

General Notes:

1. In all tables the columns can be dragged to another position (left or right) by left click+hold.
   In all tables the contents of the columns can be sorted by clicking on the column name:
   
   
   1. Ascending at first click
   2. Descending on second click
      
      
2. In all tables it is possible to access a context menu with a right click.
   This context menu provides standard operations of Midoco and the respective table.
   
   
3. If several suppliers are to be settled with one file, there are two ways to proceed:
   
   
   1. There is a column "Supllier" in the settlement file and this column is loaded accordingly.

   2. The suppliers are assigned to one settlement group.

      i.e..: XTUI, TUI, TUID share settlement group „TUI"; if a file with the service provider "TUI" is loaded, only the booking number and not the LT code is used when matching the suppliers in this group.

4. Differences / Tolerances:
   Since small differences often occur with some suppliers, an option was created to set a tolerance for them.
   In order master data at supplier level, the tab "Settlement differences" has therefore been created. 
   Here you can enter whether (you may define absolute values as well as percentage values):

   1. The purchase price may vary ("(Purchase) Price Difference")
   2. The revenue of the can vary („Revenue/Commission Diff.")

   This must be set per supplier and per travel type. If the tolerance should be the same for all travel types, you can enter a " * " there.
   Furthermore, the account to which the difference is to be posted needs to be specified.
   This ensures there are no more open entries on the corresponding accounts.
   Note: it should be checked whether the differences have to be subject to VAT/VAT (if necessary)
   → see Supplier Master Data - Settlement Differences

5. Settlement of purchase price and commission for a supplier within a package:
   If a commission is to be settled for an item within a package in addition to the actual purchase price, there are two ways to proceed:

   1. Purchase price and commission are imported and booked in separate files.
   2. The purchase price, included in the file  is reduced by the commission, then import and posting can also take place in one file.

   Note: The revenue accounts of the package supplier ( flagged as "Tour Operator) are used for the commission. If defined, also the account "Commission Receivable" set there is addressed.
   If the commissions are to be broken down further, the functionality "Virtual Accounts" in conjunction with "Product Types" can be used. 

Supplier Master Data - Settlement Differences

To handle differences the tab "Settlement Differences" is available in Supplier master data. Here you can define whether a difference (percentage or absolute amount) should be ignored by Midoco.

Furthermore, the difference determined can be posted to a separate account, within the defined tolerance.

^{"Settlement Differences" tab in Order Master Data / Supplier}

Field description:

1. (Purchase) Price Difference
   here you enter the maximum amount by which the settled amount may differ from Midoco.
2. (Purchase) Price Diff Percent
   here you enter the number (percent, without percent sign) by which the settled amount may differ from Midoco.
   Note: it is only possible to enter either an absolute amount or a relative amount.
3. Revenue/Commission Diff.
   here the revenue amount is entered, by which the revenue of Midoco vs settlement may differ at most.
4. Revenue/Commission Diff. Percent:
   here you enter the number (percent, without percent sign) by which the revenue of Midoco vs. settlement may differ at most.
   Note: it is only possible to enter either an absolute amount or a relative amount.
5. Supplier ID:
   this field is automatically filled by Midoco using the Supplier.
6. Travel Type:
   with this field an individual difference can be entered for each travel type.
   Note: If you do not wish the difference to be restricted by travel type, then enter " * " (asterisk) in this field.
7. If the difference, which is within the specified tolerance, is to be posted to a separate account, you can specify this here:
   
   1. Diff Account without VAT
   2. Diff Account with VAT
   Note: The selection "vat-free" vs "vatable" is based on the VAT of the service.
   Note 2: If you do not want to post the difference to a specific account, just leave these fields empty.
8. Vakid From:
   The validity of the settings is defined here.

Note: Only in the case of price differences (Midoco vs. settlement) the difference will be posted.

If the calculated commission according to Midoco differs from the settled commission, no difference is booked.

Program functionality description for handling partial and full purchase invoices

1. if a booking was marked as a deposit 
1. in the tab "Bookings" this item is displayed with status "green", a posting is created against the account initially addressed for the remaining value.
2. if a posting was not marked as a deposit and
   
   1. the difference is within the tolerance and
   1. an account is specified
      --> In the tab "Bookings", this item is displayed with status "green" and the difference is posted to the defined account.
   2. no account is specified
      --> In the tab "Bookings" this item is displayed with status "green" and the difference remains on the corresponding posting account (no extra posting).
   2. the difference is outside the tolerance and
   1. an account is specified
      -> In the tab "Bookings", this item is displayed with the status "Difference" (orange/yellow/+/-) and the difference remains on the corresponding posting account (no extra posting, previous program behavior).
   2. no account is specified
      -> In the tab "Bookings", this item is displayed with the status "Difference" (orange/yellow/+/-) and the difference remains on the corresponding posting account (no extra posting, previous program behavior).

Importing a settlement file

Opening the dialogue

The dialogue ist opened via the menu "Reconciliation / Supplier Settlement / Electr. Supplier Settlement":

^{Import dialog (menu)}

To load a settlement file, use the "Import" button on the left:

^{Settlement import}

Importing a settlement file using a defined file format

Open the combo box and select the supplier of which you received the settlement. If the supplier is not defined there, no special format is available. 

In this case continue from point "Import of a file using the generic 'MIDOCO' option"

List of currently available formats:

^{Import dialog}

^{Import combobox}

After selecting the supplier, enter the settlement date or select it using the calendar function.
A click on the "Browse" button opens the file selection.
Here you select the file to be loaded and confirm with "Open".

^{Select file}

The content of the file is now displayed.
Lines, which do not belong to the settlement (for example, blank lines or column labels), must now be removed.
To do this, highlight the corresponding line(s) with the mouse and delete them with the "Del" key (on the keyboard).
If too many lines have been deleted by mistake, the import process must be cancelled (button "Cancel") and restarted.
Note: You can also delete the lines that are not required for the settlement (this usually only affects blank lines or headers) in the source file in Excel, for example.
You should not delete any settlement lines, as the settlement then differs from the document and is therefore falsified.
By confirming with "OK" the entries are transferred to Midoco.
During the transfer, a formal check of the contents of the individual data elements is already carried out (e.g. whether a date field contains a date). Depending on this, a corresponding error message may appear (see "Error handling").



^{Data to be processed}

The imported settlement is displayed in Midoco in the tab "Electr. Supplier Settlement".

Special Case BSP-Settlement

The procedure is slightly different for BSP settlements:

1. BSP statements are usually provided in a ZIP archive (file extension = .zip).
2. This archive may not be unzipped, this is done during import.
3. After selecting the file, the "OK" button in the window is disabled for a while. This is due to the large amount of data included in a BSP file.

After a short moment, the button changes to a clickable state.

^{Selection of a BSP settlement as ZIP archive}

4. Instead of the data to be imported, the message "[BSP.zip]" is displayed:

^{BSP settlement loaded}

5. After clicking "OK" the message "BSP_FILE_UPLOADED" appears, the file was uploaded successfully

^{BSP successfully loaded}

6. Depending on the file size, it may take a while (a few minutes) until the settlement is ready for further processing in the tab "Electr. Supplier Settlement". 
If even after this time the settlement does not appear in the list (search with: "Entry date" = [today] and click on "search")

1. 1. the statement was loaded earlier and therefore rejected by Midoco.
   2. the settlement is incorrect and therefore cannot be imported.

7. A BSP file contains all data required for further processing, therefore, unlike some other upload processes, no further query window appears.

Note: During a BSP settlement, the system checks the ticket number because it is unique. There is no check of the Supplier.
Note: In order to correctly assign a BSP settlement to the respective organisational units in Midoco, the agency number must be entered for each unit. (BSP Supplier, order master data, in the tab "Agencies".
Furthermore, the checkbox "Batch settlement" mut be activated.

^{BSP Agency no}

Import of a file using the generic 'MIDOCO' option

Instead of a supplier in the drop-down list, the entry "Midoco" is selected.
Additional fields will then appear in the dialog.
After entering the settlement date and clicking on "Browse", the file selection opens.

^{MIDOCO generic option}

Here the file to be imported is selected and confirmed with "Open".

^{Select file to be loaded}

The content of the file is now displayed.
Lines, which do not belong to the settlement (for example, blank lines or column labels), must now be removed.
To do this, highlight the corresponding line(s) with the mouse and delete them with the "Del" key (on the keyboard).
If too many lines have been deleted by mistake, the import process must be cancelled (button "Cancel") and restarted.
Note: You can also delete the lines that are not required for the settlement (this usually only affects blank lines or headers) in the source file in Excel, for example.
You should not delete any settlement lines, as the settlement then differs from the document and is therefore falsified.
By confirming with "OK" the entries are transferred to Midoco.
During the transfer, a formal check of the contents of the individual data elements is already carried out (e.g. whether a date field contains a date). Depending on this, a corresponding error message may appear (see "Error handling").

^{Loaded file (MIDOCO generic format)}

Now select the date format and, if necessary, the decimal indicator similar to the imported file:

^{Loaded file (MIDOCO generic format) - date format, decimal indicator}

Then activate the checkbox "Needs Supplier Matching", this changes the display of the data in the window.

^{Loaded file (MIDOCO generic format)}

Now select the supplier by clicking the "info" button or enter it directly.
If the Supplier is found within the file and the column assignment was already done in the past, Midoco will recognize this and immediately apply this setting to the corresponding columns.By confirming with "OK" the entries are transferred to Midoco.
During the transfer, a formal check of the contents of the individual data elements is already carried out (e.g. whether a date field contains a date). Depending on this, a corresponding error message may appear (see "Error handling").

^{Loaded file (MIDOCO generic format)}

Import of a supplier´s file (MIDOCO format) for the first time

If a settlement of this service provider has not yet been imported via the entry "Midoco" in the selection list, please select according to the content in the file:

• the separator of the individual data fields (usually a semicolon for CSV files)
• the date format
• the decimal separator
• if necessary the checkbox "Text in Quotes"?

The content of the file is now displayed.
Lines, which do not belong to the settlement (for example, blank lines or column labels), must now be removed.
To do this, highlight the corresponding line(s) with the mouse and delete them with the "Del" key (on the keyboard).
If too many lines have been deleted by mistake, the import process must be cancelled (button "Cancel") and restarted.
Note: You can also delete the lines that are not required for the settlement (this usually only affects blank lines or headers) in the source file in Excel, for example.
You should not delete any settlement lines, as the settlement then differs from the document and is therefore falsified.
By confirming with "OK" the entries are transferred to Midoco.
During the transfer, a formal check of the contents of the individual data elements is already carried out (e.g. whether a date field contains a date). Depending on this, a corresponding error message may appear (see "Error handling").

^{Loaded file (MIDOCO generic format)}

If the checkbox "Needs Supplier Matching" is activated, the display in the window will change.
Now select the supplier by clicking the "info" button or enter it directly.

^{Loaded file (MIDOCO generic format)}

Right-clicking on the individual columns opens a menu.
The entries in the menus are shown below.

Each column is assigned to the corresponding entry from the selection list according to its content.
However, it is not necessary that all columns have an assignment, but all entries with a green check mark must be assigned to a column, otherwise no settlement can be created.

Explanation of the mandatory entries:

1. 1. Settlement Issuer = Supplier
      Note: if there is no supplier in the file, an empty column can get this assignment, because the LT code has already been entered before.
   2. Booking ID = Matching criteria, this entry is used to find the corresponding item in Midoco (in combination with the LT-Code)
   3. Travel Date = to match the travel date saved in Midoco
   4. Billing Date = Billing date of the settlement item

To make full use of the settlement functionality, it is recommended to assign as many columns as possible to the corresponding entries in the selection list.

• Gross amount (of the service), so that differences between supplier and saved values are revealed.
• Commission Amount, as to be able to check the calculated commission, if any.
• Collection Type (AGENCY/SUPPLIER), so that differences resulting from this are revealed

 If an assignment turns out to be wrong, this can be cleared by clicking on the "Delete" entry (the assignment of an entry to this column is deleted).

1. Settlement
   1. Agentur No.
      Number of the agency, important for possible assignment to the correct subsidiary organizational units.
   2. Settlement Issuer
   3. Settlement Period
   4. Settlement Type
2. Booking
   1. Supplier
   2. Booking ID
   3. Travel Date
   4. No of persons
   5. Travel Type
   6. Traveller
   7. Billing Date
   8. Receipt No.
   9. Sign (R 0 invoice, G = credit/negative)
   10. Description
   11. Collection Type (AGENCY/SUPPLIER)
       In contrast to the primary collection type entered, different collection types can also occur in a file; these are then entered in this column.
3. Commission
   1. Currency
      If the supplier is to be settled in a foreign currency, this currency must be included in the settlement file in another column and assigned to this column in Midoco.
      This compares the "Purchase Price FCY" of the item with the foreign currency price according to settlement.
      Note: in order to use the foreign currency functionality, settings are required.
      If a foreign currency is used, the display in the order and in the settlement changes:
   2.   <sup>Details, supplier settlement                                                                                                                                                                                                                                                        
      
      Invoice entries order</sup>
      
   3. Gross Amount
      Price (Gross amount) of the service.
   4. Commission Amount
      Commission gross amount.
      Note: in Midoco the net commission is always calculated for the service and compared with the commission amount in the settlement. If in your case there is a difference in the amount of VAT, try:
      Remove the "Commission Amount" column from the assignment. Midoco will now automatically calculate the net amount from the settlement and compare it with the net amount in Midoco.
   5. Net Amount
      Price (Net amount) of the service.
   6. VAT Amount
      This is the VAT amount of the service.
   7. VAT Percent
   8. Comm. Insurance Amount
      This column is used if the supplier is an insurance company.
      Note: To ensure that the insurance commission of the respective service provider is correctly assigned, activate the checkbox "Insurance" in the supplier master data.
   9. Commission NoVAT
   10. Deposit?
       Note: enter  "is deposit" = "1", "is NOT deposit" = "0" 
   11. FX Amount
       Note: see pont a) in this list.
   12. FX
       Note: see pont a) in this list.
   13. Conversion Rate

After finishing the column assignments, confirm with "OK".
This settlement format is now saved for the selected supplier.

This means that the next file (with exactly the same structure) can be read in without re-assigning the columns to the selected fields.

^{Loaded file (MIDOCO generic format)}

Completing the file import

In case the file doesn´t contain the following columns

• Settlement Period → Enter the billing format in the previously defined format.
• Supplier
• Collection Type (AGENCY/SUPPLIER)

after confirming the import with "OK" the following window appears
The data must be completed, then confirm with OK.

^{Finish file import}

Display of the supplier settlement data

After loading a supplier settlement, it is displayed in the tab "Electr. Supplier Settlement" as shown below
By default, all imported settlements of the current day are displayed; this display can be extended accordingly using the filter fields.
The tab "Electr. Supplier Settlement" is divided into three areas:

1. Filter
   
   1. Creation Date From/To
   2. Settlement Date From/To
      Here you can search for a specific settlement date. This date is specified during import or is included in the import file and can be overwritten in the header fields on the "Bookings" tab (field = "Settlement Day") if the settlement has not yet been posted.
   3. Supplier Code
   4. Booking ID
      Here you can search for a specific Booking ID, all settlements in which this number is available are displayed.
   5. Checked 
      Selection whether the settlement to be searched for has been checked / not checked or both  Note: This always refers to the entire settlement, e.g. "checked = yes" means that the entire settlement was checked (if only individual items were checked, this settlement does not appear in this selection, but with "both" and "no")
   6. Settlement Booked Note: This always refers to the entire settlement, e.g. "Booked = yes" means that the entire settlement was booked (if only individual items were booked, this settlement does not appear in this selection, but with "both" and "no")
2. Result Table
   Explanation of columns: 
   1. Supplier ID
      Supplier acc. to import
   2. Settlement Day
   3. Creation Date
   4. Status Checked
      The number of items that have already been checked and the number of all items in a settlement are displayed here.
   5. Status Booked
      The number of items that have already been booked and the number of all items in a settlement are displayed here.
   6. Transaction Reference
      Is preset with the month (two digits) and the year (two digits) of the settlement date, can be edited / set in the tab "Bookings".
   7. Show
      The tab "Bookings" is opened and displays the settlement details.
   8. Check
      A grey check mark is displayed if not all items have been checked yet. Changes to a green check mark as soon as all items have been checked.
      It is recommended to check the items for the entire settlement by clicking this check mark. After the check via this function, the tab "Bookings" is automatically displayed. The same effect is achieved by clicking the button in the "Show" column. 
   9. Delete
      As long as the settlement has not been booked, you can delete it. Once an item has been posted, the settlement cannot be deleted. 
3. Buttons
   1. Search
      After entering the search criteria, the query is executed by clicking this button.
   2. Import
      Opens the import screen
   3. Book
      Books the correspondingly selected settlement, a dialog box appears which must be confirmed.
   4. Clear
      Clears the entire tab "Electr. Supplier Settlement"
   5. Export
      The list of results is exported to an Excel sheet.
   6. Print
      Creates a PDF out of the list of results.

^{Electr. Supplier Settlement, results}

Tab „Bookings"

This tab displays the individual items of the imported statement.
It is divided into three parts:

^{Tab Bookings}

1. Header

This tab provides information on the whole settlement file.
If necessary, you can set the following values here:

1. 1. Settlement Day
      Note: It is not possible to use a date in the future.
   2. Due Date (preset with the settlement day)
   3. Transaction Reference

This modification must be confirmed with "save".

2. Filter

These fields can be used to change the view of the lower list
The following fields only contain elements from the displayed settlement file (analogous to Excel's auto filter function) and are therefore empty or cannot be selected if the corresponding information is not included in the settlement file:

• • Supplier agency no
  • Supplier
  • Traveltype

The filters can be reset by clicking the "reload" button.
The set filter criteria are saved so that you can switch between the general view and the filter view.

3. Result table

^{Bookings, result table}

The result table lists all positions of the settlement file.
Click on a column title sorts the contents of the column in ascending order ( ), a second click sorts the content in descending order ( ).

Column Headers

1. 1. Position 
   2. Org.Unit
   3. Supplier agency no.
   4. Supplier
   5. Booking Id
   6. Settlement Payment Type
   7. Traveller
   8. Travel Date
   9. Traveltype
   10. Price acc. to Midoco
   11. Price acc. to settlement
   12. Nat Amount (Payable amount acc. to settlement)
   13. calculated revenue
   14. Revenue difference
   15. Service status
   16. Persons
   17. Booked
       Indicates whether the item has been posted
   18. Ignore
       indicates whether the item was ignored (user action required)
   19. Deposit
       indicates whether the item represents a deposit
   20. Manual Entry
       indicates that the position has been converted into a manual booking, i.e. at least one manual posting record has been entered and saved for this record(siehe Manuelles Buchen)

   21. Status (Indicators)

       shows the status of the position, the "Status" column can have the following content:
       1.  - the record has not yet been checked
          All other states occur only after a data record has been checked:
       2.  - no matching service was found (booking ID does not exist)
       3.  - a corresponding service was found, the amounts match
       4. - A corresponding service was found, the amounts match. The tiny orange dot in the lower right corner indicates that this (potentially also other purchase positions) were not yet booked.
       5.  /  - a matching service was found, a difference was calculated (the settlement shows a higher amount / revenue than Midoco)
          Note: the difference can be made up of several postings with this booking ID (e.g. from another settlement)
       6.  /  - a matching service was found, a difference was determined (the settlement shows a lower amount / revenue than Midoco)
          Note: the difference can be made up of several postings with this booking ID (e.g. from another settlement)
       7.  - a matching service was found, a booking is not necessary (order with errors or amount 0,00)
       8.  - the settlement position was marked with "manually checked"
       9. - an error has occurred (for example, it was determined during posting that a required cost center does not exist, an exact error message appears at this status)
       10.   - the Form of Payment in the statement vs. the order does not match
       11. - from Release 19.4: the related order/item has an error which potentially may lead to wrong journals being created. The order errors need fixing first and this transaction needs to be checked again prior to being able to create journals for it. This status blocks this transaction from being booked for as long as it has this status.
       Note: This is a step-by-step check: 
       1. first it is checked whether the settlement amount matches the service price in Midoco (deviations are shown in orange (+/-)
       2. then it is checked whether the settled commission matches the commission calculated by Midoco (set on the respective service provider in the order master data under payment conditions) (deviations are shown in yellow (+/-). If there is a difference as described under i., it remains orange (+/-)
       Note 2: Depending on the settings on the tab page "Settlement Differencies" in the respective master data of the supplier, the display of the differences may vary. This means that differences may not be displayed because they are ignored according to the settings.
   22. Order The symbol indicates whether an order has been found, a click will opens it.
   23. Check
       by clicking on the icon, the individual item is checked (e.g. useful after changes in the order)
   24. Split
       Here you can split a position (e.g. several services were invoiced in one booking number)
       Note: The "Split" function will only be available if the position to be split has not yet been posted
       Click on the icon to open the following dialog box:

Here it is possible to enter another booking ID. If the supplier is different, you can replace it.
The amount belonging to this position is entered in the "Net amount" field.
Note on BSP settlements: Tickets cannot be split as they are clearly assigned to a specific ticket number.
Note: the amount in the "Net amount" field must be less than the predefined amount, but also greater than zero, otherwise a zero posting would occur in both cases (an error message appears) 

After confirming with "OK", the original position is reduced by the amount entered.

A new line is created with the entered amount. This settlement item behaves in the same way as all other items. There is no longer a reference to the split item.
An amount that has already been split up once can be split further, in accordance with the conditions above 

Buttons:

1. Set Item Price
   If a service has been found for the booking ID and the settlement amount differs from the expected settlement amount, the service price in the order can be adjusted according to the settlement amount by clicking this button.
   Hinweis: there is neither a further question nor a confirmation of this action. After clicking, the column "Price acc. to Midoco" will show the same amount as in column "Price acc. to settlement".
2. Export
   the result table is exported as it appears on the screen.
3. Print
   a PDF file is generated
4. Refresh
   The table is reloaded, e.g. to refresh all entries after filtering, but also to solve display problems / update problems of the display (e.g. after checking or splitting of entries)
5. Report
   Clicking this button will open a dialog.
   After confirmation with "OK", the corresponding export is carried out, including the differences.

^{Report dialog}

     6. Overview Bookings
         Switches to the tab "Overview Bookings" and shows the items of the current settlement that have already been checked and show a difference.

Working on the settlement positions

Dialogue 'Details View'

Double-click on a line or click on the status indicator to open a new dialog

^{Details View}

The dialog box is divided into three sections:

1. Comparision
   Here data from Midoco and the settlement are compared.
   Note: the status is updated for the first two lines, the other lines are for information purposes, no status adjustment is made here.
   
   
   1. Checkbox „Ignore Booking"
      This checkbox prevents the posting of this item.
      This function can be used to prevent a transaction that has not yet been clarified from being posted, especially when using the " Book" button in the tab "Electr. Supplier Settlement" (the entire settlement is posted).
      By activating this checkbox, the difference in the "Total difference" area is recalculated. This means that an ignored data set is also ignored in the difference calculation.
      Note: the settlement is therefore not complete, a (later) posting is recommended.
   2. Checkbox „manual checked"
      This checkbox sets the status in the result table.
      Note: If there is a difference, it will be ignored.
   3. Checkbox „Manual Booking"
      This checkbox activates a section " Manual Booking" in the popup.
      
      ^{Section Manual Booking}
      
      The question below appears if the record has already been "checked" (either as part of the entire stack or separately using the "check" button in the "Bookings" tab) and a suitable service has been found
      Note: You can only either post on the item or enter a manual posting. Both of these together is not permitted.
      
      

      Here you have the option to allocate individual postings within the reconciliation as in "manual booking" and to post them within the batch processing. 

      This is useful, if the settlement file of a supplier contains non-order-related data, i.e. data that cannot be (directly) assigned to a service.

      The account assignment is carried out as usual. You can navigate through the fields by pressing the tab key. Standing in the last field and pressing TAB moves the posting record to the table.

      
      ^{Table manual booking}
      
      
      The button "Save" stores the entries, the following question appears:
      
      
      
      
      Confirm mith "Yes" or use "Cancel":
      Unsaved bookings are discarded when leaving the popup!    Bookings already entered and saved cannot be deleted. If an adjustment is necessary, a reverse posting record must be entered to cancel the posting
      
      
      saved booking record
      
      Further postings can be entered until the batch (and thus the manually entered postings) has been posted.
      
      Note: The checkbox "ignore" also works in this case, as described in point 1a). This means that the entered postings are not posted as long as the checkbox "ignore" is activated.
      
      
   4. Button „Detach"
      This button disconnects the found service from this record.
      This function can be used if the service is still associated with the billing record when the booking ID has been changed in the order and checked again.
      Note: The check must be repeated if the booking number is to be matched again.
2. Differences
   Here the sum of all bookings available for the booking ID is compared with the service price found in Midoco.
3. Postings for Booking ID
   All invoice entries, which have been entered for this Booking ID, are displayed here.
   The first line shows the incoming invoice of the current settlement (the settlement you are currently working on).
   Note: Please consider the symbol in the column "book", if it is green, the settlement is booked. If the symbol is gray, the settlement has not yet been posted.
   
   Columns:
   
   
   1. Invoice Date
      Transaction Date (invoice entry or settlement)
   2. Amount
   3. Invoice No.
      Abrechnungsbetrag
   4. Collection Mode
      Agency- or Supplier collection
   5. Revenue incl. VAT
      Posting to the account defined in supplier master data
   6. Revenue VAT free
      Posting to the account defined in supplier master data
   7. Revenue Insurance
      Posting to the account defined in supplier master data
   8. Total Price
   9. Supplier DC Amount
      Supplier collection amount
   10. Creation Type
       Indicates the origin of the entry:
       
       1. Settlement → This record was created electr. Supplier settlement.
       2. Advice → This record was created by a payment advice.
       3. Manually → The incoming invoice was entered manually.
       4. Automatik → This record was created automatically, i.e. accrual.
   11. Voided?
       This column indicates whether the respective transaction has been voided, it is therefore displayed in gray.
   12. Show
       Click on the icon to display the posting in the original document (for example, the system switches to the corresponding reconciliation).
   13. book
       The icon is gray if the booking has not yet been posted.
       By clicking on the icon the booking is posted, the icon colour changes to green.
       Note: At this point, all displayed bookings can be finally posted, It does not matter, whether you are in the original settlement. 
       The following window pops up:
       
       By clicking on "OK" the posting is done accordingly.
   14. Details of a position
       A double-click opens the detailed display of the respective line, as long as it has not yet been posted.

                       If the line has already been posted, then:

                       - The detailed display opens for the first item (= current settlement), but fields can no longer be edited 

                       - For all other lines, the system jumps to the respective settlement.

1. 1. Orig. Amount
      Here the original amount of the settlement is shown, it cannot be edited.
   2. Net
      Here the net amount is shown (corresponds to the original amount by default), can be changed.
      This changes the settlement amount to the amount entered and is posted accordingly.
   3. Description
      A description can be entered here.
   4. IsDeposit
      Indicates whether the settlement is a deposit.
   5. Settl. Type
      Selection of the settlement type.
      Note:
      To be able to select a type here, you must
      
      1. The "Settlement types" tab in the order master data can be added by the "ordersd_settlement_types" module.
      2. The required settlement types are then entered there.
      3. In supplier master data, a settlement type can be assigned to the supplier.
   6. Comments
      A comment can be entered; this is then also visible in the table in the "Bookings" tab in the " Comment" column.

Tab 'Overview Bookings'

The tab can be called up directly from a settlement, in this case only the items of the respective settlement (and any associated postings) are filtered.

Note: If you want to filter postings outside the current settlement, you must first click on the " Clear" button. By doing so, the relationship to a settlement is cancelled.
The tab can be called up directly, then it is possible to filter all orders / services in Midoco (depending on the assigned organizational unit).

Note: In this query, all postings / settlements for a Booking ID are displayed. This means that even if, i.e. "Settlement Booked | No" is selected, the posted lines are still displayed in the details to provide a complete overview of this data record.


^{Overview Bookings}

The tab is divided into two sections:

1. Filter area
   1. Creation Date From/To
      Creation date of the order (these dates can be a maximum of 30 days apart).
   2. Travel Date Fraom/To
      These dates can be a maximum of 30 days apart.
   3. Supplier Code
   4. Travel Type
      Only travel types that have been created in master data are displayed here.
   5. Settlement Group
      Only Settlement Groups that have been created in master data are displayed here.
   6. Org. Unit
      By default, all assigned units are included in the search. It is recommended that you narrow down the search when there is a lot of data (for example, when org. units share databases and the dataset may be very large).
      Note: Only those org. units are available for selection to which the logged-in user is assigned.
   7. Has supplier invoice
      Yes = invoice entries exist (from posted/unposted payment advices and/or electr. supplier settlement and/or from manually posted incoming invoices)
      No = There are no invoice entries (accruals are not considered as incoming invoices, corresponding orders are therefore displayed here)
      Both = Display of all services in the period under review.
   8. Settlement Booked 
      Hinweis: depending on the settings in the supplier (tab Settlement differences), deviations within the tolerance set there are treated accordingly as "Difference | No".
       
2. Result table
   In the result table, the corresponding data (depending on the filtering) is displayed in aggregated form. This means that there is exactly one row for each booking ID.
   Columns:
   
   1. Item Org. Unit
      Indicates the org. unit in which this entry is located. Especially with more complex hierarchical constructions (e.g. many org. units on one order database), previous filtering is useful
   2. Settlement Total
      The total of all settlements / postings for this data record.
   3. Difference
      The sum of all differences of the settled values as opposed to the values in Midoco.
   4. Supplier
   5. Booking Id
   6. Settlement Payment Type
   7. Traveller
   8. Travel Date
      Travel Date acc. to order.
   9. Traveltype
   10. Price acc. to Midoco
       Abrechnungsbetrag laut Midoco
   11. calc. Revenue
   12. Revenue Diff.
   13. service status
       Status der Leistung in Midoco
   14. Pers.
       Total number of travellers in Midoco
   15. Status
       Status of the entire existing settlement / postings for this item with the specifications from the "Bookings" tab.
   16. Check
       Checks whether any changes have occurred (e.g. changes in service)
   17. Create Advice
       Clicking on the icon transfers the item to "Remittance Advice" for further processing.
       
       This function can be used to:
       
       1. Carry out the settlement of not yet settled postings of a supplier.
       2. To invoice a supplier for differences from settlements
          
          A double click on a line opens a window in which all related bookings are displayed:
          
          ^{Details, Overview Bookings}
          
          Columns:
       3. Invoice Date
       4. Amount
          Total of the respective settlement / posting
       5. Invoice No.
       6. Collection Mode
       7. Revenue incl. VAT
       8. Revenue VAT free
       9. Revenue Insurance
       10. Total Price
       11. Supplier DC Amount
       12. Creation Type
           Zeigt an, aus welcher Buchungsquelle die Zeile stammt:
           1. Settlement → This record was created electr. Supplier settlement.
           2. Advice → This record was created by a payment advice.
           3. Manually → The incoming invoice was entered manually.
           4. Automatik → This record was created automatically, i.e. accrual.
       13. Show
           Click on the icon to display the posting in the original document (for example, the system switches to the corresponding reconciliation).
       14. book
           The icon is gray if the booking has not yet been posted.
           By clicking on the icon the booking is posted, the icon colour changes to green.

Additional functionalities BSP Settlement

Allocation of an ADM (D) or ACM (C) to different orders - the respective items are not yet created in the orders.

Note: Since Tickets (T), Refunds (R) and EMD's (E) each refer to one particular ticket, splitting is not possible here.

If no matching ticket is found in Midoco after checking a BSP statement, an icon (search) appears in this column ( ).
Hinweis: Refunds are created automatically during the check if the ticket number is found in an order (i.e. if an order only contains ticket "T/123456", the BSP settlement contains a refund "R/123456", it is automatically created in the order). 

This function can also be disabled, if you wish to do so please contact Midoco Support.

Using the "magnifying glass", the order search can be called up directly:

^{Order search from BSP settlement}

Here you can search for orders and assign them directly to a settlement item:

1. For this, fill in the search criteria and click "Search"
2. Select the order from the ones found and open a new dialog by double-clicking.
3. Select the resp. passenger via the selection list in the upper part.
4. By clicking "new", a corresponding new item is created in the order
   
   ^{Create / assign ticket to an order}

Error Handling

Error Handling in Supplier Settlement

1. „Supplier settlement MIDOCO […] was already imported. "
   
   
   This error indicates that a file of exactly the same type has already been loaded.
   Here you should check whether this is the case (compare the files already loaded with the (supposedly) new file).
2. "No org. unit found for agency no. XXXX"
   
   This error message means that the agency numbers included in the settlement file are not entered in the order master data of supplier.
   For information on how agency numbers are defined, see Additional Information - Definition of Agency Numbers.
    

Additional Information

Definition of Agency Numbers

Some suppliers include agency numbers in their settlement files.

These must be entered in the order master data of the supplier so that the settlement file can be uploaded and validated correctly: