This guide describes the operational logic and data transfer between Rackbeat and Netvisor. The guide answers which program data should be updated in to ensure it is also updated in the other program.
CONTENTS
- General
- Customers
- Suppliers
- Products
- Product structures
- Sales orders
- Purchase orders
- Sales invoices
- Purchase invoices
- Accounting targets
General
This guide explains how data is transferred between the programs. The table below describes which program data is updated in. For example, product information is updated in Rackbeat, from where it is then automatically updated to Netvisor.
Subject | Master |
Product information | Rackbeat |
Customer details | Rackbeat |
Vendor details | Rackbeat |
Sales orders | Rackbeat |
Purchase orders | Rackbeat |
Creating sales invoices | Rackbeat |
Sending sales invoices | Netvisor |
Processing purchase invoices | Netvisor |
Bookkeeping | Netvisor |
Accounting targets | Netvisor |
Customers
During use, new customers and updated customer details are automatically transferred from Rackbeat to Netvisor via integration. Creating a customer or updating customer details triggers automatic data transfer. Adding customer details to Rackbeat via CSV does not trigger immediate data transfer. In the evenings, a scheduled register synchronization is run between Rackbeat and Netvisor to ensure the customer register data is up to date. Synchronization is also used during implementation if the supplier register has been imported to Rackbeat first.
Note! If the customer register is to be transferred from Netvisor to Rackbeat, customers in Netvisor must have customer codes consisting of numbers. The customer number must not start with 0.
Rackbeat | Netvisor |
Name | Name |
Number | Customer code |
Business id | Business id |
Group | Customer group |
Billing address, street address | Billing address |
Postal code | Postal code |
City | Postal address |
Country | Country |
For customer groups, the name is transferred from Rackbeat to Netvisor's customer group.
Rackbeat's country list is as follows, if no country information is found, the default selection is FI
"default": "FI",
"albania": "AL",
"andorra": "AD",
"austria": "AT",
"belarus": "BY",
"belgium": "BE",
"bosnia and herzegovina": "BA",
"bulgaria": "BG",
"croatia": "HR",
"cyprus": "CY",
"czech republic": "CZ",
"czechia": "CZ",
"denmark": "DK",
"estonia": "EE",
"finland": "FI",
"france": "FR",
"germany": "DE",
"greece": "GR",
"hungary": "HU",
"iceland": "IS",
"ireland": "IE",
"italy": "IT",
"kosovo": "XK",
"latvia": "LV",
"liechtenstein": "LI",
"lithuania": "LT",
"luxembourg": "LU",
"malta": "MT",
"moldova": "MD",
"monaco": "MC",
"montenegro": "ME",
"netherlands": "NL",
"north macedonia": "MK",
"norway": "NO",
"poland": "PL",
"portugal": "PT",
"romania": "RO",
"russia": "RU",
"san marino": "SM",
"serbia": "RS",
"slovakia": "SK",
"slovenia": "SI",
"spain": "ES",
"sweden": "SE",
"switzerland": "CH",
"ukraine": "UA",
"united kingdom": "GB",
"vatican city": "VA",
"suomi": "FI",
"ruotsi": "SE",
"sverige": "SE",
"norge": "NO",
"norja": "NO",
"tanska": "DK",
"danmark": "DK",
"hollanti": "NL",
"eesti": "EE",
"usa": "US",
"yhdysvallat": "US"
Suppliers
During use, new suppliers and updated vendor details are automatically transferred from Rackbeat to Netvisor via integration.
Creating a supplier or updating vendor details triggers automatic data transfer. Adding vendor details to Rackbeat via CSV does not trigger immediate data transfer. In the evenings, a scheduled register synchronization is also run between Rackbeat and Netvisor to ensure the supplier register data is up to date. Synchronization is also used during implementation if the supplier register has been imported to Rackbeat first.
Note! If the supplier register is to be transferred from Netvisor to Rackbeat, customers in Netvisor must have supplier codes consisting of numbers. The supplier number must not start with 0.
In the transfer of a supplier from Rackbeat to Netvisor, the following information is transferred from the supplier card:
Rackbeat | Netvisor |
Number | Supplier code |
Supplier name | Name |
Business id | Business id |
Street address | Address |
Postal code | Postal code |
City | Postal address |
Country | Country |
Products
During use, new products and updated product information are automatically transferred from Rackbeat to Netvisor via integration. Creating a product, updating product information, or saving triggers automatic data transfer. Adding product information to Rackbeat via CSV does not trigger immediate data transfer. In the evenings, a scheduled register synchronization is also run between Rackbeat and Netvisor to ensure the product register data is up to date. Synchronization is also used during implementation if the product register has been imported to Rackbeat first.
In the transfer of products from Rackbeat to Netvisor, the following information is transferred from the product card:
Rackbeat | Netvisor |
Name | Item |
Number | Product code |
Description | Description |
Unit | Unit |
Product group | Product group |
Base price | Base price |
Recommended purchase price | Purchase price |
The following information is retrieved from Rackbeat's product group during the transfer of products:
Domestic VAT | VAT rate |
The transferred information is the same for both a regular product and the main product of a product structure.
Product structures
For product structures, the main product is synchronized to Netvisor as a regular product. Sub-products are transferred with normal products to Netvisor. The product structure itself is not transferred to Netvisor.
Sales orders
When an order confirmation is sent from a sales order in Rackbeat, it is transferred to Netvisor for cash flow forecasting. When a sales order is delivered from Rackbeat, the delivery information is updated to Netvisor. When the order is invoiced from Rackbeat, the order is removed from Netvisor and a sales invoice is created in its place. Note! Partial delivery information of a sales order is not currently visible in Netvisor.
The following information is transferred from Rackbeat to Netvisor from the sales order header:
Rackbeat | Netvisor |
Sales order number | Order number |
Customer | Customer |
Order date | Date |
Delivery date | Delivery date |
Billing address | Billing address |
Our reference* | Our reference |
Your reference | Your reference |
Additional information if contains letters | Internal additional information |
Additional information if only numbers | Contract id |
Note | Text before invoice rows |
Order number** | External order number |
Seller*** | Seller |
For the seller information, the following logic is followed:
*If there is no name in Rackbeat's seller field, it is checked whether the Our reference field matches the name of a seller found in Netvisor. If it matches, the information is set as the seller of the order in Netvisor.
**Order number here is the Rackbeat order number. If you want the customer's actual order number in the External order number field, it must be in the Your reference field and either consist only of numbers, or start with OT or PO followed by only numbers.
***If the name in Rackbeat's seller field matches the name of a seller found in Netvisor, the information is set as the seller of the order in Netvisor.
If no matches are found in either way, no seller is set for the order in Netvisor by the integration.
The following information is transferred from Rackbeat to Netvisor from the sales order lines:
Rackbeat | Netvisor |
Product number | Product code |
Product name | Product |
Unit price | Unit price (VAT 0) |
VAT-% | VAT-% |
Quantity | Quantity |
Purchase orders
When a purchase order is sent to the supplier from Rackbeat, it is transferred to Netvisor for cash flow forecasting and invoice allocating. When the purchase order is received in Rackbeat, the information is updated on the purchase order in Netvisor. This allows delivery information to be used in invoice allocating.
The following information is transferred from Rackbeat to Netvisor from the purchase order header:
Rackbeat | Netvisor |
Purchase order number | Purchase order number |
Supplier | Supplier |
Date | Purchase order date |
Billing address | Supplier address |
Delivery address name | Receiver |
Delivery address | Delivery address |
Note | Comment |
Currency | Currency |
Payment terms | Payment term |
The following details from the purchase order lines are transferred from Rackbeat to Netvisor:
Rackbeat | Netvisor |
Product number | Product code |
Supplier product code | Supplier code |
Quantity | Quantity |
Unit price | Unit price |
Delivered quantity | Delivered quantity |
Delivery date of receipt | Actual delivery date |
Note! The delivered quantity and delivery date are added to the line only when the receipt has been made in Rackbeat.
Sales invoices
When a sales order is invoiced in Rackbeat, the invoice is transferred to Netvisor after the user has recorded it. The invoice is sent to the customer from Netvisor. Netvisor generates a reference number for the invoice. If the product on the invoice is marked with an EAN code, i.e. the barcode on the product card, this is transferred to the sales invoice in the row specification field.
The following header details from the sales invoice are transferred from Rackbeat to Netvisor:
Rackbeat | Netvisor |
Customer | Customer |
Billing address | Billing address (postal address, not e-invoice address) |
Invoice date | Invoice date |
Due date | Due date |
Our reference | Our reference |
Your reference | Your reference |
Note | Text before invoice rows |
Order number | External order number |
Additional information if numeric | Contract id |
The following item details from the sales invoice are transferred from Rackbeat to Netvisor:
Rackbeat | Netvisor |
Product number | Product code |
Product name | Product |
Quantity | Quantity |
Unit* | Unit* |
Unit price | Unit price excl. VAT |
VAT-% | VAT-% |
*If extended product management is enabled in Netvisor, the unit on the sales invoice comes from the Netvisor product card.
Purchase invoices
Purchase invoices are received in Netvisor. When a purchase order in Netvisor is matched to a purchase invoice, the integration transfers the matched purchase invoice to Rackbeat. The invoice accounts payable process is fully managed in Netvisor. Rackbeat does not transfer purchase invoices to Netvisor.
The following header details from the purchase invoice are transferred from Netvisor to Rackbeat:
Netvisor | Rackbeat |
Supplier | Supplier |
Purchase order number (purchase order allocating) | Purchase order number (purchase order allocating) |
Purchase invoice number | Supplier invoice number |
The following item details from the purchase invoice are transferred from Netvisor to Rackbeat:
Netvisor | Rackbeat |
Product code | Product number |
VAT-% | VAT-% |
Quantity | Quantity |
Unit price (excl. VAT) | Unit price |
There may be slight rounding differences in unit and line prices due to the necessity of calculating tax-exempt prices between systems based on the taxable prices provided by Netvisor's interface.
Accounting targets
Rackbeat does not use cost centres/accounting targets. However, if accounting targets are set behind a customer or product in Netvisor, they appear on the sales invoice sent from Netvisor.
Keywords: Rackbeat-Netvisor operational logic, data update, synchronization.
Did you find it helpful? Yes No
Send feedback