Purchase Invoices

From UG

Revision as of 17:44, 29 June 2009

Intro

• 1] System provides facilities for entering, editing, reporting on incoming (purchase) invoices (PI).
• 2] Related sub-components are:
  • PI profile
  • Incomplete PI Report
  • Search PI Report

PI Profile

User Interface Overview

See example below: http://mantis.jaguarfreight.com/svn/ct2/SS/acc/PI/v4/PI_form2.JPG

It consists of the following sections:

• navigation/actions (Save, New, Back, etc)
• sec A – General Fields (for example Total Amount)
• sec B – Table Of Charges (TOC)(this is a multiline table that presents breakdown of charges by charge code and by CT)
• sec C – Table of Masters Distribution (TOMD) (this is an instant report that illustrates how charges mapped to a particular master would be distributed proportionally among CTs for example based on number of CTs inside of that Master )

General Fields

• Vendor - single select, values = [Admin.AddrBook.VendorsTab];
  • all categories V1, v2, … combined;
  • default = blank

• Receiving Office
• Invoice#
• Date – date/time – datebox and timebox, read-only
  • default – current date and time (when new inv created)
  • when opened for edit, date/time would be updated to current
• Currency
• Amount
• Exchange Rate to USD (based on Date/time above)
• Note

Charge Base

• [1] Charge Base (CB) is a physical quality of the CT/Master and is a basis for calculating charges. For example, CB for Air shipment is normally Chargeable Weight and CBV for Truck shipments is Gross Weight.
• [2] Charge base Value is a specific value for that Charge Base, for example: 5 cbm
• [3] There are 4 types of CB:
  • chargeable_weight (unit of measurement is kg or lb)
  • gross_weight (unit of measurement is kg or lb)
  • volume/cbm (unit of measurement is cbm or cft)
  • CT_count (unit of measurement is Number Of CTs)

Table Of Charges (TOC)

1) TOC is used to assign portions of total PI amount to specific CT or Master.

2) If there is at least one line in TOC then Total for TOC must be equal to PI total. If not then system will refuse to save invoice.

3) Typical use case to complete TOC:

• user selects how many lines he wants to add and clicks "Add"
• system produces that number of lines. All fields are empty except Currency that is pre-filled to currency selected in PI General Fields Section
• user selects Charge Code
• system pre-fills Description (defined in CC Admin), M/I (defined in CC Admin)
• if it is I-type then:
  • system produces empty textbox for user in "CT#" column and no textbox in "M#" column
  • user enters existing CT#

• if it is M-type then:
  • system expects Master number to distribute charges
  • system offers 2 textboxes for entering M itself and CT for entering any CT that is a part of M that we are looking for
  • user enters amount
  • this amount is mapped into M and split accordingly to CBV rules
• if it is CT then 100% of amount would be mapped against that CT

Completeness and Errors

• [1] There are a number of cases when there are not enough information for PI to be saved or to mark PI as completed

• [2] PI cannot be saved if:
  • charge is M-charge and user enters CT that has no Master
  • TOC Grand Total is not equal to Purchase Invoice Amount
  • CC code field is empty

• [3] PI can be saved but will remain on "incomplete black list" if:
  • CBV = 0 for at least one master or CT in TOC

Future PI parameters change

• [1] General PI fields and TOC fields are parameters. Some of them can change in the future - after PI has been successfully saved with "complete" status. For example CT can be removed from Master or CT's volume can be changed to 0. In this case PI status will become "incomplete".

• [2] Here is full list of such cases and how system react to them:

Questions and Answers

RFC and Future

History