Authorization Number

0 views

Skip to first unread message

Janoc Florez

unread,

Aug 3, 2024, 12:14:32 PM8/3/24

to holciadecu

I'm new to the Concur Community, but not new to managing our corporate travel policies and approvals. We are a large non-profit medical association and we utilize Concur Expenses and Concur Travel for staff only (over 500). We have not integrated in our Members (over 54,000), nor do we plan to. When Staff or Members travel on behalf of the organization for business, we cover the cost of their airfare. Prior to any travel booking, trip request must be approved and assigned a travel authorization number (TA #). Our TA # is more than a standard Program/Project number as it consists of a combination of valued numbers important to our accounting team as well as to our corporate travel company for billing purposes (i.e., 1 Letter + 4 digit project code - 4 digit cost center - 6 digit activity code). Our TA request process is a multi stepped manual process (complete TA request form, submit form for review/approval, accounting assigns TA #, records TA #, add to original request form, send from back to requesting staff member with a copy to our corporate travel company to code tickets for our tracking and billing purposes). Additionally, we have no automated verification that authenticates that the provided TA # in Concur Travel or provided to our corporate travel company is the correct approved TA # assigned to said trip. This results in many miscodings that require hours of research on the back for our accounting team to identify and properly recode. In the millennium of technology and automation, we are liteyears behind! Does anyone have a recommendation of an automated system/platform for better efficiency. Sincerely, Drowning in too many steps

If you are open to adding Concur Request to your current system, that could help the manual approval process. You would put the travel requests through Concur Request, and once approved, the person could then book through Concur Travel, and then put the expenses through Concur Expense. It all connects to each other, and all the history (approvals/rejections/changes) would be visible in one place. Concur has many options to add custom fields as well, but that might be more difficult and would not solve the manual processing of pre-approvals.

Thank you Jessica for this suggestion. We are exploring more about Concur Request to see if this a viable option for our unique needs and/or if its something we can adopt our current ways into. I know there is a better solution exists than our out dated manual process. JulieC.

A CAF number is a unique nine-digit identification number and is assigned the first time you file a third party authorization with IRS. A letter is sent to you informing you of your assigned CAF number. Use your assigned CAF number on all future authorizations.

CAF numbers are different from the third party's TIN (Taxpayer Identification Number), EIN (Employer Identification Number) or PTIN (Preparer Identification Number). CAF numbers may be assigned to an individual or a business entity.

If you are a tax professional and cannot remember your CAF number, you may call the Practitioner Priority Service, otherwise known as PPS. PPS may be reached at 866-860-4259. A PPS assistor will initiate the process to help you retrieve your CAF number once you provide your authenticating information.

What is a CAF number?
A CAF number is a unique nine-digit identification number and is assigned the first time you file a third party authorization with IRS. A letter is sent to you informing you of your assigned CAF number. Use your assigned CAF number on all future authorizations.

Ability to Modify Authority
The Centralized Authorization File (CAF) allows the input of codified additional acts authorized on a Form 2848, Line 5a. Taxpayers should be clear with regard to additional acts authorized and to which representative it applies.

CAF Unit Addresses, Fax Numbers, and State Mapping
General Rule: All states west of the Mississippi process authorizations in Ogden; all states east of the Mississippi process authorizations in Memphis. Exceptions: Louisiana and Arkansas process in Memphis; Wisconsin process in Ogden and International authorizations are processed in Philadelphia.

Hunters and certain trappers (bobcat, fisher and river otter only) will have several options for registering harvests through the GameReg electronic registration system. Go online to gamereg.wi.gov (fastest and easiest option), call 1-844-GAME-REG (1-844-426-3734) or, if registering a deer or bear, find an in-person registration station that provides one of these methods.

Upon submitting all required harvest information through GameReg, the hunter will receive a 10-character confirmation number for his/her records. This confirmation number no longer needs to be written on the tag or harvest authorization, but should be retained and may be required if the game is taken to a taxidermist or meat processor. All hunters will obtain a confirmation number at the completion of registration, even if registering at an in-person station.

Exception: while bobcat, are reported through GameReg, they still require in-person registration within seven days of the end of the month of harvest. Otter and fisher no longer have in person registration.

For key species-specific registration requirements, review the harvest registration fact sheet [PDF]Go Wild: Step-by-Step InstructionsFor help with purchasing a license please see our Go Wild step-by-step instructions.

A new section has been added to your Go Wild personal homepage. The My GameReg section provides you with information on your current tags where you can view and reprint your unused tags or click the quick link to report your harvest. Also available is your GameReg harvest history, where you can view your previous GameReg harvest reports with the confirmation number and the details of your harvest.

Harvest History lists all registered harvests on your Go Wild account (2016 to present). This section includes the tag/harvest authorization number and registration confirmation number for each harvest, allowing you to look up your confirmation number if taxidermists or meat processors require it for processing the harvested animal.

Car-killed deer and turkey can also now be registered online through GameReg. On gamereg.wi.gov, click on the car-killed deer and turkey link to get started. Car-killed deer and turkey can also be registered at 608-267-7691. Please note that car-killed bear must still be registered by phone at 608-267-7691. Learn more about taking possession of car-killed wildlife.

Electronic registration allows hunters to fulfill the requirements of registering their harvests using the phone or Internet, making this task fast, easy and convenient for hunters while providing the department with timely access to valuable harvest data.In 2015, Wisconsin rolled out the electronic registration system GameReg for all deer and bear hunters. By the end of the 2015 deer seasons, over 300,000 hunters had successfully registered deer electronically, with only 3 percent requiring additional assistance in registering and an overall compliance rate of over 90 percent.

To prepare for this change, the department conducted a test of electronic registration options during the 2014 deer seasons. Over 14,000 hunters were selected to participate and offer feedback. During all Wisconsin deer seasons, over 10,000 deer were registered electronically. Hunters were later surveyed for feedback, resulting in changes that will make the new electronic registration system as quick and easy as possible.

Upon submitting all required harvest information, hunters will receive a 10-character confirmation number which must be written on the carcass tag. Once hunters have completed this step, the animal will be officially registered. All hunters must obtain a confirmation number and write it on the tag for the animal to be registered, even if registering at an in-person station.

Since the 1950s, in-person registration stations have aided Wisconsin hunters in registering their harvests. Local businesses have always been a cornerstone of the hunting experience and are encouraged to continue offering registration services. The traditions of registration stations do not need to end.

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner.

This specification definesthe core OpenID Connect functionality:authentication built on top of OAuth 2.0 andthe use of Claims to communicate information about the End-User.It also describes the security and privacy considerations for using OpenID Connect.

The OpenID Connect Core 1.0 specification definesthe core OpenID Connect functionality:authentication built on top of OAuth 2.0 andthe use of Claims to communicate information about the End-User.It also describes the security and privacy considerations for using OpenID Connect.

In the .txt version of this specification, values are quoted to indicate that they are to be taken literally. When using these values in protocol messages, the quotes MUST NOT be used as part of the value. In the HTML version of this specification, values to be taken literally are indicated by the use of this fixed-width font.

IMPORTANT NOTE TO READERS: The terminology definitions in this section are a normative portion of this specification, imposing requirements upon implementations. All the capitalized words in the text of this specification, such as "Issuer Identifier", reference these defined terms. Whenever the reader encounters them, their definitions found in this section must be followed.

ID Tokens SHOULD NOT use the JWS or JWEx5u,x5c,jku, orjwkHeader Parameter fields.Instead, references to keys used arecommunicated in advance using Discovery and Registration parameters,per Section 10 (Signatures and Encryption).