Accounting String Requirements for other UC Campuses

As a general rule, departments that are charging other UC campuses shouldn’t need an understanding of the other school’s account string. When the department asks the other campus for their account info, the department should simply copy and paste whatever the other campus provides into the KFS ICT document. It’s the other campus’ responsibility to ensure that the account info that they provide meets the requirements of their accounting system.

* indicates mandatory field

(#) indicates number of max characters

UC Berkeley

**Note: For UC Berkeley, the Program field is mandatory when the account begins with 5.

FAU Loc* (1) Account* (5) Fund* (5) Org* (5) Program** (2) Project (6) Flexfield (5)

UC San Francisco

FAU Loc* (1) Business Unit* (5) Account* (5) Fund* (4) Dept ID* (6) Project* (7) Activity Period (2) Function* (2) Flexfield (6)

UC Davis

FAU Loc* (1) Account* (7) SubAccount (5) Object* (4) SubObject (3) Project (10) Reference (8)

UC Los Angeles

**Note: For UCLA, if the account starts with 1 or 2, the sub and object are not mandatory.

FAU Loc* (1) Account* (6) Cost Center (2) Fund* (5) Project (6) Sub** (2) Object** (4) Source (6)

UC Riverside

FAU Loc* (1) Account (6) Activity* (6) Fund* (5) Function* (2) Cost Center (5) Project Code (5)

UC San Diego

FAU Loc* (1) Index Number* (7) Fund* (5 or 6) Org (6) Account* (6) Program (6)

UC Santa Cruz

FAU Loc* (1) Fund* (5) Org* (6) Account* (6) Program (2) Activity (6) Doc Ref (6)

UC Santa Barbara

FAU Loc* (1) Account* (6) Fund* (5) Object* (4) Sub* (1) Reference (6)

UC Merced

**Note: For UCM, if the account starts with 1 or 2, the sub and object are not mandatory.

FAU Loc* (1) Account* (6) Cost Center (2) Fund* (5) Project (6) Sub** (2) Object** (4) Source (6)

UC Office of the President

**Note: For UCOP, if the account starts with 1 or 2, the sub and object are not mandatory.

FAU Loc* (1) Account* (6) Cost Center (2) Fund* (5) Project (6) Sub** (2) Object** (4) Source (6)