CIPERB: Customers, Invoices, Project Expenses Report & Billing

• In Oracle, invoices are sent to customers, and payments are sent to Suppliers.
• A Customer is a person or business that UCSD needs to bill for services that UCSD provides.
• A Supplier is a person or business that provides UCSD with a service that UCSD needs to pay the business for.
• If a supplier account is required instead, please use PaymentWorks.

Customer: A party, an organization, or a person, with whom you have a selling relationship. This selling relationship can result from purchasing products and services or negotiating terms and conditions that provide the basis for future purchases. **This is known as the Party or Registry ID in Oracle**

Customer Account: A customer account represents the attributes of the business relationship that a customer can enter into with UCSD. The account has information about the terms and conditions of doing business with UCSD.

You can create multiple customer accounts for a customer, to maintain information about different categories of business activities. For example, to track invoices for different types of sales, you can maintain an account for sponsored research, service agreements, consulting services, etc.

Contact: A person who communicates for or acts on behalf of a customer or customer account. Contacts are added at the customer level internally and can be assigned at the account or address/site level. Multiple contacts can be added.

Sites/Addresses: A site is where the customer is physically located. Party sites are added internally at the customer level but created at the account level. An account site is a customer site used in the context of an account. Multiple sites can be added under an account.

The following primary roles will be defined for CIPERB application:

1. UCSD CIPERB Manage GP User JR + UCSD CIPERB Manage Customer ALL JR = Manage Customer & Others Customers (Parties and accounts) (GP Super User)
2. UCSD CIPERB Manage GP User JR + UCSD CIPERB Manage Customer Accounts Only JR = Able to add/edit Other Accounts

Please note, the Oracle & Concur Role Request Form in Services & Support has been updated to require users requesting OFC inquiry roles and higher-level access to complete specific training courses in UC Learning.

• To learn more about training requirements, please go to the Finance Training Program in Blink.
• For information about Oracle and Concur role requests, see
  • KB0032241 - How to Request Oracle and Concur Roles
  • KB0035155 - How to Request CIPERB Roles to Create & Edit Customers (Parties)
  • KB0035154 - How to Request CIPERB Roles to Create & Edit Customer Accounts (Not Parties)
• Internal Controls Checklist Updated: The internal controls checklist has been updated to reflect the release of the new Consolidated Exceptions Report. Please download the latest version of the checklist from Blink: Best Practices in Internal Controls.  

Specific Training Requirements for Role Request Form Submissions:

Oracle Foundationsfor the following roles:

• All standard roles for all business units, except for UCSD BI Consumer JR
• All financial unit approver roles [UCSD WF XXXXXXX Approver JR]
• All cost transfer approver roles [UCSD WF XXXXXXC Cost Adjustment Approver JR]
• All elevated roles for all business units

CIPERB: Customers, Invoices, Project Expenses Report & Billing for the following roles:

• CIPERB Manage Customer Accounts Only
• CIPERB Manage GP User
• CIPERB Manage Customer ALL
• CIPERB Manage Events JR

Corresponding Oracle Applications

New Customer Flowchart

Knowledge Based Articles (KBAs)

KB0035096 - How To Use The CIPERB Application For Customer Accounts in Oracle

KB0035287 - How to Create & Upload Mass Events in CIPERB

KB0032971 - How to Search for a Customer

CIPERB Overview

1. Homepage defaults to the Dashboard and provides ability to toggle between light & dark themes  
   
   
2. When performing searches, select the Customer Type (Organization or Person) prior to conducting the Search                                
   
   
   
   
3. When editing customer accounts, the Organizational Chart View and the Explorer View on the left-hand panel provide a flowchart for customer account details 
   
   

Additional CIPERB Requirements

The implementation of Tax IDs for new Customers is a requirement for the CIPERB application. Having a customer tax identification number (TIN) [domestic & foreign] is important for various reasons, both for the customer and the entity they're transacting with (this does NOT apply to individual "Person" accounts - SSNs are never required for "person" customer accounts). The following key points elaborate on this implemented customer account policy:

1. Identification and Verification: TIN helps in uniquely identifying customers for tax purposes. It provides a reliable means of verifying a customer's identity, especially for financial transactions and regulatory compliance.
2. Tax Reporting and Compliance: For businesses, having customers' TINs is crucial for tax reporting and compliance. It ensures accurate reporting of income and helps in fulfilling tax obligations such as issuing 1099 forms (in the United States) for certain types of transactions.
3. Preventing Tax Evasion: TINs help in preventing tax evasion by ensuring that income earned by individuals or entities is properly reported to tax authorities. Without TINs, it would be easier for individuals or businesses to conceal income and evade taxes.
4. International Transactions: In international trade and transactions, TINs are often required for customs clearance and tax purposes. They help in identifying parties involved and ensuring compliance with tax regulations of respective countries.
5. Credit and Financial Transactions: TINs are sometimes used by financial institutions for credit checks and assessing the creditworthiness of customers. They can be part of the information required when opening bank accounts or applying for loans.
6. Legal and Regulatory Requirements: In many jurisdictions, there are legal and regulatory requirements mandating the collection and use of TINs for certain types of transactions. Failure to comply with these requirements can lead to penalties and legal consequences.
7. Business-to-Business Transactions: In business-to-business transactions, TINs are often required for invoicing and accounting purposes. They help in tracking transactions, managing accounts receivable and payable, and facilitating smooth business operations.

Overall, having a customer tax identification number is important for ensuring transparency, accountability, and compliance in financial transactions and tax matters. It helps in building trust between parties involved and contributes to the integrity of the financial system.

CIPERB Application Demo

CIPERB Mass Event Creation & Upload Demo

CIPERB Training Session 1 - 05/01/24

CIPERB Training Session 2 - 05/08/24

CIPERB Training Session 3 - 05/15/24

CIPERB Training Session 4 - 05/22/24

CIPERB Training Session 5 - 06/05/24

CIPERB Training Session 6 - 06/20/24

CIPERB Training Session 7 - 06/26/24