Skip to main content

New DN

The form Create Sales DN opens via the path Sales > DN > Create Sales DN or by using the button New found in the Sales DN Search form.

How to create a Sales DN​

1. Mandatory Data​

To continue creating the Sales DN, the user must enter the required fields:

  • Delivery note type: default set in Configuration > Tables > Sales > DN Types.
  • Number: each document is assigned a number according to the numbering specified by the user and the type of document that contains the numbering. The numbering associated with the DN type generally includes an automatic progression based on date and number, with a retrieval function that covers any gaps in the sequence (for example, caused by the deletion of documents). This behavior is regulated by two specific flags in the numbering table. If the user wishes to manually enter the number, they can disable the date-number progression flag (which ensures the increment of numbering on future dates) and the number retrieval flag. Furthermore, they will need to enable the external numbering flag, indicating to the system that the numbering will be managed manually.
  • Client: can be typed using the field help, typing it directly, or using the automatic procedure if they choose to create documents via the DN Fulfillment from Customer Order. Upon entering the customer, the following fields, if present in the registry, will be automatically populated, which we will explain in the following sections: currency, country, language, region, shipping, price list, any discounts, payments, fees, agents, destination, carriers, extra data.
  • Date: indicates the creation date of the DN. This date is crucial for calculating deadlines and any payment conditions. The current date is proposed, which can be modified; if the numbering requires a progression of date and number, and a past date is entered, Fluentis will check the availability of numbers on that date to ensure progression, and if not present, will notify the user that there are no available numbers on that date.

The form contains a series of tabs.

After selecting the mandatory data in the upper section, the user can continue entering the following data manually or with the field help; alternatively, depending on the procedures chosen, the application automatically fills in the fields.

Remember

If the document is created automatically, these data will be retrieved from the origin document from which it was generated.

Entering the Customer, all specific data of the Header tab are automatically proposed according to the data previously set in the customer registry, in the fields corresponding to their address and in the sections:

Other header fields​

  • Printed: activated when the document is printed, indicating that the document has been printed; this flag is also important for allowing the fulfillment of the DN in other documents.
  • Unloaded: this flag is automatically activated when the document is moved to the warehouse, either with the Automatic unload button on the toolbar or with the available procedures.
  • Valorized: this flag is activated when the DN is valued in the invoice.
  • Partial Valorized: this flag indicates that the DN has been partially valued in the invoice.
  • Forced Valorized: this flag is activated if the DN has been forcefully closed with the forced fulfillment of the items; for example, when the remainder will not be delivered and the document is considered closed even if it would not be.
  • Cancelled: the active flag allows the order to be canceled.
note

Flags can be removed with the operation recovery procedures.

  • Unique Project Code/Identifying Code for Bid: if in the fiscal information of the customer registry it is enabled for management of CIG and CUP, it will be possible to fill in these details in the document.
  • Customer note: this field is retrieved from the order that created the DN, but can also be entered manually.
  • Our Reference/Your Reference: in these fields usually an internal reference and a customer reference for the document is indicated; if the DN is generated through an automatic creation procedure, these fields will be populated with the indications present in the origin document (this transfer is valid only for DN created by retrieving data from a single origin document).
  • Reference to Customer Order Number: this field automatically inserts the order from which the DN originates.
  • Reference to Customer Order Date: this field automatically inserts the date of the order from which the DN originates; together with the previous field, it creates the data necessary for tag 2.1.2 of the electronic invoice xml file when it is created; if not filled, the Your Reference field will be taken instead.
  • D.N. initial note: you can select the notes that have been previously entered in the homonymous table found in the path Configuration > Utilities > Management of Coded Notes; for this, the user must double-click the field to open the Help and select the data; otherwise, they can enter them manually.
  • Project: it is possible to associate a project with the document.
  • User: allows you to enter the user creating the document. Employees were previously entered in the Home > Employees table; this data becomes mandatory if the option is set in the Document Parameters.
  • Execution status: when the order is fulfilled through DN or invoices, its fulfillment status changes automatically from Not executed to Partially executed or Closed; the user can force the fulfillment of an order not fully fulfilled, and when this happens, the fulfillment date is also saved.
  • Apply from is the date for calculating payment deadlines.
  • Audit Trail: as in all documents, this section shows the document creation date with the operator, and the last modification date of the document with the operator.

Specific buttons​

Fulfillment from Orders (see the relevant documentation).
Automatic Shipment (see the relevant documentation)
Help recipients/destinations: this button opens Help to select the recipient/destination for the document, among those available for the customer and thus coded in their registry.
Insert AgentAccount in the Items rows: this button opens a pop-up in which to insert an agent registry, which will be spread across all item lines, optionally adding to already present Agents.
Replace CIG/CUP in Lines: after specifying CIG and/or CUP in the header, it is possible to replace these data in bulk in the already entered item lines.
Cancel: deletes the selected discounts in the Discounts tab of the Header.

In the header, there are also some tabs that we analyze below.

2.1 Payments​

The Payment Terms are automatically reported from the origin document or from the Customer Registry > Payments tab and can be modified/deleted by the user.
If the Payment type is associated with a financial discount, the amount of the discount is only considered for accounting purposes, that is, in the deadlines of the document and not in the total order.

Specific button*​

Delete Payments: used to delete the selected payment lines.

2.2 Discounts​

Only the pre-defined discounts taken from the Customer Registry > Discounts tab (Anagrafica cliente > tab Sconti) are proposed and can be modified/deleted by the user.

The discounts proposed in the header of the document are reflected in each new item line inserted in the document.
If a new discount is entered in the header after entering the item lines, it will not be replicated in the item lines already inserted.

Specific button:

Delete discounts: used to delete the selected discount lines.

2.3 Agents​

Indicates the agent code and their commission for each item line. The code and percentage defined in the Customer Registry > Agents tab (Anagrafica cliente > tab Agenti) are proposed. If the commission is not linked to the customer in their registry, the agent must still be entered but with a NULL commission because if it were with a 0 commission, it would mean that the agent is linked to the agent but receives no commission. The same section will be proposed for each item line in the corresponding Agents tab.

Specific button*​

Delete agents: allows the deletion of selected agents.

2.4 Extra Data​

Here is proposed the information entered in the Subject Registry > Extra data tab, only if default data exists.

Header Procedures:​

Fulfillment from Order​

In the header of the DN, pressing the Fulfillment from Order button will open the form where it is possible to filter the confirmed orders of the document's customer and transfer them into the DN. It is also possible to perform the DN creation operation from the Order Search.

Through this procedure, a sales DN can be created from the fulfillment of the related customer order. It is thus possible to enter items within the DN, fulfilling either the entire order or specific lines, either fully or partially.

For this procedure to be usable, there are initial conditions that must be met:

  • The customer of the orders must be the same as the DN;
  • The order you wish to fulfill must have the Printed flag and the Order confirmation date set;
  • In the DN Types table, the flag on Order (indicating that the DN can derive from an order) must be present.
  • Only if the procedure is executed from the Order Search, the document types must be compatible: in the Order Types table, the order type you wish to fulfill must have the corresponding DN type set.

You must then set in the header of the new DN, the Delivery note type you wish to create (which must correspond to what is set in the order types table) and the Client. Once these data are entered, you need to click on the Orders Processing button to open the fulfillment form.

Procedure:​

The filters for customer and currency will be automatically populated based on the customer selected in the DN.

Once all desired Filters are set, clicking the Search button will display a line in the grid for each printed, confirmed, and unfulfilled or partially fulfilled order.

Note

The procedure retrieves all data present in the order, and consequently, the purchasing conditions present in the order will be applied, even if they have currently changed.

Note

Lines of type Note will always be visible, even if already fulfilled, until all lines of other types have been fulfilled.

In the results grid, the user then has the option to:

  1. select the entire order. To do this, simply select the flag present at the beginning of the order line.
  2. select only some of the Items proposed. To do this, simply select the flag present at the beginning of the item line.
  3. select only some items for a specific quantity. In this case, they must modify the quantity to be fulfilled.

To complete the procedure, the user must then click the Transfer button, which will retrieve all data present in the order and bring it back into the DN.

Specific buttons​

Search allows searching supplier orders.
Transfer allows transferring the data of the selected order into the new DN.
Forced Oreder Execution allows for the forced fulfillment of the order; if some lines of the order are selected, only the selected lines will be forcefully fulfilled (with the addition of the flag Forcefully Fulfilled corresponding to the item line); if the entire order is fulfilled, its status will also change in the header.
Orders Processing allows the fulfillment of the order.
Expand allows expanding the entire tree of orders in the underlying grid, to view the items contained within them.
Collapse allows collapsing the display of item lines, showing only the order lines.
Select all allows selecting all items from the list.
Deselect all allows deselecting all items from the list.

Automatic unload​

The other procedure present in the DN header is the automatic shipping from the warehouse. The button is enabled if the document is Printed.
Remember that if in the DN Parameters the automatic shipping is enabled, this procedure will be started automatically once the document is printed.
Once the procedure is initiated, Fluentis checks for the presence of warehouses and reasons in the DN lines and the eventual presence of lots and serial numbers if required; if the procedure does not go well, the user will be notified with an error.
If the procedure is successful, a Warehouse Registration is created, which moves the items in the document, and the Load flag is inserted in the DN header.

Items​

In this tab, all items with their respective data are entered.

For everything not detailed in this document on the common functioning of forms, refer to the following link Common Features, Buttons, and Fields.

The data is entered manually, with the help of the field help or can be proposed by the connected procedures.

To insert a New Item in the grid, simply position yourself on the row to fill in the various data or use the New button present on the ribbon bar. The available columns are as follows:

  • Line number: this field will automatically and progressively populate as data is entered in the line.
  • Line type: offers the option to select, from the combo box, items with different characteristics:
  • Codified Item: these are items coded in the registry and can be accounted for in analytical accounting and recorded in the warehouse.
  • Uncoded Item: these are descriptive items that can be accounted for in analytical accounting but cannot be moved in the warehouse.
  • Charge Item: these are coded or uncoded items and are summarized separately in the document summaries; if the expense item is coded and of fiscal interest, it will be moved in the warehouse; if it is uncoded or not of fiscal interest, it will not be moved in the warehouse.
  • Note Item: these are descriptive notes included in the document print; they do not affect accounting and warehouse.
  • GiveAway Item: the gift item is treated as a coded or uncoded item for fiscal and warehouse purposes, but being a gift, it is counted separately in the document summaries and based on the VAT reclaim flag, the VAT amount of the gift will be calculated to be charged to the entity or not.
NOTE

If starting directly with the item insertion, its class, code, and line type - Coded Item will be automatically entered.

  • Barcode: if the management of Barcodes is enabled in the DN Parameters, the Barcode column will appear where you can select the data for the item from the Barcodes entered in Item Registry > Barcode.
  • Item Class/Code/Description: it is possible to enter manually or with the assistance of the field help, which will propose all the related data entered in the Item registry. After entering the item, its Description will be automatically retrieved from the registry. If the item has Variants, it will be possible to select the desired variant from the Item data tab.
  • Customer item: if the management of Customer Items is enabled in the DN Parameters, the Customer Item column will appear, with the valid item code for the customer to whom the document is issued and entered in Item Registry > Customers.
  • Units of Measure: the main unit of measure of the item is proposed, but in the case where alternative units of measure are coded in the item registry, the user has the option to choose another one.
  • Quantity: represents the quantity of the main unit of measure and by default has the value 1; it can be manually modified or can be taken from the document considered for fulfillment.
  • Price: the price is proposed from the price list entered in the contact registry; the reference price list for the item itself is displayed in the Discounts/Price Lists tab; the same document may contain items with prices taken from different price lists if multiple cascading price lists are associated with the subject in the registry (see Register Printing). Through a double click in the Price list field (in the Discounts/Price Lists tab), the user has the option to select a different price list from the default one, from which the price of the entered item will be taken.
note

In the absence of a price list, the proposed data is the Sales price retrieved from the Item Registry > Cost tab > tab Costi or it will be retrieved based on the document parameters settings. In the absence of this data, the price will be shown as 0.

  • Origin amount: this field shows the Unit Price, multiplied by the item quantity, net of discounts.

  • Item discounts: it reports the sum of the discounts provided for the item.

  • Item final discounts: it reports the sum of the final discounts entered for the item in the document summaries.

  • VAT: the data entered in the VAT field of the Contact Register is prioritized; if this is not present, the value from the Item registry is proposed, but the user has the option to enter another value. It is a mandatory field.

  • Sales Turnover: the data entered in the Item Registry > General tab is proposed. If this is not present, no data will be proposed, but at the time of invoicing the invoice, the value entered in the Default Counterparty Cost/Revenue field of the Customer Registry > Accounting Data > Administrative tab will be considered, or an error message will be generated.

  • On invoice: this flag is inserted by default, but can be disabled if the item should not be transferred to the invoice and therefore should not appear in the DN fulfillment procedures.

  • Net weight: shows the net weight present in the item registry, multiplied by the item quantity of the line.

  • Gross Weight: shows the gross weight present in the item registry, multiplied by the item quantity of the line.

Specific buttons​

Recalculate Recycle: if the CONAI is enabled for the document, it is possible to recalculate the values with this button after any updates.

Update the Recycle values of the Item registry: if the CONAI Materials for the item tab is modified with Units of Measure and/or Weight, these values can be transferred to the CONAI section of the item registry.

Packages management: allows opening the management of packaging to be returned used in the purchase document. The button becomes active if the document is saved but not loaded. Clicking this button opens the corresponding form where: enter the quantity, select the line and transfer the selected packaging into the item lines by clicking the Execute button. In this form, the items that have been entered with the nature Packaging and that are present in the table of Packaging to return will be reported.

Update price lists: by clicking on the dropdown next to the button, you have access to two procedures. The first procedure is Refresh current price list, which allows aligning the price of the item internally to the Listino, following a possible price variation directly in the item line. Instead, with the second procedure, Create new price list with new validity, it is possible to create a new customized price list for the customer to whom the document is issued; it will request, in a pop-up, the start and end dates of validity of the new price list.

Show/Hide details: clicking this button will make the internal tabs of the Items visible or not.

3.1 Discounts/Price Lists​

In this tab, the price list and discounts associated with the item line can be consulted.

In the Price list section, the price list from which the item has been retrieved is proposed, along with the start/end validity date.
In the Bracket type, the default tier that the customer has associated for this price list is proposed; if no default tier is present, a discount tier can be manually selected to use; it is important to remember that price lists can have different discount tiers associated with the same item (quantity discounts, general discounts, etc.).

The Manual price flag not active means that the price list, price, and discounts of the line are all calculated automatically; if the user changes any of these, the flag will be activated.

In the Discounts grid, all discounts associated with the item are proposed, each with its own calculation base and assignment. Discounts can be retrieved from: the customer registry, the payment solution assigned to the document, from the price list via the price list-customer association. All proposed data can be modified.

Specific Button

Delete discount: allows you to delete the discount associated with the selected item in the above grid.

3.2 Data​

This tab contains/entered additional information related to the item.

  • Alternative UM: in these fields, the alternative unit of measure will be displayed if this data is present in the Item registry in the Alternative UM tab (it takes the one with the Default flag set), and if the flags have been activated in the docUMent parameters: Manage double unit of measure and Automatic proposal alternative UM.
  • Alternative quantity: the value related to the alternative UM is proposed, calculated by UMltiplying or dividing the Operational quantity (related to the main UM) by the Conversion Factor set in the Item Registry > Alternative UM tab.
  • Alternative unit of measure price: this flag indicates to consider the alternative quantity for the item; the line amount will therefore be calculated as price for the alternative quantity.
  • Warehouse and Reason: the warehouse and cause of reference will be automatically proposed that will appear when the items are discharged from the warehouse. The data is retrieved from the DN Types or entered manually.
  • Variant: it is possible to choose a variant of the item, if coded within the Item Registry > Variants.
  • Execution status: in this section, it is possible to verify whether the item line has been Valuated, Partially Valuated, or Forcefully Valuated.
  • Project: it is the project associated with the document or can be assigned with the help of the field help.
  • VAT recourse: if set, the VAT of the gift is considered for the document total.
  • Order reference: refers to the order from which the DN was created.
  • Our Reference/Your Reference: in these fields, an internal reference and a customer reference for the document is usually indicated; if the DN is generated through an automatic creation procedure, these fields will be populated with the indications present in the origin document.
  • Reference Number/Date: refers to the Reference to the Number and the Date of the original Customer Order.
  • Brand: represents the brand of the item, taken from its registry or from the item's price list.
  • On invoice: this flag is inserted by default but can be disabled if the item should not be transferred to the invoice and therefore should not appear in the DN fulfillment procedures.
  • Note: allows entering notes for each item.
  • Detail declarations: the Intent Declaration used to propose the VAT of the item is reported; from the combo box, it is possible to change the reference intent declaration if more valid declarations are present.

3.3 Agents​

  • Agent: the agent linked with the corresponding commission for the selected item; the data corresponds to that present in Header > Agents tab. The percentage can be changed.

Specific button

Delete agents: allows you to delete the agent associated with an item.

3.4 Lots and Serial Numbers​

In the two grids, lots and serial numbers that need to be discharged from the warehouse can be entered.
This operation is conditioned by the presence of lots and serial numbers in the warehouse.

If the item does not require the management of Lots/Serial Numbers, this tab will be disabled.  

Specific buttons​

  • Delete Batch: allows you to delete the selected batch line.
  • Cancel serial number: allows for the deletion of the selected serial number line.

3.5 Analytical​

It can contain information about the cost/profit centers on which the values of the items are distributed.

This data can be entered manually or automatically (in case the cost/profit centers have been previously entered in the contact register, Item registry, or in the Chart of Accounts).

3.6 Extra Data​

The list of Extra data related to the item is displayed, with the possibility of adding new extra data useful only for the document in question. The To print flag allows you to choose which extra data to print.

3.7 Attached Documents​

The details of any Attached Document (name, type of document, any notes, our/their reference) are displayed. For instructions on how to attach a document, please refer to the article Attach Documents.

3.8 Values Section​

The section at the bottom right presents a summary of the costs that contribute to the formation of the final price of each selected item in the item grid. The fields present are:

  • Unit price: the value of the Price field;
  • Quantity: the value of the Quantity or Alternative quantity field, depending on the Alternative Measurement Unit Price flag;
  • Line amount: Item price * Item quantity;
  • Total discounts: the sum of the item discounts, including any final discounts;
  • Origin amount: Gross amount - Discounts;
  • VAT: Taxable amount * VAT rate of the item;
  • Total: Taxable amount + Tax.

Summaries​

In the Summaries, the main information of the entire document is presented.

4.1 Final Item Discounts​

The final discounts applied at the level of each individual item are distributed (or "spread") across each item line of the document. This means that the discount amount is proportionally divided among all the items present in the document, and the corresponding discount will be visible in the Items tab for each individual line.

  • Type/Description of discount: allows you to choose the types of discounts (preset in Discount Types), assigning the type the priority for discount application and whether the discount is calculated on the taxable amount or cascaded from previously applied discounts.
  • Priority: represents the priority of discount application; the ordering to be applied occurs in ascending order.
  • Cascade/Amount: to define whether the calculation of the discount uses as taxable the (price * quantity) - (discounts already calculated) or (price * quantity).
  • Value: numerical value of the final discount to be applied.

4.2 Agent Commission Summary​

In this tab, the commissions expected for each agent are summarized.

4.3 Fees/Discounts/Final Increases​

Expenses entered in the contact register are proposed in the Charges/Discounts tab. In this grid, any expenses should be entered as positive, and any discounts as negative.

These elements are applied to the totality of the document and are not distributed among the article lines. They may include additional costs, global discounts, or surcharges applied to the entire document. If set in the item registry, they are automatically proposed at the time of document creation.

  • Type/Description: allows you to choose the types of expense (predefined in the table Expense Types), assigning a percentage of the expense to apply to the type.
  • Charge amount: indicates the value of the expense expressed in the currency of the document.
  • VAT: indicates the VAT rate to be applied to the entered expenses.
  • Percentage/Value: indicates whether to calculate expenses with a percentage or with a predefined monetary value. By selecting Value, the expense amount should be entered under the corresponding heading.
  • Percent Completed: numeric value of the expense percentage.
  • Detail declarations: the possible valid intent declaration for the customer is inserted.

4.4 VAT Summaries​

The VAT summary of the document is proposed for each VAT code.

4.5 Due Date Summary​

Represents the summary of the document deadlines, for each type and payment solution.

  • Number: progressive value of the line.
  • Payment: represents the alphanumeric code of the Payment type retrieved from Document Header > Payments tab.
  • Amount: Amount of the calculated deadline. It can be manually overridden, in which case the subsequent flag Manually edit is automatically activated. (Automatic controls and alerts regarding the alignment between the deadline values and the total invoice are triggered)
  • Expiry date: Date of the calculated deadline. It can be manually overridden, in which case the subsequent flag Manually edit is automatically activated.
  • Collection charges: Field in which the calculated collection fees are reported.
  • VAT: to be applied to collection fees (can also be set manually)
  • Payment template: it is possible to directly enter a ledger template in the invoice that leads to an automatic recording of collection/payment. Note: pay attention to the template of the template because it will use the accounts present even without detail account, which is why the following field is present.
  • Customer/Supplier detail account: account used to collect/pay (cash or bank, for example) the deadline, overriding the account present in the payment (or collection) ledger template.
  • Receipt no.: An eventual receipt number for the money received.
  • Single: activates the accounting of the deadline closure in the automated writing.
  • Discount type: Type of financial discount.
  • Mat. value: Value of the financial discount on collection.
  • Detail declarations: This is the reference to the declaration of intent. The VAT applied to collection fees could always be a plafond VAT, so it is also necessary to insert the related declaration of intent here (as for item lines and expense lines).

PURCHASE INVOICES:

  • Sign: only the deadlines that have this flag are then managed in payment with the template and account set.
  • Payment reference models: Model for creating the payment code. In some foreign locations, each deadline in the invoice requires a code assigned by the invoicer: this code is structured according to specific models (table MB_PaymentReferenceModels), in order to construct the code with an algorithm.
  • Payment model codes: This is the code (structured as per the previous model) to be reported in the transaction and then in the payments sent to the bank, so that the bank communicates to the beneficiary which deadline has been paid (thus automating the import from bank movements with transaction closure). From here it is populated inside the transaction and in the Sepa file.
  • Prepayment date limit: This is a field provided in the ES invoice trace, the deadline for being able to apply the financial discount.

4.6 Document Totals​

  • Items gross amount: represents the sum of the values of all items.

  • On-account: represents the value of any deposit received for the document.

  • Amount giveaway: represents the amount of items classified as gifts entered in the Items tab.

  • Total discounts applied: represents the total value of discounts applied to the items, excluding final discounts.

  • Items net amount: Items gross amount – Total discounts applied.

  • Final item discounts: represents the value of final discounts expressed as a percentage of the gross amount of the items.

  • Net amount of final discounts: Items net amount - Total final discounts.

  • Total charges items: represents the value of expenses entered in the previous tab as items of Charge type.

  • Collection charges: represents the sum of collection expenses entered in the Charges grid.

  • Stamp charges: represents the sum of stamp duty expenses entered in the Charges grid.

  • Total expenses/discounts/increases: represents the total value of expenses entered in the Charges grid.

  • Origin amount: Items net amount – Final discounts + Total charges items + Total expenses/discounts/increases.

  • VAT: represents the sum of the values contained in the VAT summaries.

  • Total: Origin amount + VAT.

Transport​

The data present are:

  • Recipient: the default recipient entered in the customer registry is proposed; if not present, the customer's address is taken.
  • Destination: the default destination of the recipient is proposed, if entered in the customer registry.
  • Tracking Number: free field.
  • Volume: the cumulative volume is proposed, resulting from the sum of the volumes of the items (the value is taken from the Item Registry > Weights/Dimensions tab), when the unit of measure of the volume of items corresponds to that entered in the DN parameters.
  • Net weight: the cumulative net weight is proposed, resulting from the sum of the weights of the items (the value is taken from the Item Registry > Weights/Dimensions tab), when the unit of measure of the weight of the items corresponds to that entered in the DN parameters.
  • Gross Weight: the cumulative gross weight is proposed, resulting from the sum of the weights of the items (the value is taken from the Item Registry > Weights/Dimensions tab), when the unit of measure of the weight of the items corresponds to that entered in the DN parameters.
  • Type of packaging: combo box that refers to the homonymous table.
  • Packages: the number of packages is proposed, based on the data entered in the Item Registry > Weights/Dimensions tab, in the fields Items present in one package or Packages for item. Only items that have this field filled will be considered.
  • Values manually modified: with this flag, we enable the modification of the Volume, Net Weight, Gross Weight, and Packages fields, which otherwise show the data from the item registry without the possibility of modification.
  • Customs Office Entry/Exit: fields used for eTransport for the Romanian version, referring to the Customs Office table.
  • Border Crossing Entry/Exit: fields used for eTransport for the Romanian version, referring to the Border Crossing table.
  • Transport: it is necessary to select the person responsible for the transport, setting the flag in Sender, Recipient, or Carrier; based on the selection, the section below will change; if the transport is at the Sender's expense, it will be possible to enter Vehicle License Plate, Trailer, Date and Time of Transport Start; if at the Recipient's expense, it will be possible to enter Vehicle License Plate, Trailer, Date and Time of Transport Start; if at the Carrier's expense, the available fields will be Accounting Registry of the Carrier, License Plate, Trailer, Date and Time of Transport, possible Client, Loader, Owner, Loading Place.

Linked documents​

In this tab, you can consult the attached documents. To attach documents, you can proceed in two ways:

  • using the button on the toolbar Documents, you can choose to attach a document already coded in Fluentis or create a new Document to attach.
  • directly using the right button in the grid and selecting Attach a file, you go about creating a new Document to attach.