Software and accounting guide

Rippling: employee records, payroll and accounting handoffs

Rippling brings employee information together with payroll and other workforce tools. Time, benefits and payroll records depend on which modules your business has purchased and configured.

By Sam Yang · Updated 2026-10-09

How Rippling supports the workflow

Who this guide is for: Owners, HR and payroll staff, with office or finance teams checking labor costs and payroll payments.

Everyday uses

Keep employee information and changes organized.
Run and review payroll in the enabled payroll product.
Coordinate payroll with the benefits and workforce tools the business uses.

How it connects to accounting: Accounting needs payroll earnings and employer costs for the dates employees worked, plus the separate money taken from the bank for payroll. The payment date does not tell you when all the work was done. Payroll totals alone do not show the cost assigned to each job.

How to connect it and get the records you need

A built-in connection transfers the records its vendor supports. An API lets software read or exchange specific records directly. Browser automation may use the screens and reports your role can access when a direct connection leaves a gap. Its coverage and reliability need checking for the specific workflow. Start with the options available in your account, then check what actually reaches your books.

Documented API access

Rippling has an official developer portal. Before designing an automated download, verify that the account permits an API request for the exact payroll or time records you need.

Native payroll and time reports

Use the available payroll summary, register and relevant time detail. A payroll register lists the payroll’s earnings, deductions and other components; compare its own period with the books.

Browser assistance

Collect an authorized report or inspect a pay run when the existing connection does not supply the detail. Keep its payroll-run ID and work dates alongside payment dates.

Start here: Separate the period employees worked from the date payroll was paid before comparing labor cost with the monthly accounts.

Integration options and their limits

An API gives software direct access to supported records. Native reports are the files and reports available inside the product. Browser automation collects through the screens you can access. Choose the route that supplies the missing records, then check that it covers the accounts and dates you need. Reports may contain filters or omit rows. Browser work depends on permitted account access and can fail when screens change. Check record IDs, counts and dates whichever route you use.

Supported API

What it supplies: Rippling maintains an official developer portal. This investigation did not verify an API request that returns the required account’s full original payroll register.
What to check first: The required API request, permissions, companies, correction history and complete register records remain unverified. A developer portal alone does not prove the required data is available.

Choose it when: An existing authorized connection has demonstrated that it supplies the exact payroll register and funding records.

Native export

What it supplies: Our October 2026 collection observations distinguish the original Payroll Register from comparison exports and record whether each run’s file arrived.
What to check first: A Download button does not prove the file arrived. Report menus and access permissions depend on the account.

Choose it when: You need the original register for an identified payroll run, with a record of which run and settings were selected.

Permitted browser

What it supplies: Our saved collection routines check the company and payroll run, keep the complete displayed records, and report incomplete exports. The observed register collector selects by check date or by a work period that overlaps the requested dates.
What to check first: A complete payroll list does not prove that card spending, reimbursements or bank records were collected. Missing or stale controls still leave the collection incomplete.

Choose it when: The required original report is available in the authorized browser but not through the existing verified connection.

What to automate and what an accountant should review

Good work for automation

Check entity and run IDs, keep correction credits, and collect the selected original report with a clear record of any incomplete download.

Keep a person on these decisions

Review when unpaid earned wages should be recorded, how labor maps to jobs, which employer costs are covered and how to account for corrections or reimbursements.

Lessons from accounting and operations

Known problems and what to check

Does the payroll total show work done or money paid?

For job costs, use the dates the work was done. For cash planning, follow the amounts taken for payroll and any correction credits. A run marked completed or approved does not answer both questions.

Evidence basis: Saved payroll export, funding and rendered-spend observations. Current roles and report controls must be verified. Some checks are Level’s own review requirements, rather than observed vendor behavior.

Check which reports or API requests the account permits and whether the connection supplies the required records. An integration logo does not establish this.

The run has a future check date

Keep approval and check dates separately. Find the funding and bank records before saying the cash was paid.

A correction changes the required funding

Retain credits and negative components alongside new debits. Adding only positive lines overstates the cash requirement.

Start with an API, connection or built-in report that your account offers and you have confirmed. An authorized browser session may collect records those routes leave out; test its coverage for the workflow. Still check the totals against the books and confirm that all relevant costs are included.

Pitfalls and when to pause

Approval, earned labor and paid funding are different events. Payroll and card grids need separate coverage checks. Funding credits must remain explicit.

How a plausible answer can go wrong

A full payroll register does not complete card spend, and an approved correction does not prove the bank debit occurred. Visible card rows or a row showing two dollar values also cannot certify the whole spend total.

Pause if you cannot confirm the account, permission, reporting dates or completeness of the records. Return the missing evidence for review. Do not fill the gap with an invented record, a balancing entry or an assumed zero.

When the result does not make sense

Completed payroll does not equal the bank debit

Check: Check when funding was taken, the check date, each correction debit or credit, and the separate amounts taken for payroll funding.

Resolve the question: Explain how the payroll run leads to its funding amounts. Leave bank arrival unconfirmed until bank records support it.

Export has totals but no required employer cost detail

Check: Verify whether a comparison export was selected instead of the Payroll Register, then inspect supporting journal detail.

Resolve the question: Collect the original register and supporting reports. Do not treat missing employer costs as zero.

A reimbursement is absent from Billing Payments

Check: Check the reimbursement batch and employee expense records. Our saved observations found these separate from Billing Payments.

Resolve the question: Keep batch and expense IDs, then investigate the funding separately. Absence from Billing Payments does not prove nonpayment.

Collect the records and check nothing is missing

Payroll register: Keep the company, run ID, work dates and check date. A comparison export is a different report and does not replace the payroll register.
Funding and journal detail: Keep correction history and employer-paid taxes, benefits and other costs. Use supporting reports for missing register fields instead of assuming zero.
Card spend detail: Keep each original transaction ID and the amount shown as Total. Purchase date and Finalized on can differ. If a screen shows two unclear dollar amounts, it does not establish the total spending.

Select the correct company and payroll run. Keep work dates and check dates separately. Collect the complete payroll register, funding amounts and correction credits, including rows beyond the visible table. Collect card-spending records separately.

Step-by-step collection notes

Dated saved collection procedure reviewed October 6, 2026. Verify the current account, interface, permission and available reports. Menu names may differ.

Verify company and payroll entity, then open Payroll > Overview > Completed.
Retain run links, entity, service-period dates, check date and status. Completed can include an approved run with a future check date.
Open the run Payroll Summary > More Options > Payroll register.
Select Download in the register panel. In the second dialog choose CSV, deselect PDF if unnecessary, leave grouping None, then Download report.
Retain the original file and separate funding, employee and tax evidence. Export pay run comparison is a different control and does not replace the register.
If a correction preview lacks the register control, retain complete visible evidence and explicitly mark missing export coverage.

Checks before using the records

Select the entity, run, earned period and check date explicitly.
Retain complete register, funding and credit sets of records beyond the visible grid.
Collect card activity separately and record which transactions and dates were included.

Fictional collection example

A fictional payroll register is approved before the bank payment arrives, and a correction credit reduces the amount taken for payroll. Keep approval, work dates, gross funding and the credit separate. Booking the net bank withdrawal as another payroll expense can duplicate costs already recorded in the payroll journal and obscure amounts owed.

Invented teaching scenario, not a customer result or a reproduced vendor defect.

Capture the setup with the evidence

Company, legal entity or account, report name, period, cash or accrual accounting basis, currency and timezone.
Selected filters, status, page count, original record identifiers, record counts and totals used to check completeness.
Collection time, source route and authorized role. Record browser and automation versions when using a browser.
Original files and exceptions. Keep credentials, customer identifiers and financial artifacts private.

A browser version helps reproduce an interface issue. It does not validate the financial conclusion.

Practical workflows

Practical checks you can follow

Does the Rippling total show work done, payroll approved or money paid?

Rippling payroll records show what employees were paid. To use them for job costs or cash planning, keep three dates separate: when the work was done, when payroll was processed or paid, and when funding moved through the bank. Keep correction credits alongside new debits. A payroll register does not automatically include card spending or reimbursements.

Compare labor costs with the money taken for payroll

Identify the company, payroll run, dates employees worked, check date and run status. Include relevant off-cycle runs (outside the normal schedule) and correction runs.
Collect the original Payroll Register, accounting journal, employer-cost detail and funding records separately. The register lists the run’s pay and other payroll components; the journal shows entries for the books. A comparison report is not the register.
Assign labor costs to the period worked using actual time and service records. Do not move every cost to the check date or assume work after the last run cost nothing.
Calculate net funding using each debit or credit’s sign, so a correction credit reduces the amount funded. Find the corresponding bank transactions separately.

Bring to the review: One view of labor costs for the dates worked and another of money taken to fund payroll, connected by payroll run IDs.

Then decide: Resolve missing dates, employer costs or correction credits before using the figures for job margins or payroll funding.

Investigate reimbursements without double-booking cash

First decide whether you are checking the purchase expense, reimbursement approval or bank funding. These are different events.
Keep the exact reimbursement batch with its company, batch ID, debit and payout dates, and total including credits. Obtain original receipts when available.
Check the employee’s expense detail for actual purchase or trip dates. A mileage claim does not necessarily have a supplier invoice.
Connect the batch funding to the bank transaction already recorded in the books. Keep employee items without support separate.

Bring to the review: Expense detail dated to the purchase or trip, connected to the separately supported funding batch.

Then decide: Check existing accounting entries before proposing an expense entry. Do not record the same bank movement twice.

Worked example

Fictional correction credit changes funding

All records and amounts below are fictional teaching inputs. CSV files are spreadsheet-compatible text files. This example demonstrates the calculation, not a customer outcome or a reproduced software defect.

Positive funding is 2500, but the signed requirement is 2500 - 400 = 2100. The 400 credit changes funding, not necessarily current-period earned labor. This simplified fixture is a signed funding bridge, not a complete payroll journal.

What the CSV columns mean

component: new_debit or correction_credit
run_id: fictional run identity
signed_funding: USD debit requirement, credits negative

New debit: 2500 USD; Positive funding component before the credit.
Signed funding requirement: 2100 USD; Required funding after this fixture's correction credit.
Overstatement if credit omitted: 400 USD; Difference caused by summing only positive components.

Inspect rippling-funding.csv

run_id,component,signed_funding
run_demo,new_debit,2500
run_demo,correction_credit,-400

Download this CSV

Next decision: Seek the identified run funding and actual bank occurrence. Collect separate service-period costs before calculating job margin.

Expected results and calculation checks Download the reproduction code

Run the example locally

Save the CSV files, expected-results.json and reproduce.mjs in one folder. With Node.js installed, run the command below. It calculates the checks from the CSV bytes and rejects a changed input or expected result.

node reproduce.mjs expected-results.json

No software login, customer records or API key is required.

AI prompt for collecting records without changing them

Replace the bracketed scope before use. This prompt collects evidence; it does not permit edits, approvals or accounting execution. Requesting an emailed report is a separate account action and requires explicit authorization.

Collect read-only evidence for Rippling to answer [financial question]. Confirm [company], [account/entity], [period], [basis], [currency] and [allowed reports]. Select the correct entity, payroll run and service/check dates. Retain the complete register, funding and credits. Check all rows, including those beyond the visible grid. Collect card evidence separately. Retain original files, complete record IDs, counts, filters, collection timestamp and exceptions. Approval, earned labor and paid funding are different events. Payroll and card grids need separate coverage checks. Funding credits must remain explicit. Stop if the source or scope is uncertain. Do not post, match, reconnect, delete or change settings. Return the evidence for financial review; do not claim the books are correct. Do not approve, submit payroll, pay, transfer, refund, send messages, invite users or accept terms. Stop at any login, MFA or credential prompt and hand back to the account owner. Store files only in [approved private location]. Do not paste customer artifacts into public tools. Use only preauthorized collection actions. Request an emailed report only when its delivery is explicitly authorized; otherwise ask the account owner to supply the file.

Next decision

What can you decide from these records?

Give the owner separate labor-cost and payroll-funding views. Name unresolved credits and missing report totals. A status label does not prove money moved through the bank.

Compare the same records, accounts and reporting dates. List costs or payments you cannot yet verify before using the result for pricing, cash planning or month-end review.

Read the next finance check →

References behind these workflows

Each product reference supports only the features and limits described beside that source. Level's checks and fictional calculations are separate from what the vendor documents.

Read the product and workflow references with their scopes and review dates Explore the financial diagnostic examples

Sources and scope

Base product-reference scopes were reviewed 2026-10-06. The collection procedure retains its own review date in the dated sequence above. Individual source rechecks are dated with their citations. Operator decision guidance was reviewed 2026-10-09. The references below support their stated product scope, not every observed interface detail. It is not a vendor capability certification, a measured customer result or an independently reconciled account. Verify current features and what your plan includes in the account you use.

Rippling API access and authorization reference
Product reference: API access reference, not payroll or card coverage certification.
Rippling workforce product overview
Product reference: Employee information, payroll, benefits and workforce product families; no specific API endpoint or module entitlement established. Reviewed 2026-10-08.
Rippling developer portal
Product reference: Official portal existence only. Specific payroll endpoint and permissions were not verified. Reviewed 2026-10-07.
Workflow reference: Official portal existence only. Specific payroll endpoint and permissions were not verified. Reviewed 2026-10-07.

Content revision history