Skip to main content

System Status: 

CIPERB: Customers, Invoices, Project Expenses Report & Billing

CIPERB is a new tool that provides full functionality for individuals to manage customers under the Accounts Receivable module in the OFC application. Customer data created and updated via CIPERB will be updated real-time in Oracle to improve customer experiences and increase operational efficiency.

Training Course

The CIPERB course has now been uploaded to the UC Learning module for immediate CIPERB training and access.  Please log into the UC Learning platform to access the CIPERB: Customers, Invoices, Project Expenses Report & Billing eCourse. Completing this course will be essential to the customer account creation and amendment process as we phase out the current process of submitting request forms.

The process of submitting the Create New Oracle Customer form and Edit Existing Oracle Customer form will be phased out by July 1, 2024.

*This course must be completed prior to requesting role access to the CIPERB application*


Launch CIPERB: Customers, Invoices, Project Expenses Report & Billing

*Access to CIPERB requires VPN connection*

For additional support, reference KBA KB0035096 - How To Use The CIPERB Application For Customer Accounts in Oracle.


CIPERB is utilized to create customer accounts in Oracle.
  • 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.

Roles & Access

The following primary roles will be defined for CIPERB application:


Role Name Role Description Role Workflow


User can View any data in CIPERB

No Workflow-anyone can have this role


User can only view Non-SP Data (non-sp customers, no FER, etc)

Non Sponsored data access

UCSD CIPERB Manage Customer ALL JR

User can create/edit Customers (Parties)

Department Approval + AR Team Approval

UCSD CIPERB Manage Customer Accounts Only JR

User can create/edit Customer Accounts

Department Approval


  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


To request CIPERB access, please use the Oracle and Concur Role Requests Form selecting one or more of the role names, and review the following KBAs for additional assistance:

CIPERB Flowcharts

Corresponding Oracle Applications

 Visual of corresponding Oracle Applications




New Customer Flowchart

Customer Create Flowchart

Additional Resources

Knowledge Based Articles (KBAs)

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

KB0032971 - How to Search for a Customer


CIPERB Overview

  1. Homepage defaults to the Dashboard and provides ability to toggle between light & dark themes  

    Toggle CIPERB 1
  2. When performing searches, select the Customer Type (Organization or Person) prior to conducting the Search                                

    Select Customer Type

  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. 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.

Demo & Training Videos

For additional assistance, please submit a Services & Support ticket to the following:

  • I want to: Ask a Question or Make a Request
  • About: Financial Accounting
  • Related to: Oracle Project Portfolio Management
  • More Specifically: CIPERB (Customers, Invoices, Project Expenses Reporting & Billing) Inquiries

Find answers, request services, or get help from our team at the UC San Diego Services & Support portal or call the Finance Help Line at (858) 246-4237.