Review Rippling payroll runs
Use the Payroll runs page to review regular and off-cycle runs discovered during Rippling synchronization. The page shows payroll dates, status, approval and payment times, and the accrual and settlement journal status for each run.
Review payroll runs
- Open Menu > Accounting > Settings > Rippling Integration.
- Select Payroll runs.
- Use Search payroll runs and the check-date filter to narrow the list.
- Review Pay Run, Type, Status, Check date, Debit date, Approved, Paid, Accrual journal entry, Settlement journal entry, Journal processing, Pay period start, Pay period end, First discovered, Last synchronization, and Last changed as needed.
- To choose and order visible columns, open column personalization. Changes to the columns are saved automatically.
The journal columns use these statuses:
- Pending: The journal is applicable but has not been attempted.
- Processing: Journal creation is in progress.
- Created: Journal creation completed. Select the journal number to open the journal entry.
- A failure status that requires attention indicates that recovery is required and an automatic retry is not available.
- Ready to retry: Recovery released the journal for another attempt.
- Awaiting payment: The settlement journal is not applicable until the approved payroll run is paid.
Request payroll processing
- Review the time shown after Last synchronized. If synchronization has never completed, the page displays Not synchronized yet.
- Select Sync and create journals.
QuickStart queues synchronization and journal creation. If another payroll process is already queued or running, it does not start a second one. Refresh the list after processing completes to review newly discovered or changed runs and journal links.
While processing is active, the page shows that synchronization is queued or running. If all retry attempts fail, it shows Last synchronization failed with a timestamp. Authorized Rippling administrators also receive Rippling payroll synchronization failed, which opens the Rippling request log. A later successful synchronization replaces the failure status and resolves the active failure notification.