2565 rfsa

From UG

Contents 1 PARENT MANTIS 2 Glossary 3 REQUIREMENTS 3.1 Estimated Cost 3.2 Estimated Sell 3.3 Reports 4 DESIGN IDEAS 5 SA Notes 5.1 Summary 5.2 Implementation Phase 1 5.2.1 Shipments 5.2.2 Reports 5.3 Implementation Phase 2 6 LA Notes 7 HISTORY

PARENT MANTIS

0002515: [Estim P&L] .......<proj>

Glossary

Gross Margin - same as "P/L".

Point Of Revenue Recognition - This is the date that the "Sale" is considered complete. (based on law/standard)

For Ocean LCL and FCL Shipments #Port Of Loading Actual Date

For Air shipments #Airport Of Departure Actual Date

For Truck shipments #Actual Export Pick Up Date

Month-end closing An accounting procedure undertaken at the end of the month to close out the current posting period. IN the context of this task it means to have all cost and sale numbers are available. This is for CTs that reached Point Of Revenue Recognition.

REQUIREMENTS

Core: Enable accounting to “close out” the month end, at the actual end of each month, based on estimated charges. In order to achieve this we will follow the below.

Estimation for freight charges:

• Pull the estimated sell rate from a database to be entered under the client profile (to be handled on phase 2)
  • If nothing is in the database that matches the required information(TBA defined in Phase 2)the system should automatically calculate the estimated sell by:
    • Pull cost from a database (to also be handled in phase 2) and add 15% to it. The estimated sell should equal the total of the (cost x 15%)+ cost
  • Work around for Phase one - Operators should manually enter cost. The sell should calculate automatically be based on the above calculation.
• Operators will need to be able to edit the costs and sell and cost or sell estimations manually.
• They should also be able to add and remove lines from the estimation.

Exception:

• Customs Cost's
  • Charge Codes beginning with 12 should have no calculation. The sell should match the cost entered. (System should copy same number from cost to sales field).
  • The operators should still be able to manually update the cost and sell and the cost or sell.

Estimated Cost

should reflect:

• Dollar Amount
• Vendor
• Currency
• Charge Code
• Charge Code Description

Estimated Sell

should reflect:

• Bill To Party
• Dollar amount
• Currency

Reports

• Should be able to generate a report showing both estimated cost/sell and actual cost/sell
• The report should be per CT record
• should be within a selected time frame
• should able to download to excel

DESIGN IDEAS

These charges will be entered in on a separate Tab Est., as per examples below

Once these charges are entered into this Estimation invoice – It should then pull through and show on the P/L tab.

The difference between actual and estimation should be easily identified (by example attached maybe using a lighter color)

SA Notes

Summary

Questions:

1) In BR is described only actions that provide work with estimated cost and sell and eventually profit/loss values. Would be good define the meaning of term "close out the month end".

2) Is it separate procedure? Or reaction of system on the reaching of the Point of Revenue Recognition? (By example, the preventing of editing of some CT fields). Or something else?

Implementation Phase 1

What we need to do in:

Shipments

• New CT Tab - Estimated (like a New Invoice Template include Table of Charges)
  • List of Fields
• Manually enter estimated cost
• Automatically calculate estimated sale
• Immediately show estimated values on P/L Tab

Reports

• Edit Profit/Loss for Multiple CTs report
  • change "Profit/Loss" in the name of report to "Gross Margin"
  • new Date Type - Point of Revenue Recognition
  • add estimated columns to Output

Questions:

1) Should the fields of Estimated Invoice be the same as on InvTab? Or should they reflect only Estimated Cost and Sell as specified in #Requirements?

2) In which moment should be filled Estimated Cost in TOC?

3) Could whether be allowed editing of "estimated" fields after the reaching of the Point of Revenue Recognition?

4) Do we need show Estimated P/L on P/L Tab? Now it is not reflected in requirements.

Implementation Phase 2

Questions:

1) Is estimated sell rate the client-specific?

LA Notes

• Requirement "Operators will need to be able to edit the costs and sell and cost or sell estimations manually." UI design should be "smart" to handle this well. For example add checkbox to every line indicating if it is "auto" or "manual". If auto then show sale box as read only. If "manual" then show both editable and do not apply auto calculate.

HISTORY

0002565: [Estim P&L] Complete Requirements / Design Ideas wiki sections