Histórico da Página

The Travel routine (FINA665) has all the information related to trips already issued via agency or request for individual travel.

A trip is composed of:

Travel header, which has the start and end dates, origin and destination, customer to be served (when applicable) etc.

The advances tab lists the participants and the advances requested for each one.

In the tab of the trip itself you will see the list of all orders placed.

When selecting a travel order item, a context per service is enabled with specific data for each one, such as: For a flight, there is Airline, Locator, Class etc.; in the case of a hotel, there is the Hotel Name, check-in and check-out dates etc. Possible services are:

• Flight
• Accommodation
• Car
• Road
• Insurance
• Other

Participants and related Cost Entities are also displayed.

A trip made on Reserve is integrated only when it is issued, that is, it is not possible to change its services in Protheus (dates, values, etc.). The only editable data are the Cost Entities. For more details, see the TOTVS X Reserve integration manual.

A trip generated by a Travel Request from Protheus, on the other hand, must have its service details informed by the travel department through the Verification option, since the request is an order for the purchase of the trip. If approval is enabled after the verification, a pending approval will be generated for the superior of the participants.

A trip with all its services and expenses properly paid and accounted for is eligible for billing. This process displays the travel costs that can be passed on to the customer, in whole or in part, and generates a sales order for the customer. If it is not applicable for the company segment, this step is not required.

With a trip in progress or after its completion, the traveler must account for expenses to the company.

Every trip, regardless of whether or not there is an advance, automatically generates a record in the Accountability routine (FINA677) linked to it.

A rendering of accounts has the basic data of a trip, such as its number, start and end dates, location, customer that was served (if applicable), in addition to the cost entities and percentage of billing against the customer (if applicable) etc.

The employee may inform their expenses item by item, informing: expense, location, amount (in local currency or other and its conversion rate), quantity, cost entities, etc.

In addition, advances are listed on accountability and deducted from the total amount at the bottom of accountability.

The amounts spent, refundable and the balance are also shown in the bottom, in the 3 currencies used by Protheus: local, dollar and euro.

Once finalized and forwarded to the travel department (after its inclusion or at a later time by the option to send to be checked), the travel department will check the accountability. Although the system already calculates the reimbursable amounts of expenses using the expense limit rule, if the verifier identifies an item in the statements that are outside the travel policy, they can post the discounts at this time and the amount to be returned/refunded is updated.

If the approval and/or release steps for financial are active, pending issues will be generated for the superior of the traveler and for the financial/travel department, respectively.

Example:

In the event that the whole process must pass through approval or verification, we have:

If any step can be performed automatically, we have:

Finally, in addition to the trips, the routine also allows individual rendering of accounts.