Review Questions Flashcards
The Dashboard’s zones always contain information about the account/person/premise whose information is displayed in the Object Display Area. True/False
True. For example, if you were to use the bill search page to find a bill that’s linked to an account that differs from the Dashboard, the system will refresh the dashboard to continue the new account’s information.
The system automatically refreshes the Dashboard zones whenever the user saves any change. True/False
True. For example, if a user changes a customer’s name, the Dashboard’s zones will be refreshed and therefore reflect the new name.
Portal preferences are used to define the zones that appear on a portal. True/False
True
Most users know how to change their portal preferences. True/False
False. Most users are typically production users and most implementations do not allow production users to change their portal preferences as it makes support and training difficult.
If a user references a template user, they cannot change their portal prefences. True/False
True. When a user references a template user, the template user’s portal preferences are inherited by the user and cannot be change.
Some zones in the Dashboard contain zones that show person/account/premise information; whilest others are tools that have nothing to do with person/account/premise information. True/False
True
The zones that appear on the Dashboard are configured on User Preferences just like the zones in any portal. True/False
True
The Work List is dashboard zone that can be populated with a column from an explorer zone in any portal. True/False
True
The Dashboard always appears on the desktop. True/False
False. Trick question. You can click the Dashboard’s title to temporatily disable it (in case you need more horizontal real estate). You can permanently disable it by changing your User Preferences. (set the Dashboard Width to 0)
There are many business rules developed on the database tier (e.g., in PL/SQL). True/False
False. In this system, business rules reside on the application server tier, not the database tier.
There are many business rules developed on the user interface tier (e.g. in JavaScript). True/False
Both True and False. While there are some rules that have been developed in JavaScript (that is, they run on the browser), these rules are considered “redundant” as the rules will be repeated on the application server prior to any updates ocurring. The reason for this redundancy is because it makes the system more pleasant to use (e.g., disabling fields, showing valid values in drop-downs, etc. are business rules that are manifest on the UI so that users can’t select /do things that they aren’t allowed to do), However, the rules cannot just reside on the UI because the system is truly service-oriented (meaning that all UIs send messages to back-end services that do the work). This design philosophy is what allows you to be confident that using a web service to update an object is identical to what happens when a web page is used.
If you see a box on an entity relationship diagram (ERD) that is not white, you can be certain that there’s a transation on of the menus for this object. True/False
True. And the color of the box helps determine the menu item.
If your users (or customers) speak mulitple languages, you can define descriptive values in an unlimited number of languages. True/False
True. When users use the system, the labels, messages and descriptive values are shown in the language they speak. Also note, a dashboard zone exists that allows you to switch your language (this is useful during multi-lingual testing and there are some customers who use this in production as some customer-facing users prefer to see the system in the language the customer speaks).
There is no limit to the number characteristics (that is, user defined fields) an object can have. True/False
True. Note, the Configuration Tools class teaches you how to tailor the user interface so that end-users cannot distinguish between an element whose values is heald in a characteristic versus one held in a dedicated column.
There are owned objects flags that have columns that can be changed regardless of the owner. True/False
True. There are several metadata objects that have columns that can be changed regardless of the owner.<br></br><br></br>A good example is the message metadata, Every error and warning is owned because the system does not want implementations to change its message text. However, you’ll find that every message has an “override text” column. This column can be changed regardless of who ons the message. At run time, if the override text is non-blank, this verbiage is shown to the end-user. The analogy is true for field labels (that is, an implementation can enter an “override label” for a field to change the label that prefixes a field on the user interface.)
<div>Control
Central is a page where a user can:</div>
<div>- search for a person,
account, or premise</div>
<div>- view information related
to the person, account and premise</div>
<div>- be alerted to anomalies
about the customer or premise</div>
<div>- navigate into other pages.
</div>
<div><br></br></div>
<div>With these
points in mind, please choose the specific functionality embodied within
Control Central (please choose all that apply):</div>
<div><br></br></div>
<div>a. Find an
account or premise by entering the account’s account number.</div>
<div>b. Find an
account or premise by entering a telephone number.</div>
<div>c. Find an
account by entering an address.</div>
<div>d. Drill to the
page where a bill can be added, canceled, or rebilled.e.Identify the premise
where a customer wants to start service.</div>
<div>f. Drill into
Start/Stop.</div>
<div>g. View
financial transactions (e.g., payments, adjustments, bill cancellations) that
have been created since the last bill was completed.</div>
<div>h. View all
customer contacts associated with a person.</div>
<div>i. Find an
account by entering a social security number.</div>
<div>j. Display the
account’s payments and bills.</div>
<div>k. Display
alerts highlighting anomalous things about the account (e.g., active collection
process, account has multiple premises, etc.)</div>
<div>l. Drill into
the page used to start and stop service.</div>
<div>m. Modify an
account’s customer class.</div>
<div>n. Drill into
the account page to modify this information.</div>
<div>o. Display an
account’s arrearage history.</div>
<div><span>a, b, c, d, g, h, i, j, k, l, o.</span><span></span></div>
<span><div><span>The aged</span><span>debt bar in the
Context zone does show the account’s arrearage in “buckets.” You can view
arrearage to the day by drilling into Account –Financial Balances.</span>in the
Context zone does show the account’s arrearage in “buckets.” You can view
arrearage to the day by drilling into Account –Financial Balances.</div></span>
What is the significance of a comma (,) in the name field?
A comma designates a human name as opposed to business name. All human names should be entered in the format Last Name,First Name (with no space between the comma and the first name).
Many add and update dialogs default the person/account/premise that was last selected on Control Central. True/False
True. When you use the context buttons to transfer to other pages (in add or update mode), the system assumes you want to add or update information for the object associated with the context button.
If a user types in the name “Jones,Pam” in Control Central - Main and there is more than one customer with this name, what happens?
The scroll area at the bottom of the page is populated with one row for each account with the name Jones,Pam. The user would select the row they really wanted. They can use the ID information adjacent to the customer name to pinpoint the customer in question. When an account is selected, the user can use “Next Item” and “Previous Item” to scroll through the other matches.
There are many different ways to navigate to a page from Control Central. List them:
<div><span>- You can push a go to button or a link.</span><span></span></div>
<span><div><span>- You can click many nodes in the trees.</span></div></span><span></span><span><div><span>- You can click a context menu button.</span></div></span><span></span><span><div><span>- You can click the start and stop buttons.</span></div></span><span></span><span><div><span>- You can click a bar in the Bill Graph zone.</span></div></span><span></span><span><div><span>- The dashboard has numerous ways to drill into other pages</span>as numerous ways to
drill into other pages</div></span>
If Rick Bush has a small business and a residence in the utility’s ervice territory, he may have one or two accounts, but will only have one person record. True/False
True. It’s important to stress that Rick is the sole financially responsible individual for both entities (the residence and the small business). This means that there is only one financially responsible individual. This individual has his demographic information recorded on a person record.<br></br><br></br>This person may choose to have all of his obligations on one bill or to segregate them onto two bills. Their choise will dictate if he has one or two accounts.
If a customer moves without paying their debt and then returns two years later and tries to resume service, the system will be able to highlight this to the customer service rep. True/False
True. This is because an account stays with a customer from cradle to grave. When debt is written off, a write-off service agreement is created and uncollectable debt from the account’s regular service agreements is transferred to it. You should associate an alert with the write-off SA type so that the system will warn the user when an account has an active write-off service agreement.
It’s important to know who the customer is before a premise can be added to the system. True/False
False. You can add a premise to the system without knowing the customer.
If there are two water meters at a property, there will be two water service points linked to the premise. True/False
True. A service point is a socket into which a meter is plugged. You can only plug one meter into a socket. Therefore, if there are two meters, there must be two service points.
The system requires an account to exist before a service can be started. True/False
True. In the system the customer dictates how they want to be billed (that is, the number of accounts). This means we have to know which account will be billed for service before the service is connected (it;s a little late after hte connection crew has returned from the field and the customer is no longer on the phone). Also we need to know, while the customer is on the phone, if we are going to reuse an existing account or create a new one.
Most service agreements are added using the service agreement page. True/False
False. Most Service agreements are created behind the scenes when an operator starts service using the “Start/Stop” service page.
Over time, a given porperty’s owner may be linked to several different parties as customers move in and out. True/False
True. Over time, a given service point may be contractually obligated to any number of parties.
The consumption measured on one service point could be added or subtracted from the consumption measured on a different service point in order to derive the total amount of consumption to be billed on a service agreement. True/False
True. You can use a field on the SA/SP relationship (see the service agreement page) to handle this type of subtractive metering requirement.
A user must choose a start option for eash service to be started. True/False
False. Only some SA types use start options (which ones depend on how the system has been set up).
What is a SQI?
A SQI (service quantity identifier) is a third identifier that can be used if UOM and TOU code do not clearly define the type of measurement. Examples include kWh, on peak, and energy <u><b><i>consumed</i></b></u> versus kWh, on peak, and energy <b><i><u>generated</u></i></b>.
How is scalar meter read data different than interval data?
Scalar meter reads are often read on a sporadic basis, like March 15, April 16, or May 13. While interval data is fixed and provides consistent readings every hour, every 30 minutes or every 15 minutes.
What is the difference between consumptive and subtractive metering?
Consumptive readings provide measurement values like KW. While subtractive meter devices only provide a stop reading and C@M must calculate the consumption (<i>(Stop Read - Previous Read) * Meter multiplier(s)</i>)
What is admin data?
Admin data is administrative data that does not change very often. This includes MC and SP types. Admin data (or refernce data or control data) defines the types of master data that may exist. This data is accessed via the admin menu option.
What is master data?
Master data is non-transactional data that defines a busines entity. Examples inclued data about devices, device configurations, MCs, etc. Most master data objects have a corresponding admin objest. Master data is accessed from the main Menu.
What is a usage subscription?
A record that defines how the system will want usage summarized.
Are usage subscriptions for billing only?
No, a usage subscription can be used for other purposes like sending usage to other edge applications like load research, forecasting, etc.
Can a service point be assigned to more than one usage subscription?
Yes
What is a condition code?
Measurements have condition codes, used to indicate the source and quality of measurement. For example:<br></br>- Regularly recorded measurements might have a condition code of “Regular”<br></br>- Missing measurements might have a condition code of “Missing”<br></br>- Estimated measurements might have a condition code of “External Estimated” or “System Estimated” based on where the estimation was performed.<br></br><br></br>Both Pre VEE and Post VEE values have their own condition code, which can also change during VEE processing
What is the difference between Pre and Post VEE IMD values?
The Pre VEE IMD values show the data as it came into the MDM. Post VEE IMD values are after the data has been change by a user or the MDM system.
Can I change final measurement directly?
No, a new IMD must be created that replaces the incorrect final measurement.
Must derived values originate from the original measurement values?
No, while derived values are usually based on the final measurement other items can also be derived. The derivation formula for each value on a final measurement is held in an algorithm and therefore can derive anything, e.g. a profiles value for the period.
Can I manually add meter reader remarks to a finalized initial measurement?
Yes.
Can I manually add meter reader remarks to non-finalized initial measurement?
No, the initial measurement must be in a “Finalized” state.
Can I use the device event upload XML format for meter reader remarks?
No, you must use the scalar initial data measurement XML nodes for meter reader remarks
Are meter reader remarks used to note problems with interval meteres?
No, currently meter reader remarks can only be used with scalar initial measurements.
A specific user is assigned to a To Do entry when it is in the state of Being Worked on. True/False
True
Only the user assigned to a Being Worked On To Do entry may see the entry in the To Do Summary Page. True/False
True
Assume there is an entry that highlights an account without a bill cycle. When a user assigns a bill cycle to the account, the To Do entry will be completed automatically by the system. True/False
True. The answer is true, but it’s important to understand that the system will only automatically complete the entry the next time the background process responsible for the creation and completion for such a To Do entry executes. If a user wants to mark it as Complete before the process runs, they can.
A supervisor is a user who is part of a To Do role who also has access to the supervisor pages. True/False
True. There is no specific attribute on a user that designates them as a supervisor.
The system issues a warning if you attempt to assign a To Do entry that has a special skills requirement to a user that doesn’t have these skills. True/False
True
Some To Do lists have the same message text for every entry, while others have different messages for the various entries. True/False
True. It’s up to the process that creates the entry - if it supplies a specific message number, it’s used ; if it doesn’t, the default on the To Do type is used.
An implementation will pronanly use a combination of On Demand and Supervisor Push work distribution methods. True/False
True. The systen has been designed to support both methods in a single implementation.
A complete entry can be re-opened. True/False
False. Only a Being Worked on entry can be re-opened.
The Alerts zone will highlight if the person/account.premise in context has open or being worked on To Do Entries. True/False
True
If an implementation prefers different message verbiage for a To Do entry, implmenters must create a new message and define it on a new To Do type. True/False
False. Every message’s text can be overridden by an implemnetation. To do this, display the message on Admin>System>Message and specify the text that you prefer.
Assume a specific To Do list is being populated with hundreds of entries with the same message number. It would be a good idea to update the To Do type to indicate that To Do entries should be suppressed for the specific message number (and your team should creat a repot or a “sample and submit” instead). True/False
True
Assume there is an entry that highlights an account without a bill cycle. A user can set the status of the entry to Complete without specifying a bill cycle for the account. True/False
True. If a user does this, the sytem will recreate the entry the next time the respective background process runs.
In order to Forward or Send back an entry, user should first click the entry’s date/time or info string to open the To Do Entry maintenance page. True/False
True.
A bill segment has a related FT, which controls how the service agreement’s debt and the GL are affected by the billed segment. True/False
True
An adjustment has a related FT, which controls how the service agreement’s debt and the GL are affected by the adjustment. True/False
True
A payment has a related FT, which controls how the service agreement’s debt and the GL are affected by the paymeny. True/False
False. A payment doesn’t have a financial transaction. Rather, the payment segments each have a financial transaction.
A FT references a service agreement, not an account. True/False
True
In order to determine an account’s balance, the system summarizes all FTs linked to the account’s service agreements. True/False
True
If a bill segment is canceled, another FT is created and linked to the bill segment. This FT reverses the financial effects of the bill segment. True/False
True. This means a bill segment can have a maximum of two FTs linked to it - the original plus the cancelation.
If an adjustment is canceled, another FT is created and linked to the adjustment. This FT reverses the financial effects of the adjustment. True/False
True
If a payment is canceled, an FT is created for each of the payment’s payment segments. These FTs reverse the effects of the payment. True/False
True
All financial transactions affect the GL in some way. True/False
False. FTs that just affect a service agreement’s current balance (as opposed to its payoff balance) do not affect the GL. A good example of such a FT a bill segment that charges for a deposit (as most companies do not update the GL for a deposit being billed because it’s not truly debt).
FTs that affect the GL have at least two GL distribution lines. True/False
True. There must be at least one GL account debited and another that is credited. Note, most bill segment FTs have more than two GL distribution lines.
Fts are interfaced to the GL via a flat file. True/false
True
A given FT may affect a service agreement’s payoff balance and/or current balance. True/False
True. Note, most FTs affect payoff and/or current balance. The FT algorithm used to create the FT controls which balance is affected. However, there is an interesting FT algorithm that affects neither current not payoff balance - the one used to book company usage. These FTs only affect the GL.
The system creates FTs behind-the-scenes when bill segements, payment segments, and adjustments are created. True/False
True. FTs for payment segments are only created when the payment is frozen, not when the payment is created.
A user is allowed to modify some fields on an FT. True/False
True
Accounts on the same bill cycle will recieve bills at roughly the same time every month. True/False
True. We say “roughly” because a bill cycle has a “bill window” that can span several days. An account will recieve a bill on the first day in the bill window that the system successfully creates a bill. An account may not recieve a bill on the first day of the bill cycle due to missing info (e.g., a missing meter read) or incorrect information.
<b>If the remitted funds are used to pay the outstanding debt on two different accounts, two payment events are necessary. True/False</b>
False. This is a situation where the payor account is not the same as the payee account. In this example a single payor covers the payments of multiple payee accounts.<br></br><br></br>Using the Payment Event Quick Add single payment event dialog box, a single payment event with two distribution details may be added. Each detail record references the rule value that uniquely identifies the respective account whose debt is being releived by the payment.
<b>A payment event must have at least one tender and one payment. True/False</b>
True
<b>A tender contains the amount and references a specific tender type (e.g., cash, credit card, check). True/False</b>
True
<b>The account on a payment event’s tender(s) must be the same as the account on the event’s payment(s). True/False</b>
False. The account remitting the finds is typically the same as the account whose debt is being paid. However, they can differ (e.g., when a social service agency pays other customer’s debts).
<b>Both a tender and a payment reference an account. True/False</b>
True
<b>A payment contains the amount of the tender(s) applied to a given account’s balance. True/False</b>
True.
<b>I a customer pays with a check, the check number would be entered on the tender. True/False</b>
True
<b>If a customer remits both cash and a check two payment events are necessary. True/False</b>
False. A single payment with two tenders would be recorded. This payment event would the have a single payment to distribute the grand total of both tenders to the account’s service agreements.
<b>A payment segment’s financial transaction always credits a recievable account. True/False</b>
False. The GL account credited by a payment is defined on the service agreement’s SA type (in the distribution code field). For many types of SA’s, this is a receivable account.<br></br><br></br>However, there are other SA’s that don’t affect a receivable account - deposits and charitable contributions - these almost always affect a payable account.
<b>If you cancel a payment before it’s swept onto a bill, no information about the payment will appear on the account’s next bill. True/False</b>
True. This is analogous to what happens if you cencel a bill segment before the bill is completed - if bill completion sees both the original FT and its cancellation are linked to the same bill, it marks both as “do not print”.
<b>A payment could cause a collection to be canceled. True/False</b>
True
<b>A payment could cause a stopped service agreement to be closed. True/False</b>
True
<b>A payment could cause a new service agreement to be created. True/False</b>
True. If a customer pays more than what they owe AND you have plugged in the appropriate overpayment algorithm on customer class, the system will create an “overpayment service agreement” at this time. This overpayment service agreement will have a credit balance equal to the overpayment amount. This credit will be distributed to the debt arising from future bills (if you plug in the appropriate bill completion algorithm on the overpayment SA type).
<b>If a check bounces, you would cancel the tender associated with the check. True/False</b>
True. When you cancel a tender, you must specify a cancellation reason. Certain types of reasons are used when a check bounces. These reasons cause a NSF charge to be created.
<b>If a check bounces, the NSF charge is levied on the account that remitted the funds (that is, the account on the tender) as opposed to the account whose debt was relieved. True/False</b>
True
<b>When you cancel a payment , the system automatically cancels all tenders linked to the payment’s payment event. True/False</b>
False. You tend to cancel a payment ( as opposed to a tender) when it was applied to the wrong account. The system therefore assumes the tender is still valid. In this situation, the payment event becomes unbalanced until the sum of the event’s payments equal the sum of the event’s tenders.
<b>You can save an unbalanced payment event. True/False</b>
True. Note, unbalanced payment events appear in an exception query.
<b>A payment event created using the Non CIS Payment zone will have a seperate payment for each distribution code. True/False</b>
True
<b>An FT for a Non CIS payment will typically debit cash and credit an account receivable account. True/False</b>
False. It will typically credit a revenue account as a recievable only when a payment pays for something that was previously billed.
<b>A payment event can contain both Non CIS payments and CIS payments. True/False</b>
True
<b>An installation option setting dictates if payment in alternate currency is allowed. True/False</b>
True
<b>The base package currency conversion script retrieves the exchange rate from a charateristic. True/False</b>
False - This value is stored on a Bill Factor. Bill factors must be set up for each currency accpted; it is up to the implementation to populate the bill factor values with the effective exchamge rates.
<b>Only one Tender Source can be defined for each user. True/False</b>
False - Multiple Tender Sources can be defined, but only one per currenct is allowed.
<b>Cash back is calculated in the account’s currency. True/False</b>
True
<b>If a customer was charged an incorrect rate on a bill, the proper way to correct the error in to calculate what the customer’s bill should have been and then create an adjustment to affect the SA’s balance accordingly. True/False</b>
False. The correct method is to change the rate on the SA and then do a cancel/rebill in the billing subsystem. The cancel/rebill process will reverse the original bill segment and create a new one. In other words, correct the cause of the error, no the effect.
<b>An adjustment can be used to change the amount a customer owes for a deposit. True/False</b>
True. You don’t know this yet, but a deposit is held on a service agreement just like every other type of “debt”. Therefore, you can use an adjustment to change the amount of deposit “debt”.
<b>A single adjustment can be used to modify several service agreements’ debt. True/False</b>
False. An adjustment is linked to a service agreement. To change several service agreements’ debt, it would be necessary to create several adjustments.
<b>An adjustment is used to charge a customer for a bounced check. True/False</b>
Tru. Adjustments can be used to levy any type of one-time charge. The system creates an NSF adjustment behind-the-scenes when a tender is canceled using a NSF reason code.
<b>Many one-off charges are levied by creating adjustments “behind the scenes”. True/False</b>
True. Besides NSF charges, the system creates adjustments for late payment charges and connection charges (connection charges can be created via an adjustment on a start option) and many other charges.
<b>All adjustments have an adjustment type. True/False</b>
<i>True</i>
An adjustment type could reference both a default amount and a default amount algorithm. True/False
False. The adjustment type may refernce one or the other, but not both.
An adjustment can apply a rate to a quantity to calculate the adjustment amount. True/False
True
The default amount algorithm and the generate adjustment algorithm both provide an adjustment amount. What is the difference between these two plug-in spots?
A user may override the amount produced by the default adjustment amount algorithm. The generate adjustment algorithm may apply further calculations to a base amount and produce a calculated amount. The user cannot override the calculated amount. (The user could modify the base adjustment amount and regenerate the calculated amount.)<br></br><br></br>The generate adjustment algorithm could also produce multiple calculation lines and general ledger details.
The general ledger account used to book late payment charges from the adjustment type. True/False
True. And the recievable GL account comes from the distribution code on the SA’s SA type.
A customer with a single metered service agreemtn who is not on a budget could have an adjustment where current amounts differs from payoff amount. True/False
False. There is no justification for these two attributes to differ for such an SA. The amount the customer thinks they owe is equivalent to how much they really owe.
The GL account defaulted from the adjustment type may be debited or credited as a result of an adjustment. It all depends on whether the adjustment amount is positive or negative. True/False
True. For example, if the adjustment is used to levy a charge (a positive adjustment value), you will credit the GL account defaulted from the adjustment type. If the adjustment is uded to forgive a charge (a negative adjustment), you will debit the GL account defaulted from the adjustment type.
Information about an adjustment always appears on the account’s next bill. True/False
False. Every adjustment’s financial transaction contains a switch that controls whether infomration should appear on the account’s next bill. The value of this switch defaults from the adjustment’s adjustment type but you can change the value as needed.
An adjustment affects an account’s total debt when the adjustment is frozen. However, most adjustments only start aging when they are swept onto an account’s bill. True/False
True. Every adjustment’s financial transaction contains a switch that controls when the adjustment starts aging. By default, this switch is set to only start aging the adjustment when it’s swept onto the next bill. You can change the value as needed.
A transfer adjustment can be used to transfer funs between two accounts (e.g., a credit balance from one service agreement can be used to offset the debit balance on another). True/False
True
Assume a customer had 2 service agreements, both of which have a credit balance. Next assume that the customer would like a check for the total amount of the credit. Explain how / if you could satisfy this request.
Transfer the credit from the SA1 to SA2 with a transfer adjustment. Then create an A/P adjustment for the check amount against SA2.
It seems logical that every bill segment that is canceled will have associated adjustment. True/False
False. When a bill is canceled, the financial impact is recorded on the bill segment (actually on the bill segment’s cancellation financial transaction), therefore an adjustment is not needed to change the account’s debt.
Fact: transfer adjustments (a pair of adjustments use a clearing GL account to “hold” the transferred money. Question: the net effect on the clearingGL account will always be sero? True/False
True
Canceling an adjustment reverses its financial impact. True/False
True
If you cancel an adjustment before it’s swept onto a bill, no information about the adjustment will appear on the account’s next bill. True/False
True
An adjustment that reduces a customer’s debt could cause a stopped agreement to be closed. True/False
True.
If an adjustment type references an approval profile, its adjustments will always require approval. True/False
False. It all depends on how the thresholds have been set on the approval profile. If the first threshold is 0, the all adjustments will have to be approved. If the first threshold is 20, only adjustments greater than or equal to 20 will require approval.
An approval profile can be set up to require multiple leveles of approval for certain monetary values. True/False
True
An approval profile can be linked to an unlimited number of adjustment types. True/False
True
You can use the To Do List transaction to see the total number of outstanding adjustments that are awaiting approval. True/False
True
If an email is sent to an approver, a ToDo entry will not be created. True/False
False. To Do entries are what cause the email to be created.
If an email message is sent to an approver, a hyperlink will contain the Adjustment - Approval Portal where the user can press approve or reject. True/False
True
When an approver approves an adjustment, the associated To Do entry is completed by the system. True/False
True. And, the next approver would be notified that it’s their turn to approve.
When the last approver approves an adjustment, the adjustment is frozen. True/False
Both True and False. Depends on if the adjustment type has been configured to freeze at will or freeze at bill completion.
