Common Elements Used in Setting Up an Integration to the Transaction Billing Processor
Field or Control |
Definition |
---|---|
Agreement |
A PeopleSoft CRM agreement is a list of obligations to which a service provider has agreed or committed to the customer. The agreement lines listed on the agreement include services and products covered by the agreement, information about who or what customer locations can request service, and the level of service that is provided, which includes restore time, response time, prime period of maintenance, and service coverage (time, material, and expense). |
Agreement Pricing |
Agreement pricing records define the fee paid for a specific service or support offering. The agreement price is defined when the agreement is issued to the customer. PeopleSoft CRM also enables you to initiate recurring charges for which a customer might pay a monthly or quarterly fee. |
Agreement Service Pricing |
Agreement service pricing records define what the customer pays when the work associated with the service or support offering on the agreement is performed. This record includes the price paid per transaction covered by the agreement line. |
Billing Plan |
When the system creates a contract, it also generates a billing plan that is linked to a contract line. The billing plan determines how a transaction should be billed. It contains customer billing information, billing method (for example, as-incurred), and status of the billing plan. |
Contract Amendment |
A contract amendment is any change made to an active contract for which you are altering the fundamental obligations and entitlements of the contract. |
Deferred Revenue |
Deferred revenue helps to create and send invoices for products or services that are to be delivered in the future or over a range of time. You may use deferred revenue to generate accounting entries that defer revenue recognition based on a revenue recognition date and proration method that you select. |
General Ledger |
General ledger is where all of the journal entries are posted. Journal Generator populates the general ledger with accounting entries (for example, accounts receivable and revenue entries). |
Location |
Select the location of the store where the order is to be purchased. This field is used for tax vendor exceptions and reporting. |
Order Acceptance Location |
Select the location where the order is to be accepted. The system uses this field to determine tax jurisdiction. |
Order Origin Location |
Select the location where the order originated. The system uses this field to determine tax jurisdiction. |
Rate Based Contract Line |
A rate based contract line is a transaction-based offering (or an ad hoc offering) that the Transaction Billing Processor picks up and sends to PeopleSoft Billing. |
Revenue Plan |
When the system creates a contract, a revenue plan is also created and associated with a contract line. You can create revenue plans either automatically or manually. The contract line, however, must be linked to the revenue recognition plan to recognize revenue. |
Revenue Recognition |
Revenue recognition occurs when the system sends revenue information to the general ledger and it is counted in the revenue projection for the accounting period. |
Store Location |
Enter the address of the store location. Note: If you are using a third-party tax vendor, the entry in this field should match the store location code in Vertex or Taxware. |