Generating Correspondence

This chapter provides overviews of correspondence generation and acceptgiro form printing and discusses how to:

• Generate customer statements.

• Run balance forward statements the first time.

• Generate dunning letters.

• Generate and print follow-up letters.

• Reprint invoices.

Understanding Correspondence Generation

When you run the processes that generate statements, dunning letters, and follow-up letters, the processes generate the correspondence for the customers that meet the criteria that you specify on the run control request.

To run the processes, you can do the following:

• Schedule the processes to run at a designated time.

• Run the processes on demand from the menu.

• Set up collection and assessment rules that trigger correspondence and run the Condition Monitor Application Engine process (AR_CNDMON).

  The process generates correspondence for customers that have a Send a Dunning Letter (DLTR), Send Follow Up Letter (OLTR), or Send Statement of Account (STMT) action on the customer action list. The action must have the Process Flag field set to Y. Depending on the setup in the action template, the Condition Monitor process automatically sets the flag to Y or you manually set the flag to Y when you work the action that is on the customer action list. The Condition Monitor process calls the Statements (ARSTMT) multiprocess job, AR Dunning (AR_DUNNING) process, and Follow-up Letter Extract (AR_FOLLOWUP) process to generate correspondence for customers that have one of the correspondence actions. If you manually work a correspondence action, you can transfer from the customer action list to the appropriate correspondence request page for the single correspondence action.

See Also

Delivery of Correspondence

(NLD) Understanding Acceptgiro Form Printing

Receivables enables you to print dunning letters and statements with the acceptgiro form. The acceptgiro becomes an attachment to the dunning letters and statements. You must use the A/S Contract Type acceptgiro form. The system prints the normal dunning letter or statement information on the top of the form and if there is an overflow, it prints the remainder on subsequent pages. The form says Vervallen (Void) in the body and counterfoil sections of the acceptgiro attachment on the subsequent pages.

The system prints the total balance due for the dunning letter or statement in the body and counterfoil sections of the acceptgiro attachment, which is at the bottom of the form. If the total amount exceeds 999,999.00 EUR, then the system prints Vervallen (Void) instead in the amount field. The system also prints the address and bank account number for the receivables business unit—this is the collector's bank address and account number— in the body and counterfoil sections of the acceptgiro attachment. The body and counterfoil sections of the attachment also include the address and bank account for the remit to customer.

Important! If you do not assign a bank account to the customer on the Customer Bank page, the system prints only the normal dunning letter or statement information at the top of the form.

The system also prints the system-generated acceptgiro reference number in the body and counterfoil section of the acceptgiro attachment. The system uses the acceptgiro reference number assigned to the business unit on the Bank/Payment Options page and increments the number by one. The system also appends the control digit to the number. The system also updates the AG Number (acceptgiro reference number) field for each item with the acceptgiro reference number from the dunning letter or statement. If an item already has an acceptgiro reference number, the system overwrites it. The bank normally sends the payment for acceptgiros electronically and includes the acceptgiro reference number. So the Payment Predictor process (ARPREDCT) can use this number to apply payments if you use detail algorithms, or you can use the number to apply payments to items on the payment worksheet.

If a statement has a negative balance, the system prints Vervallen (Void) on the acceptgiro attachment in the amount field.

To enable acceptgiros, you must select A/S Contract in the Accept Giro Type field on the Bank/Payment Options page for the business unit.

Each time that you generate dunning letters and statements for business units enabled for acceptgiro attachments, you have the option to print the letters or statements without the attachments by overriding the option on the run control page. If you leave the business unit field blank on the run control pages, the system does not print the letters or statements with the acceptgiro attachments. If the Condition Monitor process triggers the dunning letter or statement processing, you cannot override acceptgiro processing.

Important! You may need to make modifications to the Crystal Report formats to ensure that the fields line up correctly on the acceptgiro attachment. Also, you are responsible for certification with banking institutions.

Generating Customer Statements

This section provides an overview of the statement generation process and discusses how to:

• Run the Statements multiprocess job (ARSTMT).

• (Optional) Select the currency for Open Item statements.

• Print statements.

Understanding the Statement Generation Process

The Statements - Preprocessor multiprocess job (ARSTMT) includes:

• The Statement Parallel Preprocessor process (AR_STMTPP).

• The Statements - Parallel multiprocess job (AR_STMT).

  The Statements - Parallel multiprocess job runs the Statements process (AR_STMTS).

See Setting Up Parallel Processing for Statements.

The Statements process (AR_STMTS) extracts data from customer and item records and populates statement records. The Statements Print multiprocess job (ARSTPRT) merges data from the statement records with predefined layouts and prints both the Open Item Statement (AR32000 and AR32A00) and the Balance Forward Statement (AR32001 and AR32A01). You can also choose to print these statements separately and to print the Draft Customer Statement (AR32002). You can use the customer statement samples that PeopleSoft provides or use Crystal Reports to create your own statements.

Note. The AR32A00 and AR32A01 statements print only if you enable acceptgiro processing for the business unit.

The Statements process assigns a process instance number to all items that it is processing. When it completes, it sets the number to zero. This enables you to run the process concurrently with other PeopleSoft Enterprise Application Engine processes that use different run control IDs.

Note. Receivables also provides the Statements-Parallel/Print multiprocess job (STATEMNT), which runs the Statements multiprocess job (ARSTMT) and prints the Open Item Statement and the Balance Forward Statement.

If you run the Statements - Preprocessor multiprocess job (ARSTMT), each AR_STMT# child process that runs statements uses the same statement ID. So if you run the statement print processes separately, you use one statement ID for all statements. This also enables you to view all statements in the run using the same statement ID.

Receivables enables you to generate customer statements on a regular schedule for many customers or a single statement for only one customer. When you run the Statements process, you specify the scope of the process at any of the following levels:

• SetID level: Generates an invoice or a statement for each correspondence customer in all business units that reference the setID.

• Business unit level: Generates an invoice or statement for each correspondence customer in the business unit.

• Correspondence customer level: Generates a single invoice or statement for all customers in the correspondence group.

• Customer level: Generates a single invoice or statement for the specified customer’s correspondence customer.

Customer statements are based on current customer balances and open item information, which are updated by the Receivable Update Application Engine process (ARUPDATE). Therefore, it is recommended that you run Receivable Update before creating statements.

Receivables provides the ability to create different types of statements:

Prerequisites

You must perform these tasks before you generate statements:

• Set up statement IDs.

• Assign default statement IDs to each setID and define the default remit to address that is used on statements (from bank account addresses) on the Receivables Options - General 1 page.

• Specify which entry types are included on statements on the Entry Type page.

  If you do not select the Include in Statements check box for an entry type, activities with that entry type do not appear on statements.

• Override the remit to address and statement ID defaults or place a global hold on customer documents on the Receivable Options - General 1 page.

• Specify the destination of statements as either the customer or the correspondence customer on the Correspondence Selection page.

• Provide the address and contact for the customer to which you will send the statement on the General Info page.

• Specify the contact and address options for statements on the Correspondence Options page.

• Set up delivery information for correspondence.

• Assign the next available statement number at the installation level.

• Set up parallel processing for statements.

• (NLD) If the organization uses acceptgiros, enable acceptgiros processing for the appropriate business units on the Bank/Payment Options page and assign the initial acceptgiro reference number.

• (NLD) Enter the bank account information for customers that use acceptgiros to make their payments on the Customer Bank page.

• Run the Receivable Update process to post pending items.

See Also

Setting Up Statement Processing

Defining General Options

Defining Entry Types

Setting Up Delivery Information for Correspondence

Selecting Bank and Payment Interface Options

Adding General Customer Information

Defining Receivables Installation Options

Entering Customer-Specific Bank Information

Pages Used to Generate Customer Statements

Running the Statements Multiprocess Job

Access the Statements Parameters page.

Language	Select the language used to print the statements if running the STATEMNT multiprocess job. Do not select a language if you run the ARSTMT multiprocess job. To print statements in multiple languages, place copies of the Crystal report in language subdirectories in the Crystal Reports directory.
As of Date	Enter a date that determines the last date that the statement includes data. The current date is the default. If you use an earlier date, the process reconstructs customer balances so that statements show open items as of the date that is provided. For example, if statements are run on January 5 and you select an as of date of 1/1/00, the results are the same as if the statements are run on January 1 and the current default date is accepted. For balance forward statements, the as of date also determines the ending date for the current statement period. The current balance forward statement period begins with the statement date from the previous balance forward statement.
Open Item and Balance Forward	Clear one of these check boxes if you do not want to run both statement types in the same statement run. This is useful when you select a business unit that has some customers who receive open item statements and others who receive balance forward statements, and you do not want to process all of them all at the same time.
Open Item Include Drafts	Select to include draft items in an open item statement.
Balance Forward Re-Run	Select to rerun a balance forward statement. The system determines which previous balance forward statement to use for the opening balance based on the as of date. It uses the most recent balance forward statement prior to the as of date. When you rerun a statement, use the same as of date that you use when you run the original statement. The process deactivates the original statement and creates a new one. If you rerun a balance forward statement and you ran other later balance forward statements with a different as of date, you must also rerun those statements to ensure that all balances remain correct from one statement to the next. Note. If the statement type is Bal Fwd, only items that have not appeared on a previous balance forward statement are eligible for exclusion.
(NLD) Print Acceptgiro	Clear this check box if you do not want to print statements with an acceptgiro attachment. This field displays only if you enabled acceptgiro processing for the selected business unit on the Bank/Payments page, and the check box is selected by default.
Unit	Enter a business unit to create statements for all customers in a specific business unit.
SetID	Leave the SetID field blank to include all tableSets. If you use only a setID, the process creates statements for each correspondence customer in every business unit that references the tableSet.
Customer	Enter only a customer ID to create statements for the specified customer. If you select a customer who is part of a correspondence group the system addresses the statement to the correspondence customer but includes only the specified customer’s information. Note. If you select a single customer, the system generates a statement for that customer even if the customer is on hold.
Correspondence Customer	Enter only the customer ID for a correspondence customer to create statements for all customers in the correspondence group. Note. If you add or remove a customer from a correspondence customer group between statement periods, rerun the statements for the correspondence customer by using the same as of date as the prior statement. This ensures that the balance forward amount for the next statement run will reflect the correct amount.
Statement Group	Enter a statement group to create statements for all groups or only for customers who belong to a selected statement group. Assign customers to a statement group on the Correspondence Options page.
Balance Forward Due Date	Enter the due date to print on the statements, if you are running balance forward statements.

Note. Enter the percent wildcard in the SetID, Unit, and Customer fields if you want to include IDs that begin or end with the same characters or numbers. For example, entering US0% includes all business units that begin with US0, such as US000 and US001.

Provide more than one parameter to tailor statements even further. The following table describes the results of combining different parameters. It assumes that a parameter in the left column is combined with one or more parameters to the right of that parameter:

Selecting the Currency for Open Item Statements

Access the Currency to Convert page.

The default values for the fields depend on the values that you enter on the Receivables Options - Currency Display Options page for the business unit. Override the values if you want to use a different display currency on the statements.

Printing Statements

Access the Statement Print page.

On the Process Scheduler Request page, select one of these statement print processes:

Warning! If you print one statement type only, you must print the other statement type before you run the Statements process again.

Running Balance Forward Statements the First Time

When running the balance forward statements the first time for existing customers, follow a slightly different procedure to generate a starting balance forward balance that appears on the customer’s first statement.

To run balance forward statements for the first time:

1. Use the Statements Parameters page to run the Statements - Preprocessor multiprocess job (ARSTMT).

   Important! Do not select the Statements-Parallel/Prnt multiprocess job (STATEMNT). Also do not run the Balance Forward Statement Print (AR32001) or Balance Forward Stmt P w/Agiro (AR32A01) process that prints the statement at this time.

   Use the end date of the previous statement period for the as of date.

2. Run the Statements - Preprocessor multiprocess job (ARSTMT) again by using the current statement period for the as of date.

3. Use the Statement Print page to run the Balance Forward Statement Print process for each AR_STMT# child process to print the statements.

Example

You run statements that contain activity that ends on September 30, 2000.

In the first run of the process, you enter August 31, 2000 for the as of date. Because the process does not find an as of date from a previous run, it extracts all activity from January 1, 1900 through August 31, 2000.

In the second run, you enter September 30, 2000 for the as of date. Because the system now has an as of date from the first run, it extracts activity from September 1, 2000 through September 30, 2000.

See Also

Generating Customer Statements

Generating Dunning Letters

This section provides an overview of the dunning letter process and discusses how to:

• Define run parameters for the AR Dunning Application Engine process (AR_DUNNING).

• Define the display currency for dunning letters.

• (Optional) Review and delete dunning letters before printing.

• (Optional) Review and modify dunning letters before printing.

• (Optional) Review and remove items from dunning letters before printing.

• Print dunning letters.

Understanding the Dunning Letter Process

Use these processes to generate dunning letters:

• The AR Dunning process (AR_DUNNING) extracts customer data and populates a temporary table, PS_AR33000_TMP.

  When the Dunning extract process begins, it assigns a process instance number to all items that it is processing.

• Predefined dunning reports that merge data from the temporary table with predefined report layouts and generate dunning letters.

• The Dunning Letters process (DUNNING), which is a multiprocess job that runs both the AR Dunning process and then the dunning reports in one step.

  The job runs the Level One Dunning Letter (AR33001 and AR33A01), Level Two Dunning Letter (AR33002 and AR33A02), and the Level Three Dunning Letter (AR33003 and AR33A03). The system prints data on the AR33A01, AR33A02, AR33A03 reports only if you enabled acceptgiro processing for the business unit.

• The Dunning for All Levels process (DUNNINGA), which is a multiprocess job that runs both the AR Dunning process and then the Dunning Letter All Levels report (AR33000 or AR33A00) in one step.

  The system prints the AR33A00 report only if you enabled acceptgiro processing for the business unit.

  Note. Use the Dunning for All Levels process if you have more than three letter codes or for the Dunning by Action List method.

Note. If you run the Dunning or Dunning for All Levels multiprocess jobs, you cannot change the text or delete unwanted letters before printing.

If you select the Include Finance Charge field when you create a dunning method, and you run the process for customers that are assigned that dunning method, you must run Overdue Charges Application Engine process (AR_OVRDUE) before you generate the letters to create the overdue charges invoice.

AR Dunning Process Data Extract

To generate dunning letters, you run the extract process, review and edit the results as needed, and then run a dunning report that prints a dunning letter.

When you enter the run parameters for the AR Dunning process, you select the scope of the dunning letters:

• Unit level: Generates a letter for each correspondence customer in the business unit.

• Correspondence customer level: Generates a single letter containing all past due items for all customers in the correspondence group.

• Customer level: Generates a single letter for the specified customer’s correspondence customer.

The process uses the default dunning ID that is assigned to the customer on the Correspondence Options page. If none is defined for the customer, it uses the default dunning ID that is assigned to the business unit on the Receivables Options - General 1 page.

Review and Edit of Letters Before Printing

After running the AR Dunning process, you can do the following:

• Review the letters before printing them.

• View a list of the letters that the process generates.

• Selectively delete items that are on a letter.

• Delete letters that you do not want to send.

• Change the text for an individual letter before printing.

After you review the letters and make any needed onetime changes, run the dunning reports that print dunning letters.

Days, Intervals, and Action Lists

When past due items exist for a customer, dunning letters are sent based on the dunning methods that you selected when you set up the system. The following figure shows dunning by days, where the age of the item determines the level of the dunning letter sent. In this scenario, depending on when the dunning run is performed, a customer could receive a level three letter as a first correspondence. If a customer has multiple past due items, they receive one letter based on the age of their oldest item, rather than multiple letters.

This graphic illustrates what the Dunning process includes in letters if the dunning method is Dunning by Days:

Dunning by days

When you use dunning by interval, the level of the letter sent corresponds to the time intervals that you have defined between letters. Therefore, items that receive a level one letter could have different ages, but subsequent letters would be determined by the time interval between letter levels. For a customer with multiple past due items, the oldest item is used to determine the start of the interval cycle.

This graphic illustrates what the Dunning process includes in letters if the dunning method is Dunning by Interval:

Dunning by interval

Dunning by action list is entirely based on rules you determine when you set up the system.

This graphic illustrates what the Dunning process includes in letters if the dunning method is Dunning by Action List:

Dunning by action list

See Also

Setting Up Dunning Letter Processing

Prerequisites

You must perform these tasks before you generate dunning letters:

• Define letter codes and letter content.

• Define the dunning ID and dunning method.

• Define the dunning levels for each dunning ID.

• Assign default dunning IDs to business units and the default remit to address for letters.

• Override the default dunning IDs and default remit to addresses for correspondence customers if appropriate.

• Enter customer addresses and assign an address and contact to correspondence customers who should receive the dunning letters.

• Specify whether you want item-based addressing or customer-based addressing.

• Set up delivery information for correspondence.

• Assign the next available dunning number at the installation options level.

• (Optional) Change the sample dunning letters that PeopleSoft provides or create additional letter layouts.

• (NLD) If the organization uses acceptgiros, enable acceptgiros processing for the appropriate business units on the Bank/Payment Options page and enter the initial acceptgiro reference number.

• (NLD) Enter the bank account information on the Customer Bank page for customers that use acceptgiros to make their payments.

• Apply all the payments to items and run the Receivable Update process.

See Also

Setting Up Dunning Letter Processing

Setting Up Delivery Information for Correspondence

Defining General Options

Selecting Bank and Payment Interface Options

Adding General Customer Information

Defining Receivables Installation Options

Entering Customer-Specific Bank Information

Common Element Used in This Section

Pages Used to Generate Dunning Letters

Defining Run Parameters for the AR Dunning Application Engine Process

Access the Dunning Letters Parameters page.

As of Date	Enter a date that determines the last date for the dunning letter data. The current date is the default.
SetID	Leave this field blank to include all setIDs. If you use only a setID, the process creates a dunning letter for each correspondence customer in every business unit that references the setID.
Unit	Enter only a business unit to create a dunning letter for each customer in the business unit.
(NLD) Print Acceptgiro	Clear this check box if you do not want to print dunning letters with an acceptgiro attachment. This field displays only if you enabled acceptgiro processing for the selected business unit on the Bank/Payments page, and the check box is selected by default.
Customer ID	Enter only a customer ID to extract dunning data for the specified customer. If you specify a customer who is part of a correspondence group, the process addresses the letter to the correspondence customer but includes only the specified customer’s items.
Correspondence Customer	Enter only a correspondence customer ID to extract dunning data for all the customers in the correspondence group.
Dunning Group	Select All Groups or the name of a specific group. You assign customers to a dunning group on the Correspondence Options page.
Use Severest Dunning Letter	Select to print the text from the letter code that is associated with the highest dunning level and to print all past-due items for the customer.
Use Modest Dunning Letter	Select to print the text from the letter code that is associated with the lowest dunning level and to print all past-due items for the customer.

This table describes the results of combining different parameters. It assumes that a parameter in the left column is combined with one or more parameters to the right:

Note. When you save the page or click the Run button, the system assigns the next available dunning number to the run control instance. The system also increments the next available dunning number on the Installation Options - Receivables page. If you save the page without running the process, the system saves the dunning number and uses it when you return to run the process. If you never run the process for the run control, the dunning number is never used.

Defining the Display Currency for Dunning Letters

Access the Display Currency page.

Some customers prefer to have business units share tableSet data. This page enables you to generate dunning letters for a business unit that has a setID that is also used by another business unit. When letters contain different currencies, the AR Dunning process groups and subtotals items by customer and then by currency.

The default values for the fields depend on the values that you enter on the Receivables Options - Currency Display Options page for the business unit. Override the values if you want to use a different display currency on the dunning letters.

Reviewing and Deleting Dunning Letters Before Printing

Access the Letter Preview page.

Review information about various items in the dunning letter, such as the customer, item ID, dunning date, and letter code.

Reviewing and Modifying Dunning Letters Before Printing

Access the Letter Editing page.

Note. If you change the text of the letter to make it longer, you may need to modify the format of the report in Crystal reports so that all of the report prints.

Reviewing and Removing Items from Dunning Letters Before Printing

Access the Dunning Preview Delete Item page.

Use the check boxes to select the items that you want to remove from a dunning letter before printing.

Printing Dunning Letters

Access the Dunning Letter Print page.

Note. Each time that the AR Dunning process runs, it generates a unique dunning number that serves as a batch ID. The dunning number for the process is applied to all the dunning letters that the process generates. If a process retrieves data for 37 dunning letters, it assigns each dunning letter the same run control ID that is assigned to the AR Dunning process. Using the run control ID in the report parameters enables you to generate multiple dunning letters by using one report. So if you have 37 letters, you do not have to run the report 37 times.

On the Process Scheduler page, select one or more of the following dunning reports. Each Crystal Reports report corresponds to a dunning level and letter code. If you select only the level 3 dunning letter, Crystal Reports prints letters only for customers who have past-due items in dunning level 3.

Note. You define dunning levels and the age range of items that are included in each letter category that is on the Dunning Levels page.

See Also

Defining Dunning Levels

Generating and Printing Follow-Up Letters

This section provides an overview of follow-up letter processing and discusses how to:

• Run the Follow Up Letters multiprocess job.

• Run the Follow Up Letters Extract process.

• Run the Follow Up Letter report.

Understanding the Follow-Up Letter Process

Follow-up letters change little from mailing to mailing. Only the names, addresses, and dates change. Receivables delivers a sample follow-up letter that is created by using Crystal Reports that you can modify to suit your organization’s needs.

The system generates follow-up letters as long as you provide a valid contact ID, follow-up action, follow-up user ID, and letter code on the Conversations page.

To generate follow-up letters, you run two processes:

• The Follow Up Letters Extract Application Engine process (AR_FOLLOWUP) extracts names, addresses, and other data, scanning conversation records with letter codes for follow-up letters that have not been marked by the system as done.

  After the process extracts data, it marks the conversation record as done on the Conversation Actions and Keywords page.

• The Follow Up Letter Crystal report (AR33004) merges the extracted data with the follow-up letter template.

Note. Receivables also provides the Follow Up Letters multiprocess job (FOLLOWUP), which runs both the Follow Up Letters Extract process and the Follow Up Letter Crystal report.

You run all three processes from the Customer Follow Up Letter page. If you run the extract process and the Crystal report separately, you must wait for the Follow Up Letters Extract process to complete before you run the Crystal report.

See Also

Modifying the Sample Follow-Up Letter

Prerequisites

You must perform these tasks before you generate follow-up letters:

• Verify that you have a letter code of F for follow-up letters.

• Assign a remit to address to the correspondence customer who should receive follow-up letters and other types of customer correspondence on the General Information - Correspondence Options page.

• Set up delivery information for correspondence for a contact.

• When you create the conversation entries for a specific customer, provide a valid contact ID, follow-up action, and a follow-up letter of F.

See Also

Setting Up Follow-Up Letter Processing

Setting Up Delivery Information for Correspondence

Adding General Customer Information

Entering Conversations

Common Element Used in This Section

Page Used to Generate Follow-up Letters

Running the Follow Up Letters Multiprocess Job

Access the Customer Follow Up Letter page.

Select the FOLLOWUP multiprocess job on the Process Scheduler Request page.

Running the Follow Up Letter Extract Application Engine Process

Access the Customer Follow Up Letter page.

Select the AR_FOLLOWUP process on the Process Scheduler Request page.

Running the Follow Up Letter Report

Access the Customer Follow-Up Letter - Parameters page.

Select the AR33004 process on the Process Scheduler Request page.

Reprinting Invoices

This section provides an overview of invoice reprinting and discusses how to:

• Select items for reprinting.

• Print invoices and override print parameters.

Understanding Invoice Reprinting

Receivables enables you to reprint invoices that you created in Billing that are associated with open items. You cannot reprint invoices that originate in PeopleSoft Enterprise Grants that have a letter of credit ID. If you select to print these Grants' invoices or invoices that are created in a third-party billing system, the system issues a warning message.

The Reprint Invoice multiprocess job (BIJOB19) uses the server and printer that you specify on the User Preferences - Billing page. You can override these parameters when you reprint the invoices. The invoices print in the customer's language.

The existence of a summarization template on invoice lines determines whether the system prints a summarized or detail pro forma or actual invoice. If you are printing an invoice with multiple invoice lines, the system does the following:

• If any of the lines in the invoice have a summarization template, the system generates a summarized pro forma or actual invoice.

• If there is no summarization template on any of the lines, the system generates a detail pro forma or actual invoice.

(NLD) If you enabled acceptgiros for the billing business unit associated with the item, the system prints the invoice with an acceptgiro attachment. If the original invoice in Billing or Purchasing was printed with an acceptgiro attachment, the system uses the same acceptgiro reference number.

See Also

Defining Billing User Preferences

Generating Invoices

Setting Up Bill Summarization

Prerequisites

If you enabled acceptgiros for the billing business unit, you must enter the bank account information for the remit to customer on the Customer Bank page.

See Also

Entering Customer-Specific Bank Information

Pages Used to Reprint Invoices

Selecting Items for Reprinting

Access the Item List page.

To reprint invoices:

1. Enter search criteria for the items and click Search.

2. Select the items for which you want to reprint invoices.

   Note. You must select items that came from Billing and have a billing business unit that is associated with them and a valid invoice number in the Invoice field.

3. Select Reprint Invoices in the Item Action field and click Go.

See Also

Researching a Customer's Items

Printing Invoices and Overriding the Print Parameters

Access the Invoice Reprint Overrides page.

Override the print parameters as needed and click OK to run the Reprint Invoices job.