Guides for HR and Finance work in the system
Each guide explains one topic with the rules that matter, worked examples, common mistakes and a free practice level.
Foundations
Skills every user needs: search, business processes and reports.
Find your way
Search, core objects and the worker profile.
Search like a pro
Most tasks open faster from the search box than from any menu. A few rules make search much more precise: short word starts, prefixes and numbers only for IDs.
Core objects
Almost every HR task touches the same building blocks. Once you see how they link, screens and reports make more sense, and you know which prefix to use.
Worker profile and actions
The worker profile is a starting point for most HR tasks. Related Actions put the right tasks next to the worker, and Worker History shows everything that happened before.
Business processes
Inbox, approvals, status and effective dates.
Inbox and approvals
Approvals look simple until a request is almost right. Knowing exactly what Send Back and Deny do saves rework and awkward follow ups.
Process status and history
“Where is my request?” is one of the most common questions. The process history answers it in seconds, and the status tells you whether to cancel, rescind or correct.
Effective dates
The effective date is the most important field on many changes. It decides when the data switches, what reports show and whether later changes fit the timeline.
Reports basics
Report types, filters and prompts.
Report types
Picking the report type first saves you from rebuilding later. Each type has clear limits, and most real reports are advanced or matrix.
Filters and prompts
Most “wrong” reports are filter logic problems. Reading a filter one condition at a time tells you exactly which rows should appear.
HR
Core HR, pay and time, recruiting, benefits, security and data.
I already work with it
Core HR moves
Hires, job changes and terminations.
Hire and onboarding
A hire looks like a form with a few fields. Those fields decide pay, benefits eligibility and reports for years, so they are worth getting right.
Job and org changes
Many changes can be forced through the wrong task. They still “work”, but history, approvals and reports end up wrong. The fix is to name the one thing that changes.
Terminations
Terminations cost real money when a date is one day off. The two date fields mean different things, and the reason feeds turnover reports.
Pay and time
Compensation, time off, leave and overtime.
Compensation
Compensation questions come with numbers. Knowing the plan types and three simple formulas covers most of what managers ask.
Time off and leave
Absence questions come down to three things: is it time off or a leave, what is the balance, and how many days does this request use.
Time tracking and overtime
Hourly time feeds payroll directly. A wrong total or a late approval shows up on someone’s paycheck.
Talent, benefits and security
Recruiting, benefit events, access and data checks.
Recruiting pipeline
Recruiting is a series of small decisions: move forward or decline. Knowing the usual order of stages keeps candidates moving and reports honest.
Benefits events
Most benefit questions are timing questions. Is this open enrollment, a life event or a passive event, and is the window still open?
Security basics
Access tickets are some of the most common in HRIS. They get easier once you separate the two questions: which group, and which policy.
HR data checks
Bad data rarely announces itself. It shows up later as a failed approval, a wrong paycheck or a report nobody trusts. Audit reports catch it early.
I want to get into the field
Start in HR tech
The lifecycle, US basics and HRIS careers.
The employee lifecycle
HR systems are built around one simple story: someone joins, works, changes jobs and leaves. Each step is a process with its own data.
US HR basics
A handful of forms and classifications come up every day in US HR. Knowing them makes system fields and employee questions easy to place.
HRIS careers
There is no single path into HR technology. Most people come from HR operations, recruiting or payroll and move toward data and systems.
Finance
Worktags, journals, close, procure to pay, expenses, receivables and cash.
I already work with it
Financial data model
Worktags, journals and period close.
Worktags
Instead of one long account code, finance systems use a ledger account plus worktags. Each worktag answers one question about the transaction.
Journals
A journal posts only when debits equal credits. Most “it won’t post” problems are totals, missing worktags or a closed period.
Period close
Month end questions often come down to one field: the ledger period status. It explains why a journal is rejected and why a cost landed in next month.
Procure to pay
Requisitions, three-way match and supplier payments.
Procure to pay
Every purchase leaves a trail of documents. When one is missing or wrong, payment stops later, so knowing the order of steps prevents most problems.
Three-way match
When the purchase order, the receipt and the invoice agree, the invoice pays. When they do not, a match exception holds it until someone fixes the right document.
Supplier invoices and payments
Suppliers ask two questions: when will I be paid, and how much. Payment terms and statuses answer both.
Expenses, customers and cash
Expense reports, receivables and bank reconciliation.
Expense reports
Expense reports go back and forth when receipts are missing, bills are not itemized or limits are ignored. A few rules prevent most of it.
Customer invoices and aging
Receivables are money customers owe. The aging report tells collectors where to start, and payment application keeps balances right.
Bank reconciliation
The bank statement and the books rarely agree on the last day of the month. A reconciliation explains every difference.
I want to get into the field
Start in finance systems
Account types, debits and credits, finance careers.
Account types
Every ledger account belongs to one of five types. Once you can sort accounts into them, trial balances and reports start to make sense.
Debits and credits
Debit means left, credit means right. Two short rules and a few examples are enough to read most journal entries.
Finance systems careers
Finance systems roles sit between accounting and technology. Many people start in accounts payable or receivable and move toward the system side.
Questions and answers
Where should I start?
Start with Foundations: search, business processes and reports. Then pick HR or Finance.
I am not working in the field yet. Where do I start?
Open the starter path of your track: Start in HR tech or Start in finance systems. They explain the basics behind the system.
Are the examples real?
The people, companies and numbers are made up. The rules and task names follow common setups. Your company’s setup may differ.