software Archives - Page 3 of 4 - SQLWorks

Did you know? SQLWorks Cloud Link

SQLWorks includes a useful ‘drag and drop’ facility for saving documents against projects, sales leads, accounting records and more.

If your organisation stores files in a cloud storage app, SQLWorks can be integrated directly to view these folders in your ‘Documents’ tab, and files can be dragged and dropped into SQLWorks directly from the cloud.

This option can be set up from the main Navigation bar via Preferences > User Preferences > (User) > and by clicking the Setup Tab. By saving the file-path of your cloud app’s desktop folder into the ‘Remote/ Cloud Folder Path’ field, and clicking ‘Save & Close’, a SQLWorks user’s document tree will automatically default to view the chosen file location.

sqlworks cloud link filepath

As long as your cloud app on your PC/Mac is able to sync to the cloud, SQLWorks will be able to make most up-to-date version of your synced files available for drag and drop.

document management

This can be a useful way to make documents collected during fieldwork (eg: photographs) available to a main office – syncing direct from a smartphone, via your cloud app of choice, to be dragged and dropped against projects in SQLWorks.

Options include Microsoft OneDrive, Google Drive, Apple iCloud and Dropbox, as well as many other cloud file storage applications with a read/write access ‘desktop folder’ style client. (If you’re using a lesser-known cloud storage service with SQLWorks cloud link – we’d like to hear about it!)

This tool can also be used with a valid filepath to a location on a traditional on-premise server, and may be useful for businesses with very complex file structures, to help users automatically find the file location they would normally use for managing documents.

SQLWorks cloud link helps leverage all the flexibility of your favourite cloud app, to gather important files into your CRM, accounting and stock control system.

For additional support and assistance, please contact our SQLWorks team today.

Fact Sheet: Accounting Locks

SQLWorks includes a range of accounting locks which allow data entry for business accounting to be restricted to certain time periods.

SQLWorks operates date based-accounting rather than ‘Period-based accounting’ in the commonly understood sense – this gives companies greater granularity over how accounting is controlled.

Because of this, SQLWorks accounting can be locked down* based on a number of different periods and conditions, depending on your preference:

  • Financial Year Level Locking
  • Monthly Locking
  • VAT Period /  Quarterly Locking
  • Appropriation Locking

 

Financial Year Level Lock

Year Level Locking is available from Audit > Audit by Year in the main SQLWorks Navbar, by right-clicking on the financial year and selecting ‘Lock Year’.

year locking

Financial years that have been locked will display a ‘Yes’ in the ‘Lock’ column of the financial years list, and will prevent SQLWorks users from making any changes to financial transactions within that year. However, nominal journals may still be posted to a locked year.

This lock should only be used by your SQLWorks Accounting Admin, and acts independently of all other accounting conditions.

 

Monthly Lock (Current Financial Year Only)

This lock can be made available in your Accounts Prefs, where individual months, or months within specific ledgers, can be locked or unlocked for current financial year.

month locking

By default, users can only post in the designated active financial year – however transitionary options are available here to allow temporary posting into the final period of the previous financial year if this is still Year Level unlocked.

Because this lock can be turned on/off by a user with sufficient privileges and are always reversible, this forms a ’soft’ lock accounting managers can deploy as a highly flexible ‘Month-end’ control or similar.

 

VAT Locking (Quarterly Lock)

The SQLWorks VAT Ledger allows users to calculate the UK tax return due for each VAT Quarter.

vat locking

Once the VAT return has been complete, the date period covered by the specified VAT Quarter will be automatically locked against further accounting entries.

Reporting VAT accurately is a legal obligation, and additional transaction entries will not be permitted into the locked Quarter once VAT has been calculated for reporting to HMRC. Journaling between nominal codes is still permitted.

 

Appropriation Locking

Once you have set retained profit for a financial year (‘appropriated’ profit) the financial year will be locked, even if the financial year has not yet been Month, VAT or Year Level locked yet. No further transactions may be created in this year.

Because of this, Appropriation is usually only completed once year-end processing for that financial year has already been completed. For more information, please read: “1.1.2.4 – How to Set Retained Profit.

 

*Under certain circumstances some accounting locks can be reversed – please speak to your SQLWorks team about this in more detail.

SQLWorks V8 – your thoughts?

With SQLWorks Version 8 debuting later this year, we’re gathering feedback on what our clients would like to see after the upcoming major upgrade.

Version 8 will be our opportunity to make considerable improvements to both the technical capabilities and user experience of SQLWorks.

Our team’s development priorities have been shaped by the feedback our users have given us in recent weeks and months – please let us know your thoughts below:

Did you know? Importing Journals

SQLWorks Accounting includes the option to enter Journals both manually, but also offers the chance to save time by importing journals from a spreadsheet of data directly to your Nominal Ledger.

When in the Nominal Ledger click ‘Journal’ in the top toolbar, and the add Journals window opens. To begin importing your journals, click the ‘Import Journal Option, and browse for the file you wish to import.

Imports must be imported using a fixed format from a template file: a copy of which can be found within your SQLWorks installation ‘Misc’ Folder as a Microsoft Excel spreadsheet – or downloaded here. You will need to enter your data and save the file as a tab-delimited text (.txt) file before importing.

SQLWorks will warn you if the data you are seeking to import is old, and may block you from entering nominal journals into locked accounting periods.

Once importing journals has run successfully, your nominal journal data will appear in the list of journals to be added, and users can commit them to the Nominal Ledger by clicking ‘Save and Close’.

 

For accounting advice and support, contact the SQLWorks team today.

Fact Sheet: Security Permissions

SQLWorks includes two levels of security permissions: Group and User security.

  1. User security states which parts of SQLWorks a user has access to (visible within menus) and does not have access to.
  2. Group Security sets permissions for groups of users, including every user in that group and overrides an individual’s security settings.

To review your SQLWorks users, click the ‘System Administration’ button on the main navbar. If you wish to review your users, click ‘Users.’ This displays a table with every valid SQLWorks user at your company, and administrators can double click to view or edit an individual’s user settings.

To review your SQLWorks groups, click ‘Groups.’ This displays a table with your saved Groups of users. You can also add a new group, copy or edit any existing group from this table.

To change your security settings, click ‘Security’ (1). This loads your list of groups in the left hand list, with the users contained within any selected group in the right hand list. By clicking the ‘Add’ or ‘Remove’ buttons you can add or remove individual users to the correct group.

By using the ‘Group Windows Security’ Tab along the top, you can also set the permissions for that group (and therefore the users contained within it.) Grant access by clicking the checkboxes next to each area of the system, and  give ‘Basic’ (find, add new or edit) or ‘All’ permissions (find, add new, edit, edit multiple or delete.) (2)

There are no limits on the size or number of groups users can be assigned to, so your permissions structure can be as simple or complex as your internal company policies require. Please ask the SQLWorks team if you need help or advice on setting up security permissions settings, or on IT security best practice.

By default, SQLWorks has one ‘Admin’ group which has administration permissions for the Sales/Purchase Ledgers, Stock Ledger, Finance and CRM sections. This can be changed to different groups in larger organisations – for example to designate a different administrator for sales/purchasing.

Once you have your users and groups configured correctly, simply close the System Administration window, and your SQLWorks security permissions will be in place when each user next logs on.

 

SQLWorks Security Permissions


Bank Ledger – Security permissions for managing Bank accounts and cash accounting

Bank Accounts – Lets users see Bank accounts within the Bank Ledger.

Bank Transactions –  Lets users access options for bank transactions within the Bank Ledger.

Petty Cash Accounts – Lets users access any petty cash accounts.

Sundry Cash Ledger – Lets users access the sundry cash ledger for cash payments.

Sundry Cash List –  Lets users access the global table listing all sundry cash payments.

 

CRM System – Security permissions for ‘SQLWorks CRM’ functions

Actions – Gives access to the Actions Table.

CRM Links – Admin Only. Allows users to link CRM items, for example: attaching a document to a lead.

CRM Prefs – Allows users access to edit system-wide CRM preferences under ‘Preferences.’

Diary Calendar – Allows users access to the diary window.

Diary Entries – Lets users access entries to the diary.

Layers – Lets users edit types of appointment, e.g.: Meeting, Visit etc.

Lead Categories – Lets users use custom checkbox categories to categorise leads.

Lead Sources – Allows users to use the editable dropdown noting where a lead originated from.

Leads – Allows users access to the Leads window.

Phone Logs – Lets users access the phone logs table.

Project Types – Admin only. Lets users access project types.

Projects –  Gives users access to the Project window.

Tasks – Gives users access to the task tables.

 

ISSAccountsPrefs – Security permissions for setting SQLWorks ‘Accounts’ preferences

Accounts Prefs – Financial Management ONLY. Gives users access to system-wide accounting preferences under ‘Preferences.’

Day Book – Gives users access to the day book.

ForX – Gives users access to amend system currencies and foreign exchange rates (multiple currency) accounting.

Message Sets – Gives users access to edit various option lists – eg: ‘why a quote is cancelled’ field answers.

VAT Ledger – Gives users access to the VAT Ledger for calculating VAT submissions to HMRC.

 

Documents – Security permissions for ‘Document Management’ functions

Crystal Reports – Deprecated feature. Lets users import Crystal Reporting.

Document Analysis – Gives users access to edit the custom document type category checkboxes when uploading a new file.

Documents – Gives users access to files uploaded to SQLWorks.

Emails – Gives users access to emails linked into SQLWorks.

Email Browser – Gives users access to the email browser which synchronises to their email account.

Icons – Gives users access to amend the preview icons which load on screen when using Documents within SQLWorks.

Letters – Currently unavailable. Gives users access to SQLWorks letter writing tool.

 

IssPRList – Security permissions for the main ‘Companies’ list and associated data management tools

Address Editor – Gives users access to the full table of recorded addresses.

Client Lists – Allows users access to SQLWorks fixed and dynamic list building tools.

Client Types – Allows users to set custom checkbox categories for categorising companies.

Companies – Allows users access to the Companies List.

Contact Data – Allows users access to the contacts table (listing each company’s recorded contacts.)

 

IssPurchase Ledger – Security permissions for Purchasing

Purchase Accounts – Lets users see their Purchase Accounts with recorded suppliers.

Purchase Ledger – Grants users access to the Purchase Ledger.

Purchase Orders – Gives users access to Purchase Orders.

Purchase Transactions – Gives users access to Purchase Transactions.

Purchase Transaction List – Allows users access to the global table listing all purchase transactions.

 

IssQuotesOrderSales – Security permissions for Sales

Contracts – Lets users access contracts system.

Customer Order –  Allows users access to the Sales Orders panel within the Sales Ledger.

Customer Quote – Allows users access to the Sales Quotes panel within the Sales Ledger.

Directors – Lets users access the recorded list of directors for each company.

Disbursements – Gives users control over sales disbursements (e.g.: expenses, mileage etc.)

Sales Account – Gives users access to each customer’s sales account details.

Sales Account List – Gives users access to their list of customer sales accounts in the Sales Ledger.

Sales Ledger – Allows users to access the Sales Ledger window within Accounts.

Sales Ledger Detail –  Gives users access to unlocked detail lines on Sales Ledger quotes, orders and invoices.

Sales Ledger Transaction – Allows users access to the Sales Transactions panel (Invoices, payments and credit notes) within the Sales Ledger.

Sales Order List – Allows users access to the global table listing all customer sales orders.

Sales Quote List – Allows users access to the global table listing all customer sales quotes.

Sales Runs –  REDUNDANT

Sales Transaction Archives – Allows users access to the global table listing all archives customer sales transactions.

Sales Transaction List – Allows users access to the global table listing all customer sales transactions.

SL Web List – (Top Secret Work in Progress. Shhhh!)

 

IssSQLWorksMain – Security permissions for managing SQLWorks itself

Audit Logs – Gives users access to the ‘audit log’ of users actions within SQLWorks.

Binary Objects –  Controls template images and more. Should be enabled by default.

Database Table Viewer – For Lineal Use Only

DB Sessions – Lets users see logged-in SQLWorks sessions.

Employees – Lets users see the recorded list of company employees.

External Databases – For Lineal Use Only. Allows access to secondary databases if required for external document stores or alternate companies.

Help – Gives users help shortcut to SQLWorks online assistance. Please see www.sqlworks.co.uk/help

Label Prefs – Allows system admin to define system-wide user-defined fields. Should be locked by default.

Refs – Lets users access reference lookup lists and set start points, e.g.: first invoice number.

Server Logs – For Lineal Use Only.

SQLWorks Prefs – Management ONLY. Lets users access system-wide SQLWorks Preferences.

System Monitor – For Lineal Use Only.

User Logs – Lets users access the recorded log of user logins.

User Prefs – Lets users set the user preferences of their own SQLWorks account.

Years – REDUNDANT.

 

Nominal – Security permissions for the Nominal accounting and company finances.

Analysis – Lets users access the accounts ordered by analysis code.

Audit By Code – Lets users audit by nominal code and run nominal reporting.

Audit By Year – Lets users audit by financial year and run nominal reporting.

Budget By Year – Lets users access and compare against recorded financial budgets.

Dashboard – Lets users access the SQLWorks account dashboard.

Departments – Lets users access the accounts ordered by department.

Financial Years – Lets users set system-wide financial year start/end dates.

Nominal Journals – Gives users access to Nominal Journals.

Nominal Ledger – Lets users access the accounts ordered by Nominal Code.

Nominal Audit List – Grants users access to ‘audited’ data calculated from the nominal ledger for financial years.

Nominal Code List – Allows users access to the list of nominal codes defined within the nominal Ledger.

Nominal Journals – Allows users access to Nominal Journals within the Accounts.

Nominal Ledger – Allows users access to the Nominal Ledger (General Ledger) Window within Accounts.

Standing Journal Items – Allows users access to standing journal entry line details for each journal.

Standing Journals –  Allows users access to the Standing Journals window.

Standing Journals Group – Allows users access to standing journal entries.

 

Products – Security permissions for managing Stock

Assets –  Lets users access the ‘Assets’ tab of equipment linked to a company.

Bin Locations – Allows users access to stock ‘bin’ locations within each warehouse.

Dealers – Allows users access to set dealerships, defining both approved suppliers and customers for a stock item, and cross reference the two (eg: for hazardous materials.)

Order Allocation –  Allows users access to SQLWorks stock ‘Order Allocation’ tab in for reserving stock for specific customer orders.

Pricing and Discounting – Allows users permission to set current and future price break rules for stock items.

Stock Allowed –  Gives users access to approvals list, restricting warehouse bins to holding only specific stock items.

Stock Audit – Gives users access to Stock Audit to perform stock takes.

Stock Browser – Allows users access to the stock browser table of all stock items.

Stock Groups – Allows users access to stock groups, to which any stock item can be assigned.

Stock Ledger – Allows users access to the Stock Ledger.

Warehouse Map – Allows users access to the Warehouse Map displaying warehouses, bin locations within these, and stock items within those bins.

 

Fact Sheet: Works Orders

To compliment SQLWorks manufacturing and kitting, Stock Ledger allows users to create and manage manufacturing works orders to different degrees of detail.

(For an introduction to SQLWorks manufacturing and kitting, click here.)

Works Orders are accessible from the Stock Ledger screen, under the ‘Products’ module, in the main NavBar (1), by clicking the ‘Works Orders’ tab for a chosen stock item.

The two tables on the left-hand side show ‘Active Word Orders’ still being worked upon, and ‘Completed Works Orders’ which have been finished (2.)

To the right the ‘Build Quantity’ (3) Panel shows the parts needed for that stock item, how many are available in the default warehouse to use for this works order, and the maximum finished items that can be built from these parts.

The lower right panels (4) show a summary of the scheduled builds on a selected works order, and the parts required for each of these scheduled builds (in case the Works Orders vary between builds.)

 

Quick Build

Users can complete a simple works order by right clicking in the ‘Active Works Orders’ and choosing ‘Quick Build.’ This simplified option checks the correct parts out of stock from their default warehouses, completes a Works Order immediately, and checks in the finished item into stock in its default warehouse.

This is useful for simple builds where no extra works order detail is required and the works order doesn’t need to be drafted in advance.

 

Full Works Order

Users can create a full new works order by right clicking in the ‘Active Works Orders’ and selecting ‘New Works Order’.

This opens a new works order window for the chosen stock item– these can be given header information including a Total Build Quantity. Parts for kitting will be taken from the ‘Take Stock From’ Warehouse code, and (via the designated build bin) the finished item will be checked into the ‘Build Product Where?’ Warehouse code and Bin number.

Each line on the Works Order represents one ‘schedule’ for building a given quantity of the kit – with the quantity of that schedule enterable on the left hand side. A component list is also shown here, to help inform production numbers.

The middle column (‘Cost Groups’) displays advanced Construction Time / Cost Centre additions for this kit if this feature is turned on in SQLWorks.*

The ‘Build Group Column’ is used for the actual building of the works order: typing a quantity into the ‘Take’ field and clicking ‘Take’ removes the required parts from the ‘Take Stock From’ warehouse, and doing the same in the ‘Build’ field and clicking ‘Build’ assembles the new kitted item and moves it to your designated ‘Build Product Where?’ Warehouse and Bin.

You can also cancel quantity’s from the Works Order by typing a quantity into the ‘Cancel Qty’ field.

On the right hand side of each line the ‘Inspection Group’ allows you to enter up to four custom quality testing/inspection checkpoints for each works order schedule, date-stamped for approval.

Works Orders can be saved without being built (to schedule future work), but when the ‘built’ quantity within the works order and any cancelled quantity added together equal the ‘Total Quantity’ required, the works order will automatically be moved to the ‘Completed Works Order’ list.

 

*Construction Time / Cost Centres

Advanced users can turn on ‘Default Construction Costs (per Hour)’ and ‘Default Construction Times (per Hour)’ which will appear at the top of the Works Order Tab if used.

This allows the user to save details for time taken, and costs expended, as the finished kit is processed through up to a maximum of six stages to complete the Works Order, and can be factored into sales costs accordingly.

 

Did you Know? Quoting Tips

quoting tips

Quoting a customer can be a delicate process, and sometimes you need to be able to issue a quote with detailed options. We’ve collated a few handy tips to help your sales team build the perfect SQLWorks quote.

If you’re putting together a more complex quote, it can sometimes be useful to give a customer options. You can create these by right-clicking on the line numbers on the left of each quote line, and selecting ‘Choose Option Group’ to place groups of lines under ‘Option 1’ ‘Option 2’ subheadings (1.)

These options are normally alternatives to each other, so you typically won’t want SQLWorks to total them together. You can remove the overall total by switching to the to ‘Extras and Project’ Tab in the top right of the quote header, and unchecking the ‘Print Totals’ checkbox (2.) This will remove the ‘grand total’ from the bottom of the normal quote template (please note that if you exclude VAT you’ll need to include an amendment to this effect, as depending on your settings, the total VAT may no longer be visible.)

If you need to include sub-total lines instead for each option group, the easiest way is to add a sub-total line at the end of each group. By right clicking on the grey background of any given line, you can choose ‘Toggle Line Type’ to change a line to display the sub-total of the group immediately above it, to be hidden or to become a comment line without any costs (3.)

The area around the line number will change to a different colour to reflect the line type (1), and the quote template will change to incorporate the new line type. This is useful to help keep your quote clear and tidy – to add a running sub-total, line gaps or comments.

With these extras it’s easy to build more complex quotes from SQLWorks, and give customers an informative choice.

A Quick Disclaimer: if you have a custom quotations window for your company/organisation, one or more of these quoting tips features may be disabled. If you need them – speak to the SQLWorks team!

Fact Sheet: Sales Leads

sales leads

Need to manage a sales leads pipeline for your business? SQLWorks CRM includes a comprehensive sales leads module which can help you manage your customer outreach.

Leads can be accessed within the CRM section of the main navbar (1.) and will load a table of leads with multiple coloured panels representing your sales stages (2.)

You can double click on a lead to open it, reorder your leads by clicking the column headers or click the ‘Q1’ ‘Q2’ ‘Q3 ‘Q4’ buttons along the top toolbar to filter by financial quarter.

Once a lead has been opened, you can record common sales qualification data including priority level, log a lead source, assign categorisation and note the contact details of your contact in the top half of the edit Lead window (3.) You can also give each lead speculative value, profit and conversion chance, and set a follow up date for further action which can display in the SQLWorks diary. In the lower panel (4) are your normal SQLWorks CRM tools – you can link phone logs, emails, tasks and drag in documents to be saved against your lead, and save a record of actions performed to progress the lead with a time/date.

By clicking the [+] button above the lead stages you can unlock each new lead stage – moving your lead down the sales pipeline.

As leads move through your pipeline, your brightly coloured lead stages in the main screen (2) display how many leads are active at that stage, what the total value of these are in turnover, and the total likely profit (calculated by multiplying each lead’s percentage by it’s turnover value and adding the sum of that stages leads these together.) You can load the leads active at any single stage by clicking on that stage, and the stages themselves can be set to match your own sales pipeline. ‘Receipted’ and ‘Lost’ sales leads will always default their quantity to 100% of value converted or lost, and will move a lead to ‘Closed.’ By clicking the ‘Load Open’ button in the top toolbar you can filter your list to exclude these closed leads, and just work on those that are active.

If you need a quick way to record new enquiries over the phone, you can create a new lead when making a new phone log by clicking the ‘leads’ tab in the new phone log screen. To save time, the details of your new lead will be automatically populated from those you recorded in the phone log.

Your leads are kept isolated from your main companies list to prevent bigger sales departments with large numbers of cold contacts swamping your SQLWorks Sales Ledger with non-customers.

At any time however, (for example when a Lead becomes a customer) you can click the ‘Conversion Tab’ in the lower half of the edit lead window to automatically save the company details gathered by your Sales agent as a new company in your main SQLWorks companies list.

In this way SQLWorks makes it simple to log new leads, record progress in detail between multiple sales staff, and estimate future conversion rates.

For CRM guidance and help: contact us today.

Team SQLWorks at EurOmnis 2016

EurOmnis

Our SQLWorks team recently exhibited at the 2016 EuroOmnis developers conference in Tuscany, Italy – joining Omnis developers conference from more than a dozen countries around the globe.

EurOmnis is an annual educational event designed to bring Omnis programmers together to share knowledge and to showcase the very latest in software development.

“Lineal have been part of, and latterly helped organise, this international conference of Omnis developers since 1999” explained Managing Director Mike Matthews. “As a member of the Omnis developers group (ODEV), our SQLWorks Business Management Software undergoes an ongoing process of learning and development – and we’re always looking at what features future versions of SQLWorks will need to stay at the forefront.”

“The best businesses are always looking to the latest technology for an extra edge, so both our team and SQLWorks software need to be just as agile.”

EurOmnis

Attendees enjoyed classes, discussions and more surrounding the latest advances in Omnis software development, including javascript web tools, responsive graphs and visualisation aids, and Omnis development for portable devices such as smartphones and tablets.

Representatives from Omnis were also present, to host seminars informing and updating attendees on the platform’s latest news, as well as explore likely developments in the near future and gather feedback.

EurOmnis

The conference also gives developers a chance to showcase what they have been working on to other developers, drawing on software projects undertaken across countless industries and sectors.

To learn more about SQLWorks: contact us today.

Importing your data to SQLWorks

importing –

If you’re new to SQLWorks, importing your existing data to SQLWorks can seem daunting. Fear not! We’ve prepared this handy guide to make this process easier.

Decisions about your data are yours – but at any stage, you can ask the SQLWorks Team for help.

 

About Your Data

Data imported into SQLWorks is categorised in two types: Static and Transactional.

Static data is fixed lists of ‘things’ – including companies, contacts, address, your stock list, warehouses and more. Transactional data includes list of transactions, stock movements and financial ledger entries like orders, invoices, credit notes and more. Static data must be imported first, followed by transactional data.

importing

 

Finding Your Data

Both your static and transactional data comes from whichever system(s) you use currently – this could mean importing from a number of sources, including:

  • An old software program (e.g.: Sage)
  • A patchwork of spreadsheets (e.g.: Microsoft Excel)
  • A legacy database program or file (odbc compatible)
  • Nowhere (because you’re a new or paper-based company)
  • Some combination of the above

It’s up to you what data you place in SQLWorks, however whilst some data is almost always needed SQLWorks (even if entered new), other data is optional. As a rule, names, codes, accounting and VAT entries will need to be imported, but the optional parts of how your business model works (e.g.: records of quotes, or past stock movements) are optional.

 

How To Import:

All data for importing into SQLWorks needs to be given to the SQLWorks team in one of two formats:

  • An agreed file format exported from another software (e.g.: Sage export file)
  • A comma or tab delimited spreadsheet, .CSV or .TXT file. (e.g.: If using Excel, it is helpful to save the files as a .CSV in the ‘save as’ menu)

If you provide data to the SQLWorks team in spreadsheets (or .CSV/.TXT files) these will need column headings grouping certain types of the data together. For example, in a stock list, all your stock codes need to be in the same column, under an identifiable heading such as ‘Stock Code.’ The SQLWorks team can help you with this stage if you get stuck.

Depending on what SQLWorks modules you will be using, you will need to import files for the following data (see table below). Compulsory data within these are marked – for example: every Company imported must have a name.

 

 

SQLWorks Core

CRM

ACCOUNTS

STOCK

Static Companies

  • Name
  • Company Code

 

Contacts

  • Name

 

Addresses

  • Line 1
  Sales Accounts

  • Name
  • Company Code

Purchase Accounts

  • Name
  • Company Code

Nominal Codes

  • Name
  • Nominal Code
 
Transactional    

 

Outstanding Sales Orders

  • Company code

 

Outstanding Purchase Orders

  • Company code

 

Outstanding Sales Invoices

  • Company code
  • Date
  • Amount
  • VAT

 

Outstanding Purchase Invoices

  • Company
  • Date
  • Amount
  • VAT

 

Bank Rec

 

1 Bank Account

  • Name, Acc & Sort Codes

 

1 Petty Cash Account

  • Link to Bank Account
 
Optional Static

 

 

 

 

Sales Leads

 

Projects

  • Project Code

 

 

Nominal Departments

  • Name
  • Department Code

 

Nominal Analysis Codes

  • Name
  • Analysis Code

 

Nominal Subheadings

  • Name

 

Budgets

  • Amount
Warehouses

  • Name
  • Number

 

Stock List

  • Stock Item Name
  • Stock Code
  • Sale Price
  • Purchase Cost
  • Current Stock Quantity

 

Warehouse Bins

  • Number
Optional Transactional

Tasks

 

Phone Logs

 

Actions

 

Emails

 

Historic Sales Quotes

  • Company
  • Date

 

Historic Purchase Quotes

  • Company
  • Date

 

Historic Sales Orders

  • Company
  • Date

 

Historic Purchase Orders

  • Company
  • Date

 

Historic Sales Invoices / Receipts / Credit Notes

  • Company
  • Date
  • Amount
  • VAT

 

Historic Purchase Invoices / Payments / Credit Notes

  • Company
  • Date
  • Amount
  • VAT

 

Purchase Invoices (Historic)

Stock Movements

  • Stock Code
  • Date