Book 1

Req. No.
Module
1 Accounting Close
2 Accounting Close
3 Accounting Close
4 Accounting Close
5 Accounting Close
6 Accounting Close
7 Accounting Segment Setup
14 AI
15 AI
16 Allocations
17 Allocations
18 Allocations
19 Allocations
20 Allocations
21 AP
22 AP
23 AP
24 AP
25 AP
26 AP
27 AP
28 AP
29 AP
30 AP
31 AP
32 AP
33 AP
34 AP
35 AP
36 AP
37 AP
38 AP
39 AP
40 AP
41 AP
42 AP
43 AP
44 AP
45 AP
46 AP
47 AP
48 AP
49 AP
50 AP
51 AP
52 AP
53 AP
54 AP
55 AP
56 AP
57 AP
58 AP
59 AP
60 AP
61 AP
62 AP
63 AP
64 AP
65 AP
66 AP
67 AP
68 AP
69 AP
70 AP
71 AP
72 AP
73 AP
74 AP
75 AP
76 AP
77 AP
78 AP
79 AP
80 AP
81 AP
82 AP
83 AR
84 AR
85 AR
86 AR
87 AR
88 AR
89 AR
90 AR
91 AR
92 AR
93 AR
94 AR
95 AR
96 AR
97 AR
98 AR
99 AR
100 AR
101 AR
102 AR
103 AR
104 AR
105 AR
106 AR
107 AR
108 AR
109 AR
110 Billing
111 Billing
112 Billing
113 Billing
114 Billing
115 Billing
116 Billing
117 Billing
118 Billing
119 Billing
120 Billing
121 Billing
122 Billing
123 Billing
124 Billing
125 Billing
126 Billing
127 Billing
128 Billing
129 Billing
130 Billing
131 Billing
132 Billing
133 Billing
134 Billing
135 Billing
136 Billing
137 Billing
138 Billing
139 Billing
140 Billing
141 Billing
142 Billing
143 Billing
144 Billing
145 Billing
146 Billing
147 Billing
148 Billing
149 Billing
150 Billing
151 Billing
152 Billing
153 Billing
154 Billing
155 Billing
156 Billing
157 Billing
158 Billing
159 Billing
160 Billing
161 Billing
162 Billing
163 Billing
164 Billing
165 Billing
166 Billing
167 Billing
168 Billing
169 Budget & Forecasting














CAPEX
Budgeting
242
&
Management
CAPEX
Budgeting
243
&
Management
CAPEX
Budgeting
244
&
Management
CAPEX
Budgeting
245
&
Management
246 Collections
247 Collections
248 Collections
249 Collections
250 Collections
251 Collections
252 Collections
253 Collections
254 Collections
255 Collections
256 Collections
257 Collections
258 Collections
259 Collections
260 Collections
261 Eliminations
262 Financial Consolidations
269 Fixed Asset

270 Fixed Asset
271 Fixed Asset
272 Fixed Asset
273 Fixed Asset
274 Fixed Asset
275 Fixed Asset
276 Fixed Asset
277 Fixed Asset
278 Fixed Asset
279 Fixed Asset
280 Fixed Asset
281 Fixed Asset

282 Fixed Asset
283 Fixed Asset
284 Fixed Asset
285 Fixed Asset
286 Fixed Asset
287 Fixed Asset
288 Fixed Asset
289 Fixed Asset

290 Fixed Asset
291 Fixed Asset
292 Fixed Assets Processing

300 GL
301 GL
302 GL
303 GL
304 GL
305 GL
306 GL
307 GL
308 GL
309 GL
310 GL
311 GL
312 GL
313 GL
314 GL
315 GL
316 GL
317 GL
318 GL
319 GL
320 GL
321 GL
322 GL
323 GL
324 GL
325 GL
326 GL
327 GL
328 GL
329 GL
330 GL
331 GL
332 GL
333 GL/TAX
334 GL/TAX
335 GL/TAX
336 GL/TAX
337 Intercompany
338 Intercompany
339 Intercompany
340 Intercompany
341 Intercompany
342 Intercompany
343 Intercompany
344 Intercompany
345 Intercompany
346 Intercompany
347 Lease Accounting
348 Payroll
349 Payroll
350 Payroll
351 Payroll
352 Payroll
353 Payroll
354 Payroll
355 Payroll
356 Payroll
357 Payroll
358 Payroll
359 Payroll
360 Payroll
361 Payroll
362 Payroll
363 Payroll
364 Payroll
365 Payroll
366 Payroll
367 Payroll
368 Payroll
369 Payroll
370 Payroll
371 Payroll
372 Payroll
373 Payroll
374 Payroll
375 Payroll
376 Payroll
377 Payroll
378 Payroll
379 Payroll
380 Payroll
381 Payroll
382 Payroll
383 Payroll
384 Payroll
385 Payroll
386 Payroll
387 Payroll
388 Payroll
389 Payroll
390 Payroll
391 Payroll
392 Payroll
393 Payroll
394 Payroll
395 Payroll
396 Payroll
397 Payroll
398 Payroll
399 Procurement Contracts


411 Project Accounting
412 Project Billing
413 Project Billing
414 Project Billing
415 Project Forecasting & Budgeting
421 Purchasing
422 Purchasing
423 Purchasing
424 Purchasing
425 Purchasing
426 Purchasing
427 Purchasing
428 Purchasing
429 Purchasing
430 Purchasing
431 Purchasing
432 Purchasing
433 Purchasing
434 Purchasing
435 Purchasing
436 Purchasing
437 Purchasing
438 Purchasing
439 Purchasing
440 Purchasing
441 Purchasing
442 Revenue Recognition




468 Sales Commission


473 Tax
474 Tax
475 Tax
476 Tax
477 Tax
478 Tax
479 Tax
480 Tax
481 Tax
482 Tax
483 Tax
484 Tax
485 Tax
486 Tax
487 Tax
488 Tax
489 Tax
490 Vendor Contracts


Requirement
System shall provide the ability to create & track financial close process tasks/assignments through completion using workflow.
Ability to track by business day, due date, etc.
System shall have the ability to provide the functionality to create an approval rule to ensure that a manager has reviewed and
approved the journal entry before it is posted.
System shall have the ability to provide the functionality to support a global close calendar.
System shall have the ability to support transactions posted to one standardized, global COA and then mapped to a local cost
center.
System shall have the ability to provide built in data mass loading template.
System shall have the ability to flag GL level actuals/historical transactions as EBITDA add backs.
System shall have the ability to provide the functionality to have a global system to centrally manage legal entities by country.
System shall provide GL staff the ability to designate each general ledger account accounting segment by a user-definable
"account type" as follows in order to prepare lead schedules:
a. Asset Account
b. Liability Account
c. Equity Account
d. Budget Account
e. Revenue Account
f. Project Account
g. Expense and expenditure account
The System shall have the ability to automaticlally distinguish/identify journal entries in to specific categorties for reporting
purposes (e.g. Local/country reporting vs. US GAAP/Corporate).
System shall provide the ability to code Investment Account transactions as either 'unrealized gain' or 'unrealized loss' in order
generate certain SEC reports.
System shall provide the ability to code whether Purchase orders, invoices, and associated transactions are "pre-paid" for the
purposes of expense reporting
System shall provide the ability to code an 'Account' Accounting segment/business object as "allocation account" vs "non-
allocation account" for the purposes of expense reporting
System shall have the ability to automaticlally distinguish/identify journal entries in to specific categorties for reporting purposes
(e.g. Local/country reporting vs. US GAAP/Corporate).
System shall have the ability to automate cash allocation based patterns from the past.
System shall have the ability for auto-billing for re-curring revenue.
System shall have the ability to support Rule based automated allocations across COA segments and within a specific COA
segment (Cost Center, GL Account, etc.)
System shall have the ability to support Rule based allocations across GL periods that are open.
System shall have the ability to support allocations centrally.
System shall have the ability to support allocations across COA (LE, segments, etc.)
System shall have the ability to support various vacation rules. Need to feed vacation accruals from HCM to ERP.
System shall provide AP Admin staff the ability to create and maintain an enterprise wide, vendor master file which interfaces w
other ERP modules, in order to allow auto-population of vendor data into payment ledger entries.
System shall allow a designated system Admin user to add, update, and delete vendor master data.
Vendors can be created in bulk.

System shall provide a designated Admin user the ability to block a vendor in order to prevent transactions from being made wi
that vendor.
(e.g. the master record is available in the system, but no transaction can be posted to that vendor, and vendor is not allow to
further supply materials until the block is removed)
System shall have the ability to easily link the vendor invoice, the purchase order, and the receiving report (goods receipt) to all
unified purchase order, invoice, and goods receipt data in all relevant ledger entries and reports.
System shall provide user the ability to setup invoice matching tolerances (upper & lower) in order to enforce the following, at a
minimum,
a) Invoices that match the details on the purchase order for the price and quantity should be automatically released for paymen
IF match tolerance is met.
b) Invoices that do not match the details on purchase order (according to tolerances) for the price and quantity should be
automatically blocked from payment.
System shall provide AP Manager the ability to manually remove the payment block (unblock) when discrepancy (ies) with vend
have been resolved in order to release the invoice for payment (for cases where the invoice and/or good receipt did not fall with
the PO matching tolerance)
System shall provide AP staff or the Vendor the ability to scan the invoice using OCR (optical character reader) and have an
invoice record created automatically as a payable in the Invoice Ledger in ERP
System shall allow AP user to enter invoices in the AP system that are to be paid via Credit Card
System shall provide AP staf the ability to import accounts payable invoices in bulk, including fixed assets (e.g., from a
spreadsheet such as excel) in order to allow AP staff to post a large quantity or group of invoice transactions simultaneously to
ledgers.
System shall provide an AP staff the ablity to flag an invoice as 'fixed asset' in order to auto generate an asset card when invoic
is posted to AP Ledger
System shall provide the ability to create an intuitive PO/Invoice Approval workflow, including designated Approvers, in order to
allow purchase orders and invoices to be automatically routed through the workflow to be approved.
Workflow approvers must include the invoice/Purchase Order initiator and at least one level of approval
i.e:
a. Invoice/PO Initiator
b. Initiator's Manager
System shall allow user in the approval workflow hierarchy to add notes to the Purchase order even though the PO/Invoice
amount execeds their approval threshold
System shall provide an AP Manager the ability to assign backup approvers to each assigned approver in all of the AP approva
workflows (PO approval, invoice approval, credit card transaction approval), in order to allow approval coverage when the
assigned approver is not in office.
The backup approver will have the same approval capabilties as the assigned approver.
When the Requester (the staff member who submitted a PO, Invoice, or Credit Card Authorization Request) gets their
PO/Invoice/Credit Card Transaction approved at each dollar threshold approval tier, the system shall immediately notify the
Buyer's entire chain of management that the Buyer's item was approved.
System shall provide the ability to create a staff hierarchy that lists the employee's complete management chain, in order for the
ERP to send notifications to the employee's management chain (ex - AP Invoice Approvals, etc)
System shall provide a Purchase Order Approval work area that allows AP managers authorized to approve Purchase Orders to
view all pending purchase orders needing their approval.
System shall allow the AP manager to set thresholds for Purchase Order approvals, in order to allow efficient & fast approvals o
Purchase Orders of any amount that are entered into the system.
System shall provide the ability to set up approval workflows for credit card transactions, in order to allow Payable Staff Approve
to quickly approve credit card purchases that need to be made, at user-defined dollar amount thresholds.
System shall allow AP managers to set thresholds for corporate credit card transaction authorizations, in order to allow efficient
fast authorizations of all credit card transactions.
System shall allow all transactions (e.g. invoice, purchase order, and credit cards) requiring approval to be mobile accessible.
System to provide the Approver the ability to review the invoice/PO or credit card transaction via a mobile device or email befor
clicking the Approve or Reject button.
System shall have the ability to auto-populate General Ledger for Expense entries with PO and Invoice information at the time
when Purchase orders and Invoices are approved (via the approvals process).
System shall allow an AP staff to set default Organizational Codes for recurring payables in order to auto-populate those codes
every corresponding payable ledger entry.
(Org Codes = Project, Dept, Business Unit, etc.)
System shall allow an AP staff to set payment dates for recurring payables in order to automatically release the payment to the
vendor at the pre-defined date.
System shall allow AP staff to set a Number of Payment Days for specified invoice dollar amount thresholds, in order to allow a
payable to be released automatically to the vendor on the pre-set date if that payable is under the corresponding dollar amount
threshold.
System shall provide GL staff the ability to configure general ledger, fixed asset ledger, and vendor ledger in a way that allows A
staff to specify if unit cost should or shouldn't include tax in ledger posting, based on data entry of the AP invoice
System shall have the ability to automatically determine if a posted credit memo needs to be issued as a refund (for cases whe
the Customer is no longer actively billing and where there is an aged credit balance over a number of months since the posting
date of the last invoice) and to automatically post debit to customer card, credit to vendor card, & debit to open (negative) credi
balance – with ability to review all refunds prior to posting (and either reject or approve)
System shall provide user the ability to select any aged credit balance from the General Ledger for a customer and auto-post a
corresponding refund to the customer account.
System shall allow AP staff to set up only one vendor instance to use for issuing refunds.
System shall have the ability to post a refund directly to a Customer Account
the Customer has no invoices remaining to be sent & where credit balance is >= 6 months old), and the ability to automatically
post a corresponding vendor debit memo and refund payable to the customer account
ERP GL should provide the ability for a user to post a refund directly to a Customer Account (along with refund type =
ach/check/or credit card)
System shall have Ledger controls to detect and prevent posting of duplicate invoice, duplicate payments and duplicate refunds
System shall provide a Travel Expense module to allow users to manage end-to-end travel expenses including but not limited to
booking of travel to payment/reimbursement of expenses.
When an AP staff enters an invoice in the GL for a payable where a down-payment has been made to the vendor, then the syst
shalll notify the AP staff that the $ amount/down payment was made, and give ability to deduct the down payment from the invo
balance due.
System shall allow AP staff to generate and print accounts payable checks on demand
System shall have the ability to consolidate multiple invoices for the same vendor on one check, and itemize the invoices (invoi
numbers) on the remittance advice.
(e.g. useful if you send your supplier one payment to cover multiple invoices. When you record the payment, you can also
produce a remittance advice, which you can then send to your supplier to let them know which invoices you’re paying.)
System shall provide AP staff the ability to print accounts payable checks in foreign language and in foreign currency
(e.g., helpful for foreign entities that have different currency and language)
System to maintain the following languages, at a minimum:

a. English
b. French
c. German
e. Spanish
System shall provide AP staff the ability to void checks by check number or by group of check numbers.
(e.g., ability to a perform mass void)

System shall provide AP staff the ability to capture the reissue reason for a check based upon a drop down menu of reasons (e
canceled check, lost, etc.).
Ie user enters a check re-issuance, and selects a re-issuance reason from a drop down list, and the reason is saved wit the
payment entry.
System shall have the ability to support different payment types (Check, ACH/EFT, Credit Card, Wires, etc..) in order to allow K
to pay each vendor according to pre-defined payment routes
System shall provide the ability for vendor to set up their account (ach and routing) info via the portal
System shall provide AP staff the ability to maintain terms of payment offered by a vendor in order to take advantage of invoice
discounts when payment is made within certain time frames from the invoice date
System shall allow for Payment by credit card directly from the AP system
The system shall have the ability to auto-post check payments from the corresponding tax expense ledger entry, in order to allo
AP staff to issue electronic checks for all tax payments: regular State/Federal, Income, States Sales & Use Tax, Annual Busines
License Taxes, use tax
System shall provide AP staff the ability to post pre-paid taxes to the appropriate balance sheet account
When an AP payment is made via ach, echeck, or wire (and the corresponding payment remittiance is sent from the Bank to the
ERP using the Bank Interface), the system shall auto-post the payment information in order to auto-update the correspoinding
inovice/PO as "paid"
System shall have the ability to auto-post (and manually post) all vendor payment transactions with the specific locality where th
transaction originated – locality should include country, state, city, etc
System shall have a vendor portal that allows 2-way communication between ERP and vendors in order to perform the followin
at a minimum:
a) vendors to be able to submit invoices (and other docs)
b) vendors to be able to view outstanding invoices
c) vendors to be able to view payment status
d) portal to provide real time payment information
e)allow ERP users to request invoices (and other docs) from vendor
System shall have the ability to integrate with the KLD email system in order to allow any incoming electronic mail from outside
the organization to be routed to a shared inbox where authorized users can retrieve messages from the queue.
(e.g. AP invoices sent by vendors)
System shall have the ability for approval of invoices locally based on org hieararchy within cost center.
System shall have the ability to have one global AP processing Inbox to be used as an imaged invoice repository.
System shall have the ability to have OCR capability built into the ERP.
System shall have the ability to triage and assign invoices to AP processors.
System shall have the ability to default to invoice requestor's information from HCM based on the employee's accounting string
System shall have the ability to recognize predermined rules for routing to duplicate approvers (i.e skip approver and move on t
next level approver).
System shall have the ability to pay foreign vendor from the US to a foregin country in ACH (preferred) or by wire.
System shall have the ability to receive and flag an FA invoice and automatically feed into FA sub-ledger.
System shall have the ability to allow for local payment approval but centralized payment processing.
System shall have the ability to provide the funcationality to support purchase categories must be available.
System shall have the ability to support PO invoices that have values default to the PO when the invoice is created.
System shall have the ability to provide the functionality that recognizes if a Journal Entry or a transaction has an incorect codin
The system should have the ability to FAIL or not accept information and route the entry to an error suspense account for furthe
review.
System shall provide the ability to provide tolerance for PO matching.
System shall provide the user the ability to ensure that sales and use tax are being captured separtely/accurately on the Vendo
invoice.
System shall have the ability to calculate invoice amounts for approval based on Sales Tax setting but the user shall have the
ability to enter net amount of Sales Tax.
The system shall allow that when an inovice is matched to a PO, the matching (and associated Tolerence Threshold) shall be n
of VAT amount
System shall provide the ability to create and maintain an enterprise wide, customer master file which interfaces with other ERP
modules, in order to allow auto-population of customer data into payment ledger entries.
System shall provide the ability to create and maintain an enterprise wide, product master file which interfaces with other ERP
modules, in order to provide a single view of products across the enterprise and to distribute this master information to all
operational and analytical applications.
System shall allow a designated system Admin user to add, update, and delete customer master data.
Customers can be created in bulk.

The Customer Master should have the ability to specify the customer’s country (Spain, Germany, UK and France, US) in order t
send customer invoices according to locality requirements (language, currency, etc).
System shall allow user to upload credit memos from Excel via a user interface.
System shall allow the end user to configure the revenue and tax allocation account numbers where a credit memo is allocated
(after being either uploaded through an Excel interface or received via a data feed from the CRM interface - or created manuall
System shall prevent posting of duplicate credit memos.

System shall have the ability to link the Sales Order to the customer invoice, in order to see invoice payments for each sales
order.
The AR/billing module shall allow internal users to issue refunds to customers using a billing method established for that custom
(credit card, ach), by entering the refund amount and type - from the customer's available configurations for 'type' (credit
card/ach/echeck).
System shall provide AR staff the ability to build customizable invoice templates based on the product(s)/Brands for which the
customer is being billed.
System shall have the ability to determine sales tax/VAT collectability at the customer level.
System shall have the ability to support different payment types (Check, ACH/EFT, Credit Card, Direct Debit, Wires, etc..) in ord
to allow KLD to receive and auto-post payment from each customer according to pre-defined payment routes (where 'payment
route' is a pre-established connection to a customer's bank/payment interface).
System shall have the ability to re-apply customer payments made in AR /Customer payment system
System shall provide the ability to configure the customer in KLD Bank/Customer Bank, in order to receive ACH/Wire, and Direc
Debit payments from the customer’s country (Spain, Germany, UK and France, US)
System shall provide a bank Reconciliations module which processes bank transactions (from external banks) and the
corresponding GL transactions in order to generate the Variance Report.
System shall have the ability to capture customer Down Payments (through the customer payment interfaces) so that when the
payment is received by the ERP GL, it is stored as a Down Payment to the Customer Account.
When the ERP GL receives an invoice for a customer bill, the System shall automatically detect that the customer has a Down
Payment and apply the down payment (portion that matches the billed amount due) to the invoice, in order to generate the data
feed with the adjustment amount due.
System shall have the the ability to apply multiple customer payments against a single invoice, in order to allow installment
payments.
When an AR payment is received via ach, echeck, or wire (and the corresponding payment remittiance is received from the Ban
to the ERP using the Bank Interface), the system shall auto-post the payment information in order to auto-update the
correspoinding inovice as "paid"
System shall have the ability to auto-post (and manually post) all customer payment transactions with the specific locality where
the transaction originated – locality should include country, state, city, etc
System shall have the ability to receive an invoice and send a receipt acknowledgement.
System shall have the ability to book transactions on multiple currency by country.
System shall provide the ability to transact in multiple currencies out of the same ledger and/or LE.
System shall provide the ability for all the Alloc8 features.
System shall provide the ability to identify tolerance account to automatically book variances of a certain threshold left on the
invoice.
System shall provide the ability to provide predictive learning.
System shall have ability to access invoices and customers to submit invoices via mobile devices.
System shall provide users with the ability to do any or all of the following in one step:
1) Generate open invoices
2) Generate current dunning letter (letter applicable to current days late on invoice)
3) Send both to customer / vendors
(e.g., hit one button and dunning info and open invoices are sent to customer)
System shall provide the ability to validate field values within the invoice entry screen prior to posting to avoid coding errors.
e.g., Source of coding errors include:

a) Negative discounts being entered
b) Carriage return / data entered in wrong place causing incorrect posting
c) Escalation or price increase errors (current month compared to previous month)
System shall not allow user to bill/post a payment for any desired period: past, current, or future, even when accounting period
closed.
System shall have a Customer portal that allows for Bill presentment and payment processing.
System shall provide multiple options for the way to send customer invoices, including:
- having multiple recipients
- ability to send via e-mail
- ability to print (in order to mail)
- customer portal
- ability to set a preferred method (usually email)
System shall provide Billing staff the ability to maintain KLD terms of payment which consist of payment discounts extended to
customers for certain payment dates (e.g., if customer makes a payment within 10 days of invoice date - 5% discount, or within
days - 2% discount, net due 30 days)
System shall have the ability to show payment terms on invoice with corresponding dollar amount due.
Example:
a) 5% discount if paid in full within 10 days - Net due amount $475
b) 2% discount if paid in full within 20 days - Net due amount $490
c) net due 30 days or full payment - $500
System shall allow the business user (Contracts or Billing/Collections) to specify the text to appear on a customer invoice
containing a price escalation.
The system should allow the user to set this text to be the same for all invoices, or different for any invoices (completely flexible
System shall automatically apply user-defined Escalation invoice text to the invoice when the ERP receives information from the
CRM interface that a specific invoice contains a price escalation.
System shall have the ability to post the correct variable credit card fee rate for the corresponding customer payment (received
from Billing System interface)
Example, customer pays with Amex 1.7%, Billing System sends 1.7% to ERP, ERP posts 1.7%, etc.
System shall provide Billing staff the ability to capture critical customer information including email address, key contact
information, etc… , in order to auto-populate that data across all segments which need customer data (invoices, etc).
System shall provide Billing staff the ability to assign customer to a Corporate region, Collections Staff Memeber, and one or mo
GL companies.
System shall provide an Admin user the ability to flag a customer as 'inactive', in order to prevent future billing or any other
customer-related system processes.
System shall provide Billing staff the ability to establish parent child relationships between customers, in order to bill to parent
entitites, report on parent entities - etc.
System shall have the ability to create invoice lines based on details received from the interface to the 3rd party CRM.
System shall have the ability to support invoice creation and presentment in multiple languages (spanish, French and German a
least) in order to allow a customer to receive their bill in their local language.
For cases where an approved invoice subsequently has a dollar amount adjusted, a notification should be sent to all invoice
approvers, and there should be the ability to re-route the invoice back through the approval workflow.
System shall have the ability to support manual payment application
ie - capturing a manual check or otherwise entering a payment manually for any reason
System shall have the ability to seamlessly import lockbox files and apply payments based on various matching rules that ensu
there is a customer/invoice match before posting the payment.
Matching Rules:
a) If customer provides an Account # and an Invoice #, the system will check to ensure invoice goes with that account. If not po
an error msg
b) System will post to Invoice #'s only or to Account #'s only.

The System's payment application shall be PCI compliant
(e.g., set of security standards designed to ensure that companies that accept, process, store or transmit credit card information
maintain a secure environment.)
The payment application shall be SEPA compliant
(i.e the new format for cross-border Euro bank transfers).
System shall have the ability to suppress dunning letter generation at the customer level
System shall have the ability to trigger email notifications to the customer based on user-entered collection activities for the
customer (e.g., customer's promise to pay by a certain date should send an email notification to customer confirming that paym
is expected on stated date. etc..)
System shall have an Internal Customer Work Area that provides the ability for business users to capture and centrally store an
details about a customer in order create customer profiles (where a 'profile' is the Master data plus any other customer
data/interaction).
e.g. Ability to capture conversations and other interactions with customer via customer portal, email, phone call, collections issu
etc.
The system's localization packges shall allow users to view ERP screens in local language (while the data entered is on the
original form)
System shall allow customer to view and update their own customer information via a centralized customer portal (e.g. custome
personal info, address, email etc.)
System shall allow customers to access the customer portal to view invoices, dunning letter, statements, and to request
invoice/billing adjustments
System shall provide the ability for customer to effect payment on open invoices (e.g., Credit Card, ACH, Direct Debit for UK
clients and European entities) via a centralized customer portal
System shall provide the ability to automatically send email notifications to customers about expiring or declined credit cards via
centralized customer portal
System shall allow an administrator to send mass email communication to customers or group of customers
System should allow for easy credit/rebill adjustments that do not require 10 approvals or too much manual processing. Ie. An
invoice is selected to be credited, immediately following a clone is created and can be edited to get to the rebill amount.
System should allow for easy credits that do not require total manual entry. Ie. Collector chooses (clicks) the invoice to credit, e
the amount if applicable, and sends for approval. Approver reviews data and posts. All should be done without having to worry
about G/Ls because that should be handled on the backend.
System should allow for easy cloning of invoices in the event of multiple manual invoice entry.
System should allow for different billing locations for different brands.
System shall provide the ability to send email notifications to clients that receive a renewal increase and go over their 'Payment
Threshold'
System shall provide the ability to send email notifications to clients for 'Welcome Letters' which are sent out through Mail Merg
via the tellus mailbox,
System shall have the ability to create an invoice on behalf of other entities centrally w/entities legal name on the invoice.
System shall have the ability to support the creation of different types of contacts for billing and other purposes.
System shall provide the ability to easily calculate state sales tax & state usage tax based on up-to-date state tax tables, & ven
location from the invoice.
System shall feed customer relationship data from CRM solution to billing system.
System shall have the ability to attach reference document at the invoice header level, invoice line level and customer level.
System shall have ability to access billing system and customers to pay invoices via mobile devices.
System shall have the bility to distribute invoices via email, postal mail and email via customer portal.
System shall have the ability to build approval workflows within the ERP for billing invoices, credit memos.
System shall have the ability to automate credit memo for certain scenarios for re-curring billing, sales tax exemptions, etc.
System shall have the ability to provide receipt images from travel and expense system to the client.
System shall have the ability to bill the customers at different site levels/centralized(customers AP shared services).
System shall have the ability to have doc date (date invoice is created in AR-not GL) , posting date (posted in GL-rev rec date),
service period (start/end date of billing period), as separate dates in customer detail.
System shall have the ability to have downpayment (prepayment). Customer will pay a credit on account for customer to prepa
but not in a regular invoice. It is a contract that includes downpayment information. (med)
System shall have the ability to have installment billing.
System shall have the ability to initiate a refund off the customer account based on the credit memo. Needs a debit AR subledg
and credit to AP.
System shall have the ability to have a credit approval workflow. Concessions (approved by sales exec distro setup in Salesforc
integrate with ERP.
System shall have the ability to consolidate invoices based on relationship.
System shall have the ability to generate billing invoices in real time.
System shall provide the user the ability to automatically trigger a capture transaction when an invoice is posted.
The system shall provide the user the ability to perform internal credit card authorizations.
The system shall have the ability to create payment entries for sales orders so that duplicate entry of the information is not
necessary.
**DST related**
The system shall provide the ability to tie prepaid order with bill coming from CRM.
The system shall have the ability to update/live synce contract data from CRM to the ERP.
The ERP budgeting module shall be able to track budgeted and actual spending amounts by all existing Accounting service
offerring and transaction-level user-defined Organization codes. Example – budgeted and actual payroll expense for ‘Company
across Company A’s departments.
The budgeting and forecasting system shall be able to project payroll expenses using user-defined assumptions (variables) upo
which to base projections.
Assumptions include:
1- number that reflects planned adding or deleting headcount
2-merit increase percentage
3- start dates for employees (which affect expense pro-rations)
4-FICA payment assumptions
5-Employment tax assumptions (including the actual timing of bonuses and stock compensation with associated timing of
employment tax payments)
6-health insurance assumptions
7-percentage of merit bonuses that will be achieved
System shall have the ability to forecast Commission including end user-input forecasted commission rates as a % of Sales.
System shall have the ability to forecast operating expense pre-payment projections by allowing the end-user to input the # of
planned pre-payments, the status of pre-payments (continue, revoke), and the pre-payment schedule.
System shall have the ability to forecast operating expense by allowing the end user to input the list/count of hw/sw spending
agreements & associated line item detail (line items can be input by Account, Business Unit, Department groupings).
The system shall have the ability to flag GL level actuals/historical transactions as EBITDA add backs.
The system shall have the ability to forecast commission by sales.
The system shall have the ability to forecast currency fluctuations (gains and losses).
System shall have the ability to keep a fixed budget rate and apply it to the actuals for more than one year. (i.e. ability to provide
an option to review actuals by fixed rate)
Workforce Planning: System shall have the ability to perform workforce planning by cost center and entity.
System shall have the ability to automatically spread topdown adjustments to cost centers.
System shall have the ability to allocate annual costs by days, months, quarters or year.
System shall have the ability to perform budget allocations for assets by line of business.
System shall have the ability to perform cash forecasting by line of business, country, region based on income statement
forecasting assumptions.
The system shall have the ability be able to perform allocations forecasting between COA string (includes country, LE, natural
acct. cost center, service offerring, sub account/activity).
The system shall have the ability to perform multi year forecasting.
The system shall have the ability to support and maintain multiple budget and forecasting scenarios.
The system shall have the ability to support what if analysis for informal what if scenarios.
The system shall have the ability to perform native forecasting based on the new COA (country, LE, natural acct. cost center,
service offerring, sub account/activity).
The system shall have the ability to add budget and forecasting only dimensions and values (includes future cost centers not ye
active in ERP, commission or vendor) not synced w/ERP to be used for specific budgetary purposes (contingency planning and
will not be used with the business).
System shall have the ability to support revenue and expense in native/local currency for all International entities; all balances
must be converted to USD for consolidation.
Budget module shall be able to incorporate year to date actual results into the budget/forecast module.
EPM Chart of Account (COA) Hierarchies should allow for planning-only child values to be added that do not exist in ERP.
System shall have the flexibility to distribute budget submission responsibility to the Budget Owner and/or Finance delegate.
Solution should the ability to view both approved and un-approved budgets.
Budgeting module shall be able to archive various version of the budget/forecast for future comparison.
Budget Solution must allow for comparison versus multiple scenarios (forecast vs budget; forecast vs prior forecast; actual vers
forecast)
Budget Solution must be able to Run Scenario Analyses to segregate the cost of hiring (impact if we keep headcount flat, impac
we keep December headcount flat, etc.)
Solution shall provide forms / templates look like for Headcount and/or OpEx and other STAT accounts or allocation based
assumptions
Solution shall be able to accept upload, smartview write-template, and/or direct entry for revenue.
The budgeting and forecasting solution shall be able to project payroll expenses using user-defined assumptions (variables) up
User-defined assumptions (variables) include:
2a-promotion increase percentage
7-percentage of target bonuses that will be achieved
Budget Solution must be able to discretely calculate the impact of merit and promotion increases.
Wages: Solution shall be able to accept employee census/roster data as well as open requisitions via API from ERP.
Solution should be able to calculate multi-year (and compounded) merit and promotion increases (i.e. 3% in 2018 and 3% in 20
based on 2018 salary)
Solution should be able to calculate pro-rated merit and promotion increases based on date of last pay increase (date can be fe
from ERP)
Temporary Employees: Solution shall be able to accept employee census/roster data with hourly pay rates and FTE assumptio
Bonus: Solution shall be able to calculate bonus expense by Bonus plan with unique target bonus achievement assumptions fo
each plan type.
Payroll Taxes: the Solution shall project expenses using user-defined assumptions (variables) upon which to base projections.
Payroll Taxes: the Solution shall be able to calculate taxes and benefits differently by Country.
Benefits: the Solution shall project expenses using user-defined assumptions (variables) upon which to base projections.
Commissions: System shall have the ability to plan target incentive comp per employee with on-top adjustment for
seasonality/sales timing.
Commissions: Solution should be able to calculate payroll taxes on any on-top adjustments to Commissions.
Headcount: Solution should be able to plan "bulk" headcount (positives and negatives) and calculate taxes and benefits.
System shall have the ability to plan operating expense with Vendor-level detail at the Chart of Account level (unique Account,
Product, Cost Center relationship).
Budget module shall allow for flexibility to plan expense at multiple levels / dimensions. (e.g. some budgets will be planned at t
vendor level; some expenses by account/cost center)
Planning templates should include prior year actuals by month using the same level of detail as the planning Solution (by Vendo
Data Agreements: Planning templates by vendor that can be shared and/or submitted by the budget owner.
HW and SW and Data Agreements: Planning templates by vendor should pre-populate any scheduled multi-period accounting
ERP (leveraging the ERP asset accounting)
Travel: Plan as a Travel dollar per head at the Cost Center level (using historical actuals); Solution should allocate budget to a
travel accounts. Plan at Parent Level, consider allocating to child level
Occupancy: Plan new locations in the same form as existing Straight-line and Deferred Rent assumptions for existing facilities.
Plan by location.
Supplies: Planning templates by Location that can be shared and/or submitted by the budget owner.
Communications: Planning templates by Vendor and Location that can be shared and/or submitted by the budget owner.
Location-based Planning (Occupancy/Supplies/Communications): System should have the ability to include a location field tha
can pull together the cost of running a facility (rent, supplies, communications, etc.).
Professional Services: Planning templates by vendor that can be shared and/or submitted by the budget owner.
Budget Solution must allow for Tagging Budget Item with an "Activity/Project Code" to segregate total cost of initiatives.
System shall have the ability to support D&A forecast based on ERP run-out of Fixed Assets and Intangibles.
System shall have the ability to plan for new capital expenditures by year.
System shall have the ability to plan for new capital assets with same amortization schedules as ERP.
System shall have the ability to forecast and budget foreign exchange rates and will need to be able to change this rate based o
the scenario. (e.g. budget, forecast, etc.)
System shall have the ability to provide net new sales by product (e.g. upload actuals from excel; upload forecast and budget fr
excel)
System shall have the ability to provide headcount by cost center (e.g. month end actual from ERP via API; Forecast from
EPBCS; Budget from EPBCS)
System shall have the ability to provide weighted average shares. (e.g. actual from ERP Stat Account; Forecast and Budget fro
Excel upload)
System shall have the ability to provide non-GAAP adjustments and tag line items in the planning solution as non-GAAP (e.g.
acquisition & integration; restructuring; etc.)
System shall have the ability to provide headcount by cost center (e.g. month end actual from ERP; Forecast from EPBCS;
Budget from EPBCS; include ERP Functional Role; include Location)
Budget solution must allow for finance user admin to consolidate inputs. (not solution admin)
Budget module shall have the ability to replicate any/all automated cost allocations performed in the GL financial close process
Solution shall provide the ability to set different user roles for the budget module: Read Vs write; access rights by department.
Budget module must allow for different levels of control/viewing/edit rights. (e.g. Financial Analyst can view/edit salary informat
for Cost Center X, but not for Cost Center Y, OR for all Cost Centers except for Cost Center Z)
System shall have the ability to create custom roles for System Admin (Add/create users, change permissions and roles) vs.
Functional Admin. (e.g. add scenarios, non GL Dimensions, etc.)
Budget Solution must allow for future period budgets to be built leveraging formulas and direct inputs to predict future revenue
and expense (Driver-based Rolling Forecast).
System shall have the ability to support Base / Current Year(s) bottoms-up detailed forecast; future years are largely driver-base
with a few manual inputs.
System shall have the ability for manual input items to include Revenue, Rent/Occupancy, Marketing expense, and Legal Fees.
Solution must have the flexibility to add adjustments on-top of any driver/historical data-based forecast.
The PO System shall provide the ability to the Finance/Accounting team to tag a Purchase Order as "Capex" in order to denote
that the PO is part of the capex budget and to track associated spending.
-this includes the ability to enter the Capex account/charge number on the PO.
System shall prevent the ability to book a payment for a Capex project where the approved budget is exhausted,
System shall provide an option to over-ride with manager approval
System shall provide a budgeting module which allows construction of an Inter-Deparment Budget.
The inter-department budget should be able to be constructed using the same data points as the data contained in the 'Capex
Expense' History & Projections reports, in order to build budgets in a uniform structure with the underlying expense
history/projections.
This means that the Financial Planning/Budget Owner user can enter the dollar amount of the specific budget need for a)each
Department and for b)each spending category within each department - where 'spending category' is defined as the [desired
subset of] data points for which expenses are aggregated in the Expense History/Projections reports.
The Project/accounting module shall allow the end user to set up Capex Project instances with coding, Owners, budgets and
Capex Thresholds
System shall provide Collection Staff the ability to configure dunning forms (collections notices that go to the customer) based
user-defined aging buckets for overdue balances (e.g. 30 days late notice, 60 days late notice, 90 days late notice).
System shall allow for the method of transmitting dunning forms to be the same as the one used to transmit the invoice (mail-
ready printout or email)
System shall have the ability for the collector to have the functionaility to view historical invoices, communication email,
matter_contract, etc.
System shall have the ability for the collector to view specific contract information (e.g. payment terms, legal signatory, etc).
System shall have the ability to capture trading community architecture. Needs to be shared between CRM and ERP and vice
versa.
System shall have the ability to provide the functionality to interface with a credit scoring tool.
System shall have the ability to predict based on trends of payments in the system predicts CF and expected payment date ran
System shall have the ability to include preset rules to assist with identifying prioritization of collection targets.
System shall have the ability to flag a customer's cash basis.
System shall have the ability to bill in arrears, advance, or other methods.
System shall have the ability for Collector Manager to determine bad debt vs credit memo.
System shall have the ability to not allow business to be done with the customer until the bad debt is removed.
System shall have the ability to notify/flag CRM via feed if a customer has bad debt before continuing to do business with the
customer.
System shall have the ability to automate customers who go default based on contract based aging schedule.
The system shall have the ability to make bad debt account (contract data) available via web service.
System shall provide Finance staff the ability to create the following elimination companies:
1- LE to LE
2- (US and foreign)
3- (foreign to foreign)
System shall have the ability to convert foreign currencies at the consolidated level to a corporate Currency (currently USD) from
any locally transacted currency. This should be done for both actuals and budgeted numbers.
System shall have the ability to convert foreign currencies to USD.
System shall have the ability to automatically eliminate intercompany balances from consolidated financial reports and trial
balance.
The system shall have the ability to prevent loading data from Country/Legal entity to the Consolidated entity without first resolv
all eliminations and intercompany transactions.
System shall have the ability to consolidate legal entities according to different hieararchies and for different reporting purposes
(e.g. for Corporate GAAP, for SEC reporting, for Local government reporting, tax reporting etc.).
System shall have the ability to consolidate legal entities according to different hieararchies (e.g. consolidation by region, count
and global).
The system shall have the ability to automatically create the of-setting elimination intercompany balances from consolidated
financials. Reports and TB.
System shall provide FA staff one corporate set of books and one or more set of tax books per legal entity.
System shall provide FA staff the ability to configure default depreciation methods for an asset class
System shall provide the ability to mass copy of one tangible or intagible assets.
System shall provide FA staff the ability to easily import mass upload capability of asset sub-ledger in order to create multiple
asset classes at once.
System shall have the ability to automatically create a fixed asset sub-ledger when a fixed asset invoice is posted to the AP
Ledger
System shall have the ability to flag the disposal of a fixed asset to prevent FA Staff from further processing.
System shall allow all Fixed Assets, Vendor, and General Ledger entries to be easily viewable from the asset sub-ledger. (all
ledger entries for asset should be viewable from sub-ledger)
System shall allow user to view Acquisition Cost details from the Fixed Asset Ledger
System shall allow user to view Unit Cost details from the vendor ledger
System shall provide the ability to automatically include assets that were acquired in the past in current depreciation calculation
(e.g. if the Asset sub-ledger was created after the in-service date, the depreciation calculation should know to include the asset
System shall provide FA staff the ability to easily select which assets to depreciate based on an advanced search criteria. (e.g.
company, date, country, asset class, depreciation type)
System shall provide FA staff the ability to set custom asset life for any asset.
(depreciation Start Date and duration of depreciation)
System shall provide FA staff the ability to easily review depreciation journal entries before posting
System shall provide FA staff the ability to post all pending depreciation entries at once.
System shall have the ability to auto-populate from the asset sub-ledger to the depreciation entry organizational Segment Code
like service offerring and cost center
Sytem shall have the ability to retroactively correct / edit asset data including retroactively editing depreciation.
System shall provide the ability to partially dispose of an asset by easily disposing one or more of its parts/disposable compone
System shall provide FA staff abilty to dispose an asset where the Book Value is not '0' or 0.
System shall provide FA staff the ability to easily dispose of multiple assets within a Company and Asset Class at once
System shall provide FA staff the ability to review disposal journal entries before posting them
System shall provide Tax staff the ability: 1. Track the location of the Fixed Assets, by city and by state (this m
be a required field). 2. Provide the option for a drop down menu of pre-defined loations (e.g. offic
data center). 3. Provide the ability to move location field as needed (e.g. transfer data center
equipment from one location to another).
System shall have the ability to handle asset conversion rate by country (e.g. assets purchased in the US for AUS).
System shall have the ability to auto create and/or auto post based on the source of JEs (e.g. subledger, external system (AX-
free text invoice to depreciate/dispose FA - does it need to be approved before the posting takes place), etc.) -ask Mark or Jeff.
you have scenarios?
System shall have the ability to maintain two sets of FA books for local and corporate reporting.
System shall have the ability to create local, US GAAP and tax books for financial reporting.
System shall have the ability to merge or split multiple invoices into one asset.
System shall have the ability to identify at requisition or AP level that POs can be assigned to one specific Asset.
System shall have the ability to perform depreciation by days, weeks, or months.
System shall have the ability to handle VAT variances for asset transfers (see Andreas diagram).
System shall have the ability to send an alert to approvers when assets are transferred from one LE to another LE.
System shall have the ability to calculate VAT based on the location of the transaction.
When an accounting segment, for which transactions occur, is added to the system (segment could be customer, vendor,
company, account, etc), the system shall provide user the ability to easily configure basic default values for the account segmen
in order to have those values auto-populate on corresponding transactions for that entity.
ex-An 'Account123' accounting segment has default Location = 'HQ', so Vendor payment ledger entries using Account123 will
have default location - 'HQ'.
Within the account segment, user should have the ability to set up account codes where the value (alphanumeric) represents a
the transaction-level components such as (account, business unit, etc) - request in a BI/Reporting meeting
System shall provide user the ability to easily create multiple instances of accounting segments at once using a 'copy' feature.
For example, ability to create multiple invoice lines at once, multiple purchase orders at once, etc
System shall provide the user the ability to do a mass upload of any type of journal entry via a user interface.
The system shall have the ability to allow/not allow Journal entry approvals (in the automated workflow) based on predetermine
rules (e.g.local reporting vs. Corporate/GAAP reporting purposes; Country, Legal Entity, etc.)
System shall have the ability to support transactions posted to one standardized, global COA and then mapped to a local GL
books for localized reporting.
System shall have the ability to provide built-in data mass loading template to mass upload journal entries, invoices, and other
transactions without the use of a third party tool.
System shall provide user the ability to perform any type of reversal including mass reversal of posted transactions (i.e, journal
entries or group of journal entries, AP/GL, AR/GL entries, etc…)
System shall provide user the ability to perform any type of re-posting of reversed entries according to business rules
System shall have the ability to reverse sub-ledger entries
System shall provide GL staff the ability to code a balance sheet account item in order to flag it as either "current" or "non curre
in reporting period.
System shall provide GL staff the ability to code an expense journal entry with any user defined activity codes:
-Activity Codes exmaples: 'Business Deal', 'Advertising', 'Non-Advertising'
System shall provide the ability to flag journal entry by entity
Example, ability to set up Legal Entity > Account hierarchies and report on all child account activity under the specified parent
Legal Entity.
System shall provide GL staff the ability to classify expense accounts as ('Personnel', 'marketing', and 'operating').
Specifically in the 'Personnel' expense accounts, there must be the ability to classify associated transactions as: wages, payroll
bonuses in the transaction ledgers.
The system shall provide GL staff the abiltity to label an account as a 'COGS' account for the purposes of SEC reporting.
System shall provide GL staff the ability to code an accounting segment as an "income statement" or "balance sheet" account
System shall provide GL staff the ability to flag account accounting segments as "Europe" or "North America" for reporting
purposes.
System shall provide GL staff the abilty to flag all transactions as 'Non-GAAP' adjustments for public reporting purposes
(e.g. Ability for all GAAP accounts to be easily setup/coded to comply with GAAP requirements of account’s locality (add the ma
ones US, UK, Poland)
System shall have the ability to be IFRS-Compliant easily while also being local-GAAP compliant
System shall have the ability to maintain revenue and expense ledgers in multiple currencies (with historical fx rate auto-applied
with rate valid at time of ledger posting)
System shall allow user to look up the chart of accounts and also any accounting segment hierarchy.
System shall have the ability to automatically feed JE’s from external systems using a API.
System shall provide GL staff the ability to export any type of general ledger entry to Excel, Powerpoint, PDF, XML, TXT, CSV
format.
System shall provide GL staff the ability to export any type of general ledger entry to Excel.
System shall provide user's with specific permissions and the ability to post prior period posting adjustments, (and also the abili
to specify that NO adjustments can be made for certain accounts or other GL segments).
In these cases, there should be a clear audit trail of what changed, viewable by a report.
(e.g. retroactively update account balances by creating and posting journal entries to a previous accounting period. User must
specify the year and the period to which they should be posted)
System shall not allow user to delete any posted Journal Entry. Journal entries can only be reversed once posted (Journal entri
created but not posted can still be deleted, with a proper audit trail)
System shall not allow user to delete any Journal Entry without the proper audit trail being associated to it.
System shall have the ability for all transaction IDs to be globally unique and frozen - no duplicates.
Transaction IDs shall be auto-generated, in order to easily refer to the same Transaction ID across any ERP entity
Ex- journal entries, invoices, Purchase Order, etc.
System shall provide the ability to code whether AP invoices, and associated GL transactions are "pre-paid" for the purposes of
expense reporting.
System shall have the ability to minimize the volume of manual JE by Allowing an approval workflow for each manual JE.
System shall have the ability to minimize the volume of manual JE.
System shall have the ability to be configured to manage ledgers locally or centrally.
System shall be able to track unrealized and realized gain/loss by country and prevent the posting of these entries for certain lo
entities based on the local requirements.
System shall provide user the ability to track the history of structure changes to any accounting segment heirarchy including cha
of accounts.
System shall be able to differentiate between reporting currency, functional currency and transactional currency.
System shall be able to track unrealized gain/loss by country and automatically calculate actual unrealized gain/loss to be
recorded.
System shall have the ability to limit user access to local ledgers by country and/or legal entity.
System shall have the ability to support close processes. (e.g. close periods for all books centrally by a single click for a period)
The system shall have the ability to control intercompany entries to avoid incorrect In tercompany entries posting between legal
entities via an approval workflow or other automated controls.
The system shall have the ability to automatically create the of-setting intercompany entry in the corresponding Legal entity bas
on pre-defned rules at the GL and/or consolidation level.
System shall have the ability to have up to the minute updated consolidation in order to perform, at a minimum, the following:
- Auto-calculate and auto-post the elimination entries
- Enable real time viewing of all Financial Consolidation reports (Income Statement, Balance sheet, trial balance, etc).
System shall provide the ability to code all intercompany accounts as either:
1) Interest is Charged
2) Interest is not Charged
Using the coding for intercompany accounts, which identify each account as 'interest bearing' or 'not interest bearing', the syste
should auto-calculate and post interest to the 'interest bearing' accounts as follows:
1-the GL user enters an intercompany interest rate in the appropriate ledger
2-the system auto-calculates and posts the interest to the 'interest bearing' accounts according to the calculation for the specific
type of interest rate that was entered:
(Example - calculate [rate (x) avg balance for last 2 years] * .25)
System shall have the ability to automate eliminations between statutory accounts by country (across LEs).
System shall have the ability to automate revaluation for intercompany entries by country (functional currency by country).
System shall have the ability to provide automated intercompany transactions based on preset rules.
System shall have the ability to provide the functionality that recognizes if there are no preset rules for Intercompany transaction
FAIL the transaction or not release to the suspense account.
System shall have the ability to consolidate with intercompany eliminations by country, region and global.
System shall have the ability to comply with gov regs around lease acct for lease real estate and equipment.
System would need to calculate the hold a training fund as a mandatory requirement from the government.
System will need to hold historical payslip information for 5 years.
Payroll will need to see the saving due to social charge deductions or tax savings
System will need to be able to do benefit in kind tax calculations for each monthly payroll depent on Pension contribution and
other benefit allowances that are subject to tax.
System shall have the ability to allow multiple tax years.
System shall have the ability to enable net to gross calculations.
System shall allow for shadow payroll processing for international employees.
The system shall be able to support employment based on "at-will" employment with each employee.
System shall have the ability to provide unlimited number of payrolls, if an extra payroll cycle is required.
System shall have the ability to be available for keying data during all phases of the payroll process.
System shall be able to multiple payroll schedules (e.g. bi-weekly and monthly).
System shall have the ability to run separate payroll corporate groups for each location.
System shall have the ability to add unlimited locations and new corporate structures (e.g. department, business units, function
etc).
System shall be able to provide unlimited number of Earnings Codes or Pay Types.
System shall have the ability to provide unlimited number of Deductions Codes, both pre-tax and post-tax.
System shall have the ability to provide direct deposit and paper check hard copy versions are available.
System shall have the ability for Payroll Administrators to print “live checks” on demand (including Manual / Off Cycle Checks).
System shall have the ability to allow for payments to be loaded to “VISA” (or other major bank) “Pay Cards” / Debit Cards.
System shall have the ability to provide pay slips/check stubs to employees each pay period (electronic and/or paper).
System shall have the ability to provide stub descriptions for all earnings, deduction codes and stub earnings details for both
current pay period and Year-to-Date accumulators.
System shall have the ability to allow for Direct Deposit to up to 3 destination bank accounts per employee.
System shall have the ability for payroll to accept input from and send output of earnings information from/to multiple sources
(time-keeping, benefits systems, etc.).
System shall have the ability to allow payroll to accept input of deduction information seamlessly from multiple sources, most
especially from Benefits Admin partners.
System shall have the ability to schedule specific earnings for a specific payroll cycle (e.g. monthly commission, expat COLA, c
allowance, etc).
System shall have the ability to specify start and stop dates for Earnings and/or Deductions.
System shall have the ability to allow Administrator to add new Deduction Codes.
System shall have the ability to allow overrides of data for rates, taxes, supplemental tax rates, deductions, but keeps previous
input visible.
System shall have the ability to manage garnishments, liens, withholdings and remittance.
System shall have the ability to support inputed income or taxable benefit withholdings, when required.
System shall have the ability to acommodate Shift Differentials, if needed.
System shall have the ability to support computations of pay, vacation, overtime pay, apply break rules, sick leave,
maternity/paternity, etc. in compliance with country/state laws.
System shall have the ability to calculates annual bonus payouts.
System shall have the ability to commodate and perform complex calculations including multiple pay rates for same task or
activity.
System shall have the ability to acommodate Specialty Pay Types (e.g. luncheon voucher, travel reimbursement, training bonus
local travel allowance, wellness discounts on benefit deductions, etc.).
System shall have the ability to acommodate and track Incentive Pay (e.g. bonuses and awards, commission).
System shall have the ability to calculate pay based on copyright type of work (e.g. certain job titles in Poland and Italy are paid
differently for copyrighted work).
System shall have the ability to load mass payroll changes (e.g. merit increases, COLA’s, etc.) via simple spreadsheets (e.g.
Excel, CSV or other).
System shall have the ability to manage all Tax Reporting (federal, state, municipal, unemployment, social insurance) per count
including in person remittance as necessary (e.g Japan).
System shall hae the ability to produce Tax forms for employees and/or contract workers across the globe (T4, W-2, 1099, 1095
etc.).
System shall have the ability to produce 1 (one) W-2 (or international equivalent annual earnings statement) for an employee if
they change employee status (rehires, exempt to non-exempt or have an immigration status change).
System shall have the ability to customize information on pay slips.
They system shall have the ability to provide employees on-demand access to view and change their payroll information via on
self-service tools (view/print pay slips, change address, W-2, change W4, change state withholding, change direct deposit).
System shall have the ability to provide additional payroll functionality that will need to match KO process for uploading to ADP.
System shall have the ability to display PTO balance for all hourly employees from the absence management system.
The system shall be able to comply with local employee payroll reporting to tax and labor government authorities in all EMEA
Countries.
The system shall be able to support employment based on a personal contract with each employee.
System shall have the ability to allow for proper handling of 13 month salaries.
System shall have the ability to provide Manages requests and approval process. Information should appear either regularly on
pay stubs or in another accessible way. Must allow multiple leave plan setup and be compliant with state and local laws (ie: S.F
Cali).
System shall have the ability to manage comp time and over time payment.
System shall have the ability to support a workflow to approve timesheets (e.g. manager or delegated manager).
System shall have the ability to store and retain payslips for all employees.
System shall provide Purchasing staff the ability to create and re-use Contract Agreements/Master Agreements (via templates)
System shall provide Purchasing staff the ability to convert any awarded solicitation to a contract (ability to export solicitation
information to a contract file upon user status change to 'awarded')
System shall provide the ability to store contract language.

The template creator should have the ability to control permissions or rights to change/update a Contract, or Access to contract
System shall have the ability to create any type of contract, including buy-side, sell-side, and non-monetary agreements (e.g.
Intellectual Property, Non-Disclosure Agreements, etc.).
System shall have the ability to manage contracts in multiple formats, including MS-Word compatible and PDF.
System shall notify suppliers (vendors that have been set up in the Vendor Master) that contracts have been drafted and allow
them to log in and evaluate/ agree or decline based on proposed terms.
System shall notify Purchasing Manager and/or a group of internal users of any requested contract edit made by an external us
(e.g. supplier).
System shall provide Purchasing staff the ability to assign compliance items (KPIs) to contracts, allowing users to track the
fulfillment of these KPIs and also be able to automatically issue alerts to Purchasing staff/Vendor when a KPI is not met.
Example, Compliance Item could be set as Price Variance KPI (where price agreed to in Contract and Price Billed are different
a certain amount above a threshold), and a vendor subsequently sends a bill for a price above the threshold.
Then, the alert would be triggered and notification sent to Purchasing staff/Vendor.
System shall provide the ability to add electronic signature to contracts via an E-signature or DocuSign interface.
(e.g. KLD representative will sign the contract using E-signature or DocuSign. Vendor representative will also sign using E-
signature or DocuSign, then interface will automatically transfer the signature to the contract)
System shall have the ability to support punch out catalogs.
System shall have the ability to flag unbudgeted requisitions and automatically route to finance for approval.
System shall have the ability to send IT requisitions for approval/review based on purchase category.
System shall allow Finance end users to input Capital Expense thresholds for any user-defined Project spending category (whe
'category' is a set of transactions that occur under specific Accounting Segments/GL Coding) in order to subsequently report on
Capex spending and budgeted amounts (where the amounts meet the Capex treshold).
System shall have the ability to split bills by project to multiple customers based on contract details.
System shall allow for alternate billing item/product description to be displayed on invoices based on client specification on the
sales contract.
The System shall allow for alternate billing item/Product description to be displayed on invoices based on clent specification on
the sales contract
System shall have the ability to calculate actual and projected Project-level expenses using Line Item detail from Expense
Ledgers.
System shall have the ability to define/configure non-financial performance metrics in order to set budgeted performance values
and measure actual performance against budgeted values.
Non-Financial metrics include:

1-Brand Preference - market cap or other quantitative position of a KLD brand compared to a competitor brand for same type o
product
2-Take Rate - how well customers and prospects respond to CTAs (Calls to Action) - example: % of emails sent offering free
demos that user selected to schedule (helps measure ROI of CTAs)
3-Customer Retention & Churn - Retention = # of customers that continue to purchase and Churn = # of customers that drop of
and stop purchasing over time
4-Customer Experience - tools to build KLD-specific metrics around all touchpoints that customers interact with KLD staff (sales
call center, etc)
5-Innovation - Adoption rate of new products
6-Market Share - amount of customer dollars in market invested into KLD
System shall provide the ability to set different user roles for the budget module: Read Vs write; access rights by department
System shall provide the ability to enter Project level purchase orders for Project Budgets (non-capex) in order to track expense
against project budgeted amounts.
System shall have the ability to forecast (revenue, opex, personnel exp) at a Consolidated level (above the project level – like b
location or even globally)
System shall provide the ability to view approved budgets globally (from the budget approval workflow)
System shall provide user the ability to search Vendor documents such as contracts, contract attachments, etc...
System shall allow full text search functionality (e.g. search for text, words, phrases, etc.) within any contract and/or template
contained in the system, including the ability to search attached documents (in PDF, Word or HTML formats) in order to find all
instances of a document with the entered phrase.
System shall provide Purchasing staff the ability to copy / transfer purchase requisition data to a corresponding purchase order
without re-keying (e.g., requisition to purchase order).
System shall provide AP staff the ability to create a PO for multiple vendors, for cases where the PO needs to be created at the
Project Level.
System shall have the ability to automatically turn invoices into Purchase Orders and should pass two way matching.
System shall have the ability to provide purchase category rules based on items purchased.
System shall have the ability to enter a requisition into local currency and translate into USD; all requisition approvals should be
done in USD.
System shall be able to automatically convert Requisition to PO (e.g. not a manual conversion from Req. to PO)
System shall be able to provide support for account coding needs and to automatically route the requisition for approval.
System shall provide the ability to match Purchase Orders to the invoice.
System shall have the ability to only setup approval routing for all transactions to the cost center hierarchy.
System shall provide the ability to track certain projects and / or activities.
System shall provide the ability to create alternative routes of approval based on preset rules.
System shall provide the ability to create an approval workflow prior to cash disbursements by country (Accounting activity, not
Treasury).
System shall provide support for the daily load file (open billing for LT projects) process that loads billing transactions into AX. T
feed collects billing metrics from the legacy DataMart for active projects and loads them into AX item journals. This process is
running in the early morning hours of each day.
The automated load process is also used for user created files that need to load large amounts of data into open billing. Users
create a csv file and put it into a specific directory where it is processed.
System shall have the ability to create the following Purchase Order types:
1. Purchase Order from Contract (without requisition)
2. Create a stand alone Purchase Order
3. Create a Purchase Order for Projects
System shall have the ability to create the following Requisitions:
1. Catalog / Punch-Out
2. Non-Catalog / ad-hoc
3. Copy an existing requisition
System shall have the ability to calculate requisition amounts requested for approval based on VAT setting but the user shall ha
the ability to enter net amount of VAT.
Purchase Orders amounts shall be net of VAT or Sales Tax

Purchase Orders amounts shall be translated to USD first for all countries and then routed for approval
Requisitions amounts shall be translated to USD first for all countries and then routed for approval
The system shall allow for an approved PO to be amended with no additional approval only if it meets one the the below criteria
1. Updated requested amount is less than the original approved amoount OR Updated requested amount is within a predefined
threshold (e.g. +- $100 or +1%).
System shall be able to analyze the sales of all offerings and quantitatively determine standalone selling price (SSP) both unde
ASC 606 and IFRS 15.
Under ASC 606 system shall be able to identify SSP on distinct performance obligations using a similar approach as identified
above.
System shall be flexible enough to allow stratifications of agreements and the ability to apply SSP based on qualitative factors t
can be input into the system
e.g.
Attributes related to the calculation of the SSP such as contract groupings should be able to be identified in the system and the
there should be the flexibility if we identify which should be grouped together that the system can apply the SSP calculation to t
identified populations.
System shall have the ability to ensure that the ending value after the rev allocations between line items / SKUs that have
occurred does not exceed the initial value of the original transaction
System shall be flexible enough to be able to calculate the SSP for each SKU / service offerring code at any frequency
management requires
System shall have robust reporting capabilities and at a minimum be able to report at the individual multiple performance
obligations (MPO) (bundle) level by line the SSP related to the product, the last date of the assessment and any adjustments
necessary
System shall include custom descriptive error handeling messages in case any function or data transfer from KLD's source
systems has not completed correctly or sufficiently.
System shall be able to identify current and long term deferrals and be able to report on them.
System shall be able to identify backlog of revenues by service offering.
System shall be able to account for changes in Revenue Recognition Entries resulting from reversals of contracts line items.
System shall have the ability to standardize contract setup system (rev recs / rev man engine).
System shall have the ability to feed billing data from the billing system.
System shall have the ability for all products to be setup in the billing module.
System shall have the ability to create a hieararchy for service offerrings.
System shall have the ability to automatically generate deferred or recognized revenue based on contract details (billing lines) a
invoices are posted.
System shall have the ability to automtially populate the rev schedule for the life of the contract based on the type of the contrac
(e.g. hosting, t&m, subscription, processing).
System shall have the ability for techincal accounting to manually override the rev schedule that was created for the invoice.
System shall have the ability to recognize revenue on a monthly basis.
System shall have the ability to create a link with the stored image of the contract in CRM (Salesforce).
System shall have the ability to determine the shipping points for revenue (e.g. DST - shipping point, LT - service period).
System shall have the ability to add a to flag for contracts that have volume discounts, service level agreements, or other 1 off
options that aren't part of the original template. Route for review and approval by technical accounting before rev recongition to
occur.
System shall have the ablity to calculate SSP by netting out CMs, invoices, contract line items, and other revenue adjustments.
System shall have the ability to allow manually created revenue recognition schedule in the revenue recognition module as an
exception process, in the cases of nonstandard contracts.
System shall have the ability prior to billing, to match the invoice to sales order for exceeded contract terms.
System shall have the ability to flag contracts that have volume discounts, service level agreements or other terms that are one
or are not part of the original template .
System shall have the ability to create non standard contract based on a rev schedule. it's an exception process.
System shall have the ability to flag non-standard contract as they come in from the CRM, and route those through the approva
workflow.
System shall have the ability to include standardized, unique identifiers for customer names, sales reps.
System shall have the ability to have one single source of information to store sale commission data.
System shall have the ability to calculate payroll taxes on any on-top adjustments to sales commissions.
System shall have the ability to change the sales commission data (billed or credited data - e.g. billed rev for managed review w
need to include accrued revenue)
System shall have the ability to provide accurate/clean data required to calculate commission.
System shall have the ability to support countries that require the ERP system to handle depreciation.
System shall provide the ability to add an asset with different values in corporate books vs tax books.
be a required field). 2. Provide the option for a drop down menu of pre-defined locations (e.g. offi
System shall provide the ability to record tax as part of intercompany loan transactions.
System shall provide user the ability to break out the sales tax vs use tax by location.
System shall provide user the ability to calculate GAAP and tax depreciation.
System shall provide Tax staff the ability to capture whether a transaction is 'tax sensitive' or 'not tax sensitive' in order to help
estimate tax payments/credits due.
System shall allow user to view transactions by legal entity.
System shall have the ability to maintain quarterly tax schedules and rates going into financial statements.
System shall provide the user the ability to reset acquired fixed asset values in order to reset depreciation.
System shall provide the user the ability to maintain historical cost value, historical tax depreciation and historical useful lives
depending Fixed Asset transactional structure.
System shall provide a Sales Taxability Matrix to record the appropriate tax on products/services offerings.
System needs to be able to extract only items that are taxable.
System needs to integrate with state tax website (if the option is available by the state).
Tax tool (to replace STO) shall have the ability to extract use tax (e.g. currently there is a separate extract pulled from AX).
System shall have the ability to pay invoices based on contract terms.
System shall have the ability to have a central repository and maintain contracts.
System shall have the ability pay recurring, variable lease payments based on a set schedule.
System shall have the ability to enable users to search Contract information by key words, vendor names and contract terms.
System shall have the ability to provide an approval workflow for new contracts created and seamlessly capture the new contra
data to be stored in a central repository.
System shall have the ability to create an approval workflow based on compliance regulations that impact KLD's compliance an
regulatory standing.
System shall have the ability to create an approval workflow based on a threshold amount.
System shall have the ability to provide PO matching with signed contract.
System shall have the ability to provide an automated alert/notification of the requisition, contract and PO progress.
System shall have the ability to automatically generate an invoice for self service managed review sub-contactors.
System shall have the ability to allow a parallel first level approval workflow (first level US approver and from invoice or PO line
amount; multiple cost centers and requisitions
Req. No. Module
1 Accounting Close
2 Accounting Close
3 Accounting Close
4 Accounting Close
5 Accounting Close
6 Accounting Close
14 AI
15 AI
16 Allocations
17 Allocations
18 Allocations
19 Allocations
20 Allocations
21 AP
22 AP
23 AP
24 AP
25 AP
26 AP
27 AP
28 AP
29 AP
30 AP
31 AP
32 AP
33 AP
34 AP
35 AP
36 AP
37 AP
38 AP
39 AP
40 AP
41 AP
42 AP
43 AP
44 AP
45 AP
46 AP
47 AP
48 AP
49 AP
50 AP
51 AP
52 AP
53 AP
54 AP
55 AP
56 AP
57 AP
58 AP
59 AP
60 AP
61 AP
62 AP
63 AP
64 AP
65 AP
66 AP
67 AP
68 AP
69 AP
70 AP
71 AP
72 AP
73 AP
74 AP
75 AP
76 AP
77 AP
78 AP
79 AP
80 AP
81 AP
82 AP
83 AR
84 AR
85 AR
86 AR
87 AR
88 AR
89 AR
90 AR
91 AR
92 AR
93 AR
94 AR
95 AR
96 AR
97 AR
98 AR
99 AR
100 AR
101 AR
102 AR
103 AR
104 AR
105 AR
106 AR
107 AR
108 AR
109 AR
110 Billing
111 Billing
112 Billing
113 Billing
114 Billing
115 Billing
116 Billing
117 Billing
118 Billing
119 Billing
120 Billing
121 Billing
122 Billing
123 Billing
124 Billing
125 Billing
126 Billing
127 Billing
128 Billing
129 Billing
130 Billing
131 Billing
132 Billing
133 Billing
134 Billing
135 Billing
136 Billing
137 Billing
138 Billing
139 Billing
140 Billing
141 Billing
142 Billing
143 Billing
144 Billing
145 Billing
146 Billing
147 Billing
148 Billing
149 Billing
150 Billing
151 Billing
152 Billing
153 Billing
154 Billing
155 Billing
156 Billing
157 Billing
158 Billing
159 Billing
160 Billing
161 Billing
162 Billing
163 Billing
164 Billing
165 Billing
166 Billing
167 Billing
168 Billing













CAPEX
Budgeting
242
&
Management
CAPEX
Budgeting
243
&
Management
CAPEX
Budgeting
244
&
Management
CAPEX
Budgeting
245
&
Management
246 Collections
247 Collections
248 Collections
249 Collections
250 Collections
251 Collections
252 Collections
253 Collections
254 Collections
255 Collections
256 Collections
257 Collections
258 Collections
259 Collections
260 Collections
261 Eliminations

269 Fixed Asset
270 Fixed Asset
271 Fixed Asset
272 Fixed Asset
273 Fixed Asset
274 Fixed Asset
275 Fixed Asset
276 Fixed Asset
277 Fixed Asset
278 Fixed Asset
279 Fixed Asset
280 Fixed Asset
281 Fixed Asset

282 Fixed Asset
283 Fixed Asset
284 Fixed Asset
285 Fixed Asset
286 Fixed Asset
287 Fixed Asset
288 Fixed Asset
289 Fixed Asset
290 Fixed Asset
291 Fixed Asset

300 GL
301 GL
302 GL
303 GL
304 GL
305 GL
306 GL
307 GL
308 GL
309 GL
310 GL
311 GL
312 GL
313 GL
314 GL
315 GL
316 GL
317 GL
318 GL
319 GL
320 GL
321 GL
322 GL
323 GL
324 GL
325 GL
326 GL
327 GL
328 GL
329 GL
330 GL
331 GL
332 GL
333 GL/TAX
334 GL/TAX
335 GL/TAX
336 GL/TAX
337 Intercompany
338 Intercompany
339 Intercompany
340 Intercompany
341 Intercompany
342 Intercompany
343 Intercompany
344 Intercompany
345 Intercompany
346 Intercompany
347 Lease Accounting
348 Payroll
349 Payroll
350 Payroll
351 Payroll
352 Payroll
353 Payroll
354 Payroll
355 Payroll
356 Payroll
357 Payroll
358 Payroll
359 Payroll
360 Payroll
361 Payroll
362 Payroll
363 Payroll
364 Payroll
365 Payroll
366 Payroll
367 Payroll
368 Payroll
369 Payroll
370 Payroll
371 Payroll
372 Payroll
373 Payroll
374 Payroll
375 Payroll
376 Payroll
377 Payroll
378 Payroll
379 Payroll
380 Payroll
381 Payroll
382 Payroll
383 Payroll
384 Payroll
385 Payroll
386 Payroll
387 Payroll
388 Payroll
389 Payroll
390 Payroll
391 Payroll
392 Payroll
393 Payroll
394 Payroll
395 Payroll
396 Payroll
397 Payroll
398 Payroll


411 Project Accounting
412 Project Billing
413 Project Billing
414 Project Billing
421 Purchasing
422 Purchasing
423 Purchasing
424 Purchasing
425 Purchasing
426 Purchasing
427 Purchasing
428 Purchasing
429 Purchasing
430 Purchasing
431 Purchasing
432 Purchasing
433 Purchasing
434 Purchasing
435 Purchasing
436 Purchasing
437 Purchasing
438 Purchasing
439 Purchasing
440 Purchasing
441 Purchasing






473 Tax
474 Tax
475 Tax
476 Tax
477 Tax
478 Tax
479 Tax
480 Tax
481 Tax
482 Tax
483 Tax
484 Tax
485 Tax
486 Tax
487 Tax
488 Tax
489 Tax


Requirement
System shall provide the ability to create & track financial close process tasks/assignments through completion using workflow.
Ability to track by business day, due date, etc.
System shall have the ability to provide the functionality to create an approval rule to ensure that a manager has reviewed and
approved the journal entry before it is posted.
System shall have the ability to provide the functionality to support a global close calendar.
System shall have the ability to support transactions posted to one standardized, global COA and then mapped to a local cost
center.
System shall have the ability to provide built in data mass loading template.
System shall have the ability to flag GL level actuals/historical transactions as EBITDA add backs.
System shall have the ability to provide the functionality to have a global system to centrally manage legal entities by country.
System shall provide GL staff the ability to designate each general ledger account accounting segment by a user-definable
"account type" as follows in order to prepare lead schedules:
a. Asset Account
b. Liability Account
c. Equity Account
d. Budget Account
e. Revenue Account
f. Project Account
g. Expense and expenditure account
The System shall have the ability to automaticlally distinguish/identify journal entries in to specific categorties for reporting
purposes (e.g. Local/country reporting vs. US GAAP/Corporate).
System shall provide the ability to code Investment Account transactions as either 'unrealized gain' or 'unrealized loss' in order
generate certain SEC reports.
System shall provide the ability to code whether Purchase orders, invoices, and associated transactions are "pre-paid" for the
purposes of expense reporting
System shall provide the ability to code an 'Account' Accounting segment/business object as "allocation account" vs "non-
allocation account" for the purposes of expense reporting
System shall have the ability to automaticlally distinguish/identify journal entries in to specific categorties for reporting purposes
(e.g. Local/country reporting vs. US GAAP/Corporate).
System shall have the ability to automate cash allocation based patterns from the past.
System shall have the ability for auto-billing for re-curring revenue.
System shall have the ability to support Rule based automated allocations across COA segments and within a specific COA
segment (Cost Center, GL Account, etc.)
System shall have the ability to support Rule based allocations across GL periods that are open.
System shall have the ability to support allocations centrally.
System shall have the ability to support allocations across COA (LE, segments, etc.)
System shall have the ability to support various vacation rules. Need to feed vacation accruals from HCM to ERP.
System shall provide AP Admin staff the ability to create and maintain an enterprise wide, vendor master file which interfaces w
other ERP modules, in order to allow auto-population of vendor data into payment ledger entries.
System shall allow a designated system Admin user to add, update, and delete vendor master data.
Vendors can be created in bulk.

System shall provide a designated Admin user the ability to block a vendor in order to prevent transactions from being made wi
that vendor.
(e.g. the master record is available in the system, but no transaction can be posted to that vendor, and vendor is not allow to
further supply materials until the block is removed)
System shall have the ability to easily link the vendor invoice, the purchase order, and the receiving report (goods receipt) to all
unified purchase order, invoice, and goods receipt data in all relevant ledger entries and reports.
System shall provide user the ability to setup invoice matching tolerances (upper & lower) in order to enforce the following, at a
minimum,
a) Invoices that match the details on the purchase order for the price and quantity should be automatically released for paymen
IF match tolerance is met.
b) Invoices that do not match the details on purchase order (according to tolerances) for the price and quantity should be
automatically blocked from payment.
System shall provide AP Manager the ability to manually remove the payment block (unblock) when discrepancy (ies) with vend
have been resolved in order to release the invoice for payment (for cases where the invoice and/or good receipt did not fall with
the PO matching tolerance)
System shall provide AP staff or the Vendor the ability to scan the invoice using OCR (optical character reader) and have an
invoice record created automatically as a payable in the Invoice Ledger in ERP
System shall allow AP user to enter invoices in the AP system that are to be paid via Credit Card
System shall provide AP staf the ability to import accounts payable invoices in bulk, including fixed assets (e.g., from a
spreadsheet such as excel) in order to allow AP staff to post a large quantity or group of invoice transactions simultaneously to
ledgers.
System shall provide an AP staff the ablity to flag an invoice as 'fixed asset' in order to auto generate an asset card when invoic
is posted to AP Ledger
System shall provide the ability to create an intuitive PO/Invoice Approval workflow, including designated Approvers, in order to
allow purchase orders and invoices to be automatically routed through the workflow to be approved.
Workflow approvers must include the invoice/Purchase Order initiator and at least one level of approval
i.e:
a. Invoice/PO Initiator
b. Initiator's Manager
System shall allow user in the approval workflow hierarchy to add notes to the Purchase order even though the PO/Invoice
amount execeds their approval threshold
System shall provide an AP Manager the ability to assign backup approvers to each assigned approver in all of the AP approva
workflows (PO approval, invoice approval, credit card transaction approval), in order to allow approval coverage when the
assigned approver is not in office.
The backup approver will have the same approval capabilties as the assigned approver.
When the Requester (the staff member who submitted a PO, Invoice, or Credit Card Authorization Request) gets their
PO/Invoice/Credit Card Transaction approved at each dollar threshold approval tier, the system shall immediately notify the
Buyer's entire chain of management that the Buyer's item was approved.
System shall provide the ability to create a staff hierarchy that lists the employee's complete management chain, in order for the
ERP to send notifications to the employee's management chain (ex - AP Invoice Approvals, etc)
System shall provide a Purchase Order Approval work area that allows AP managers authorized to approve Purchase Orders to
view all pending purchase orders needing their approval.
System shall allow the AP manager to set thresholds for Purchase Order approvals, in order to allow efficient & fast approvals o
Purchase Orders of any amount that are entered into the system.
System shall provide the ability to set up approval workflows for credit card transactions, in order to allow Payable Staff Approve
to quickly approve credit card purchases that need to be made, at user-defined dollar amount thresholds.
System shall allow AP managers to set thresholds for corporate credit card transaction authorizations, in order to allow efficient
fast authorizations of all credit card transactions.
System shall allow all transactions (e.g. invoice, purchase order, and credit cards) requiring approval to be mobile accessible.
System to provide the Approver the ability to review the invoice/PO or credit card transaction via a mobile device or email befor
clicking the Approve or Reject button.
System shall have the ability to auto-populate General Ledger for Expense entries with PO and Invoice information at the time
when Purchase orders and Invoices are approved (via the approvals process).
System shall allow an AP staff to set default Organizational Codes for recurring payables in order to auto-populate those codes
every corresponding payable ledger entry.
(Org Codes = Project, Dept, Business Unit, etc.)
System shall allow an AP staff to set payment dates for recurring payables in order to automatically release the payment to the
vendor at the pre-defined date.
System shall allow AP staff to set a Number of Payment Days for specified invoice dollar amount thresholds, in order to allow a
payable to be released automatically to the vendor on the pre-set date if that payable is under the corresponding dollar amount
threshold.
System shall provide GL staff the ability to configure general ledger, fixed asset ledger, and vendor ledger in a way that allows A
staff to specify if unit cost should or shouldn't include tax in ledger posting, based on data entry of the AP invoice
the Customer is no longer actively billing and where there is an aged credit balance over a number of months since the posting
date of the last invoice) and to automatically post debit to customer card, credit to vendor card, & debit to open (negative) credi
balance – with ability to review all refunds prior to posting (and either reject or approve)
System shall provide user the ability to select any aged credit balance from the General Ledger for a customer and auto-post a
corresponding refund to the customer account.
System shall allow AP staff to set up only one vendor instance to use for issuing refunds.
System shall have the ability to post a refund directly to a Customer Account
the Customer has no invoices remaining to be sent & where credit balance is >= 6 months old), and the ability to automatically
post a corresponding vendor debit memo and refund payable to the customer account
ERP GL should provide the ability for a user to post a refund directly to a Customer Account (along with refund type =
ach/check/or credit card)
System shall have Ledger controls to detect and prevent posting of duplicate invoice, duplicate payments and duplicate refunds
System shall provide a Travel Expense module to allow users to manage end-to-end travel expenses including but not limited to
booking of travel to payment/reimbursement of expenses.
When an AP staff enters an invoice in the GL for a payable where a down-payment has been made to the vendor, then the syst
shalll notify the AP staff that the $ amount/down payment was made, and give ability to deduct the down payment from the invo
balance due.
System shall allow AP staff to generate and print accounts payable checks on demand
System shall have the ability to consolidate multiple invoices for the same vendor on one check, and itemize the invoices (invoi
numbers) on the remittance advice.
(e.g. useful if you send your supplier one payment to cover multiple invoices. When you record the payment, you can also
produce a remittance advice, which you can then send to your supplier to let them know which invoices you’re paying.)
System shall provide AP staff the ability to print accounts payable checks in foreign language and in foreign currency
(e.g., helpful for foreign entities that have different currency and language)
System to maintain the following languages, at a minimum:

a. English
b. French
c. German
e. Spanish
System shall provide AP staff the ability to void checks by check number or by group of check numbers.
(e.g., ability to a perform mass void)

System shall provide AP staff the ability to capture the reissue reason for a check based upon a drop down menu of reasons (e
canceled check, lost, etc.).
Ie user enters a check re-issuance, and selects a re-issuance reason from a drop down list, and the reason is saved wit the
payment entry.
System shall have the ability to support different payment types (Check, ACH/EFT, Credit Card, Wires, etc..) in order to allow K
to pay each vendor according to pre-defined payment routes
System shall provide the ability for vendor to set up their account (ach and routing) info via the portal
System shall provide AP staff the ability to maintain terms of payment offered by a vendor in order to take advantage of invoice
discounts when payment is made within certain time frames from the invoice date
System shall allow for Payment by credit card directly from the AP system
The system shall have the ability to auto-post check payments from the corresponding tax expense ledger entry, in order to allo
AP staff to issue electronic checks for all tax payments: regular State/Federal, Income, States Sales & Use Tax, Annual Busines
License Taxes, use tax
System shall provide AP staff the ability to post pre-paid taxes to the appropriate balance sheet account
When an AP payment is made via ach, echeck, or wire (and the corresponding payment remittiance is sent from the Bank to the
ERP using the Bank Interface), the system shall auto-post the payment information in order to auto-update the correspoinding
inovice/PO as "paid"
System shall have the ability to auto-post (and manually post) all vendor payment transactions with the specific locality where th
transaction originated – locality should include country, state, city, etc
System shall have a vendor portal that allows 2-way communication between ERP and vendors in order to perform the followin
at a minimum:
a) vendors to be able to submit invoices (and other docs)
b) vendors to be able to view outstanding invoices
c) vendors to be able to view payment status
d) portal to provide real time payment information
e)allow ERP users to request invoices (and other docs) from vendor
System shall have the ability to integrate with the KLD email system in order to allow any incoming electronic mail from outside
the organization to be routed to a shared inbox where authorized users can retrieve messages from the queue.
(e.g. AP invoices sent by vendors)
System shall have the ability for approval of invoices locally based on org hieararchy within cost center.
System shall have the ability to have one global AP processing Inbox to be used as an imaged invoice repository.
System shall have the ability to have OCR capability built into the ERP.
System shall have the ability to triage and assign invoices to AP processors.
System shall have the ability to default to invoice requestor's information from HCM based on the employee's accounting string
System shall have the ability to recognize predermined rules for routing to duplicate approvers (i.e skip approver and move on t
next level approver).
System shall have the ability to pay foreign vendor from the US to a foregin country in ACH (preferred) or by wire.
System shall have the ability to receive and flag an FA invoice and automatically feed into FA sub-ledger.
System shall have the ability to allow for local payment approval but centralized payment processing.
System shall have the ability to provide the funcationality to support purchase categories must be available.
System shall have the ability to support PO invoices that have values default to the PO when the invoice is created.
System shall have the ability to provide the functionality that recognizes if a Journal Entry or a transaction has an incorect codin
The system should have the ability to FAIL or not accept information and route the entry to an error suspense account for furthe
review.
System shall provide the ability to provide tolerance for PO matching.
System shall provide the user the ability to ensure that sales and use tax are being captured separtely/accurately on the Vendo
invoice.
System shall have the ability to calculate invoice amounts for approval based on Sales Tax setting but the user shall have the
ability to enter net amount of Sales Tax.
The system shall allow that when an inovice is matched to a PO, the matching (and associated Tolerence Threshold) shall be n
of VAT amount
System shall provide the ability to create and maintain an enterprise wide, customer master file which interfaces with other ERP
modules, in order to allow auto-population of customer data into payment ledger entries.
System shall provide the ability to create and maintain an enterprise wide, product master file which interfaces with other ERP
modules, in order to provide a single view of products across the enterprise and to distribute this master information to all
operational and analytical applications.
System shall allow a designated system Admin user to add, update, and delete customer master data.
Customers can be created in bulk.

The Customer Master should have the ability to specify the customer’s country (Spain, Germany, UK and France, US) in order t
send customer invoices according to locality requirements (language, currency, etc).
System shall allow user to upload credit memos from Excel via a user interface.
System shall allow the end user to configure the revenue and tax allocation account numbers where a credit memo is allocated
(after being either uploaded through an Excel interface or received via a data feed from the CRM interface - or created manuall
System shall prevent posting of duplicate credit memos.

System shall have the ability to link the Sales Order to the customer invoice, in order to see invoice payments for each sales
order.
The AR/billing module shall allow internal users to issue refunds to customers using a billing method established for that custom
(credit card, ach), by entering the refund amount and type - from the customer's available configurations for 'type' (credit
card/ach/echeck).
System shall provide AR staff the ability to build customizable invoice templates based on the product(s)/Brands for which the
customer is being billed.
System shall have the ability to determine sales tax/VAT collectability at the customer level.
System shall have the ability to support different payment types (Check, ACH/EFT, Credit Card, Direct Debit, Wires, etc..) in ord
to allow KLD to receive and auto-post payment from each customer according to pre-defined payment routes (where 'payment
route' is a pre-established connection to a customer's bank/payment interface).
System shall have the ability to re-apply customer payments made in AR /Customer payment system
System shall provide the ability to configure the customer in KLD Bank/Customer Bank, in order to receive ACH/Wire, and Direc
Debit payments from the customer’s country (Spain, Germany, UK and France, US)
System shall provide a bank Reconciliations module which processes bank transactions (from external banks) and the
corresponding GL transactions in order to generate the Variance Report.
System shall have the ability to capture customer Down Payments (through the customer payment interfaces) so that when the
payment is received by the ERP GL, it is stored as a Down Payment to the Customer Account.
When the ERP GL receives an invoice for a customer bill, the System shall automatically detect that the customer has a Down
Payment and apply the down payment (portion that matches the billed amount due) to the invoice, in order to generate the data
feed with the adjustment amount due.
System shall have the the ability to apply multiple customer payments against a single invoice, in order to allow installment
payments.
When an AR payment is received via ach, echeck, or wire (and the corresponding payment remittiance is received from the Ban
to the ERP using the Bank Interface), the system shall auto-post the payment information in order to auto-update the
correspoinding inovice as "paid"
System shall have the ability to auto-post (and manually post) all customer payment transactions with the specific locality where
the transaction originated – locality should include country, state, city, etc
System shall have the ability to receive an invoice and send a receipt acknowledgement.
System shall have the ability to book transactions on multiple currency by country.
System shall provide the ability to transact in multiple currencies out of the same ledger and/or LE.
System shall provide the ability for all the Alloc8 features.
System shall provide the ability to identify tolerance account to automatically book variances of a certain threshold left on the
invoice.
System shall provide the ability to provide predictive learning.
System shall have ability to access invoices and customers to submit invoices via mobile devices.
System shall provide users with the ability to do any or all of the following in one step:
1) Generate open invoices
2) Generate current dunning letter (letter applicable to current days late on invoice)
3) Send both to customer / vendors
(e.g., hit one button and dunning info and open invoices are sent to customer)
System shall provide the ability to validate field values within the invoice entry screen prior to posting to avoid coding errors.
e.g., Source of coding errors include:

a) Negative discounts being entered
b) Carriage return / data entered in wrong place causing incorrect posting
c) Escalation or price increase errors (current month compared to previous month)
System shall not allow user to bill/post a payment for any desired period: past, current, or future, even when accounting period
closed.
System shall have a Customer portal that allows for Bill presentment and payment processing.
System shall provide multiple options for the way to send customer invoices, including:
- having multiple recipients
- ability to send via e-mail
- ability to print (in order to mail)
- customer portal
- ability to set a preferred method (usually email)
System shall provide Billing staff the ability to maintain KLD terms of payment which consist of payment discounts extended to
customers for certain payment dates (e.g., if customer makes a payment within 10 days of invoice date - 5% discount, or within
days - 2% discount, net due 30 days)
System shall have the ability to show payment terms on invoice with corresponding dollar amount due.
Example:
a) 5% discount if paid in full within 10 days - Net due amount $475
b) 2% discount if paid in full within 20 days - Net due amount $490
c) net due 30 days or full payment - $500
System shall allow the business user (Contracts or Billing/Collections) to specify the text to appear on a customer invoice
containing a price escalation.
The system should allow the user to set this text to be the same for all invoices, or different for any invoices (completely flexible
System shall automatically apply user-defined Escalation invoice text to the invoice when the ERP receives information from the
CRM interface that a specific invoice contains a price escalation.
System shall have the ability to post the correct variable credit card fee rate for the corresponding customer payment (received
from Billing System interface)
Example, customer pays with Amex 1.7%, Billing System sends 1.7% to ERP, ERP posts 1.7%, etc.
System shall provide Billing staff the ability to capture critical customer information including email address, key contact
information, etc… , in order to auto-populate that data across all segments which need customer data (invoices, etc).
System shall provide Billing staff the ability to assign customer to a Corporate region, Collections Staff Memeber, and one or mo
GL companies.
System shall provide an Admin user the ability to flag a customer as 'inactive', in order to prevent future billing or any other
customer-related system processes.
System shall provide Billing staff the ability to establish parent child relationships between customers, in order to bill to parent
entitites, report on parent entities - etc.
System shall have the ability to create invoice lines based on details received from the interface to the 3rd party CRM.
System shall have the ability to support invoice creation and presentment in multiple languages (spanish, French and German a
least) in order to allow a customer to receive their bill in their local language.
For cases where an approved invoice subsequently has a dollar amount adjusted, a notification should be sent to all invoice
approvers, and there should be the ability to re-route the invoice back through the approval workflow.
System shall have the ability to support manual payment application
ie - capturing a manual check or otherwise entering a payment manually for any reason
System shall have the ability to seamlessly import lockbox files and apply payments based on various matching rules that ensu
there is a customer/invoice match before posting the payment.
Matching Rules:
a) If customer provides an Account # and an Invoice #, the system will check to ensure invoice goes with that account. If not po
an error msg
b) System will post to Invoice #'s only or to Account #'s only.

The System's payment application shall be PCI compliant
(e.g., set of security standards designed to ensure that companies that accept, process, store or transmit credit card information
maintain a secure environment.)
The payment application shall be SEPA compliant
(i.e the new format for cross-border Euro bank transfers).
System shall have the ability to suppress dunning letter generation at the customer level
System shall have the ability to trigger email notifications to the customer based on user-entered collection activities for the
customer (e.g., customer's promise to pay by a certain date should send an email notification to customer confirming that paym
is expected on stated date. etc..)
System shall have an Internal Customer Work Area that provides the ability for business users to capture and centrally store an
details about a customer in order create customer profiles (where a 'profile' is the Master data plus any other customer
data/interaction).
e.g. Ability to capture conversations and other interactions with customer via customer portal, email, phone call, collections issu
etc.
The system's localization packges shall allow users to view ERP screens in local language (while the data entered is on the
original form)
System shall allow customer to view and update their own customer information via a centralized customer portal (e.g. custome
personal info, address, email etc.)
System shall allow customers to access the customer portal to view invoices, dunning letter, statements, and to request
invoice/billing adjustments
System shall provide the ability for customer to effect payment on open invoices (e.g., Credit Card, ACH, Direct Debit for UK
clients and European entities) via a centralized customer portal
System shall provide the ability to automatically send email notifications to customers about expiring or declined credit cards via
centralized customer portal
System shall allow an administrator to send mass email communication to customers or group of customers
System should allow for easy credit/rebill adjustments that do not require 10 approvals or too much manual processing. Ie. An
invoice is selected to be credited, immediately following a clone is created and can be edited to get to the rebill amount.
System should allow for easy credits that do not require total manual entry. Ie. Collector chooses (clicks) the invoice to credit, e
the amount if applicable, and sends for approval. Approver reviews data and posts. All should be done without having to worry
about G/Ls because that should be handled on the backend.
System should allow for easy cloning of invoices in the event of multiple manual invoice entry.
System should allow for different billing locations for different brands.
System shall provide the ability to send email notifications to clients that receive a renewal increase and go over their 'Payment
Threshold'
System shall provide the ability to send email notifications to clients for 'Welcome Letters' which are sent out through Mail Merg
via the tellus mailbox,
System shall have the ability to create an invoice on behalf of other entities centrally w/entities legal name on the invoice.
System shall have the ability to support the creation of different types of contacts for billing and other purposes.
System shall feed customer relationship data from CRM solution to billing system.
System shall have the ability to attach reference document at the invoice header level, invoice line level and customer level.
System shall have ability to access billing system and customers to pay invoices via mobile devices.
System shall have the bility to distribute invoices via email, postal mail and email via customer portal.
System shall have the ability to build approval workflows within the ERP for billing invoices, credit memos.
System shall have the ability to automate credit memo for certain scenarios for re-curring billing, sales tax exemptions, etc.
System shall have the ability to provide receipt images from travel and expense system to the client.
System shall have the ability to bill the customers at different site levels/centralized(customers AP shared services).
System shall have the ability to have doc date (date invoice is created in AR-not GL) , posting date (posted in GL-rev rec date),
service period (start/end date of billing period), as separate dates in customer detail.
System shall have the ability to have downpayment (prepayment). Customer will pay a credit on account for customer to prepa
but not in a regular invoice. It is a contract that includes downpayment information. (med)
System shall have the ability to have installment billing.
System shall have the ability to initiate a refund off the customer account based on the credit memo. Needs a debit AR subledg
and credit to AP.
System shall have the ability to have a credit approval workflow. Concessions (approved by sales exec distro setup in Salesforc
integrate with ERP.
System shall have the ability to consolidate invoices based on relationship.
System shall have the ability to generate billing invoices in real time.
System shall provide the user the ability to automatically trigger a capture transaction when an invoice is posted.
The system shall provide the user the ability to perform internal credit card authorizations.
The system shall have the ability to create payment entries for sales orders so that duplicate entry of the information is not
necessary.
**DST related**
The system shall provide the ability to tie prepaid order with bill coming from CRM.
The system shall have the ability to update/live synce contract data from CRM to the ERP.
The ERP budgeting module shall be able to track budgeted and actual spending amounts by all existing Accounting service
offerring and transaction-level user-defined Organization codes. Example – budgeted and actual payroll expense for ‘Company
across Company A’s departments.
The budgeting and forecasting system shall be able to project payroll expenses using user-defined assumptions (variables) upo
Assumptions include:
7-percentage of merit bonuses that will be achieved
System shall have the ability to forecast Commission including end user-input forecasted commission rates as a % of Sales.
System shall have the ability to forecast operating expense pre-payment projections by allowing the end-user to input the # of
planned pre-payments, the status of pre-payments (continue, revoke), and the pre-payment schedule.
System shall have the ability to forecast operating expense by allowing the end user to input the list/count of hw/sw spending
agreements & associated line item detail (line items can be input by Account, Business Unit, Department groupings).
The system shall have the ability to flag GL level actuals/historical transactions as EBITDA add backs.
The system shall have the ability to forecast commission by sales.
The system shall have the ability to forecast currency fluctuations (gains and losses).
System shall have the ability to keep a fixed budget rate and apply it to the actuals for more than one year. (i.e. ability to provide
an option to review actuals by fixed rate)
Workforce Planning: System shall have the ability to perform workforce planning by cost center and entity.
System shall have the ability to automatically spread topdown adjustments to cost centers.
System shall have the ability to allocate annual costs by days, months, quarters or year.
System shall have the ability to perform budget allocations for assets by line of business.
System shall have the ability to perform cash forecasting by line of business, country, region based on income statement
forecasting assumptions.
The system shall have the ability be able to perform allocations forecasting between COA string (includes country, LE, natural
acct. cost center, service offerring, sub account/activity).
The system shall have the ability to perform multi year forecasting.
The system shall have the ability to support and maintain multiple budget and forecasting scenarios.
The system shall have the ability to support what if analysis for informal what if scenarios.
The system shall have the ability to perform native forecasting based on the new COA (country, LE, natural acct. cost center,
service offerring, sub account/activity).
The system shall have the ability to add budget and forecasting only dimensions and values (includes future cost centers not ye
active in ERP, commission or vendor) not synced w/ERP to be used for specific budgetary purposes (contingency planning and
will not be used with the business).
System shall have the ability to support revenue and expense in native/local currency for all International entities; all balances
must be converted to USD for consolidation.
Budget module shall be able to incorporate year to date actual results into the budget/forecast module.
EPM Chart of Account (COA) Hierarchies should allow for planning-only child values to be added that do not exist in ERP.
System shall have the flexibility to distribute budget submission responsibility to the Budget Owner and/or Finance delegate.
Solution should the ability to view both approved and un-approved budgets.
Budgeting module shall be able to archive various version of the budget/forecast for future comparison.
Budget Solution must allow for comparison versus multiple scenarios (forecast vs budget; forecast vs prior forecast; actual vers
forecast)
Budget Solution must be able to Run Scenario Analyses to segregate the cost of hiring (impact if we keep headcount flat, impac
we keep December headcount flat, etc.)
Solution shall provide forms / templates look like for Headcount and/or OpEx and other STAT accounts or allocation based
assumptions
Solution shall be able to accept upload, smartview write-template, and/or direct entry for revenue.
The budgeting and forecasting solution shall be able to project payroll expenses using user-defined assumptions (variables) up
User-defined assumptions (variables) include:
2a-promotion increase percentage
7-percentage of target bonuses that will be achieved
Budget Solution must be able to discretely calculate the impact of merit and promotion increases.
Wages: Solution shall be able to accept employee census/roster data as well as open requisitions via API from ERP.
Solution should be able to calculate multi-year (and compounded) merit and promotion increases (i.e. 3% in 2018 and 3% in 20
based on 2018 salary)
Solution should be able to calculate pro-rated merit and promotion increases based on date of last pay increase (date can be fe
from ERP)
Temporary Employees: Solution shall be able to accept employee census/roster data with hourly pay rates and FTE assumptio
Bonus: Solution shall be able to calculate bonus expense by Bonus plan with unique target bonus achievement assumptions fo
each plan type.
Payroll Taxes: the Solution shall project expenses using user-defined assumptions (variables) upon which to base projections.
Payroll Taxes: the Solution shall be able to calculate taxes and benefits differently by Country.
Benefits: the Solution shall project expenses using user-defined assumptions (variables) upon which to base projections.
Commissions: System shall have the ability to plan target incentive comp per employee with on-top adjustment for
seasonality/sales timing.
Commissions: Solution should be able to calculate payroll taxes on any on-top adjustments to Commissions.
Headcount: Solution should be able to plan "bulk" headcount (positives and negatives) and calculate taxes and benefits.
System shall have the ability to plan operating expense with Vendor-level detail at the Chart of Account level (unique Account,
Product, Cost Center relationship).
Budget module shall allow for flexibility to plan expense at multiple levels / dimensions. (e.g. some budgets will be planned at t
vendor level; some expenses by account/cost center)
Planning templates should include prior year actuals by month using the same level of detail as the planning Solution (by Vendo
Data Agreements: Planning templates by vendor that can be shared and/or submitted by the budget owner.
HW and SW and Data Agreements: Planning templates by vendor should pre-populate any scheduled multi-period accounting
ERP (leveraging the ERP asset accounting)
Travel: Plan as a Travel dollar per head at the Cost Center level (using historical actuals); Solution should allocate budget to a
travel accounts. Plan at Parent Level, consider allocating to child level
Occupancy: Plan new locations in the same form as existing Straight-line and Deferred Rent assumptions for existing facilities.
Plan by location.
Supplies: Planning templates by Location that can be shared and/or submitted by the budget owner.
Communications: Planning templates by Vendor and Location that can be shared and/or submitted by the budget owner.
Location-based Planning (Occupancy/Supplies/Communications): System should have the ability to include a location field tha
can pull together the cost of running a facility (rent, supplies, communications, etc.).
Professional Services: Planning templates by vendor that can be shared and/or submitted by the budget owner.
Budget Solution must allow for Tagging Budget Item with an "Activity/Project Code" to segregate total cost of initiatives.
System shall have the ability to support D&A forecast based on ERP run-out of Fixed Assets and Intangibles.
System shall have the ability to plan for new capital expenditures by year.
System shall have the ability to plan for new capital assets with same amortization schedules as ERP.
System shall have the ability to forecast and budget foreign exchange rates and will need to be able to change this rate based o
the scenario. (e.g. budget, forecast, etc.)
System shall have the ability to provide net new sales by product (e.g. upload actuals from excel; upload forecast and budget fr
excel)
System shall have the ability to provide headcount by cost center (e.g. month end actual from ERP via API; Forecast from
EPBCS; Budget from EPBCS)
System shall have the ability to provide weighted average shares. (e.g. actual from ERP Stat Account; Forecast and Budget fro
Excel upload)
System shall have the ability to provide non-GAAP adjustments and tag line items in the planning solution as non-GAAP (e.g.
acquisition & integration; restructuring; etc.)
System shall have the ability to provide headcount by cost center (e.g. month end actual from ERP; Forecast from EPBCS;
Budget from EPBCS; include ERP Functional Role; include Location)
Budget solution must allow for finance user admin to consolidate inputs. (not solution admin)
Budget module shall have the ability to replicate any/all automated cost allocations performed in the GL financial close process
Solution shall provide the ability to set different user roles for the budget module: Read Vs write; access rights by department.
Budget module must allow for different levels of control/viewing/edit rights. (e.g. Financial Analyst can view/edit salary informat
for Cost Center X, but not for Cost Center Y, OR for all Cost Centers except for Cost Center Z)
System shall have the ability to create custom roles for System Admin (Add/create users, change permissions and roles) vs.
Functional Admin. (e.g. add scenarios, non GL Dimensions, etc.)
Budget Solution must allow for future period budgets to be built leveraging formulas and direct inputs to predict future revenue
and expense (Driver-based Rolling Forecast).
System shall have the ability to support Base / Current Year(s) bottoms-up detailed forecast; future years are largely driver-base
with a few manual inputs.
System shall have the ability for manual input items to include Revenue, Rent/Occupancy, Marketing expense, and Legal Fees.
Solution must have the flexibility to add adjustments on-top of any driver/historical data-based forecast.
The PO System shall provide the ability to the Finance/Accounting team to tag a Purchase Order as "Capex" in order to denote
that the PO is part of the capex budget and to track associated spending.
-this includes the ability to enter the Capex account/charge number on the PO.
System shall prevent the ability to book a payment for a Capex project where the approved budget is exhausted,
System shall provide an option to over-ride with manager approval

System shall provide a budgeting module which allows construction of an Inter-Deparment Budget.
The inter-department budget should be able to be constructed using the same data points as the data contained in the 'Capex
Expense' History & Projections reports, in order to build budgets in a uniform structure with the underlying expense
history/projections.
This means that the Financial Planning/Budget Owner user can enter the dollar amount of the specific budget need for a)each
Department and for b)each spending category within each department - where 'spending category' is defined as the [desired
subset of] data points for which expenses are aggregated in the Expense History/Projections reports.
The Project/accounting module shall allow the end user to set up Capex Project instances with coding, Owners, budgets and
Capex Thresholds
System shall provide Collection Staff the ability to configure dunning forms (collections notices that go to the customer) based
user-defined aging buckets for overdue balances (e.g. 30 days late notice, 60 days late notice, 90 days late notice).
System shall allow for the method of transmitting dunning forms to be the same as the one used to transmit the invoice (mail-
ready printout or email)
System shall have the ability for the collector to have the functionaility to view historical invoices, communication email,
matter_contract, etc.
System shall have the ability for the collector to view specific contract information (e.g. payment terms, legal signatory, etc).
System shall have the ability to capture trading community architecture. Needs to be shared between CRM and ERP and vice
versa.
System shall have the ability to provide the functionality to interface with a credit scoring tool.
System shall have the ability to predict based on trends of payments in the system predicts CF and expected payment date ran
System shall have the ability to include preset rules to assist with identifying prioritization of collection targets.
System shall have the ability to flag a customer's cash basis.
System shall have the ability to bill in arrears, advance, or other methods.
System shall have the ability for Collector Manager to determine bad debt vs credit memo.
System shall have the ability to not allow business to be done with the customer until the bad debt is removed.
System shall have the ability to notify/flag CRM via feed if a customer has bad debt before continuing to do business with the
customer.
System shall have the ability to automate customers who go default based on contract based aging schedule.
The system shall have the ability to make bad debt account (contract data) available via web service.
System shall provide Finance staff the ability to create the following elimination companies:
1- LE to LE
2- (US and foreign)
3- (foreign to foreign)
System shall have the ability to convert foreign currencies at the consolidated level to a corporate Currency (currently USD) from
any locally transacted currency. This should be done for both actuals and budgeted numbers.
System shall have the ability to convert foreign currencies to USD.
System shall have the ability to automatically eliminate intercompany balances from consolidated financial reports and trial
balance.
The system shall have the ability to prevent loading data from Country/Legal entity to the Consolidated entity without first resolv
all eliminations and intercompany transactions.
System shall have the ability to consolidate legal entities according to different hieararchies and for different reporting purposes
(e.g. for Corporate GAAP, for SEC reporting, for Local government reporting, tax reporting etc.).
System shall have the ability to consolidate legal entities according to different hieararchies (e.g. consolidation by region, count
and global).
The system shall have the ability to automatically create the of-setting elimination intercompany balances from consolidated
financials. Reports and TB.
System shall provide FA staff the ability to configure default depreciation methods for an asset class
System shall provide the ability to mass copy of one tangible or intagible assets.
System shall provide FA staff the ability to easily import mass upload capability of asset sub-ledger in order to create multiple
asset classes at once.
System shall have the ability to automatically create a fixed asset sub-ledger when a fixed asset invoice is posted to the AP
Ledger
System shall have the ability to flag the disposal of a fixed asset to prevent FA Staff from further processing.
System shall allow all Fixed Assets, Vendor, and General Ledger entries to be easily viewable from the asset sub-ledger. (all
ledger entries for asset should be viewable from sub-ledger)
System shall allow user to view Acquisition Cost details from the Fixed Asset Ledger
System shall allow user to view Unit Cost details from the vendor ledger
System shall provide the ability to automatically include assets that were acquired in the past in current depreciation calculation
(e.g. if the Asset sub-ledger was created after the in-service date, the depreciation calculation should know to include the asset
System shall provide FA staff the ability to easily select which assets to depreciate based on an advanced search criteria. (e.g.
company, date, country, asset class, depreciation type)
System shall provide FA staff the ability to set custom asset life for any asset.
(depreciation Start Date and duration of depreciation)
System shall provide FA staff the ability to easily review depreciation journal entries before posting
System shall provide FA staff the ability to post all pending depreciation entries at once.
System shall have the ability to auto-populate from the asset sub-ledger to the depreciation entry organizational Segment Code
like service offerring and cost center
Sytem shall have the ability to retroactively correct / edit asset data including retroactively editing depreciation.
System shall provide the ability to partially dispose of an asset by easily disposing one or more of its parts/disposable compone
System shall provide FA staff abilty to dispose an asset where the Book Value is not '0' or 0.
System shall provide FA staff the ability to easily dispose of multiple assets within a Company and Asset Class at once
System shall provide FA staff the ability to review disposal journal entries before posting them
be a required field). 2. Provide the option for a drop down menu of pre-defined loations (e.g. offic
System shall have the ability to handle asset conversion rate by country (e.g. assets purchased in the US for AUS).
System shall have the ability to auto create and/or auto post based on the source of JEs (e.g. subledger, external system (AX-
free text invoice to depreciate/dispose FA - does it need to be approved before the posting takes place), etc.) -ask Mark or Jeff.
you have scenarios?
System shall have the ability to maintain two sets of FA books for local and corporate reporting.
System shall have the ability to create local, US GAAP and tax books for financial reporting.
System shall have the ability to merge or split multiple invoices into one asset.
System shall have the ability to identify at requisition or AP level that POs can be assigned to one specific Asset.
System shall have the ability to perform depreciation by days, weeks, or months.
System shall have the ability to handle VAT variances for asset transfers (see Andreas diagram).
System shall have the ability to send an alert to approvers when assets are transferred from one LE to another LE.
System shall have the ability to calculate VAT based on the location of the transaction.
When an accounting segment, for which transactions occur, is added to the system (segment could be customer, vendor,
company, account, etc), the system shall provide user the ability to easily configure basic default values for the account segmen
in order to have those values auto-populate on corresponding transactions for that entity.
ex-An 'Account123' accounting segment has default Location = 'HQ', so Vendor payment ledger entries using Account123 will
have default location - 'HQ'.
Within the account segment, user should have the ability to set up account codes where the value (alphanumeric) represents a
the transaction-level components such as (account, business unit, etc) - request in a BI/Reporting meeting
System shall provide user the ability to easily create multiple instances of accounting segments at once using a 'copy' feature.
For example, ability to create multiple invoice lines at once, multiple purchase orders at once, etc
System shall provide the user the ability to do a mass upload of any type of journal entry via a user interface.
The system shall have the ability to allow/not allow Journal entry approvals (in the automated workflow) based on predetermine
rules (e.g.local reporting vs. Corporate/GAAP reporting purposes; Country, Legal Entity, etc.)
System shall have the ability to support transactions posted to one standardized, global COA and then mapped to a local GL
books for localized reporting.
System shall have the ability to provide built-in data mass loading template to mass upload journal entries, invoices, and other
transactions without the use of a third party tool.
System shall provide user the ability to perform any type of reversal including mass reversal of posted transactions (i.e, journal
entries or group of journal entries, AP/GL, AR/GL entries, etc…)
System shall provide user the ability to perform any type of re-posting of reversed entries according to business rules
System shall have the ability to reverse sub-ledger entries
System shall provide GL staff the ability to code a balance sheet account item in order to flag it as either "current" or "non curre
in reporting period.
System shall provide GL staff the ability to code an expense journal entry with any user defined activity codes:
-Activity Codes exmaples: 'Business Deal', 'Advertising', 'Non-Advertising'
System shall provide the ability to flag journal entry by entity
Example, ability to set up Legal Entity > Account hierarchies and report on all child account activity under the specified parent
Legal Entity.
System shall provide GL staff the ability to classify expense accounts as ('Personnel', 'marketing', and 'operating').
Specifically in the 'Personnel' expense accounts, there must be the ability to classify associated transactions as: wages, payroll
bonuses in the transaction ledgers.
The system shall provide GL staff the abiltity to label an account as a 'COGS' account for the purposes of SEC reporting.
System shall provide GL staff the ability to code an accounting segment as an "income statement" or "balance sheet" account
System shall provide GL staff the ability to flag account accounting segments as "Europe" or "North America" for reporting
purposes.
System shall provide GL staff the abilty to flag all transactions as 'Non-GAAP' adjustments for public reporting purposes
(e.g. Ability for all GAAP accounts to be easily setup/coded to comply with GAAP requirements of account’s locality (add the ma
ones US, UK, Poland)
System shall have the ability to be IFRS-Compliant easily while also being local-GAAP compliant
System shall have the ability to maintain revenue and expense ledgers in multiple currencies (with historical fx rate auto-applied
with rate valid at time of ledger posting)
System shall allow user to look up the chart of accounts and also any accounting segment hierarchy.
System shall have the ability to automatically feed JE’s from external systems using a API.
System shall provide GL staff the ability to export any type of general ledger entry to Excel, Powerpoint, PDF, XML, TXT, CSV
format.
System shall provide GL staff the ability to export any type of general ledger entry to Excel.
System shall provide user's with specific permissions and the ability to post prior period posting adjustments, (and also the abili
to specify that NO adjustments can be made for certain accounts or other GL segments).
In these cases, there should be a clear audit trail of what changed, viewable by a report.
(e.g. retroactively update account balances by creating and posting journal entries to a previous accounting period. User must
specify the year and the period to which they should be posted)
System shall not allow user to delete any posted Journal Entry. Journal entries can only be reversed once posted (Journal entri
created but not posted can still be deleted, with a proper audit trail)
System shall not allow user to delete any Journal Entry without the proper audit trail being associated to it.
System shall have the ability for all transaction IDs to be globally unique and frozen - no duplicates.
Transaction IDs shall be auto-generated, in order to easily refer to the same Transaction ID across any ERP entity
Ex- journal entries, invoices, Purchase Order, etc.
System shall provide the ability to code whether AP invoices, and associated GL transactions are "pre-paid" for the purposes of
expense reporting.
System shall have the ability to minimize the volume of manual JE by Allowing an approval workflow for each manual JE.
System shall have the ability to minimize the volume of manual JE.
System shall have the ability to be configured to manage ledgers locally or centrally.
System shall be able to track unrealized and realized gain/loss by country and prevent the posting of these entries for certain lo
entities based on the local requirements.
System shall provide user the ability to track the history of structure changes to any accounting segment heirarchy including cha
of accounts.
System shall be able to differentiate between reporting currency, functional currency and transactional currency.
System shall be able to track unrealized gain/loss by country and automatically calculate actual unrealized gain/loss to be
recorded.
System shall have the ability to limit user access to local ledgers by country and/or legal entity.
System shall have the ability to support close processes. (e.g. close periods for all books centrally by a single click for a period)
The system shall have the ability to control intercompany entries to avoid incorrect In tercompany entries posting between legal
entities via an approval workflow or other automated controls.
The system shall have the ability to automatically create the of-setting intercompany entry in the corresponding Legal entity bas
on pre-defned rules at the GL and/or consolidation level.
System shall have the ability to have up to the minute updated consolidation in order to perform, at a minimum, the following:
- Auto-calculate and auto-post the elimination entries
- Enable real time viewing of all Financial Consolidation reports (Income Statement, Balance sheet, trial balance, etc).
System shall provide the ability to code all intercompany accounts as either:
1) Interest is Charged
2) Interest is not Charged
Using the coding for intercompany accounts, which identify each account as 'interest bearing' or 'not interest bearing', the syste
should auto-calculate and post interest to the 'interest bearing' accounts as follows:
1-the GL user enters an intercompany interest rate in the appropriate ledger
2-the system auto-calculates and posts the interest to the 'interest bearing' accounts according to the calculation for the specific
type of interest rate that was entered:
(Example - calculate [rate (x) avg balance for last 2 years] * .25)
System shall have the ability to automate eliminations between statutory accounts by country (across LEs).
System shall have the ability to automate revaluation for intercompany entries by country (functional currency by country).
System shall have the ability to provide automated intercompany transactions based on preset rules.
System shall have the ability to provide the functionality that recognizes if there are no preset rules for Intercompany transaction
FAIL the transaction or not release to the suspense account.
System shall have the ability to consolidate with intercompany eliminations by country, region and global.
System shall have the ability to comply with gov regs around lease acct for lease real estate and equipment.
System would need to calculate the hold a training fund as a mandatory requirement from the government.
System will need to hold historical payslip information for 5 years.
Payroll will need to see the saving due to social charge deductions or tax savings
System will need to be able to do benefit in kind tax calculations for each monthly payroll depent on Pension contribution and
other benefit allowances that are subject to tax.
System shall have the ability to allow multiple tax years.
System shall have the ability to enable net to gross calculations.
System shall allow for shadow payroll processing for international employees.
The system shall be able to support employment based on "at-will" employment with each employee.
System shall have the ability to provide unlimited number of payrolls, if an extra payroll cycle is required.
System shall have the ability to be available for keying data during all phases of the payroll process.
System shall be able to multiple payroll schedules (e.g. bi-weekly and monthly).
System shall have the ability to run separate payroll corporate groups for each location.
System shall have the ability to add unlimited locations and new corporate structures (e.g. department, business units, function
etc).
System shall be able to provide unlimited number of Earnings Codes or Pay Types.
System shall have the ability to provide unlimited number of Deductions Codes, both pre-tax and post-tax.
System shall have the ability to provide direct deposit and paper check hard copy versions are available.
System shall have the ability for Payroll Administrators to print “live checks” on demand (including Manual / Off Cycle Checks).
System shall have the ability to allow for payments to be loaded to “VISA” (or other major bank) “Pay Cards” / Debit Cards.
System shall have the ability to provide pay slips/check stubs to employees each pay period (electronic and/or paper).
System shall have the ability to provide stub descriptions for all earnings, deduction codes and stub earnings details for both
current pay period and Year-to-Date accumulators.
System shall have the ability to allow for Direct Deposit to up to 3 destination bank accounts per employee.
System shall have the ability for payroll to accept input from and send output of earnings information from/to multiple sources
(time-keeping, benefits systems, etc.).
System shall have the ability to allow payroll to accept input of deduction information seamlessly from multiple sources, most
especially from Benefits Admin partners.
System shall have the ability to schedule specific earnings for a specific payroll cycle (e.g. monthly commission, expat COLA, c
allowance, etc).
System shall have the ability to specify start and stop dates for Earnings and/or Deductions.
System shall have the ability to allow Administrator to add new Deduction Codes.
System shall have the ability to allow overrides of data for rates, taxes, supplemental tax rates, deductions, but keeps previous
input visible.
System shall have the ability to manage garnishments, liens, withholdings and remittance.
System shall have the ability to support inputed income or taxable benefit withholdings, when required.
System shall have the ability to acommodate Shift Differentials, if needed.
System shall have the ability to support computations of pay, vacation, overtime pay, apply break rules, sick leave,
maternity/paternity, etc. in compliance with country/state laws.
System shall have the ability to calculates annual bonus payouts.
System shall have the ability to commodate and perform complex calculations including multiple pay rates for same task or
activity.
System shall have the ability to acommodate Specialty Pay Types (e.g. luncheon voucher, travel reimbursement, training bonus
local travel allowance, wellness discounts on benefit deductions, etc.).
System shall have the ability to acommodate and track Incentive Pay (e.g. bonuses and awards, commission).
System shall have the ability to calculate pay based on copyright type of work (e.g. certain job titles in Poland and Italy are paid
differently for copyrighted work).
System shall have the ability to load mass payroll changes (e.g. merit increases, COLA’s, etc.) via simple spreadsheets (e.g.
Excel, CSV or other).
System shall have the ability to manage all Tax Reporting (federal, state, municipal, unemployment, social insurance) per count
including in person remittance as necessary (e.g Japan).
System shall hae the ability to produce Tax forms for employees and/or contract workers across the globe (T4, W-2, 1099, 1095
etc.).
System shall have the ability to produce 1 (one) W-2 (or international equivalent annual earnings statement) for an employee if
they change employee status (rehires, exempt to non-exempt or have an immigration status change).
System shall have the ability to customize information on pay slips.
They system shall have the ability to provide employees on-demand access to view and change their payroll information via on
self-service tools (view/print pay slips, change address, W-2, change W4, change state withholding, change direct deposit).
System shall have the ability to provide additional payroll functionality that will need to match KO process for uploading to ADP.
System shall have the ability to display PTO balance for all hourly employees from the absence management system.
The system shall be able to comply with local employee payroll reporting to tax and labor government authorities in all EMEA
Countries.
The system shall be able to support employment based on a personal contract with each employee.
System shall have the ability to allow for proper handling of 13 month salaries.
System shall have the ability to provide Manages requests and approval process. Information should appear either regularly on
pay stubs or in another accessible way. Must allow multiple leave plan setup and be compliant with state and local laws (ie: S.F
Cali).
System shall have the ability to manage comp time and over time payment.
System shall have the ability to support a workflow to approve timesheets (e.g. manager or delegated manager).
System shall have the ability to store and retain payslips for all employees.
System shall provide Purchasing staff the ability to create and re-use Contract Agreements/Master Agreements (via templates)
System shall provide Purchasing staff the ability to convert any awarded solicitation to a contract (ability to export solicitation
information to a contract file upon user status change to 'awarded')
System shall provide the ability to store contract language.

The template creator should have the ability to control permissions or rights to change/update a Contract, or Access to contract
System shall have the ability to create any type of contract, including buy-side, sell-side, and non-monetary agreements (e.g.
Intellectual Property, Non-Disclosure Agreements, etc.).
System shall have the ability to manage contracts in multiple formats, including MS-Word compatible and PDF.
System shall notify suppliers (vendors that have been set up in the Vendor Master) that contracts have been drafted and allow
them to log in and evaluate/ agree or decline based on proposed terms.
System shall notify Purchasing Manager and/or a group of internal users of any requested contract edit made by an external us
(e.g. supplier).
System shall provide Purchasing staff the ability to assign compliance items (KPIs) to contracts, allowing users to track the
fulfillment of these KPIs and also be able to automatically issue alerts to Purchasing staff/Vendor when a KPI is not met.
Example, Compliance Item could be set as Price Variance KPI (where price agreed to in Contract and Price Billed are different
a certain amount above a threshold), and a vendor subsequently sends a bill for a price above the threshold.
Then, the alert would be triggered and notification sent to Purchasing staff/Vendor.
System shall provide the ability to add electronic signature to contracts via an E-signature or DocuSign interface.
(e.g. KLD representative will sign the contract using E-signature or DocuSign. Vendor representative will also sign using E-
signature or DocuSign, then interface will automatically transfer the signature to the contract)
System shall have the ability to support punch out catalogs.
System shall have the ability to flag unbudgeted requisitions and automatically route to finance for approval.
System shall have the ability to send IT requisitions for approval/review based on purchase category.
System shall allow Finance end users to input Capital Expense thresholds for any user-defined Project spending category (whe
'category' is a set of transactions that occur under specific Accounting Segments/GL Coding) in order to subsequently report on
Capex spending and budgeted amounts (where the amounts meet the Capex treshold).
System shall have the ability to split bills by project to multiple customers based on contract details.
System shall allow for alternate billing item/product description to be displayed on invoices based on client specification on the
sales contract.
The System shall allow for alternate billing item/Product description to be displayed on invoices based on clent specification on
the sales contract
System shall have the ability to calculate actual and projected Project-level expenses using Line Item detail from Expense
Ledgers.
System shall have the ability to define/configure non-financial performance metrics in order to set budgeted performance values
and measure actual performance against budgeted values.
Non-Financial metrics include:

1-Brand Preference - market cap or other quantitative position of a KLD brand compared to a competitor brand for same type o
product
2-Take Rate - how well customers and prospects respond to CTAs (Calls to Action) - example: % of emails sent offering free
demos that user selected to schedule (helps measure ROI of CTAs)
3-Customer Retention & Churn - Retention = # of customers that continue to purchase and Churn = # of customers that drop of
and stop purchasing over time
4-Customer Experience - tools to build KLD-specific metrics around all touchpoints that customers interact with KLD staff (sales
call center, etc)
5-Innovation - Adoption rate of new products
6-Market Share - amount of customer dollars in market invested into KLD
System shall provide the ability to set different user roles for the budget module: Read Vs write; access rights by department
System shall provide the ability to enter Project level purchase orders for Project Budgets (non-capex) in order to track expense
against project budgeted amounts.
System shall have the ability to forecast (revenue, opex, personnel exp) at a Consolidated level (above the project level – like b
location or even globally)
System shall provide the ability to view approved budgets globally (from the budget approval workflow)
System shall provide user the ability to search Vendor documents such as contracts, contract attachments, etc...
System shall allow full text search functionality (e.g. search for text, words, phrases, etc.) within any contract and/or template
contained in the system, including the ability to search attached documents (in PDF, Word or HTML formats) in order to find all
instances of a document with the entered phrase.
System shall provide Purchasing staff the ability to copy / transfer purchase requisition data to a corresponding purchase order
without re-keying (e.g., requisition to purchase order).
System shall provide AP staff the ability to create a PO for multiple vendors, for cases where the PO needs to be created at the
Project Level.
System shall have the ability to automatically turn invoices into Purchase Orders and should pass two way matching.
System shall have the ability to provide purchase category rules based on items purchased.
System shall have the ability to enter a requisition into local currency and translate into USD; all requisition approvals should be
done in USD.
System shall be able to automatically convert Requisition to PO (e.g. not a manual conversion from Req. to PO)
System shall be able to provide support for account coding needs and to automatically route the requisition for approval.
System shall provide the ability to match Purchase Orders to the invoice.
System shall have the ability to only setup approval routing for all transactions to the cost center hierarchy.
System shall provide the ability to track certain projects and / or activities.
System shall provide the ability to create alternative routes of approval based on preset rules.
System shall provide the ability to create an approval workflow prior to cash disbursements by country (Accounting activity, not
Treasury).
System shall provide support for the daily load file (open billing for LT projects) process that loads billing transactions into AX. T
feed collects billing metrics from the legacy DataMart for active projects and loads them into AX item journals. This process is
running in the early morning hours of each day.
The automated load process is also used for user created files that need to load large amounts of data into open billing. Users
create a csv file and put it into a specific directory where it is processed.
System shall have the ability to create the following Purchase Order types:
1. Purchase Order from Contract (without requisition)
2. Create a stand alone Purchase Order
3. Create a Purchase Order for Projects
System shall have the ability to create the following Requisitions:
1. Catalog / Punch-Out
2. Non-Catalog / ad-hoc
3. Copy an existing requisition
System shall have the ability to calculate requisition amounts requested for approval based on VAT setting but the user shall ha
the ability to enter net amount of VAT.
Purchase Orders amounts shall be net of VAT or Sales Tax

Purchase Orders amounts shall be translated to USD first for all countries and then routed for approval
Requisitions amounts shall be translated to USD first for all countries and then routed for approval
The system shall allow for an approved PO to be amended with no additional approval only if it meets one the the below criteria
1. Updated requested amount is less than the original approved amoount OR Updated requested amount is within a predefined
threshold (e.g. +- $100 or +1%).
System shall be able to analyze the sales of all offerings and quantitatively determine standalone selling price (SSP) both unde
ASC 606 and IFRS 15.
Under ASC 606 system shall be able to identify SSP on distinct performance obligations using a similar approach as identified
above.
System shall be flexible enough to allow stratifications of agreements and the ability to apply SSP based on qualitative factors t
can be input into the system
e.g.
Attributes related to the calculation of the SSP such as contract groupings should be able to be identified in the system and the
there should be the flexibility if we identify which should be grouped together that the system can apply the SSP calculation to t
identified populations.
System shall have the ability to ensure that the ending value after the rev allocations between line items / SKUs that have
occurred does not exceed the initial value of the original transaction
System shall be flexible enough to be able to calculate the SSP for each SKU / service offerring code at any frequency
management requires
System shall have robust reporting capabilities and at a minimum be able to report at the individual multiple performance
obligations (MPO) (bundle) level by line the SSP related to the product, the last date of the assessment and any adjustments
necessary
System shall include custom descriptive error handeling messages in case any function or data transfer from KLD's source
systems has not completed correctly or sufficiently.
System shall be able to identify current and long term deferrals and be able to report on them.
System shall be able to identify backlog of revenues by service offering.
System shall be able to account for changes in Revenue Recognition Entries resulting from reversals of contracts line items.
System shall have the ability to standardize contract setup system (rev recs / rev man engine).
System shall have the ability to feed billing data from the billing system.
System shall have the ability for all products to be setup in the billing module.
System shall have the ability to create a hieararchy for service offerrings.
System shall have the ability to automatically generate deferred or recognized revenue based on contract details (billing lines) a
invoices are posted.
System shall have the ability to automtially populate the rev schedule for the life of the contract based on the type of the contrac
(e.g. hosting, t&m, subscription, processing).
System shall have the ability for techincal accounting to manually override the rev schedule that was created for the invoice.
System shall have the ability to recognize revenue on a monthly basis.
System shall have the ability to create a link with the stored image of the contract in CRM (Salesforce).
System shall have the ability to determine the shipping points for revenue (e.g. DST - shipping point, LT - service period).
System shall have the ability to add a to flag for contracts that have volume discounts, service level agreements, or other 1 off
options that aren't part of the original template. Route for review and approval by technical accounting before rev recongition to
occur.
System shall have the ablity to calculate SSP by netting out CMs, invoices, contract line items, and other revenue adjustments.
System shall have the ability to allow manually created revenue recognition schedule in the revenue recognition module as an
exception process, in the cases of nonstandard contracts.
System shall have the ability prior to billing, to match the invoice to sales order for exceeded contract terms.
System shall have the ability to flag contracts that have volume discounts, service level agreements or other terms that are one
or are not part of the original template .
System shall have the ability to create non standard contract based on a rev schedule. it's an exception process.
System shall have the ability to flag non-standard contract as they come in from the CRM, and route those through the approva
workflow.
System shall have the ability to include standardized, unique identifiers for customer names, sales reps.
System shall have the ability to have one single source of information to store sale commission data.
System shall have the ability to calculate payroll taxes on any on-top adjustments to sales commissions.
System shall have the ability to change the sales commission data (billed or credited data - e.g. billed rev for managed review w
need to include accrued revenue)
System shall have the ability to provide accurate/clean data required to calculate commission.
System shall have the ability to support countries that require the ERP system to handle depreciation.
System shall provide the ability to add an asset with different values in corporate books vs tax books.
be a required field). 2. Provide the option for a drop down menu of pre-defined locations (e.g. offi
System shall provide the ability to record tax as part of intercompany loan transactions.
System shall provide user the ability to break out the sales tax vs use tax by location.
System shall provide user the ability to calculate GAAP and tax depreciation.
System shall provide Tax staff the ability to capture whether a transaction is 'tax sensitive' or 'not tax sensitive' in order to help
estimate tax payments/credits due.
System shall allow user to view transactions by legal entity.
System shall have the ability to maintain quarterly tax schedules and rates going into financial statements.
System shall provide the user the ability to reset acquired fixed asset values in order to reset depreciation.
System shall provide the user the ability to maintain historical cost value, historical tax depreciation and historical useful lives
depending Fixed Asset transactional structure.
System shall provide a Sales Taxability Matrix to record the appropriate tax on products/services offerings.
System needs to be able to extract only items that are taxable.
System needs to integrate with state tax website (if the option is available by the state).
Tax tool (to replace STO) shall have the ability to extract use tax (e.g. currently there is a separate extract pulled from AX).
System shall have the ability to pay invoices based on contract terms.
System shall have the ability to have a central repository and maintain contracts.
System shall have the ability pay recurring, variable lease payments based on a set schedule.
System shall have the ability to enable users to search Contract information by key words, vendor names and contract terms.
System shall have the ability to provide an approval workflow for new contracts created and seamlessly capture the new contra
data to be stored in a central repository.
System shall have the ability to create an approval workflow based on compliance regulations that impact KLD's compliance an
regulatory standing.
System shall have the ability to create an approval workflow based on a threshold amount.
System shall have the ability to provide PO matching with signed contract.
System shall have the ability to provide an automated alert/notification of the requisition, contract and PO progress.
System shall have the ability to automatically generate an invoice for self service managed review sub-contactors.
System shall have the ability to allow a parallel first level approval workflow (first level US approver and from invoice or PO line
amount; multiple cost centers and requisitions
TOTAL
Does Vendor Meet the
Priority Global/Country Specific?
Requirement?
Low (Nice to Have) Does Not Meet
Meets – Out of the Box –
Low (Nice to Have)
Current release
High (Must Have)
High (Must Have)
Yes, Vendor can meet the

High (Must Have)
requirement
High (Must Have)
High (Must Have)
Medium (High Value Add)
High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)
Low (Nice to Have)

Low (Nice to Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have) Global
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)

High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
Medium (High Value Add) EMEA

High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
Low (Nice to Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
Medium (High Value Add) France and UK
Medium (High Value Add) France

High (Must Have) UK
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have) Germany

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
France - shall be able to

accommodate change in tax
system in 2019 when france moves
to PAYE processing.
High (Must Have)
High (Must Have)
France - to be able to show holiday

balance, leave taken, earned and
Medium (High Value Add) remaining balance in month. Also
able to show expenses reimbursed
through payroll.
EMEA - Allow bank account details

change
High (Must Have)

High (Must Have)
High (Must Have) Poland

Low (Nice to Have) APAC
High (Must Have) US
Medium (High Value Add) Poland, Germany, France

High (Must Have) US/Canada
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
Low (Nice to Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
Low (Nice to Have)
Low (Nice to Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)

High (Must Have)
High (Must Have)
High (Must Have)
High (Must Have)
L
High (Must Have) Meets – Out of the Box – Current release
Medium (High Value Add) Meets – Out of the Box – Next release
Low (Nice to Have) Meets – Out of the Box – 2 or more releases away
Meets – Require Third Party solution integration
Meets – Requires customization
Does Not Meet
Yes, Vendor can meet the requirement
Select how the
Requirement is Met
yes, Vendor can meet

App Create Dunning Notices - Runs
transaction F150 in the
background. Invoice output sent
during actual billing. Dunning
notice can refer to the open
invoice.
Would need customization,

standard process should call pricing
procedure. Only manaul condition
records would be input in the
invoice. Further condition types
can be configured as positive value
only or with tolerance levels.
Standard functionality
SAP Hybris E com native integration
with S4 HANA
BRF rule based output

configuration, where output type
can be configured on the basis of
Standard solution - can maintain

early payment discounts by
configuring these in your payment
terms. the system recognizes the
timing of the payments posting
and could propose discounts based
on the payment terms you
configured. normally, the payments
posting is done on FI side, instead
of SD. possible tcodes used by FI in
posting payments are F-28, F-
01/02, etc.
Depends on the payment terms

and baseline date configured.
However, this would be visible on
the FI side and not on the SD side.
Invoice PDF template can have a
provision for picking Invoice TEXT
ID manually entered/ or passed on Might need In app extensibility to
from CRM application in case of make provision for this in the
price escalation Invoice template
Invoice PDF template can have a

provision for picking Invoice TEXT
ID manually entered/ or passed on Might need In app extensibility to
from CRm application in case of make provision for this in the
price escalation Invoice template
Make these customer data

mandatory in the customer master
(business partner)
BP transaction, company code data

and sales area data can be
maintained.
Use Block Business partner App

Parent Payer or Biller customer can
be assigned to the customer
HCI, web services and APIs can be

used for this integration. If any field
is missing, then it would require
extensibility
– Current release
– Next release
– 2 or more releases away
arty solution integration
e requirement

Book 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Book 1

Uploaded by

Copyright:

Available Formats

Req. No.

8 Accounting Segment Setup

9 Accounting Segment Setup

10 Accounting Segment Setup

11 Accounting Segment Setup

12 Accounting Segment Setup

13 Accounting Segment Setup

169 Budget & Forecasting

170 Budget & Forecasting

171 Budget & Forecasting

172 Budget & Forecasting

173 Budget & Forecasting

174 Budget & Forecasting

177 Budget & Forecasting

182 Budget & Forecasting

183 Budget & Forecasting

184 Budget & Forecasting

187 Budget & Forecasting

188 Budget & Forecasting

189 Budget & Forecasting

190 Budget & Forecasting

192 Budget & Forecasting

193 Budget & Forecasting

194 Budget & Forecasting

195 Budget & Forecasting

196 Budget & Forecasting

197 Budget & Forecasting

198 Budget & Forecasting

199 Budget & Forecasting

200 Budget & Forecasting

202 Budget & Forecasting

203 Budget & Forecasting

204 Budget & Forecasting

206 Budget & Forecasting

209 Budget & Forecasting

210 Budget & Forecasting

212 Budget & Forecasting

213 Budget & Forecasting

214 Budget & Forecasting

216 Budget & Forecasting

217 Budget & Forecasting

218 Budget & Forecasting

219 Budget & Forecasting

221 Budget & Forecasting

222 Budget & Forecasting

227 Budget & Forecasting

228 Budget & Forecasting

229 Budget & Forecasting

230 Budget & Forecasting

231 Budget & Forecasting

232 Budget & Forecasting

233 Budget & Forecasting

236 Budget & Forecasting

237 Budget & Forecasting

239 Budget & Forecasting

240 Budget & Forecasting

263 Financial Consolidations

264 Financial Consolidations

265 Financial Consolidations

266 Financial Consolidations

267 Financial Consolidations

268 Financial Consolidations

269 Fixed Asset