Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
86 Cards in this Set
- Front
- Back
a type of report that breaks down marginal profit
contributions by territory, customer, or other basis |
profitability analysis
|
|
an arrangement for customers to send their electronic
payments directly to the bank, which then reports on the amounts remitted |
electronic lockbox
|
|
a legal contract that defines responsibility for the goods in
transit |
bill of lading
|
|
a turnaround document used in the billing and collection
process |
remittance advice
|
|
the billing method used when customers pay according to
each invoice |
open invoice
|
|
a document listing the quantity and description of each item
ordered that is included with a shipment |
packing slip
|
|
when there is insufficient inventory on hand to fill an order,
this is created |
backorder
|
|
a list of names and amounts of all customer payments often
compiled in the mailroom and sent to the AR department |
remittance list
|
|
the use of EDI tby a manufacturer to manage a retail
customer's inventory |
VMI
|
|
a document that provides precise estimates of cash inflows
and outflows |
cash budget
|
|
a document that authorizes the crediting of a customer's
account for returns or adjustments |
credit memo
|
|
a list of items (and quantities of each) that a customer
ordered, used to release merchandise to the shipping department |
picking slip
|
|
the basic document created in the billing process used to
notify customers of the amount due, etc. |
sales invoice
|
|
a set of business activities associated with providing goods
and services to customers and collecting cash in payment |
revenue cycle
|
|
documentation of a request for goods and services by a
customer |
sales order
|
|
the billing method in which customers are billed in subsets
staggered over time |
cycle biling
|
|
direct electronic payments to or from banks
|
EFT
|
|
the billing method used when customers pay a monthly
statement |
balance forward
|
|
a report that lists customer accounts receivable balances by
the length of time they have been outstanding |
aging schedule
|
|
a maximum allowable account balance for each customer
based on their ability to pay |
credit limit
|
|
a database separate from the company's live database
that contains a large amount of data used for analysis |
data warehouse
|
|
the part of a graph that generally should be set to zero
in order to present a clear picture of the data relationships being depicted |
vertical axis
|
|
a form that is often used to document journal entries to
be entered in the general journal |
journal voucher
|
|
the use of sophisticated statistical analysis of company
data to discover previously unsuspected relationships among stored data items |
data mining
|
|
this depicts the path of a transaction through the
accounting system and can be used to trace all changes made to the general ledger |
audit trail
|
|
an input edit used to verify that an entry that must be a
negative number is indeed negative |
sign check
|
|
input edits used to verify that total debits equal total
credits in a journal entry |
zero balance check
|
|
reporting financial results on the basis of managerial
responsibilities within an organization |
responsibility accounting
|
|
the use of data in data warehouses to support strategic
decision-making |
business intelligence
|
|
a report that lists the balances for all general ledger
accounts at a particular point in time |
trial balance
|
|
an input edit used to ensure that a field contains only
numeric data |
field check
|
|
a report that provides a four dimensional perspective of
organizational performance., including innovation and learning |
balanced scorecard
|
|
an input edit used to verify that all required data has
been entered |
completeness test
|
|
a database separate from the company's live database
(and usually smaller) that contains data used for analysis of one of the company's specific functions - often for marketing |
datamart
|
|
the markup language that is a form of XML and is
increasingly used to store and report information for accounting and business reporting |
xbrl
|
|
the process of defining a database so that is faithfully
represents all aspects of the organization |
data modeling
|
|
a special type or format of ER diagram originally
developed specifically for use in designing AIS |
REA data model
|
|
this exists when the maximum cardinality for both entities
in a relationship |
many to one relationship
|
|
this exists when the maximum cardinality of one entiry in
the relationship is 1 and the maximum cardinality for the other entity in that relationship is "many" (M or N) |
one to many relationship
|
|
this describes the part of the cardinality between two
entities that indicates whether a relationship between those two entities is optional or mandatory |
minimum cardinality
|
|
the step in the database design process in which the
finished data model is used to guide the participants |
physical design
|
|
entities representing those things owned or used by an
organization that have economic value to the organization |
resources
|
|
descriptions of the nature of the relationship between two
entities that indicate how many instances (records) of one entity can be linked to each specific instance (record) of another entity |
cardinalities
|
|
this exists when the maximum cardinality for each entity in
that relationship is 1. |
one to one relationshps
|
|
this describes the part of the cardinality between two
entities that indicates whether each instance (record) of one entity can be linked to only one or more than one instance (record) of the other entity in the relationship |
max cardinality
|
|
anything about which an organization wants to collect and
store information |
entity
|
|
the REA model serves as a source of ___________ about
an organization's business activities in addition to its use in designing AIS |
documentation
|
|
the people and organizations that participate in events and
about whom information is desired for planning, control and evaluation purposes |
agents
|
|
one of the steps in the database design process in which
data modeling occurs |
conceptual design
|
|
a graaphical technique for portraying a data-base schema
or logical model |
ERD diagram
|
|
the various business activities about which management
wants to collect information for planning or control purposes |
events
|
|
the number of tables needed to implement an REA
data model that has seven distinct entities, three M:N relationships and five 1:N relationships in a relational database |
ten
|
|
in the data modeling process, one of these is
created for each M:N relationship identified in the REA diagram |
relationship table
|
|
an attribute appearing in one table that is itself the
primary key of another table, and is used to link tables in a database |
foreign key
|
|
one of two names that refer to the primary key
when it is made up of more than one attribute(field), and is a "multiple-attribute" primary key |
composite primary key
|
|
this is an alternate name for a relationship table and
represents a connection between two tables that have a M:N relationship in an REA diagram |
junction table
|
|
this is a synonym for fields - each of which
represents an attribute or characteristic of the data gathered in a database table for a particular entity in an REA data model |
attributes
|
|
one of two names that refer to the primary key
when it is made up of more than one attribute(field), and is a "multiple-attribute" primary key |
concatenated keys
|
|
a table attribute that is used to uniquely identify
each record in that table |
primary keys
|
|
this type of entity is used in an REA database to
store information traditionally found in journals |
event
|
|
these are used to create journals and ledgers from
a completed relational database that was designed using a REA data model |
queries
|
|
in the data modeling process, one of these is
created for each distinct entity identified in the REA diagram |
table
|
|
the group of executive level people who
oversee an information systems development effort |
steering committee
|
|
the building and testing of a new IT
system |
implemenation
|
|
ignoring a new system in the hope that it
will go away |
avoidance
|
|
the actual switch from using an old
system to using a newly completed system |
conversion
|
|
systems development life cycle
|
SDLC
|
|
the shortest time in which a project can be
completed is calculated using this |
critical path
|
|
the logical or conceptual design for the
processes/programs to be included in a new system - documented with data flow diagrams |
logical process model
|
|
a long-range (3 year or less) planning
document that specifies where the AIS is headed in terms of planned projects |
master plan
|
|
the program evaluation and review
technique used in project planning and management |
PERT
|
|
behavior that is usually intended to
destroy or weaken a system's effectiveness |
aggression
|
|
one method used to determine financial
feasibility in which all estimated future cash flows from potential projects are discounted back to the present and then used to compare the potential comparative value of each project |
NPV Method
|
|
the type of maintenance activity carried
out to fix system problems |
corrective maintenance
|
|
the logical or conceptual design for a
database - documented with ER or REA diagrams |
logical data model
|
|
the effective interest rate that results in a
net present value of 0 for a project when all of the project's estimated future cash flows are discounted back to the present |
internal rate of return
|
|
the stages and activities involved in
building an IT system |
system development life cycle
|
|
the longest path through a PERT chart
|
critical path
|
|
the specifications that will be needed to
translate a conceptual design into an actual system |
physcial design
|
|
the number of years required for the net
savings from an investment to equal its initial cost |
payback period
|
|
a person who studies existing systems,
designs new ones, and prepares specifications that are used by programmers in the development process |
system analyst
|
|
the type of maintenance activity that
makes the system faster or better in some way |
perfective maintenance
|
|
the development of specifications for the
data and processes to be included in a new system |
conceptual design
|
|
the gathering of information needed to
purchase or develop a new system |
system analysis
|
|
blaming a new system for any and every
unpleasant occurance (related to the system or not) |
projection
|
|
a graphical depiction of project plans
using horizontal bars to represent system activities |
gantt chart
|