Service Records Administration Clerk

HRS Talent Solutions; Mobile (AL); Remote; USD 37,000 - 40,000; Full time

Job summary

HRS Talent Solutions seeks a Service Records Administration Clerk to support remote office administration by processing and recording service codes, descriptions, and entries.

You will read requests, verify codes against lookup tables, enter matched records, and flag conflicts for review. No specialist questions beyond the reference list; training will be provided. This remote role offers flexible engagement with hourly compensation in the $27.05–$28.85 range.

Qualifications

• No service-coding experience required; training provided.
• Basic online forms and careful reading are important.
• Data entry or customer service experience is helpful but optional.

Responsibilities

• Read assigned written requests and related records.
• Locate the current approved service-code reference.
• Compare code, description, and account context.
• Enter straightforward supported matches in permitted fields.
• Flag obsolete, missing, or conflicting references.
• Record a correction after an authorized decision.
• Keep an unresolved item assigned to the right owner.
• Check saved entries for typing or transposition errors.

Skills

Attention to detail

Data entry

Reading comprehension

Remote work

Job description

Service Records Administration Clerk

Office administration Remote records support

Full-time or part-time. The hourly range is $27.05–$28.85.

A written service request may mention an internal code that needs to be recorded accurately. The Service Records Administration Clerk compares that code with an approved lookup list, enters a supported match in the online record, and flags any uncertain item. The position does not choose a service for a customer or decide which price applies. It makes an existing request easier for the responsible team to process.

Codes often look alike. A single letter can distinguish two services, and an old code may still appear in a prior document. Check the current reference before entering a match. Read the description alongside the number instead of relying on memory. If the request’s wording and code point to different services, leave the record for review with both details noted. Do not change the requester’s words to fit the code list.

For example, a request might quote code S14 while describing a service whose current reference is S41. That is a conflict, not a typing correction you should silently make. Record the code as supplied and the differing description, then send the question to the service owner. Another request may use an older code that has a documented replacement; use the approved mapping and keep a note of the source. This careful distinction protects the customer from a reply about the wrong service and the team from an unsupported record change.

A careful lookup

Begin with the assigned request and permitted account view. Identify the code as written, check the current approved table, and see whether the surrounding request supports the same service. Make the permitted entry and reopen the saved record to confirm it landed in the correct field. If a code is missing, deprecated, or shared by multiple categories, document the question and refer it to the service owner. The result should show a reliable source, not just a filled box.

This role may also involve correcting a previously mistyped code after the owner supplies confirmation. Keep the change history where the employer requires it. A colleague reviewing the record should be able to see why a correction occurred. If a customer’s online form contains only a free-text description, you may identify possible matches for review, but final classification stays with the authorized team.

Tasks you could handle

• Read assigned written requests and related records.
• Locate the current approved service-code reference.
• Compare code, description, and account context.
• Enter straightforward supported matches in permitted fields.
• Flag obsolete, missing, or conflicting references.
• Record a correction after an authorized decision.
• Keep an unresolved item assigned to the right owner.
• Check saved entries for typing or transposition errors.

Customer service colleagues may later rely on the code when replying to a question. Your office administration work helps them avoid giving information about the wrong service. You are not expected to answer a specialist question merely because you found a matching label. Use the approved handoff if a request needs explanation beyond the reference list.

No service-coding experience is required. The employer will train you on its reference table, record system, and approval process. Basic online forms, careful reading, and comfort with short alphanumeric strings matter more than a particular prior title. Data entry or customer service experience is helpful but optional. The employer will specify secure access and scheduling for this remote records position.

Candidate review

You are eligible without service-code experience because the company provides its lookup guide. Accuracy with forms or short reference numbers is worth making visible on your resume. Some applicants will bring office administration experience; others may be entering their first clerical role. If you’re selected for the next step, you may be asked to complete an application on the hiring company’s website. The employer will identify the specific record system used for this opening.