Apps: SolaHR + SolaCount. Outcome: review and approve a payroll run, record that salaries were actually paid, and verify that both journals reached SolaCount and match the run.
#The situation
Palm Grove Furnishings LLC (base currency AED) runs October 2026 payroll. HR officer Sara Mansour prepares the run, Mona Fares approves it, and accountant Layla Haddad checks SolaCount. This practice case has one employee, Yousef Nasser, and these assumptions:
| Component | AED |
|---|---|
| Basic salary | 8,000 |
| Housing allowance | 2,500 |
| Transport allowance | 500 |
| Gross pay | 11,000 |
| Recorded deduction (one agreed deduction) | 200 |
| Net pay | 10,800 |
There is no overtime, advance, unpaid leave, employee tax or social-security contribution and no employer contribution. Statutory rules (income tax, pension or social insurance, end-of-service, wage-protection filings) depend on country, contract and the settings in your SolaHR organization. These figures are a teaching example, not a legal payroll formula and not advice for any jurisdiction.
#Desired result
HR shows the run as Paid; SolaCount contains two posted journals dated correctly; salary expense is 11,000, the bank has decreased by 10,800, the net-salary payable is back to zero, and HR's reconciliation shows Matches.
#Before you start
- The employee, effective salary record, employment dates and payroll currency are correct, and attendance and other payroll inputs are resolved.
- Sara needs payroll view/create rights. Mona needs payroll approval rights and, under the default setting, must be a different user from the person who submitted the run. Payslip generation has its own permission.
- An administrator has completed Payroll & Compensation → Payroll Settings → Accounting integration (SolaCount): SolaCount organization and credentials (the Paste provisioning output box fills the connection fields), the Account mapping, Amount decimals (must match SolaCount), and Send events dated from (older events are marked skipped and never sent). Click Save integration settings, Test connection (look for Last test passed), tick Send accounting events to SolaCount, and save.
- The integration must be included in the workspace's plan. When plan limits are enforced and the integration is not included, SolaHR does not queue any accounting event.
- In SolaCount the accounting period for the dates must be open; the account mapping must name accounts that exist there.
- Mapping tips for this case: map Salary expense, Allowances expense, Penalties and other deductions, Net salaries payable and Cash or bank. Unmapped Allowances expense, Overtime expense, Employer insurance expense and Penalties and other deductions fall back to the Salary expense account, so their lines merge into one line there. Any other unmapped account blocks delivery.
#Workflow overview
| Step | App | Who owns it |
|---|---|---|
| Calculate, review, submit, approve, lock | SolaHR | Sara, then Mona |
| Pay the bank/cash transfer | Outside both apps | Palm Grove finance |
| Record "paid" | SolaHR | Authorized HR user |
| Queue and send two journals | SolaHR, automatic after Paid | Delivery runs every five minutes |
| Receive and post journals | SolaCount | Automatic; Layla verifies |
Approval freezes the figures but does not queue accounting. The two events are created at the moment the run becomes Paid (the posting and payment journals are queued together). Nothing else in a normal run creates them. SolaCount has no second payroll approval: the journal is created already posted.
#Exact steps
- Sara opens Payroll & Compensation → Payroll Runs and selects year 2026 and month October. For a past month with no run, click Generate draft for October 2026; for an existing editable draft use Recalculate draft after fixing source records.
- Review employee count, warnings and the employee breakdown. Gross should be 11,000 and final net 10,800.
- Click Submit for Review and confirm. Resolve pending attendance instead of omitting it; the approval step refuses a run with unacknowledged pending attendance or a negative net.
- Mona opens the run, clicks Approve Payroll and confirms. The figures can no longer be recalculated. Nothing is sent to SolaCount yet.
- Palm Grove pays Yousef 10,800 through its bank. SolaHR does not move money.
- Record payment. For the whole run click Confirm Payroll Paid and confirm (it needs the payroll approval right). The run becomes Paid and both events are queued. Pressing it twice does not queue a second pair: the run is re-checked under a lock and an already Paid run is left unchanged.
- On the run, open Accounting delivery (SolaCount). Wait until Payroll posted and Payroll paid show Delivered with a SolaCount entry reference.
- Layla opens SolaCount Journal entries and finds both entries (memo starts "SolaHR hr.payroll.posted ..." and "SolaHR hr.payroll.paid ...", reference PR-2026-10, source SolaHR). Compare lines and dates with the tables below.
- Back on the run, read Reconciliation with SolaCount: each row should show Matches with a zero Difference.
- Use Generate Payslips (needs its own permission) and check gross, deduction, net and the paid status.
#App handoffs
| Trigger / source | Destination | Type | What transfers | Review and posting | Effect timing | How to verify | Check before retrying |
|---|---|---|---|---|---|---|---|
| Run set to Paid in SolaHR (Confirm Payroll Paid, or the last employee marked paid when the payroll setting for automatic closing is on) | SolaHR outbox, then SolaCount journal API | Queue automatic; user triggers Paid; delivery automatic | Two events: posting totals and payment total, currency, period dates, run id, mapped account roles. Not employee names. | No second approval in SolaCount; the journal is created posted | Posting dated on the period end date (31 Oct 2026); payment dated on the day Confirm Payroll Paid is pressed (SolaHR takes the date from that moment, you cannot type a different bank date) | Accounting delivery (SolaCount) and Reconciliation with SolaCount on the run; SolaCount Journal entries | Look at the Detail column first; do not add manual copies of these journals |
| Approve Payroll | Nothing in SolaCount | None | Nothing | Figures are final | No accounting effect | Delivery table says No accounting events for this run yet. | Confirm the run is Paid, not merely approved |
| Mark Salaries Paid (employee checkboxes) | Nothing, unless every employee is then paid and the payroll setting that closes the run automatically when everything is paid is on | User triggered | Row payment state only | Does not send run journals by itself | Journals only on the run's final Paid transition | Check the run status and delivery table | Use Confirm Payroll Paid if the run stays unpaid |
| A payroll correction (reversal) on a Paid run | SolaHR outbox, then SolaCount | User triggered; delivery automatic | Two reversing events (posting and payment), each negating the original | Each waits (shown as Pending) until its original is delivered; if there is no original event at all (the run was paid before the integration existed) the reversal is Skipped | Dated the day the correction was recorded, after the originals are delivered | Rows Payroll reversed and Payroll payment reversed in the delivery table | One reversal per run is allowed; check the Detail column before retrying |
Delivery status meanings:
| Status shown | Meaning | Action |
|---|---|---|
| Pending / Sending | Queued or in flight | Wait; it is not complete |
| Will retry | A timeout, network error, HTTP 408/425/429 or 5xx. Retried automatically (the schedule runs every five minutes) after 1 min, 5 min, 15 min, 1 h, 3 h, 6 h and 12 h | Wait; the Next attempt time is shown |
| Failed | A 4xx rejection (closed period, unmapped or unknown account, bad credentials, content conflict), or 8 attempts used | Read the Detail, fix the cause, then Retry |
| Skipped | Event date is before Send events dated from, or a reversal has no original to reverse | Normally leave it; Retry rebuilds it if you changed the start date |
| Delivered | SolaCount accepted it (or answered that this exact journal already exists) | Final; never re-sent |
The Retry button is on each row of the run's Accounting delivery (SolaCount) table, next to events that are Pending, Will retry, Failed or Skipped, and only users with the payroll approval right see it. It puts the event back in the queue with its attempt count reset to zero; the next five-minute run picks it up. An event that SolaCount rejected (or that was skipped) is rebuilt from the current account mapping, while one that may already have been committed before a timeout is resent unchanged so the replay is identical. A Delivered or Sending event cannot be retried. Protection against duplicates: every event carries its own key, and SolaCount holds a unique key per organization for each journal; a repeat with identical content returns the journal already created (counted as Delivered), and a repeat with the same key but different content is refused and shows as Failed. This protects SolaCount against a repeated send; it does not stop a user from keying a manual copy of the journal.
#Check your result
Journal 1, Payroll posted, dated 2026-10-31:
| Account (mapping role) | Debit | Credit |
|---|---|---|
| Salary expense | 8,000 | |
| Allowances expense (housing 2,500 + transport 500) | 3,000 | |
| Penalties and other deductions | 200 | |
| Net salaries payable | 10,800 | |
| Total | 11,000 | 11,000 |
Journal 2, Payroll paid, dated the recorded payment date:
| Account | Debit | Credit |
|---|---|---|
| Net salaries payable | 10,800 | |
| Cash or bank | 10,800 |
Expected balances after both are delivered: salary and allowance expense 11,000; bank down 10,800; net-salary payable 10,800 credit minus 10,800 debit = 0. In Reconciliation with SolaCount, the Payroll posting row compares SolaHR's 11,000 (earned expense plus employer contributions) to the delivered debit total 11,000; the Payroll payment row compares 10,800 to 10,800. Not matched yet means something is still pending or failed; Changed after delivery means the live run no longer matches what was captured. A passed connection test alone proves nothing about journals.
If an organization has tax, insurance or employer contributions, the same builder adds Insurance payable, Income tax payable, Employer insurance expense, and Employee advances receivable lines, so the lines differ from this table.
#Common variations
- Advance recovery. The recovered amount is credited to Employee advances receivable and reduces the net payable. See Recover a salary advance through payroll.
- Rounding. If the journal is out of balance by no more than the configured tolerance (default 0.05) and Rounding differences is mapped, the difference is posted there; otherwise the event fails with an unbalanced error.
- Rejected run. Read the reason, fix inputs, resubmit.
- Correction after Paid. Use SolaHR's payroll correction workflow; it queues reversing events for both journals, which wait until the originals are delivered. Layla should review the reversal in SolaCount. A reversal changes the journals only; it does not by itself restore an advance that the run had recovered (see Recover a salary advance through payroll).
- Overtime paid separately, final settlements use their own event types and rows in the same table.
- Another country or contract. Add the tax, insurance and end-of-service settings your jurisdiction requires before relying on any amount.
- Time tracking. SolaHR attendance and timesheets are not linked to SolaProjects time. A search of both deployed apps found only app-launcher menu links between them; no code reads attendance into project time or project time into payroll.
#Mistakes to avoid
- Marking payroll Paid before salaries are paid just to get a journal.
- Entering manual copies of the delivered journals in SolaCount.
- Expecting the journals at approval, or when only some employees are marked paid.
- Treating Test connection, a bank transfer or a payslip as proof of delivery.
- Assuming SolaHR files statutory returns or sends a bank file: it does neither.
- Changing the mapping after delivery and expecting delivered entries to change; delivered events are final.
#Related documentation
Payroll Runs, Accounting integration, Payroll Settings, Payslips, Journal entries, Recover a salary advance through payroll, Business Solutions & Examples.