PF1
Payroll Fundamentals 1Exam
PF1 Exam Guide: Payroll Concepts, Study Priorities, and Scheduling Decisions
PF1 is best approached as a payroll-operations assessment: the supplied evidence points to work involving employee records, earnings, taxes, deductions, benefits, garnishments, payroll transactions, reporting, and payroll-to-ledger controls. It is suited to candidates building or validating practical payroll knowledge, although the supplied official pages do not identify PF1 by name or provide a PF1 blueprint. This guide therefore helps you decide which payroll topics to study first, how to test your understanding with defensible calculations, and what to confirm with the exam owner before applying or booking.
What does the available evidence establish about PF1?
The official research supplied for this page describes PayrollOrg certification examinations and payroll-system knowledge, but it does not publish a PF1 exam page, content outline, eligibility rule, score, question count, duration, language list, or delivery specification. Treat PF1-specific details as items to verify before you commit money or select an appointment.
The Pearson VUE page identifies PayrollOrg resources for the FPC and CPP examinations, including candidate handbooks, applications, and content outlines. It also states that a candidate cannot make an exam reservation until the application is complete, the examination fee is paid, and PayrollOrg has confirmed authorization. Because PF1 is not named in the supplied scheduling evidence, do not assume that FPC or CPP rules automatically apply to it.
The practical implication is straightforward: use the payroll topics in the Microsoft documentation as a study framework, but use the official PF1 handbook or exam-owner instructions for the authoritative blueprint. If the PF1 listing belongs to a different program, its measured skills and booking workflow may differ. Start by confirming the exam-owner identity, official title, current handbook, application route, and approved testing channel.
The verification task before studying
Record the exact exam title shown in your candidate account, the organization that owns it, and the URL supplied for the candidate handbook. Check whether PF1 is an internal catalogue code rather than the public exam name. This single check prevents a common preparation failure: studying a related payroll credential while following the wrong eligibility and scheduling instructions.
Who should use this guide?
PF1 preparation is most useful for people who need a structured test of payroll administration rather than a narrow software-feature check. That includes payroll coordinators, HR and finance staff supporting payroll, implementation or support personnel, and candidates moving into payroll work. The guide is also useful to experienced practitioners who need to find gaps between routine processing and underlying payroll logic.
New payroll professionals should focus on the relationships among setup data, employee transactions, calculations, deductions, reporting, and controls. A person can enter a regular payroll run correctly while still misunderstanding why an earning is taxable, how a deduction affects disposable earnings, or how a payroll-provider file reaches the general ledger. Those distinctions are likely to matter in any assessment built around operational payroll competence.
Experienced practitioners should not use familiarity with one employer’s configuration as a substitute for transferable knowledge. Microsoft Dynamics GP and Dynamics 365 documentation uses specific field names and workflows. Those examples are valuable for understanding concepts, but PF1 questions may use different terminology or a different product context. Translate each workflow into a general rule, then note the product-specific behavior separately.
Candidates whose work is limited to HR records should give extra attention to payroll consequences. The supplied Dynamics 365 documentation explains that payroll information about a worker’s position, taxes, and benefits is required before the worker can be paid. It also explains that position settings influence pay-cycle data, work cycles, salary, schedules, and earning statements. That is the bridge between HR setup and payroll processing.
A useful self-assessment
You are closer to readiness if you can explain not only what to enter, but why the entry changes an employee’s pay, tax treatment, report, or accounting result. Test yourself with questions such as: Which setup record supplies the default? What happens when a worker has multiple positions? Which amount is being limited? Which report or statement should reflect the result?
Which payroll skills deserve priority?
Prioritize the complete payroll flow: configure the organization and employee, define earnings and time rules, apply taxes and statutory deductions, process benefits and other deductions, calculate special orders, reconcile the result, and report or post it. The supplied evidence supports this sequence through Microsoft documentation covering setup, cards, transactions, inquiries and reports, utilities, routines, direct deposit, and payroll imports.
Start with data structures and dependencies. In Dynamics GP, employee cards are described as the foundation of the U.S. Payroll system, while employee classes can supply default information for new records. The setup material also separates department, position, pay, shift, workers’ compensation, local tax, unemployment tax, deduction, benefit, and employee-class configuration. Study how those records feed later transactions rather than memorizing menu paths.
Next, master earnings calculations. The evidence covers hourly, salary, piecework, commission, business expense, overtime, double time, vacation, sick, holiday, pension, tips, and other pay types. It also shows that automatic overtime can change the required transaction entry. If automatic overtime is not selected, an hourly transaction and an overtime transaction must both be entered, such as 75 hours of hourly pay and 5 hours of overtime pay in the documented example.
Then study payroll consequences. Benefits can include employer-paid insurance portions and 401(k) matching contributions. Deductions can include charitable donations, union dues, and retirement contributions. The classification of an expense as reportable wages or an accountable plan affects taxation and W-2 treatment. These are reasoning topics: identify the pay element, determine its treatment, and trace the effect into gross pay, taxes, net pay, and reporting.
Finally, study controls and integration. Payroll documentation describes reconciliation, reports for identifying transaction-entry errors, year-end routines, direct-deposit processing, and automatic checkbook updates when Bank Reconciliation is used. Business Central documentation describes importing payroll-provider transactions into the General Journal, mapping external accounts to G/L accounts, and posting the mapped journal. That flow is important if PF1 assesses payroll accounting interfaces.
The skill map to build
Create a personal map with six columns: setup, calculation, legal or policy treatment, employee impact, reporting, and control. For every topic, fill in all six where possible. For example, a benefit is not just a deduction setup item; its rate source, limit period, worker enrollment, tax status, cumulative limit, and statement treatment may all matter.
How should you study payroll setup?
Study setup as a dependency chain, not as a list of screens. Begin with the position or employee structure, then connect pay cycles and work cycles to earnings, connect tax codes to the paying legal entity, and connect benefits and deductions to the worker. This approach makes unfamiliar terminology manageable because you are following data and business consequences.
The Dynamics 365 evidence says payroll details must be added to a position before payroll can be generated for that position. The pay cycle determines calculation frequency and pay date. For non-exempt positions, the work cycle identifies work periods; some regular-rate-of-pay premiums are based on work periods rather than pay periods. Workers with more than one position should have the same work cycle across assigned positions.
Annual regular hours are another useful reasoning point. The documented example uses 2080 for a regular salaried worker and explains that the value represents 40 hours per week. The field can be used to determine salary adjustments. Do not memorize the example as a universal payroll setting; understand what the field represents and why a system needs a regular-hours basis.
The same source explains that a paying legal entity must be assigned to the position before worker tax codes can be assigned. It also describes workers’ compensation setup by compensation state and compensation code. These dependencies are excellent practice prompts: ask what must exist first, what is inherited, what is worker-specific, and what changes when the position or legal entity changes.
For Dynamics GP, organize setup into the manual’s broad parts. Setup includes department and position codes, pay codes, workers’ compensation codes, and local and unemployment tax cards. Cards include employee, tax, deduction, benefit, and beginning-balance records. Transactions include one-time or recurring batches and payroll checks. Reports and routines then provide the validation layer.
A frequent mistake is to study employee data in isolation. Employee classes can make record entry easier by grouping common payroll information, but defaults still need review for the individual worker. A default pay code, tax region, benefit, or deduction is not proof that the employee’s actual circumstances match the class. Build a habit of checking the source, effective date, and worker-specific override.
A setup exercise
Take one hypothetical worker and write the minimum information needed before payment: position, paying entity, pay cycle, work cycle where applicable, regular hours or salary basis, earning configuration, taxes, benefits, and deductions. Then mark which items are organizational defaults and which belong to the worker. This exposes missing dependencies better than rereading definitions.
How do you handle earnings, overtime, and time balances?
Separate hours, rates, pay factors, and resulting dollar values whenever you solve an earnings problem. The supplied payroll examples show that overtime may require allocating overtime hours across pay-code transactions, calculating adjusted hours, determining an average rate, and then producing transaction and overtime values. Mixing those stages is a reliable way to lose accuracy.
For a single pay code, the documented relationship is total pay divided by hours equals average pay rate. One example shows $500.00 divided by 50 as $10.00 and $540.00 divided by 45 as $12.00. Overtime value is then determined by multiplying overtime hours by the overtime pay code and multiplying that result by the average pay rate. Use this as a worked-method example, not as a universal overtime rule outside the stated system context.
When several pay codes are involved, the documentation allocates overtime by weight. It calculates total overtime hours from regular hours, overtime hours, and total regular hours for each pay code, subtracts the resulting weight from each transaction, and multiplies adjusted hours by the pay rate. The reason for the allocation is that the system does not know which pay code should have the overtime hours removed.
Shift codes introduce another layer. The documented calculation uses hours multiplied by hourly pay with the shift code to produce a dollar value. If the transaction total exceeds the overtime threshold, the overtime calculation must be handled separately. In your notes, keep shift premiums distinct from the base rate and from overtime pay so that you can trace each amount.
Time-off balances require the same discipline. The evidence describes hours per year, hours currently available, accrual methods, warnings for balances below zero, and password control when a transaction exceeds available vacation or sick time. If Human Resources is selected as the accrual type in the Attendance Setup window, some vacation and sick fields are not available in Payroll. That is a configuration dependency, not a calculation error.
Study salary and schedule generation as alternative settings. The Dynamics 365 source states that if salary is generated without earnings from schedule, a default earning code is required and the worker receives the standard position salary amount for each pay period. If earnings from schedule is selected without salary, a schedule and default earning code are required, and a day-by-day breakout can appear on the earnings statement. A schedule is also required when both selections are used.
How to practice calculations without live questions
Create original scenarios with altered facts, then show every intermediate line: ordinary hours, overtime hours, adjusted hours, rate, factor, transaction value, overtime value, and gross result. Recalculate the same scenario using a spreadsheet or calculator, but keep the written reasoning. The goal is to detect a wrong assumption, not merely to obtain a final number.
What should you know about taxes, deductions, and benefits?
Learn taxability and reporting as separate decisions. A payroll element may affect gross wages, taxable wages, disposable earnings, a W-2 box, or none of these in the same way. The supplied documentation repeatedly links setup choices to tax calculations and year-end reporting, so practice tracing an element through the paycheck and the statement rather than labeling it simply taxable or nontaxable.
The Dynamics GP evidence distinguishes accountable and nonaccountable plans. If a business expense is marked Report as Wages, it is included in gross wages on the W-2 and treated as a nonaccountable plan. If it is not marked, the pay is not included in gross wages on the W-2 and is treated as an accountable plan. The documentation also states that nonaccountable plans are reported as wages and subject to taxes, while accountable plans are not subject to taxes or reported on the W-2.
Tips require careful separation of calculation and withholding. The supplied evidence states that taxes are calculated on tips wages and reported on the employee’s W-2, but are not withheld from the employee’s paycheck in the described treatment. Do not generalize that statement to every payroll jurisdiction or configuration; use the applicable official rules and product documentation for the scenario presented.
Benefits can contain both employee and employer components. The evidence gives insurance premiums and 401(k) matching contributions as examples and describes an Employer Maximum Match field for the maximum employer contribution. In Dynamics 365, selecting Benefit can update the worker’s deduction amount and basis when benefit rates are updated. That means a rate change may require review of each enrolled worker rather than assumption that one change is sufficient.
Limits and effective dates deserve their own notes. The Dynamics 365 material describes limit periods, limit end dates, cumulative deduction or contribution limits, and date-effective tax-code parameters. It states that the first change made during a day creates a new parameter version, while a later change on the same day overwrites the previous change without creating another version. When studying, always ask which version is effective for the payroll date.
Legally required deductions and voluntary deductions are not interchangeable in every calculation. The evidence identifies federal, state, or local income tax, Social Security or Medicare tax, state unemployment or disability tax, and mandated state employee retirement payments as deductions required by law. It also states that voluntary deductions such as insurance premiums, union dues, and retirement contributions are generally not subtracted when disposable earnings are calculated, although state law may require a different treatment for health premiums.
Do not treat the supplied examples as current legal advice. The Microsoft page directs readers to IRS rules for applicable-year labels and current rates. For an exam question, apply the rule and facts given. For real payroll work, confirm current federal, state, and local requirements before processing pay.
The tax-treatment worksheet
For each earning, benefit, expense, or deduction, record five answers: Is it included in gross wages? Is it subject to the relevant tax? Is it included in disposable earnings? Is it reported on a year-end statement? Does a limit, rate source, or effective date change the result? This worksheet turns vague tax familiarity into a repeatable decision process.
How should you approach garnishments and withholding orders?
Treat garnishments as an ordered calculation with priority, disposable earnings, statutory limits, minimum-wage protection, and deduction sequencing. Do not begin with the amount demanded in an order and assume that amount can be withheld. The supplied Dynamics GP material shows that the system may have to compare federal and state limits, account for priority orders, and take the smallest permitted amount.
For ordinary creditor garnishments, the documented CCPA rule uses the lesser of 25% of weekly disposable earnings or the amount by which weekly disposable earnings exceed 30 times the federal minimum hourly wage then in effect. The source also states that the applicable multiplier changes with the pay period. Because minimum-wage values and legal rules can change, verify the current rule for real payroll and follow the exam scenario’s stated assumptions.
Child-support withholding has separate limits and priority considerations. The supplied evidence states that the maximum for an employee supporting another spouse and/or children is 50% of disposable earnings, and it identifies a different maximum when the employee is not supporting another spouse and/or children. It also notes higher limits when support payments are at least 12 weeks late. Do not carry a child-support rule into a creditor-garnishment question.
Priority can change the result before a later order is considered. The evidence says that a tax levy, bankruptcy order, or other priority order must be taken into account when determining whether the CCPA maximum has been reached. It also explains that if a priority order constitutes at least 25% of disposable wages, no amount may be withheld for a creditor garnishment in the described situation.
Separate the order amount, available amount, maximum amount, and amount actually withheld. One supplied example describes a $200 maximum deduction code applied across three garnishments; the calculation reduces later garnishments after earlier amounts have used the available maximum. Another example states that when separate state and federal maximums exist, Payroll applies the maximum that deducts the smallest amount from the employee’s pay.
Finally, study deduction sequence. A company-level deduction sequence specifies the order in which deductions are taken from wages. A new deduction may be placed before an existing credit deduction, but the resulting withholding still has to respect the applicable minimum-wage and maximum rules. In a practice problem, write the sequence first, calculate each candidate deduction, apply limits, and then reconcile the total.
The garnishment checklist
Before calculating, identify the order type, pay frequency, disposable-earnings definition, priority orders, required deductions, voluntary deductions, statutory maximums, minimum-wage rule, previous amounts taken, and deduction sequence. If any fact is missing, do not silently invent it. Mark the missing assumption and identify the official rule or handbook that should supply it.
What payroll reporting and accounting controls matter?
A payroll result is not complete when the paycheck is calculated. You should be able to explain how the organization checks employee and pay activity, corrects errors, completes periodic routines, prepares year-end information, and transfers payroll-related financial data into the general ledger. These controls distinguish a calculation exercise from operational payroll competence.
Dynamics GP documentation describes current and historical employee information, pay activity, payroll reports for identifying transaction-entry errors, reconciliation between detail and summary records, and customized checklists for month-end, quarter-end, and year-end tasks. It also describes beginning balances used to keep monthly, quarterly, and yearly amounts correct and to support W-2 processing when Payroll begins after the start of a calendar year.
W-2 setup is a recurring study theme. The evidence refers to federal and state tax identification numbers, W-2 box numbers and labels, benefits and deductions that may be printed in specific boxes, and the treatment of reportable business expenses. When practicing, connect the source transaction to the statement field. A correct paycheck can still produce an incorrect year-end form if reporting configuration is wrong.
Business Central presents a different but transferable control flow. The payroll provider’s file is imported into the General Journal, external accounts are mapped to relevant G/L accounts, and the resulting journal lines are edited or posted. The mapping is remembered for recurring records. The documentation also says that a payroll-import extension must be installed and enabled. The general lesson is to validate mapping before posting, not treat import as automatic accounting approval.
Direct deposit and bank reconciliation add operational consequences. The Dynamics GP manual describes creating employee direct-deposit cards and an ACH file for transferring funds. It also states that when Bank Reconciliation is used, the checkbook is automatically updated when Payroll transactions are posted. Study these as downstream effects that require reconciliation, not as evidence that every payroll product uses the same process.
A control-oriented review
For every practice payroll, perform three reviews: employee-level review of earnings and deductions, payroll-level review of totals and exceptions, and accounting-level review of posting or import results. Add a fourth review for year-end or statutory reporting when the scenario includes W-2 information, tax identifiers, or reportable benefits.
Which study materials should you trust?
Use the official PF1 candidate handbook and content outline for scope, eligibility, format, and current administrative rules. Use official payroll documentation to understand the concepts and system behavior. Use your own notes and original practice scenarios to rehearse decisions. Do not use unauthorized question banks, leaked content, or memorized answers as a substitute for understanding.
The supplied Microsoft Dynamics GP manual is broad enough to serve as a concept index. Its sections cover setup, codes, employee classes, tax cards, employee cards, deduction and benefit cards, beginning balances, transactions, reports, utilities, routines, direct deposit, and payroll integration. Read selectively: start with topics named in the PF1 outline once you obtain it, then use the relevant Microsoft section to clarify mechanics.
The Dynamics 365 worker-payroll article is useful for position-based payroll, payroll periods, annual regular hours, salary and schedule generation, worker tax codes, benefits, garnishments, tax-code versions, calculation priority, and limit periods. It is especially helpful for understanding how effective dates and worker position data affect payroll.
The Business Central import article is narrower. Use it for the payroll-provider-to-general-ledger workflow: import, map, review, and post. Do not let that article lead you into assuming that PF1 is a Business Central certification or that a particular extension is part of the exam. Its value here is the accounting-control concept.
The Pearson VUE pages are administrative sources, not study guides. The login directory explains that each exam program has its own login route. The PayrollOrg page provides application, authorization, scheduling, identification, payment, accommodation, and contact information for the programs it names. Check whether PF1 appears in the relevant program account before relying on those instructions.
A note-taking format that works
Use three labels in your notes: official rule, product behavior, and personal recommendation. For example, “application must be authorized before reservation” belongs to official scheduling evidence for the named PayrollOrg programs; “review a default employee-class entry” is a practical recommendation; “automatic overtime requires different transaction entry when unmarked” is product behavior documented for Dynamics GP. Keeping these labels separate prevents overclaiming.
What is a practical PF1 study roadmap?
Use a staged roadmap that moves from scope confirmation to concepts, calculations, controls, and final administration. The schedule length should match your background and the official exam date; the important decision is sequencing. Do not begin with random practice questions. First establish the blueprint, then build a payroll model, then test each part under time and accuracy pressure without relying on live or recalled exam content.
Stage one is scope and baseline. Obtain the PF1 handbook or current official outline, list every domain, and mark each as strong, familiar, or unknown. Confirm whether PF1 is the public exam name for the catalogue entry. Take a diagnostic using original questions you write from the outline. Record why each answer is correct, not just whether it was correct.
Stage two is payroll architecture. Study employee and position records, pay cycles, work cycles, legal entities, annual regular hours, earning codes, tax codes, benefits, deductions, and employee classes. Draw the dependencies from setup to pay statement. At the end of this stage, explain what must be configured before a worker can be paid and which values are defaults versus worker-specific.
Stage three is calculation practice. Work through ordinary earnings, shift pay, overtime, salary or schedule generation, tips, business expenses, time-off accruals, and benefit or deduction limits. Show intermediate steps and label each amount. Repeat any scenario where you reached the right total for the wrong reason. Accuracy without a defensible method is fragile.
Stage four is compliance and withholding logic. Practice tax treatment, W-2 reporting, disposable earnings, child support, creditor garnishments, tax levies, bankruptcy priorities, minimum-wage protection, deduction sequencing, and state-versus-federal maximums. For each scenario, identify the rule before calculating. If the scenario requires a current rate or legal threshold that is not supplied, flag it for official verification instead of filling in a remembered value.
Stage five is operations and controls. Review transactions, recurring batches, reconciliation, reports, beginning balances, year-end routines, direct deposit, and payroll imports. Build a control checklist that asks whether totals agree, exceptions are investigated, mappings are correct, and reporting fields are complete. This stage is particularly important for candidates whose daily work focuses only on entering payroll data.
Stage six is examination readiness. Use mixed original practice sets that force you to switch between setup, calculations, withholding, reporting, and controls. Review error patterns by topic. Prepare a one-page rule sheet containing formulas, definitions, dependencies, and “check before answering” prompts, while remembering that the official handbook—not your sheet—controls the exam rules.
Your final administrative step is separate from studying. Confirm the application status, authorization, payment record, legal name, identification requirements, approved delivery options, accommodation process, and appointment availability through the exam owner or the applicable testing-program account. The supplied PayrollOrg scheduling page says appointment date and time options vary with selected test-center availability and that payment is not accepted at the local test center. Confirm PF1-specific treatment before booking.
How to decide whether to book
Book only after you can explain your weak areas and have a realistic plan to close them. A high result on familiar payroll calculations is not enough if you cannot handle setup dependencies, withholding priority, reporting treatment, or accounting controls. If the official PF1 outline is unavailable, pause the booking decision until the exam owner confirms the scope and administrative rules.
Which mistakes most often undermine preparation?
The most damaging mistakes are not usually arithmetic slips; they are scope errors. Candidates study a related certification, memorize product navigation, apply a general payroll rule to a different jurisdiction, or calculate an order amount without checking priority and limits. Correct these by tying every answer to the stated facts, the applicable rule, and the payroll stage being tested.
Do not infer PF1 requirements from its catalogue code. The supplied research does not establish PF1’s prerequisites, blueprint weights, score, question count, duration, languages, retirement status, or exact delivery method. Publishing or planning around any of those details without the PF1 source would create avoidable risk.
Do not confuse official requirements with recommendations. An application and authorization requirement is administrative evidence for the named PayrollOrg programs. Creating a dependency diagram is a study recommendation. Reviewing a Dynamics GP employee card is product documentation. Label those categories so a convenient preparation tactic does not become an invented exam rule.
Do not memorize isolated percentages or dollar examples. The payroll material includes specific examples of overtime factors, garnishment limits, exempt amounts, wage limits, and contribution caps, but some are tied to a particular scenario, product behavior, or legal assumption. Reproduce a number only when the question supplies or officially supports the exact context.
Do not skip effective dates and cumulative totals. Tax-code versions, benefit rates, limit periods, beginning balances, previous garnishment amounts, and year-to-date taxable wages can change an otherwise correct calculation. Make dates, prior amounts, and period boundaries visible in your working rather than leaving them in your head.
Do not use exam dumps or leaked questions. They are not a reliable way to learn payroll reasoning, may be unauthorized, and cannot guarantee a passing result. Build original scenarios from official topics and verify current legal or administrative information through the responsible organization.
Do not book first and investigate later. The supplied Pearson VUE material states that candidates cannot make a reservation until the application, payment, and authorization steps are complete for the described PayrollOrg programs. It also requires the full legal name to match the primary government ID. Check the PF1-specific process before making a nonrefundable or difficult-to-change commitment.
The correction loop
When you miss a practice item, classify the error as scope, definition, setup dependency, calculation, tax treatment, priority, reporting, or reading. Rewrite the rule in your own words, create a new scenario with different facts, and solve it without looking at the original. This loop is more valuable than repeatedly answering the same item.
What should you do next?
Your next action is to verify PF1’s public exam identity and obtain its current official outline or handbook. Then build a gap list against the payroll domains supported by the supplied research: setup, earnings, taxes, deductions, benefits, garnishments, reports, controls, and integration. Only after that should you choose study materials and make a scheduling decision.
Use the Microsoft sources to deepen technical understanding, especially where a payroll result depends on setup or sequence. Read the Dynamics GP material for employee records, pay codes, overtime, deductions, benefits, tax cards, garnishments, reporting, reconciliation, and routines. Read the Dynamics 365 material for position payroll, tax-code effectiveness, benefit rates, limits, and calculation priority. Read the Business Central material for import and posting controls.
Use the Pearson VUE PayrollOrg page to locate the correct program route, then confirm whether PF1 is handled there. The page provides a login path, application and handbook links for the programs it names, and contact information for PayrollOrg. If the PF1 listing does not appear, contact the exam owner rather than guessing which account or handbook applies.
Before booking, prepare a short checklist: exact public exam name, owner, current outline, eligibility, application status, authorization, payment status, identification name, accommodation needs, delivery option, appointment availability, rescheduling terms, and cancellation terms. Only some of these are supported by the supplied PayrollOrg evidence for named programs; the rest must be confirmed for PF1.
After booking, keep studying by error category rather than expanding your materials endlessly. Revisit the weakest domain, solve a fresh scenario, check the result against the official rule, and update your one-page decision sheet. This keeps preparation focused on transferable payroll judgment instead of unverified exam folklore.
Conclusion
PF1 preparation should end with two confirmed decisions: you know what the official PF1 assessment covers, and you can follow a payroll transaction from setup through calculation, withholding, reporting, and control. The supplied evidence supports a strong payroll-focused study plan, but it does not establish PF1-specific administrative facts. Verify those facts with the exam owner, use official documentation for technical reasoning, and measure readiness by your ability to explain each result rather than recall isolated answers.