PeopleSoft Enterprise Billing 9.1 PeopleBook

Setting Up the Billing Interface

This chapter discusses how to:

Receive billing activity from external sources.
Populate the INTFC_BI table.
Populate the INTFC_BI_AEDS table.
Populate the INTFC_BI_NOTE table.
Populate the INTFC_BI2 table.
Populate the INTFC_BI_HDR table.
Populate the INTFC_BI_EXSD table.
Populate the INTFC_BI_TAX table.
Use the bill-by identifier with the Billing interface.
Populate identifiers.
Generate consolidated billing through the Billing interface.
Generate paperless invoices through the Billing interface.
Process adjustments through the Billing interface.
Use target-invoice processing with the Billing interface.
Create temporary bills through the Billing interface.
Process bill lines with deferred revenue accounting entries.

Correcting Billing Interface Process Errors

Receiving Billing Activity from External Sources

The PeopleSoft Billing system can accept information from several billing sources. The Billing interface tables (INTFC_BI, INTFC_BI2, INTFC_NOTE, INTFC_BI_AEDS, INTFC_BI_TAX, INTFC_BI_EXSD and INTFC_BI_HDR) act as staging areas for this external source information, holding it until you run the Billing Interface process (BIIF0001).

This section provides an overview of the Billing interface staging area and discusses how to assign zero values to revenue percentage fields that exceed size limits.

Note. When importing data into the Billing interface from an external source, ensure that you round the data to the currency precision of the transaction.

To maintain performance efficiency, the system does not perform edit checks for all of the required fields. Ensure that the source system populates required Billing interface fields with valid data.

Understanding the Billing Interface Staging Area

Consider the Billing interface staging tables as the denormalized form of the online bill data structure. Therefore, the Billing interface staging area supports the online bill data structure, storing one or more rows of data for each line of chargeable activity sent into PeopleSoft Billing.

The type of data stored in the Billing interface is characterized by one of five transaction types.

LINE	Represents a bill line charge. For any bill line presented to the interface staging area, one or more accounting entries may be related. For example, if a charge is presented to the staging area and the revenue is distributed 50 percent to one account and 50 percent to another account, then two account entry (AE) transactions are populated in the Billing interface, one for each of the accounts.
AE (accounting entry)	Represents different types of accounting entries for the LINE transaction. The different types of accounting entries are revenue, deferred revenue, accounts receivable (AR), unbilled accounts receivable (UAR), InterUnit payables, InterUnit expenses, and statistical information. AE transactions for general ledger (GL) are only mandatory for a LINE transaction when PeopleSoft Billing is generating GL accounting distributions.
NOTE	Represents a note or comment for the LINE transaction. Notes or comments may be related to a LINE transaction and may represent bill header notes or comments or bill line notes or comments. In the event that there are multiple notes or comments for a particular LINE transaction, multiple NOTE rows may be populated in the interface staging area for the LINE transaction. Note or comment transactions (NOTE) are not mandatory for LINE transactions.
DS (discount or surcharge)	Represents an optional discount or surcharge for the LINE transaction. Discounts and surcharges may be related to a LINE transaction. In the event that there are multiple discounts or surcharges for a specific LINE transaction, multiple DS rows may be populated in the interface staging area for the LINE transaction. DS transactions are optional for LINE transactions.
DDS (deferred discount surcharge)	Represents deferred accounting distribution for the discount or surcharge of the LINE transaction. When the deferred revenue feature is enabled, each DS entry has DDS accounting distribution.
AHDR (adjustment header)	Represents an adjustment header. This transaction type is used only when adjusting an entire bill (CRALL and RBALL). It is also used to specify values to appear on the rebill header. AHDR is the only transaction type that does not require an associated LINE transaction.

EXSD (excise, sales tax, and VAT detail)

Represents excise, sales tax, and VAT detail. This transaction type is used only for India transactions and is applicable only to transactions from the PeopleSoft Order Management feeder system.

TAX (sales tax detail)

Represents sales tax detail of the LINE transaction. This transaction type is applicable only to transactions from the PeopleSoft Order Management feeder system.

Note. To ensure that the data is populated correctly in the Billing interface staging tables, populate all of the Billing interface fields for which you have valid data. Even though the system provides default values for some fields if you leave them blank, you should populate all fields for which you have valid data. This also reduces the work required by the Billing Interface process and can impact batch performance.

Assigning Zero Values to Revenue Percentage Fields that Exceed Size Limits

When importing from an external source other than a PeopleSoft application and when you have defined the GL Level as BI Creates GL Acct Entries (billing creates general ledger accounting entries) on the Installation Options - Billing - GL/AR Options page, the source system must assign a zero value to all revenue (DST) percentage fields if they exceed the +/-999.99 size limit. The source system cannot successfully insert into the interface tables if the Revenue Percentage field values exceed this size limit.

Additionally, for bill lines with zero-dollar gross extended amounts, you must assign a zero value to all revenue (DST) percentage fields.

A bill line revenue percentage might exceed the +/-999.99 size limit, for example, when there exists a sizable discrepancy between the line amount and the gross amount.

Note. Discount and surcharge percentages must not exceed the +/-999.99 field size limit.

Populating the INTFC_BI Table

This section provides an overview of the INTFC_BI table and discusses how to:

Populate the INTFC_BI table for LINE transactions.
Populate the INTFC_BI table for NOTE transactions.
Populate the INTFC_BI table for AHDR transactions.

Understanding the INTFC_BI Table

The following four attributes comprise the key to the Billing Interface table (INTFC_BI):

INTFC_ID (interface ID)	Represents a batch of billing activity, that is, a collection of billing activity that may be produced by a billing source system. Some systems may generate a batch each night. Other systems may produce a batch for a certain kind of billing activity. When assigning a new INTFC_ID for a batch of data, the Last BI Interface ID field (INSTALLATION_BI.LAST_INTFC_ID) on the Installation Options – Billing General page can be used to ensure that a unique number is assigned. The source system can increase this number by one and use that number for the new batch of data.
INTFC_LINE_NUM (interface line number)	Represents a bill line charge. For each interface ID (batch of billing activity), there may be multiple interface line numbers, one for each bill line charge in the group.
TRANS_TYPE_BI (transaction type billing)	Transaction type. Characterizes the type of data being stored. Options are LINE, NOTE, and AHDR: Each LINE within an interface ID should be assigned a unique interface line number. Each LINE may have multiple NOTE transactions. When providing AHDR transactions, there should be only one AHDR row for each interface line number. In this scenario, you may only associate NOTE transaction types with the same interface line number and interface ID as this AHDR row.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	Transaction type sequence. Part of the key used to provide uniqueness in the event that there are multiple notes or comments for a bill line charge. For a LINE transaction, set this attribute to 0 (zero).

Populate the INTFC_BI table for LINE, NOTE, and AHDR transactions only. For each bill line charge added as a bill line to the bill data structure, the Billing Interface table contains one row of data with a transaction type of LINE. For each bill line charge row with a transaction type of LINE, the Billing Interface table can contain one or more notes or comments (NOTES).

Note. To ensure VAT data integrity, you must run the VAT Defaulting process after the Billing Interface process when importing bills with VAT data.

Populating the INTFC_BI table for LINE transactions

The following table demonstrates how to populate the INTFC_BI fields for LINE transactions:

Field Number	Field Name	Required for LINE Transaction?	Remarks
1	INTFC_ID (interface ID)	Required.	Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required.	Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI (transaction type)	Required.	Value must be LINE.
4	TRANS_TYPE_BI_SEQ (transaction type sequence)	Required.	Initialize to zero for LINE transaction type.
5	HDR_FIELDS_KEY	Populate whenever a record is inserted into the INTFC_BI_HDR table.	Populate whenever a record is inserted into the INTFC_BI_HDR table.
6	HDR_FIELDS_BILL_BY	Leave blank.	Leave blank.
7	ADJ_TRANS_TYPE (adjustment transaction type)	Required if the line is part of an adjustment.	Must be RBALL if line is a delta line for a Rebill Entire Bill. Select CRLIN for Credit Line, RBLIN for Rebill Line, and NTLIN for Net Line.
8	CREATE_NEW_BILL	Optional.	N is the default value.
9	TMP_BILL_FLG (temporary bill flag)	Optional.	N is the default value. Bills with this set to Y are created in TMR status.
10	ENTRY_TYPE	Optional.	Optional.
11	ENTRY_REASON	Optional.	Optional.
12	ENTRY_EVENT	Conditional	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
13	LOAD_STATUS_BI	Optional.	May initialize to NEW or leave blank.
14	ERROR_STATUS_BI	Leave blank.	Leave blank.
15	BUSINESS_UNIT (billing business unit)	Required.	Must be a valid billing business unit.
16	BUSINESS_UNIT_GL	Leave blank.	Leave blank.
17	BILL_TO_CUST_ ID (bill-to customer)	Required.	Must be a valid bill-to customer.
18	ADDRESS_SEQ_NUM (address sequence number)	Required for India tax transactions populated by PeopleSoft Order Management.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
19	BILL_TO_COPIES	Leave blank.	Leave blank.
20	CNTCT_SEQ_NUM (contact sequence number)	Conditional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
21	NAME1 (customer name)	Leave blank.	Leave blank.
22	INTERUNIT_FLG	Leave blank.	Leave blank.
23	BUSINESS_UNIT_TO	Required if an InterUnit flag is active and the customer default does not provide a value.	If not populated and if the customer is an InterUnit customer, the system uses the BUSINESS_UNIT_GL value from the CUST_OPTION table, based on the customer ID. If the system cannot obtain this value, it marks the transaction in error.
24	DIRECT_INVOICING	Optional.	Bills set to Y are created in RDY bill status. If provided, it must be valid and included in the bill-by definition. If not provided, defaults to N.
25	RANGE_SELECTION_ID	Optional.	Used in range selection options and with direct invoicing.
26	BILL_SOURCE_ID	Required only if invoice numbering by bill source.	Must be a valid bill source if provided.
27	BILL_TYPE_ID	Required.	Must be a valid bill type.
28	BILL_CYCLE_ID	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
29	BILL_BY_ID (bill-by identifier)	Optional.	Must be valid if provided. Defaults if left blank.
30	PAYMENT_METHOD (payment method)	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
31	PYMNT_TERMS_CD (payment terms code)	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
32	BANK_CD (bank code)	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
33	BANK_ACCT_KEY	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
34	BI_CURRENCY_CD (billing transaction currency)	Required.	It must be a valid currency
35	BASE_CURRENCY	Leave blank.	Leave blank.
36	CUR_RT_TYPE (currency rate type)	Optional.	Must be valid if provided. Defaults if left blank.
37	RATE_MULT (rate multiplier)	Required if CUR_RT_SOURCE is U (user defined).	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 0 (zero)
38	RATE_DIV (rate divisor)	Required if CUR_RT_SOURCE is U (user defined).	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 1.
39	CUR_RT_SOURCE (currency rate source)	Optional.	Defaults to T (from tables) if blank. If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
40	INVOICE_DT (invoice date)	Optional.	Optional.
41	ACCOUNTING_DT (accounting date)	Optional.	Optional.
42	ACCRUE_UNBILLED	Leave blank.	Leave blank.
43	TARGET_INVOICE	Optional.	If passed, target invoice becomes the invoice number. Note. Non-Contracts or Project Costing invoices should not be used as the target for Contracts or Project Costing lines.
44	INVOICE	Leave blank.	Use the TARGET_INVOICE field to specify an invoice number.
45	DOC_TYPE (document type)	Optional.	Optional.
46	CONSOL_SETID (consolidation customer setID)	Populate if generating consolidated bill headers across bill-to customers through the Billing interface.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
47	CONSOL_CUST_ID (consolidation customer ID)	Populate if generating consolidated bill headers across bill-to customers through the Billing interface.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
48	CONSOL_KEY (consolidation key)	Populate if generating consolidated bill headers through the Billing interface.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
49	INVOICE_TO_ADJ	Required for ADJ_TRANS_TYPES of CRLIN, RBLIN, NTLIN, and RBALL.	Must be a valid invoice.
50	ADJ_DELTA_ACTION	Required for ADJ_TRANS_TYPES of RBALL.	Must be ADD for new lines, RPL for lines to be replaced, and DEL for lines to be deleted.
51	LINE_SEQ_TO_ADJ	Required for ADJ_TRANS_TYPES of CRLIN, RBLIN, and NTLIN. Also required for RBALL except when ADJ_DELTA_ACTION is DEL.	Must be a valid line sequence.
52	LINE_SEQ_NUM	Leave blank.	Leave blank.
53	LINE_DST_SEQ_NUM	Leave blank.	Leave blank.
54	LINE_DFR_SEQ_NUM	Leave blank.	Leave blank.
55	LINE_UAR_SEQ_NUM	Leave blank.	Leave blank.
56	LAST_NOTE_SEQ_NUM	Leave blank.	Leave blank.
57	NOTES_SEQ_NUM	Leave blank.	Leave blank.
58	LINE_TYPE	Required.	Must be a valid translate value.
59	IDENTIFIER (bill charge identifier)	Optional.	See Populating Identifiers.
60	DESCR (bill charge description)	Optional.	For lines from PeopleSoft feeder systems, use the base language description.
61	UNIT_OF_MEASURE	Optional.	Must be valid if provided.
62	QTY (quantity)	Required.	Line charge quantity.
63	ORIG_QTY (original quantity)	Optional.	Used only with PeopleSoft Project Costing integration.
64	UNIT_AMT (unit amount)	Required.
65	LIST_PRICE	Optional.	Optional.
66	PPRC_PROMO_CD (promotion code)	Optional.	Optional.
67	MERCH_TYPE (merchant type)	Optional.	Optional.
68	TAX_CD (tax code)	Must be valid if provided.	If not populated and ship-to customer exists, the system defaults the tax code from the ship-to customer address for non third-party vendor tax transactions.
69	TAX_EXEMPT_CERT (tax exempt certificate)	Optional.	Optional.
70	TAX_EXEMPT_FLG (tax exempt flag)	Optional.	If not provided, the system uses N (no) as the default value.
71	TAX_EXEMPT_RC (tax exempt reason code)	Optional.	Used only with Taxware tax option.
72	TAX_JOB_NUM (tax job number)	Optional.	Used only with Taxware tax option.
73	BI_TAX_TIMING	Optional.	Optional.
74	CUSTOMER_GROUP	Optional.	Used with Vertex tax option.
75	VAT_TXN_TYPE_CD (value-added tax transaction type code)	Optional.	Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process.
76	TAX_CD_VAT (tax code value-added tax)	Conditional.	Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process. Must be populated if VAT applicability is provided and equals T (taxable), X (exonerated), or S (suspended). Must be blank if VAT applicability is provided and equals E (exempt) or O (outside of scope).
77	VAT_APPLICABILITY	Optional.	Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process.
78	VAT_PRODUCT_GROUP	Optional if IDENTIFIER_TBL = SVC, LAB, ITM, ID, G, PRD, or PDA. Otherwise, leave blank.	Applies to VAT transactions only.
79	PROD_GRP_SETID (product group setID)	Optional.	Identifies the SetID to use with the VAT_PRODUCT_GROUP. If left blank when VAT_PRODUCT_GROUP is provided, defaults from the most relevant business unit. Applies to VAT transactions only.
80	IST_TXN_FLG (intrastat transaction flag)	Leave blank.	Applies to VAT transactions only.
81	IDENTIFIER_TBL (identifier table)	Required if IDENTIFIER is populated. Values are ID, D, S, PRD, PDA, CON, ITM, PRM, A,, LAB, SVC, G.	The value entered in the IDENTIFIER and IDENTIFIER_TBL fields must be a valid combination. See Populating Identifiers. If the IDENTIFIER field is populated, and the IDENTIFIER_TBL field is not populated, the system uses G as the default value in the IDENTIFIER_TBL field.
82	SHIP_FROM_LOC (ship-from location)	Optional.	Must be a valid location if provided. Used in conjunction with Taxware or Vertex tax options. Note. For third-party tax transactions with no ship-to address override, you must populate either the SHIP_FROM_LOC field or the ORD_ACCEPT_LOC field for the system to insert a row into the BI_LINE_TAX table.
83	ORD_ACCEPT_LOC (order acceptance location)	Optional.	Must be a valid location if provided. Used in conjunction with Taxware or Vertex tax options. If not provided, the system retrieves as a default value the order acceptance location from the Billing business unit definition. Note. For third-party tax transactions with no ship-to address override, you must populate either the SHIP_FROM_LOC field or the ORD_ACCEPT_LOC field for the system to insert a row into the BI_LINE_TAX table.
84	ORD_ORIGIN_LOC (order origin location)	Optional.	Must be a valid location if provided. Used in conjunction with Taxware tax options. If not provided, the system retrieves as a default value the order origin location from the Billing business unit definition.
85	STORE_LOC (store location)	Optional.	Must be a valid location if provided. Used in conjunction with Taxware or Vertex tax options.
86	TITLE_PASSAGE	Optional.	Must be valid if provided. Used in conjunction with Taxware tax options.
87	TAX_GROUP	Optional.	Used in conjunction with Taxware or Vertex tax options.
88	TAX_USER_AREA	Optional.	Used in conjunction with Vertex tax options.
89	TAX_TRANS_TYPE (transaction type)	Optional.	Used in conjunction with Taxware or Vertex tax options.
90	TAX_TRANS_SUB_TYPE (transaction subtype)	Optional.	Used in conjunction with Vertex tax options.
91	NET_EXTENDED_AMT (net extended amount)	Leave blank.	Calculated by interface process, depending on gross extended amount, discounts, and surcharges.
92	GROSS_EXTENDED_AMT (gross extended amount)	Required.	Net extended amount, discounts, and surcharges are calculated based on this amount.
93	REV_RECOG_BASIS	Required for deferred revenue recognition.	Defaults from Bill Type definition for deferred revenue transactions. Values are defined by translate table. If set to a value other than blank or INV, indicates whether the line can have deferred accounting entries created.
94	PROJECT_ID	Optional.	You may assign a project reference value here. This value is not automatically associated with the PROJECT_ID. This is not used as a ChartField.
95	BUSINESS_UNIT_OM (PeopleSoft Order Management business unit)	Required if PRODUCT_ID is populated or when India tax transactions are populated by PeopleSoft Order Management.	Identifies Order Management business unit.
96	ORDER_NO (order number)	Optional.	Optional.
97	ORDER_INT_LINE_NO (order line number)	Optional.	Optional.
98	SCHED_LINE_NBR (schedule line number)	Optional.	Optional.
99	DEMAND_SOURCE	Optional.	Optional.
100	DEMAND_LINE_NO (demand line number)	Optional.	Optional.
101	BUSINESS_UNIT_RMA (PeopleSoft Order Management business unit for RMA)	Optional.	Optional.
102	RMA_ID (RMA identifier)	Optional.	Optional.
103	RMA_LINE_NBR (RMA line number)	Optional.	Optional.
104	PRODUCT_ID (product identifier)	Required when PeopleSoft applications populate the IDENITIFIER_TBL with PRD or PDA.	See Populating Identifiers.
105	ORDER_DATE	Conditional.	Required for deferred revenue if recognition basis is ORD (order date).
106	PO_REF (purchase order number)	Optional.	Optional.
107	PO_LINE (purchase order line)	Optional.	Optional.
108	CONTRACT_NUM (contract number)	Optional.	Optional.
109	CONTRACT_DT	Conditional.	Required for deferred revenue if recognition basis is CON (contact date).
110	CONTRACT_TYPE	Optional.	Optional.
111	CONTRACT_LINE_NUM (contract line number)	Optional.	Optional.
112	FREIGHT_TERMS	Optional.	Optional.
113	BILL_OF_LADING	Optional.	Optional.
114	COUNTRY_SHIP_FROM	Required for India tax transactions populated by PeopleSoft Order Management.	If not provided, the system obtains a default value from the ship-from business unit, then from the billing business unit location for VAT transactions.
115	COUNTRY_SHIP_TO	Optional.	If not provided, the system obtains a default value from the ship-to customer location for VAT transactions.
116	SHIP_TO_CUST_ID (ship-to customer)	Required when third-party tax software is associated with a billing business unit, and for India tax transactions populated by PeopleSoft Order Management.	For VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner: If the bill-to customer location is also a ship-to customer location, the bill-to customer becomes the ship-to customer, and the bill-to location becomes the ship-to location. If the bill-to customer location is not a ship-to customer location, the process uses as a default value the customer's primary ship-to customer, if it exists.
117	SHIP_TO_ADDR_NUM (ship-to address)	Required when third-party tax software is associated with a billing business unit and for India tax transactions populated by PeopleSoft Order Management.	For VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner: If the bill-to customer location is also a ship-to customer location, the bill-to customer becomes the ship-to customer, and the bill-to location becomes the ship-to location. If the bill-to customer location is not a ship-to customer location, the process uses as a default value the customer's primary ship-to customer, if it exists.
118	SHIP_ID (shipment ID)	Optional.	Optional.
119	SHIP_TYPE_ID (shipment type)	Optional.	Optional.
120	SHIP_FROM_BU (ship-from business unit)	Required when PeopleSoft applications populate IDENTIFIER with INV_ITEM_ID from MASTER_ITEM_TBL	Identifies shipping business unit.
121	SHIP_DATE	Required for deferred revenue if recognition basis is SHP (ship date).	The date an order is shipped.
122	SHIP_TIME	Optional.	Optional.
123	PACKSLIP_NO (packing slip number)	Optional.	Optional.
124	LC_ID (letter of credit ID)	Optional.	Optional.
125	LOC_DOC_ID (location document ID)	Optional.	Optional.
126	SEQUENCE_NBR (shipment sequence number)	Optional.	Optional.
127	SOLD_TO_CUST_ID (sold to customer)	Optional.	Optional.
128	SOLD_TO_ADDR_NUM (sold to address number.)	Optional.	Optional.
129	BUSINESS_UNIT_PC (PeopleSoft Project Costing business unit)	Optional.	Optional.
130	BUSINESS_UNIT_CA (PeopleSoft Contracts business unit)	Required if PRODUCT_ID from PROD_ITEM table is populated by PeopleSoft Contracts.	Identifies Contracts business unit.
131	RT_EFFDT (rate effective date)	Leave Blank.	Not currently used.
132	BILL_PLAN_ID	Optional.	Optional.
133	PC_DISTRIB_STATUS	Leave blank.	N is the default value if Contract Number and Bill Plan ID are present. If they are not present, I is the default value. Controls integration with PeopleSoft Project Costing.
134	BPLAN_LN_NBR (bill plan line number)	Optional.	Optional.
135	EVENT_OCCURRENCE	Optional.	Optional.
136	XREF_SEQ_NUM (cross-reference sequence number)	Optional.	Optional.
137	CONTRACT_PPD_SEQ (prepaid add sequence)	Optional.	Optional.
138	ANALYSIS_TYPE	Optional.	Optional.
139	RESOURCE_ID	Optional.	Optional.
140	RESOURCE_TYPE	Optional.	Optional.
141	RESOURCE_CATEGORY	Optional.	Optional.
142	RESOURCE_SUB_CAT (resource subcategory)	Optional.	Optional.
143	ACTIVITY_ID	Optional.	Optional.
144	ACTIVITY_TYPE	Optional.	Optional.
145	DIST_CFG_FLAG	Required.	Set to either Y or N. When an item is configurable, set to Y.
146	PRODUCT_KIT_ID	Optional.	Optional.
147	SYSTEM_SOURCE	Optional.	For PeopleSoft Order Management sales orders: OBI. For PeopleSoft Order Management and Inventory returns: OBI. For PeopleSoft Promotions Management: OBI. For PeopleSoft Inventory: IBI. For PeopleSoft Contracts: CBI. For PeopleSoft Project Costing: PBI. For PeopleSoft Asset Managements: ABI. If left blank, the Billing Interface process uses BBI as the default value.
148	EMPLID (employee ID)	Optional.	Optional.
149	EMPL_RCD (number of employee record)	Optional.	Optional.
150	START_DT	Required for deferred revenue if recognition basis is STE (start and end date range).	Use START_DTwith END_DT to specify the period over which revenue should be recognized.
151	END_DT	Required for deferred revenue if recognition basis is STE (start and end date range).	Use START_DTwith END_DT to specify the period over which revenue should be recognized.
152	FROM_DT	Optional.	Optional.
153	TO_DT	Optional.	Optional.
154	SERVICE_CUST_ID (service customer)	Optional.	Optional.
155	SERVICE_ADDR_NUM (service address)	Optional.	Optional.
156	NOTE_TYPE	Leave blank.	Used for NOTE transactions only.
157	STD_NOTE_FLAG (standard note flag)	Leave blank.	Used for NOTE transactions only.
158	INTERNAL_FLAG	Leave blank.	Used for NOTE transactions only.
159	HDR_OR_LINE_NOTE (header or line note flag)	Leave blank.	Used for NOTE transactions only.
160	AR_LVL	Leave blank.	Leave blank.
161	AR_DST_OPT	Leave blank.	Leave blank.
162	GL_LVL	Leave blank.	Leave blank.
163	ENABLE_DFR_REV_FLG	Leave blank.	Leave blank.
164	BILLING_SPECIALIST	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
165	BILLING_AUTHORITY	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
166	BILLING_FREQUENCY	Optional.	ONC (once) is the default value, if left blank.
167	BILL_INQUIRY_PHONE	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
168	SALES_PERSON	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
169	COLLECTOR	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
170	CR_ANALYST	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
171	INVOICE_FORM_ID	Optional.	If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
172	STD_NOTE_CD (standard note code)	Leave blank.	Used for NOTE transactions only.
173	TOT_LINE_DST_AMT	Leave blank.	Leave blank.
174	TOT_LINE_DST_PCT	Leave blank.	Leave blank.
175	TOT_LINE_DFR_PCT	Leave blank.	Leave blank.
176	TOT_LINE_DFR_AMT	Leave blank.	Leave blank.
177	TOT_LINE_UAR_AMT	Leave blank.	Leave blank.
178	TOT_LINE_UAR_PCT	Leave blank.	Leave blank.
179	SSN (social security number)	Optional.	Optional.
180	CHARGE_FROM_DT (charge from date)	Required for deferred revenue if recognition basis is CHG.	Use CHARGE_FROM_DT with CHARGE_TO_DATE to set the revenue recognition period.
181	CHARGE_TO_DT (charge to date)	Required for deferred revenue if recognition basis is CHG.	Use CHARGE_FROM_DT with CHARGE_TO_DATE to set the revenue recognition period.
182	SUBCUST_QUAL1 (subcustomer qualifier 1)	Optional.	If not populated, the system defaults subcustomer1 from bill-to customer setup.
183	SUBCUST_QUAL2 (subcustomer qualifier 2)	Optional.	If not populated, the system defaults subcustomer2 from bill-to customer setup.
184	REIMB_AGREEMENT	Optional.	Optional.
185	TOT_DISCOUNT_AMT	Leave blank.	Leave blank.
186	TOT_SURCHARGE_AMT	Leave blank.	Leave blank.
187	ACCUMULATE	Optional.	Include in cumulative balance (Y/N). If not provided, the system uses Y as the default value.
188	VAT_TREATMENT_GRP	Optional.	Applies to VAT transactions only. If provided, it must be a valid VAT treatment group. If not provided, the system populates with a default value through the VAT Defaulting process.
189	COUNTRY_VAT_BILLFR	Optional.	Applies to VAT transactions only. If provided, it must be a valid VAT country. If not provided, the system populates with a default value through the VAT Defaulting process.
190	COUNTRY_VAT_BILLTO	Optional.	Applies to VAT transactions only. If provided, it must be a valid VAT country. If not provided, the system populates with a default value through the VAT Defaulting process.
191	VAT_TREATMENT	Optional.	Applies to VAT transactions only. If provided, it must be a valid VAT treatment. If not provided, the system populates with a default value through the VAT defaulting process.
192	PHYSICAL_NATURE	Optional.	Use G for goods; S for services. Applies to VAT transactions only. If not provided, the Billing Interface process obtains a default value from the PeopleSoft Billing VAT drivers hierarchy for transactions that are liable for VAT.
193	COUNTRY_LOC_BUYER	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must a valid country. If not provided, the system obtains a default value from the customer's bill-to location.
194	STATE_LOC_BUYER	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid state associated with the buyer's location country. If not provided, the system obtains a default value from the customer's bill-to location. Leave blank when the buyer's location country does not track VAT by state or province.
195	COUNTRY_LOC_SELLER	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid country. If not provided, the system obtains a default value from the appropriate business unit location according to the source of the transaction.
196	STATE_LOC_SELLER	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid state associated with the seller's location country. If not provided, the system obtains a default value from a business unit location, as described for COUNTRY_LOC_SELLER. Leave blank when the seller's location country does not track VAT by state or province.
197	VAT_SVC_SUPPLY_FLG	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must be valid. If not provided, the system populates with a default value through the VAT Defaulting process.
198	VAT_SERVICE_TYPE	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid VAT service type. If not provided, the system populates with a default value through the VAT Defaulting process.
199	COUNTRY_VAT_PERFRM	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided it must be a valid country. If not provided, the system populates with a default value from the PeopleSoft Billing VAT drivers hierarchy.
200	STATE_VAT_PERFRM	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid state associated with the COUNTRY_VAT_PERFRM value. If not provided, the system populates with a default value from the PeopleSoft Billing VAT drivers. Leave blank when the COUNTRY_VAT_PERFRM does not track VAT by state or province.
201	COUNTRY_VAT_SUPPLY	Optional.	Applies only to VAT transactions where the physical nature is S (services). If provided it must be a valid country. If not provided, the system populates with a default value through the VAT Defaulting process.
202	STATE_VAT_SUPPLY	Leave blank.	Leave blank.
203	STATE_SHIP_FROM	Optional.	If provided, it must be a valid state associated with the ship-from country. If not provided, the system obtains a default value as described for COUNTRY_SHIP_FROM. Leave blank when the ship-from country does not track VAT by state or province.
204	STATE_SHIP_TO	Optional.	If provided, it must be a valid state. If not provided, the system obtains a default value from the ship-to customer location for VAT transactions. Leave blank when the ship-to country does not track VAT by state or province.
205	MAST_CONTR_ID	Optional.	Optional.
206	TAX_CUST_ID	Optional.	Used in conjunction with Taxware or Vertex tax options. Populate with customer number defined in Vertex or Taxware to determine tax exemptions. (If blank, tax calculation in PeopleSoft Billing sends ship-to customer to Vertex or Taxware.)
207	BUSINESS_UNIT_AM	Required for Asset Management transactions.	Populated by the asset management system only.
208	BUSINESS_UNIT_AMTO	Required for InterUnit transactions.	Populated by the asset management system only.
209	ASSET_ID	Required for InterUnit transactions.	Populated by asset management system only.
210	PROFILE_ID	Required for InterUnit transactions.	Populated by the asset management system only.
211	COST_TYPE	Required for InterUnit transactions.	Populated by the asset management system only.
212	STATE_VAT_DEFAULT	Optional.	Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process. Leave blank when the VAT reporting country does not track VAT by state or province.
213	SO_ID	Optional.	Optional.
214	BUSINESS_UNIT_RF	Optional.	If populated, use the CRM services business unit value associated with the SO_ID.
215	SOURCE_REF_TYPE	Optional.	Populate if the SOURCE_REF_NO is populated, and use a value that describes the type of generic reference used in the SOURCE_REF_NO field.
216	SOURCE_REF_NO	Optional.	If populated, use a unique generic reference number (that does not already exist on the INTFC_BI table), such as the CRM agreement or CRM case ID.
217	SOURCE_REF_KEY	Optional.	Populate only when SOURCE_REF_NO is also populated, and use a key to the generic reference number. For example, you might use the business unit or SetID.
218	ACCEPTGIRO_IND	Leave blank.	Leave blank.
219	CA_PGP_SEQ	Conditional.	Required for progress payment transactions. Populate with the value in the CA_PGP_SEQ field for the row on the CA_PGP_TERMS table corresponding to the progress payment term entry for this transaction. Leave blank for other transactions.
220	SUM_TEMPLATE_ID	Optional.	Populate with an ID value from the BI_SUM_TEMPLATE table.
221	SUM_GROUP_TYPE	Optional.	If the summarization template identified in the SUM_TEMPLATE_ID field includes the summarization group type, populate with an ID from the BI_SGRP_TYP_TBL.
222	SUM_GROUP_ID	Optional.	If the summarization template identified in the SUM_TEMPLATE_ID field includes the summarization group, populate with an ID from the BI_S_GRP_ID_TBL. Important! The Billing Interface process does not check that the summarization group is a member of the summarization group type.
223	CUST_DEPOSIT_ID	Required when line references a customer deposit.	Must be blank if not used. Otherwise, must match the DEPOSIT_ID on the DEPOSIT_CONTROL table corresponding to the customer's deposit entry.
224	TAX_DATE	Optional.	Enter a date that third-party tax software should use to determine effective tax rates, if this date is different from the invoice date or transaction date.
225	GROUP_CODE	Leave blank.	Leave blank.
226	SRV_PERFORM_LOC	Optional.	If used must correspond to a value in the LOCATION field on LOCATION_TBL. Enter the location where the service will be performed.
227	TAX_DIVISION	Optional.	Defaults from Billing Business Unit.
228	TAX_DEPARTMENT	Optional.	Defaults from Billing Business Unit.
229	PT_SALE_FLG	Optional.	Y or N, defaults to N. Used in tax calculation, this indicates that the customer visited the seller's office for part of the transaction.
231	CUST_PICKUP	Optional.	Indicates that the customer picked up the goods, and the ship-to address is equivalent to the ship-from address.
232	CUSTOMER_PO_SCHED	Leave blank.	Leave blank.
233	PUBLIC_VOUCHER_NBR	Optional	Leave blank to have the Billing Interface assign a PVN number when PVN_GEN_LVL is not blank.
234	PVN_GEN_LVL	Optional	Required for Public Voucher Number assignment. Populated by PeopleSoft Contracts module for PVN processing.
235	USER_AMT1 (user amount 1)	Optional.	User-defined field.
236	USER_AMT2 (user amount 2)	Optional.	User-defined field.
237	USER_DT1 (user date 1)	Optional.	User-defined field.
238	USER_DT2 (user date 1)	Optional.	User-defined field.
239	USER1 (user field 1)	Optional.	User-defined field.
240	USER2 (user field 2)	Optional.	User-defined field.
241	USER3 (user field 3)	Optional.	User-defined field.
242	USER4 (user field 4)	Optional.	User-defined field.
243	USER5 (user field 5)	Optional.	User-defined field.
244	USER6 (user field 6)	Optional.	User-defined field.
245	USER7 (user field 7)	Optional.	User-defined field.
246	USER8 (user field 8)	Optional.	User-defined field.
247	USER9 (user field 9)	Optional.	User-defined field.
248	SETID	Leave blank.	Leave blank.
249	PROCESS_INSTANCE	Leave blank.	The Process Instance ID is set by the Billing Interface process.
250	ADD_DTTM (add date and time)	Optional.	Allows accurate reporting on interface activity. Used by interface workflow functions.
251	LAST_UPDATE_DTTM (last update date and time)	Leave blank.	The last update date and time field is set by the Billing Interface process.
252	VAT_RVRSE_CHG_GDS	Leave blank.	Leave blank.
253	TAX_CD_VAT_RVC	Leave blank.	Leave blank.

Populatinge the INTFC_BI table for NOTE transactions

The following table demonstrates how to populate the INTFC_BI fields for NOTE transactions:

Field Number	Field Name	Required for NOTE Transactions?	Remarks
1	INTFC_ID (interface ID)	Required.	Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required.	Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI (transaction type)	Required.	Value must be NOTE.
4	TRANS_TYPE_BI_SEQ (transaction type sequence)	Required.	If more than one note is populated for a particular LINE transaction, the transaction type sequence must be used for uniqueness. Note. Do not initialize to zero, for note transactions, TRANS_TYPE_BI_SEQ must begin with 1.
13	LOAD_STATUS_BI	Optional.	May initialize to NEW or leave blank.
15	BUSINESS_UNIT (billing business unit)	Required.	Must be a valid billing business unit.
156	NOTE_TYPE	Optional.
157	STD_NOTE_FLAG (standard note flag)	Optional.	Y is the default value if a standard note code (STD_NOTE_CD) exists and the note text (TEXT254) is blank. N is the default value if note text (TEXT254) is populated and standard note code (STD_NOTE_CD) is blank.
158	INTERNAL_FLAG	Required.	Must be Y or N.
159	HDR_OR_LINE_NOTE (header or line note flag)	Optional.	Values are: H (header note) and L (line note). L appears as the default value, if left blank.
184	REIMB_AGREEMENT	Optional.
246	ADD_DTTM	Optional.	Allows accurate reporting on interface activity. Used by interface workflow functions.

Populate the INTFC_BI table for AHDR transactions

The following table demonstrates how to populate the INTFC_BI fields for AHDR transactions:

Field Number	Field Name	Required for AHDR Transactions?	Remarks
1	INTFC_ID (interface ID)	Required.	Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required.	Each unique interface line number for an interface ID with AHDR transaction guarantees uniqueness.
3	TRANS_TYPE_BI (transaction type)	Required.	Value must be AHDR.
4	TRANS_TYPE_BI_SEQ (transaction type sequence)	Required.	Initialize to zero for AHDR transaction type.
7	ADJ_TRANS_TYPE (adjustment transaction type)	Required.	Must be CRALL for Credit Entire Bill or RBALL for Rebill Entire Bill.
9	TMP_BILL_FLG (temporary bill flag)	Leave blank.	Temporary bills are not supported for adjustments.
10	ENTRY_TYPE	Optional.
11	ENTRY_REASON	Optional.
12	ENTRY_EVENT	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
13	LOAD_STATUS_BI	Optional.	May initialize to NEW or leave blank.
15	BUSINESS_UNIT (billing business unit)	Required.	Must be a valid billing business unit.
17	BILL_TO_CUST_ID (bill-to customer)	Required.	Must be a valid bill-to customer. Leave blank for India tax transactions populated by PeopleSoft Order Management. AHDR is not supported for India transactions.
18	ADDRESS_SEQ_NUM (address sequence number)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. Leave blank for India tax transactions populated by PeopleSoft Order Management.
20	CNTCT_SEQ_NUM (contact sequence number)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
23	BUSINESS_UNIT_TO	Conditional.	Leave blank for CRALL For RBALL, if not populated and if the customer is an InterUnit customer, the system uses the BUSINESS_UNIT_GL value from the CUST_OPTION table, based on the customer ID. If the system cannot obtain this value, it marks the transaction in error.
24	DIRECT_INVOICING	Optional.	Bills set to Y are created in RDY bill status. If provided, it must be valid and included in the bill-by definition. If not provided, defaults to N.
25	RANGE_SELECTION_ID	Optional.	Used in range selection options and with direct invoicing.
26	BILL_SOURCE_ID	Required only if invoice numbering by bill source.	Must be a valid bill source if provided.
27	BILL_TYPE_ID	Required.	Must be a valid bill type.
28	BILL_CYCLE_ID	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
29	BILL_BY_ID (bill-by identifier)	Conditional.	Leave blank for CRALL. Must be valid if provided for RBALL. Defaults if left blank.
30	PAYMENT_METHOD (payment method)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
31	PYMNT_TERMS_CD (payment terms code)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
32	BANK_CD (bank code)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
33	BANK_ACCT_KEY	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
34	BI_CURRENCY_CD (billing transaction currency)	Conditional.	Leave blank for CRALL. For RBALL, must be the same currency as the bill being adjusted.
36	CUR_RT_TYPE (currency rate type)	Conditional.	Leave blank for CRALL. Must be valid if provided for RBALL. Defaults if left blank.
37	RATE_MULT (rate multiplier)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 0 (zero)
38	RATE_DIV (rate divisor)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 1.
39	CUR_RT_SOURCE (currency rate source)	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
40	INVOICE_DT (invoice date)	Optional.
41	ACCOUNTING_DT (accounting date)	Optional.
43	TARGET_INVOICE	Optional.	If passed, target invoice becomes the invoice number.
45	DOC_TYPE (document type)	Optional.
46	CONSOL_SETID (consolidation customer setID)	Leave blank.	Not supported for adjustments.
47	CONSOL_CUST_ID (consolidation customer ID)	Leave blank.	Not supported for adjustments.
48	CONSOL_KEY (consolidation key)	Leave blank.	Not supported for adjustments.
49	INVOICE_TO_ADJ	Required.	Invoice to be adjusted must be a valid invoice.
95	BUSINESS_UNIT_OM (PeopleSoft Order Management business unit)	Conditional.	Leave blank for CRALL. Required for RBALL if PRODUCT_ID is populated or when India tax transactions are populated by PeopleSoft Order Management.
96	ORDER_NO (order number)	Optional.	Leave blank for CRALL. Optional for RBALL.
102	RMA_ID (RMA identifier)	Optional.	Leave blank for CRALL. Optional for RBALL.
103	RMA_LINE_NBR (RMA line number)	Optional.	Leave blank for CRALL. Optional for RBALL.
105	ORDER_DATE	Conditional.	Leave blank for CRALL. For RBALL, required for deferred revenue if recognition basis is ORD (order date).
106	PO_REF (purchase order number)	Optional.	Leave blank for CRALL. Optional for RBALL.
114	COUNTRY_SHIP_FROM	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. If not provided for RBALL, the system obtains a default value from the ship-from business unit, then from the billing business unit location for VAT transactions.
115	COUNTRY_SHIP_TO	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. If not provided for RBALL, the system obtains a default value from the ship-to customer location for VAT transactions.
116	SHIP_TO_CUST_ID (ship-to customer)	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. For RBALL VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner: If the bill-to customer location is also a ship-to customer location, the bill-to customer becomes the ship-to customer, and the bill-to location becomes the ship-to location. If the bill-to customer location is not a ship-to customer location, the process uses as a default value the customer's primary ship-to customer, if it exists.
117	SHIP_TO_ADDR_NUM (ship-to address)	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. For RBALL VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner: If the bill-to customer location is also a ship-to customer location, the bill-to customer becomes the ship-to customer, and the bill-to location becomes the ship-to location. If the bill-to customer location is not a ship-to customer location, the process uses as a default value the customer's primary ship-to customer, if it exists.
118	SHIP_ID (shipment ID)	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. Optional for RBALL.
119	SHIP_TYPE_ID (shipment type)	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. Optional for RBALL.
120	SHIP_FROM_BU (ship-from business unit)	Optional.	Leave blank for CRALL. Optional for RBALL.
123	PACKSLIP_NO (packing slip number)	Optional.	Leave blank for CRALL. Optional for RBALL.
124	LC_ID (letter of credit ID)	Optional.	Leave blank for CRALL. Optional for RBALL.
125	LOC_DOC_ID (location document ID)	Optional.	Leave blank for CRALL. Optional for RBALL.
127	SOLD_TO_CUST_ID (sold to customer)	Optional.	Leave blank for CRALL. Optional for RBALL.
128	SOLD_TO_ADDR_NUM (sold to address number.)	Optional.	Leave blank for CRALL. Optional for RBALL.
129	BUSINESS_UNIT_PC (PeopleSoft Project Costing business unit)	Optional.	Leave blank for CRALL. Optional for RBALL.
130	BUSINESS_UNIT_CA (PeopleSoft Contracts business unit)	Conditional.	Leave blank for CRALL. Required for RBALL if PRODUCT_ID from PROD_ITEM table is populated by PeopleSoft Contracts.
132	BILL_PLAN_ID	Optional.	Leave blank for CRALL. Optional for RBALL.
134	BPLAN_LN_NBR (bill plan line number)	Optional.	Leave blank for CRALL. Optional for RBALL.
135	EVENT_OCCURRENCE	Optional.	Leave blank for CRALL. Optional for RBALL.
137	CONTRACT_PPD_SEQ (prepaid add sequence)	Optional.	Leave blank for CRALL. Optional for RBALL.
138	ANALYSIS_TYPE	Optional.	Leave blank for CRALL. Optional for RBALL.
140	RESOURCE_TYPE	Optional.	Leave blank for CRALL. Optional for RBALL.
141	RESOURCE_CATEGORY	Optional.	Leave blank for CRALL. Optional for RBALL.
142	RESOURCE_SUB_CAT (resource subcategory)	Optional.	Leave blank for CRALL. Optional for RBALL.
143	ACTIVITY_ID	Optional.	Leave blank for CRALL. Optional for RBALL.
144	ACTIVITY_TYPE	Optional.	Leave blank for CRALL. Optional for RBALL.
145	DIST_CFG_FLAG	Conditional.	Leave blank for CRALL. For RBALL, set to either Y or N. When an item is configurable, set to Y.
146	PRODUCT_KIT_ID	Conditional.	Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. Optional for RBALL.
147	SYSTEM_SOURCE	Same as LINE for RBALL. See Understanding Guidelines for Creating Adjustments.	Leave blank for CRALL. For RBALL of PeopleSoft Order Management sales orders: OBI. For RBALL of PeopleSoft Order Management and Inventory returns: OBI. For RBALL of PeopleSoft Promotions Management: OBI. For RBALL of PeopleSoft Inventory: IBI. For PeopleSoft Contracts: CBI. For RBALL of PeopleSoft Project Costing: PBI. For RBALL of PeopleSoft Asset Managements: ABI. If left blank, the Billing Interface process uses BBI as the default value.
148	EMPLID (employee ID)	Optional.	Leave blank for CRALL. Optional for RBALL.
150	START_DT	Conditional.	Leave blank for CRALL. Required for RBALL with deferred revenue if recognition basis is STE (start and end date range).
151	END_DT	Conditional.	Leave blank for CRALL. Required for RBALL with deferred revenue if recognition basis is STE (start and end date range).
152	FROM_DT	Optional.	Leave blank for CRALL. Optional for RBALL.
153	TO_DT	Optional.	Leave blank for CRALL. Optional for RBALL.
154	SERVICE_CUST_ID (service customer)	Optional.	Leave blank for CRALL. Optional for RBALL.
155	SERVICE_ADDR_NUM (service address)	Optional.	Leave blank for CRALL. Optional for RBALL.
164	BILLING_SPECIALIST	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
165	BILLING_AUTHORITY	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
166	BILLING_FREQUENCY	Conditional.	Leave blank for CRALL. For RBALL, ONC (once) is the default value, if left blank.
167	BILL_INQUIRY_PHONE	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
168	SALES_PERSON	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
169	COLLECTOR	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
170	CR_ANALYST	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
171	INVOICE_FORM_ID	Conditional.	Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy.
179	SSN (social security number)	Optional.	Leave blank for CRALL. Optional for RBALL.
182	SUBCUST_QUAL1 (subcustomer qualifier 1)	Conditional.	Leave blank for CRALL. If not populated for RBALL, the system defaults subcustomer1 from bill-to customer setup.
183	SUBCUST_QUAL2 (subcustomer qualifier 2)	Conditional.	Leave blank for CRALL. If not populated for RBALL, the system defaults subcustomer2 from bill-to customer setup.
184	REIMB_AGREEMENT	Optional.
231	USER_AMT1 (user amount 1)	Optional.	Leave blank for CRALL. Optional for RBALL.
232	USER_AMT2 (user amount 2)	Optional.	Leave blank for CRALL. Optional for RBALL.
233	USER_DT1 (user date 1)	Optional.	Leave blank for CRALL. Optional for RBALL.
234	USER_DT2 (user date 1)	Optional.	Leave blank for CRALL. Optional for RBALL.
235	USER1 (user field 1)	Optional.	Leave blank for CRALL. Optional for RBALL.
236	USER2 (user field 2)	Optional.	Leave blank for CRALL. Optional for RBALL.
237	USER3 (user field 3)	Optional.	Leave blank for CRALL. Optional for RBALL.
238	USER4 (user field 4)	Optional.	Leave blank for CRALL. Optional for RBALL.
239	USER5 (user field 5)	Optional.	Leave blank for CRALL. Optional for RBALL.
240	USER6 (user field 6)	Optional.	Leave blank for CRALL. Optional for RBALL.
241	USER7 (user field 7)	Optional.	Leave blank for CRALL. Optional for RBALL.
242	USER8 (user field 8)	Optional.	Leave blank for CRALL. Optional for RBALL.
243	USER9 (user field 9)	Optional.	Leave blank for CRALL. Optional for RBALL.
246	ADD_DTTM	Optional.	Allows accurate reporting on interface activity. Used by interface workflow functions.

Populating the INTFC_BI_AEDS Table

This section provides an overview of the INTFC_BI_AEDS table and discusses how to populate the INTFC_BI_AEDS table.

Understanding the INTFC_BI_AEDS Table

The Billing Interface Accounting Entry and Discount/Surcharge table (INTFC_BI_AEDS) contains only AE, DDS and DS transactions. The following four attributes comprise the key to the INTFC_BI_AEDS table.

INTFC_ID (interface ID)	Represents a group or batch of billing activity, that is, a collection of billing activity that may be produced by a billing source system. For example, a system may generate a group or batch each night, while another may produce a group or batch for a certain kind of billing activity.
INTFC_LINE_NUM (interface line number)	With INTFC_ID, identifies the bill line charge on the INTFC_BI table to which this accounting entry, discount, or surcharge applies.
TRANS_TYPE_BI (transaction type billing)	Characterizes the type of data being stored. Options are: AE (bill line accounting entry). DS (bill line discount or surcharge). DDS (bill line deferred discount or surcharge entry). For each interface line number associated with an interface ID, there should be only one row of transaction type LINE in the INTFC_BI table. There can be multiple rows with transaction types containing AE, DS, or DDS values in the INTFC_BI_AEDS table. When the deferred revenue feature is enabled, bill lines using revenue recognition basis other than INV (invoice date) must have deferred revenue ChartFields associated with the revenue ChartFields.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	The part of the key that provides uniqueness in the event that there are multiple AE, DS, or DDS transactions for a bill line charge.

Populating the INTFC_BI_AEDS Table for AE, DS and DDS

For each bill line charge added as a bill line to the bill data structure, the Billing Interface table contains one row of data with a transaction type of LINE. For each bill line charge row with a transaction type of LINE, the Billing Interface Accounting Entry, Discount, and Surcharge table (INTFC_BI_AEDS) can contain accounting entries (AE), discounts or surcharges (DS), and discount or surcharge deferred accounting entries (DDS).

The following table demonstrates how to populate the INTFC_BI_AEDS table:

Field Number	Field Name	AE	DS	DDS
1	INTFC_ID (interface ID)	Required. Used to group or batch a collection of Billing interface activity.	Required. Used to group or batch a collection of Billing interface activity.	Required. Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required. Each unique interface line number for an interface ID represents a separate bill line charge.	Required. Each unique interface line number for an interface ID represents a separate bill line charge.	Required. Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI (transaction type)	Required. Value must be AE.	Required. Value must be DS.	Required. Value must be DDS.
4	TRANS_TYPE_BI_SEQ (transaction type sequence) Warning! Cannot exceed three digits	Required. If more than one accounting entry is populated for a particular LINE transaction, the transaction type sequence must be used for uniqueness.	Required. If more than one discount or surcharge is populated for a particular LINE transaction, the transaction type sequence must be used for uniqueness.	Required. If more than one discount or surcharge is populated for a particular LINE transaction, the transaction type sequence must be used for uniqueness. DDS rows have a one-to-one relationship with DS rows.
5	ACCT_ENTRY_TYPE	Required. Must be AR for AR offset entries, RR for regular revenue entries, DR for deferred revenue, IP for InterUnit payables, IE for InterUnit expenses, ST for statistical entry, and UAR for unbilled AR.	Leave blank.	Leave blank.
6	LOAD_STATUS_BI (load status)	Optional. May initialize to NEW or leave blank.	Optional. May initialize to NEW or leave blank.	Optional. May initialize to NEW or leave blank.
7	ERROR_STATUS_BI	Leave blank.	Leave blank.	Leave blank.
8	BUSINESS_UNIT (billing business unit)	Required. Must be a valid billing business unit.	Required. Must be a valid billing business unit.	Required. Must be a valid billing business unit.
9	INVOICE	Leave blank.	Leave blank.	Leave blank.
10	LINE_SEQ_NUM	Leave blank.	Leave blank.	Leave blank.
11	LINE_DST_SEQ_NUM	Leave blank.	Leave blank.	Leave blank.
12	DST_ID (distribution code)	Optional. Must be valid if provided.	Optional. Defaults from discount, surcharge ID (DISC_SUR_ID) if DISC_SUR_ID is provided.	Leave blank.
13	DST_ID_DFR	Leave blank.	Leave blank.	Optional. Appears by default from the discount surcharge line's distribution ID. Must be present if no ACCOUNT is provided.
14	DISC_SUR_LVL (discount, surcharge level)	Leave blank.	Optional. Defaults to 1 if less than one. If the charge line has more than one level of discount or surcharge, you must provide unique values for each discount surcharge level.	Optional. Defaults to 1 if less than one. If the charge line has more than one level of discount or surcharge, you must provide unique values for each discount surcharge level.
15	DISC_SUR_INDICATOR (discount or surcharge indicator)	Leave blank.	Optional. Values are: D (discount), S (surcharge). Defaults to D if left blank.	Leave blank.
16	DISC_SUR_ID (discount or surcharge identifier)	Leave blank.	Required.	Required.
17	DESCR	Leave blank.	If not populated, the system obtains a default value from the Discount & Surcharge table. For PeopleSoft application systems, use base language description, if populated.	Leave blank.
18	AMOUNT (accounting entry amount)	Required. Sum of accounting entry amounts for a particular LINE transaction must equal GROSS_EXTENDED_AMT on the LINE transaction.	Optional. Appears by default from the value that is associated with the discount or surcharge ID (DISC_SUR_ID) if DISC_SUR_ID is provided.	Leave blank.
19	PERCENTAGE (discount or surcharge percentage)	Required. Accounting entry percent. Sum of accounting entry percents for a particular LINE transaction must equal 100 percent.	Optional. Appears by default from the value that is associated with the discount or surcharge ID (DIS_SUR_ID) if DISC_SUR_ID is provided.	Leave blank.
20	BI_CURRENCY_CD	Leave blank.	Leave blank.	Leave blank.
21	BASE_CURRENCY	Leave blank.	Leave blank.	Leave blank.
22	BUSINESS_UNIT_GL	Leave blank.	Leave blank.	Leave blank.
23	BUSINESS_UNIT_TO	Leave blank.	Leave blank.	Leave blank.
24	TARGET_INVOICE	Leave blank.	Leave blank.	Leave blank.

Fields 25 through 40 describe ChartFields as they are initially delivered in the system. By using ChartField configuration, you can define the ChartFields differently. The behavior described here provides general reference for how ChartFields are handled in this context.

Configurable ChartFields can be fully configurable (identified below by F), partially configurable (identified below by P), or affiliate ChartFields (identified below by A).

Note. If you selected the Customer Vendor Affiliate option (BUS_UNIT_TBL_GL.CUST_VNDR_AFFILIATE = Y) on the General Ledger Definition - Definition page, the system ignores any affiliate values that you provide to the Billing interface tables when creating bills. In this scenario, the system automatically populates affiliate fields by using default values.

See Setting Up Ledgers.

The following table demonstrates how to populate the INTFC_BI_AEDS table:

Note. When a feeder system passes the DST_ID (distribution code) and an account value, the system ignores the account and the ChartField data on the INTFC_BI_AEDS table. It will use the default values from the DST_ID setup obtained from subsequent accounting processing (the Pre-Load process, the Load GL process, and the Load AR process). To preserve the feeder system ChartField information on the invoice and on the accounting entries, feeder systems must pass only the account value.

Populating the INTFC_BI_NOTE Table

This section provides an overview of the INTFC_BI_NOTE table and discusses how to populate the INTFC_BI_NOTE table.

Understanding the INTFC_BI_NOTE Table

The Billing Interface Note/Comment table (INTFC_BI_NOTE) contains the text of nonstandard notes and comments. Each record corresponds to a record on the INTFC_BI table having a transaction type of NOTE. The following four attributes comprise the key to the INTFC_BI_NOTE table:

INTFC_ID (interface ID)	Represents a group or batch of billing activity—that is, a collection of billing activity that may be produced by a billing source system. For example, a system may generate a group or batch each night, while another may produce a group or batch for a certain kind of billing activity.
INTFC_LINE_NUM (interface line number)	With INTFC_ID, identifies the NOTE record on the INTFC_BI table to which this note entry applies.
TRANS_TYPE_BI (transaction type billing)	Characterizes the type of data being stored. NOTE (custom note or comment) is the only valid option.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	Part of the key that provides uniqueness in the event that there are multiple notes or comments for a bill line charge.

Populating the INTFC_BI_NOTE Table for standard notes

The INTFC_BI_NOTE table has the same key structure as the INTFC_BI table; consider it an extension of the INTFC_BI table. In addition to the key fields, the table contains one additional column: TEXT254. Populate this table to pass nonstandard notes along with an interface transaction line. The TEXT254 column is used to hold the note text. The value of the TRANS_TYPE_BI column for the INTFC_BI_NOTE table must be NOTE.

For every row in INTFC_BI_NOTE, there must exist a row in INTFC_BI with the same key values. You do not, however, need a row in INTFC_BI_NOTE for every row in INTFC_BI.

If you are passing standard notes (the note is already predefined in the PeopleSoft Billing system), you do not need to pass an associated INTFC_BI_NOTE row. Specify the note code in the STD_NOTE_CD column.

If you elect to pass a nonstandard note in INTFC_BI_NOTE, the associated row in INTFC_BI must have the standard note code column (STD_NOTE_CD) set to blank.

The following table demonstrates how to populate the INTFC_BI_NOTE table:

Field Number	Field	NOTE
1	INTFC_ID (interface ID)	Required. Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required. Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI (transaction type)	Required. Value must be NOTE.
4	TRANS_TYPE_BI_SEQ (transaction type sequence)	Required. If more than one note is populated for a particular LINE transaction, the transaction type sequence must be used for uniqueness. Note. For note transactions, do not initialize TRANS_TYPE_BI_SEQ to zero. For note transactions, TRANS_TYPE_BI_SEQ must begin with 1.
5	PROCESS_INSTANCE	Leave blank.
6	TEXT254 (note text)	Required if standard note (STD_NOTE_CD) is left blank on the associated row in INTFC_BI.
7	ADD_DTTM	Required for accurate reporting purposes and for taking advantage of interface workflow function.
8	LAST_UPDATE_DTTM	Leave blank.

Populating the INTFC_BI2 Table

This section provides an overview of the INTFC_BI2 table and discusses how to populate the INTFC_BI2 table.

Understanding the INTFC_BI2 Table

The Billing Interface Extension table (INTFC_BI2) (used for extended tax information, such as prepaid taxes, ship-to address overrides, and India transactions) contains LINE transactions only. India related fields are populated only by PeopleSoft Order Management. The following four attributes comprise the key to the INTFC_BI2 table:

Note. India tax functionality is supported only for PeopleSoft Order Management and only for net line adjustments (adjustment transaction type = NTLIN).

INTFC_ID (interface ID)	Represents a group or batch of billing activity—that is, a collection of billing activity that may be produced by a billing source system. For example, a system may generate a group or batch each night, while another may produce a group or batch for a certain kind of billing activity.
INTFC_LINE_NUM (interface line number)	Represents a bill line charge. For each interface ID (group or batch of billing activity), there may be multiple interface line numbers, one for each bill line charge in the group.
TRANS_TYPE_BI (transaction type billing)	Characterizes the type of data being stored. LINE (bill line charge) is the only valid option. For each interface line number associated with an interface ID, there should be only one row of transaction type LINE.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	Zero for LINE transactions.

Populating the INTFC_BI2 Table for Line Transactions

The INTFC_BI2 table has the same key structure as the INTFC_BI table; consider it an extension of the INTFC_BI table. Currently, it is used only for certain tax transactions, including prepaid taxes, ship-to address overrides (for tax vendor tax calculation purposes) and India transactions

For every row in INTFC_BI2, there must exist a row in the INTFC_BI table with the same key values. However, you do not need a row in the INTFC_BI2 table for every row in INTFC_BI.

The following table contains all columns in the INTFC_BI2 table and how they should be populated for LINE transactions:

Note. For Third-party tax transactions with a ship-to address override, you must at least populate the following fields: to insert a row into BI_LINE_TAX table: CITY, STATE, POSTAL, and COUNTRY.

Field Number	Field Name	LINE
1	INTFC_ID (interface ID)	Required. Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required. Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI (transaction type)	Required. Value must be LINE.
4	TRANS_TYPE_BI_SEQ	Required. Set it to 0 (zero).
5	PROCESS_INSTANCE	Leave blank.
6	ADDRESS1 (address line1)	Optional.
7	ADDRESS2 (address line2)	Optional.
8	ADDRESS3 (address line3)	Optional.
9	ADDRESS4 (address line4)	Optional.
10	IN_CITY_LIMIT	Optional. Used by third-party tax provider products to determine additional city taxes, where applicable.
11	GEO_CODE (geographic code)	Optional. Used by the third-party tax provider products to determine what taxing jurisdictions and tax rates to use.
12	CITY	Optional.
13	HOUSE_TYPE	Optional.
14	ADDR_FIELD1 (address field1)	Optional.
15	ADDR_FIELD2 (address field2)	Optional.
16	ADDR_FIELD3 (address field3)	Optional.
17	NUM1	Optional. Related to an address in countries, such as the Netherlands.
18	NUM2	Optional. Related to an address in countries, such as the Netherlands.
19	COUNTY	Optional.
20	STATE	Optional. Select from the values in the STATE_TBL.
21	POSTAL	Leave blank.
22	COUNTRY	Optional. Select from the values in the COUNTRY_TBL.
23	TAX_AMT	Required if sales and use taxes were prepaid. Report the amount of prepaid sales and use tax. Should equal the TAX_AMT field on the INTFC_BI table and the sum of the TAX_AMT fields of records on the INTFC_BI_TAX table correlating to the same line transaction.
24	TAX_PCT	Required if sales and use taxes were prepaid. Report the percentage tax rate of prepaid sales and use taxes.
25	MAX_TAX_FLG	Set to Y if prepaid sales and use taxes were calculated taking advantage of maximum tax rules.
26	TAX_JUR_IND	Required if VAT was prepaid. Set to the VAT tax journal to which the VAT payment should be recorded.
27	VAT_BASIS_AMT	Required if VAT was prepaid. Report the VAT basis used to calculate value-added taxes.
28	VAT_AMT	Required if VAT was prepaid. Report the prepaid VAT amount.
29	VAT_TRANS_AMT	Required if VAT was prepaid. Report the VAT transaction amount used to calculate value-added taxes.
30	TAX_CD_VAT_PCT	Required if VAT was prepaid. Report the VAT percentage used to calculate value-added taxes.
31	EXD_INVOICE_NO	Required for India transactions populated by PeopleSoft Order Management if excise tax is applicable.
32	EXD_INVOICE_LINE	Required for India transactions populated by PeopleSoft Order Management. Populate if excise tax is applicable.
33	EXD_APPL_FLG	Required for India transactions populated by PeopleSoft Order Management. Values are: Y if excise tax is applicable. N if excise tax is not applicable.
34	STX_APPL_FLG	Required for India transactions populated by PeopleSoft Order Management. Values are: Y if sales tax or VAT is applicable. N if sales tax or VAT is not applicable.
35	STX_TAX_AUTH_CD	Required for India transactions populated by PeopleSoft Order Management. Populate with a valid sales tax authority code.
36	EXD_TAX_RATE_CD	Required for India transactions populated by PeopleSoft Order Management. Populate with a valid excise tax rate code if excise tax is applicable.
37	STX_TAX_RATE_CD	Required for India transactions populated by PeopleSoft Order Management. Populate with a valid sales tax rate code if sales tax is applicable.
38	INV_ITEM_ID	Required for India transactions populated by PeopleSoft Order Management.
39	ORG_SETID	Required for India transactions populated by PeopleSoft Order Management.
40	ORG_CODE	Required for India transactions populated by PeopleSoft Order Management.
41	ORG_TAX_LOC_CD	Required for India transactions populated by PeopleSoft Order Management.
42	EXD_CONVERSION_RT	Required for India transactions populated by PeopleSoft Order Management.
43	QTY_BASE	Required for India transactions populated by PeopleSoft Order Management. Populate with QTY_SHIP_BASE field.
44	EXS_TAX_TXN_TYPE	Required for India transactions populated by PeopleSoft Order Management.
45	EXD_CUST_CATG_CD	Required for India transactions populated by PeopleSoft Order Management.
46	STX_CUST_CATG_CD	Required for India transactions populated by PeopleSoft Order Management.
47	EXD_ITM_CATG_CD	Required for India transactions populated by PeopleSoft Order Management.
48	STX_ITM_CATG_CD	Required for India transactions populated by PeopleSoft Order Management.
49	EXS_SERV_TAX_FLG	Required for India transactions populated by PeopleSoft Order Management.
50	EXD_ASSESS_VALUE	Required for India transactions populated by PeopleSoft Order Management. Populate when excise tax is applicable.
51	EXD_UOM	Required for India transactions populated by PeopleSoft Order Management. Populate when excise tax is applicable.
52	EXD_USE_AV_FLG	Required for India transactions populated by PeopleSoft Order Management.
53	BI_CURRENCY_CD	Leave blank.
54	BASE_CURRENCY	Leave blank.
55	EXS_CURRENCY_RPTG	Required for India transactions populated by PeopleSoft Order Management.
56	EXD_TAX_AMT	Required if taxes are calculated in PeopleSoft Order Management for India transactions.
57	EXD_TAX_AMT_BSE	Required if taxes are calculated in PeopleSoft Order Management for India transactions.
58	EXD_TAX_AMT_RPT	Required if taxes are calculated in PeopleSoft Order Management for India transactions.
59	STX_TAX_AMT	Required if taxes are calculated in PeopleSoft Order Management for India transactions.
60	STX_TAX_AMT_BSE	Required if taxes are calculated in PeopleSoft Order Management for India transactions.
61	STX_TAX_AMT_RPT	Required if taxes are calculated in PeopleSoft Order Management for India transactions.
62	STX_FORM_CD	Required for India transactions populated by PeopleSoft Order Management.
63	LOAD_STATUS_BI	Initialize to NEW or leave blank.
64	ERROR_STATUS_BI	Leave blank.
65	USETAX_AMT	Leave blank.
66	USETAX_BASIS_AMT	Leave blank.
67	USETAX_BASIS_AMT	Leave blank.
68	USETAX_BASIS_AMT_B	Leave blank.
69	TAX_AMT_BSE	Leave blank.
70	TAX_CD_VAT_RVC_PCT	Leave blank.
71	VAT_AMT_RVC	Leave blank.
72	ADD_DTTM	Required for accurate reporting purposes and for taking advantage of interface workflow function.
73	LAST_UPDATE_DTTM	Leave blank.

Populating the INTFC_BI_HDR Table

This section provides an overview of the INTFC_BI_HDR table and discusses how to populate it for LINE transactions.

Understanding the INTFC_BI_HDR Table

The Billing Interface Bill Header table (INTFC_BI_HDR) contains only LINE transactions. The following six attributes comprise the key to the INTFC_BI_HDR table:

INTFC_ID (interface ID)	Represents a group or batch of billing activity, that is, a collection of billing activity that may be produced by a billing source system. For example, a system may generate a group or batch each night, while another may produce a group or batch for a certain kind of billing activity.
INTFC_LINE_NUM (interface line number)	Represents a bill line charge. For each interface ID (group or batch of billing activity), there may be multiple interface line numbers, one for each bill line charge in the group.
TRANS_TYPE_BI (transaction type billing)	Characterizes the type of data being stored. LINE (bill line charge) is the only valid option. For each interface line number associated with an interface ID, there should be only one row of transaction type LINE.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	Zero for LINE transactions.
HDR_FIELDS_KEY (header fields key)	Represents subheader information, including VAT, credit card, header level AR distribution, and miscellaneous header information. This field also exists in the INTFC_BI table and is used as a foreign key to the INTFC_BI_HDR table. Source systems populate and maintain this key based on grouping of billing activity. PeopleSoft Billing maintains this field in the Billing Interface History record (INTFC_BI_CMP) as well as in the BI_HDR record. Bill header-related overrides for credit card, VAT, AR, and miscellaneous data records in the INTFC_BI_HDR table are tied to the main Billing Interface table (INTFC_BI) through this field.
HDR_TRANS_TYPE (header transaction type)	Options are: VAT: Bill header VAT data. CRC: Bill header credit card data. MSC: Bill header miscellaneous data. HAR: Bill header AR data.

Populating the INTFC_BI_HDR Table for LINE Transactions

The following table demonstrates how to populate the INTFC_BI_HDR table for LINE transactions:

Field Number	Field Name	LINE
1	INTFC_ID (interface ID)	Required. Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM (interface line number)	Required. Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI (transaction type)	Required. Value must be LINE.
4	TRANS_TYPE_BI_SEQ (transaction type sequence)	Set to 0 (zero).
5	HDR_FIELDS_KEY	Required.
6	HDR_TRANS_TYPE	Depending on the transaction type, enter VAT, CRC, MSC, or HAR.
7	PROCESS_INSTANCE	Leave blank.
8	LOAD_STATUS_BI	Leave blank.
9	ERROR_STATUS_BI	Leave blank.
10	BUSINESS_UNIT	Required.
11	INVOICE	Leave blank.
12	BUSINESS_UNIT_GL	Leave blank.
13	BUSINESS_UNIT_TO	Leave blank.
14	TARGET_INVOICE	Leave blank.
15	DST_ID_AR	Optional. Must be provided in the absence of ACCOUNT. [HAR]

Fields 16 through 31 describe ChartFields as they are initially delivered in the system. By using ChartField configuration, you can define the ChartFields differently. The behavior described here provides general reference for how ChartFields are handled in this context.

Configurable ChartFields can be fully configurable (identified below by F), partially configurable (identified below by P), or affiliate ChartFields (identified below by A).

Note. VAT-related fields in this table are provided so that feeder systems can pass VAT-related data into the Billing interface. Feeder systems such as PeopleSoft Order Management pass fully-defaulted VAT data. Some other feeder systems may pass less than fully defaulted VAT data. You must run the Billing VAT Defaults process (BIPVAT00) to assign missing default values and to validate the fully defaulted VAT data.

Field Number	Field Name	LINE
16	ACCOUNT (P)	Required unless appearing by default from DST_ID_AR. Appears by default from DST_ID_AR if DST_ID_AR is provided [HAR]
17	ALTACCT (P)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. It must get a value when Alt Accounting is ON. [HAR]
18	DEPTID (department) (P)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
19	OPERATING_UNIT (F)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
20	PRODUCT (F)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
21	FUND_CODE (F)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
22	CLASS_FLD (class field) (F)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
23	PROGRAM_CODE (F)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
24	BUDGET_REF (budget reference) (F)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
25	AFFILIATE (A)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
26	AFFILIATE_INTRA1 (A)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
27	AFFILIATE_INTRA2 (A)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
28	CHARTFIELD1 (F)	Leave blank. [HAR]
29	CHARTFIELD2 (F)	Leave blank. [HAR]
30	CHARTFIELD3 (F)	Leave blank. [HAR]
31	PROJECT_ID (P)	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
32	STATISTICS_CODE	Optional. Appears by default from DST_ID_AR if DST_ID_AR is provided. Must be valid if provided. [HAR]
33	OPEN_ITEM_KEY	Required when ChartFields reference an open item. Must correspond to a record on the OPEN_ITEM_GL table. [HAR]
34	JRNL_LN_REF	Optional. If provided, must correspond to a record on the JRNL_LINE table. [HAR]
35	BI_PAID_AT_SRC	Set to one of the following: (when HDR_TRANS_TYPE is MSC). 0 = Unpaid (default). 1 = Deposit applied. 2 = Partial payment. 9 = Full payment.
36	PAID_AMT (paid amount)	Required when paid reference provided for HDR_TRANS_TYPE is MSC. Report amount of payment or applied deposit. Note. PAID_AMT does not reduce AR distribution.
37	PAID_REFERENCE (paid reference)	Required when PAID_AMT is not zero. (when HDR_TRANS_TYPE is MSC).
38	VAT_CALC_GROSS_NET	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
39	VAT_DCLRTN_DT	Required if VAT declaration date source is M (manual) or D (delivery). This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
40	VAT_DCLRTN_DT_SRC	Optional. VAT declaration date source. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
41	VAT_DCLRTN_POINT (VAT declaration point)	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
42	VAT_DST_ACCT_TYPE	Optional. If provided, it must be valid. If not provided, the system populates with a default value during the invoice finalization process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
43	VAT_EXCPTN_CERTIF	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT), when VAT exception type is not blank or not N.
44	VAT_EXCPTN_TYPE (VAT exception type )	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
45	VAT_RECALC_FLG (VAT recalculate at payment flag)	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
46	VAT_ROUND_RULE (VAT rounding rule)	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
47	VAT_RGSTRN_BUYER	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
48	VAT_RGSTRN_SELLER	Optional. If provided, it must be valid. If not provided, the system populates with a default value obtained through the VAT Defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT).
49	PROVINCE	Leave blank.
50	CR_CARD_DIGITS	Required when HDR_TRANS_TYPE is CRC.
51	CR_CARD_EXPMO (credit card expiration month)	Required when HDR_TRANS_TYPE is CRC.
52	CR_CARD_EXPYR (credit card expiration year)	Required when HDR_TRANS_TYPE is CRC.
53	CR_CARD_FNAME (credit card first name)	Required when HDR_TRANS_TYPE is CRC.
54	CR_CARD_LNAME (credit card last name)	Required when HDR_TRANS_TYPE is CRC.
55	CR_CARD_NBR (credit card number)	Required when HDR_TRANS_TYPE is CRC.
56	CR_CARD_TYPE (credit card type)	Required when HDR_TRANS_TYPE is CRC.
57	NAME_EXACT	Optional. Populates only when HDR_TRANS_TYPE is CRC.
58	EXPIRATION_DT (expiration date)	Required when HDR_TRANS_TYPE is CRC.
59	ADDRESS1 (address line 1)	Required when HDR_TRANS_TYPE is CRC.
60	ADDRESS2 (address line 2)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
61	ADDRESS3 (address line 3)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
62	ADDRESS4 (address line 4)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
63	NUM1 (number 1)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
64	NUM2 (number 2)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
65	CITY	Optional. Populate only when HDR_TRANS_TYPE is CRC.
66	COUNTY	Optional. Populate only when HDR_TRANS_TYPE is CRC.
67	STATE	Optional. Populate only when HDR_TRANS_TYPE is CRC.
68	POSTAL	Required when HDR_TRANS_TYPE is CRC.
69	GEO_CODE (tax vendor geocode)	Leave blank.
70	COUNTRY	Optional. Populate only when HDR_TRANS_TYPE is CRC.
71	PHONE	Optional. Populate only when HDR_TRANS_TYPE is CRC.
72	EMAILID (email address)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
73	HOUSE_TYPE	Optional. Populate only when HDR_TRANS_TYPE is CRC.
74	ADDR_FIELD1 (address field 1)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
75	ADDR_FIELD2 (address field 2)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
76	ADDR_FIELD3 (address field 3)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
77	IN_CITY_LIMIT	Optional. Populate only when HDR_TRANS_TYPE is CRC.
78	CR_CARD_RQST_ID (credit card request ID)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
79	CR_CARD_AUTH_STAT (credit card authorization status)	Optional. Populate only when HDR_TRANS_TYPE is CRC.
80	CR_CARD_AUTH_CD (credit card authorization code)	Optional. Populates only when HDR_TRANS_TYPE is CRC. This field is populated by the credit card processing vendor.
81	CR_CARD_A_DTTM (credit card authorization code date and time)	Optional. Populates only when HDR_TRANS_TYPE is CRC. This field is the credit card authorization date and time in characters and is populated by the credit card processing vendor.
82	CR_CARD_AUTH_DTTM (credit card authorization code date and time)	Optional. Populates only when HDR_TRANS_TYPE is CRC. This field is populated by the credit card processing vendor.
83	CR_CARD_MSG1 (credit card message 1)	Optional. Populates only when HDR_TRANS_TYPE is CRC. This field is populated by the credit card processing vendor.
84	CR_CARD_MSG2 (credit card message 2)	Optional. Populates only when HDR_TRANS_TYPE is CRC. This field is populated by the credit card processing vendor.
85	CR_CARD_MSG3 (credit card message 3)	Optional. Populates only when HDR_TRANS_TYPE is CRC. This field is populated by the credit card processing vendor.
86	COUNTRY_LOC_BUYER	Optional. If provided it must be a valid country. If not provided, the system obtains a default value from the customer's bill-to location. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT), where the physical nature is S (services).
87	STATE_LOC_BUYER	Optional. If provided it must be a valid state associated with the buyer's location country. If not provided, the system obtains a default value from the customer's bill-to location. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT), when the physical nature is S (services) and the buyer's location country tracks VAT by state or province.
88	COUNTRY_LOC_SELLER	Optional. If provided, it must be a valid country. If not provided, the system obtains the default value from the billing business unit location. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services).
89	STATE_LOC_SELLER	Optional. If provided, it must be a valid state associated with the seller's location country. If not provided, the system obtains the default value from the billing business unit location. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services). Leave blank when the seller's location country does not track VAT by state or province.
90	VAT_SVC_SUPPLY_FLG	Optional. If provided it must be valid. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services).
91	VAT_SERVICE_TYPE	Optional. If provided it must be a valid VAT service type. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services).
92	COUNTRY_VAT_PERFRM	Optional. If provided it must be a valid country. If not provided, the system populates with a default value from the PeopleSoft Billing VAT drivers hierarchy. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services).
93	STATE_VAT_PERFRM	Optional. If provided it must be a valid state associated with the COUNTRY_VAT_PERFRM value. If not provided, the system populates with a default value from the PeopleSoft Billing VAT drivers hierarchy. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services). Leave blank when the COUNTRY_VAT_PERFRM value does not track VAT by state or province.
94	COUNTRY_VAT_SUPPLY	Optional. If provided it must be a valid country. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services).
95	STATE_VAT_SUPPLY	Leave blank.
96	VAT_HDR_IND	Leave blank.
97	STATE_VAT_DEFAULT	Optional. If provided it must be a valid state associated with the VAT reporting country. If not provided, the system populates with a default value obtained through the VAT defaulting process. This applies only to VAT transactions (when HDR_TRANS_TYPE is VAT) where the physical nature is S (services).
98	ADD_DTTM	Required for accurate reporting purposes and for taking advantage of interface workflow function.
99	LAST_UPDATE_DTTM	Leave blank.

Note. When importing bills with VAT data, to ensure VAT data integrity you must run the VAT Defaulting process after the Billing Interface process.

You do not need to populate a row in INTFC_BI_HDR for every row in INTFC_BI. You need only to populate one row in which INTFC_BI_HDR matches the key of the LINE with MIN(INTFC_ID) and MIN(INTFC_LINE_NUM) in the INTFC_BI table. For example, if the INTFC_BI table is populated for Interface ID 75, for an order as follows:

INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_BI_SEQ	ORDER_NO	HDR_FIELDS_KEY
1	LINE	0	WESUS001	WESUS001CRC
2	LINE	0	WESUS001	WESUS001CRC
3	LINE	0	WESUS001	WESUS001CRC
4	LINE	0	WESUS001	WESUS001CRC

The INTFC_BI_HDR table should appear as follows:

INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_BI_SEQ	HDR_FIELDS_KEY	HDR_TRANS_TYPE
1	LINE	0	WESUS001	CRC

Populating the INTFC_BI_EXSD Table

This section provides an overview of the Excise Tax Detail table and discusses how to populate it for LINE transactions.

Understanding the INTFC_BI_EXSD Table

The Excise Tax Detail table (INTFC_BI_EXSD) contains EXSD (India excise, sales tax, and VAT detail) transactions only. The following four attributes comprise the INTFC_BI_EXSD key:

Note. The Excise Tax Detail table is populated only by PeopleSoft Order Management. India tax functionality is supported only for PeopleSoft Order Management.

INTFC_ID (interface ID)	Represents a group or batch of billing activity. PeopleSoft uses the term group or batch to mean a collection of billing activity that may be produced by a billing source system. Some systems may generate a group or batch each night. Other systems may produce a group or batch for a certain kind of billing activity.
INTFC_LINE_NUM (interface line number)	Represents a bill line charge. For each interface ID (group or batch of billing activity), there may be multiple interface line numbers, one for each bill line charge in the group.
TRANS_TYPE_BI (transaction type billing)	Characterizes the type of data being stored. The only option is EXSD (bill line excise tax detail entry). For each interface line number associated with an interface ID, there should be only one row of transaction type LINE in the INTFC_BI table. There can be multiple rows with transaction type EXSD in the INTFC_BI_EXSD table.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	The transaction type sequence is part of the key, to provide uniqueness in the event that there are multiple EXSD for a bill line charge.

Populating the INTFC_BI_EXSD Table for LINE Transactions

For each bill line charge added as a bill line to the bill data structure, the Billing Interface table contains one row of data with a transaction type of LINE. The value of the TRANS_TYPE_BI column for the INTFC_BI_EXSD table must be EXSD. For each bill line charge row with a transaction type of LINE, the Billing interface can contain bill line excise tax detail entries (EXSD entries) in the INTFC_BI_EXSD table.

The following table demonstrates how to populate the INTFC_BI_EXSD table for LINE transactions:

Field Number	Field Name	EXSD
1	INTFC_ID	Required for India transactions populated by PeopleSoft Order. Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM	Required for India transactions populated by PeopleSoft Order Management. Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI	Required for India transactions populated by PeopleSoft Order Management. Value must be EXSD.
4	TRANS_TYPE_BI_SEQ	Required for India transactions populated by PeopleSoft Order Management. If more than one excise tax detail entry is populated for a particular EXSD transaction, the transaction type sequence must be used for uniqueness.
5	LOAD_STATUS_BI	Initialize to NEW or leave blank.
6	ERROR_STATUS_BI	Leave blank.

The following fields can contain values for excise, sales tax, and VAT. When the EXS_TAX_TYPE equals S (sales), fields prefixed with EXS_ must be populated with sales-tax-related data. When EXS_TAX_TYPE equals E (excise), fields prefixed with EXS_ must be populated with excise-tax-related data. EXS_ fields populate the BI_LINE_EXS_DTL table.

Field Number	Field Name	EXSD
7	EXS_TAX_TYPE	Required for India transactions populated by PeopleSoft Order Management. Values are: C: Custom Duty S: Sales Tax and VAT E: Excise Tax
8	EXS_TAX_RATE_SEQ	Required for India transactions populated by PeopleSoft Order Management.
9	EXS_TAX_RATE_CD	Required for India transactions populated by PeopleSoft Order Management. Populate with a valid tax rate code.
10	EXS_TAX_CMPNT_CD	Required for India transactions populated by PeopleSoft Order Management.
11	EXS_TAX_DEP_CD	Required for India transactions populated by PeopleSoft Order Management.
12	EXS_CALC_SCHEME	Required for India transactions populated by PeopleSoft Order Management.
13	EXS_TAX_RATE_PCT	Required for India transactions populated by PeopleSoft Order Management.
14	EXS_TXRTAMT_TRC	Required for India transactions populated by PeopleSoft Order Management.
15	EXS_CURRENCY_TRC	Required for India transactions populated by PeopleSoft Order Management.
16	BI_CURRENCY_CD	Leave blank.
17	BASE_CURRENCY	Leave blank.
18	EXS_TAXRT_AMT	Required for India transactions populated by PeopleSoft Order Management.
19	EXS_TAXRT_AMT_BSE	Required for India transactions populated by PeopleSoft Order Management.
20	EXS_TAXRT_AMT_RPT	Required for India transactions populated by PeopleSoft Order Management.
21	EXS_TAX_RATE_UOM	Required for India transactions populated by PeopleSoft Order Management.
22	EXS_CURRENCY_RPTG	Leave blank.
23	EXS_TAX_AMT	Required if PeopleSoft Order Management calculates taxes for India transactions.
24	EXS_TAX_AMT_BSE	Required if PeopleSoft Order Management calculates taxes for India transactions.
25	EXS_TAX_AMT_RPT	Required if PeopleSoft Order Management calculates taxes for India transactions.
26	EXS_BASIS_AMT	Required if PeopleSoft Order Management calculates taxes for India transactions.
27	EXS_BASIS_AMT_BSE	Required if PeopleSoft Order Management calculates taxes for India transactions.
28	EXS_BASIS_AMT_RPT	Required if PeopleSoft Order Management calculates taxes for India transactions.
29	PROCESS_INSTANCE	Leave blank.
30	ADD_DTTM	Required for accurate reporting purposes and for Billing interface workflow functionality.
31	LAST_UPDATE_DTTM	Leave blank.

Populating the INTFC_BI_TAX Table

This section provides an overview of the INTFC_BI_TAX table and discusses how to populate the INTFC_BI_TAX table for LINE transactions.

Understanding the INTFC_BI_TAX Table

The Tax Detail table (INTFC_BI_TAX) is used to report the details of sales and use taxes paid for fully-paid invoices. Report taxes by line, using separate transactions to reflect the amount levied by each tax authority. The following four attributes comprise the INTFC_BI_TAX key::

INTFC_ID (interface ID)	Represents a group or batch of billing activity. This PeopleSoft application uses the term group or batch to mean a collection of billing activity that may be produced by a billing source system. Some systems may generate a group or batch each night. Other systems may produce a group or batch for a certain kind of billing activity.
INTFC_LINE_NUM (interface line number)	With INTFC_ID, identifies the bill line charge on the INTFC_BI table to which this tax detail entry applies.
TRANS_TYPE_BI (transaction type billing)	Characterizes the type of data being stored. The only option is TAX. For each interface line number associated with an interface ID, only one row of transaction type LINE should appear in the INTFC_BI table. Multiple rows can have transaction type TAX in the INTFC_BI_TAX table.
TRANS_TYPE_BI_SEQ (transaction type billing sequence)	The transaction type sequence is part of the key. It provides uniqueness in the event that a bill line charge has multiple tax detail records.

Note. Billing ignores any INTFC_BI_TAX entries unless the invoice is fully-paid.

Billing does not validate whether taxes should be levied on fully-paid invoices.

Populating the INTFC_BI_TAX Table for LINE Transactions

For each bill line charge added as a bill line to the bill data structure, the Billing Interface table contains one row of data with a transaction type of LINE. The value of the TRANS_TYPE_BI column for the INTFC_BI_TAX table must be TAX. For each bill line charge row with a transaction type of LINE, the Billing Interface Tax table can contain multiple tax detail entries.

The following table shows how to populate the INTFC_BI_TAX table for LINE transactions:

Field Number	Field Name	TAX
1	INTFC_ID	Required. Used to group or batch a collection of Billing interface activity.
2	INTFC_LINE_NUM	Required. Each unique interface line number for an interface ID represents a separate bill line charge.
3	TRANS_TYPE_BI	Required. Value must be TAX.
4	TRANS_TYPE_BI_SEQ	Required. If more than one tax detail entry is populated for a particular transaction, the transaction type sequence must be used for uniqueness.
5	LOAD_STATUS_BI	Initialize to NEW or leave blank.
6	ERROR_STATUS_BI	Leave blank.
7	BUSINESS_UNIT	The Billing business unit.
8	INVOICE	Invoice number of the invoice to which the tax detail record applies.
9	LINE_SEQ_NUM	Line sequence number of the invoice line to which the tax detail record applies.
10	TAX_AUTHORITY_CD	Tax authority code.
11	SEQ_NBR_5	Leave blank.
12	TAX_JUR_NAME	Tax journal for logging the tax.
13	BI_CURRENCY_CD	Currency in which the taxes were paid.
14	BASE_CURRENCY	Leave blank.
15	TAX_AMT	Report the amount of sales and use tax paid for the applicable line and tax authority. The sum of the TAX_AMT fields of all records on the INTFC_BI_TAX table correlating to a line transaction must equal the TAX_AMT fields on the INTFC_BI and INTFC_BI2 tables for that line.
16	TAX_AMT_BSE	Leave blank.
17	TAX_PCT	Report the percentage tax rate of prepaid sales and use taxes.
18	TAX_EXEMPT_AMT	Report the portion of the line amount held exempt in the tax calculation.
19	NON_TAXABLE_AMT	Report the portion of the line amount held nontaxable in the tax calculation.
20	TAX_BASIS_AMT	Report the tax basis amount used in the tax calculation.
21	MAX_TAX_FLG	Set to Y if prepaid sales and use taxes were calculated taking advantage of maximum tax rules.
22	TARGET_INVOICE	Leave blank.
23	PROCESS_INSTANCE	Leave blank.
24	ADD_DTTM	Required for accurate reporting purposes and for Billing interface workflow functionality.
25	LAST_UPDATE_DTTM	Leave blank.

Using the Bill-By Identifier with the Billing Interface

This section provides an overview of the bill-by identifier and discusses how to:

Evaluate Billing interface activity.
Populate data for new bill headers.

PeopleSoft Billing uses the bill-by identifier to define how to group billing activity when it is added to a bill through the Billing interface. You can associate the bill-by identifier with the bill-to customer, bill source, bill type, and billing business unit.

Understanding the Bill-By Identifier

By adding one or more fields to the bill-by definition, you instruct the Billing interface to use those fields to determine which uninvoiced bills will receive interface activity and when a new bill should be started for billing activity.

When you create new bill-by IDs:

Use the fewest number of bill-by fields that meet your requirements.
From external interfaces, you may want to populate default fields if you know their values.

This action reduces the work required by the Billing Interface process and can significantly improve batch performance.

If you have a bill-by identifier defined with fields ORDER_NO and SHIP_TO_ADDR_NUM, for example, the Billing Interface process generates a new bill for each distinct combination of order number and ship-to location for each customer. For each line of activity in the interface staging area, the Billing Interface process determines whether an uninvoiced bill exists for that business unit, bill-to customer, bill type, billing currency, order number, and ship-to location. If a bill exists, the process adds the interface line of activity to that bill as another bill line provided that the bill status of the existing bill allows new lines to be added. If no bill exists, the process generates a new bill header and adds the interface line activity to the new bill.

For example, five lines of billable activity are populated in the interface staging area for customer 5001. Before you ran the Billing Interface process for the activity in the following table, one uninvoiced bill existed for business unit US001, customer 5001, order 550122, and ship-to location 1. Order number 5554095 had no existing bills. The Billing Interface process determines that a bill exists for order number 5550122, ship-to location 1, and adds lines 1 and 2 to that bill. It then generates two new bill headers: one for order 5554095, ship-to location 1; and one for order 5554095, ship-to location 2. The process adds lines 3 and 5 to the first of these two new bills. It adds line 4 to the second of these two new bill headers, as shown in this table:

Line	Business Unit	Customer	Order Number	Ship To Location	Amount
1	US001	5001	5550122	1	500 USD
2	US001	5001	5550122	1	2000 USD
3	US001	5001	5554095	1	45 USD
4	US001	5001	5554095	2	4700 USD
5	US001	5001	5554095	1	16000 USD

Note. Do not use this bill-by concept for full bill adjustments and transactions referencing a target invoice.

Evaluating Interface Activity

Before the Billing Interface process evaluates interface activity to determine whether new bill headers are required, it evaluates the customer, bill source, bill type, and business unit characteristics to send the appropriate bill-by to the interface staging area by default. The Billing Interface process then uses the bill-by identifiers to determine which new bill headers need to be generated.

If, for example, you have a different bill-by identifier defined for each bill type, the Billing Interface process selects by default the bill-by identifier for each bill type. It groups the interface data for each bill type by using the bill-by criteria of that type.

You must define some fields together as part of the bill-by in order for the functionality of the fields to process correctly. For example, to use the user-defined currency rate functionality, you must define three fields together in the bill-by: CUR_RT_SOURCE, RATE_MULT, and RATE_DIV. If you define only one or two of these fields in the bill-by criteria, the system creates a bill with erroneous rate information.

Other fields that work as a group are listed in the following table:

Functionality	Fields to Add to Bill-By
User-Defined Currency Rate	CUR_RT_SOURCE, RATE_MULT, RATE_DIV
Direct Invoicing	RANGE_SELECTION_ID, DIRECT_INVOICING
Override Defaults for Consolidated Billing	(CONSOL_KEY) and (CONSOL_SETID, CONSOL_CUST_ID)
OM_BILL to Billing interface	ADDRESS_SEQ_NUM, PAYMENT_METHOD, PYMNT_TERMS_CD

You should include SHIP_FROM_BU as a bill-by field for transactions from Order Management or Inventory that will be subject to VAT.

Populating Data for New Bill Headers

When the Billing Interface process generates a new bill header, the system uses default values for much of the data, if it is not provided. The defaulting mechanism operates by using the same hierarchy as online bill entry defaulting. For example, payment terms codes appear by default onto new bill headers from customer, bill source, bill type, and business unit, in that order. To override bill header defaults applied by the Billing Interface process, you must provide data (in the interface table) in the field that you want to override, and include that field in the bill-by criteria. For example, to override the Billing interface payment terms defaulting, populate the payment terms field on the interface table, and ensure that the bill-by identifier includes PYMNT_TERMS_CD.

Data in the interface staging area is grouped for billing according to the bill-by fields defined for the bill-by identifier. The system always populates this data on the bill header. In the preceding example, the order number and ship-to location appear on both bill header and bill line tables. The order number and ship-to location are the same for all lines on the bill. If the preceding activity had five different shipment types, the shipment types would be populated on the bill line table but not on the bill header. However, if you defined the bill-by identifier with the fields ORDER_NUM and SHIP_TYPE_ID, the system populates the order number and shipment type on both the bill header and bill line tables, and the ship-to location would be a variable at the bill line level.

These fields are implied bill-by fields and need not be specified:

BUSINESS_UNIT
BILL_TO_CUST_ID
BILL_TYPE_ID
BILL_SOURCE_ID (if invoice numbering is set to bill source)
BI_CURRENCY_CD
HDR_FIELDS_KEY
BUSINESS_UNIT_TO
COUNTRY_SHIP_FROM (if the transaction is subject to VAT)
COUNTRY_SHIP_TO (if the transaction is subject to VAT)
COUNTRY_VAT_BILLFR (if the transaction is subject to VAT)
COUNTRY_VAT_BILLTO (if the transaction is subject to VAT)
VAT_TREATMET_GRP (if the transaction is subject to VAT)

For the system to consider a field a bill-by field, that field must exist both in the bill header (BI_HDR) record and in the Billing Interface table (INTFC_BI). Some exceptions exist, such as PROCESS_INSTANCE, AR_LVL, and GL_LVL fields. The fields listed in the following two tables exist in both the Bill Header table and the Billing Interface table, but they do not exist in the Bill Line table. Data in the first table does not appear on the bill header unless it is defined as a bill-by field. Data in the second table has default values provided by the Billing Interface process from various setup tables (such as Customer, Bill Source, Bill Type, Billing Business Unit). If you want to override the default, you must provide an override value and include the field on the list of bill-by fields on the bill-by identifier definition.

The fields listed between the two tables are referred as commonly shared fields. A commonly shared field exists in all three tables: INTFC_BI, BI_HDR, and BI_LINE.

Header Fields: No Defaulting Applied

Field	Explanation
ACCOUNTING_DT	Optional
LC_ID	Optional
LOC_DOC_ID	Optional
FROM_DT	Optional
INVOICE_DT	Optional
RANGE_SELECTION_ID	Optional
REIMB_AGREEMENT	Optional
TO_DT	Optional
MAST_CONTR_ID	Optional
BUSINESS_UNIT_AM	Optional
DOC_TYPE	Optional

If you populated FROM_DT and TO_DT in the interface staging area, for example, but did not define these fields as bill-by fields, the data does not appear in the bill header.

To populate the bill header with commonly shared fields, define them as bill-by fields. Commonly shared fields are:

ACTIVITY_ID
ACTIVITY_TYPE
ANALYSIS_TYPE
BILL_OF_LADING
BUSINESS_UNIT_CA
BUSINESS_UNIT_OM
BUSINESS_UNIT_PC
BUSINESS_UNIT_RF
CONTRACT_DT
CONTRACT_NUM
CONTRACT_TYPE
COUNTRY_SHIP_FROM

Note. The COUNTRY_SHIP_FROM field is used as an implicit bill-by when the transaction is subject to VAT.
COUNTRY_SHIP_TO

Note. The COUNTRY_SHIP_TO field is used as an implicit bill-by when the transaction is subject to VAT.
EMPLID
END_DT
ENTRY_REASON
ENTRY_TYPE
FREIGHT_TERMS
ORDER_DATE
ORDER_NO
PACKSLIP_NO
PHYSICAL_NATURE
PO_REF
PPRC_PROMO_CD
PROJECT_ID
RESOURCE_CATEGORY
RESOURCE_SUB_CAT
RESOURCE_TYPE
RMA_ID
SERVICE_ADDR_NUM
SERVICE_CUST_ID
SHIP_FROM_BU
SHIP_ID
SHIP_TO_ADDR_NUM
SHIP_TO_CUST_ID
SHIP_TYPE_ID
SO_ID
SOLD_TO_ADDR_NUM
SOLD_TO_CUST_ID
SOURCE_REF_KEY
SOURCE_REF_NO
SOURCE_REF_TYPE
SSN
START_DT
STATE_SHIP_FROM
STATE_SHIP_TO

Header Fields: Defaulting Applied

Field	Explanation
ACCEPTGIRO_IND	Provided by default from the Billing business unit setup table.
ACCRUE_UNBILLED	Optional. Provided by default if left blank.
ADDRESS_SEQ_NUM	Optional. Provided by default if left blank.
AR_DST_OPTL	Provided by default from billing setup tables.
AR_LVL	Provided by default from billing setup tables.
BI_BU_TAX_IND	Always provided by default based on Business Unit Tax setup.
BANK_ACCT_KEY	Optional. Provided by default if left blank.
BILL_BY_ID	Optional. Provided by default if left blank.
BANK_CD	Optional. Provided by default if left blank.
BILL_CYCLE_ID	Optional. Provided by default if left blank.
BILL_INQUIRY_PHONE	Optional. Provided by default if left blank.
BILL_TO_COPIES	Optional. Provided by default if left blank.
BILLING_AUTHORITY	Optional. Provided by default if left blank.
BILLING_FREQUENCY	Optional. Provided by default if left blank.
BILLING_SPECIALIST	Optional. Provided by default if left blank.
BUSINESS_UNIT_GL	Provided by default from a billing business unit.
CF_ACTION_FLG	Provided by defaults from GL business unit and Ledger setup tables.
CNTCT_SEQ_NUM	Optional. Provided by default if left blank.
COLLECTOR	Optional. Provided by default if left blank.
CONSOL_CUST_ID	Optional. Provided by default if left blank.
CONSOL_KEY	Optional. Provided by default if left blank.
COUNTRY_SHIP_FROM	Optional. Provided by default if left blank.
COUNTRY_SHIP_TO	Optional. Provided by default if left blank.
CR_ANALYST	Optional. Provided by default if left blank.
CR_CARD_FLG	Defaults to Y (yes), if customer's payment method is Credit Card. Otherwise it is N (no).
CUR_RT_SOURCE	Optional. Provided by default if left blank.
CUR_RT_TYPE	Optional. Provided by default if left blank.
DFR_ACCTG_DT_CD	Provided by default from billing setup tables.
DFR_MID_PERIOD_DAY	Provided by default from billing setup tables.
DFR_REV_PRORATION	Provided by default from billing setup tables.
DIRECT_INVOICING	Optional. N is the default value, if left blank.
DST_ID_DFR	Optional. Provided by default if left blank.
ENABLE_DFR_REV_FLG	Provided by default from billing setup tables.
ENTRY_EVENT	Optional. Provided by default if left blank.
GL_LVL	Provided by default from billing setup tables.
INVOICE_FORM_ID	Optional. Provided by default if left blank.
NAME1	Optional. Provided by default from CNTCT_SEQ_NUM.
PAYMENT_METHOD	Optional. Provided by default if left blank.
PYMNT_TERMS_CD	Optional. Provided by default if left blank.
RATE_DIV	Optional. Provided by default if left blank.
RATE_MULT	Optional. Provided by default if left blank.
SALES_PERSON	Optional. Provided by default if left blank.
SUBCUST_QUAL1	Optional. Provided by default from CUSTOMER, if left blank.
SUBCUST_QUAL2	Optional. Provided by default from CUSTOMER, if left blank.
SUMMARIZE_IVC_FLG	Default is N (no).
VAT_ENTITY	Provided by default from Billing and GL business unit setup.

Note. Only include those fields listed in the second table as part of the bill-by criteria when you supply override values. Having these fields as part of the bill-by identifier definition and not supplying a value could cause transactions to be left in a RDY (ready) load status.

Populating Identifiers

This section discusses:

Valid IDENTIFIER and IDENTIFIER_TBL field combinations.
Valid codes feeder systems should use when importing data into the Billing interface.

Valid IDENTIFIER and IDENTIFIER_TBL Field Combinations

This table lists the value combinations for populating the IDENTIFIER and IDENTIFIER_TBL fields in the Billing interface:

If the Identifier Field Contains:	Populate IDENTIFIER_TBL with:
A charge code from the BI_CHARGE table	ID (charge code)
A discount code from the BI_DISC_SUR table	D (discount)
A surcharge code from the BI_DISC_SUR table, including installment surcharges	S (surcharge)
A product code from the PROD_ITEM table	PRD (product). In this case, the PRODUCT_ID field should be populated with the same value as IDENTIFIER.
A customer's product code	PDA (product alias) In this case, PRODUCT_ID field should be populated with the system product code.
An item ID from the MASTER_ITEM_TBL table	ITM (item master)
A promotion code from the PPRC_PROMO_TBL table	PRM (promotion)
An asset ID from the ASSET table	A (asset)
A Labor Type code from the RF_COST_CAT table	LAB (labor)
A Service code from the RF_SERVICE table	SVC (service)
Any free form code not listed in this table	G (generic)
Any other non-blank value passed by PeopleSoft Contracts or Project Costing	CON (contract) In this case, the PRODUCT_ID field should be populated with the system product code; PRODUCT_ID can be different from the Identifier field.
<blank>	<blank>

Note. No edit check exists in the Billing interface logic to prevent invalid values in the IDENTIFIER_TBL field, nor to ensure that the IDENTIFIER and IDENTIFIER_TBL field combinations are valid.

IDENTIFIER and IDENTIFIER_TBL Field Requirements

This table demonstrates how systems that import data into PeopleSoft Billing through the Billing interface must populate the IDENTIFIER and IDENTIFIER_TBL fields:

Feeder System	Interface Process	IDENTIFIER Value	PRODUCT_ID Value	IDENTIFIER_TBL Value
PeopleSoft Order Management	OM_BILL	A product code from the PROD_ITEM table	A product code from the PROD_ITEM table	PRD (all bills)
PeopleSoft Order Management	OM_BILL	A customer's product code (product alias to system product code)	A product code from the PROD_ITEM table	PDA (all bills)
PeopleSoft Promotions Management	OM_BILL	A product code from the PROD_ITEM table	A product code from the PROD_ITEM table	PRD (all bills)
PeopleSoft Promotions Management	OM_BILL	A customer's product code (product alias to system product code)	A product code from the PROD_ITEM table	PDA (all bills)
PeopleSoft Promotions Management	TD_PAYMENTS	A PPRC_PROMO_CD from the PPRC_PROMO_TBL table		PRM (all bills)
PeopleSoft Contracts	CA_BI_INTFC	Any non-blank value	A product code from the PROD_ITEM table, if available	CON (all bills.)
PeopleSoft Project Costing	CA_BI_INTFC	Any non-blank value	A product code from the PROD_ITEM table, if available	CON (all bills.)
PeopleSoft CRM (using Contracts)	CA_BI_INTFC	COST_CAT_CD from the RF_COST_CAT table		LAB
PeopleSoft CRM (using Contracts)	CA_BI_INTFC	SERVICE_ID from the RF_SERVICE table		SVC
PeopleSoft Inventory	INBILL	INV_ITEM_ID from the MASTER_ITEM_TBL table		ITM
PeopleSoft Asset Management	AM_BI_INTFC	ASSET_ID from the AMBI_INTFC_BILL table		A

Note. If the IDENTIFIER field is populated and the IDENTIFIER_TBL field is blank, the Billing Interface process populates the IDENTIFIER_TBL field with G. If the IDENTIFIER field is blank and the IDENTIFIER_TBL field is populated, the Billing Interface process leaves the IDENTIFIER_TBL blank.

Generating Consolidated Billing Through the Billing Interface

The Billing interface supports automatic generation of consolidated bill headers. To generate a consolidated bill, each bill must be attached to a consolidated bill. Consolidated bill headers may have standard bills related to them. They do not have bill lines related to them.

To generate consolidated bill headers by using the Billing interface, you must populate either the CONSOL_KEY column or the CONSOL_CUST_ID and CONSOL_SETID columns for LINE transaction types. Alternatively, populate all three fields through defaulting or by passing them to the INTFC_BI table. All three of these fields appear by default from the customer.

To consolidate bills across bill-to customers, the source system must provide a value for CONSOL_SETID and CONSOL_CUST_ID, or these values must be obtained through defaulting. If the interface cannot find a value for these two fields, but it does find a value for CONSOL_KEY, it assumes that the consolidation customer is the bill-to customer.

The interface process uses the consolidation fields to determine how billing data should be consolidated. For example, you populate the staging area with two kinds of activity: contract billing activity and miscellaneous billing activity. To generate bills by contract and consolidate all contract bills for the customer, provide a standard value in the consolidation key (such as CONSOL/CONTRACTS). When the interface process generates a new bill header that has a value in the consolidation key, it establishes whether a consolidated bill header exists for the same billing currency, with the same consolidation key. If so, the process attaches a new bill to the consolidated header. Otherwise, the process generates a new consolidated bill header and attaches the new bill header to this. Do not populate the consolidation fields (CONSOL_KEY, CONSOL_SETID, and CONSOL_CUST_ID) with a value if the miscellaneous activity should not be consolidated. If the miscellaneous activity should be consolidated, but not with the contract activity, populate the consolidation key with a different value (such as CONSOL/MISC).

To override the defaults for the consolidation fields, you must make the fields part of the bill-by.

Note. Default information for consolidated bills is maintained at the customer level. The Load AR process (BILDAR01) does not create open items for consolidated bills at the consolidated bill header level. It creates open items for consolidated bills at the attached bill level or attached bill line level.

The Billing Interface process does not support consolidation of adjustment transactions or consolidation of temporary bills.

If any bill attached to a consolidated header contains a line with a summarization template, all bills attached to that header must also contain at least one line with a summarization template.

(NLD) When consolidating acceptgiro invoices, all bills attached to a header must have the same Billing business unit and customer ID.

Generating Paperless Invoices Through the Billing Interface

Three types of paperless invoice may be generated through the Billing interface: Email Notification for bills presented through the eBill Payment application, EDI bills and Email Invoice as Attachment. To determine which type of invoice to generate, the Billing Interface process examines the invoice communication preference setting of the customer's billing contact and provides the bill-to media field by default for the invoice as follows:

Preferred Communication	Bill-To Media Default
C (Call)	Print
Email Invoice as Attachment	Email Invoice as Attachment
F (Fax)	Print
I (XML only)	EDI
M (Standard mail)	Print
Email Notification	Email Notification
R (XML & Print)	EDI

Important! If eBill Payment is not installed, the bill-to media will be provided by default to Print instead of Email.

The bill-to media can be changed using the Invoice Media field in online bill entry. However, the automatic bill-to media defaulting of the Billing interface process cannot be overridden.

See Also

Running the Email Notification Process

Processing EDI Transactions in PeopleSoft Billing

Processing Adjustments Through the Billing Interface

This section provides overviews of adjustment processing through the Billing interface and restrictions on editing bills from other sources, and discusses how to:

Reverse an original bill.
Credit a bill and rebill.
Credit a line.
Credit a line and rebill.
Create a line net adjustment.

The Billing Interface process supports the processing of adjustments of an entire bill and adjustments of selected bill lines.

Understanding Adjustment Processing Through the Billing Interface

Using the adjustment processing through the Billing interface provides you with automated bill reversal, as well as adjustment history tracking.

If you are sending line adjustments through the Billing interface, you may want the interface to create a new bill for the lines, rather than appending the adjustment lines to an existing bill. To create a new bill, set the CREATE_NEW_BILL field to Y for these transactions. The Billing Interface process groups lines from the current interface activity with the same bill-by criteria and puts them into a newly created bill. The process creates a new bill for these transactions, regardless of whether a bill with the same bill-by criteria already exists. You do not need to include the CREATE_NEW_BILL field with the bill-by criteria.

To mark a transaction as an adjustment, specify the invoice to be adjusted in the INVOICE_TO_ADJ field. Also, specify an adjustment transaction type in the ADJ_TRANS_TYPE field. This table lists possible values for this field:

Value	Description
CRALL	Credit entire bill
RBALL	Bill rebill
CRLIN	Line credit
RBLIN	Line rebill.
NTLIN	Line net adjustment

Guidelines for Creating Adjustments

When creating adjustments through the Billing interface, consider the following rules:

Copy existing notes as is.

Pass new notes with the LINE or AHDR transaction to append them to existing notes.
Do not add new lines to full bill credits.
Submit delta lines at the time that the rebill is first initiated. You cannot process lines for a full bill rebill and later process more delta lines for the same rebill.
In general, the system does not provide default values for reversal bills.

Credits are exact reversals of the original, with a few exceptions: the interface populates some fields with a value passed to the staging table, rather than taking the value from the credited bill. Those fields are: ACCOUNTING_DT, DIRECT_INVOICING, DOC_TYPE, ENTRY_REASON, ENTRY_TYPE, INVOICE_DT, and RANGE_SELECTION_ID.
For rebills, the system applies default values to fields left blank, with one exception: when processing lines on bill rebills, the system provides current default values for delta lines (ADD or RPL) and copies unchanged lines from the original.

The values provided for a rebill transaction or its delta lines must be valid values. Fields that do not exist in the Billing Interface table but exist in the bill header are copied from the original bill.
The Billing interface does not support courtesy copy processing, even for adjustments.

For example, if the original bill had courtesy copy information, the system does not copy that data into the adjustment bill.
For line-level adjustments, the Billing Interface process does not provide default values for any header-level information from the adjusted bill.
The Billing interface does not support Transaction type AHDR transactions or adjustment transaction type CRLIN, RBLIN transactions for India tax processing. It supports only NTLIN adjustments from PeopleSoft Order Management-RMA Adjustments for India functionality.

Understanding Restrictions on Editing Bills from Other Sources

Several restrictions apply to changing billing information transferred through the Billing interface:

Contracts and Project Costing
- Do not perform any adjustments, credits, or rebills on prepaid transactions (line type UTL).
- Do not change the Billing currency.
- Do not change the unit of measure.
- When the system source is CBI, or PBI, most of the fields on the Line - Proj Info page are disabled.
- Do not add bill lines created through online entry or through a different external system to bills from Contracts or Project Costing.
- Do not create new Contracts or Project Costing bills by filling in contract information through online bill entry or an external system.
Government Contracts
- Government contracts bills are subject to the same restrictions as other contracts bills.
- Do not adjust any progress payment or progress payment liquidation lines.
- Do not change the amounts of withholding write-off lines, either directly or by changing other values, such as quantity or unit price.
Order Management
- Do not create fully-paid invoices in online bill entry.
- Do not add or remove lines from fully-paid invoices.
- You can change only the accounting distribution of bill lines for fully-paid invoices.
- You cannot cancel fully-paid, partially-paid, and deposit-applied invoices.
- Do not enter deposit, deposit applied, deposit refund, and deposit refund fee lines in online bill entry.
- Do not change the amount of any deposit, deposit applied, deposit refund, and deposit refund fee lines in online bill entry if the lines have a deposit ID.
- Do not delete deposit, deposit applied, deposit refund, and deposit refund fee lines in online bill entry if the lines have a deposit ID.
- Do not apply discounts and surcharges to deposit, deposit applied, deposit refund, and deposit refund fee lines.
- Do not enter more than one accounting distribution for deposit, deposit applied, deposit refund, and deposit refund fee lines.
- Do not enter any deferred revenue distribution for deposit, deposit applied, and deposit refund lines.
- Payment with corporate voucher lines (PYCV) can only be passed to Billing in fully-paid invoices. If the fully-paid invoice with PYCV is copied or adjusted, then a PYCV line will exist in the new invoice. You can then modify or delete this line, as necessary, in online bill entry.
- The system will not perform VAT defaulting and calculations for fully-paid invoices, except for deposit refund fees or deposit, deposit applied, and deposit refund lines when the system is set to charge VAT on advance payments.

Reversing an Original Bill

Transactions that reference a credit entire bill (CRALL) must use the AHDR transaction type (TRANS_TYPE_BI AHDR). This type of adjustment is an exact reversal of the original bill.

To credit an entire bill, pass only one line (the AHDR transaction) along with the invoice number that is to be adjusted. The Billing Interface process automatically creates a new bill that credits all lines and reverses any accounting, tax, and discount or surcharge entries. You may also pass any new header notes to be appended to any existing header notes.

The following example shows how to populate the staging area for a credit entire bill adjustment:

INTFC_ID	INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_SEQ_NUM	ADJ_TRANS_TYPE	INVOICE_TO_ADJ
10015	1	AHDR	1	CRALL	00009101112

Crediting a Bill and Rebilling

For a bill rebill, you must pass at least two AHDR (adjustment header) lines to the interface: one for the credit and one for the rebill. Use the ADJ_TRANS_TYPE CRALL for the credit, and RBALL for the rebill. You must pass both lines under the same INTFC_ID, but with different interface line numbers (INTFC_LINE_NUM). Both lines must reference the invoice to be adjusted.

In addition to the two AHDR lines, you must pass any delta lines for the rebill under the same INTFC_ID. Delta lines are the lines that have changed from the original; they have been added, replaced, or deleted. Delta lines must reference a TRANS_TYPE_BI of LINE and ADJ_TRANS_TYPE of RBALL. They must also specify the line sequence number of the line to be adjusted in the LINE_SEQ_TO_ADJ field. Use the ADJ_DELTA_ACTION field to specify what action to take on the lines. This is the only type of adjustment that can use the ADJ_DELTA_ACTION field. When building the rebill, the valid values for ADJ_DELTA_ACTION are:

ADD	Add this bill line.
RPL (replace)	Replace the specified line with this line.
DEL (delete)	Do not include the specified line.

Note. AE and DS entries from the original bill are not carried forward on an RPL action. You must pass any associated AE, DS, and DDS lines if the line has been replaced or added. Notes are copied over and new NOTE lines may be sent.

If the only change to the rebill is at the header level, you are required to send only two AHDR lines. For example, if the only change is to the payment terms (where all lines are the same) for the rebill, you must pass an AHDR line that contains the correct payment terms.

The AHDR line for the rebill must contain all values that are to appear on the rebill header. The system uses current defaults for fields that are left blank on this line. If you pass as a blank field that did not appear by default, it appears as a blank on the rebill header. For example, there is no defaulting logic for contract number. If the original bill header referenced contract number ABC, you must supply this value on the AHDR record to display it on the rebill. If you do not supply it, the field is blank on the rebill header.

The following example demonstrates how to populate the staging area for a credit and rebill of invoice 00009101112:

INTFC_ID	INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_SEQ_NUM	ADJ_TRANS_TYPE
10015	1	AHDR	1	CRALL
10015	2	AHDR	1	RBALL
10015	3	LINE	1	RBALL
10015	4	LINE	1	RBALL
10015	5	LINE	1	RBALL

INTFC_ID	INTFC_LINE_NUM	INVOICE_TO_ADJ	LINE_SEQ_TO_ADJ	ADJ_DELTA_ACTION
10015	1	00009101112
10015	2	00009101112
10015	3	00009101112	2	RPL
10015	4	00009101112	0	ADD
10015	5	00009101112	1	DEL

Note. The bill-by concept is not used to group the delta lines onto the rebill header. The grouping is based strictly on the BUSINESS_UNIT and INVOICE_TO_ADJ fields.

Crediting a Line

Transactions that reference a credit line adjustment (CRLIN) must use the LINE transaction type (TRANS_TYPE_BI = LINE). This type of adjustment is an exact reversal of the original bill line.

To credit a line, pass only one LINE transaction with the invoice number and sequence number of the line to be adjusted. The Billing Interface process automatically credits the line and reverses any accounting, tax, and discount or surcharge entries for that line. You may also pass any new NOTE lines that are to be appended to any existing notes for this line.

The following example demonstrates how to populate the staging area for a line credit adjustment:

INTFC_ID	INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_BI_SEQ	ADJ_TRANS_TYPE	INVOICE_TO_ADJ	LINE_SEQ_TO_ADJ
10015	1	LINE	1	CRLIN	00009101112	2

Crediting a Line and Rebilling

Transactions that reference a line rebill adjustment (RBLIN) must use the LINE transaction type (TRANS_TYPE_BI = LINE).

For a line rebill, you must pass at least two LINE transactions to the Billing interface: one for the credit and one for the rebill. Use the ADJ_TRANS_TYPE CRLIN for the credit, and RBLIN for the rebill. You must pass both lines under the same INTFC_ID. Both lines must reference the invoice number and line sequence number to be adjusted. You must pass with the LINE transaction for the line rebill adjustment any accounting entries, discount or surcharge entries, note lines and any other line information associated with the line rebill, similar to the way non-adjustment LINE transactions are passed to the Billing interface.

The following example demonstrates how to populate the staging area for a line rebill adjustment:

INTFC_ID	INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_BI_SEQ	ADJ_TRANS_TYPE	INVOICE_TO_ADJ	LINE_SEQ_TO_ADJ
10015	1	LINE	1	CRLIN	00009101112	2
10015	2	LINE	1	RBLIN	00009101112	2

Creating a Line Net Adjustment

Transactions that reference a line net adjustment (NTLIN) must use the LINE transaction type (TRANS_TYPE_BI_=LINE).

To create a net adjustment to a line, you can pass a LINE transaction with or without the invoice number and sequence number of the line to be adjusted, depending on the history of the invoice. Pass with the LINE transaction any accounting entries, discount or surcharge entries, or note lines associated with the net adjustment line. It is important to note that the billing interface process does not copy any values from the history invoice for NTLIN adjustments as it does for CRLIN adjustments.

The following example demonstrates how to populate the staging area for a line net adjustment:

INTFC_ID	INTFC_LINE_NUM	TRANS_TYPE_BI	TRANS_TYPE_BI_SEQ	ADJ_TRANS_TYPE	INVOICE_TO_ADJ	LINE_SEQ_TO_ADJ
10015	1	LINE	1	NTLIN	00009191112	2

Using Target-Invoice Processing with the Billing Interface

When the Billing Interface process creates new bill headers, it assigns the next available invoice number to each new bill according to the invoice number ID for the bill. To override the automated invoice numbering, use the Billing interface target-invoice functionality.

If data from a source system has an assigned invoice number that you want to retain in PeopleSoft Billing, populate the TARGET_INVOICE field with the preassigned invoice number to pass that number to the Billing interface. You do not need to specify TARGET_INVOICE as a bill-by field in order to take advantage of this functionality. You do not need to modify the Installation Options − Billing - General Options page to mark the autonumbering parameter as user defined.

Ensure that the source system numbering scheme is different from PeopleSoft Billing numbering scheme. Alternately, the source system can populate the BI_IVC_NUM_PRE table to reserve the numbers. The system initiates the Duplicate Invoice Check function during online bill entry to check the BI_IVC_NUM_PRE table for system-reserved invoice numbers.

If the invoice specified in the TARGET_INVOICE field already exists for the same business unit, the Billing Interface process adds the lines that reference this target invoice to the existing bill. Otherwise, the system creates a new target invoice.

When you specify a target invoice, the system uses only the bill-by functionality to assign bill status. The Billing Interface process groups lines that have the same business unit and target invoice onto the same bill. These lines must reference the same bill-to customer and billing transaction currency. If there are multiple transaction lines that reference the same target invoice, the Billing Interface process uses the fields from the line with the minimum INTFC_ID and INTFC_LINE_NUM to populate the header fields.

When using target-invoice functionality, consider the following:

An existing target invoice cannot have a bill status of INV, CAN, FNL, TMP, or TMR.
An existing target invoice cannot have an INVOICE_TYPE of ACR.

These bills cannot be modified.
If the interface transaction is for a full bill credit or rebill (AHDR), the target invoice specified cannot already exist.
If one of the target invoice lines is in error, all other transactions associated with that target invoice will error out.
For consolidations, you may specify a target invoice for the bills to be attached, but not for the consolidated bill header.
Only Contracts and Project Costing bills should be used as a target invoice for Contracts and Project Costing transactions. Other bills may not contain all the information, such as contract number, required to complete these transactions.

Note. When you specify a target invoice, use only the bill-by ID to assign bill status.

See Also

Defining Billing Installation Options

Creating Temporary Bills Through the Billing Interface

You may want to print a pro forma invoice from the source system before the data is actually sent to PeopleSoft Billing, to proof the invoice, for example, or have it approved before creating an actual bill from the transactions. In PeopleSoft Billing, this is a temporary bill.

You can create temporary bills only through the Billing Interface process, which creates these bills with a bill status of TMR. Once created, a temporary bill cannot be modified. A temporary bill is viewable only from the bill inquiry pages, unless the temporary bill is a billing worksheet, in which case you can view and modify it in the Billing Worksheet component and in bill entry. Bills with a bill status of TMR can never be invoiced. You can generate only a pro forma from a temporary bill. To set up a special invoice numbering ID for use specifically for the creation of temporary bills, define the temporary invoice number ID on the Installation Options - Billing - General Options page.

Note. When you approve a bill imported from PeopleSoft Contracts and Project Costing with a status of TMR, that bill is copied to a real bill; the real bill is subsequently invoiced.

To mark interface lines as temporary, set the TMP_BILL_FLG to Y on the LINE transaction. The TMP_BILL_FLG does not need to be part of the bill-by criteria to take advantage of this feature. You may need to resend the transactions to the Billing interface multiple times before you have determined that the temporary bill meets your satisfaction.

When you create temporary bills, the system stores them in the PeopleSoft Billing tables. If you often create temporary bills, the billing tables fill quickly with data for these bills, which eventually degrades system performance. After you print a temporary bill and you no longer need it in the PeopleSoft Billing system, purge it from the Billing tables. To purge temporary bills from the system, use the Delete Temporary Bills page or the Billing Workflow/Batch Parameters page.

Note. Temporary bill processing is not supported for adjustments through the Billing interface.

Deleting Temporary Data

Defining Billing Installation Options

Processing Bill Lines with Deferred Revenue Accounting Entries

You can send bill lines to the Billing interface staging tables to create invoices for products or services that you will deliver in the future or over a range of time. You can import into PeopleSoft Billing deferred revenue accounting entries that defer revenue recognition based on a revenue recognition date and a proration method.

Supported revenue recognitions include contract date, order date, ship date, and range of dates (using CHARGE_FROM_DT and CHARGE_TO_DT fields or START_DT and END_DT fields).

When you use a range of dates as the revenue recognition basis, you can set up different methods of proration. If you enable the deferred revenue feature, bill lines using a revenue recognition bases other than INV (invoice date) must have deferred revenue accounting entries (DR) that correspond to each revenue accounting entry (RR).

This table represents a bill line in the INTFC_BI table:

TRAN_TYPE_BI	REV_RECOG_BASIS	CHARGE_FROM_DT	CHARGE_TO_DT
LINE	CHG	April 1, 2003	April 15, 2003

This table represents bill lines in the INTFC_BI_AEDS table:

TRANS_TYPE_BI	TRANS_TYPE_BI_SEQ	ACCT_ENTRY_TYPE	DST_ID
AE	1	RR	REV W/DFR
AE	2	DR	DFR REV

When a deferred revenue bill line has a discount or surcharge, each discount or surcharge entry (DS) must have a corresponding deferred revenue discount or surcharge entry (DDS).

Note. To use deferred revenue accounting, you must set up the PeopleSoft Billing and PeopleSoft General Ledger systems to accommodate deferred revenue accounting entries.

See Setting Up Deferred Revenue Accounts.