Reviewing Billing Examples
Review the following examples to see how data flows from a billing plan in PeopleSoft Contracts to the Billing Worksheet in PeopleSoft Billing and from the Billing Worksheet to the finalized bill and update of Contract/Projects data. You can also see the updates that the system makes to the rows in the CA_BP_XREF table during this process.
Milestone Billing Example
Percent Complete works the same way.
Create a billing plan with two billing plan events and two billing plan lines.
CA_BILL_PLAN:
| CONTRACT_NUM | BILL_PLAN_ID | AMOUNT |
|---|---|---|
|
CA1 |
BP1 |
1000 |
CA_BP_LINES:
| CONTRACT_NUM | BILL_PLAN_ID | BPLAN_LN_NBR | GROSS_AMT |
|---|---|---|---|
|
CA1 |
BP1 |
1 |
400 |
|
CA1 |
BP1 |
2 |
600 |
CA_BP_EVENTS:
| CONTRACT_NUM | BILL_PLAN_ID | EVENT_OCCURRENCE | EVENT_DATE | PERCENTAGE |
|---|---|---|---|---|
|
CA1 |
BP1 |
1 |
1/1/99 |
50 |
|
CA1 |
BP1 |
2 |
10/31/99 |
50 |
According to BP1, these are the invoice due dates and amounts:
-
On January 1, 1999, the following amount is due: (0.5*400) + (0.5*600).
-
On October 31, 1999, the following amount is due: (0.5*400) + (0.5*600).
Mark the first event RDY, and then run the Contracts Billing Interface process. When you run this process, the system creates the following entries in the CA_BP_XREF table:
| Field | Row 1 | Row 2 |
|---|---|---|
|
CONTRACT_NUM |
CA1 |
CA1 |
|
BILL_PLAN_ID |
BP1 |
BP1 |
|
XREF_SEQ_NUM |
1 |
2 |
|
XREF_STATUS |
NEW |
NEW |
|
SYSTEM_SOURCE |
CBI |
CBI |
|
EVENT_OCCURRENCE |
1 |
1 |
|
BPLAN_LN_NBR |
1 |
2 |
|
CONTRACT_LINE_NUM |
|
|
|
NET_AMOUNT |
200 |
300 |
|
GROSS_AMOUNT |
200 |
300 |
|
BI_CURRENCY_CD |
USD |
USD |
|
BUSINESS_UNIT_BI |
EAST |
EAST |
|
PROCESS_INSTANCE |
123123 |
123123 |
|
TEMP_INVOICE |
|
|
|
INVOICE |
|
|
|
INVOICE_TYPE |
|
|
|
INVOICE_DT |
|
|
|
NET_EXTENDED_AMT |
|
|
|
GROSS_EXTENDED_AMT |
200 |
300 |
|
CONTRACT_PPD_SEQ |
|
|
|
BUSINESS_UNIT_PC |
|
|
|
PROJECT |
|
|
|
LASTUPDDTTM |
1-DEC-1998 10:30:22 |
1-DEC-1998 10:30:22 |
|
LASTUPDOPRID |
OPRID that ran the Contracts Billing Interface process |
OPRID that ran the Contracts Billing Interface process |
After you have successfully run the Contracts Billing Interface process, run the billing interface process in PeopleSoft Billing. This process updates the CA_BP_XREF rows to an XREF_STATUS of RCV (received). This process also adds a TEMP_INVOICE number and inserts the date into the LASTUPDDTTM field:
| Field | Row 1 | Row 2 |
|---|---|---|
|
CONTRACT_NUM |
CA1 |
CA1 |
|
BILL_PLAN_ID |
BP1 |
BP1 |
|
XREF_SEQ_NUM |
1 |
2 |
|
XREF_STATUS |
RCV |
RCV |
|
SYSTEM_SOURCE |
CBI |
CBI |
|
EVENT_OCCURRENCE |
1 |
1 |
|
BPLAN_LN_NBR |
1 |
2 |
|
CONTRACT_LINE_NUM |
|
|
|
NET_AMOUNT |
200 |
300 |
|
GROSS_AMOUNT |
200 |
300 |
|
BI_CURRENCY_CD |
USD |
USD |
|
BUSINESS_UNIT_BI |
EAST |
EAST |
|
PROCESS_INSTANCE |
123123 |
123123 |
|
TEMP_INVOICE |
TMP-000234 |
TMP-000234 |
|
INVOICE |
|
|
|
INVOICE_TYPE |
|
|
|
INVOICE_DT |
|
|
|
NET_EXTENDED_AMT |
|
|
|
GROSS_EXTENDED_AMT |
200 |
300 |
|
CONTRACT_PPD_SEQ |
|
|
|
BUSINESS_UNIT_PC |
|
|
|
PROJECT |
|
|
|
LASTUPDDTTM |
1-DEC-1998 12:43:02 |
1-DEC-1998 12:43:02 |
|
LASTUPDOPRID |
OPRID that ran the billing interface |
OPRID that ran the billing interface |
The billing administrator accepting the Billing Worksheet to which these rows were written triggers the next update to the CA_BP_XREF table. The system updates the XREF_STATUS for rows that were accepted in the Billing Worksheet to a status of ACP (accepted). The system also inserts the actual invoice number, inserts the date in the LASTUPDDTTM field, and adds the user ID of the user who accepted the bills to the LASTUPDOPRID field:
| Field | Row 1 | Row 2 |
|---|---|---|
|
CONTRACT_NUM |
CA1 |
CA1 |
|
BILL_PLAN_ID |
BP1 |
BP1 |
|
XREF_SEQ_NUM |
1 |
2 |
|
XREF_STATUS |
ACP |
ACP |
|
SYSTEM_SOURCE |
CBI |
CBI |
|
EVENT_OCCURRENCE |
1 |
1 |
|
BPLAN_LN_NBR |
1 |
2 |
|
CONTRACT_LINE_NUM |
|
|
|
NET_AMOUNT |
200 |
300 |
|
GROSS_AMOUNT |
200 |
300 |
|
BI_CURRENCY_CD |
USD |
USD |
|
BUSINESS_UNIT_BI |
EAST |
EAST |
|
PROCESS_INSTANCE |
123123 |
123123 |
|
TEMP_INVOICE |
TMP-000234 |
TMP-000234 |
|
INVOICE |
112233 |
112233 |
|
INVOICE_TYPE |
|
|
|
INVOICE_DT |
|
|
|
NET_EXTENDED_AMT |
|
|
|
GROSS_EXTENDED_AMT |
200 |
300 |
|
CONTRACT_PPD_SEQ |
|
|
|
BUSINESS_UNIT_PC |
|
|
|
PROJECT |
|
|
|
LASTUPDDTTM |
3-DEC-1998 09:43:20 |
3-DEC-1998 09:43:20 |
|
LASTUPDOPRID |
OPRID that accepted the worksheet |
OPRID that accepted the worksheet |
After the billing administrator has finalized the invoice in PeopleSoft Billing, the last update to the CA_BP_XREF table occurs when the Update Contract/Projects Data process (BIPCC000) in PeopleSoft Billing is run. The system updates the XREF_STATUS to FIN (finalized), INVOICE_TYPE, and inserts values for the billing currency code (BI_CURRENCY_CD), the net extended amount (NET_EXTENDED_AMT), and gross extended amount (GROSS_EXTENDED_AMT). The system then inserts the date in the LASTUPDDTTM field and adds the user ID of the user who finalized the invoice:
| Field | Row 1 | Row 2 |
|---|---|---|
|
CONTRACT_NUM |
CA1 |
CA1 |
|
BILL_PLAN_ID |
BP1 |
BP1 |
|
XREF_SEQ_NUM |
1 |
2 |
|
XREF_STATUS |
FIN |
FIN |
|
SYSTEM_SOURCE |
CBI |
CBI |
|
EVENT_OCCURRENCE |
1 |
1 |
|
BPLAN_LN_NBR |
1 |
2 |
|
CONTRACT_LINE_NUM |
|
|
|
NET_AMOUNT |
200 |
300 |
|
GROSS_AMOUNT |
200 |
300 |
|
BI_CURRENCY_CD |
USD |
USD |
|
BUSINESS_UNIT_BI |
EAST |
EAST |
|
PROCESS_INSTANCE |
123123 |
123123 |
|
TEMP_INVOICE |
TMP-000234 |
TMP-000234 |
|
INVOICE |
112233 |
112233 |
|
INVOICE_TYPE |
REG |
REG |
|
INVOICE_DT |
5-DEC-1998 |
5-DEC-1998 |
|
NET_EXTENDED_AMT |
200 |
300 |
|
GROSS_EXTENDED_AMT |
200 |
300 |
|
CONTRACT_PPD_SEQ |
|
|
|
BUSINESS_UNIT_PC |
|
|
|
PROJECT |
|
|
|
LASTUPDDTTM |
5-DEC-1998 10:08:02 |
5-DEC-1998 10:08:02 |
|
LASTUPDOPRID |
OPRID that finalized the invoice |
OPRID that finalized the invoice |
Milestone Billing Example Part Two The Credit/Rebill
On January 10, 1999, the customer calls the billing department to complain that tax was charged on line two when it was a nontaxable item. The billing department issues a line level adjustment. Here are the CA_BP_XREF entries for these transactions.
Note:
The system does not make entries to the cross-reference table for adjustments until the invoices for those adjustments are finalized and the Update Contract/Projects Data process is run.
| Field | Row 3 | Row 4 |
|---|---|---|
|
CONTRACT_NUM |
CA1 |
CA1 |
|
BILL_PLAN_ID |
BP1 |
BP1 |
|
XREF_SEQ_NUM |
3 |
4 |
|
XREF_STATUS |
FIN |
FIN |
|
SYSTEM_SOURCE |
FBI |
FBI |
|
EVENT_OCCURRENCE |
1 |
1 |
|
BPLAN_LN_NBR |
2 |
2 |
|
CONTRACT_LINE_NUM |
|
|
|
NET_AMOUNT |
|
|
|
GROSS_AMOUNT |
|
|
|
BI_CURRENCY_CD |
|
|
|
BUSINESS_UNIT_BI |
EAST |
EAST |
|
PROCESS_INSTANCE |
|
|
|
TEMP_INVOICE |
|
|
|
INVOICE |
112234 |
112234 |
|
INVOICE_TYPE |
RAD |
RAD |
|
INVOICE_DT |
10-JAN-1999 |
10-JAN-1999 |
|
NET_EXTENDED_AMT |
300 |
300 |
|
GROSS_EXTENDED_AMT |
300 |
300 |
|
CONTRACT_PPD_SEQ |
|
|
|
BUSINESS_UNIT_PC |
|
|
|
PROJECT |
|
|
|
LASTUPDDTTM |
10-JAN-1999 12:15:23 |
10-JAN-1999 12:15:23 |
|
LASTUPDOPRID |
OPRID that finalized the invoice |
OPRID that finalized the invoice |
Note that the amount here does not show any change. This is because the tax amount is handled in PeopleSoft Billing only.
As-incurred Billing Example
Define two rate-based contract lines.
CA_DETAIL:
| CONTRACT_NUM | CONTRACT_LINE_NUM | DESCR | OTHER FIELDS |
|---|---|---|---|
|
CA2 |
1 |
Consulting Services |
… |
|
CA2 |
2 |
Consulting Services |
… |
CA_BILL_PLAN
You must associate the rate-based lines with an as-incurred billing plan. The as-incurred billing plan does not have an amount associated with it. You bill as work is performed:
| CONTRACT_NUM | BILL_PLAN_ID | AMOUNT |
|---|---|---|
|
CA2 |
BP1 |
|
CA_BP_EVENTS
Billing plan events are optional for as-incurred billing plans. If no billing plan events are defined, you bill for work performed to date when you run the Contracts Billing Interface process:
| CONTRACT_NUM | BILL_PLAN_ID | EVENT_OCCURRENCE | EVENT_DATE | PERCENTAGE |
|---|---|---|---|---|
|
|
|
|
|
|
CA_BP_LINES
You do not define billing plan lines for as-incurred billing.
CA_DETAIL_PROJ
This table stores PeopleSoft Project Costing information related to contract lines. You relate projects to contract lines on the Related Projects page:
| CONTRACT_NUM | CONTRACT_LINE_NUM | BUSINESS_UNIT_PC | PROJECT_ID | ACTIVITY_ID |
|---|---|---|---|---|
|
CA2 |
1 |
PCBU |
PC1 |
A1 |
|
CA2 |
1 |
PCBU |
PC2 |
A1 |
|
CA2 |
2 |
PCBU |
PC1 |
A2 |
CA_BP_XREF
The Billing Plan - History page displays one row per combination of contract line, business unit, and project, even though the billing for that contract line may have included billing for multiple activities. The system inserts this row into the cross-reference table only after the invoice has been finalized in PeopleSoft Billing and the Update Contract/Projects Data process is run:
| Field | Row 1 | Row 2 |
|---|---|---|
|
CONTRACT_NUM |
CA2 |
CA2 |
|
BILL_PLAN_ID |
BP1 |
BP1 |
|
XREF_SEQ_NUM |
1 |
2 |
|
XREF_STATUS |
FIN |
FIN |
|
SYSTEM_SOURCE |
PBI |
PBI |
|
EVENT_OCCURRENCE |
|
|
|
BPLAN_LN_NBR |
1 |
1 |
|
CONTRACT_LINE_NUM |
1 |
2 |
|
NET_AMOUNT |
|
|
|
GROSS_AMOUNT |
|
|
|
BI_CURRENCY_CD |
USD |
USD |
|
BUSINESS_UNIT_BI |
EAST |
EAST |
|
PROCESS_INSTANCE |
|
|
|
TEMP_INVOICE |
|
|
|
INVOICE |
112236 |
112236 |
|
INVOICE_TYPE |
REG |
REG |
|
INVOICE_DT |
31-OCT-1999 |
31-OCT-1999 |
|
NET_EXTENDED_AMT |
400 |
200 |
|
GROSS_EXTENDED_AMT |
400 |
200 |
|
CONTRACT_PPD_SEQ |
|
|
|
BUSINESS_UNIT_PC |
PCBU |
PCBU |
|
PROJECT |
PC1 |
PC2 |
|
LASTUPDDTTM |
31-OCT-1999 07:22:14 |
31-OCT-1999 07:22:14 |
|
LASTUPDOPRID |
OPRID that finalized the invoice |
OPRID that finalized the invoice |