Explanation of Exact FMUTA files from RetailVista
- 10 Jun 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Explanation of Exact FMUTA files from RetailVista
- Updated on 10 Jun 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
If a '-' is present in the 'RetailVista field' column, it indicates that RetailVista will never populate this field, as it is not implemented. The 'FMUTA explanation' field will still mention what the content of the field would have been according to the Exact documentation. If this explanation is also empty, then the field is not in use according to the Exact documentation.
The fields for the header and detail lines are almost identical. Where they are truly identical, no additional comments are provided in the 'FMUTA explanation' in the detail line section.
Multivers also uses the FMUTA format, but with minor deviations. At the time of writing, the deviation is only present in column 25 of the header line.
The following overview shows the header line from the FMUTA file. The header line is repetitive and can appear later in the file. A header line is identifiable by line number 0.
Column | RetailVista field | FMUTA explanation | |
1 | Line number | ||
2 | Journal type | B - Bank G - Giro M - Memo I - Purchase V - Sale | |
3 | Journal | ||
4 | Period | ||
5 | Fiscal year | Always truncated to 2 characters | |
6 | Document | Fiscal year, journal, and document, max 9 characters | |
7 | Description | ||
8 | Booking date | Format ddmmyyyy | |
9 | - | ||
10 | Debtor | ||
11 | Creditor | ||
12 | - | ||
13 | Amount | ||
14 | Journalize | Always 'N' | |
15 | Currency | Always 'EUR' | |
16 | Exchange rate | Always '1' | |
17 | Credit limit | ||
18 | Credit limit amount | ||
19 | - | Invoice due date | |
20 | - | Credit limit expiration date | |
21 | - | ||
22 | - | ||
23 | - | Week number | |
24 | Invoice reference | Payment reference | |
25 | Payment method code | In case of Multivers FMUTA variant, always empty | |
26 | - | G-account | |
27 | - | ||
28 | - | ||
29 | - | ||
30 | - | ||
31 | - | ||
32 | Subtype | Booking cancellation, sales invoice, etc | |
33 | - | ||
34 | - | ||
35 | - | ||
36 | - | ||
37 | - | ||
38 | - | ||
39 | - | ||
40 | - |
The following overview shows the detail lines from the FMUTA file. The first detail line always has line number 1, and then it is numbered consecutively until the next header line is placed.
Column | RetailVista field | FMUTA explanation | Remark |
1 | Line number | Always equal to header line column 1 | |
2 | Journal type | Always equal to header line column 2 | |
3 | Journal | Always equal to header line column 3 | |
4 | Period | Always equal to header line column 4 | |
5 | Fiscal year | Always equal to column 5 header | |
6 | - | Journal entry | |
7 | Description | ||
8 | Date | Format ddmmyyyy | |
9 | General ledger | ||
10 | Debtor | Always equal to column 10 header | |
11 | Creditor | Always equal to column 11 header | |
12 | Invoice reference | Always equal to column 12 header | |
13 | Amount |
14 | Journalize | Always 'N' | |
15 | - | Currency | Always equal to header column 15 |
16 | - | Exchange rate | Always equal to header column 16 |
17 | Credit limit | Always equal to header column 17 | |
18 | Credit limit amount | Always equal to header column 18 | |
19 | - | Invoice due date | |
20 | - | Credit limit due date | |
21 | VAT code |
22
VAT amount
23
-
Week number
24
-
25
-
26
-
27
Cost center code
28
Cost carrier code
29
Quantity
30
-
31
-
32 | Sub type | Cancellation booking, sales invoice, etc | Always equal to column 32 header |
33 | - | ||
34 | - | ||
35 | - | ||
36 | - | ||
37 | - | ||
38 | - | ||
39 | - | ||
40 | - |
Was this article helpful?