Understanding Invoicing Processes
This section provides an overview of invoice processing and discusses:
PeopleSoft Billing generates invoices from the data stored in the Billing tables when an invoicing job is run. The components of an invoicing job can include AE, SQR, and BI Publisher processes, as well as subjobs. You can configure the invoicing jobs so that all the processes needed to generate an invoice are part of a single job, or you can use separate jobs to divide the invoicing process into logical steps. Likewise, you can configure a single job to generate all types of invoice forms or you can use different jobs for different types of invoice forms.
The typical steps required to generate an invoice are:
Complete the preprocessing steps:
Import billing data through the Billing interface.
Set value-added tax (VAT) and tax defaults.
Finalize invoice data and set status.
Extract invoice data and complete the print processing steps:
Extract data to temporary tables.
Run print processes for each invoice form.
Complete physical printing, email notification, and electronic data interchange (EDI) transmittal.
Complete the post-processing steps:
Process credit card payments.
Convert currency (if needed).
Create accounting entries.
When configuring invoice jobs, you must maintain the proper processing order. The processes and subjobs within a job can be configured to run in series or in parallel. In general, pre- and post-process steps must be run in series, while the processes that print the different types of invoice can be run in parallel.
Before invoices can be printed, the billing data must be imported (for Interface bills), validated, and finalized.
This table lists the processes, in alphabetical order, used to prepare billing data for invoicing:
Process Name |
Type |
Prerequisites |
Notes |
---|---|---|---|
BIIF0001 |
AE |
External sources of billing data must load the Billing interface tables. |
Transfer data from the interface tables to the standard Billing tables. BIIF0001 can be run on its own, or as part of a larger job such as in direct or streamlined invoicing. See Understanding the Billing Interface Process Main Processing Logic. |
BIIVC000 |
AE |
BIPVAT00 must be run before BIIVC000, if VAT defaulting is required. |
Prepare bills for invoicing. No further changes can be made to billing data after the BIIVC000 process is run. |
BIPVAT00 |
AE |
Must be run before BIIVC000 for those transactions that are subject to VAT taxation. |
Set VAT defaults. See Understanding the Process VAT Defaults Process (BIPVAT00). |
BIRMAADJ |
AE |
NA |
Load RMA (return material authorization) adjustments into the billing interface tables. |
IN_FUL_CONF |
AE |
NA |
Confirm inventory picking. |
IN_PUB_MSG |
AE |
NA |
Publish inventory outbound message. |
INS6300 |
SQR |
NA |
Load interunit transfer bills into the billing interface tables. |
INS6500 |
SQR |
NA |
Generate inventory packing slips. |
OM_BILL |
AE |
NA |
Load PeopleSoft Order Management bills into the billing interface tables. See Populating Billing. |
Finalization Process (BIIVC000)
The Finalization process selects bills that are ready for invoicing and validates and transforms the bill data. The process works in two modes. In pro forma mode, the process performs data validations and transformations that are necessary to preview the invoice. In finalization mode, the process carries out the same tasks as in pro forma mode and also performs final processing, such as setting the invoice date and status, and processing credit cards. Any number of pro formas can be created for a single bill; however, a bill can be finalized only once.
The Finalization process performs the following tasks (the tasks performed only in finalization mode are noted):
Selects invoices that are equal to or greater than the Threshold Amount specified on the Billing Definition - Business Unit 4 Page.
Sequences bill lines by the user-defined sort by option, or according to the invoice line numbers that you define manually during bill entry.
Calculates taxes by line according to current line values and tax rates.
Updates the bill header invoice amount to include currently calculated taxes.
Note: The system does not calculate taxes or VAT for a bill line when the tax timing option for the bill line (populated by PeopleSoft Contracts) is defined as S (taxes on services rendered).
Calculates due date and updates the bill header with this value.
Changes bill status from RDY (ready) to INV (Finalization mode only).
Updates the invoice date with the appropriate value for the bill, the run control, or the current date (Finalization mode only).
If you define the invoice date on the run control request page, the system checks if the date is in an open accounting period and issues a warning on the run control request page if the date falls outside of the period that is currently open in PeopleSoft General Ledger.
Updates the invoice print setting with a status of Printed for bills where the invoice form ID specifies a nonprinting form (Finalization mode only).
(If no printing is expected on this bill, the print status is Complete upon finalization).
For credit card bills, generates credit card authorization requests and changes the status of the bill to FNL (final) instead of INV (invoiced) (Finalization mode only).
Updates the last maintenance user ID and last updated date and time fields (Finalization mode only).
For invoices in euro-participating currencies, converts the invoice amount to the euro currency so that the amount appears on printed invoices in both currencies.
Creates EDI request entries for bills by EDI using XML technology (Finalization mode only).
Performs the Screen for Denied Parties process (SCM_FSS) as a secondary process if the Financial Sanctions Screening (FSS) is configured to be performed for the Order to Cash.
Note: Use the Message Log page to review the results of this process online.
Platform-Specific Statements in BIIVC000
The ROUND and DATETIME functions differ from platform to platform; therefore, the system creates the following platform-specific sections:
Statements |
Description |
---|---|
DBSPEC |
DAY-related statement. |
DBSPEC05, 06, 07, 08 |
Due date calculation. |
DBSPEC10, 11 |
ROUND function for tax calculation without VAT. |
DBSPEC25, 26 |
ROUND function for tax calculation with VAT. |
BIBIIVC000_UPD_BI_HDR |
Bill Header multi-column update. |
BIBIIVC000_UPD_BI_HDR_VAT |
Bill Header VAT multi-column update. |
BIBIIVC000_UPD_BI_LINE |
Bill Line multi-column update. |
BIBIIVC000_UPD_BI_LINE_TAX |
Bill Line Tax multi-column update. |
BIBIIVC000_UPD_BI_LINE_EXS_DTL |
Bill Line Excise and Sales Tax multi-column update. |
Finalization Errors
BIIVC000 validates bill data during proforma and finalization processing. Use the Review Invoice Errors component (Standard Billing - Header - Info 1 Page or the Express Billing - Billing General Page to correct these errors.
), or the message log to view errors that the system finds during the Finalization (BIIVC000) process. Use theThe following error codes are issued to BI_HDR and BI_LINE for validation and processing errors:
Term |
Definition |
---|---|
0120 |
Invalid Tax Code. |
0233 |
Missing or invalid bill currency. |
0900 |
Missing Remit To / Bank Code. |
0901 |
Invalid Invoice Form for Accepgiro. |
0902 |
Invalid Bank CD for Accepgiro. |
0903 |
Invalid Bank Account for Accepgiro. |
1000 |
AVP Error. |
1050 |
Ship To Geocode Not Numeric. |
1055 |
Ship From Geocode Not Numeric. |
1060 |
Order Acc Geocode Not Numeric. |
1110 |
Missing Ship To Cust ID (missing ship-to customer ID). |
1111 |
Invalid Ship To Cust Addr (invalid ship-to customer address). |
1112 |
Invalid HDR Ship To Cust Addr (invalid header ship-to customer address). |
1120 |
Invalid Ship From Bus Unit (invalid ship-from business unit). |
1121 |
Invalid Ship From Bus Unit Loc (invalid ship-from business unit location). |
1122 |
Invalid Ship From Location. |
1123 |
Missing Inventory BU Location (missing Inventory business unit location). |
1130 |
Missing Order Mgmt Bus Unit (missing Order Management business unit). |
1131 |
Invalid Ord Mgmt Bus Unit Loc (invalid Order Management business unit location). |
1132 |
Invalid Business Unit Loc (invalid business unit location). |
1140 |
Order Accept Address not found. |
1141 |
Order Origin Address not found. |
1142 |
Location Address is incomplete. |
1143 |
Original BU/INV does not exist. |
1200 |
Line(s) contain error. |
1210 |
Attached Bill(s) contain error. |
1220 |
Consolidation group has error. |
1300 |
Missing active Remit To Address. |
1310 |
Missing active Bill To Address. |
1350 |
Missing active Payment Terms. |
1360 |
Missing active Distribution CD. (missing active distribution code). |
1370 |
Missing Invoice Date. Rerun the program. |
1380 |
Error calculating Due Dates. |
1400 |
Missing Email ID for Contact. |
1410 |
Contact Not Set up for eBill Payment. |
1420 |
Contact has no row-level security on the Bill-To Customer of the bill. |
1430 |
Email Notification Failed. |
2033 |
Financial sanctions list match. |
2040 |
Invalid Tax Provider Supplied. |
2041 |
Invalid action supplied. |
2042 |
Ship To address required. |
2043 |
No Geocode found - ShipTo ZIP (no geocode found – ship-to zip code). |
2044 |
Invalid ShipTo Geocode. |
2045 |
No Geocode found - ShipFr ZIP (no geocode found – ship-from zip code). |
2046 |
Invalid Ship From Geocode. |
2047 |
No Geocode found - Ord Acc ZIP (no geocode found - order acceptance address zip code). |
2048 |
Invalid Ord Accept Geocode (invalid order acceptance geocode). |
2050 |
Error calculating tax. |
2051 |
No Tax Provider Install data. |
2052 |
Tax Provider Error. |
2053 |
No Tax Provider Application. |
2054 |
Tax Upgrade Not Run. |
2100 |
Invalid Tax Code. |
2110 |
Interlink Tax Error. |
2111 |
Integration Gateway Error. |
2150 |
Invalid Tax Authority Code. |
2160 |
Incomplete Header VAT Defaults. |
2170 |
Incomplete Line VAT Defaults. |
2500 |
Missing Intrastat NatureOfTxn1 (missing intrastat nature-of-taxation one). |
2510 |
Missing Intrastat NatureOfTxn2 (missing intrastat nature-of-taxation two). |
2520 |
Missing Intrastat Fiscal Regm (missing intrastat fiscal regime). |
2600 |
Missing VAT Reporting Country. |
2650 |
Missing Supply State. |
2800 |
GST Defaulting Not Applied. |
2810 |
No Tax Rate Code. |
2820 |
No Excise Tax Rate Details. |
2830 |
No GST Rate Details. |
2840 |
GST Calculation Error. |
2850 |
No Tax Transaction Type. |
2860 |
Missing Excise Tax Parameter(s). |
2870 |
Missing Tax Parameter(s). |
2880 |
No Excise Conversion Rate. |
3000 |
Missing EDI Profile. |
3100 |
Document Sequence Error. |
3110 |
Missing DOC TYPE on Billing BU (missing document type on billing business unit). |
3500 |
Missing Currency Rate Type. |
3530 |
Missing Euro exchange rates. |
The print processes consist of the data extract process, which copies bill data to temporary extract tables and print processes for generating each type of invoice. There are three types of print processes, which are SQR and BI Publisher reports. Each printing process selects bills from the extract tables that meet the requirements for the type of invoice it generates.
The delivered SQR programs combine invoice selection, layout, and formatting in a single, modular program. Most of the SQR programs can generate several forms of invoice within a given layout; however, separate SQR programs are used for consolidated versus nonconsolidated invoices, portrait versus landscape invoices, and summarized versus detailed invoices. Thus one SQR program prints consolidated, portrait, and detailed invoices, while another prints consolidated, landscape, and detailed invoices. Not every combination is available in the delivered SQR programs. For example, summarized invoices are only provided in landscape format.
BI Publisher invoices have two parts:
An Application Engine program which selects the invoices to process.
Report definitions, or templates, which define the format and the layout of the invoice
The print processes and queries can be modified to produce tailored invoice forms.
See Understanding Invoice Programming.
This table lists the print process options:
Process Name |
Type |
Layout |
Prerequisites |
Notes |
---|---|---|---|---|
BI_IVCEXT |
AE |
BIIVC000 |
Extracts billing data to the temporary extract tables. BI_IVCEXT must be run before any of the other print processes. |
|
BIGIVCPN |
SQR |
Portrait |
BI_IVCEXT |
Grants invoices. |
BIIVCLC |
SQR |
Landscape |
BI_IVCEXT |
Consolidated invoices. |
BIIVCLN |
SQR |
Landscape |
BI_IVCEXT |
Nonconsolidated invoices. |
BIIVCPC |
SQR |
Portrait |
BI_IVCEXT |
Consolidated invoices. |
BIIVCPCA |
SQR |
Portrait |
BI_IVCEXT |
Consolidated acceptgiro invoices. |
BIIVCPN |
SQR |
Portrait |
BI_IVCEXT |
Nonconsolidated invoices. |
BIIVCPNA |
SQR |
Portrait |
BI_IVCEXT |
Nonconsolidated acceptgiro invoices. |
BISF108X |
SQR |
Portrait |
BI_IVCEXT |
Standard Forms 1080 and 1081. |
BISLSUM |
SQR |
Landscape |
BI_IVCEXT |
Summarization invoices. |
BISLSUMC |
SQR |
Landscape |
BI_IVCEXT |
Consolidated summarization invoices. |
BI_PRNXPN01 |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Sample BI Publisher invoice. |
BIPRNXPC01 |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Sample BI Publisher consolidated invoice. |
BI_XPSF103X |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Standard form 1034/1035 BI Publisher invoice. |
BIXCA |
BI Publisher |
Portrait |
BI_IVCEXT |
BI Publisher contracts invoice. |
BIXCLSUM |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher summarization invoice. |
BIXCLSUMC |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher consolidated summarization invoice. |
BIXPRNT00 |
BI Publisher |
Portrait |
BI_IVCEXT |
BI Publisher generic invoice. |
BIXPRNC00 |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher generic consolidated invoice. |
BIXPRNT01 |
BI Publisher |
Landscape |
BI_IVCEXT |
PS/PC - BI Publisher projects invoice. |
BIXPRNT02 |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher Order Management invoice. |
BIXPRNC02 |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher Order Management consolidated invoice. |
BIXPSA01 |
BI Publisher |
Portrait |
BI_IVCEXT |
BI Publisher project by employee invoice. |
BIXPSA02 |
BI Publisher |
Portrait |
BI_IVCEXT |
PS/PSA02 - BI Publisher projects by activity invoice. |
BIXPSA03 |
BI Publisher |
Portrait |
BI_IVCEXT |
PS/PSA03 - BI Publisher project detail invoice. |
BI_PRNLOC |
BI Publisher |
Portrait |
BI_LOCEXT |
BI Publisher Letter of Credit. |
BI_PRNXPGN1 |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Sample BI Publisher invoice. |
PeopleSoft Billing supports two ways of paperless invoicing, Email Notification and Email invoice as attachment. You can specify the type to use on the invoice media field of the invoice.
The BIIVCEMAIL Email Notification process sends an email to billed customers for invoices that were finalized with an Invoice Media setting of Email Notification. You must have the eBill Payment product installed in order to choose this option. The process can be run independently from its own run control page, or it can be incorporated into one or more of the invoicing jobs. If incorporated, the Email Notification process must follow the BIIVC000 finalization process. This process will send an email to the billing contact on the bill. The email will contain a link to the eBill Payment application. When the customer clicks the link, they will be directed to the eBill Payment log in screen. Once logged in, the customer will be able to view and pay the invoice.
Alternatively, you can choose the Email invoice as attachment feature to accomplish paperless invoicing. The BI_XMLPBURST process sends an email to the customer with the invoice attached as a PDF. This feature is available only for BI Publisher invoices. The Review Email Invoice Log component can be used to review the processing results of the email attempts.
Notification Composer Framework
Oracle PeopleSoft delivers Notification Composer Framework in Enterprise Components to manage the setup and administration of notifications in one central location. Once you have adopted the Notification Composer feature, you must use it to create new notifications and manage your existing notifications.
These PeopleSoft Billing invoice business processes are delivered with FSCM Update Image 49, and must use Notification Composer:
Billing Invoice Courtesy Copy
Billing Invoice Customer Contact
For more information about Notification Composer Framework, see Understanding Notification Composer.
During the invoice print processing, the system can generate an image of the formatted invoice for permanent storage. The image that is generated is in a PDF file format and is automatically attached to the bill header. The image is viewable from the Bill Summary or Supporting Documentation components. If the eBill Payment product is installed, the image can also be viewed by your customers from the self-service Bill Summary page.
The invoice image is produced by the BI_XMLPBURST program when the invoice is finalized. An image is not retained when a pro forma or a reprint is run for the invoice. This feature is available only for invoices that specify a BI Publisher invoice format. This feature is not available for invoices marked for the following Invoice Media delivery options: Invoice Notification, EDI and Federal Highway File because a formatted invoice is not produced for these media types.
The PeopleSoft Billing system is able to achieve batch emailing of invoices and retaining invoice images via the bursting feature of BI Publisher. During the Finalize and Print processing of invoices, the BI_XMLPBURST program is run which will generate a PDF file which contains multiple invoices, and break it up into smaller PDF files of one file per invoice. This means that for each distinct invoice, a separate PDF file will be generated.
The name of the PDF will be a concatenation of Business Unit, Invoice and sequence number. These bursted files are stored in a temporary working directory which is deleted once the processing completes. For Windows, the working directory is specified in the TMP environment variable of the process scheduler. For UNIX environments, the working directory is specified in the PS_FILEDIR environment variable.
The burst program will loop through each bursted file and either email the PDF file, attach the PDF file or both depending on your system settings. If the invoice file is to be emailed, then a row is inserted into an email log table to track the email attempt and the results.
Note: The email invoice as attachment and retain invoice image features do not support the SF1034/1035 BI Publisher invoice.
After you generate a set of invoices, several processes can be run to create accounting entries.
This table lists the Billing post-invoice processes in alphabetical order:
Note: Processes not listed here may be required when finalized invoice data is sent back to integrated applications such as Project Costing and Contracts.
Process Name |
Type |
Prerequisites |
Notes |
---|---|---|---|
BICRC000 |
AE |
BIIVC000 |
Credit card processing. Note: BICRC000 process must be rerun if the program abends for any reason. |
BICURCNV |
AE |
BIIVC000 and BICRC000 (when credit card payments are accepted). |
Billing currency conversion. Warning! Do not run the Currency Conversion process concurrently. If you run two Currency Conversion processes at the same time, one or both processes may fail. See Understanding the Currency Conversion Process (BICURCNV). |
BIGNAP01 |
SQR |
BIPRELD |
Generate AP vouchers. |
BILDAR01 |
SQR |
BIPRELD |
Load AR pending items. |
BILDGL01 |
SQR |
BIPRELD |
Load GL interface. |
BIPCC000 |
AE |
Billing to PC/CA Interface. |
|
BIPRELD |
AE |
BICURCNV |
Billing preload process. |
FS_BP |
AE |
BILDGL01 |
Commitment Control Budget Check. |