Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Posting Information to Sage

The Vision to Sage Manager Service must be running for Vision Commerce to post data to Sage. 

Everything posted to Sage is sent to the Windows Messaging Queue service as a ‘message’.  Vision Commerce creates these ‘messages’, for the Vision to Sage Manager Service to handle in a queue process.  The messages are explained in more detail below.

Customer & Supplier Data

Customer Maintenance

Create

Create messages are sent to Sage when a new customer is created in Vision Commerce in the ‘Customer Maintenance’ window.  This posting updates Sage with the new customer information.

The first time a customer is set up in Vision Commerce, a posting will be made to Sage as a ‘Customer CREATE’ message.  It is therefore important that all customers are first set up in Vision Commerce, for Sage to be automatically updated.

Edit

Edit messages are sent to Sage when an existing customer is edited in Vision Commerce in the ‘Customer Maintenance’ window.  This posting updates Sage with the updated customer information.

Message

                A/C, Name, AddL1...etc

Supplier Maintenance

Create

Create messages are sent to Sage when a new supplier is created in Vision Commerce in the ‘Supplier Maintenance’ window.  This posting updates Sage with the new supplier information.

The first time a supplier is set up in Vision Commerce, a posting will be made to Sage as a ‘Supplier CREATE’ message.  It is therefore important that all suppliers are first set up in Vision Commerce, for Sage to be automatically updated.

Edit

Edit messages are sent to Sage when an existing supplier is edited in Vision Commerce in the ‘Supplier Maintenance’ window.  This posting updates Sage with the updated supplier information.

Message

                A/C, Name, AddL1,...etc

System Data

Currency Maintenance

Create

New Currencies must be set up separately in Vision Commerce (by System Administrator) and Sage (by Sage user).  This is because specific codes must be used in the Vision Commerce database for Sage to recognise and correctly process the postings made from Vision.

Edit

Edit messages are sent to Sage when an existing currency is edited in Vision Commerce in the ‘Currency Maintenance’ window.  This posting updates Sage with the updated currency information.

Message

                EU Member, Exchange Rate, Name, Symbol.

Tax Code Maintenance

Create

A predefined list of Tax codes are already set up in the system to use.

Edit

Edit messages are sent to Sage when an existing tax code is edited in Vision Commerce in the ‘Tax Code Maintenance’ window.  This posting updates Sage with the updated tax code information.

Message

                Rate, Description.

Invoicing

Sales

Stock Sales Order

SI            Sales Invoices

SC           Sales Credits

Sales Invoice & Sales Credit postings are generated from the ‘Invoice Sales Order’ window in Vision Commerce which is available under the ‘Sales Orders’ menu.

Invoices / Credit Notes are selected in this window, when either the ‘Invoice Selected’ or ‘Invoice All’ buttons are clicked; postings to Sage are generated.

The invoices / credit notes will be available to view in the Customer Activity & Financials almost immediately*.

Purchases

PI            Purchase Invoices

PC           Purchase Credits

Purchase Invoice & Purchase Credit Note postings are generated from the ‘Purchase Order’ window in Vision Commerce. 

When any order lines are invoiced/credited under the ‘Invoicing’ or ‘Credit Notes’ tab and the save button is clicked, a ‘P.O.P Vat Analysis’ window is opened.  The purchase invoice/credit note information is then entered by the user, and the ‘Process’ button is clicked.  It is at this point that the posting to Sage is generated.

...

Price Variance Postings

Overview

Purchase Orders are input on to the system with different products, and product costs.  Sometimes the cost specified on the order, is actually different to the value invoiced by the Supplier. 

In this instance, in the ‘Purchase Order’ window under the ‘Invoicing’ tab, the ‘Inv Value’ entered by the user would be different to the original expected cost input under the ‘Purchase Order Details’ tab.

Please see section above which explains when a Purchase Order Invoice is posted to Sage which is also when a PO Price Variance posting is sent to Sage.

Purchase Order Price Variance

Please see the table below for the debit/credit details posted to Sage for this posting type.

Posting Type

JD (Journal Debit)

JC (Journal Credit)

1.  PRODUCT COST (VARIANCE)

 

 

  Purchase Invoice (Invoice Value > Order Value)

GRN Price Variance

Goods Received (GRN) Accrual

  Purchase Invoice (Invoice Value < Order Value)

Goods Received (GRN) Accrual

GRN Price Variance

 

 

 

 EP Sales Order Cost of Sales Accruals & Variance Postings

When an EP Sales Order is created, and an EP Invoice is raised, the same procedure applies as for a normal Stock Sales Order Invoice.  However the next time a Stock Movement Posting is made, an accrual is also made as follows:

Posting Type

JD (Journal Debit)

JC (Journal Credit)

1.  PRODUCT COST

 

 

  EP Sales Order Invoice

Cost of Sales

EP Cost of Sales Accruals

 

 

 

When the EP Purchase Order is receipted and the Purchase Invoice raised, stock is allowed to be allocated against the EP Sales Orders.  When these EP Sales Orders are confirmed delivered, if the product cost is more/less than accrued then a price variance is posted to Sage to compensate for this.

Posting Type

JD (Journal Debit)

JC (Journal Credit)

1.  PRODUCT COST (VARIANCE)

 

 

  EP Sales Order Despatch (Product Cost > Accrual)

Cost of Sales

EP Cost of Sales Accruals

  EP Sales Order Despatch (Product Cost < Accrual)

EP Cost of Sales Accruals

Cost of Sales

 

 

Â