Short Description
...
Test data for invoicing integration can be generated in the Dataloy VMS post fixture modules (Accounts Receivable, Accounts Payable and Hire Payable).
Post Transaction
When an invoice is successfully transferred to an accounting system, the document status must be updated to Posted in Dataloy VMS. This is done in a PUT request:
...
| Code Block | ||
|---|---|---|
| ||
GET /VoyageHeader?filter=modifiedDate(GTE)2014-01-01T12:30:00 |
Post Transaction
No post transaction is required.
...
Create test data for transferring business partners from Dataloy VMS by updating Business Partners in Master Data.
Post Transaction
No post transaction is required.
...
Before setting up and testing a bunker transaction integration other integrations need to be in place.
- Transfer of voyage related data to the accounting system.
- Synchronization of business partners between Dataloy VMS and the accounting system.
- Exchange rate transfer to Dataloy VMS.
...
More information: /DocumentType, /Document.
Post Transaction
When an invoice is successfully transferred to the accounting system, the document status has to be updated to Posted in Dataloy VMS. This is done in a PUT request:
...
Create an invoice in Dataloy VMS and transfer it to the accounting system. Create a payment in the accounting system and transfer it to Dataloy VMS.
Post transaction
No post transaction is required.
...
More information: /DocumentType, /Document.
Test Data
Test data for accruals integration can be generated in the Accruals module in Dataloy VMS. Generate and batch post the accruals.
Post Transaction
When an accrual is successfully transferred to an accounting system, the accrual status must to be updated to Posted in Dataloy VMS. This is done in a PUT request:
...
| Field Name | Description | Not possible to user in filters |
|---|---|---|
| documentAmount |
| |
| companyCurrencyAmount | For all /DocumentType : Amount in Company Currency for the Document.Company. | |
| sourceCurrencyAmount |
| |
| documentCurrency.currencyCode | Currency Code for documentAmount. More information, see documentAmount | |
| sourceCurrencyCode | Currency code for sourceCurrencyAmount. More information see sourceCurrencyAmount | |
| exchangeRate | Exchange Rate between documentAmount and sourceCurrencyAmount | |
| exchangeRateDate | Exchange Rate Date | |
| glAccount | General Ledger Account | X |
| quantity | Has Different Meaning Depending on Document Type:
| |
| unitPrice | Unit Price. Quantity * Unit Price = Document Amount | |
| invoicingStatus.statusTypeCode | Status Code, see Document Status List | |
| documentLineText | Document Line Text/Description | |
| businessPartner | Business Partner Object. (Value: businessPartnerCode or businessPartner Key). Invoice and Payment/Receipt:
| |
| isAccountsPayable | false = Accounts Receivable, true = Accounts Payable Inserting Payment/Receipt: For payments referring to Accounts Receivable invoices set value to 0. For payments referring to Accounts Payable invoice set value to 1. This value should always have the same value as for the referring invoice. | |
| refDocument | Referring Document for Reversals, Payments and Receipts. To set refDocument use Document Number or Key. Payment/Receipts: Setting refDocument for payment receipts, documentLine.voyage will be set equal to the documentLine.voyage of the referring invoice. | |
| vatRate.vatRate | VAT Rate | |
| vatRate.vat.vatCode | VAT Code | |
| freightRate | Freight Rate Object | |
| portCall | portCall Object | |
| handlingCost | handlingCost Object | |
| businessUnit | businessUnit Object | |
| account | Account Object, use glAccount instead | |
| handlingCostCode | handlingCostCode Object, use glAccount instead | |
| billOfLading | billOfLading Object | |
| claim | Claim Object | |
| offhire | Offhire Object | |
| voyage | Voyage Object |
...