Tools & Utilities - Getting started

1What Tools & Utilities does #

Tools & Utilities holds the jobs every module shares and that are not a record of their own: bringing masters in from a spreadsheet and taking them out again, and locking a period once its books are final. A few more tools carry the same /tools address but live on their own module's menu - GST returns and linked transactions.

2Where to find help #

• On every screen: the Help panel on the right, with the steps, the fields, the rules the server enforces and every message the screen can show.
• The manual: at the foot of this page, the full help of Close Transaction Period, Data Import & Export, Manage Linked Transactions and the GST Filing Register.
• The search box in the help finds a message or a word across every screen.

3Where things are - the Tools & Utilities menu #

The same import also opens from the Import button on the Ledger Account master, the Product master and CRM Leads.

4First-day setup (administrator) #

1. A user who is not an administrator also needs the page ticked on their Menu Definition tab, as for every page.
2. Grant Close Transaction Period (Execute) on the Tools & Utilities tab of User Manager to whoever closes periods. Administrators hold it already.
3. Decide who imports. Importing needs Execute on Import/Export Data plus the master's own Create right (and Modify to update, View to export). See Who may do what below - today that means an Administrator.
4. If GST returns should close the month when filed, switch on #241 or #242 in Settings > GST Filing Settings.
5. Agree with your accountant when periods are closed - monthly after the books are final, or after each return is filed.

5Keyboard shortcuts #

Manage Linked Transactions has its own: Set Off (F5), Auto Set-Off (F4), Reserve stock (F3) and Print (Ctrl+P).

6Close Transaction Period #

Closing a period locks a date range. From then on the database refuses to add, edit or delete any voucher (sales, purchase, accounting, inventory, manufacturing), attendance entry, pay bill batch, cash counter opening or closing or cash receipt dated inside it - for the chosen branch, or for all branches - and that includes administrators. Use it once the books are final for a month, a quarter or a filed return.

Step by step

1. Make sure every entry for the period is final. After closing, a correction needs the period reopened first.
2. Pick Period begin and Period end - both days are locked. Both start at today, by the server's date.
3. On the ERP edition, pick the Branch, or All branches where it is offered. Professional has one branch and shows neither the field nor the Branch column.
4. Type a Description so others know why (up to 255 characters).
5. Press Close Period (F5) and OK. The period appears in the list as Closed.

The list

• Every closed period, newest first: when it was closed, by whom, the dates, the branch and the description.
• Closed rows are enforced. Reopened rows (orange) are kept for the record and lock nothing.
• Nothing is ever deleted. A reopened period stays in the list.

Correcting something in a closed period

1. Select the period and press Reopen. Entries dated in it can be made again.
2. Make the correction.
3. Close it again: a new close, or Close Again on the reopened row (an administrator only).

The rules the server enforces

• Period begin must not be after period end, and the whole period must lie inside the company's financial year.
• A user who is not an administrator may close only from today less 2 days up to today - the desktop's rule. An administrator may close any period in the year, including a future one.
• All branches is offered to administrators, and to a user who has only one branch. A single-branch company closes all branches.
• The branch list is your own allocation, as everywhere else.
• A period may not overlap one already closed for the same branch or for all branches. The message names the clash.
• Reopening needs the same right and a branch you may use.
• Every problem is listed at once, numbered, and the server repeats every check.

Closed by GST filing

When GST Filing Settings say so (#241 for GSTR-1, #242 for GSTR-3B), filing the return writes a closed period for that month here itself. It shows in this list like any other and is reopened the same way.

7Data Import & Export #

Starting on the software, or taking over a list from somewhere else, means hundreds of records. This screen reads them from a spreadsheet instead. Every row is checked before anything is saved, and saved through the same rules as the master screen - a lead gets its number and first follow-up, a ledger its account code, a product its prices - so an imported record is exactly what a keyed one would be.

A switched-off record matches too, so a record is never added a second time.

Importing, step by step

1. Pick what to import on the left. A kind you may not use says so.
2. Press Download format (.xlsx) (or .csv). The .xlsx has a Data sheet with the headings and sample rows, and an Instructions sheet saying what every column takes.
3. Fill the Data sheet: delete the sample rows and type or paste yours. Keep row 1 as the headings and Data as the first sheet. Column order does not matter; extra columns are ignored.
4. Under The file, choose your file. Every row is checked at once: New, Already there, or Error, with each problem named.
5. Work in the grid: click a cell to change it, press the cross to remove a row (or Remove rows with errors), filter, sort and group. Press Check again after changes.
6. For rows already there, choose Skip them or Update them for the whole batch, and change the Action of any single row that should differ.
7. Press Import (F5) and confirm with OK (F5). The outcome of every row is listed: added, updated, skipped, or failed with its reason.

Exporting

1. Press Load records to export. The records you may see fill the grid - Export mode.
2. Shape the file in the grid: change cells, remove rows, filter, sort, group. Nothing you do here changes the records.
3. Press Export grid (.xlsx) (F5) or Export grid (.csv). The file takes the rows the grid holds after its filters, in the import format.
4. To correct many records at once, import that file back and choose Update.

The rules

• Nothing is saved until you confirm. Choosing the file only checks it.
• The grid is what is imported. Your edits and removals count; the server checks every row once more before saving.
• Update changes only the cells filled in. A blank cell never clears a value. A ledger's account code is never renumbered.
• Inactive records travel. They are exported with Inactive = Yes; imported back, Update switches a record on or off as the column says, and a blank leaves it.
• Names, not codes. Group, unit, tax class, HSN, brand, lead source, owner, state - write them as the master shows them (capitals do not matter). A misspelt group is reported, not created.
• One record per row. A row repeating an earlier row of the same file is reported.
• A failed row does not stop the others. Each row saves on its own.
• Limits: 20 MB and 10,000 rows per file. Only .xlsx and .csv are read - save an old .xls as .xlsx first.
• Not for voucher lines. Those come in on the voucher itself, with its own Import from Excel.

8InvoiceNET® Studio - design your own pages and reports #

InvoiceNET® Studio makes pages without code. A design is a description - its fields, its grids and their rules - and one ERP page draws it, so a designed page works like the hand-built ones: Find (F2), Add (F3), Modify (F4), Save (F5), every problem listed at once, a hint under every field, the same help panel. Rules are checked while typing and again on the server, so they cannot be walked around.

Before you start

1. InvoiceNET® Studio is a licensed module of its own. It includes one page; every further page is bought (Admin > Subscription and Add-ons). Every page design counts from the moment it is made, draft or published, for all the licence's companies together - InvoiceNET® Studio page shows how many are made of how many allowed. Deleting a design frees its page.
2. Designed reports are counted apart from pages: InvoiceNET® Studio includes one report, and every further report is bought the same way. A report design counts from the moment it is made, draft or published.
3. Make the tables in Masters > Custom Table Designer, each with its key fields. A table of rows that belong to a record (lines, photos) carries a field that holds the record's key.
4. Have Studio Designer in User Manager > InvoiceNET® Studio: Create, Alter and Delete to design, Execute to publish.

A data object

• Main - the table the record lives in; Find, Modify and Save work through its key.
• Child - rows of the record, joined to the main table by a relation; shown as a grid and saved with the record in one transaction.
• Parent - a table the record points to (a customer, an item); read for display and popups, never written.
• Independent - no key link to the record; a grid of its own with its own key, saved on its own unless *Save with the page* is on.
• Key fields for every table the page writes, and how they are filled: by the database (identity), typed by the user, made from other fields, or a line number within the record. Other unique keys, such as a code, are checked too.
• Relations - read from the database's foreign keys where there are any, drawn by hand where there are none; the page then fills the child's field itself.

A page design, step by step

1. On InvoiceNET® Studio page press New page design (F3) and choose the data object.
2. Drag the main table's columns into a section, or double-click one (or press Enter on it) to add it to the selected section - each arrives bound, as the right kind of field, required if the column needs a value.
3. Drag a child or independent table: it arrives as a grid with its columns. A page can have no grid, one grid or several.
4. Click a field to set its rules on the right: validation, starting value, read-only, visible when, computed value, choices or a popup (with the fields it fills and the field it follows), format, and what it sets when it changes.
5. Fix what the check under the canvas lists, press Preview to try it on real records (nothing is saved), then Publish.
6. Give people View, Create, Alter and Delete on the page's row in User Manager > InvoiceNET® Studio. The page is on the menu under Designed Pages.

Voucher pages - your own layout for a voucher type

A voucher page enters real vouchers of one voucher type - a sale, a purchase, a journal - on a layout of your own. It is a separate menu entry under Designed Pages; the standard voucher screen stays as it is. The voucher is saved by the voucher screen's own writer, so its numbering, your rights on the voucher type, the price lock, the date and sundry rules, stock and GST checks all apply.

1. Press New page design (F3), set Kind of page to *Voucher page* and choose the Voucher type. An empty canvas gets the voucher's usual layout at once: the voucher fields, the product lines (or account lines for an accounting voucher), the sundries and the totals.
2. The toolbox lists the type's Voucher fields, its Custom fields (from Voucher Manager) and each grid's own columns - including the spare line columns (Reserved columns) for extra details per line. Drag them where you want; a field the voucher works out (tax, line amount, totals) arrives read-only.
3. To keep details of your own with each voucher, add a data object: its main table holds one row per voucher, keyed by *The voucher's number* (a whole-number column, and a text column for the voucher type); child tables become extra grids. They are saved in the same step as the voucher - all of it or none.
4. Fix what the check lists - it names any field the voucher cannot be saved without - then Preview and Publish, and give View, Create, Alter and Delete on the page's row in User Manager > InvoiceNET® Studio.

• While you type, the server works the voucher out exactly as the voucher screen does: the price from the price list, the discount, tax, the class's automatic sundries and the totals. A rate or discount you type is kept; one the voucher filled follows a change of party or item.
• Find (F2) lists the vouchers of the type; Modify, Delete and Print work on the voucher on screen. A voucher page touches only vouchers of its own type.

Voucher pages - linked from earlier vouchers, and printing

A voucher page links to earlier vouchers exactly as Voucher Manager sets it for the voucher type (Enable Linked Transaction and its properties) - a delivery note from sales orders, a purchase from purchase orders. The strip above the page says what the voucher is Linked from and what the voucher type allows. Linked Transactions must be on the licence.

1. Choose the party (or, where the voucher type picks its sources first, go straight on), then press Load from linked (F7). The earlier vouchers still waiting are listed as cards - tick one, or several where the voucher type allows; Not applicable is offered where the link is optional (a compulsory link needs a real source, as on the desktop).
2. Press Load (F5): their pending lines replace the grid's lines, with the pending quantity and the source's rate. Deliver less by lowering the quantity; the voucher type's rules on the quantity and the rate are checked again on Save.
3. Save (F5) stores the link, so the earlier voucher is used up as on the voucher screen - a sales order delivered in full no longer appears. Take the link off keeps the lines but stops them using up the earlier vouchers.
4. When the party's credit check stops the save and the party's credit Mode is *Approval*, the page offers Request approval (F5): the request goes to the Credit Approvals desk, and once it is granted Save (F5) goes through.

• Print (Ctrl+P) prints the saved voucher the voucher screen's way: the formats set up for the voucher type and their groups, System Print, and the page's own layout. A format remembered on this computer prints straight away - Silent to a printer through the InvoiceNET Print Agent, or Preview.
• Print options (Ctrl+Shift+P) always opens the dialog: Printer, Copies and Remember, then Print (F5), Preview, Download, Share (F6) to WhatsApp, e-mail or any app, Cancel (Esc). Voucher Manager's Print Voucher On Save prints after Save the same way.
• Printing needs the page's Print right and the voucher type's Print (Re-print once printed) and Find or View rights; a voucher status may forbid it.

Link rules - one page loads rows from another

A link rule lets a grid of a designed page load rows from another published page - an order's lines into a delivery, an advance into a bill - under conditions you set. What each row takes is counted, so a source is never taken beyond what it holds: the picker shows what is still pending, and Save checks it again.

1. In the designer press Links (beside Events) and Add a link rule: a title (the button says *Load from <title>*), the page it loads from and its grid (or *the records themselves*), and this page's grid the rows land in.
2. Choose How it takes: row by row with each row's quantity pending, a whole record once, always (no pending), or by value - an amount pending (setting 327).
3. Map the columns (Suggest by name pairs those with the same name) and name the quantity, rate and amount columns on both sides.
4. Set how much a row may take - can reduce, can increase, fixed; a tolerance in % above pending (setting 326); a minimum per row; the rate kept as on the source; not above the source's amount - and whether rows come only from sources and whether a source is compulsory.
5. Set which sources are offered: matches (the same party, project...), approved sources only, the branch, a source dated on or before this record, an age limit, one source or several, and any condition of your own in the condition builder. Header fields can be copied from the first source.
6. Save draft, then Publish - Publish checks each rule against its source page as published.

• On the page: in Add (F3) or Modify (F4) press Load from <title> (F7 for the first rule). The records that meet the conditions are listed as cards with what is pending; tick a record for all its rows, or tick rows and change Take to take less now; Load (F5) puts them in the grid with a link mark - point at it to see where the row came from and what is still pending there.
• Save (F5) checks the conditions and the pending again - with the source lines locked, so two people cannot take the same last units. Deleting the record gives back what it took.
• A record other records loaded from is protected: its rows cannot go below what they took nor be removed, and it cannot be deleted while they hold it.
• A record whose approval was rejected keeps holding what it took until it is changed or deleted (setting 328, on by default).
• A voucher page can have link rules too: designed records - approved requests, job cards, orders taken on a designed page - load into the voucher's product lines by quantity, and Save holds them in the same transaction as the voucher. What a voucher holds follows its line: changing the voucher on the voucher screen, or cancelling it, gives the rest back.
• On a designed page, the action Create a voucher from this record (on a button, or after saving) opens the chosen voucher page ready to add, with this saved record loaded through that page's link rule - the party (whatever the rule matches on) taken from the record. Publish checks that the voucher page really has that rule loading from this page.
• With Voucher screen loads from designed records on (Linked Transactions > Linked Transactions Settings, setting 325 - off by default) the ERP voucher screen of that voucher type shows the same rules as Load from ... buttons beside Item List: the cards, the Take boxes and the checks at Save are the same, and the lines are priced and taxed as any added line. A voucher that holds designed records is checked on every save, even after the setting is switched off.

Reports - your own report in the report viewer

A designed report reads the company's data and shows it in the ordinary report viewer, so it prints, exports to Excel, CSV, HTML and PDF, e-mails, schedules, saves presets and has the analysis, pivot and chart views like every standard report. The ERP writes and runs the query from the design, so a report can never change data.

1. On InvoiceNET® Studio page press New report design, give it a code and a title.
2. Data: choose the table or view it reads - or Start from a data object to take its tables and relations. Join another table brings more columns in; say which column of it equals a column of a table above (a party's name beside its voucher).
3. Columns: click a field to add it, or Add a worked-out column such as {L.Qty} * {L.Rate}. Give each its heading, its Total (Auto adds up money), decimals or date format, alignment, and tick Hidden for a value only a colour rule or a drill needs.
4. Options: what users fill in before it runs. Date range adds From and To on the first date column; Branch offers only the branches the user may use; a pick-list takes its choices from a column, an ERP list or a fixed list. Each option names the column it narrows - or the filter reads it as {Option.Key}. A blank option never narrows.
5. Filter & order: a fixed condition such as {M.Status} <> 'Cancelled', up to three group levels with a subtotal each, the sort, the grand total and the most rows one run may read.
6. Colours: a rule colours a whole row or one figure when its condition holds - {Balance} < 0 in red, {Due} < TODAY() in amber. The colour says what it means; print and the exports keep it.
7. Drill & chart: a row can open its voucher (its type and SEQ among the columns) or another report filled in from the row; choose what the chart view opens on.
8. Preview (F8) runs the draft on real data, up to 200 rows, with the options as users will see them. Publish puts it on the menu under Designed Pages > Reports and in the report launcher.
9. Give people the rights on the report's own row in User Manager > Permissions > InvoiceNET® Studio: View runs it, Print prints it, Export exports and e-mails it.

Designing the printout

1. In the designer press Print layout above the canvas. The sheet shows the layout the page suggests - each section as fields, each grid as a table with its totals, signature lines at the end - filled with made-up values.
2. Drag Fields, Grid, Text, Signatures or Line onto the sheet, or double-click one to add it after the selected block. Drag a block to move it; the arrows in its properties do the same.
3. Click a block to set what it prints: which fields (1 to 4 side by side, a box, leave out empty ones), which grid columns (totals row, row numbers), the text (with {Field}s such as {Customer}), the signature captions, *Printed when* and *Starts a new page*.
4. Click the empty part of the sheet for the paper (A4, A5, Letter, Legal), portrait or landscape, the margin, the text size, the heading, and the company band - name, address and contact, and the System Print logo.
5. Print a sample prints the made-up sheet. Save the draft and publish: the page prints the new layout from then on.

In a designed page

• Every field is edited in place; Tab and Enter move to the next field in the order the designer set, skipping read-only ones.
• In a grid, Enter on the last editable column of the last row adds a row; a grid always ends with a ready blank row that is never saved.
• Drop-downs and popups load once and follow the fields they depend on (Branch to Godown) in the browser.
• A popup over a master - ledgers, items, units, warehouses, employees, bill sundries, transaction classes or a custom table - has + Create new ... at its foot (in a grid cell too - a cell's popup is the same list: type to narrow it, pick with Enter): it opens that master ready to add, and the new entry is put in the field once saved. Not in Preview - nothing is written there.
• A grid ends with a totals row: number and money columns are summed, and the designer can make a column count its rows, average, show its smallest or largest value, or work out its own total - for example the item total plus or minus each sundry: `SUM({Items.Amount}) + SUM({Sundry}, IF({Sign} = '-', -{Amount}, {Amount}))`. The empty ready row never counts.
• Print (Ctrl+P) prints the saved record on screen on the sheet the designer laid out (right: Print on the page's row). Save first - a record being typed is not printed.
• A grid is a Syncfusion grid. A column's Column look sets its width in pixels, the heading's alignment and tooltip, Hidden, Frozen, Skip on Tab / Enter, bold, italic, underline, font size, the text and background colours of the cells and the heading, the Focused text and background (default none), how a long value ends, resizing, and Highlight when - a condition on the row that colours the cell. The grid's Grid look sets its lines, alternate rows, hover shade, row height, resizing, text wrap, row numbers, heading colours, font size, the row the cursor is in, and the totals row's colours.
• A printed grid follows the columns' look when its print block says Use the columns' look, with Print colours and Print highlights to turn the colours off, and Lines: All, Rows or None.

Buttons and automatic steps

• Press Events in the designer to choose what runs when a record is shown, before saving and after saving. A Button on the canvas runs its own list when pressed.
• The actions: set fields, show a message, stop with a message, ask to confirm, fill fields from a lookup, open another designed page (with values passed in) or a report, refresh a grid, send an e-mail, request approval, and create a voucher (or another page) from this record. Each can have an Only when condition.
• A stop before saving is checked again by the server. The e-mail and the approval run on the server on the record as saved - a button sends them only once the record is saved.
• E-mail goes out through Settings > Mail Accounts and is logged in Administration > Notification Log; {Field} in the subject or message shows a field's value.

Approval of designed pages

1. Add a Request approval action after saving (with a condition such as {Amount} >= 100000) or on a button, and name the levels in order - each level's approvers are users or user groups.
2. Saving (or the button) sends the record to level 1. It shows in their Approvals inbox and bell, and they are e-mailed. The link opens the record with Approve and Reject.
3. Each level is decided by any one of its approvers; approving passes it to the next level, a rejection (with a reason) ends it. The person who asked never decides.
4. While it waits, nobody can change or delete the record. A change to an approved or rejected record sends it for approval again. An optional read-only field shows Pending, Approved or Rejected.
5. Approvers open the link when the page is on their menu (Menu Definition) and they hold its View right. Switch on Approval links open the record for its approvers in Settings > Approval Alert Settings to let the link open just that record for the approvers of the level waiting.

Custom Fields panels

• A Custom Fields panel is a design of the kind *Custom Fields panel*: it opens from a master (Ledger, Product, Employee) or from a saved voucher of one voucher type, instead of the plain entry grid.
• Its data object's main table keeps one row per host record, in a whole-number column you choose (Host's key kept in) - the screen writes it, nobody types it.
• On the master, Custom Fields opens the panel (pick it when there are several). On a voucher, the panel's own button appears on the action rail once the voucher is saved; the panel saves on its own.
• A published panel counts against InvoiceNET® Studio's page allowance, like a page.

Moving designs to another company

1. On InvoiceNET® Studio page press Export designs, tick the published pages and reports to take, and press Export (F5). A .json file is saved: the published versions, their data objects and the structure of their custom tables - never a record.
2. In the other company press Import designs and choose the file. Check lists every table, column, data object and design it would make or change; nothing is written yet.
3. Press Import (F5). Missing custom tables and columns are made (a column already there is never changed), each design is published and put on the Designed Pages menu. A design or data object already there stops the import unless Replace is on - replacing makes a new version, the old ones stay under Versions.
4. New designs count against that company's licence, pages and reports apart. Give people the View right on each in User Manager (InvoiceNET® Studio tab).

Designs inside a custom module

• C-Land can make a page or report part of a custom module made for you. It then arrives in each company the module is assigned to, on the module's own menu section, and runs under the module - InvoiceNET® Studio licence is not needed for it. It still counts against InvoiceNET® Studio allowance when there is one.
• Such a design shows From CUS_... on its card and is read-only here: it is changed in the company it was made in and arrives again when the module is applied. It cannot be exported or replaced by an import.
• When the module is taken off the company, its designs are switched off - the records they kept are untouched, and assigning the module again switches them back on.

SQL sources approved by C-Land

A view or a function written in SQL can list what a popup offers, or be a data object's look-up (Parent) table. Pages only read it. C-Land approves every one in Licence Admin, and it is then created in every company of your serial.

1. Press Check: the rules are run (it only reads, one statement, no other database, no system tables) and SQL Server lists its columns. Nothing is created.
2. Save draft keeps it against your serial in Licence Admin; Send for approval asks C-Land. C-Land can also write one for you there.
3. Once approved it shows as In use. A rejected one shows C-Land's note - open it, change it and send it again.
4. In the designer, choose sql:CODE as a popup's Data source, or add it in a data object as a Parent table. For a function, say what fills each parameter: a field of the page, or today, the user, the branch, the financial year, the company code, the report option, the reporting period, the company code, the report option or the reporting period.
5. In a report, pick it among the tables - it is listed under its title, marked approved by C-Land. For a function, choose under Parameters what fills each one: an option of the report (add the option first) or a context value. It can be joined with the company's tables like any other.

Deleting a design or a data object

1. Press Delete on the design or the data object. A delete cannot be undone, so it needs a code.
2. Press Send code. Six digits go to the licence's registered e-mail - never an address typed on the screen.
3. Enter the code and press Delete (F5). It is good for 30 minutes and works once; five wrong tries end it, then send a new one.
4. A deleted design takes its versions, its menu entry and the rights people were given on it (User Manager, InvoiceNET® Studio tab) with it. The records it saved stay in their tables.

9Who may do what #

Administrators hold every right through the permission function. The screens ask it, and the server asks it again for every request, so a right cannot be walked around.

10Tools that live with their module #

GST Returns and the GST Filing Register

GST Returns prepares a return for a GSTIN and month, sends it through the approval levels set in Settings > GST Filing Settings, and records the ARN when it is filed. The GST Filing Register has one row per return per GSTIN per month, from the first submit on, with its status - Draft, In approval (at level of levels), Returned, Rejected, Approved (ready to file) or Filed - and the tax as submitted. Double-click a row, or pick it and press Open return, to open it in GST Returns. Only returns of your report option's GSTIN are listed. Both are on the Financial Accounting menu.

Manage Linked Transactions

Every voucher a later voucher can still pull from - an order, an indent, an inward supply - listed once for each voucher type it can be set off into. Set the filters and press Apply; nothing is read before that.

• Set Off (F5) opens the target voucher type with the ticked sources loaded; save it there.
• Auto Set-Off (F4) creates the vouchers for you, one per party, after a preview.
• Close voucher... gives up everything still pending on a voucher; Short-close... gives up the lines you pick. Both need a reason from Short-Close Reasons. Nothing already delivered changes - bills, stock and the ledger are untouched.
• Reopen ticked... under Show: Closed puts a balance back; the close stays in the log.
• Reserve stock (F3), Change status..., item-wise pending, history and price comparison act on the picked row.

It needs the Linked Transactions module and Execute on Manage Linked Transactions. The Linked Transactions guide covers it in full.

Inbox & Outbox

The mail outbox that used to sit here is now Communications > Inbox & Outbox, the Communication Hub. Messages the software sent, and why one failed or was skipped, are also in Admin > Notification Log.

11Moving from the desktop #

• Close Transaction Period writes the same closed-period table the desktop uses, and the same database triggers enforce it, so a period closed on either side locks both. The two-days-back rule for ordinary users is the desktop's.
• Import needs the same Tools right as the desktop's import, Import/Export Data.
• Manage Linked Transactions shows closes made here or on the desktop. The desktop's custom list query setting does not apply on the web.

12Common messages and what to do #

This is the short list. Each screen's Help panel lists every message it can show.