Data from Acubiz is divided into two areas
Posting to ERP
In export formats, the data structure is the same across the different export types. This means that all export types contain the same number of columns, but whether the different columns provide data depends on the export type
Export types:
- Preregistration (provision)
- Costs
- Invoice
- Cash advances
The export types consist of 31 columns with the following information. All postings contains 2 lines - one debet (D+) and one credit (C-) line
Filetype * | |||||||||||
1 | 2 | 3 | 4 | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
# | Description | Datatype | D+ | C- | D+ | C- | D+ | C- | D+ | C- | XML tagname |
1 | Linenumber | String | ● | ● | ● | ● | ● | ● | ● | ● | lineno |
2 | Exportdate | Date | ● | ● | ● | ● | ● | ● | ● | ● | postingdate |
3 | Transactions type (f, d, k) | String | ● | ● | ● | ● | ● | ● | ● | ● | transactiontype |
4 | Account no | String | ● | ● | ● | ● | ● | ● | ● | ● | account |
5 | VAT code | String | ● | vatcode | |||||||
6 | Amount | Number | ● | ● | ● | ● | ● | ● | ● | ● | amount |
7 | Booking currency (ISO) | String | ● | ● | ● | ● | ● | ● | ● | ● | basecurrency |
8 | Used currency amount | Number | ● | ● | ● | ● | ● | ● | ● | ● | amountoriginal |
9 | Used currency (ISO) | String | ● | ● | ● | ● | ● | ● | ● | ● | foreigncurrency |
10 | Record description text | String | ● | ● | ● | ● | ● | ● | ● | ● | bookingtext |
11 | Dimension 1 | String | ● | dim1 | |||||||
12 | Dimension 2 | String | ● | dim2 | |||||||
13 | Dimension 3 | String | ● | dim3 | |||||||
14 | Dimension 4 | String | ● | dim4 | |||||||
15 | Dimension 5 | String | ● | dim5 | |||||||
16 | Dimension 6 | String | ● | dim6 | |||||||
17 | Dimension 7 | String | ● | dim7 | |||||||
18 | Dimension 8 | String | ● | dim8 | |||||||
19 | Dimension 9 | String | ● | dim9 | |||||||
20 | Users initals | String | ● | userninitials | |||||||
21 | Users name | String | ● | username | |||||||
22 | TravelID / ExportNo | String | (●) | (●) | ● | ● | (●) | (●) | (●) | (●) | transactionid |
23 | Key for auto clearing | String | ● | ● | ● | ● | ● | transactionuniquekey | |||
24 | Invoice no (Credit Card) | String | ● | ● | invoiceno | ||||||
25 | Split enclosure no | String | ● | enclosureno | |||||||
26 | Mandatory comment | String | ● | enclmancom | |||||||
27 | Voluntary comment | String | ● | enclvolcom | |||||||
28 | composed #26+#27 | String | ● | enclmancom_enclvolcom | |||||||
29 | Country of use (ISO) | String | ● | ● | ● | ● | ● | countryiso | |||
30 | Filename of reciepts*/Base64** | String | ● | documentationfilenames*/files** | |||||||
31 | Use date | Date | ● | ● | ● | ● | ● | ● | transactiondate |
* Possible multiple files seperated by * (asterix)
** Base64 encoded images are only available in the XML export format, and will replace the naming used in CSV
Base64 encoded files/receipts
Example of data output in the XML file
<files>
<file filetype="JPG" filename="[base64encodeddata]</file>
</files>
See File examples - txt (csv) and xml
Comments
0 comments
Please sign in to leave a comment.