Download Report

Mississippi Management and
Reporting System
Department of Finance and Administration
5610
MMRS MASH/Training Materials
SAAS Agency Manual
Revision Date: 01/20/2014
Expenditure Accounting
Version: 2
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
SAAS Agency Manual
Expenditure Accounting
Table of Contents
General ...................................................................................................................................... 3
Payment Voucher Transactions ................................................................................................. 3
Payment Voucher Transactions (PV) ..................................................................................... 4
Vendor Payment Voucher Transactions (P1) ........................................................................11
Quick Voucher Transactions (QV) .........................................................................................12
Recurring Payment Vouchers ...................................................................................................12
Recurring Payment Voucher Table (REPV)...........................................................................13
Payment Voucher Approvals .....................................................................................................16
Printing Payment Vouchers .......................................................................................................16
Expenditure Tables ...................................................................................................................16
Listing of Master Tables ............................................................................................................17
Page 2 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
General
•
Purchasing, expenditures, and disbursements are linked in MMRS/SAAS.
•
Due to the link between purchasing, expenditures, and disbursements, data entry can be
reduced. Data entered on one transaction can be automatically brought to the next
document in the accounting cycle by simply referencing the prior document. In the
MMRS/SAAS system this capability is referred to as a reference facility.
•
MMRS/SAAS has a baseline purchasing system and an extended purchasing system.
Generally, online agencies use the Extended Purchasing Subsystem (EPS), although some
of these agencies use both the baseline purchasing and the Extended Purchasing
Subsystem to satisfy agency procurement requirements.
The baseline purchasing system is discussed within this section of the manual as it is a part
of the baseline system of MMRS/SAAS. The Extended Purchasing Subsystem is detailed in
a separate section of the manual.
•
Encumbered transactions are recorded on purchasing documents; pre-encumbered
transactions are recorded on requisition documents.
•
Non-encumbered transactions are payments for items not requiring a purchase order.
Examples of non-encumbered transactions include rent, telephone, utilities, employee
travel, etc.
•
Payment vouchers are required for all payables resulting from both encumbered and nonencumbered transactions.
•
When a payment voucher is accepted by MMRS/SAAS, a warrant is produced by the
Department of Finance and Administration (DFA). The warrant process is detailed within
this Expenditure Section of the MMRS/SAAS Agency Manual.
Payment Voucher Transactions
•
Payment Vouchers may be entered into MMRS/SAAS either through the Document
Suspense File or within a specific table.
•
Generally, the Document Suspense File is used for payment of claims that are not one-time
expenditures and when payment vouchers are entered within batches.
•
A special Master Table (REPV) is used to enter recurring payment vouchers.
•
There are three available Payment Voucher transactions in the MMRS/SAAS system:
PV
P1
QV
Payment Voucher
Vendor Payment Voucher
Quick Voucher
Page 3 of 20
5610 – SAAS Agency Manual Expenditure Accounting
•
V2 01/20/2014
In addition to these transactions, the following transactions are entered by the Bureau of
Financial Control, DFA, for expenditure functions:
MW
QW
CX
WR
Manual Warrant
Quick Warrant
Cancelled Warrant
Warrant Reconciliation
These transactions are not detailed within this manual as their use is limited to Bureau of
Financial Control. Reference is provided for explanation purposes.
Payment Voucher Transactions (PV)
The Payment Voucher transaction is the most detailed of all the expenditure transactions
available. The PV consists of a header screen and a detailed accounting line screen. The
header screen contains fields for recording seller and buyer information.
Entering a Payment Voucher Transaction
Suspense Screen
Data Entry Instructions
In order to access the appropriate transaction screen, the following data must be entered:
FIELD
Function:
BATCH ID:
DOCUMENT ID:
DESCRIPTION
Key in N for new document.
To enter transactions by the batch, key in the
transaction code, the agency code XXX, and
the batch identification number.
To enter individual documents, key in the
appropriate transaction code (PV for a
Payment Voucher, P1 for a Vendor Payment
Voucher, or a QV for a Quick Voucher), the
agency code XXX, and press the pound key
(#) to initiate the automatic numbering system
or enter the document identification number.
Press ENTER. If entering a single document, the Input Form screen will appear; if entering a
batch, the Batch Form Input Screen will appear.
Page 4 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
Screen 1-Date Entry Instructions
FIELD
PV DATE:
ACCTG PRD (Accounting Period):
BDGT FY (Budget Fiscal Year):
ACTION:
PV TYPE (Payment Voucher Type):
SCH PAY DATE (Scheduled Payment Date):
OFF LIAB ACCT (Off-set Liability):
DESCRIPTION
This date will be entered by the system (the
date the transaction is accepted by the
system is used). If the current date is desired
for the payment voucher, it may be entered;
the system will allow only the current date to
be entered.
The system will automatically enter the
accounting period inferred from the
transaction date. If a different date is
needed, that date may be entered (it cannot
be a future or a closed period) in MMDDYY
format. During the lapse period (July and
August) this field must be entered.
This field will be automatically entered by the
system. During the lapse period (July and
August) this field must be entered.
The system will automatically enter E for new
entry if left blank. To modify, enter M.
This field remains blank.
This field is used only to designate a payment
date that is different from the systemcomputed date.
This field remains blank.
Page 5 of 20
5610 – SAAS Agency Manual Expenditure Accounting
FIELD
DOCUMENT TOTAL:
V2 01/20/2014
DESCRIPTION
Enter the unsigned net amount of all lines on
the document, including the decimal. To
compute this amount:
•
•
•
EFT FLAG (Electronic Funds Transfer):
HIPAA FLAG:
CALC DOC TOTAL (Calculated Document
Total):
VENDOR CODE:
CHECK CATEGORY:
SINGLE CHECK FLAG:
VENDOR NAME/ADDR (Address):
VEND PAYMENT TYPE:
PRIVACY-FLAG:
add the increase amounts together
add the decrease amounts together
subtract the smaller of these amounts
from the larger; enter that amount
Enter a "Y" (Yes) only if funds are to be
electronically transferred by the State
Treasury and no warrant is needed.
Enter a “Y” (Yes) if this is a medical payment
and only if you have claim data to enter on
the HCLM screen.
This field is automatically completed by the
system.
Key in the vendor code XXXXXXXXXXX.
(This is an 11-digit number.)
This field remains blank.
If the invoice or purchase order being paid
consists of 30 or more lines, enter Y to
indicate that a single warrant should be
written for this voucher. If left blank, it will
default to N.
Note: If this field is left blank, defaults to N
(No) and more than one payment voucher is
entered for a single vendor, only one warrant
will be generated for all payment vouchers to
that vendor. If a separate warrant is required
for each payment voucher to the vendor, the
single check flag must be a Y (Yes).
The system will automatically enter these
fields if the vendor is valid in the Vendor
Table (VEND). If it is a miscellaneous vendor
code, then the name and address must be
entered.
This field remains blank.
This field requires entry; it is used to
determine if the vendor address will be
displayed in the public access database for
non-confidential payments. Yes means
vendor address will be displayed. No means
vendor address will NOT be displayed.
Page 6 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
NOTE: The Seller fields are only completed if an intra-governmental transaction is coded; since
this option is not used by the State of Mississippi, these fields will remain blank.
FIELD
SELLER FUND:
SELLER AGENCY:
SELLER ORG (Organization):
SELLER SUB-ORG (Sub-organization):
SELLER APPR UNIT (Appropriation Unit):
SELLER ACTIVITY:
SELLER REV SRC (Seller Revenue Source):
SELLER SUB-REV (Seller Sub-revenue
Source):
SELLER JOB NO (Number):
SELLER REPT CAT (Seller Reporting
Category):
SELLER OBJECT:
SELLER SUB-OBJ (Sub-object):
SELLER OFF REC ACCT (Off-setting
Receivable Account):
SELLER BS ACCT (Balance Sheet Account):
DESCRIPTION
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
This field remains blank.
Press ENTER and Screen 2 appears.
Screen 2 – Data Entry Instructions
Page 7 of 20
5610 – SAAS Agency Manual Expenditure Accounting
FIELD
LN NUMBER (Line Number):
REFERENCE CD (Code):
REFERENCE AGY (Agency:
REFERENCE NUMBER (Reference
Transaction Number):
LN (Reference Line):
COM LN (Commodity Line:
VENDOR INVOICE:
FUND (Fund Number):
AGENCY:
ORG (Organization Code):
SUB ORG (Sub-organization Code):
APPR UNIT (Appropriation Unit):
V2 01/20/2014
DESCRIPTION
Enter a consecutive two-digit number for
each accounting line on the document. No
more than 50 lines should be entered on any
one Payment Voucher.
If this payment voucher is referencing a
transaction entered on a purchasing
document or requisition, enter the code
designating the type of transaction.
If this payment voucher is referencing a
previous transaction, enter the agency code
XXX.
If this payment voucher is referencing a
previous transaction, enter the purchase
order or requisition number referenced by this
payment voucher.
This field is used for items that have been
previously recorded on a purchase order or
travel transaction. Enter the line number of
the item being referenced if applicable. This
field remains blank for items originally
recorded on a requisition.
Enter the purchase order commodity line
being referenced (3 digits) if applicable.
Enter PV (for Payment Voucher), the agency
code XXX, and the actual invoice number. If
there is not an invoice number, enter PV XXX
and the document number (obtained from the
document header). This will allow the system
to group all PVs from the agency together on
the Document Suspense File (SUSF).
If a purchase order or travel transaction was
referenced, this field is inferred. If not, key in
the code of the Fund to be charged for this
payment voucher. The code must be valid in
the FUND Table (FUND).
If a purchase order or travel transaction was
referenced, this field is inferred. If not, enter
the agency code XXX for initial entry.
If a transaction containing an organizational
code was referenced, this field is inferred.
This field may be used for reporting
purposes.
If a transaction containing a suborganizational code was referenced, this field
is inferred. This field may be used for
reporting purposes.
This field defaults from the fund number.
Page 8 of 20
5610 – SAAS Agency Manual Expenditure Accounting
FIELD
ACTIVITY:
LOC:
OBJCT (Object Code):
SUB-OBJ (Sub-object):
REV SRC (Revenue Source):
SUB REV (Sub-revenue):
PROJECT NUMBER:
REPT CATG (Reporting Category):
BS ACCT (Balance Sheet Account):
ACCOUNT NUMBER:
DESCRIPTION:
AMOUNT:
REC DATE:
V2 01/20/2014
DESCRIPTION
If a transaction containing an activity code
was referenced, this field is inferred. This
field may be used for reporting purposes.
This field is used to specify the location of the
goods/services.
Enter the appropriate object code. If a
previous transaction was referenced, this field
is inferred.
This field remains blank.
This field will be used only in rare instances
when a refund of a revenue source must be
paid (i.e., sales tax, revenue refunds for
duplicate payments, specified magazine
subscriptions, etc.).
Leave this field blank unless the revenue
source is coded. The sub-revenue code must
be valid on the Sub-revenue table (SREV).
This field is currently used for extended
project accounting. Until the State of
Mississippi acquires the Job Costing
Subsystem, this field will not be used for its
original intent.
This field may be used for reporting
purposes.
If coding to a balance sheet account, enter
the account code.
This field is used to enter the agency’s
account number with the vendor.
This field may be used to provide additional
information if desired.
NOTE: When paying American Express,
enter the social security number of the
employee in the first nine spaces of this field
(do not include hyphens).
Enter the amount of the item described on
this line. (Enter two digits for cents. Do not
enter dollar signs or commas; decimal points
are not required.)
If this line is a modification to a previous line,
enter the amount of change over (under) the
previous amount. Do not code a sign (+ or -);
the I/D field indicates whether this is to be
added or subtracted from the original amount.
Enter the date you received the
goods/services you are paying for on the PV.
This field is required if you are paying a
minority vendor and during lapse period.
Page 9 of 20
5610 – SAAS Agency Manual Expenditure Accounting
FIELD
I/D (Increase or Decrease):
P/F (Partial or Final Payment:
V2 01/20/2014
DESCRIPTION
This field is used for modifications. Enter I for
Increase or D for Decrease. The field will
default to I when entering a transaction.
Optional for use only when referencing a
purchase order. This field indicates whether
the line is a final payment against the
purchase order. Code this field according to
the following rules:
•
•
P for Partial Payment - The P is
optional.
F for Final Payment (Final payments
do not have to equal the amount on
the purchasing document).
If this payment voucher line makes the total
amount expensed equal to the purchase
document amount, then the purchase order
line will be closed automatically, and the "F"
is optional.
CONTRACT #:
If this payment voucher line makes the total
amount expensed less than the purchase
order amount, but there will be no more
expenses against that purchase order (the
item was less than the purchase order), the
"F" is required.
If this payment voucher line makes the total
amount paid more than the purchase order
amount, the transaction will be rejected.
The contract number is a number (up to 35
characters) used to identify the contract. This
field entry is required if payment is associated
with a contract. The contract must be valid
on the Contract Number Summary Table
(PASM), and the Transparency Flag must be
set to “Y” on the Scanned Contract for
Transparency table (SCTT).
1. If entering documents in a batch, at the end of the last document in the batch tab to the
Function field and enter a QB (for Quick Edit Batch). If entering an individual document, Q
should be performed after entering the data for that document. Read the messages at the
bottom of the screen. If errors are indicated, make the necessary corrections.
Page 10 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
2. To apply approvals to an individual document, tab to the Function field and enter A (for
Approval). The message at the bottom of the screen should read DOCUMENT
APPROVED.
3. To schedule for processing, tab to the Function field and enter E (for end) or F (for finish).
Vendor Payment Voucher Transactions (P1)
The P1 transaction consists of a single data entry screen. This transaction does not contain the
seller fields associated with the Payment Voucher (PV) transaction.
This P1 Payment Voucher does not include the seller fields which appear on the Payment
Voucher (PV) screen. The data entry instructions provided for the Payment Voucher transaction
should be followed for the fields contained on the PV Transaction.
Page 11 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
Quick Voucher Transactions (QV)
The QV transaction contains both a header screen and a detailed accounting line screen. The
fields are the same as the P1.
The Quick Voucher transaction is similar to the Vendor Payment Voucher (P1) since it does not
include the seller fields which appear on the Payment Voucher (PV) screen. The data entry
instructions provided for the Payment Voucher transaction should be followed for the fields
contained on the QV transaction.
Recurring Payment Vouchers
Expenses that occur on a regular or routine basis may be entered into MMRS/SAAS one time
using the Recurring Payment Voucher Table (REPV).
Once the data has been entered in the REPV Table, MMRS/SAAS will automatically generate a
Payment Voucher at set intervals.
The Recurring Payment Voucher can be used for payroll payment vouchers, payment of rent
and utilities, and other payments that occur routinely.
The REPV Table can only be used to enter single transactions. The transactions will be
batched in a process that runs once the recurring payment vouchers have been generated.
Page 12 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
Recurring Payment Voucher Table (REPV)
Data Entry Instructions
FIELD
PV NUMBER:
SUBMIT AGENCY:
FREQ TYPE:
VOUCHER TYPE:
ENTRY START DATE:
ENTRY END DATE:
LATEST DATE:
SCHD PAYMT DATE (Scheduled Payment
Date):
OFF LIAB ACCT (Off-set Liability):
DESCRIPTION
Key in the unique document number (the PV
Number must include nine characters at the
time it is entered; however, when the
Payment Voucher is generated, the system
will append two additional characters).
Enter the agency code (XXX).
Indicate when a payment voucher should be
generated by entering M (Monthly), Q
(Quarterly), B (Bimonthly), or F (one-time in
the Future).
This field remains blank.
Enter the date in MMDDYY format when the
first payment voucher should be generated.
Enter the date in MMDDYY format when the
last payment voucher should be generated. If
the payment voucher frequency was F, this
field remains blank.
This field remains blank. The system will
generate this date when a Payment Voucher
is generated.
This field is used only to designate a payment
date that is different from the systemcomputed date. If this field is entered, it must
be the same or a later date than the entry
start date.
This field remains blank.
Page 13 of 20
5610 – SAAS Agency Manual Expenditure Accounting
FIELD
VENDOR:
CHECK CATEGORY:
SINGLE CHECK FLAG:
VENDOR PAYMENT TYPE:
LI NO (Line Number):
REFERENCE TRANSACTION
CD/AGY/NUMBER/LN:
COMM LN:
VENDOR INVOICE:
FUND (Fund Number):
AGY (Agency):
ORG (Organization Code):
SUB ORG (Sub-organization Code):
APPR UNIT (Appropriation Unit):
ACT:
OBJ (Object Code):
SUB-OBJ (Sub-object):
V2 01/20/2014
DESCRIPTION
Enter the vendor code XXXXXXXXXXX.
(This is an 11-digit number.)
This field remains blank.
If the invoice or purchase order to be paid
consists of 30 or more lines, enter Y to
indicate that a single warrant should be
written. If left blank, it will default to N which
will have the amount added to any other
voucher for the same vendor.
This field remains blank.
Enter a consecutive two-digit number for
each accounting line on the document.
Numbers from 01 to 99 are valid.
If this payment voucher is referencing an
encumbered transaction previously entered,
enter the code designating the type of
purchase order (PC, PD, SC, CS, or PG), the
three-digit agency code, purchase order
number and line number to be paid by the
payment voucher. If this data is unknown,
the fields may remain blank to be completed
later, either in the table or during the
document data maintenance. If the payment
voucher is not referencing a purchase order,
this field remains blank.
This field requires entry if referencing a
Purchase Order. It is the purchasing
document commodity line number to be paid
(a 3-digit number).
Enter PV XXX and the actual invoice number.
If there is not an invoice number, enter PV
XXX and the document number (obtained
from the document header).
Enter the four-digit code of the fund to be
charged for this payment voucher. The code
must be valid in the Fund (FUND) table.
Enter the agency code (XXX) for this entry.
Enter the organization code (XXXX) if
applicable.
This field remains blank.
This field defaults from the fund number.
This field remains blank.
Enter the appropriate five-digit object code.
This field remains blank.
Page 14 of 20
5610 – SAAS Agency Manual Expenditure Accounting
FIELD
REV SRC (Revenue Source):
SUB REV (Sub-revenue):
JOB NUMBER:
REPT CATG (Reporting Category):
BS ACCT (Balance Sheet Account):
DT (Discount Type):
LINE DESCRIPTION:
LINE AMOUNT:
I/D (Increase or Decrease):
P/F (Partial or Final Payment):
LOC CODE:
ACCOUNT NUMBER:
CONTRACT NO:
V2 01/20/2014
DESCRIPTION
This field will be used only in rare instances
when a refund of a revenue source must be
paid (i.e., sales tax, revenue refunds for
duplicate payments, specified magazine
subscriptions, etc.).
Leave this field blank unless the revenue
source is coded. The sub-revenue code must
be valid on the Sub-revenue table (SREV).
Enter the appropriate five-character project
code if applicable.
Enter the appropriate four-character reporting
category code if applicable.
If coding to a balance sheet account, enter
the account code.
This field remains blank.
This field may be used to provide additional
information if desired.
Enter the amount of the item described on
this line (Enter two digits for cents. Do not
enter dollar signs or commas; decimal points
are not required.); OR leave the field blank to
be completed at the time the payment
voucher is generated. If it is left blank, the
system will show "FILL-IN.”
This field is used for modifications. Enter I for
Increase or D for Decrease.
This field is required only when a purchase
order is referenced. The system will
recognize if the payment is a partial payment;
therefore, no entry is needed. Enter F for
final payment only when certain that the
entire purchase has been received.
This field entry is optional. It is used to
specify the location of the goods/services. If
coded, the location code must be valid on the
Agency Location (ALOC) Table.
This field entry is optional. This field is used
to identify the agency’s account number with
the vendor related to the payment voucher.
The contract number is a number (up to 35
characters) used to identify the contract. This
field entry is required if payment is associated
with a contract. The contract must be valid
on the Contract Number Summary Table
(PASM), and Transparency Flag must be set
to “Y” on the Scanned Contract for
Transparency Table (SCTT).
Page 15 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
Tab to Action field and enter A (for add). Then press ENTER.
NOTE: The data entry for this document is now complete. The system will generate the
Payment Voucher on the scheduled date and add it to the Document Suspense File. The
Payment Voucher can be accessed in correction mode for modifications, approvals and
processing.
Payment Voucher Approvals
•
The Payment Voucher transactions have four approval levels.
•
The agency has three approval levels that are required for transaction processing.
•
The Bureau of Financial Control has the fourth level of approval. Once this final level of
approval is applied and the transaction is processed in the nightly processing cycle, a
warrant or EFT is automatically generated by MMRS/SAAS.
Printing Payment Vouchers
•
Payment Vouchers are printed on special forms, generally on the agencies' printer.
•
The Payment Vouchers will print the morning after the nightly processing cycle is completed,
and the transactions contain no errors.
•
Once the Payment Voucher has printed, the required copies must be forwarded to the
Bureau of Financial Control in order for the fourth level of approval to be applied.
Expenditure Tables
MMRS/SAAS links expenditure accounting (payment) with the purchase transaction when
applicable. The tables used for expenditures are the same as those used by the purchasing
module. For example, the vendor tables are used for both purchasing and tracking payments.
Since multiple payments can occur against one purchase order, many of the master tables are
open item tables.
There are several tables within MMRS/SAAS for processing and tracking warrants generated
from the payment voucher transactions. These tables are either system maintained or are used
only by the Bureau of Financial Control. The warrant tables are detailed in the MMRS/SAAS
Online Features Guide and are not included in this Agency Manual.
Page 16 of 20
5610 – SAAS Agency Manual Expenditure Accounting
V2 01/20/2014
Listing of Master Tables
Master Tables that provide baseline purchasing and expenditure information in MMRS/SAAS
are provided below:
TABLE NAME
DISC - Discount Type
Table
EFTT - Electronic Funds
Transfer Table
OPOD - Open Purchase
Orders by Document
Number Table
OPOH - Open Purchase
Order Header Table
OPOL - Open Purchase
Order Line Table
OPPD - Open Purchase
Order Header By
Document Table
DESCRIPTION
This table defines discount
type codes that can be used
on payment vouchers. If a
discount is given by a vendor
for earlier payment within a
specified number of days, the
system will take it into account
and calculate the discount.
This table is used to record
information on vendors who
desire electronic transfer of
funds.
This table contains detail
about all outstanding and
some recently closed baseline
purchase orders in numerical
order of the open items.
This table contains summary
information about all
outstanding and some recently
closed baseline purchase
orders. This table is used to
review outstanding purchase
orders and related vendor
data.
This table contains all detailed
information for all outstanding
and some recently closed
baseline purchase orders.
This table can be used to
access purchase orders by
particular vendors in
sequential order.
This table is an alternate view
of the Open Purchase Order
Header Table (OPPH). The
table lists open purchase
orders by document number
and is used for inquiry
purposes only.
KEY
Discount Type
MAINTAINED
BY
DFA
Vendor Code
DFA
Agency,
Purchase Order
Number, Vendor
System
Vendor Code,
Agency,
Purchase Order
Number
System
Vendor Code,
Agency,
Purchase Order
Number, Line
Number
System
Purchase Order,
Transaction
Code, Agency,
and Vendor
Code
System
Page 17 of 20
5610 – SAAS Agency Manual Expenditure Accounting
TABLE NAME
OPRQ - Open
Requisition Table
OPVD - Open Payment
Voucher Header By
Document Table
OPVH - Open Payment
Voucher Header Table
OPVL - Open Payment
Voucher Line Table
OPVV - Open Payment
Voucher By Vendor
Name Table
PAYW - Outstanding
Payroll Warrant Inquiry
Table
POHD - Purchase Order
Hold Table
PORO - Purchase Order
Rollover Table
V2 01/20/2014
DESCRIPTION
KEY
This table contains all
outstanding purchase
requisition transactions.
This table contains key only
information which exists on the
OPVH (above), rearranged to
have voucher number first and
then vendor code. It provides
a mechanism to scan for a
Payment Voucher if no more
than the Voucher Number is
known.
This table contains summary
information about all
outstanding and some recently
closed Payment Voucher
documents. This table is used
to review outstanding Payment
Vouchers.
This table contains details
about all outstanding and
some recently closed Payment
Voucher (PV) lines. This table
is used to examine details at
the line level of the PV input
form.
This table contains only key
information from the OPVH
(above), rearranged to have
vendor name first. Provides
an alternate view of the OPVD
table and allows scan
capabilities if only the Vendor
Name is known.
This table shows outstanding
payroll warrants and can only
be viewed by employees who
have the proper security
clearance. Used to identify
outstanding payroll warrants.
This table allows an agency to
prevent a baseline purchase
order from being printed.
This table identifies purchase
orders to be rolled to the next
fiscal year.
Agency,
Requisition
Number
Agency,
Voucher
Number, Vendor
MAINTAINED
BY
System
System
Vendor Code,
Agency,
Voucher Number
System
Vendor Code,
Agency,
Voucher
Number, Vendor
Invoice, Line
Number
System
Vendor Name,
Vendor Code,
Agency,
Voucher Number
System
Warrant Number
System
Transaction
Identification
Number
Vendor Code,
Agency,
Purchase Order
Number
Agency
DFA
Page 18 of 20
5610 – SAAS Agency Manual Expenditure Accounting
TABLE NAME
DESCRIPTION
POTX - Purchase Order
Text Table
This table stores text
associated with baseline
purchase order transactions.
PRPO - Printed
Purchase Order Table
This table lists all baseline
purchase orders for which
vendor purchase orders have
been printed and the date
each was printed.
This table provides information
that the system uses to
automatically create Payment
Voucher transactions on a
regular basis. The table
creates payment voucher
transactions at scheduled
intervals for ongoing
payments, such as rent.
This table provides information
that the system uses to
automatically create intragovernmental payment
voucher transactions on a
regular basis.
This table is used in the
automated check writing
process. The table has limited
user access based on security
level. The table allows users
to change the scheduled
payment date of vouchers in
the Open Payment Voucher
Header Table (OPVH). It also
permits a hold to be put on
vouchers and to subsequently
remove the hold and allow
payment.
This table defines the codes
for vendors to which the
agency makes payments. The
table includes vendor names,
addresses, and special
indicators. This table is used
to determine valid Vendor
Codes.
REPV - Recurring
Payment Voucher Table
RPV2 - Intragovernmental Recurring
Payment Voucher Table
SCHD - Voucher
Scheduling Table
VEND - Vendor Table
V2 01/20/2014
KEY
Vendor Number,
Purchase Order
Identification,
Purchase Order
Line Number,
Text Line
Number
Transaction
Identification
MAINTAINED
BY
Agency
System
Payment
Voucher
Number, and
Line Number
Agency
Payment
Voucher Number
and Line
Number
Agency
Vendor Code,
Agency, and
Voucher Number
DFA
Vendor Code
DFA
Page 19 of 20
5610 – SAAS Agency Manual Expenditure Accounting
TABLE NAME
VFED - Vendor Federal
Identification Table
VNAM - Vendor Name
Table
WREC/WRE2 - Warrant
Reconciliation Table
(Screen 1 and 2)
WSUM - Warrant
Summary Table
DESCRIPTION
This table is an alternate view
of the Vendor Table with the
vendor's federal identification
number displayed.
This table provides only the
vendor name and number in
alphabetical order. It is an
alternate view of the Vendor
Table (VEND) and is used to
determine Vendor Codes.
This table provides a listing of
warrants which have been
issued and the status of those
warrants. The status can be
Cleared, Paid, Registered,
Voided, or Unredeemed.
This table provides summary
totals of all warrants which
have cleared the State
Treasury.
V2 01/20/2014
KEY
Federal
Identification
Number and
Vendor Code
Vendor Name,
Vendor Code
MAINTAINED
BY
System
DFA
Bank Account
Code, Warrant
Number, Fund
DFA
Bank Account
Code, Date,
Fund
DFA
Page 20 of 20