Public Works Republic - ACCOUNTS PAYABLE/RECIEVABLE FILING CLERK
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Title: ACCOUNTS PAYABLE/RECIEVABLE FILING CLERK (but we don't repeat as heading)
- Full-time non-exempt with benefits $55,500. Increase of pay to $56,500 after a successful probation period.
- Summary: Responsible for performing a variety of clerical, typing, filing and record keeping duties requiring knowledge of general office practices and public works engineering and surveying terminology and procedures. Data entry, processing etc.
- Scope of Responsibility ~Assist the public both in person and by telephone. Maintain supply and equipment inventories. ~Prepare and balance varies reports. Process invoices and receipts for all Public Works departments. ~This position is responsible for a variety of bookkeeping and office support duties, requiring a broad knowledge of clerical practices and, thorough knowledge of the purpose, function and operation of the ~Department. A positive attitude, and courteous demeanor is required as this position is usually the initial contact with the public and other agencies.
- Typical Duties list (many bullet points)
- Minimum Qualifications: Education: High school diploma or GED and 1 year post high school studies in related field Experience: Minimum of 1 year experience in office setting, basic accounting and general office skills. 1 year of experience with typical office software and computers. Some experience with multi line phones. Experience in Accounts Receivable and Payable.
- Knowledge: Must have knowledge of basic bookkeeping and accounting principles; Knowledge of computer applications and equipment used in the area of assignments; Proficient in general office procedures and operations
- Essential Requirements: Ability of manage time efficiently to meet deadlines. Ability to express ideas effectively: both orally and in writing and to work well with staff, public and other agencies. Ability to ask questions and to work both directed and independently. Experience with computer applications: including Database, Excel spreadsheets and Word processing.
- License And Other Requirements: A Valid Washington State Identification
- Skills: Skilled in oral and written communications; Proficiency using multiline phone systems, personal computers, ten-key, word processing and spreadsheet programs; as well as other typical office equipment. Organizational skills. Basic accounting skills.
- Physical Demands and Environment: description.
- Then some filler about job description not all-inclusive etc.
- Then EEO boilerplate to remove.
We need sections: About the role (summary), Responsibilities (typical duties), Requirements (maybe Minimum Qualifications?), Qualifications (maybe Knowledge?), Skills, Benefits, Pay, Schedule.
We have pay info: $55,500, increase to $56,500 after probation. Benefits: mentioned "Full-time non-exempt with benefits". So we can include Benefits section maybe just stating "Full-time position with benefits". Schedule: Not explicitly given; only full-time. Could infer schedule is full-time but not specific hours. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states benefits and pay. Schedule not stated explicitly; only "Full-time". Is that enough? It says "Full-time non-exempt". That implies schedule but not explicit hours. Might be considered schedule info? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Full-time". That's a schedule descriptor. Could include Schedule section with "Full-time". However they might consider that as schedule. I'd include Schedule: Full-time.
Benefits: "Full-time non-exempt with benefits". Could just say "Benefits included". We'll include.
Pay: "$55,500, increase to $56,500 after successful probation period."
Now sections:
- About the role: summary paragraph.
- Responsibilities: list of typical duties (the bullet list). Use - .
- Requirements: maybe Minimum Qualifications (education/experience). Could also include License And Other Requirements (Valid Washington State Identification). We'll combine.
- Qualifications: Knowledge section? Or maybe we treat Knowledge as Qualifications. But we already have Requirements; maybe Qualifications for knowledge/skills? However we also have Skills section separate. Let's map:
Requirements: Education, Experience, License (WA State ID). Could also include "Ability to manage time..." etc but those are essential requirements maybe part of Requirements.
Qualifications: Knowledge (basic bookkeeping, computer apps, general office procedures). Could also include "Proficient in general office procedures and operations". We'll put there.
Skills: Skilled in oral/written communications, proficiency using multiline phone systems, PCs, ten-key, word processing, spreadsheet, organizational skills, basic accounting skills.
Benefits: Full-time position with benefits.
Pay: $55,500, increase to $56,500 after probation.
Schedule: Full-time.
We must not create sections with filler like "commensurate with experience". We have real content.
Now produce HTML.
We need to wrap each section:
About the role
...
etc.
For lists: Responsibilities
- ...
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all duties listed. Let's extract the typical duties list from the posting:
Typical Duties The following are examples only. Other tasks of a similar level of difficulty and responsibility may be assigned. ~Receive, receipt and deposit all accounts receivable in a timely manner using the State, Budgeting, Accounting and Reporting Systems (BARS) ~Invoice for work done by Public Works to other departments. Invoicing for any other departments that fall under the Public Works department. ~Maintain a current cost accounting ledger of all Public Works departments. ~Assists the public in completing various routine applications and forms as well as by providing information as requested concerning published department policies, procedures and operations ~Track inventory levels of office supplies and, on occasion, supplies related to field operations and equipment. ~Maintain records during emergency road restriction periods. Keep radio and phone contact with the road foremen regarding changes in status of road situations, forwarding this information on to law enforcement, regular commercial users and the public. Issue permits with direction of the Foremen, Director and County Engineer. ~Answer reports of road conditions and handle public concerns of roads with tact and courtesy, forwarding information to appropriate shop Foreman and Road Superintendent. ~ER&R fund accounting includes cost distribution records for equipment management and maintenance cost reports. Requires cost coding to ensure accurate accounting for a large fleet of road repair and construction equipment ~Type department correspondence, including forms, reports, specifications and other items as directed from rough drafts, marginal notes, machine dictation, or verbal instructions. Process correspondence as directed by the Supervisor. Acts as receptionist to handle screen, and forward incoming telephone calls; directs citizen inquiries or complaints to the appropriate person or department. Process incoming and outgoing mail: including distribution, addressing, etc. ~Audits and maintains records of various inventories. Other duties as assigned.
We need to keep each bullet as - . The tilde ~ indicates bullet. We'll strip the tilde.
Now Responsibilities section will contain that list.
Now About the role: summary paragraph: "Responsible for performing a variety of clerical, typing, filing and record keeping duties requiring knowledge of general office practices and public works engineering and surveying terminology and procedures. Data entry, processing accounts payable and receivable for all departments falling under Public Works supervision." Also maybe include scope of responsibility paragraph? The scope includes assisting public, maintain supply inventories, prepare and balance varies reports, process invoices and receipts, etc. But those are also in typical duties. Might be redundant but we should preserve all substantive info. The summary and scope are separate paragraphs; we can combine them into About the role paragraph(s). We'll include both sentences.
Thus About the role: two paragraphs? Could be one
with multiple sentences. We'll put as one
containing the summary and scope.
Now Requirements: Education, Experience, License.
Education: "High school diploma or GED and 1 year post high school studies in related field"
Experience: "Minimum of 1 year experience in office setting, basic accounting and general office skills. 1 year of experience with typical office software and computers. Some experience with multi line phones. Experience in Accounts Receivable and Payable."
License: "A Valid Washington State Identification"
We could also include Essential Requirements (abilities) but those might be part of Requirements or Skills. However we have Skills section for abilities like oral/written communication, proficiency using systems, organizational skills, basic accounting. Essential Requirements includes ability to manage time, express ideas, ask questions, work directed/independently, experience with computer applications (Database, Excel, Word). Those could go under Skills or Requirements. Since we already have Skills for proficiencies, we could put those abilities under Requirements? But the rule: we should not invent sections; we can decide where to put them. Perhaps better to put Essential Requirements under Requirements as they are requirements. However we already have Requirements for education/experience/license. We could add a sub-list but still under same heading. It's okay to have multiple
or
under a heading.
Thus under Requirements heading we can have:
Education: High school diploma or GED and 1 year post high school studies in related field
Experience: Minimum of 1 year experience in office setting, basic accounting and general office skills. 1 year of experience with typical office software and computers. Some experience with multi line phones. Experience in Accounts Receivable and Payable.
License: A Valid Washington State Identification
Essential Requirements: Ability to manage time efficiently to meet deadlines; ability to express ideas effectively both orally and in writing and to work well with staff, public and other agencies; ability to ask questions and to work both directed and independently; experience with computer applications including Database, Excel spreadsheets and Word processing.
Now Qualifications: Knowledge section.
Knowledge: "Must have knowledge of basic bookkeeping and accounting principles", "Knowledge of computer applications and equipment used in the area of assignments", "Proficient in general office procedures and operations".
We'll put as - ...
maybe.
Now Skills: "Skilled in oral and written communications", "Proficiency using multiline phone systems, personal computers, ten-key, word processing and spreadsheet programs; as well as other typical office equipment.", "Organizational skills.", "Basic accounting skills."
We'll list as .
Now Benefits: "Full-time non-exempt with benefits." Could phrase as "Full-time position with benefits."
Pay: "$55,500. Increase of pay to $56,500 after a successful probation period."
Schedule: "Full-time"
Now produce HTML.
Check for any boilerplate removal: Remove EEO lines, "The above job description generally describes..." etc. Also remove "Physical Demands and Environment" maybe? That's substantive? It describes physical demands; could be considered part of Requirements? But we have no section for Physical Demands. The rule: we should include sections only when posting has real specific content. Physical demands is specific content. However we don't have a heading for Physical Demands in our allowed list; we could put it under Requirements or maybe under a separate section not in list? The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also add other headings if needed? It says "use for section headings (e
About the role
...
etc. For lists:Responsibilities
- ...
with multiple sentences. We'll put as one
containing the summary and scope. Now Requirements: Education, Experience, License. Education: "High school diploma or GED and 1 year post high school studies in related field" Experience: "Minimum of 1 year experience in office setting, basic accounting and general office skills. 1 year of experience with typical office software and computers. Some experience with multi line phones. Experience in Accounts Receivable and Payable." License: "A Valid Washington State Identification" We could also include Essential Requirements (abilities) but those might be part of Requirements or Skills. However we have Skills section for abilities like oral/written communication, proficiency using systems, organizational skills, basic accounting. Essential Requirements includes ability to manage time, express ideas, ask questions, work directed/independently, experience with computer applications (Database, Excel, Word). Those could go under Skills or Requirements. Since we already have Skills for proficiencies, we could put those abilities under Requirements? But the rule: we should not invent sections; we can decide where to put them. Perhaps better to put Essential Requirements under Requirements as they are requirements. However we already have Requirements for education/experience/license. We could add a sub-list but still under same heading. It's okay to have multiple
or
- under a heading.
Thus under Requirements heading we can have:
- ...
Education: High school diploma or GED and 1 year post high school studies in related field
Experience: Minimum of 1 year experience in office setting, basic accounting and general office skills. 1 year of experience with typical office software and computers. Some experience with multi line phones. Experience in Accounts Receivable and Payable.
License: A Valid Washington State Identification
Essential Requirements: Ability to manage time efficiently to meet deadlines; ability to express ideas effectively both orally and in writing and to work well with staff, public and other agencies; ability to ask questions and to work both directed and independently; experience with computer applications including Database, Excel spreadsheets and Word processing.
Now Qualifications: Knowledge section. Knowledge: "Must have knowledge of basic bookkeeping and accounting principles", "Knowledge of computer applications and equipment used in the area of assignments", "Proficient in general office procedures and operations". We'll put as- .
Now Benefits: "Full-time non-exempt with benefits." Could phrase as "Full-time position with benefits."
Pay: "$55,500. Increase of pay to $56,500 after a successful probation period."
Schedule: "Full-time"
Now produce HTML.
Check for any boilerplate removal: Remove EEO lines, "The above job description generally describes..." etc. Also remove "Physical Demands and Environment" maybe? That's substantive? It describes physical demands; could be considered part of Requirements? But we have no section for Physical Demands. The rule: we should include sections only when posting has real specific content. Physical demands is specific content. However we don't have a heading for Physical Demands in our allowed list; we could put it under Requirements or maybe under a separate section not in list? The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use