After the Vendor Has Been Selected the Buyer Prepares a Purchase Order by nvj15162

VIEWS: 20 PAGES: 27

More Info
									                            Introduction to Atlas
                                                                                       V1.4

First Release

Title                    Introduction to Atlas
Document Language        English
Responsible Unit         Learning Resource Centre (LRC)
Creators (individuals)   Ronald McGill (UNCDF); Mike Dodd (Editor/collator)
                         Special thanks to UNCDF who kindly agreed to the inclusion of their original
Contributors             material in the form of all the workflow diagrams, tables and supporting text.
                         CBS, Management Support Centers and the LRC
Subject (Taxonomy)       Atlas Overview and Concepts for first time Users
Date released            July 2005
Audience                 New Users to Atlas
                         This document is aimed at new Users to Atlas. Its goal is to provide an easy
Applicability
                         to read introduction and general overview of Atlas.
Replaces                 N/A
                         Internal Control Framework, Change Management Toolkit, Management And
Related documents
                         Monitoring Tools
Document Type            Introduction, Atlas


Revision History
Revision date      Comments From:        Summary of Changes
May 2005           Yuna Badaker          Reference to Atlas Training Site
July 21, 2005      Agi Veres             Relationship between PO’s and Vouchers/Non-PO Voucher
July 22, 2005      Ken Lewis             Addition of Report Summary
Content
                                                         Page
1. Purpose                                                   3
2. Key Atlas Sites                                           3
3. Atlas Overview & Business Processes                       4
4. Atlas Roles                                               6
5. Chart of Accounts (COA)                                   7
6. Commitment Control (KK)                                   9
7. Atlas Grants Module (traditionally called Projects)      11
8. Accounts Receivable                                      13
9. Billing                                                  15
10. Purchasing (Procurement)                                17
11. Vendors                                                 19
12. Accounts Payable                                        21
13. Prepayment (Accounts Payable)                           23
14. Atlas Reporting (Management and Monitoring Tools)       25




                                                                2
1. Purpose

In one clearly written document introduce a new Atlas User or newly recruited staff
member to key Atlas processes and explain the interrelation across the traditions tracks
of Finance & Treasury, Programmes and Projects, Contracts, Procurement and Assets.
To introduce the idea of Atlas User Roles and their relationship to UNDP Business
Processes.

For in-depth Atlas Lessons and Topics Users are referred to OnDemand (Atlas
OnDemand)


2. Key Atlas Sites
Atlas Login (Live)
Atlas Login (Training) Contact ps.support@undp.org for access to the training site.
Atlas OnDemand
UNDP Content & Support
UNDP Prescriptive Content
UNCSD




                                                                                           3
3. Overview of Atlas & Business Processes
Atlas is an Enterprise Resource Planning (ERP) System designed to help an
Organization to achieve results.

Its central features include:

      A planning, budgeting and reporting system

      A web-based integrated project, financial and human resource management
       system; and

      A real-time tracking and reconciliation system.


Diagram 1 below presents the general system of Atlas. The General Ledger is the
repository for all transactions in Atlas. The diagram highlights the business flow between
each of the particular modules. No Module is an island, when using Atlas it is important
to be aware of the whole business process that your User Role is part of – for
example, a Buyer may raise a Purchase Order, but the Finance Officer is responsible for
the Payment. One business process – but two User Roles, it is therefore imperative
for the Buyer and Finance Officer to work together as a team. Country Offices must think
in terms of whole business processes and not standalone Units.

Diagram 1 General System of Atlas

                                                                                  CONTRACTS/
                                                                                    BILLING
                                                               Bills

      HUMAN
                                      Income      ACCOUNTS             Payment       GRANTS/
    RESOURCES/                                                         Schedule
                                                 RECEIVABLE                          AWARDS
      GLOBAL              Payroll                                      s
     PAYROLL
                                                                                      Approved
                                    GENERAL
                                                          Project Income              Grants
                                     LEDGER

                                                   Payroll and AP                    PROJECTS
         AP                                        Expenditures
         Expenditure
                                                                       Encumbranc     Project
                                                                       es             Budgets
                                         PURCHASING/
                        Purchase           ASSETS
       ACCOUNTS         rders
        PAYABLE                                                            COMMITMENT
                                                                            CONTROL




                                                                                           4
From the above diagram stem 23 currently defined UNDP Business Processes as
presented in the Change Management Toolkit

Results Management

   1. Create project
   2. Budget revision
   3. Project Closure

Contract, Asset and Procurement Management

   4.   Procure with a PO
   5.   SSA/SC
   6.   Travel
   7.   Create vendor

Human Resources Management

   8. Recruit 100 Local / 300 International & Local

Financial Resources Management

   9. Budget check
   10. Direct payment
   11. Payment of behalf of UNOPS
   12. Non-Atlas Agency payment
   13. Pay cycle
   14. Payment correction
   15. Billing CR-ENU
   16. Billing CSA
   17. Manage contributions
   18. Receipt
   19. Record deposit
   20. Bank transfer
   21. Deal management
   22. Bank reconciliation local
   23. Bank reconciliation interfaced

Business Processes flow through Atlas and cannot be taken in isolation – again, to
emphasize a point, no CO Unit or HQ Unit is an island.




                                                                                     5
4. Atlas Roles
Before a User can login to Atlas a User Role and an Approval Level must be assigned.
A User Role is largely related to a Job Function (e.g. Senior Manager, Buyer, Finance
Assistant etc). The Approval Level (of which there are three) determines the degree by
which a User is allowed to commit UNDP funds.

The User’s Supervisor must complete the Atlas Access Request Form and send it to:
ps.support@undp.org – this form requests both an Atlas User Profile and Approval
Level.

Care must be taken not to give conflicting User Roles which may have security
implications. For example, a Finance User should not also have a Buyer Profile. These
areas of conflict are outlined in detail in the Internal Control Framework.


Table 1 User Roles And Responsibilities

    ROLES           RESPONSIBILITIES                                     LIMITS
                   RC’s, RR’s, DRR’s
Senior Managers
                   HQ Unit Heads
                                                  L3 > $30k No approval Ceiling
                   Operations/Programmes                      Approval ceiling up to
                   Programme Managers.            L2 < $30k   $30,000
   Managers
                                                              Approval ceiling up to $5,000
                   Programme Officers in large
                   Country Offices                L1 < $5k

                   Billing                                    These Users cannot be
                   Accounts Receivable                        Buyers
 Finance Users
                   Accounts Payable


                                                              These Users cannot be
                   Purchasing – PO related
                   processing.                                Finance Users
    Buyers
                   Purchasing – Vendor
                   Maintenance

                                                              Apply to all who have access
                                                              to Atlas in whatever capacity
 General users     Projects - All can propose
                                                              and can at least view
                                                              information in all modules.
                   All Parties outside of Atlas               Project team, for example
 External Party    involved in the work process




                                                                                          6
5. Chart of Accounts (COA)
Fundamental to the use of Atlas is an understanding of the Chart of Accounts.

The Chart of Accounts is:

      An organizing framework used to budget, record and report on all financial
       transactions and account balances.

      A means to identify details about each organization’s financial transaction.


                                                        What the     Which entity
                     Whose                                              is re-
                                                        Money is
                  transaction                                         sponsible
                                                       Being used
                      it is                                              for
                                                           for




 GL        Acct         Fund     Oper        Dept         Proj         Imp            Donor
 BU                              Unit                                  Agy




         What type of
         transaction                             Where the
             It is                                Money
                                                Comes from


GL Business Unit (e.g. UNDP1):

   •   An independent entity which segregates its accounting data for tracking,
       reporting and possibly auditing purposes
   •   Represents the highest financial reporting level in Atlas
   •   Represents an independent entity
   •   There are a total of five GL Bus:
       UNDP1, UNCDF, UNFEM, UNFPA & UNOPS

Account Codes (e.g. 71635 - Travel – 5 digits)

      Natural classification of balance sheet and income and expenditure transactions
      Supports corporate statutory reporting




                                                                                         7
Fund (e.g. 20100 – 20700 Thematic Trust Fund for Democratic Governance):

   •   Legally separate source of funds which is self balancing and has a separate
       board or donor mandate.
   •   Each organization maintains separate fund table
   •   For UNDP, there are approximately 500 active funds.
   •   Funds of a similar type are grouped into ranges

Operating Unit (e.g. EGY):

   •    Represents country offices, HQs major units
   •    ISO code is used for country offices
   •    Self Balancing for UNDP
   •    UNOPS and UNCDF do not use Operating Unit Chartfield
   •    Operating Unit table is shared among all other GL Business Units

Dept (e.g. 31003 – 5 digits):

      Represents the hierarchical management structure of the entities
      Identifies departmental owner of a transaction
      Separate Department tables for each of the 5 GL Business Units
      HR Department table will populate FIN Department table via Application
       Messaging.

Proj (e.g. 00010001 – 8 digits):

   •   Captures development, as well as management project costs and revenue
   •   Provides the link between General Ledger and Projects, Grants and Contracts
       modules

Implement Agency (e.g. 000007 – FAO – 6 digits)

   •   Shared by all GL Business Units
   •   Tracks advances and payments made to or on behalf of implementing agencies

Donor (e.g. 00794 – Govt of Japan – 5 digits)

   •   Required to track donors’ revenue, as well as expenses apportioned to different
       donors/funding sources and to facilitate donor reporting
   •   Donor table will be populated automatically when a new Customer code is added
   •   UNFPA will not use Donor chartfield because this information is imbedded in
       their Fund code
   •   Shared among the other 4 GL Business Units




                                                                                     8
6. Commitment Control (KK)
UNDP management establishes the annual expenditure ceiling in Commitment Control
(KK). KK then relates Unit Plans with disbursement ceilings against available resources.

Unit Plans contain objectives and targets which are converted into:

       Projects

       Outputs

       Activities

       Expenditures

Diagram 2 below shows the Commitment Control Flow through User Roles – each point
is labeled and explained in Table 2.


Diagram 2 Commitment Control Business Process Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                       9
 Table 2 Commitment Control Activities



KK1   Overall Financial projections are updated in last quarter and core resources
      available for next year are determined.

KK2   Unit plans are finalized taking into account allocation established and anticipated
      contribution. The project budgets, which are cash controlled are established based
      on Cash Balance available at beginning of year.

KK3   Allocations are established by Department/Unit Heads.


KK4   Finance set up the allotment ceiling/funding in KK.

KK5   Core allocations cover both management and development project budgets. The
      Executive Board approves the Biennial Management Project budgets.
      Development project budgets are established annually based on cash balance
      and anticipated contribution.

KK6   Non-Core Allocation is set based on Cash only.

KK7   GL Business Unit, Fund and Department represent the three chart fields against
      which KK will budget check expenditures for projects funded under core allocation.

KK8   GL Business Unit, Fund and Donor represent the three chart fields against which
      KK will budget check expenditures for projects funded under non-core allocation.

KK9   Disbursement ceilings are set up by Department.




                                                                                      10
7. Atlas Grants Module (traditionally called Projects)
The Grants Module is used to establish projects within Atlas. It is the foundation for
generating awards. Awards are the basis for incurring expenditure to implement
activities in order to achieve outputs.

Diagram 3 below shows the Grants Module Business Process Flow through User Roles,
each point is labeled and explained in Table 3.

Diagram 3 Grants Module Business Process Flow through User Roles




                                                                                         11
Table 3 Grant’s Module (Projects) Activities as related to User Roles


      GM1      General User creates project proposal. Defines project title (short
               and long), identify the number of activities (sub-products to achieve
               main product, i.e. outputs), with the corresponding budget
               categories and costs, determine the project budget per period for
               the lifetime of the project. General User is also able to attach all
               documentation relevant to the project being proposed such as
               minutes of PAC meeting, project document, MOUs etc.

      GM2      Senior Manager approves the proposal whether it is a development
               or management project. DRR (P), ARR or Unit Head in Programme
               should review the proposal before the SM approves.
      GM3      Finance Unit generates the Award.

      GM4      General User then adds the General Ledger details, including the
               COA, for each identified activity.

      GM5      Senior Manager send awarded project to Commitment Control (KK).

      GM6      General User set status of project as Ongoing. Once this is done,
               pending items for receivables can be created and expenditures can
               be incurred.




                                                                                       12
8. Accounts Receivable
The Accounts Receivable (AR) module is used to track all contributions (core and non-
core), reimbursements or payments made to a Business Unit. Some of the payments
are made as income for services such as:

       Training workshops, and
       Missions

Diagram 4 below shows the Accounts Receivable Business Process Flow through User
Roles, each point is labeled and explained in Table 4.

Diagram 4 Accounts Receivable Business Process Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                   13
Table 4 Accounts Receivable Activities as related to User Roles


          SM/Finance determines the projection on annual core contribution based on
  AR1     previous pledges made by the donors.

          Schedule of payments from donors for non-core contribution is obtained
          from the signed agreements. Budget Owner based on annual work plan
 AR1”     and expenditure pattern may choose to increase or decrease the planned
          payment.
          Finance Unit creates pending items for core and non-core contributions.
  AR2
          UNDP Treasury or Country Office to record all deposits in the respective
  AR3     bank accounts.

          Finance Unit does the application of all payments in US Dollar.
  AR4
          Pending Item IDs for non-US$ contributions are sent to UNDP Treasury for
  AR41    their information

          System records the collected revenue against the corresponding fund and
  AR5     project for non-core and against the Voluntary Contribution fund for Core.




                                                                                  14
9. Billing
Billing is used to generate invoices to customers to ensure payments for services
rendered. The most common billing scenario for UNDP is to invoice other UN agencies
and other clients for support services (e.g. procurement and travel).

Diagram 5 below shows the Billing Business Process Flow through User Roles, each
point is labeled and explained in Table 5.

Diagram 5 Billing Business Process Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                   15
Table 5 Billing Activities as related to User Roles


         Memorandum of Agreement (MOU) is signed between the client and UNDP.
   B1
         Billing Processor prepares Customer ID request form to be submitted to
   B2    Management Support Centre, MSC (ps.support@undp.org)

   B3    Billing Manager signs the request form

   B4    MSC creates new Customer in the Shared Customer Table
         Billing Processor enters details to create Atlas pro-forma invoice. When the
         Client is UNDP, Billing Processor also creates a TR for the travel component
   B5    of the mission using a COA provided by UNDP.
         Billing Processor generate pro-forma invoice. Invoice must be set as "RDY"
   B6    to be picked up by Billing Manager.
         Billing Manager reviews printout and finalize all invoices set as Ready.
   B7
         System generates and prints final invoice. It also automatically generates a
   B8    corresponding Pending Item in AR from the invoice.

         Through a Batch Process the system generates AR Pending Items from the
   B9    finalized invoices.




                                                                                    16
10. Purchasing (Procurement)

The Purchasing Module allows UNDP to buy and track (capitalize as assets where
required) goods from suppliers or services from companies or consultants. Providers of
these goods or services are called vendors. Purchasing establishes the contract
between the vendor and the organization (UNDP).

Vendors are added to Atlas in the Vendor Module (See Section 10 below).

Diagram 6 below shows the Purchasing Business Process Flow through User Roles,
each point is labeled and explained in Table 6.

Diagram 6 Purchasing Business Process Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                     17
Table 6 Purchasing Activities as related to User Roles


  P1    Project set as ongoing.

        Request for purchase of goods or services are submitted to Buyer with
  P2    necessary supporting documents. Requests from the Country Office should be
        submitted through the Programme Officer.
        Buyer prepares Purchase Order (PO). Buyer should check Vendor information
        (ID and bank info) prior to creating PO and ensure that all supporting
  P3    documentation has been properly submitted.
        Budget Owner approves the PO. Manager Level 1 approves up to $5,000.
        Manager Level 2 approves up to $30,000. Manager Level 3 approve above
  P4    $30,000. If there is a problem with the PO, the Buyer is to go back and make
        the necessary corrections.
        Buyer budget checks PO.
  P5
        Buyer dispatches PO and files print out of PO along with supporting document
  P6    to ensure proper audit trail.

        After the goods have been received, the vendor submits an invoice to the
  P7    Requester. The hired consultant after rendering his/her services submits a
        Certification of Payment (CP) form.
        Requester certifies the invoice or CP preferably using a signature stamp.
  P8
        Buyer inspects and receipts PO for the fees or goods received based on
  P9    stamped or certified invoice/CP.


At this point the Business Process flows to Accounts Payable - when a PO exists, the
Payment Processor creates a PO Voucher (which in effect copies the details from the
PO to a Voucher) and processes the payment to the vendor.

When applicable, the Payment Processor prepares a Non-PO Voucher (generally for
amounts less than $2,500 that are not related to SSA contracts). Budget Owner
approves the Non-PO Voucher. Payment Processor processes the payment to the
vendor.

Accounts Payable steps are detailed below in Table 8, Page 21-22.




                                                                                       18
11. Vendors
In Atlas, before any Supplier, Contractor, SSA, SC, UNV or Staff Member can be paid
(including staff reimbursements, medical expenses and DSA etc) they MUST be added
to Atlas as a Vendor. If the ‘Vendor’ is a staff member their Index Number must also be
included in the Vendor Details.

Diagram 7 below shows the Adding a Vendor Process Flow through User Roles, each
point is labeled and explained in Table 7.

Diagram 7 Adding a Vendor Process Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                      19
Table 7 Adding a Vendor Activities as related to User Roles

          Request is submitted to Buyer with necessary supporting documents.
          Anyone who is to be paid in a CO Business Unit must exist as a Vendor in
   V1     that CO’s vendor table. If they do not, the Vendor Request Form duly filled
          out with Vendor name, address, bank information is also submitted to the
          Buyer.
          Buyer enters all information related to the vendor in UNDP’s vendor table to
          create the Vendor's ID, provided that he/she receives along with the vendor
          profile forms, a certified pro-forma or invoice by a recognized agent of
   V2     UNDP, whether at HQs (Programme Managers) or in country offices
          (Programme officers). These pro-forma forms or invoices can be sent
          through PDF or by fax.
          To approve, the designated approvers (normally those with a Finance
   V3     Profile) review the information entered in Atlas as well as the relevant
          documentation submitted by the Buyer.




                                                                                     20
12. Accounts Payable
The main purpose of accounts payable is to disburse funds in payment for goods
purchased and/or services rendered.

Diagram 8 below shows the Accounts Payable Business Process Flow through User
Roles, each point is labeled and explained in Table 8.

Diagram 8 Accounts Payable Business Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                 21
Table 8 Accounts Payable as related to User Roles


        Documentation (Invoice) submitted by Vendor.
 AP1
        Invoice certified by Budget owner and submitted for payment.
 AP2
        When applicable, Payment processor prepares a Non-PO Voucher (generally
 AP3    for amounts less than $2,500 that are not related to SSA contracts).

        Budget Owner approves the Non-PO Voucher.
 AP4
        When a PO exists, the Payment Processor creates a PO Voucher (which in
AP31    effect copies the details from the PO to a Voucher)
        The Payment processor will press the Copy from PO button to bring in all the
AP41    information from the PO in the AP voucher.

        Payment processor clicks budget check link. He/she has the option of letting
 AP5    the system run the budget check.

        System picks up voucher in Pay Cycle.
 AP6




                                                                                 22
13. Prepayment - Accounts Payable
Accounts Payable is also used for prepayments. The main purpose of prepayment is to
create an advance payment (usually quarterly) against a project’s planned activities for
the next quarter of its Annual Work Plan (AWP).

Diagram 9 below shows the Prepayment Business Process Flow through User Roles,
each point is labeled and explained in Table 9.

Diagram 9 Accounts Payable Prepayment Business Flow through User Roles




 SR MNGR/
 MANAGER




 EXTERNAL
  PARTY




                                                                                      23
Table 9 Accounts Payable Prepayment as related to User Roles


  PP1     Project set as ongoing.
          Request for quarterly advances prepared by project team in the field (CTA)
          is submitted through the PO. Hardcopy of the request remains with the
  PP2     Programme Officer while an electronic version of it is sent to HQ.

          Payment Processor in the field creates the Prepayment voucher.
  PP3
          Senior Management approves voucher. Value generally exceeds $30,000.
          The electronic version of the request along with the current Annual Work
  PP4     Plan should be submitted as supporting document.

          System picks up voucher in Pay Cycle.
  PP5
          At end of quarter, Project team submits Project Delivery Report (PDR) to
          Programme Officer/Assistant detailing all expenditures incurred. PO is to
  PP6     review the information and ensure that each expenditure correspond to an
          Activity, Budget Category and Account of the budget.

          Payment Processor in the field creates a regular AP voucher, using the
  PP7     accounts and distributions identified in the project budget. The budget is
          directly debited at this stage with all the expenditures incurred.
          Senior Management approves voucher. Value generally exceeds $30,000.
  PP8
          Payment processor clicks budget check link.       He/she has the option of
  PP9     letting the system run the budget check.
          Payment Processor in the field will execute the reconciliation
 PP10




                                                                                  24
14. Atlas Reporting (Management and Monitoring Tools)
There are many reports and other tools to monitor financial and human resources
situation; there is a need to point managers to the key reports to understand the overall
situation of their office, projects and human resources.

Table 10: Summary of key management information and financial monitoring tools

Tool/Report                What does it show?
Executive Financial        Shows overview by Fund, Resource Balance and Development/
Snapshot                   Management activities:

                               Income, ASL and Cash limit
                               Budget
                               Expenditure
Regional Resource          Shows aggregate financial summary by country:
Overview
                               ASL/Cash limit
                               Approved Budget Encumbrance
                               Disbursements
                               Delivery Rate
                               Advances
Office Resource            Shows aggregate financial summary by project:
Overview
                               ASL/Cash limit
                               Approved Budget Encumbrance
                               Disbursements
                               Delivery Rate
                               Advances
UNDP Landscaping           Shows by chosen indicators (List of indicators):
Tool (in the Toolkit for
Managing Change)                 Comparison ranking of selected country and others by
                                  chosen indicators, average and top 25 by same indicators
UN Resource Overview       Shows by selection criteria:

                                  Fund description
                                  ASL,
                                  Cash brought forward (AX1)
                                  Revenue,
                                  Total Income (AX1+Revenue),
                                  Approved Budget, Encumbrance, Disbursement (Total
                                   expenditure)
                                  Receivable

                           (Expenditure figure excludes Advances)
Atlas Data Quality         It shows data accuracy and discrepancies.
Dashboard
Resource Planning          It shows by all projects for the selected department and fund at the
Framework                  award and project level:

                           Project Budget vs. Department Budget, Associated award
                           Expenditure and Advance (aggregated, not project level)


                                                                                                  25
Tool/Report           What does it show?

Combined Delivery     It shows for selected parameters at award and associated project
Report (CDR)          level:

                         Project (ID and name)
                         Government disbursements
                         UNDP disbursements
                         UN Agency disbursements
                         Encumbrance
                      (Includes gain/loss of exchange rate, but not advances

Cash Balance Report   It shows for selection criteria Income and expenditure for all cash-
                      controlled (cost-sharing) projects:

                      Opening Balance, Collected Revenue, Available Cash,
                      Pre-encumbrance, Encumbrance, Disbursement,
                      Total Expenditure
Staffing Table        Position and incumbent information for all staff and vacant positions:

                      Fund, Donor, Project ID, Project Activity, Implementing Agent, %
                      (Distribution) Position Number, Position Type, Position Status,
                      Position Location, SPA Grade, SPA Step, Budgeted Grade,
                      Classified Grade, Post Utilization, Name, EmplID, Grade, Step,
                      Contract Begin Date, Contract End Date and Functional Title
Position Mgmt         Shows where positions are missing a valid set of chartfield values
Exception Reports     and/or where positions are missing approved budgets.
(PVR)
Annual Workplan       It shows for that Award and all associated projects:
Report
                              Expected Output,
                              Activities,
                              Timeframe, Responsible party, Budget (Fund, Donor,
                               Budget Description, Amount)
                      (Both finalized and non-finalized budgets)
Status of Project     It shows for a combination of selection criteria project level detail:
Budget
                             Pre-encumbrance, encumbrance and expense. (Expenditure
                              includes Advances)

                               The report can be sorted by department, fund, operating unit
                                or project manager
Project Budget        It shows for selected business unit all or selected projects at the
Balance               activity level:

                             Budget
                             Pre-encumbrance
                             Encumbrance
                             Disbursement
                             Total Expenditure
                             Balance (not inclusive of Advances)
                             Advances (as separate column)




                                                                                               26
Tool/Report             What does it show?

UN Expenditure Detail   Most detailed expenditure report (including vouchers), it shows for
Report                  all activities of a selected project:


                             Vendor,
                             Voucher (w/description),
                             PO
                             Accounting Date,
                             GL Unit
                             Implementing Agent, Fund,
                             Donor
                             Account,
                             Analysis Group and Type,
                             Invoice and Payment info, Journal info
                             Currency and Exchange rate
                        (Does not include advances in expenditure)
Bank to Book            Reconciles the Bank Balance as reported by your Bank to the Book
Reconciliation          Balances as recorded in the General Ledger (GL).
(summary report and
detailed report)
UN_XB_SUMMARY           Provides an overview of extra budgetary resources for a given
                        department and by fund, by showing XB income and expenditure
                        under specific accounts.

Unapplied deposits      It shows for the selected business unit:

                        Payment amount not applied to projects from selected donor

Unapplied deposits      It shows for the selected business unit:
Aging
                        Payment amount not applied to projects from selected donor
                        Age in days



For detailed information on running Atlas reports please go to the Atlas OnDemand
Management Information Tab. Also, under this tab, under Key Documents is an
excellent document on Atlas Reporting, produced by CBS, entitled ‘Atlas Management
and Reporting Tools’.




                                                                                              27

								
To top